Jira (PDB-2097) Disable dujour checkins for Puppet Server during CI runs
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2097 Disable dujour checkins for Puppet Server during CI runs Change By: Ryan Senior Story Points: 2 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2039) PuppetDB node-level securing of command submission
Title: Message Title Andrew Roetker commented on PDB-2039 Re: PuppetDB node-level securing of command submission I'm going to close this ticket and make another to design a different approach for this. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5467) Rspec-puppet not throwing error when hiera value change
Title: Message Title puppeteer commented on PUP-5467 Re: Rspec-puppet not throwing error when hiera value change I already worked on this with John Morgan from puppetlabs. He asked me to raise ticket for this issue. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4426) group resource doesn't work on Windows when members is an array and noop is used
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-4426 group resource doesn't work on Windows when members is an array and noop is used Change By: Ethan Brown Assignee: Ethan Brown 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-443) Get pre-suites working for OSX 10.11 El Capitan (x86_64) for Hiera
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Hiera / HI-443 Get pre-suites working for OSX 10.11 El Capitan (x86_64) for Hiera Change By: Josh Cooper Assignee: Josh Cooper 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5308) Bump puppet 3.x to use beaker ~> 2.23
Title: Message Title Josh Cooper commented on PUP-5308 Re: Bump puppet 3.x to use beaker ~> 2.23 Waiting for 3.8.4 to ship 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5308) Bump puppet 3.x to use beaker ~> 2.23
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-5308 Bump puppet 3.x to use beaker ~> 2.23 Change By: Josh Cooper Assignee: Josh Cooper 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-431) Get pre-suites working for Solaris 11 (SPARC, i386) for Hiera
Title: Message Title Josh Cooper commented on HI-431 Re: Get pre-suites working for Solaris 11 (SPARC, i386) for Hiera Solaris 11 SPARC passed in hiera#master and hiera#stable and Solaris 11 x86 passed in regular CI, so marking this as resolved. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2150) Provide reusable report wire-format code
Title: Message Title Hunter Haugen created an issue PuppetDB / PDB-2150 Provide reusable report wire-format code Issue Type: Improvement Assignee: Unassigned Created: 2015/11/03 3:54 PM Priority: Normal Reporter: Hunter Haugen Currently the code that transforms a puppet report object into a wire-format json payload to be sent to puppetdb lives in the report processor (https://github.com/puppetlabs/puppetdb/blob/3.2.0/puppet/lib/puppet/reports/puppetdb.rb#L28-L187). As a user I want to write my own report processor and submit the reports to puppetdb in a different way. The code is not reusable as it is enclosed in a report processor and is not directly accessible from other report processors, so it needs to be moved into a generic (like lib/puppet/util/puppetdb/*) library that other report processors can access. Add Comment
Jira (PUP-5415) Smoke test packages
Title: Message Title
Hailee Kenney commented on PUP-5415
Re: Smoke test packages
Installing from packages on Ubuntu 14.04 x86_64
oot@kdex2cr7qh1yyzc:~# puppet apply --execute "notify { 'Hello World': }"
Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning')
Notice: Compiled catalog for kdex2cr7qh1yyzc.delivery.puppetlabs.net in environment production in 0.02 seconds
Notice: Hello World
Notice: /Stage[main]/Main/Notify[Hello World]/message: defined 'message' as 'Hello World'
Notice: Finished catalog run in 0.01 seconds
root@kdex2cr7qh1yyzc:~# puppet --version
3.8.4
root@kdex2cr7qh1yyzc:~# puppet help
Jira (PUP-5415) Smoke test packages
Title: Message Title
Hailee Kenney commented on PUP-5415
Re: Smoke test packages
Installing from packages on Debian 7 i386
root@o2wnnyifpx5635g:~# puppet apply --execute "notify { 'Hello World': }"
Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning')
Notice: Compiled catalog for o2wnnyifpx5635g.delivery.puppetlabs.net in environment production in 0.02 seconds
Notice: Hello World
Notice: /Stage[main]/Main/Notify[Hello World]/message: defined 'message' as 'Hello World'
Notice: Finished catalog run in 0.01 seconds
root@o2wnnyifpx5635g:~# puppet --version
3.8.4
root@o2wnnyifpx5635g:~# puppet help
Jira (FACT-1200) Get pre-suites working for Huawei 6 (PowerPC) for Facter
Title: Message Title Michael Stahnke updated an issue Facter / FACT-1200 Get pre-suites working for Huawei 6 (PowerPC) for Facter Change By: Michael Stahnke Sprint: RE 2015-11-11 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5148) Get pre-suites working for Huawei 6 (PowerPC) for Puppet
Title: Message Title Michael Stahnke updated an issue Puppet / PUP-5148 Get pre-suites working for Huawei 6 (PowerPC) for Puppet Change By: Michael Stahnke Sprint: RE 2015-11-11 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5415) Smoke test packages
Title: Message Title
Hailee Kenney commented on PUP-5415
Re: Smoke test packages
Install the gem on Fedora 20 x86_64
[root@xc5xbqq6jzrt78j ~]# puppet apply --execute "notify { 'Hello World': }"
Notice: Compiled catalog for xc5xbqq6jzrt78j.delivery.puppetlabs.net in environment production in 0.03 seconds
Notice: Hello World
Notice: /Stage[main]/Main/Notify[Hello World]/message: defined 'message' as 'Hello World'
Notice: Finished catalog run in 0.20 seconds
[root@xc5xbqq6jzrt78j ~]# puppet --version
3.8.4
[root@xc5xbqq6jzrt78j ~]# puppet help
Usage: puppet [options] [options]
Jira (PUP-5147) Add node definition for Huawei 6 (PowerPC) to Puppet
Title: Message Title Michael Stahnke updated an issue Puppet / PUP-5147 Add node definition for Huawei 6 (PowerPC) to Puppet Change By: Michael Stahnke Sprint: RE 2015-11-11 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1199) Add node definition for Huawei 6 (PowerPC) to Facter
Title: Message Title Michael Stahnke updated an issue Facter / FACT-1199 Add node definition for Huawei 6 (PowerPC) to Facter Change By: Michael Stahnke Sprint: RE 2015-11-11 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-444) Add node definition for Huawei 6 (PowerPC) to Hiera
Title: Message Title Michael Stahnke updated an issue Hiera / HI-444 Add node definition for Huawei 6 (PowerPC) to Hiera Change By: Michael Stahnke Sprint: RE 2015-11-11 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5415) Smoke test packages
Title: Message Title
Hailee Kenney commented on PUP-5415
Re: Smoke test packages
Installing from packages on Centos 7 x86_64
[root@fbx5gj4z1fmfx55 ~]# puppet apply --execute "notify { 'Hello World': }"
Notice: Compiled catalog for fbx5gj4z1fmfx55.delivery.puppetlabs.net in environment production in 0.01 seconds
Notice: Hello World
Notice: /Stage[main]/Main/Notify[Hello World]/message: defined 'message' as 'Hello World'
Notice: Finished catalog run in 0.01 seconds
[root@fbx5gj4z1fmfx55 ~]# puppet --version
3.8.4
[root@fbx5gj4z1fmfx55 ~]# puppet help
Usage: puppet [options] [options]
Jira (PDB-2107) add mq depth to :status key of tk-status response
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2107 add mq depth to :status key of tk-status response Change By: Wyatt Alt Assignee: Wyatt Alt 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2107) add mq depth to :status key of tk-status response
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2107 add mq depth to :status key of tk-status response Change By: Wyatt Alt Sprint: PuppetDB 2015-11- 18 04 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2134) puppetdb 3.2.1 2015-11-09 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2134 puppetdb 3.2.1 2015-11-09 Release Change By: Wyatt Alt Sprint: PuppetDB 2015-11- 04 18 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title
Nathanael Cole commented on PUP-2782
Re: Yumrepo target attribute does not work
Still a bug in 3.8.2.
On CentOS 6.6:
{{ yumrepo {'repo1': baseurl => "http://yumreposerver/yum/OracleLinux/OL6/1/base/i386", descr => 'Bobs Happy Fun Oracle Linux Repo', target => '/etc/yum.repos.d/bob/repo1.repo', ensure => present, enabled => false, gpgcheck => false, }
}}
This creates a "repo1.repo" in /etc/yum.repos.d/ instead of the specified /etc/yum.repos.d/bob/
If reposdir is set to /etc/yum.repos.d/bob/ in yum.conf then it gets placed in that dir instead.
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2134) puppetdb 3.2.1 2015-11-09 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2134 puppetdb 3.2.1 2015-11-09 Release Change By: Wyatt Alt Summary: puppetdb 3.2.1 2015-11- 05 09 Release 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title Nathanael Cole updated an issue Puppet / PUP-2782 Yumrepo target attribute does not work Change By: Nathanael Cole Affects Version/s: PUP 3.8.2 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2134) puppetdb 3.2.1 2015-11-09 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2134 puppetdb 3.2.1 2015-11-09 Release Change By: Wyatt Alt Sprint: PuppetDB 2015-11-04 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2134) puppetdb 3.2.1 2015-11-09 Release
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2134 puppetdb 3.2.1 2015-11-09 Release Change By: Wyatt Alt Story Points: 2 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5387) AIX service provider returns before service operations are complete
Title: Message Title William Hopper updated an issue Puppet / PUP-5387 AIX service provider returns before service operations are complete Change By: William Hopper Comment: And now (confusingly opposed to my previous proposition), I'm wondering if this is something that we should be fixing in our codebase at all. The asynchronous weirdness of AIX services is universal for all services - not just us. Perhaps what we're seeing is actually expected behavior, and it would be weird on our part to alter our startup to loop until finished?If this is the case, then maybe our best course of action would be to work on the tests to accommodate this, rather than somehow patching our own service to behave completely differently than any other service, *or* adding a timeout in the provider which doesn't guarantee the removal of all race conditions.All of this being said, my experience with AIX services is limited, so I will seek out more qualified opinions around this idea. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5469) Indirector cache classes don't validate their return values
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-5469 Indirector cache classes don't validate their return values Change By: Charlie Sharpsteen Affects Version/s: PUP 3.8.4 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2138) Merge master into stable
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2138 Merge master into stable Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git checkout stable
Jira (PDB-2144) Push tag
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2144 Push tag Issue Type: Sub-task Assignee: Morgan Haskel Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment This message was sent by Atlassian JIRA (v6.4
Jira (PDB-2140) Prepare long form release notes and short form release story
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2140 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2135) Is the code ready for release?
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2135 Is the code ready for release? Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.2.1%22
Jira (PDB-2146) Docs pushed
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2146 Docs pushed Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2148) Update dujour to notify users to use 3.2.1
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2148 Update dujour to notify users to use 3.2.1 Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt Update dujour to notify users to use 3.2.1. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2145) Packages pushed
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2145 Packages pushed Issue Type: Sub-task Assignee: Morgan Haskel Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed. Dependencies:
Jira (PUP-5469) Indirector cache classes don't validate their return values
Title: Message Title Charlie Sharpsteen commented on PUP-5469 Re: Indirector cache classes don't validate their return values This issue is also present in Puppet 3.8.x, but the safe_yaml case above is mitigated to some extent because Puppet vendors safe_yaml, loads it at startup, and sets the default behavior to :unsafe. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2141) Tag the release and create packages
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-2141
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Morgan Haskel
Created:
2015/11/03 1:18 PM
Priority:
Normal
Reporter:
Wyatt Alt
Tag and create packages
Developer provides the SHA - Wyatt Alt - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Mak
Jira (PDB-2136) Reconcile git commits and JIRA tickets
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2136 Reconcile git commits and JIRA tickets Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into an earlier release (stable), but the ticket's fixVersion is not updated.
Jira (PDB-2143) Go/no-go meeting (before 4pm)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2143 Go/no-go meeting (before 4pm) Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: Wyatt Alt Nicholas Fagerlund Beth Cornils Kurt Wall Morgan Haskel
Jira (PDB-2134) puppetdb 3.2.1 2015-11-05 Release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2134 puppetdb 3.2.1 2015-11-05 Release Issue Type: Task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt puppetdb 3.2.1 2015-11-05 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PDB-2139) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2139 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone
Jira (PDB-2149) Close all resolved tickets in Jira
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2149 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.2.1%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PDB-2137) Update version number in source
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2137 Update version number in source Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt Bump VERSION in lib/PDB/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (PDB-2142) Smoke test packages
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2142 Smoke test packages Issue Type: Sub-task Assignee: Wyatt Alt Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output. When all platforms
Jira (PDB-2147) Send out announcements
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2147 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 2015/11/03 1:18 PM Priority: Normal Reporter: Wyatt Alt Morgan Haskel: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available" Dependencies:
Jira (PUP-5387) AIX service provider returns before service operations are complete
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5387 AIX service provider returns before service operations are complete Change By: William Hopper Assignee: William Hopper 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5446) Revamp release ticket process
Title: Message Title William Hopper commented on PUP-5446 Re: Revamp release ticket process See https://github.com/puppetlabs/packaging/pull/460 for preliminary PR. There are still a few questions there and a few things to be addressed. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5446) Revamp release ticket process
Title: Message Title William Hopper updated an issue Puppet / PUP-5446 Revamp release ticket process Change By: William Hopper Comment: I've started taking notes on things that should change for roughly the first half of the process and will continue finding things until the end of the 1.2.7 release. At the end of it all, I plan to update all of the ticket-generating rake tasks. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5469) Indirector cache classes don't validate their return values
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-5469 Indirector cache classes don't validate their return values Issue Type: Bug Affects Versions: PUP 4.2.3 Assignee: Unassigned Components: Platform Created: 2015/11/03 1:07 PM Labels: support Priority: Normal Reporter: Charlie Sharpsteen Puppet uses the YAML indirector terminii to cache various pieces of data. Catalog compilation relies on this terminus to maintain the state of agent facts during operations such as node retrieval. If facts cannot be read from the cache, the compiler will fall back to retrieving them from PuppetDB which triggers PUP-5441 and can result in a catalog that was compiled using stale information. The YAML terminii do not perform any validation to ensure an oject of the proper type is being returned from the cache. Thus, if something adjusts the behavior of Ruby YAML serialization and deserialization, compilation will start failing with cryptic errors or, in some cases, co
Jira (PUP-5415) Smoke test packages
Title: Message Title Henrik Lindberg commented on PUP-5415 Re: Smoke test packages Packages are at: http://builds.puppetlabs.lan/puppet/3.8.4/ 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2133) Add config options for turning on pretty-printing globally
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2133 Add config options for turning on pretty-printing globally Issue Type: New Feature Assignee: Unassigned Created: 2015/11/03 12:50 PM Fix Versions: PDB 4.0.0 Priority: Normal Reporter: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You receive
Jira (PUP-4934) Unit tests for static compiler are broken
Title: Message Title Josh Cooper commented on PUP-4934 Re: Unit tests for static compiler are broken The root cause for why the tests are broken will be fixed in PUP-5035, see https://github.com/joshcooper/puppet/commit/338ee79006541bfd40aa7ec6240fcc75a5bbc2bc. However, I'll leave this ticket open so that we can audit which tests need to be added as a result of recent static compiler changes. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2128) Add an atom to turn on GC and another to store catalogs historically.
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2128 Add an atom to turn on GC and another to store catalogs historically. Issue Type: New Feature Assignee: Unassigned Created: 2015/11/03 9:24 AM Priority: Normal Reporter: Andrew Roetker Add a GC task for sweeping historical catalogs. Add the ability to turn-on historical catalog storage. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5415) Smoke test packages
Title: Message Title
Eric Thompson commented on PUP-5415
Re: Smoke test packages
64bit MSI on windows2012r2:
PS C:\Users\Administrator> puppet apply -e 'notice $::os'
Notice: Scope(Class[main]): {"name"=>"windows", "family"=>"windows", "release"=>{"major"=>"2012 R2", "full"=>"2012 R2"}}
Notice: Compiled catalog for xvzn5snz2vybtmc.delivery.puppetlabs.net in environment production in 0.02 seconds
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you
Jira (PUP-3713) Allow zfs to create a zvol
Title: Message Title Michael Smith updated an issue Puppet / PUP-3713 Allow zfs to create a zvol Change By: Michael Smith Affects Version/s: PUP 3.8.4 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2130) check for updates should print something if version is latest
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2130 check for updates should print something if version is latest Issue Type: Improvement Assignee: Unassigned Created: 2015/11/03 10:37 AM Priority: Normal Reporter: Wyatt Alt Right now the update check only prints a startup message if the version is outdated. If it printed when the version is current we'd have a bit more certainty on whether it's functioning in the master branch at any given time. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-3713) Allow zfs to create a zvol
Title: Message Title Michael Smith updated an issue Puppet / PUP-3713 Allow zfs to create a zvol Change By: Michael Smith Issue Type: Improvement Bug 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3713) Allow zfs to create a zvol
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-3713 Allow zfs to create a zvol Change By: Michael Smith Assignee: Kylo Ginsberg Michael Smith 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2132) Add a `resources-graph` view for CM folks
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2132 Add a `resources-graph` view for CM folks Issue Type: New Feature Assignee: Unassigned Created: 2015/11/03 10:53 AM Priority: Normal Reporter: Andrew Roetker Currently CM uses https://github.com/puppetlabs/pe-console-middleware/blob/master/src/puppetlabs/pe_console_middleware/cm/graph.clj to construct the resources graph view for the UI. We should add an endpoint which constructs this view for them and can do it for at least 2 previous catalogs. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2131) Use the FOSS mechanisms to turn on historical catalogs in PE.
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2131 Use the FOSS mechanisms to turn on historical catalogs in PE. Issue Type: New Feature Assignee: Unassigned Created: 2015/11/03 10:51 AM Priority: Normal Reporter: Andrew Roetker This works consists of altering the Historical Catalog storage FOSS atoms added in the other historical catalogs tickets on startup on the PE routing service to turn on historical catalog storage. This work should also include adding testing around historical catalog storage. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (HI-471) Allow backends to perform Qualified Key Lookup
Title: Message Title Sean Griffin assigned an issue to qa Hiera / HI-471 Allow backends to perform Qualified Key Lookup Change By: Sean Griffin Status: Ready for CI Test Assignee: qa 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5425) puppet lookup creates phantom node
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5425 puppet lookup creates phantom node Change By: Sean Griffin Status: Ready for CI Test Assignee: qa 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5441) $trusted is not available in master compile and fails when coming from PDB
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5441 $trusted is not available in master compile and fails when coming from PDB Change By: Sean Griffin Status: Ready for CI Test Assignee: qa 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3713) Allow zfs to create a zvol
Title: Message Title
Michael Smith commented on PUP-3713
Re: Allow zfs to create a zvol
A quick example of this failing on a Solaris 11 (i386) box:
mkdir /ztstpool
mkfile 64m /ztstpool/dsk
zpool create tstpool /ztstpool/dsk
zfs create -o volsize=8192 tstpool/tstfs
zfs create -V 8192 tstpool/tstfs
The commantd zfs create -o volsize=8192 tstpool/tstfs is what Puppet currently does for
zfs {"tstpool/tstfs":
ensure => present,
volsize => 8192,
}
Jira (PUP-5414) Tag the release and create packages
Title: Message Title Morgan Haskel commented on PUP-5414 Re: Tag the release and create packages Updated packages, built off of b628b07eb521caacc920f8b87749974d269a58bc, are up at http://builds.puppetlabs.lan/puppet/3.8.4/ 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5309) Yum package provider: ensure => latest fails when kernel is updated but not current
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5309 Yum package provider: ensure => latest fails when kernel is updated but not current Change By: Eric Thompson Assignee: qa Eric Thompson 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5309) Yum package provider: ensure => latest fails when kernel is updated but not current
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5309 Yum package provider: ensure => latest fails when kernel is updated but not current Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Medium QA Risk Severity Reason: only when updating security releases QA Risk Probability: Low QA Risk Severity: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-3713) Allow zfs to create a zvol
Title: Message Title Michael Smith commented on PUP-3713 Re: Allow zfs to create a zvol I'm curious when you say "volsize property must be specified explicity when creating a zvol and can not be passed as a property". If it can't be set later, what does setting volsize on the type do? Wouldn't that be a bug? I'd like to see an example of what prompted the need for this. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4516 Agent does not stop with Ctrl-C Change By: Josh Cooper Fix Version/s: PUP 3.8.4 Fix Version/s: PUP 3.8.5 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4516 Agent does not stop with Ctrl-C Change By: Eric Thompson QA Status: Reviewed 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5414) Tag the release and create packages
Title: Message Title Morgan Haskel commented on PUP-5414 Re: Tag the release and create packages We have decided to go back and build off of the original SHA, b628b07eb521caacc920f8b87749974d269a58bc 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4516 Agent does not stop with Ctrl-C Change By: Eric Thompson QA Risk Assessment Reason: regression QA Highest Test Level: Acceptance QA Risk Probability Reason: ticket contains many users requesting a fix QA Risk Assessment: High QA Risk Probability: Medium QA Risk Severity: High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Eric Thompson commented on PUP-4516 Re: Agent does not stop with Ctrl-C validated on ubuntu14 at 3.x SHA: aeacf3add8eaae4b15c03ea4aa925f6ee98228d7 with root@hst14wwg6mi6qd8:~# puppet agent -t Info: Retrieving pluginfacts Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://hst14wwg6mi6qd8.delivery.puppetlabs.net/pluginfacts Info: Retrieving plugin Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://hst14wwg6mi6qd8.delivery.puppetlabs.net/plugins ^CNotice: Caught INT; exiting root@hst14wwg6mi6qd8:~# puppet agent -t Info: Retrieving pluginfacts Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve information from environment production source(s) puppet://hst14wwg6mi6qd8.delivery.puppetlabs.net/pluginfacts
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4516 Agent does not stop with Ctrl-C Change By: Eric Thompson Assignee: qa Eric Thompson 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2129) Detail a design for "masterless"-secure command submission
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2129 Detail a design for "masterless"-secure command submission Issue Type: Task Affects Versions: PDB 3.2.0 Assignee: Unassigned Created: 2015/11/03 10:02 AM Priority: Normal Reporter: Andrew Roetker Currently when running PuppetDB in a masterless environment, any node can submit commands for any other node. Currently when using the cert-whitelist config item in PuppetDB, every node which tries to submit commands or query PuppetDB, must be on the cert-whitelist. For "masterless" users we need to support securing command submission by restricting the ability of nodes to only submit commands for themselves, but we also need to be able to supply users with the ability to config a list of nodes which can submit commands for any nodes (such as a console/gui node). We cannot use the cert-whitelist in its current form because of the reasons listed above. Add Comment
Jira (PDB-2099) Fix test-latest-version duplication in puppetlabs.puppetdb.meta-test
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2099 Fix test-latest-version duplication in puppetlabs.puppetdb.meta-test Change By: Ryan Senior Story Points: 1 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2104) Upgrade to clojure 1.8.0beta2
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2104 Upgrade to clojure 1.8.0beta2 Change By: Ryan Senior Story Points: 1 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2100) puppetdb ssl-setup fails when environment is not production
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2100 puppetdb ssl-setup fails when environment is not production Change By: Ryan Senior Story Points: 2 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2112) benchmark -A flag is broken
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2112 benchmark -A flag is broken Change By: Ryan Senior Story Points: 1 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2069) Spike: determine what client libs we need to support
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2069 Spike: determine what client libs we need to support Change By: Ryan Senior Story Points: 2 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2073) Sync efficiency: use the report summary in sync
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2073 Sync efficiency: use the report summary in sync Change By: Ryan Senior Story Points: 3 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2069) Spike: determine what client libs we need to support
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2069 Spike: determine what client libs we need to support Change By: Ryan Senior Sprint: PuppetDB 2015- 12 11 - 02 18 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2069) Spike: determine what client libs we need to support
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2069 Spike: determine what client libs we need to support Change By: Ryan Senior Sprint: PuppetDB 2015- 11 12 - 18 02 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2068) Document expected client failover behavior
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2068 Document expected client failover behavior Change By: Ryan Senior Sprint: PuppetDB 2015- 11 12 - 18 02 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2127) Accommodate historical reports in FOSS PDB
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2127 Accommodate historical reports in FOSS PDB Issue Type: New Feature Assignee: Unassigned Created: 2015/11/03 9:21 AM Priority: Normal Reporter: Andrew Roetker Add a migration for the new database schema in the historical catalogs design doc. Change our query-rec for catalogs for the new schema. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2127) Accommodate historical catalogs in FOSS PDB
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2127 Accommodate historical catalogs in FOSS PDB Change By: Andrew Roetker Summary: Accommodate historical reports catalogs in FOSS PDB 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2124) Please support some database besides PostgresQL
Title: Message Title Johnson Earls commented on PDB-2124 Re: Please support some database besides PostgresQL MySQL is the most acceptable choice; Oracle would be a second choice. PostgreSQL has been declared taboo by the corporate security team, for some reason I cannot fathom. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2126) Add the `catalog_uuid` field to catalogs and `reports`
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2126 Add the `catalog_uuid` field to catalogs and `reports` Issue Type: New Feature Assignee: Unassigned Created: 2015/11/03 8:59 AM Priority: Normal Reporter: Andrew Roetker 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 http://groups.google.com/group/puppet-bugs. For more options, vis
Jira (PDB-2125) Burnside related historical catalog support
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2125 Burnside related historical catalog support Issue Type: Epic Assignee: Unassigned Created: 2015/11/03 8:58 AM Priority: Normal Reporter: Andrew Roetker 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.
Jira (PDB-997) Add Ubuntu 14.04/trusty to acceptance testing
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-997 Add Ubuntu 14.04/trusty to acceptance testing Change By: Ryan Senior Sprint: PuppetDB 2015-10-21, PuppetDB 2015- 11 12 - 18 02 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5097) Hostname and Domain as trusted facts
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5097 Hostname and Domain as trusted facts Change By: Michael Smith Status: Ready for CI Test Assignee: qa 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5309) Yum package provider: ensure => latest fails when kernel is updated but not current
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5309 Yum package provider: ensure => latest fails when kernel is updated but not current Change By: Michael Smith Status: Ready for CI Test Assignee: qa 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5278) puppet lookup --explain produces unhelpful reference
Title: Message Title Sean Griffin commented on PUP-5278 Re: puppet lookup --explain produces unhelpful reference Hi Thomas Hallgren, This gist contains a manifest that can be applied to instantiate the data store configuration I was using: https://gist.github.com/segatspiretech/553dc42ffea0f7156553 I did the following to get set up: (1) allocated a vm from vmpooler, redhat-7-x86_64, (2) installed a recent rpm from builds.puppetlabs.com/puppet-agent (3) scp'd this file (apply_lookup) to the vm at /tmp. (4) applied that manifest (puppet apply /tmp/apply_lookup) (5) The lookup commands should work after that. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2124) Please support some database besides PostgresQL
Title: Message Title Kenneth Barber commented on PDB-2124 Re: Please support some database besides PostgresQL Hi, So there has been requests in the past for different database support, but without a lot of good reasons, we possibly won't be doing this in a hurry. Of course if we had enough support from the community to support a database variant this would make it easier. More so, what is the correct database to choose, for example in your case - what would be the preferred database? Up until now we've only really received requests for Oracle support from our commercial customers, if this fits the bill and you are a commercial customer I'd reach out to our sales guys. I'm curious, why won't your company allow PostgreSQL without written approval from the CEO? Whats the reasoning behind this decision in your company? I've never heard of a company making this call before, although I'm sure it happens. Is there a technical reason why PostgreSQL isn't acceptable? In the past most of the reasons for a company choosing one database over another is for local support reasons (ie. you have DBA's skilled in other tech) but usually doesn't result in a complete block on using PostgreSQL, just a reluctance to implement it. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5278) puppet lookup --explain produces unhelpful reference
Title: Message Title Henrik Lindberg commented on PUP-5278 Re: puppet lookup --explain produces unhelpful reference follow up PR merged to master at: 8f9b339 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2122) Single Query Endpoint
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2122 Single Query Endpoint Change By: Kenneth Barber Scope Change Category: Adopted Scope Change Reason: Out of work in sprint, and this is a PQL work pre-cursor Sprint: PuppetDB 2015-11- 18 04 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1926) PQL: Socialise design with architecture teams
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1926 PQL: Socialise design with architecture teams Change By: Kenneth Barber Sprint: PuppetDB 2015-12- 02 16 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2122) Single Query Endpoint
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-2122 Single Query Endpoint Change By: Kenneth Barber Assignee: Kenneth Barber 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1925) PQL: Create second prototype for TQL-like querying
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1925 PQL: Create second prototype for TQL-like querying Change By: Kenneth Barber Story Points: 2 5 Summary: PQL: Update Create second prototype so it reflects latest query design & decisions for TQL-like querying Fix Version/s: PDB 4.0.0 The current prototype here: https://github.com/kbarber/puppetdb/tree/ticket/master/pql needs to be updated to reflect the new decisions around the design of PQL.In particular:* The current currently reflects a SQL syntax needs to be changed to -like query language, but we should fork this and create the new format* We need to add implicit subquery support (PDB TQL - 1924) like query language version also. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2122) Single Query Endpoint
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-2122 Single Query Endpoint Issue Type: New Feature Assignee: Unassigned Created: 2015/11/03 5:40 AM Fix Versions: PDB 4.0.0 Priority: Normal Reporter: Kenneth Barber As part of the PQL prototype here, I created an endpoint, that allowed any query across any context: https://github.com/puppetlabs/puppetdb/compare/master...kbarber:ticket/master/pql This endpoint was primarily design for PQL querying, but we should consider making this work for our existing AST syntax first. The idea would be to have a single-endpoint that can allow both AST or PQL querying later on though, so determining a way of detecting or informing of the type of query would be helpful. The current PQL design talked about having the query hang off: /pdb/query/v4?query= or something like that. This isn't just about an endpoint, we also need a query language methodology around 'setting' the context, some ideas: ["context", "nodes", ]
