Mutually exclusive services should be decided based on the used
environment files rather than by the list of the services on a role.
For example, ComputeSriov role can be deployed with ml2-ovs or ml2-odl
or ml2-ovn based on the environment file used for the deploy command.
Looking forward.
Regards
Hi All
As per the discussion at PTG, I have filed a BP [1]. I will push a spec
sometime around mid-October.
[1].
https://blueprints.launchpad.net/tripleo/+spec/automatic-role-generation
On Tue, Sep 4, 2018 at 2:56 PM Steven Hardy wrote:
> On Tue, Sep 4, 2018 at 9:48 AM, Jiří Stránský wrote:
>
On Tue, Sep 4, 2018 at 9:48 AM, Jiří Stránský wrote:
> On 4.9.2018 08:13, Janki Chhatbar wrote:
>>
>> Hi
>>
>> I am looking to automate role file generation in TripleO. The idea is
>> basically for an operator to create a simple yaml file (operator.yaml,
>> say)
>> listing services that are needed
On 4.9.2018 08:13, Janki Chhatbar wrote:
Hi
I am looking to automate role file generation in TripleO. The idea is
basically for an operator to create a simple yaml file (operator.yaml, say)
listing services that are needed and then TripleO to generate
Controller.yaml enabling only those services
Hi
I am looking to automate role file generation in TripleO. The idea is
basically for an operator to create a simple yaml file (operator.yaml, say)
listing services that are needed and then TripleO to generate
Controller.yaml enabling only those services that are mentioned.
For example:
operator
