On Tue, Feb 27, 2018 at 3:04 AM, Geoff Sweet wrote:
> OK, that's a great place for me to start. However the problem is that all
> my post-install tooling is now running on a VM that knows nothing about
> itself (having been installed via pxe and kickstart) like it's {vm_id}.
> Can the API be used
Yep, you can search for a VM using many attributes, for example to
search for a VM using IP address:
https://fqdn/ovirt-engine/api/vms?search=ip=1.2.3.4
Here you have more search parameters you can use to find a VM:
https://www.ovirt.org/documentation/admin-guide/appe-Using_Search_Bookmarks_a
OK, that's a great place for me to start. However the problem is that all
my post-install tooling is now running on a VM that knows nothing about
itself (having been installed via pxe and kickstart) like it's {vm_id}.
Can the API be used to query for a VM and it's attributes based on
something like
We don't have any such resource. We have those information in different
places of the API. For example to find the information about devices of
the VM, like network device information (IP address, MAC, etc), you can
query:
/ovirt-engine/api/vms/{vm_id}/reporteddevices
The FQDN is listed right
Is there an API endpoint that VM's can query to discover it's oVirt
metadata? Something similar to AWS's http://169.254.169.254/latest/
meta-data/ query in EC2? I'm trying to stitch a lot of automation workflow
together and so far I have had great luck with oVirt. But the next small
hurdle is to fi
5 matches
Mail list logo