[openstack-dev] [deployment][tripleo] Next steps for configuration management in TripleO (and other tools?)

Flavio Percoco flavio at redhat.com
Thu Mar 23 14:16:03 UTC 2017

On 17/03/17 10:09 -0400, Emilien Macchi wrote:
>[adding deployment tag because it might be interesting for other tools
>since it would engage cross-project work]
>If you're not working on TripleO, feel free to comment on how your
>team plans to solve the problem (or don't), so we can maybe discuss
>and work together.
>Things are moving in OpenStack deployment tools and we're working on
>solving common challenges in a consistent way. We had different topics
>and threads about key/value store for configuration management, and
>I've been thinking how it could fit with TripleO roadmap:
>Feel free to bring any feedback in this thread or even better in the etherpad.


Sorry for the delay but: PTO + PTO-backlog!

I actually like the proposal as I also mentioned in the more general thread.
Before we do anything on the tripleo side, I think we should work with the rest
of the openstack community on the common solution, which seems to be leading to

As far as the containers effort goes, this move (assuming etcd is the chosen
technology) would work just fine. I don't think this would be useful or even
consumed during the first phase of the containerized overcloud, which uses
docker daemon.


Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 862 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170323/500edd72/attachment.pgp>

More information about the OpenStack-dev mailing list