Sure thing, I can handle rabbitmq and keystone tonight. The keystone one I wrote during the mid-cycle so I will just throw it in a patch.
Sam Yaple On Tue, Aug 11, 2015 at 10:54 AM, Steven Dake (stdake) <std...@cisco.com> wrote: > Hi, > > Alicja has been heading up this blueprint: > https://blueprints.launchpad.net/kolla/+spec/dockerfile-template > > Other projects like TripleO and downstreams depend on this change to > happen as soon as possible. It is a mountain of work – too much for one > person to finish in a sprint. I’d like to distribute the load to all our > developers, so everyone understands how the templates work and how to make > them for new containers. After we have good confidence in the new > container set, we will delete the docker directory as it exists today. > > The work is being coordinated by Alicja here: > https://etherpad.openstack.org/p/kolla-dockerfile-template > > Please expand the etherpad with the various containers we have for the > various services. Then assign yourself 3 or more :) I’d estimate we have > about 50 containers or more, so if folks can pick up 4 or 5 it would be > ideal. Before beginning work I’d like to see a reference implementation of > an infra container and a basic service container from either Alicja or Sam > or a combination of both so we can copy the same style throughout the code > base. If you pick a service with multiple containers, try to do the whole > thing. If you already have experience with the containers in that area > (for example Ryan with Cinder) it might be ideal to pick that container. I > picked the Heat containers for example because I have experience with them. > > Keep in mind we have a different blueprint to implement RHEL support in > containers, and I’d really REALLY like to see that land for liberty-3, > which means we can’t have this work land at the end of l3 and expect RHEL > support to land in 1 day :) > > Lets pick rabbitmq and keystone as our reference containers. Sam or > Alicja please crank out some ref implementations of these as soon as > possible (top priority) since everyone is blocked on that work. > > Regards, > -steve > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev