What feels hacky is that I have so little information about the VM i'm running from within that I'd have a hard time crawling the API enough to know the information I got was about the VM I'm testing against. Per my later email the ID in /var/lib/cloud/data/instance-id is not the same that I'd need to hit the REST API to describe
On Wed, Mar 1, 2017 at 9:45 AM, Yaniv Kaul <[email protected]> wrote: > > > On Wed, Mar 1, 2017 at 4:53 PM Marc Young <[email protected]> wrote: > >> Ive looked through what documentation I can find and i only come up on >> bug reports from years ago, but: is there anyway to get metadata about a >> oVirt server metadata from the context of a VM ? cloud-init supports a >> metadata service that sits on 169.254.169.254 to retrieve info like >> instance-id etc. This is very useful in AWS which I'm familiar with. >> > > We support cloud-init via config drive, not over the network. > > >> >> My context is that I'd like to run some assertions against a VM and the >> test framework I'm using runs all assertions from within the VM itself. So >> If i wanted to assert that the host running my VM is "x.foo.com" I'd >> have to be able to retrieve that from within the VM. I can do that via the >> REST API but that requires me to get a REST user/pass inside the vm and >> feels hacky. The common way of doing this at openstack/aws is to curl the >> metadata service which replies with information only relevant to the >> machine asking. >> > > Feels OK to me - doesn't sound too hacky to me. > You can do it via Ansible, but still need creds. > I don't remember if anything in the VM BIOS (dmidecode) will help you > there - I think not. > Y. > > >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/devel > >
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
