Yeah thx! It's a one time setup tags and primarily to identify which tenant
the vm belongs to so no need to tweak it during the instance life cycle.
On Tue, Jan 19, 2016 at 11:21 AM, Cole Robinson wrote:
> Interesting, sounds cool :) Are these bits a one time setup thing or do
> they
> need to b
Interesting, sounds cool :) Are these bits a one time setup thing or do they
need to be tweaked for an existing VM?
- Cole
On 01/19/2016 11:10 AM, Abdi Ibrahim wrote:
> there is a process running on the hypervisor (kvm in my case) watching for VM
> events (launch, destroy, stop etc...) and reads
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 th
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
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 cust
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-i
