New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[VMware] Enable unmanaging guest VMs #4103
Conversation
@blueorangutan package |
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✖centos7 ✖debian. JID-1244 |
@blueorangutan package |
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✔centos7 ✔debian. JID-1247 |
@blueorangutan test centos7 vmware-67u3 |
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
Trillian test result (tid-1577)
|
4554b98
to
91ab3f2
Compare
@blueorangutan package |
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✔centos7 ✔debian. JID-1264 |
@blueorangutan test centos7 vmware-67u3 |
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
Trillian test result (tid-1600)
|
@nvazquez to avoid confusion, can you add either [WIP] in the PR title or open the PR as a draft? Thanks. |
a7582d6
to
a0c88ae
Compare
@blueorangutan package |
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✔centos7 ✔debian. JID-1316 |
@blueorangutan test centos7 vmware-67u3 |
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✔centos7 ✔debian. JID-1400 |
@blueorangutan test centos7 vmware-67u3 |
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
Trillian test result (tid-1743)
|
@blueorangutan test centos7 vmware-67u3 |
This one needs to be tested explicitly (besides the internal tests we've done so far) |
@blueorangutan package |
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✔centos7 ✔debian. JID-1411 |
@blueorangutan package |
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Packaging result: ✔centos7 ✔debian. JID-1439 |
@blueorangutan test |
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Trillian test result (tid-1826)
|
@andrijapanicsb @borisstoyanov @rhtyd tests are looking good, are you ok to merge this one? |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andrijapanicsb I've tested, LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT
(I've tested the internal branch, based on 4.11 - and everything looks good)
UI changes for apache/cloudstack#4103 Co-authored-by: Rohit Yadav <rohit.yadav@shapeblue.com>
UI changes for #4103 Co-authored-by: Rohit Yadav <rohit.yadav@shapeblue.com> Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
Description
This feature allows administrators to unmanage guest virtual machines from CloudStack. Once unmanaged, CloudStack can no longer monitor, control or administer the provisioning and orchestration related operations on a virtual machine.
A new API method has been added:
unmanageVirtualMachine
, accepting the virtual machine UUID as parameter The execution of this API method performs the unmanaging of a guest virtual machine. It has the following pre-conditions:Assuming these pre-conditions are met, the API execution will perform the following pre-checks, failing if they are not met:
An additional check is performed prior to unmanaging the virtual machine from CloudStack: the hypervisor returns checks that the virtual machine exists, searching the virtual machine by its instance name. If it is not found, then the operation fails.
Global setting
A new boolean zone setting has been added:
unmanage.vm.preserve.nics
, with default value = ‘false’. If set to true, the virtual machine NICs (and their MAC addresses) are preserved when unmanaging it. Otherwise, NICs are removed and MAC addresses can be reassigned.Unmanaging virtual machine actions:
Changes on the VM import functionality
A new parameter has been added to the
importUnmanagedInstances
API:forced
parameter is false by default and prevents importing a VM which has a NIC containing a MAC address that has been previously assigned by CloudStack. If it is set to true, the NICs with MAC addresses which already exist in the CloudStack database have the existing MAC addresses reassigned to its NICs.The usage events generated when importing unmanaged instances have been refactored:
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?