Hi All,
As I stated in a previous thread, we use instances types and wanted to automate some parts
to manage it [1]. Thansk to ovirt-orb/lago and pointers given in the last thread, I'm
working on ansible an module to manage ovirt instance types, but I'm facing some
troubles for some of instance type attributes. From the API, I don't have access to
all fields provided via WebUI (eg: Custom Emulated Machine), and it seems that some fields
can be added/updated via the API but are not part of the response when you read an
instance type (eg: VirtIO-SCSI Enabled). Provided examples are not exhaustive. I tried to
find my way in the oVirt engine code-base to see if the fix will be easy for a non java
developer like me. I find, I think, that it seems to be some API definitions for instance
type [2] that define, if I understand it well, all verbs that can be applied to each
resource and what field can be put when adding an instance type, but nothing about fields
to be included when you read a resource (and I'm not sure if its related to v4 API). I
find also some java code [3] [4] that seems related to this but As I'm not a java
developer, its a little bit difficult for me to find my path in it. For me this
inconsistencies are a bug, but as you stated that instance types are in deep maintenance
mode, do you think that bug will get some attention ?
My objective is to have a ansible module that manage the hardware/bios related stuff
(memory, boot sequence, scsi controller, bios type, almost all the things) and HA for
instance type.
Have a nice day.
Cheers.
[1]:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TJAXYBMSIAA...
[2]:
https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules...
[3]:
https://github.com/oVirt/ovirt-engine/blob/ede62008318d924556bc9dfc5710d9...
[4]:
https://github.com/oVirt/ovirt-engine/blob/ede62008318d924556bc9dfc5710d9...
[5]:
https://ovirt.github.io/ovirt-engine-sdk/4.1/types.m.html#ovirtsdk4.types...
--
Baptiste