Integrate the openshift-ansible Playbooks with TripleO by using the standard TripleO services (such as Heat and Mistral, etc.). Changes are required in TripleO to integrate the openshift-ansible Playbooks to deploy OCP from the Undercloud. The operator should be able to use TripleO/director to deploy only on BMs, without an Overcloud. This is the use case for "Multiple OCP clusters deployed on bare metal from the Undercloud". TripleO uses a standard Ironic and can be used to deploy the Overcloud image or any other compatible image on bare metal nodes registered with Ironic in the Undercloud. We should be able to deploy on nodes that are either a OpenShift role or no role at all, if that makes sense in TripleO (i.e. a composable role without services would be an example of a role to deploy OCP components on).
Several patches now landed to enable this, but https://review.openstack.org/#/c/494470/ is the main one I believe, so adding that to the external tracker.
Ok I've raised some follow-up bz's so we can decouple the initial integration (which is complete) from the additional tasks needed related to this work (some of which are still in progress): https://bugzilla.redhat.com/show_bug.cgi?id=1565999 - This is for scale operations to add new nodes https://bugzilla.redhat.com/show_bug.cgi?id=1591288 - node removal/replacement https://bugzilla.redhat.com/show_bug.cgi?id=1591291 - additional validations specific to OpenShift and multiple plan deployments https://bugzilla.redhat.com/show_bug.cgi?id=1591294 - plan management and configuration options when dealing with multiple plans/applications Thus I'll set this back to POST and we can make all those bz's depend on this one.
One more follow up is to enable HA deployments with multiple masters: https://bugzilla.redhat.com/show_bug.cgi?id=1595330
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/RHEA-2019:0045
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days