[openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes
Walls, Jeffrey Joel (Cloud OS R&D)
jeff.walls at hp.com
Wed Jan 15 15:04:48 UTC 2014
> -----Original Message-----
> From: James Slagle [mailto:james.slagle at gmail.com]
> Sent: Wednesday, January 15, 2014 5:52 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management
> section - Wireframes
> This does not seem quite right to me. I don't think we want to be
> enabling or disabling different services in images at deployment time.
> That's one of the reasons that we have the element nature of
> diskimage-builder, so that you can build an image with the software
> components you want. Any service that you include in the image build
> is automatically enabled. If you want that image with a service
> disabled, you build a new image.
I don't necessarily disagree with this assertion, but what this could
lead to is a proliferation of a bunch of very similar images. Templatizing
some of the attributes (e.g., this package is enabled, that one isn't)
can reduce the potential explosion of images stored in glance. If that's
a concern, then it needs to be addressed. Note that this is true whether
tuskar does/helps with the image building or not.
More information about the OpenStack-dev