nfig has the purpose of each config fields.
>>
>> If you expect the spec means documents like [1], unfortunately Congress
>> doesn't have these kind of document now.
>>
>> [1] http://docs.openstack.org/mitaka/config-reference/
>>
>> best regards,
>> Masa
ack.org/mitaka/config-reference/
>
> best regards,
> Masahito
>
> >
> > Thanks,
> > Bryan Sullivan
> >
> >> From: muroi.masah...@lab.ntt.co.jp
> >> Date: Fri, 27 May 2016 15:40:31 +0900
> >> To: openstack-dev@lists.openstack.org
&g
ly Congress
doesn't have these kind of document now.
[1] http://docs.openstack.org/mitaka/config-reference/
best regards,
Masahito
Thanks,
Bryan Sullivan
From: muroi.masah...@lab.ntt.co.jp
Date: Fri, 27 May 2016 15:40:31 +0900
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-
; To: openstack-dev@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 tha
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
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
