[openstack-dev] [openstack-ansible][kolla-ansible][tripleo] ansible roles: where they live and what do they do

Doug Hellmann doug at doughellmann.com
Thu Aug 9 20:56:27 UTC 2018


Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600:
> Ahoy folks,
> 
> I think it's time we come up with some basic rules/patterns on where
> code lands when it comes to OpenStack related Ansible roles and as we
> convert/export things. There was a recent proposal to create an
> ansible-role-tempest[0] that would take what we use in
> tripleo-quickstart-extras[1] and separate it for re-usability by
> others.   So it was asked if we could work with the openstack-ansible
> team and leverage the existing openstack-ansible-os_tempest[2].  It
> turns out we have a few more already existing roles laying around as
> well[3][4].
> 
> What I would like to propose is that we as a community come together
> to agree on specific patterns so that we can leverage the same roles
> for some of the core configuration/deployment functionality while
> still allowing for specific project specific customization.  What I've
> noticed between all the project is that we have a few specific core
> pieces of functionality that needs to be handled (or skipped as it may
> be) for each service being deployed.
> 
> 1) software installation
> 2) configuration management
> 3) service management
> 4) misc service actions
> 
> Depending on which flavor of the deployment you're using, the content
> of each of these may be different.  Just about the only thing that is
> shared between them all would be the configuration management part.

Does that make the 4 things separate roles, then? Isn't the role
usually the unit of sharing between playbooks?

Doug



More information about the OpenStack-dev mailing list