<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font color="#000000" face="Courier New,sans-serif">Masahito,</font><BR><font color="#000000" face="Courier New,sans-serif"></font> <BR><font color="#000000" face="Courier New,sans-serif">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. </font><BR><font color="#000000" face="Courier New,sans-serif"></font> <BR><font color="#000000" face="Courier New,sans-serif">It's clear to me that some will be deployment-specific.</font><BR><font color="#000000" face="Courier New,sans-serif"></font> <BR><font color="#000000" face="Courier New,sans-serif">But what I am asking is where is the spec for:</font><BR><font color="#000000" face="Courier New,sans-serif">- what congress.conf fields are supported i.e. defined for possible setting in a release</font><BR><font face="Courier New">- which fields are mandatory to be set (or Congress will simply not work)</font><BR><font color="#000000" face="Courier New,sans-serif">- which fields are not mandatory, but must be set for some specific purpose, which right now is unclear</font><BR><font face="Courier New"></font> <BR><font face="Courier New">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.</font><font color="#000000" face="Courier New,sans-serif"><br id="FontBreak"></font><br>Thanks,<br>Bryan Sullivan<br> <BR><div>> From: muroi.masahito@lab.ntt.co.jp<br>> Date: Fri, 27 May 2016 15:40:31 +0900<br>> To: openstack-dev@lists.openstack.org<br>> Subject: Re: [openstack-dev] [congress] Spec for congress.conf<br>> <br>> Hi Bryan,<br>> <br>> Oslo.config that Congress uses to manage config sets each fields to <br>> default value if you don't specify your configured values in <br>> congress.conf. In that meaning, all config is option/required.<br>> <br>> In my experience, config values differing from each deployment, like ip <br>> address and so on, have to be configured, but others might be configured <br>> when you want Congress to run with different behaviors.<br>> <br>> best regard,<br>> Masahito<br>> <br>> On 2016/05/27 3:36, SULLIVAN, BRYAN L wrote:<br>> > Hi Congress team,<br>> ><br>> ><br>> ><br>> > Quick question for anyone. Is there a spec for fields in congress.conf<br>> > file? As of Liberty this has to be tox-generated but I need to know<br>> > which conf values are required vs optional. The generated sample output<br>> > doesn't clarify that. This is for the Puppet Module and JuJu Charm I am<br>> > developing with the help of RedHat and Canonical in OPNFV. I should have<br>> > Congress installed by default (for the RDO and JuJu installers) in the<br>> > OPNFV Colorado release in the next couple of weeks, and the<br>> > congress.conf file settings are an open question. The Puppet module will<br>> > also be used to create a Fuel plugin for installation.<br>> ><br>> ><br>> ><br>> > Thanks,<br>> ><br>> > Bryan Sullivan | AT&T<br>> ><br>> ><br>> ><br>> ><br>> ><br>> > __________________________________________________________________________<br>> > OpenStack Development Mailing List (not for usage questions)<br>> > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>> ><br>> <br>> <br>> -- <br>> $B<<0f(B $B2m?N(B(Masahito MUROI)<br>> Software Innovation Center, NTT<br>> Tel: +81-422-59-4539<br>> <br>> <br>> <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></div> </div></body>
</html>