Remove UPI support statement from ShiftStack compact docs

Fixes OSDOCS-12124

installing/installing_openstack/installing-openstack-three-node.adoc

@@ -8,10 +8,9 @@ toc::[]
 
 In {product-title} version {product-version}, you can install a three-node cluster on {rh-openstack-first}. A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production.
 
-You can install a three-node cluster by using either installer-provisioned or user-provisioned infrastructure.
+You can install a three-node cluster on installer-provisioned infrastructure only.
 
 include::modules/installation-three-node-cluster-cloud-provider.adoc[leveloffset=+1]
 
 == Next steps
-* xref:../../installing/installing_openstack/installing-openstack-installer-custom.adoc#installing-openstack-installer-custom[Installing a cluster on OpenStack with customizations]
-* xref:../../installing/installing_openstack/installing-openstack-user.adoc#installing-openstack-user[Installing a cluster on OpenStack on your own infrastructure]
+* xref:../../installing/installing_openstack/installing-openstack-installer-custom.adoc#installing-openstack-installer-custom[Installing a cluster on OpenStack with customizations]

modules/installation-three-node-cluster-cloud-provider.adoc

@@ -19,6 +19,9 @@ endif::[]
 ifeval::["{context}" == "installing-nutanix-three-node"]
 :nutanix:
 endif::[]
+ifeval::["{context}" == "installing-openstack-three-node"]
+:openstack:
+endif::[]
 
 :_mod-docs-content-type: PROCEDURE
 [id="installation-three-node-cluster_{context}"]
@@ -37,13 +40,13 @@ Because application workloads run from control plane nodes, additional subscript
 
 .Procedure
 
-ifdef::nutanix[]
+ifdef::nutanix,openstack[]
 * Set the number of compute replicas to `0` in your `install-config.yaml` file, as shown in the following `compute` stanza:
-endif::nutanix[]
+endif::nutanix,openstack[]
 
-ifndef::nutanix[]
+ifndef::nutanix,openstack[]
 . Set the number of compute replicas to `0` in your `install-config.yaml` file, as shown in the following `compute` stanza:
-endif::nutanix[]
+endif::nutanix,openstack[]
 +
 .Example `install-config.yaml` file for a three-node cluster
 [source,yaml]
@@ -56,7 +59,7 @@ compute:
   replicas: 0
 # ...
 ----
-ifndef::vsphere,nutanix[]
+ifndef::vsphere,nutanix,openstack[]
 . If you are deploying a cluster with user-provisioned infrastructure:
 ** After you create the Kubernetes manifest files, make sure that the `spec.mastersSchedulable` parameter is set to `true` in `cluster-scheduler-02-config.yml` file. You can locate this file in `<installation_directory>/manifests`.
 ifdef::aws[]
@@ -69,7 +72,7 @@ ifdef::gcp[]
 For more information, see "Creating the Kubernetes manifest and Ignition config files" in "Installing a cluster on user-provisioned infrastructure in GCP by using Deployment Manager templates".
 endif::gcp[]
 ** Do not create additional worker nodes.
-endif::vsphere,nutanix[]
+endif::vsphere,nutanix,openstack[]
 
 ifdef::vsphere[]
 . If you are deploying a cluster with user-provisioned infrastructure:
@@ -81,7 +84,7 @@ endif::vsphere[]
 ** Do not create additional worker nodes.
 endif::vsphere[]
 
-ifndef::nutanix[]
+ifndef::nutanix,openstack[]
 .Example `cluster-scheduler-02-config.yml` file for a three-node cluster
 [source,yaml]
 ----
@@ -96,7 +99,7 @@ spec:
     name: ""
 status: {}
 ----
-endif::nutanix[]
+endif::nutanix,openstack[]
 
 ifeval::["{context}" == "installing-aws-three-node"]
 :!aws:
@@ -113,3 +116,6 @@ endif::[]
 ifeval::["{context}" == "installing-nutanix-three-node"]
 :!nutanix:
 endif::[]
+ifeval::["{context}" == "installing-openstack-three-node"]
+:!openstack:
+endif::[]