Add a compute node¶
How to add a compute node with bootstrap-servers, pull and deploy, each with --limit on the new host, and what
deploy --limit then touches: it creates the containers of the new compute, delegates tasks to the controllers, gathers
facts for all hosts, and does not touch existing computes apart from the delegated setup. The page gives no
verification steps for the new compute.
The scenario section is written for the assumed deployment, with compute004 as the new
host.
Warning
Existing hosts' /etc/hosts is not updated (bootstrap-servers --limit), and a full bootstrap-servers run carries
its own Docker-restart risk (R14) — see the caveats in §2.
1. Commands¶
1.1 Add a compute node¶
kolla-ansible -i multinode bootstrap-servers --limit compute501
kolla-ansible -i multinode pull --limit compute501
kolla-ansible -i multinode deploy --limit compute501
Details in §2.
- Facts for all hosts are still gathered, sequentially from
compute501(gather-facts.yml:29-50; loop items run one after another, ansible 2.9.27lib/ansible/executor/task_executor.py:317-367). Enable fact caching for large inventories. - Discovery runs from the first compute of the batch, delegated to
nova-conductor[0]. That host is outside the limit, butdelegate_toworks: Ansible looks the delegated host up in the whole inventory CODE (ansible 2.9.27lib/ansible/vars/manager.py:569-594,lib/ansible/inventory/manager.py:189-190). /etc/hostson existing hosts is not updated with the new compute (bootstrap-serverswas limited). Live migration withlibvirt_tls(hostname-based) and RabbitMQ name resolution may need a fullbootstrap-serversrun later (fact sheet E §3).
2. Add a compute node¶
CODE deploy --limit compute004 (after bootstrap-servers --limit and pull --limit), read from the plays and
task files:
- On compute004: 11 containers created, one per
compare_containeritem of a compute (Compute scaling §2). The number of task results is NOT AVAILABLE. - Elsewhere (via
delegate_to):- a Neutron bootstrap (DB sync) container on
control01(roles/neutron/tasks/bootstrap_service.yml:19-22); nova-manage cell_v2 list_cellsanddiscover_hostsoncontrol01(roles/nova-cell/tasks/discover_computes.yml:4-21,get_cell_settings.yml:2-20);- a Keystone API call to wait for compute registration (
roles/nova-cell/tasks/wait_discover_computes.yml:8-42).
- a Neutron bootstrap (DB sync) container on
- Facts: gathered for all 12 hosts. The new compute itself runs the delegated
setuploop sequentially (gather-facts.yml:29-50). - Not touched: existing computes, apart from the delegated
setupabove. Controllers get no config writes or restarts, only delegated tasks: those listed above, the fact gathering above (setupon all three controllers), and the Neutron DB and DB-user tasks (mysql_db,mysql_userrun throughkolla_toolbox) oncontrol01. - Caveats:
- Existing hosts'
/etc/hostsis not updated (bootstrap-servers --limit). - With
libvirt_tls: true(hostname-based migration), the other computes'/etc/hostslacks the new host until a fullbootstrap-serversrun, which carries its own Docker-restart risk (R14). NOT AVAILABLE Whether live migration to it fails meanwhile (fact sheet E §3).
- Existing hosts'
Related¶
- Risk register — R14 (
bootstrap-serversre-run on a live host), which this page names, and R23 (any run with--limiton a large inventory) - Nova — service cards of the roles
novaandnova-cell, and where to look - Pre-execution checklist — the checks before every production run
- Compute scaling
§2 — work per
compute host, read from the task files: the 11
compare_containeritems of a compute - Execution flow §2.4 — compute node deployment: what one compute host experiences
- Fact sheet E §3 —
/etc/hostsgeneration - Reconfigure Nova §6 — the checks listed after a Nova
run (
openstack compute service list,nova-manage cell_v2 list_hosts); this page lists none