Red Hat Bugzilla – Bug 1473342
Provide a single environment file to deploy OVN services, instead of HA and non-HA
Last modified: 2018-06-15 21:45:27 EDT
Description of problem:
Presently, there are 2 environment files to enable OVN services - one for HA and for non-HA. Squash it into one environment file and deploy pacemaker OVN DB resources if pacemaker is enabled, else base profile.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
It seems like a nice-to-have. Lowering severity.
@Emilien - I would like to get your comments if this is possible to do it in t-h-t ?
Presently to deploy OVN baremetal configuration we have environmentns/neutron-ml2-ovn.yaml and environments/neutron-ml2-ovn-ha.yaml. Is it possible to have one template which would detect if pacemaker is enabled and enable OVN DB HA ?
I am not sure if it is possible.
So we discussed at the PTG and we agreed to:
- remove files that we don't support, which means, deployments without HA and without containers.
- only keep an environment with OVN / HA / Docker.
- document in a release note.
It doesn't make sense to maintain other files, as we don't support these architectures.