Jira (PUP-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg commented on PUP-4468 Re: AIO Upgrade Module Yeah agreed that managing stringify_facts in this module is too late. It's one of the prerequisites for this module. Managing that setting could be done in a variety of ways, e.g. the inifile module, etc, and there may be demand for improving that experience, but that's a different topic than this epic for this module. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Eric Sorenson commented on PUP-4468 Re: AIO Upgrade Module stringify_facts has been off by default in PE since PE3.7, and we talk about it pretty extensively in the upgrade/migration tooling. So I don't think the preview module needs to try to be compatible with it. Turning it off at upgrade time doesn't seem to help because that would need to be done in advance, as part of the future parser migration. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg commented on PUP-4468 Re: AIO Upgrade Module Mike Hall this is the upgrade module ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Heidi Pio commented on PUP-4468 Re: AIO Upgrade Module We currently have the (blocked) module release ticket in the May 20 sprint, supporting that goal. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Eric Sorenson commented on PUP-4468 Re: AIO Upgrade Module Yes it should definitely be supported. It should not be PE-only, as it affects everyone taking a 3.x infrastructure to Puppet 4. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg commented on PUP-4468 Re: AIO Upgrade Module Alexander Johnson we're shooting for 3.8.1 next week. The first cut of this module is more likely a week after that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Alexander Johnson commented on PUP-4468 Re: AIO Upgrade Module Is the thinking that the module is going out in a week or so? or 3.8.1? or both Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Alexander Johnson commented on PUP-4468 Re: AIO Upgrade Module To be clear ... Will this be a supported module, released on the Forge? I'm about to send out a document, outlining the release process for supported modules. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg commented on PUP-4468 Re: AIO Upgrade Module Will this be a supported module, released on the Forge? That is definitely what I've been assuming, but /cc Eric Sorenson to confirm. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4468 AIO Upgrade Module Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title John Duarte commented on PUP-4468 Re: AIO Upgrade Module Will this be a PE only module for PE 3.8? Since there is no actual puppet 3.8 release, I want to clarify under what context(s) the following statement applies: Specifically, the module will run on: 3.8 with future parser 4.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg commented on PUP-4468 Re: AIO Upgrade Module Since there is no actual puppet 3.8 release We're planning to release 3.8.1 in the next week or so. My thinking was that this module should work with any released 3.8.z version. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module what are the versions of Puppet - is - (it) supports (3.x?) We are only supporting upgrades from 3.8.0 to 4.y. There will be behavior differences when running on puppet 3.8 and = 4.0, though I don't think we need acceptance testing for that. This question is for rspec-puppet testing. The module team runs specs via rspec-puppet and different versions of puppet are used like different versions of ruby. The version of puppet to install is passed into the Gemfile via the PUPPET_GEM_VERSION environment variable. See a good example of a Gemfile here. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module One thing that just struct me was that usually in a request for a module pipeline there's a name for the module already. What will the name for the module be (and there's a convention assumed of being puppetlabs-module-name) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg commented on PUP-4468 Re: AIO Upgrade Module should it include testing against future parser and strict variables (enable Puppet 4 feature flags – default: yes)? Initially I was thinking no, since future parser is no longer a setting in puppet 4. But since the module needs to run on a 3.8 agent where future parser might be enabled, I think it would be good to test. It might also be possible to test this in a unit test. might be enabled = should be enabled. Specficially, the module will run on: 3.8 with future parser 4.0 3.8 with current parser is not a supported/recommended way to run the module. That restriction doesn't need to be enforced, but can just be documented. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module From initial blush, I'd like to just go ahead and create the pipeline once we have a repo set up with the values listed above and then we can iterate if there's issues that arise. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module It may be important to point out that the module team doesn't write bare rspec tests only rspec-puppet and beaker-rspec tests and they have refused any PRs that touch the underlying system. If there's going to be rspec tests that test the underlying operating system the module team's pipeline isn't going to work. There are tickets (related to QENG-1633) to set up module pipelines for the Window's team that are an amalgamation of the platform team's spec workflow and the module team's acceptance testing workflow. However that's a work in progress and isn't as well automated as the module team's workflow yet. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module FWIW, there's also these docs that are important to scoping work with a supported module: RE Supported Release Process Module Team Checklist Intro to Module Team Practices and Tools Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module A basic module pipeline is up here (with Ruby 1.8). I will enable it (and iterate on it) once dev is ready to go! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module what is the command to run the acceptance tests (bundle exec rspec spec/acceptance)? Why not rake? The MVP of beaker-rspec was to allow module developers to run their acceptance tests via the same style of short command line invocation that they use to run their other tests. That, of course, doesn't preclude using rake to wrap that command, and since the beaker-rspec MVP the community added a rake task for doing exactly that. However, I haven't discussed with the module team if they'd like to update their default since then and they haven't approached me about it. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module what are the platforms it supports at the acceptance level? (all PE supported Linices?) Initially, I'd suggest starting with tier 1 open source platforms. Eventually this should also include PE supported platforms including Windows. For some context, the module team's acceptance pipelines are split into several steps: Step 5 is the first acceptance test job. It's for fast feedback/smoke testing/if-and-when-we-ever-get-pr-testing-what-will-be-tested-on-pr. Even though there is explicitly no support for FOSS it uses FOSS installs because it has been traditionally much faster to install than a PE stack. It is between 2 and 4 platforms, whatever gives the best bang for buck testing wise. The module team hasn't approached me about updating them, but I have a feeling we should (since they were created we created testing tiers and rhel7 has become mainstream). Step 6 is against all PE supported platforms that the module supports using the latest released version of PE. This is the explicitly supported test matrix for the module, though it is situated so that it can be ran nightly (if there's been commits) when we need to constrain resources. Step 7 is additional testing against upcoming platform features. There are multiple jobs in this step, currently they are: 7.a – PE next testing. These are typically enabled once PE next goes code complete. Testing against a tagged RC for these modules is a release criteria for PE. 7.b – Future platform support. These are jobs that run with future parser and strict variables (and any toggles the platform team has opened up to the community for preparing for future releases of the platform that the module team is concerned with). Add Comment
Jira (PUP-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4468 AIO Upgrade Module Change By: Kylo Ginsberg ThisepictrackstheMVPofanAIOupgrademodule. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg commented on PUP-4468 Re: AIO Upgrade Module John Duarte and Justin Stoller, thoughts on the testing approach for this module? I'm not sure if we have any precedent for a module that does an upgrade. If not, and if beaker doesn't currently have support for that, we may need to fall back to unit tests and manual acceptance tests for an initial release. But I'd appreciate your thoughts on the subject. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4468) AIO Upgrade Module
Title: Message Title Justin Stoller commented on PUP-4468 Re: AIO Upgrade Module I usually ask two sets of questions wrt setting up a module pipeline, first around infrastructure/tooling: I don't see any unusual infrastructure needs for this testing, please correct me if I'm wrong. As far as tooling goes, beaker supports upgrades for PE and in a normal situation could support them fine for FOSS. However, what we'd be doing in beaker terms is switching the type of test run we're doing (from foss to aio). Which we can't do in a run without some hacks. We would need to run the pre-suite as foss and then manually set the hosts' metadata about where to find puppet after the upgrade. There's going to be a number of other gotchas using our automated tooling (is the module going to be upgrading the master as well? the type of test run in beaker sets up a number of assumptions). Its certainly feasible, I don't know at this point, if it would be worthwhile however. Second set is for the pipeline itself, here's the normal questionnaire: Basically does this module adhere to the standard module team owned module pipelines, if not, how does it different? I've broken that down into specific questions below (defaults for the module team owned module pipelines are in parens). should it be lint tested (yes)? what are the versions of Ruby it supports (1.9.3 2.1.5?) what are the versions of Puppet is supports (3.x?) are there different axes that are important to spec testing (no)? what is the command to run the unit tests (bundle exec rake spec?) what are the platforms it supports at the acceptance level? (all PE supported Linices?) are there different axes that are important to acceptance testing beside platforms (like how AWS doesn't have platform dependent code but does vary based on IAM account type – default: no)? what is the command to run the acceptance tests (bundle exec rspec spec/acceptance)? does a pipeline that tests against a couple of FOSS platforms for rapid feedback and then against all PE platforms for final validation make sense (yes)?
Jira (PUP-4468) AIO Upgrade Module
Title: Message Title Josh Cooper commented on PUP-4468 Re: AIO Upgrade Module should it be lint tested (yes)? Yes what are the versions of Ruby it supports (1.9.3 2.1.5?) I believe FOSS 3.8 supports ruby 1.8.7, e.g. redhat 6 with system ruby. what are the versions of Puppet is supports (3.x?) We are only supporting upgrades from 3.8.0 to 4.y. There will be behavior differences when running on puppet 3.8 and = 4.0, though I don't think we need acceptance testing for that. are there different axes that are important to spec testing (no)? Not that I can think of. what is the command to run the unit tests (bundle exec rake spec?) what are the platforms it supports at the acceptance level? (all PE supported Linices?) Initially, I'd suggest starting with tier 1 open source platforms. Eventually this should also include PE supported platforms including Windows. are there different axes that are important to acceptance testing beside platforms (like how AWS doesn't have platform dependent code but does vary based on IAM account type – default: no)? Perhaps FOSS vs PE? what is the command to run the acceptance tests (bundle exec rspec spec/acceptance)? Why not rake? does a pipeline that tests against a couple of FOSS platforms for rapid feedback and then against all PE platforms for final validation make sense (yes)? maybe... we want to release the module in open source first, then add PE support later, so there might an initial FOSS based pipeline, with additional PE axis added later? will you be targeting existing PE 3.7 installations or is this only for PE 3.8 and above (yes, test against 3.7 and above)? Only 3.8 should it include testing against future parser and strict variables (enable Puppet 4 feature flags – default: yes)? Initially I was thinking no, since future parser is no longer a setting in puppet 4. But since the module needs to run on a 3.8 agent where future
Jira (PUP-4468) AIO Upgrade Module
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4468 AIO Upgrade Module Issue Type: Epic Assignee: Unassigned Created: 2015/04/27 10:43 PM Priority: Normal Reporter: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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.
