Jira (PDB-3655) PuppetDB query tutorial doesn't explain how to get puppetdb_query function
Title: Message Title Isaac Eldridge moved an issue PuppetDB / PDB-3655 PuppetDB query tutorial doesn't explain how to get puppetdb_query function Change By: Isaac Eldridge Workflow: Documentation Scrum Team Workflow Key: DOC PDB - 3262 3655 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3584) System requirements for puppet agent version are wrong
Title: Message Title Isaac Eldridge moved an issue PuppetDB / PDB-3584 System requirements for puppet agent version are wrong Change By: Isaac Eldridge Method Found: Needs Assessment Component/s: PuppetDB Component/s: PuppetDB Workflow: Documentation Scrum Team Workflow Key: DOCUMENT PDB - 691 3584 Project: Documentation PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3322) PuppetDB fails to update catalogs when sensitive parameters are added
Title: Message Title Isaac Eldridge updated an issue PuppetDB / PDB-3322 PuppetDB fails to update catalogs when sensitive parameters are added Change By: Isaac Eldridge Labels: davis-triage docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Isaac Eldridge updated an issue PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: Isaac Eldridge Labels: docs_reviewed maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Isaac Eldridge commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error Which PE versions will is this fixed in? 2016.4.4 and Glisan? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3322) PuppetDB fails to update catalogs when sensitive parameters are added
Title: Message Title Isaac Eldridge commented on PDB-3322 Re: PuppetDB fails to update catalogs when sensitive parameters are added Which PE versions will is this fixed in? 2016.4.4 and Glisan? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Isaac Eldridge commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error please use the docs tab to indicate if this needs a release note or not Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Isaac Eldridge updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Isaac Eldridge Release Notes Summary: PostgreSQL CPU usage increase After upgrading a split install to 2016.5.1 or 2016.5.2, PostgreSQL related CPU usage increases by around 50 % percent . To workaround this issue, use we've created the puppetlabs- pdb_3323_workaround module to create and manage an index that provides a short-term fix: . 1. On the Puppet master, download the [module]( https://forge.puppet.com/puppetlabs/pdb_3323_workaround ).2. Classify the node hosting pe-postgresql with the `pdb_3323_workaround` class.3. On the Puppet master and the node hosting pe-postgresql, run Puppet.After you install this module, it's safe to ignore. The class will be removed when you upgrade in the future. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Isaac Eldridge updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW here's the full text: PuppetDB node CPU usage increase After upgrading a split install to 2016.5.1 or 2016.5.2, CPU usage on the PuppetDB node increases by 50 percent. To workaround this issue, you can add an index to the reports table. On the PuppetDB node, run the following command: ~~~ su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -c \"CREATE UNIQUE INDEX CONCURRENTLY _idx_reports_hash on reports(hash)\"" ~~~ PDB-3323 -> Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Isaac Eldridge updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Isaac Eldridge Comment: here's the full text:## PuppetDB node CPU usage increaseAfter upgrading a split install to 2016.5.1 or 2016.5.2, CPU usage on the PuppetDB node increases by 50 percent. To workaround this issue, you can add an index to the reports table.On the PuppetDB node, run the following command:~~~su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -c \"CREATE UNIQUE INDEX CONCURRENTLY _idx_reports_hash on reports(hash)\""~~~ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Isaac Eldridge commented on PDB-3323 Re: Checking if a report exists before inserting it is SLOW removing the known issue at the request of Nick Walker Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Isaac Eldridge updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Isaac Eldridge Labels: docs_reviewed flanders-ss maintenance tcse Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Isaac Eldridge commented on PDB-3323 Re: Checking if a report exists before inserting it is SLOW Added known issue for 2016.5.2. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3313) PQL docs do not give working examples for class based searchs
Title: Message Title Isaac Eldridge moved an issue PuppetDB / PDB-3313 PQL docs do not give working examples for class based searchs Change By: Isaac Eldridge Workflow: Documentation Scrum Team Workflow Key: DOC PDB - 3114 3313 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3206) PuppetDB queries for classes must capitalize first letter of class name
Title: Message Title Isaac Eldridge moved an issue PuppetDB / PDB-3206 PuppetDB queries for classes must capitalize first letter of class name Change By: Isaac Eldridge Component/s: PuppetDB Component/s: PuppetDB Workflow: Documentation Scrum Team Workflow Key: DOC PDB - 3008 3206 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (PDB-3188) puppetdb token auth documentation is vauge on what permissions needed
Title: Message Title Isaac Eldridge moved an issue PuppetDB / PDB-3188 puppetdb token auth documentation is vauge on what permissions needed Change By: Isaac Eldridge Component/s: DOCS Component/s: DOCS Workflow: Documentation Scrum Teams Workflow Key: DOC PDB - 2996 3188 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PDB-3177) Dead links in the PuppetDB Documentation pages
Title: Message Title Isaac Eldridge moved an issue PuppetDB / PDB-3177 Dead links in the PuppetDB Documentation pages Change By: Isaac Eldridge Workflow: Documentation Scrum Teams Workflow Key: DOC PDB - 2992 3177 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3081) PuppetDB docs do not explain unsetting of node_ttl and node_purge_ttl is equivalent to 0s
Title: Message Title Isaac Eldridge moved an issue PuppetDB / PDB-3081 PuppetDB docs do not explain unsetting of node_ttl and node_purge_ttl is equivalent to 0s Change By: Isaac Eldridge Workflow: Documentation Scrum Teams Workflow Key: DOC PDB - 2954 3081 Project: Documentation [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3081) PuppetDB docs do not explain unsetting of node_ttl and node_purge_ttl is equivalent to 0s
Title: Message Title Isaac Eldridge commented on PDB-3081 Re: PuppetDB docs do not explain unsetting of node_ttl and node_purge_ttl is equivalent to 0s Moving this into the PDB project on advice of Wyatt. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PUP-6660) cached catalogs setting not respected when --test is specified
Title: Message Title Isaac Eldridge commented on PUP-6660 Re: cached catalogs setting not respected when --test is specified Ryan Coleman, if you can please fill out the docs tab with the release note info, I'll work with Jorie Tappa to make sure it's documented in the right places. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install or upgrades of PE, they're enabled globally with application orchestration or not. * If file-sync is enabled, file metadata will be inlined into the catalog. If file-sync is not enabled, file metadata will not be inlined and catalog compilation will precede as it did prior to static catalogs.* If users opt out of file sync and want to use static catalogs, they'll need to follow the OSS instructions for reaching those endpoints. Note that if both endpoints aren't included, Puppet Server will fail.h2. Turn it offglobal setting (puppet.conf, [main]) or per-environment (environment.conf [main])h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired stateh2. Question* If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install or upgrades of PE, they're enabled globally with application orchestration or not. * If users opt out of file sync and want to use static catalogs, they'll need to follow the OSS instructions for reaching those endpoints. Note that if both endpoints aren't included, Puppet Server will fail. h2. Turn it offglobal setting (puppet.conf, [main]) or per-environment (environment.conf [main])h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state * (I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me) h2. Question* If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install of PE, they're enabled globally if you choose to enable with application orchestration . You can later turn static catalogs on or off per environment not . (Outside of app orchestration, we still don't know what the behavior will be.) * During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade.* Documentation tracking off PE-13884.h2. Turn it offglobal setting (puppet.conf, [main]) or per-environment (environment.conf [main])h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state* (I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me)h2. Question* If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install or upgrades of PE, they're enabled globally with application orchestration or not. * During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade. * Documentation tracking off PE-13884. h2. Turn it offglobal setting (puppet.conf, [main]) or per-environment (environment.conf [main])h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state* (I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me)h2. Question* If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install of PE, they 're enabled globally if you choose to enable application orchestration. You can later turn static catalogs on or off per environment. (Outside of app orchestration, we still don't know what the behavior will be.) * During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade.* Documentation tracking off PE-13884.h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state* (I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me)h2. Question* If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install of PE, they enabled globally if you choose to enable application orchestration. You can later turn static catalogs on or off per environment.* During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade. * Documentation tracking off PE-13884. h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state* ( I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me . ) h2. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge updated an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Change By: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following:h2. Enabling static catalogs * During fresh install of PE, they enabled globally if you choose to enable application orchestration. You can later turn static catalogs on or off per environment.* During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade.* Documentation tracking off PE-13884.h2. Conceptual overview info* In PE Burnside, this is mostly new functionality to alleviate the issues caused by agents [running off cached catalog when participating in application orchestration services|http://docs.puppetlabs.com/pe/latest/orchestrator_install.html#prepare-your-agents-for-orchestration-services]. * Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content* Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated with specific versions of content* The agent with static catalog enabled will only contact the master when it knows the file contents don't match desired state* (I'm working with Joe Wagner to hopefully get UX resources to draw up graphic [~josh] created while explaining this to me)h2. Question * If you want to push new "static catalogs" to environments do you use the orchestrator and/or any regular puppet run? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge created an issue Puppet / PUP-5766 (Static Catalog) PE documentation for static catalogs in Burnside Issue Type: Task Assignee: Isaac Eldridge Components: DOCS Created: 2016/01/28 11:17 AM Priority: Normal Reporter: Isaac Eldridge For PE documentation of static catalogs, I'm planning on covering the following: Enabling static catalogs During fresh install of PE, they enabled globally if you choose to enable application orchestration. You can later turn static catalogs on or off per environment. During upgrades of PE, nothing happens. You must manually enable static catalogs, per environment, after upgrade. Conceptual overview info Describe the concepts behind how and why to use static catalogs; i.e., if file content on master changes, agents could be using incorrect content Static catalogs ensure agents get always get correct file content as original catalog will have unique SHA (content_uri) associated
Jira (PUP-5766) (Static Catalog) PE documentation for static catalogs in Burnside
Title: Message Title Isaac Eldridge commented on PUP-5766 Re: (Static Catalog) PE documentation for static catalogs in Burnside Josh Cooper, Eric Sorenson, Ryan Coleman. The way we document static catalogs will be slightly different (in audience and tone) than for OSS. I'm trying to put together an outline for what I'll cover. Can you indicate if I'm on the right track or not? I appreciate your help and feedback. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-513) Add disk space requirements to sys req page
Title: Message Title Isaac Eldridge created an issue PuppetDB / PDB-513 Add disk space requirements to sys req page Issue Type: Task Assignee: Unassigned Created: 14/Mar/14 10:15 AM Labels: Deluxe PE_3.x Priority: Normal Reporter: Isaac Eldridge Work with Meth and Eng. to get a set of disk space requirements for PDB. Add these to install_system_req. Also, if there any additional maintenance tasks or information we can give on how to limit and/or reduce db size, those should get added to the maintenance page. Add Comment
