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.

Hey,

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:
https://etherpad.openstack.org/p/tripleo-etcd-transition

Feel free to bring any feedback in this thread or even better in the etherpad.

Hey,

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
etcd.

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

--
@flaper87
Flavio Percoco

Attachment: signature.asc
Description: PGP signature

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to