After deploying your topology, you can add a compute node
system to your deployment. This does not apply to the Minimal topology.
Before you begin
Before you begin, ensure you completed the Deploying prerequisites steps
based on the type of your new compute node.
About this task
Use the following procedure to add a Linux Kernel-based
Virtual Machine (KVM) or QEMU, KVM for IBM z Systems®, PowerKVM or z/VM® compute
node to your deployment. To add another Hyper-V compute
node, see Installing and uninstalling the IBM Cloud Manager with OpenStack Hyper-V Agent.Note: This procedure
is only applicable for adding a new node. It is not meant for deploying
to an existing node in your topology.
Procedure
- Log in to the deployment system as the root user.
This
is the system where IBM Cloud
Manager with OpenStack was
installed.
- Create a node specific attribute file. This
step is only required when the new compute node requires different
attributes from those defined in the environment for the topology.
For more information on node specific attribute files, see the applicable Deploying a test or production cloud section for your compute node
type.
- Deploy the new compute node. Change the following in the
command below.
- node-fqdn: Set to the fully qualified domain
name of the node system. You can also set to the public IP address,
private IP address, or hostname.
- node-run-list: Set the node run
list to be the same as the run list for an existing compute node in
the topology. You can look in the topology JSON file to see the run
list for an existing compute node. For example, if the run list is "runlist":
["role[ibm-os-compute-node-kvm]","role[ibm-os-prs-compute-node]"],
then set node-run-list to 'role[ibm-os-compute-node-kvm],role[ibm-os-prs-compute-node]'.
- node-ssh-password: SSH root user password
for the node. To use an SSH identity file instead of a password, use
the -i node-ssh-identity option, where node-ssh-identity is
the SSH identity file for the node.
- node-attribute-file: Set to the node specific
attribute file created in step 2. Remove this option if not required.
- topology-file: Set to the fully
qualified path and file name of the topology JSON file used to deploy
the other nodes in the topology. The command updates the topology
file with the added compute node information.
knife os manage deploy node node-fqdn 'node-run-list' -P node-ssh-password --attribute-file node-attribute-file --topology-file topology-file
For
example, knife os manage deploy node hostname.my.company.com
'role[ibm-os-compute-node-kvm],role[ibm-os-prs-compute-node]' -P
passw0rd --attribute-file /root/clouds/hostname_attributes.json --topology-file
/root/clouds/my_topology.json
Note: For more
information on the
knife os manage deploy node command
and the topology file, see
Commands.
- After the deployment completes, you can check the status
of the IBM Cloud
Manager with OpenStack services,
see Checking status of OpenStack services.
Results
You are ready to start using IBM Cloud
Manager with OpenStack services on
the new compute node system.