Red Hat Bugzilla – Bug 1473342
Provide a single environment file to deploy OVN services, instead of HA and non-HA
Last modified: 2018-08-29 12:35:50 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): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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.
Per comment 7 it looks like the next step is to remove the non-HA environment file. What do you think?
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
Fixed in : OPS13 puddle 2018-08-08.2 openstack-tripleo-heat-templates-8.0.4-16.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2574