On 22 March 2016 at 09:15, Thierry Carrez <[email protected]> wrote:
> > For OSA, we don't produce the deployment tool, only a set of playbooks. I > was thinking we might need a type:packaging tag to describe which things we > produce are just about packaging OpenStack things for usage by outside > deployment systems (Ansible, Puppet, Chef, Deb, RPM...). So I'm not sure > your type:deployment tag would apply to OSA. > Yeah, I suppose it depends on how you define 'deployment tool'. OSA is an umbrella project providing Ansible roles which deploy services, and playbooks that put them together in an integrated deployment. Fuel similarly has libraries, Puppet roles, plugins, etc which are all packaged together to provide what we call 'Fuel'. I expect that there are other similarities - for instance 'Keystone' may be a service, but that service has libraries and all combined together we call it a daemon service. I guess it would be nice to have some sort of designation to allow easier filtering for consumers, assuming that this actually does add value to Operators/Packagers who consume these projects.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
