[openstack-dev] [congress] Spec for congress.conf
Bryan Sullivan
blsaws at hotmail.com
Fri May 27 17:52:57 UTC 2016
Masahito,
Sorry, I'm not quite clear on the guidance. Sounds like you're saying all options will be defaulted by Oslo.config if not set in the congress.conf file. That's OK, if I understood.
It's clear to me that some will be deployment-specific.
But what I am asking is where is the spec for:
- what congress.conf fields are supported i.e. defined for possible setting in a release
- which fields are mandatory to be set (or Congress will simply not work)
- which fields are not mandatory, but must be set for some specific purpose, which right now is unclear
I'm hoping the answer isn't "go look at the code"! That won't work for end-users, who are looking to use Congress but not decipher the meaning/importance of specific fields from the code.
Thanks,
Bryan Sullivan
> From: muroi.masahito at lab.ntt.co.jp
> Date: Fri, 27 May 2016 15:40:31 +0900
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [congress] Spec for congress.conf
>
> Hi Bryan,
>
> Oslo.config that Congress uses to manage config sets each fields to
> default value if you don't specify your configured values in
> congress.conf. In that meaning, all config is option/required.
>
> In my experience, config values differing from each deployment, like ip
> address and so on, have to be configured, but others might be configured
> when you want Congress to run with different behaviors.
>
> best regard,
> Masahito
>
> On 2016/05/27 3:36, SULLIVAN, BRYAN L wrote:
> > Hi Congress team,
> >
> >
> >
> > Quick question for anyone. Is there a spec for fields in congress.conf
> > file? As of Liberty this has to be tox-generated but I need to know
> > which conf values are required vs optional. The generated sample output
> > doesn't clarify that. This is for the Puppet Module and JuJu Charm I am
> > developing with the help of RedHat and Canonical in OPNFV. I should have
> > Congress installed by default (for the RDO and JuJu installers) in the
> > OPNFV Colorado release in the next couple of weeks, and the
> > congress.conf file settings are an open question. The Puppet module will
> > also be used to create a Fuel plugin for installation.
> >
> >
> >
> > Thanks,
> >
> > Bryan Sullivan | AT&T
> >
> >
> >
> >
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
> --
> 室井 雅仁(Masahito MUROI)
> Software Innovation Center, NTT
> Tel: +81-422-59-4539
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160527/4a69d8fd/attachment.html>
More information about the OpenStack-dev
mailing list