{"id":37,"date":"2018-09-06T06:14:18","date_gmt":"2018-09-06T06:14:18","guid":{"rendered":"http:\/\/virtorbis.virtcompute.com\/?p=37"},"modified":"2018-09-06T06:30:15","modified_gmt":"2018-09-06T06:30:15","slug":"openstack-compute-and-ceph-scale-out-with-composable-roles","status":"publish","type":"post","link":"https:\/\/virtorbis.virtcompute.com\/?p=37","title":{"rendered":"OpenStack Compute and Ceph scale out with Composable roles"},"content":{"rendered":"

Below steps describe the configurations required to perform scale out for compute and ceph nodes in an existing OpenStack deployment.<\/p>\n

Environment:<\/p>\n

Platform: Red Hat OpenStack 10<\/strong><\/p>\n

Compute: SRIOV nodes<\/strong><\/p>\n

Scale out: One SRIOV Compute node , and 3 Additional Ceph Nodes (the scale out nodes will have a new hardware profile, and hence a new role is assigned to each)<\/strong><\/p>\n

For composable roles, we need to have roles defined for each role in the roles_data file:<\/p>\n

file: overcloud-roles_data.yaml<\/p>\n

Role data for new SRIOV compute node:<\/p>\n

\"\"<\/a><\/p>\n

Role data for the existing and new Ceph nodes:<\/p>\n

\"\"<\/a><\/p>\n

Additional IP’s of the new nodes into IP from all pools file:<\/p>\n

\"\"<\/a><\/p>\n

Entries for network isolation file:<\/p>\n

\"\"<\/a><\/p>\n

Storage environment yaml should be updated with the new ceph node under extra configs of the respective role:<\/p>\n

\"\"<\/a><\/p>\n

As the hardware profile of the new SRIOV nodes are different, the required entries need to be updated in the Network environment file under the new nodes extra config section:<\/p>\n

\"\"<\/a><\/p>\n

As the new computes and ceph nodes are with new hardware profile, each of the nodes are required to be updated with a new nic-configs:<\/p>\n

Compute nic-config used in this deployment:<\/p>\n

\"\"<\/a><\/p>\n

As the SRIOV nodes require CPU core isolation and huge page setup, first boot configuration file needs to be updated with new node details:<\/p>\n

\"\"<\/a><\/p>\n

add the new nodes in to scheduler hints for predictive hostname and profile assignments:<\/p>\n

\"\"<\/a><\/p>\n

The hostnames and profile can be assigned to the nodes while importing the nodes using instackenv.json<\/p>\n

\"\"<\/a><\/p>\n

Once imported, you can good to update the overcloud.<\/p>\n

**Note:<\/p>\n

During the overcloud update, if the process is aborted manually or with the timeout settings, observed that the heat resource of the new roles are stuck in error state. If try to re-deploy with the same role names, the update does not go through. As a work around if you change the role names of the new nodes, update all the template files with new role and redeploy, this will start a new heat resource and deployment completes as expected. Once update is successful, all the resource in error state are cleaned\u00a0 from undercloud.<\/p>\n","protected":false},"excerpt":{"rendered":"

Below steps describe the configurations required to perform scale out for compute and ceph nodes in an existing OpenStack deployment. Environment: Platform: Red Hat OpenStack 10 Compute: SRIOV nodes Scale out: One SRIOV Compute node , and 3 Additional Ceph Nodes (the scale out nodes will have a new hardware profile, and hence a new […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,3,2,4,23,21],"tags":[29,24,28,25,26,27,30],"class_list":["post-37","post","type-post","status-publish","format-standard","hentry","category-ceph","category-cloud","category-linux","category-openstack","category-red-hat-openstack","category-scaleout","tag-ceph","tag-openstack","tag-osp","tag-red-hat-openstack","tag-rhosp","tag-scaleout","tag-sriov"],"_links":{"self":[{"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=\/wp\/v2\/posts\/37","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=37"}],"version-history":[{"count":5,"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=\/wp\/v2\/posts\/37\/revisions"}],"predecessor-version":[{"id":52,"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=\/wp\/v2\/posts\/37\/revisions\/52"}],"wp:attachment":[{"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=37"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=37"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtorbis.virtcompute.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=37"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}