이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 6. Deployment
Prerequisites
- You have configured the necessary settings to mitigate resource contention between colocated Compute and Ceph Storage services. For more information about how to mitigate resource contention, see Chapter 4, Configuring Resource Isolation on Hyper-Converged Nodes.
You are using a separate base environment file (or set of files) for all other Ceph settings. Both sections assume that you are using the same
/home/stack/templates/storage-config.yaml
file from Customizing the Storage Service and Sample Environment File: Creating a Ceph Cluster (both sections from Deploying an Overcloud with Containerized Red Hat Ceph).NoteThe same
/home/stack/templates/storage-config.yaml
environment file also defines how many nodes you are assigning to each role. For more information, see Assigning Nodes and Flavors to Roles.
-
During undercloud installation, you set
generate_service_certificate=false
in theundercloud.conf
file. Otherwise, you must inject a trust anchor when you deploy the overcloud, as described in Enabling SSL/TLS on Overcloud Public Endpoints in the Advanced Overcloud Customization guide.
Red Hat does not recommend enabling Instance HA by default for hyperconverged OpenStack deployments with Ceph (RHHI-C). It is possible to enable Instance HA with hyperconverged OpenStack deployments with Ceph provided that Red Hat reviews the configuration and that a support exception is filed. Please contact your Red Hat representative if you wish to use Instance HA with hyperconverged OpenStack deployments with Ceph.
To deploy your overcloud, run the following command:
Use the following list to understand what you include in the openstack overcloud deploy
command:
-
--templates - Creates the Overcloud from the default Heat template collection (namely,
/usr/share/openstack-tripleo-heat-templates/
). - -p /usr/share/openstack-tripleo-heat-templates/plan-samples/plan-environment-derived-params.yaml - Specifies that the derived parameters workflow should be run during the deployment to calculate how much memory and CPU should be reserved for a hyper-converged deployment.
-
-r /home/stack/templates/roles_data.yaml - Specifies the customized roles definition file from Chapter 3, Prepare Overcloud Role for Hyper-Converged Nodes, which includes the
ComputeHCI
role. -
-e /home/stack/templates/ports.yaml - Adds the environment file from Section 3.1, “Configuring Port Assignments for the ComputeHCI Role”, which configures the ports for the
ComputeHCI
role. - -e /home/stack/templates/environment-rhel-registration.yaml - Adds an environment file that registers overcloud nodes, as described in Registering the Overcloud with an Environment File (from Advanced Overcloud Customization).
- -e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-ansible.yaml - Adds the base environment file that deploys a containerized Red Hat Ceph cluster, with all default settings. See Deploying an Overcloud with Containerized Red Hat Ceph for more information.
-e /home/stack/templates/storage-config.yaml - Adds a custom environment file that defines all other Ceph settings. For a detailed example of this, see Sample Environment File: Creating a Ceph Cluster (from Deploying an Overcloud with Containerized Red Hat Ceph).
NoteIn Sample Environment File: Creating a Ceph Cluster (from Deploying an Overcloud with Containerized Red Hat Ceph), the
/home/stack/templates/storage-config.yaml
file is also used to specify what flavors and how many nodes to assign per role. See Assigning Nodes and Flavors to Roles for details.- /home/stack/templates/storage-container-config.yaml - Reserves CPU and Memory for each Ceph OSD storage container from Section 4.4, Reserving Memory and CPU Resources for Ceph.
- -e /home/stack/templates/network.yaml - Adds the environment file from Chapter 5, Finalize Networking Settings.
- -e /home/stack/templates/ceph-backfill-recovery.yaml - Adds the environment file from Section 4.2, “Reduce Ceph Backfill and Recovery Operations”.
- --ntp-server pool.ntp.org - Sets our NTP server.
Use the -e
flag to add environment files as needed for your planned overcloud deployment. For example, to also enable Single-Root Input/Output Virtualization (SR-IOV), add its corresponding environment file:
-e /usr/share/openstack-tripleo-heat-templates/environments/neutron-sriov.yaml
-e /usr/share/openstack-tripleo-heat-templates/environments/neutron-sriov.yaml
To apply your SR-IOV network preferences, add an environment file defining them:
-e /home/stack/templates/network-environment.yaml
-e /home/stack/templates/network-environment.yaml
Currently, SR-IOV is the only Network Function Virtualization (NFV) implementation supported with HCI. See SR-IOV Support for Virtual Networking (from the Networking Guide) for more details.
For a full list of deployment options, run:
openstack help overcloud deploy
$ openstack help overcloud deploy
For more information, see Creating the Overcloud with the CLI Tools (from Director Installation and Usage).
You can also use an answers file to specify which environment files to include in your deployment. See Including Environment Files in Overcloud Creation (from Director Installation and Usage) for more details.