1. On Tue, 2016-04-12 at 23:03 +0200, Frank Thommen wrote: > On 12.04.16 13:57, Alexander Wels wrote: > > > > On Monday, April 11, 2016 05:03:28 PM Brett I. Holcomb wrote: > > > > > > On Mon, 2016-04-11 at 20:41 +0200, Frank Thommen wrote: > > > > > > > > On 11.04.16 20:17, Brett I. Holcomb wrote: > > > > [...] > > > I'm in the same boat as Frank. I've done programming in various > > > languages since Fortran without the numbers <G> but only when > > > needed > > > for my job as an Engineer so I'm not a professional but just > > > trying to > > > get a job done. It would be nice to have a full reference so we > > > know > > > what to provide. When trying to connect with the api I finally > > > figured > > > out to use ca_file (like ca-file on the command line). Raz's > > > reference > > > is more complete but still leaves a lot out. The newer > > > equivalent of > > > Raz's reference seems to be http://www.ovirt.org/develop/release- > > > manage > > > ment/features/infra/python-sdk/. > > The Python/Java/Ruby SDKs are simply language specific wrappers > > around the REST > > api. So if you want a full list of all the options available check > > out the > > REST api documentation. You will have to translate a particular > > REST api > > field/feature to the SDK, but all the SDKs are generated from the > > REST api > > interface definition so the naming and everything should be the > > same. > That makes sense, thanks. On the other hand I could also not find > any > REST api reference. Just some pages with examples a la "find it out > yourself from there"... > > frank > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
Same here. A lot of examples, some more detailed but no "API Reference Manual for oVirt REST API" like we had in the old days <G>. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users