RDO deployment¶
Infrared allows to perform RDO based deployments.
To deploy RDO on virtual environment the following steps can be performed.
Provision virtual machines on a hypervisor with the virsh plugin. Use CentOS image:
infrared virsh -vv \ -o provision.yml \ --topology-nodes undercloud:1,controller:1,compute:1,ceph:1 \ --host-address my.host.redhat.com \ --host-key /path/to/host/key \ --image-url https://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2 \ -e override.controller.cpu=8 \ -e override.controller.memory=32768
Install the undercloud. Use RDO release name as a version:
infrared tripleo-undercloud -vv -o install.yml \ -o undercloud-install.yml \ --version pike
Build or import overcloud images from https://images.rdoproject.org:
# import images infrared tripleo-undercloud -vv \ -o undercloud-images.yml \ --images-task=import \ --images-url=https://images.rdoproject.org/pike/rdo_trunk/current-tripleo/stable/ # or build images infrared tripleo-undercloud -vv \ -o undercloud-images.yml \ --images-task=build \
Note
Overcloud image build process often takes more time than import.
Install RDO:
infrared tripleo-overcloud -v \ -o overcloud-install.yml \ --version pike \ --deployment-files virt \ --introspect yes \ --tagging yes \ --deploy yes infrared cloud-config -vv \ -o cloud-config.yml \ --deployment-files virt \ --tasks create_external_network,forward_overcloud_dashboard,network_time,tempest_deployer_input
To install containerized RDO version (pike and above) the
--registry-*
, --containers yes
and --registry-skip-puddle yes
parameters should be provided:
infrared tripleo-overcloud \
--version queens \
--deployment-files virt \
--introspect yes \
--tagging yes \
--deploy yes \
--containers yes \
--registry-mirror trunk.registry.rdoproject.org \
--registry-namespace master \
--registry-tag current-tripleo-rdo \
--registry-prefix=centos-binary- \
--registry-skip-puddle yes
infrared cloud-config -vv \
-o cloud-config.yml \
--deployment-files virt \
--tasks create_external_network,forward_overcloud_dashboard,network_time,tempest_deployer_input
Note
For the –registry-tag the following RDO tags can be used:
current-passed-ci
, current-tripleo
, current
, tripleo-ci-testing
, etc
Known issues¶
Overcloud deployment fails with the following message:
Error: /Stage[main]/Gnocchi::Db::Sync/Exec[gnocchi-db-sync]: Failed to call refresh: Command exceeded timeout Error: /Stage[main]/Gnocchi::Db::Sync/Exec[gnocchi-db-sync]: Command exceeded timeout
This error might be caused by the https://bugs.launchpad.net/tripleo/+bug/1695760. To workaround that issue the
--overcloud-templates disable-telemetry
flag should be added to the tripleo-overcloud command:infrared tripleo-overcloud -v \ -o overcloud-install.yml \ --version pike \ --deployment-files virt \ --introspect yes \ --tagging yes \ --deploy yes \ --overcloud-templates disable-telemetry infrared cloud-config -vv \ -o cloud-config.yml \ --deployment-files virt \ --tasks create_external_network,forward_overcloud_dashboard,network_time,tempest_deployer_input