"Aaron Greengrass" <aa...@greenbtn.com> writes: > ... > 6. continued refactoring of all modules until: > they can be used in any environmentthey can be used in puppet 2.7 or > 3.x interchangeablythey don't implicitly include more than is > required.
Thanks for this! I think that all sounds great. Regarding the last item, once the modules are fully generic, they should be moved to individual repos and put on puppetforge. We have a few like this, but not many. > Please note, these items are wide, sweeping changes, and as such I'm > expecting we would want to tackle them in small, safe steps (ie get > the framework in place and inert, then test changes on sandboxed > machines, then gradually roll out to production). You should be able to test them locally, at least enough that we would be as satisfied as we could be that they should work in production. However, before we land these sweeping changes, first we need to have puppetboard or something similar running. The design of this system is not only that anyone should be able to propose changes, but also that they can monitor the effects of those changes. I'm looking forward to the work you have proposed, but I want to make sure that, like any other project, you can follow through on the whole process and you aren't blocked by infra-root having to check to see if production systems are broken. So in short, I'd like to hold off on approving puppet refactor changes until we have puppetboard up and running. -Jim _______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
