Re: [Openstack-operators] Generate list of default configuration parameters
On Wed, Sep 7, 2016 at 7:24 PM, Joseph Bajinwrote: > I'm not sure if this fits what you need, but the Kolla project produces a > lot of default values that are included in their deployments. You could > check that out and see if it works for you. > Joseph, I'll take a closer look at that, thank you. > >> I assuming with your mention of the the python-openstackclient and >> undercloud.conf that you are talking about TripleO in particular here. >> Unfortunately at this stage there is no such integration for what you >> request. If you are interested in all configuration options for >> undercloud.conf, you can see them in >> /usr/share/instack-undercloud/undercloud.conf.sample >> > I should have been more explicit in my initial question - yes, I was referring to python-tripleoclient, specifically, the values that the undercloud install would have used as a combination of program defaults and what was found in an undercloud.conf file. I am familiar with what undercloud.conf offers out of the box. I was hoping for an interface where I could query these values and use them programatically, something a little less messy than using awk sed grep etc. > >> It's worth noting that the functionality you describe by puppet and what >> is given in 'openstack configuration show' is slightly different as >> well. Puppet aims to print/provide all possible configuration options >> you might use in a server or agent configuration >> (/etc/puppet/puppet.conf) while 'openstack configuration show' provides >> high level overview of how the openstack cloud is configured including >> api versions, auth urls, etc. It hasn't got the ability to provide or >> interrogate specific components about all their potential configuration >> options for their config files (at least, this is my understanding, >> someone can correct me here). >> > Noted, thank you so much for clarifying. Thanks! -dant ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Generate list of default configuration parameters
I'm not sure if this fits what you need, but the Kolla project produces a lot of default values that are included in their deployments. You could check that out and see if it works for you. On Wed, Sep 7, 2016 at 6:51 PM, Graeme Gillieswrote: > On 08/09/16 05:41, Dan Trainor wrote: > > Hi - > > > > Back in the day when I was using Puppet, I found it particularly useful > > to "ask" Puppet for a list of configuration parameters[1] to extract > > information on default parameters. > > > > Does the 'openstack' command or any related command have a similar > > invocation? I am familiar with 'openstack configuration show' but the > > information I'm most interested in are defaults for values that would be > > populated in undercloud.conf - well before I could expect to use > > 'openstack configuration show'. > > > > Thanks! > > -dant > > > > --- > > > > [1] https://docs.puppet.com/puppet/latest/reference/config_print.html > > > > > > ___ > > OpenStack-operators mailing list > > OpenStack-operators@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > Hi Dan, > > I assuming with your mention of the the python-openstackclient and > undercloud.conf that you are talking about TripleO in particular here. > Unfortunately at this stage there is no such integration for what you > request. If you are interested in all configuration options for > undercloud.conf, you can see them in > /usr/share/instack-undercloud/undercloud.conf.sample > > It's worth noting that the functionality you describe by puppet and what > is given in 'openstack configuration show' is slightly different as > well. Puppet aims to print/provide all possible configuration options > you might use in a server or agent configuration > (/etc/puppet/puppet.conf) while 'openstack configuration show' provides > high level overview of how the openstack cloud is configured including > api versions, auth urls, etc. It hasn't got the ability to provide or > interrogate specific components about all their potential configuration > options for their config files (at least, this is my understanding, > someone can correct me here). > > Regards, > > Graeme > > -- > Graeme Gillies > Principal Systems Administrator > Openstack Infrastructure > Red Hat Australia > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Generate list of default configuration parameters
On 08/09/16 05:41, Dan Trainor wrote: > Hi - > > Back in the day when I was using Puppet, I found it particularly useful > to "ask" Puppet for a list of configuration parameters[1] to extract > information on default parameters. > > Does the 'openstack' command or any related command have a similar > invocation? I am familiar with 'openstack configuration show' but the > information I'm most interested in are defaults for values that would be > populated in undercloud.conf - well before I could expect to use > 'openstack configuration show'. > > Thanks! > -dant > > --- > > [1] https://docs.puppet.com/puppet/latest/reference/config_print.html > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > Hi Dan, I assuming with your mention of the the python-openstackclient and undercloud.conf that you are talking about TripleO in particular here. Unfortunately at this stage there is no such integration for what you request. If you are interested in all configuration options for undercloud.conf, you can see them in /usr/share/instack-undercloud/undercloud.conf.sample It's worth noting that the functionality you describe by puppet and what is given in 'openstack configuration show' is slightly different as well. Puppet aims to print/provide all possible configuration options you might use in a server or agent configuration (/etc/puppet/puppet.conf) while 'openstack configuration show' provides high level overview of how the openstack cloud is configured including api versions, auth urls, etc. It hasn't got the ability to provide or interrogate specific components about all their potential configuration options for their config files (at least, this is my understanding, someone can correct me here). Regards, Graeme -- Graeme Gillies Principal Systems Administrator Openstack Infrastructure Red Hat Australia ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators