Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Michael Smith commented on BOLT-832 Re: Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large That 1.2Mb ceiling is not great. I'm going to look into what's happening there. As far as addressing much larger files, I don't think we can provide a good solution before the next major PE release, and our focus for that release is providing an integrated plan workflow that wouldn't suffer from this issue. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title
Dylan Ratcliffe commented on BOLT-832
Re: Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Nick Lewis Using PE I have run the exec task with a parameter "base64 /dev/urandom | head -c {num bytes}" to generate large task responses and the limit I see is around "base64 /dev/urandom | head -c 120" (1.2Mb) much, much lower than the 64Mb that it is designed to handle. The failure mode in this scenario is orchestration-services crashes with no error and restarts. This is using a single monolithic master with one node. While this is clearly an issue as it's more than an order of magnitude lower than expected, this is not the main problem. The main problem is that even if 64Mb did work, it is vastly too low, many enterprise users have to deal with agents from large enterprise software vendors (who shall not be named) that are well into the hundreds of megabytes and installing these using a task is a valid use-case which we should handle. Users running Bolt over SSH or WinRM are used to being able to upload files of almost any size using entirely free software, moving to the paid version of Puppet Enterprise should not result in a reduction in functionality
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-832 Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large Change By: Alex Dreyer Sprint: Bolt Discover/Design Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-832 Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large Change By: Michael Smith Sprint: Bolt Discover/Design Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Nick Lewis commented on BOLT-832 Re: Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large The 65536 byte limit was a regression that will be fixed in the next PE releases. The proper limit, which is configurable, is 64mb. That issue should only have affected the allowable size of task requests, not of responses. Response sizes should have been properly using the configurable 64mb limit. If there’s a problem there, I would love to know more detail. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Neil Binney updated an issue Puppet Task Runner / BOLT-832 Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Adam Bottchen updated an issue Puppet Task Runner / BOLT-832 Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large Change By: Adam Bottchen CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Dylan Ratcliffe commented on BOLT-832 Re: Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large I would disagree with this being minor, it's not a stretch to assume someone using PXP might want to use the file upload functionality to upload an 800Mb file, which would completely bring down orchestration as it's loaded into memory. Adam Bottchen can we please get a CS review of this? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-832 Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large Change By: Alex Dreyer Priority: Major Normal Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title
Dylan Ratcliffe updated an issue
Puppet Task Runner / BOLT-832
Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Change By:
Dylan Ratcliffe
*The Problem:*This is both a PCP/PXP/Orchestrator and bolt problem. When using bolt with pcp transport any tasks that involve sending even remotely large things to the client fail. e.g. using the {{run_script}} function on a script with greater than 65536 characters will cause an exception in the PXP broker and therefore bolt will return "Timed out waiting for provisional response". The {{upload_file}} function is even worse as that will POST an entire (possibly very large) file to the orchestrator API which will in turn try to store it in the database etc. Also any task that returns a large amount of data (>1MB) will cause issues. *Who will find it:*Any user using bolt with PXP will likely come across this. It its Users will not crazy expect there to want to upload be limitations when uploading a 5Mb file or run a 1500 line script, both if which will cause orchestrator/PXP to fall over completely. Users will expect this to work as it works fine over SSH or WinRM and it doesn't make sense that the PE transport has less capability .*Possible Solutions:*The PXP protocol needs to have streaming capabilities added so that it can transfer files in a similar way that users would expect to be able to over SSH. The Orchestrator API also will need to be modified to allow for binary data to be submitted or files uploaded, or something along those lines. Bolt will then need to be modified to take advantage of these features.
Add Comment
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title
Dylan Ratcliffe updated an issue
Puppet Task Runner / BOLT-832
Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Change By:
Dylan Ratcliffe
*The Problem:*This is both a PCP/ PXP /Orchestrator and bolt problem. When using bolt with PXP pcp transport any tasks that involve sending even remotely large things to the client fail. e.g. using the {{run_script}} function on a script with greater than 65536 characters will cause an exception in the PXP broker and therefore bolt will return "Timed out waiting for provisional response". The {{upload_file}} function is even worse as that will POST an entire (possibly very large) file to the orchestrator API which will in turn try to store it in the database etc. Also any task that returns a large amount of data (>1MB) will cause issues. *Who will find it:*Any user using bolt with PXP will come across this. It its not crazy to want to upload a 5Mb file or run a 1500 line script, both if which will cause orchestrator/PXP to fall over completely. Users will expect this to work as it works fine over SSH or WinRM and it doesn't make sense that the PE transport has less capability.*Possible Solutions:*The PXP protocol needs to have streaming capabilities added so that it can transfer files in a similar way that users would expect to be able to over SSH. The Orchestrator API also will need to be modified to allow for binary data to be submitted or files uploaded, or something along those lines. Bolt will then need to be modified to take advantage of these features.
Add Comment
Jira (BOLT-832) Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large
Title: Message Title Dylan Ratcliffe updated an issue Puppet Task Runner / BOLT-832 Orchestrator/PXP/PCP treats everything as text and subsequently fails with anything large Change By: Dylan Ratcliffe Summary: Orchestrator/PXP /PCP treats everything as text and subsequently fails with anything large Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
