[ovirt-users] Re: Ovirt API and CLI

Yes. The devs call it "SDK4", which has been around for a few releases now. The CLI, however, uses SDK3, which was removed from Ovirt 4.4. Search for "ovirt-shell". -derek On Fri, February 28, 2020 10:47 am, Eugène Ngontang wrote: > @Derek, > > You're talking about a client the should up-port, but before having a > client, my question is is there a documented API (server) to interact with > through that client? > > Eugene NG > > Le jeu. 27 févr. 2020 à 14:57, Derek Atkins <derek(a)ihtfp.com&gt; a écrit : > >> Eugene, >> >> On Thu, February 27, 2020 4:53 am, Eugène Ngontang wrote: >> > Yes Ansible ovirt_vms module is useful, I use it for >> > provisioning/deployment, but once my VM created, I'd like to >> > administrate/interact with them, I don't think I should write >> playbooks >> > for >> > that. >> > >> > But I'll find a solution. >> >> I am in a similar boat as you. I wrote some management scripts around >> ovirt-shell when I first started using ovirt (4.0), in order to mimic >> some >> vmware-server features that I needed. I run a single-host hosted-engine >> environment, so when the system boots up (e.g. from a power failure) I >> wanted all my VMs to auto-start, and to start in the correct order. I >> can't use the ovirt power management utilities because it's only a >> single >> host. So I wrote a relatively small script around ovirt-shell that >> would >> do the following: >> >> 1) Wait for the engine to respond >> 2) Wait for the storage to come online >> 3) Start my VMs, with appropriate order and delay between >> (e.g., ensure my DNS server and KDC come up before other VMs) >> >> I know that SOME of these features are now in Ovirt (and I think they >> are >> even in 4.4), but my understanding is that they only return the system >> to >> previous state and wont auto-start a VM that was cleanly shut down. >> Also >> the ordering is, IIUC, somewhat course (low/medium/high). >> >> At this point I plan to delay my deployment of 4.4 or beyond because >> what >> I have in 4.3 is working (still), and frankly I have no interest in >> learning Ansible or Python just to replace what should be a relatively >> simple script. >> >> I honestly find it very sad that the developers wont up-port >> ovirt-client >> to SDK4. If SDK4 is "so good" vs SDK3 then I don't see why it would be >> hard to do that. And if it IS that hard to do, then how do they expect >> us >> to use it? >> >> Maybe I will find some time to play with OV4.4 on a test system in order >> to play with the auto-start features. In my copious amounts of free >> time. :( >> >> Thanks, >> >> -derek >> >> -- >> Derek Atkins 617-623-3745 >> derek(a)ihtfp.com www.ihtfp.com >> Computer and Internet Security Consultant >> >> > > -- > LesCDN <http://lescdn.com> > engontang(a)lescdn.com > ------------------------------------------------------------ > *Aux hommes il faut un chef, et au* > > * chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te > voit on te juge!* > -- Derek Atkins 617-623-3745 derek(a)ihtfp.com www.ihtfp.com Computer and Internet Security Consultant