On 21 August 2014 14:27, Jay Pipes <jaypi...@gmail.com> wrote: > Specifically for Triple-O, by making the Deployment program == Triple-O, the > TC has picked the disk-image-based deployment of an undercloud design as The > OpenStack Way of Deployment. And as I've said previously in this thread, I > believe that the deployment space is similarly unsettled, and that it would > be more appropriate to let the Chef cookbooks and Puppet modules currently > sitting in the stackforge/ code namespace live in the openstack/ code > namespace.
Totally agree with Jay here, I know people who gave up on trying to get any official project around deployment because they were told they had to do it under the TripleO umbrella _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
