there is a process running on the hypervisor (kvm in my case) watching for VM events (launch, destroy, stop etc...) and reads the domain xml file to trigger a configuration management workflow. For example there is a tag for tenant name and ID (OpenStack) and when the VM is shutdown or rebooted the process notifies a Consul cluster (Hashicorp) for monitoring purposes. Hope this make sense.
On Tue, Jan 19, 2016 at 11:03 AM, Cole Robinson <crobi...@redhat.com> wrote: > What types of metadata are you adding? > > - Cole > > On 01/19/2016 11:00 AM, Abdi Ibrahim wrote: > > Yeah... I'm aware of that but students are given vmm access against > > hypervisors in order to launch instances/domains but no ssh access. > Folks are > > from vmware infrastructure where there is a familiarity on vSphere > Client with > > all options available on the UI. Will continue with virt-install with > custom > > xml file to include any metadata. > > > > Thanks for the response tho... much appreciated. > > > > On Tue, Jan 19, 2016 at 10:56 AM, Cole Robinson <crobi...@redhat.com > > <mailto:crobi...@redhat.com>> wrote: > > > > On 01/18/2016 01:24 PM, Abdi Ibrahim wrote: > > > Just wondering if it is possible to pass metadata to the > virt-manager (GUI > > > client) instead of using the virsh command. > > > > > > > Outside of the basic bits like description and title, there isn't any > > virt-manager support. We should add more support to > virt-install/virt-xml > > though... > > > > - Cole > > > > > >
_______________________________________________ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
