Contrail 5.0.1GA: workflow to delete a compute from an existing cluster
Bug #1788447 reported by
Luke Bockelmann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
In Progress
|
Critical
|
Nitish Krishna Kaveri | |||
Trunk |
Fix Committed
|
Critical
|
Nitish Krishna Kaveri |
Bug Description
This URL describes a procedure to add a compute: https:/
Today we don't have a GA procedure for it. Until we have a coded workflow, we have to use config APIs to delete.
Shivayogi knows these API's but we need a workflow.
This would account for any misconfigurations of a compute that needs to be fixed during the deployment.
tags: | added: ansible provisioning releaseblocker |
tags: | added: csg vmware |
tags: |
added: vcenter-only removed: vmware |
information type: | Proprietary → Public |
To post a comment you must log in.
In older release we used fab in which we had detach_vrouter task.
Detatach_vrouter does the following, vrouter. py with --del option and the IP details of the compute/api-server /github. com/Juniper/ contrail- fabric- utils/blob/ master/ fabfile/ tasks/misc. py#L47
1. Stops Nova compute
2. Stops supervisor-vrouter
3. Exeecutes provision_
Reference: https:/