<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I agree with Doug’s question, but also would extend the train of thought to ask why not help to make Chef or Puppet better and cover the more OpenStack use-cases rather than add yet another competing system?</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Cheers,</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Morgan</div><p style="color:#A0A0A8;">On January 9, 2014 at 10:24:06, Doug Hellmann (<a href="mailto://doug.hellmann@dreamhost.com">doug.hellmann@dreamhost.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div>
<title></title>
<div dir="ltr">
<div class="gmail_default" style="font-size:small">What
capabilities would this new service give us that existing, proven,
configuration management tools like chef and puppet don't
have?</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Jan 9, 2014 at 12:52 PM, Nachi
Ueno <span dir="ltr"><<a href="mailto:nachi@ntti3.com" target="_blank">nachi@ntti3.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Flavio<br>
<br>
Thank you for your input.<br>
I agree with you. oslo.config isn't right place to have server side
code.<br>
<br>
How about oslo.configserver ?<br>
For authentication, we can reuse keystone auth and oslo.rpc.<br>
<br>
Best<br>
Nachi<br>
<br>
<br>
2014/1/9 Flavio Percoco <<a href="mailto:flavio@redhat.com">flavio@redhat.com</a>>:<br>
<div class="HOEnZb">
<div class="h5">> On 08/01/14 17:13 -0800, Nachi Ueno
wrote:<br>
>><br>
>> Hi folks<br>
>><br>
>> OpenStack process tend to have many config options, and
many hosts.<br>
>> It is a pain to manage this tons of config options.<br>
>> To centralize this management helps operation.<br>
>><br>
>> We can use chef or puppet kind of tools, however<br>
>> sometimes each process depends on the other processes
configuration.<br>
>> For example, nova depends on neutron configuration
etc<br>
>><br>
>> My idea is to have config server in oslo.config, and let
cfg.CONF get<br>
>> config from the server.<br>
>> This way has several benefits.<br>
>><br>
>> - We can get centralized management without modification
on each<br>
>> projects ( nova, neutron, etc)<br>
>> - We can provide horizon for configuration<br>
>><br>
>> This is bp for this proposal.<br>
>> <a href="https://blueprints.launchpad.net/oslo/+spec/oslo-config-centralized" target="_blank">https://blueprints.launchpad.net/oslo/+spec/oslo-config-centralized</a><br>
>><br>
>> I'm very appreciate any comments on this.<br>
><br>
><br>
><br>
> I've thought about this as well. I like the overall idea of
having a<br>
> config server. However, I don't like the idea of having it
within<br>
> oslo.config. I'd prefer oslo.config to remain a library.<br>
><br>
> Also, I think it would be more complex than just having a
server that<br>
> provides the configs. It'll need authentication like all
other<br>
> services in OpenStack and perhaps even support of
encryption.<br>
><br>
> I like the idea of a config registry but as mentioned above,
IMHO it's<br>
> to live under its own project.<br>
><br>
> That's all I've got for now,<br>
> FF<br>
><br>
> --<br>
> @flaper87<br>
> Flavio Percoco<br>
><br></div>
</div>
<div class="HOEnZb">
<div class="h5">>
_______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br></div>
</div>
_______________________________________________
<br>OpenStack-dev mailing list
<br>OpenStack-dev@lists.openstack.org
<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<br></div></div></span></blockquote></body></html>