Re: [openstack-dev] [oslo.config][kolla] modular backends for oslo.cfg
On Tue, Mar 24, 2015 at 11:40 AM, Flavio Percoco fla...@redhat.com wrote: This however won't remove the need of a config file. For instance, plugins like etcd's will need the host/port options to be set somewhere - or passed as a cli parameter. Yes totally! I have been using command line switches in my example and I think in a container like environement we would want to have it using automatically the environnement variables but those can be different behavior by different stevesdore drivers if we needed. Cheers, Chmouel __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo.config][kolla] modular backends for oslo.cfg
On 19/03/15 13:31 +0100, Chmouel Boudjnah wrote: Hello, While on a long oversea flight with Sebastien Han we were talking how he had implemented ceph-docker with central configuration over etcd. We quickly came up to the conclusion that if we wanted to have that in Kolla it would be neat if it was done straight from oslo.config so that would quickly override the default keys in a central point. There is multiple advantage to use that method not just for containers but as well to avoid issues when orchestrating an openstack deployment. I have heard arguments that this should be the job of an ansible/puppet/chef tool and while I completely agree I just don't think it has to write to files the tool would just write to the etcd database. I have quickly came up with a quick and dirty POC on oslo.cfg here : https://github.com/chmouel/oslo.config/commit/ 01ee54dd5219b1434eaac422055b58e77694d89f and the demo : https://gist.github.com/chmouel/05fb715f96344161268c What others thinks about it ? IIRC, we had a talk about this in the past but it didn't go anywhere. I personally like the idea and I believe it'd be useful for other deployments too. I believe if we wanted to do that we would have to add a stevesdor based modular backend support directly to oslo.cfg first and have an etcd backend implemented. +1 This however won't remove the need of a config file. For instance, plugins like etcd's will need the host/port options to be set somewhere - or passed as a cli parameter. Flavio Chmouel PS: I am using etcd here cause it's easy and fancy but this could be any backends like a DB/NoSQL/Swift or whatever if we wanted __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- @flaper87 Flavio Percoco pgpbIGYGJRFg_.pgp Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo.config][kolla] modular backends for oslo.cfg
And don't forget about: https://review.openstack.org/#/c/130047/ Sounds pretty similar (the proxy could proxy to anything, etc.d, zookeeper, a email system, a snail, a web-service, whatever...). -Josh Davanum Srinivas wrote: Chmouel, Nice! Ben added a topic Alternative file formats for oslo.config for Liberty[1]. this would be great if we can talk about alternative backends as well :) -- dims [1] https://etherpad.openstack.org/p/liberty-oslo-summit-planning On Thu, Mar 19, 2015 at 8:31 AM, Chmouel Boudjnahchmo...@chmouel.com wrote: Hello, While on a long oversea flight with Sebastien Han we were talking how he had implemented ceph-docker with central configuration over etcd. We quickly came up to the conclusion that if we wanted to have that in Kolla it would be neat if it was done straight from oslo.config so that would quickly override the default keys in a central point. There is multiple advantage to use that method not just for containers but as well to avoid issues when orchestrating an openstack deployment. I have heard arguments that this should be the job of an ansible/puppet/chef tool and while I completely agree I just don't think it has to write to files the tool would just write to the etcd database. I have quickly came up with a quick and dirty POC on oslo.cfg here : https://github.com/chmouel/oslo.config/commit/01ee54dd5219b1434eaac422055b58e77694d89f and the demo : https://gist.github.com/chmouel/05fb715f96344161268c What others thinks about it ? I believe if we wanted to do that we would have to add a stevesdor based modular backend support directly to oslo.cfg first and have an etcd backend implemented. Chmouel PS: I am using etcd here cause it's easy and fancy but this could be any backends like a DB/NoSQL/Swift or whatever if we wanted __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [oslo.config][kolla] modular backends for oslo.cfg
Chmouel, Nice! Ben added a topic Alternative file formats for oslo.config for Liberty[1]. this would be great if we can talk about alternative backends as well :) -- dims [1] https://etherpad.openstack.org/p/liberty-oslo-summit-planning On Thu, Mar 19, 2015 at 8:31 AM, Chmouel Boudjnah chmo...@chmouel.com wrote: Hello, While on a long oversea flight with Sebastien Han we were talking how he had implemented ceph-docker with central configuration over etcd. We quickly came up to the conclusion that if we wanted to have that in Kolla it would be neat if it was done straight from oslo.config so that would quickly override the default keys in a central point. There is multiple advantage to use that method not just for containers but as well to avoid issues when orchestrating an openstack deployment. I have heard arguments that this should be the job of an ansible/puppet/chef tool and while I completely agree I just don't think it has to write to files the tool would just write to the etcd database. I have quickly came up with a quick and dirty POC on oslo.cfg here : https://github.com/chmouel/oslo.config/commit/01ee54dd5219b1434eaac422055b58e77694d89f and the demo : https://gist.github.com/chmouel/05fb715f96344161268c What others thinks about it ? I believe if we wanted to do that we would have to add a stevesdor based modular backend support directly to oslo.cfg first and have an etcd backend implemented. Chmouel PS: I am using etcd here cause it's easy and fancy but this could be any backends like a DB/NoSQL/Swift or whatever if we wanted __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
