DaanHoogland commented on PR #11061: URL: https://github.com/apache/cloudstack/pull/11061#issuecomment-3496434546
> > @phsm > > This feature looks great and provides valuable functionality for monitoring and exporting. > > My main concern is related to VM lifecycle management: I remember for KVM there is a function to unmanage a VM from CloudStack. If a VM is unmanaged this way, the newly added metadata configuration must be revoked or reset to its normal state. Has this scenario been taken into consideration. > > Hello, sorry for the late reply: had to allocate some time to build the newer Cloudstack 4.22-RC and test the Unmanage behvior. > > I wanted to test what actually happens during unmanage. I compared the VM domain XML before and after the Unmanage: the XMLs are identical. > > Which means, even the smbios info says its Cloudstack: > > ``` > <sysinfo type='smbios'> > <system> > <entry name='manufacturer'>Apache Software Foundation</entry> > <entry name='product'>CloudStack KVM Hypervisor</entry> > <entry name='serial'>15d24df0-db8d-44c4-819c-b58897e8efa0</entry> > <entry name='uuid'>15d24df0-db8d-44c4-819c-b58897e8efa0</entry> > </system> > </sysinfo> > ``` > > Thus, I am unsure whether the metadata should or should not stay in the unmanaged instance. So far the Unmanage functionality looks like "completely forget the VM and leave it be in the libvirt". yes, so do you want to give it the extra attention to remove the metadata @phsm ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
