Description of problem:
This is to allow installer to add a node to a compute group. This includes installing operating system, an extra libraries needed for ceph storage, all networks setup. (For the future extra Ceph keyring file if ceph is one of storage block back-ends for ephemeral storage and/or VM live migration).
For node deletion, VM migration is NOT part of this RFE. It is assumed that when a compute node is removed it does not have any user VMs or containers on it. But specifying in OSP installer that node is removed, or removed automatically after some administrator specified timeout, cleanup of OpenStack database, and OSP installer one are part of RFE.
For node replacement, Installer should provide a way to specify which node in compute cluster should be replaced, it could be down already, or still active.
But new node should attain identity of replaced node, including its network connections and its IP addresses. For this RFE assume that there no user VMs or containers on the node. (for the future we should add RFE for replacing that have user VMs or containers). Start with KVM hypervisor first.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
*** Bug 1123158 has been marked as a duplicate of this bug. ***
We need to treat adding and removing compute nodes as separate bugs because the work involved with each is different. This bug will track adding new compute nodes. It will be cloned to a different bug for removing.
Also, replacement == remove + add, so we don't need to track anything special for replacement.
I installed 1 controller, 1 neutron and 1 compute node with ceph as storage for glance and cinder.
the installation passed and ceph keyring files were deployed on the controller and compute.
I then add another compute node in the installer and click on the deploy button.
the deployment passed and ceph directory was installed on the new compute node.
I also verified that from horizon ui we can see both compute nodes.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.