mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 06:46:26 +01:00
73 lines
5.7 KiB
Plaintext
73 lines
5.7 KiB
Plaintext
[id="installing-openstack-installer-sr-iov"]
|
|
= Installing a cluster on OpenStack that supports SR-IOV-connected compute machines
|
|
include::modules/common-attributes.adoc[]
|
|
:context: installing-openstack-installer-sr-iov
|
|
|
|
toc::[]
|
|
|
|
In {product-title} version {product-version}, you can install a cluster on {rh-openstack-first} that can use compute machines with single-root I/O virtualization (SR-IOV) technology.
|
|
|
|
== Prerequisites
|
|
|
|
* Review details about the
|
|
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
|
|
processes.
|
|
** Verify that {product-title} {product-version} is compatible with your {rh-openstack} version by using the "Supported platforms for OpenShift clusters" section. You can also compare platform support across different versions by viewing the link:https://access.redhat.com/articles/4679401[{product-title} on {rh-openstack} support matrix].
|
|
// Statement seems somewhat obsolete, though not sure about assembly placement.
|
|
* Verify that your network configuration does not rely on a provider network. Provider networks are not supported.
|
|
|
|
* Have a storage service installed in {rh-openstack}, like block storage (Cinder) or object storage (Swift). Object storage is the recommended storage technology for {product-title} registry cluster deployment. For more information, see xref:../../scalability_and_performance/optimizing-storage.adoc#optimizing-storage[Optimizing storage].
|
|
|
|
* Have metadata service enabled in {rh-openstack}
|
|
|
|
include::modules/installation-osp-default-deployment.adoc[leveloffset=+1]
|
|
include::modules/installation-osp-control-compute-machines.adoc[leveloffset=+2]
|
|
include::modules/installation-osp-bootstrap-machine.adoc[leveloffset=+2]
|
|
include::modules/cluster-entitlements.adoc[leveloffset=+1]
|
|
include::modules/installation-osp-enabling-swift.adoc[leveloffset=+1]
|
|
include::modules/installation-osp-verifying-external-network.adoc[leveloffset=+1]
|
|
include::modules/installation-osp-describing-cloud-parameters.adoc[leveloffset=+1]
|
|
include::modules/installation-obtaining-installer.adoc[leveloffset=+1]
|
|
include::modules/installation-initializing.adoc[leveloffset=+1]
|
|
include::modules/installation-configure-proxy.adoc[leveloffset=+2]
|
|
include::modules/installation-configuration-parameters.adoc[leveloffset=+1]
|
|
include::modules/installation-osp-custom-subnet.adoc[leveloffset=+2]
|
|
include::modules/installation-osp-deploying-bare-metal-machines.adoc[leveloffset=+2]
|
|
include::modules/installation-osp-config-yaml.adoc[leveloffset=+2]
|
|
include::modules/ssh-agent-using.adoc[leveloffset=+1]
|
|
include::modules/installation-osp-accessing-api.adoc[leveloffset=+1]
|
|
include::modules/installation-osp-accessing-api-floating.adoc[leveloffset=+2]
|
|
include::modules/installation-osp-accessing-api-no-floating.adoc[leveloffset=+2]
|
|
include::modules/installation-osp-configuring-sr-iov.adoc[leveloffset=+1]
|
|
include::modules/installation-launching-installer.adoc[leveloffset=+1]
|
|
include::modules/installation-osp-verifying-cluster-status.adoc[leveloffset=+1]
|
|
include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
|
|
The cluster is operational. Before you can add SR-IOV compute machines though, you must perform additional tasks.
|
|
|
|
include::modules/networking-osp-preparing-for-sr-iov.adoc[leveloffset=+1]
|
|
include::modules/networking-osp-enabling-metadata.adoc[leveloffset=+2]
|
|
include::modules/networking-osp-enabling-vfio-noiommu.adoc[leveloffset=+2]
|
|
|
|
//Tweak copied statement, but same gist as UPI. "Day 1 is done. Now, day 2."
|
|
The cluster is installed and prepared for SR-IOV configuration. Complete the post-installation SR-IOV tasks that are listed in the "Next steps" section.
|
|
|
|
include::modules/cluster-telemetry.adoc[leveloffset=+1]
|
|
|
|
.Additional resources
|
|
|
|
* See xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about the Telemetry service
|
|
|
|
== Next steps
|
|
|
|
* To complete SR-IOV configuration for your cluster:
|
|
** xref:../../scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.adoc#installing-the-performance-addon-operator_cnf-master[Install the Performance Addon Operator].
|
|
** xref:../../scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.adoc#what-huge-pages-do_huge-pages[Configure the Performance Addon Operator with huge pages support].
|
|
** xref:../../networking/hardware_networks/installing-sriov-operator.adoc#installing-sr-iov-operator_installing-sriov-operator[Install the SR-IOV Operator].
|
|
** xref:../../networking/hardware_networks/configuring-sriov-device.adoc#nw-sriov-networknodepolicy-object_configuring-sriov-device[Configure your SR-IOV network device].
|
|
** xref:../../machine_management/creating_machinesets/creating-machineset-osp.adoc#machineset-yaml-osp-sr-iov_creating-machineset-osp[Add an SR-IOV compute machine set].
|
|
* xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
|
|
* If necessary, you can
|
|
xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
|
|
* If you need to enable external access to node ports, xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport[configure ingress cluster traffic by using a node port].
|
|
* If you did not configure {rh-openstack} to accept application traffic over floating IP addresses, xref:../../post_installation_configuration/network-configuration.adoc#installation-osp-configuring-api-floating-ip_post-install-network-configuration[configure {rh-openstack} access with floating IP addresses].
|