[Engine-devel] server/api/ full_version tag stability

[Antoni Segura Puimedon]

----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "Antoni Segura Puimedon" <asegurap at redhat.com>, "engine-devel" <engine-devel at ovirt.org>, "Michael Pasternak"
> <mpastern at redhat.com>
> Sent: Friday, August 2, 2013 5:55:45 PM
> Subject: Re: [Engine-devel] server/api/ full_version tag stability
> 
> On 08/01/2013 11:27 AM, Alon Bar-Lev wrote:
> >
> >
> > ----- Original Message -----
> >> From: "Antoni Segura Puimedon" <asegurap at redhat.com>
> >> To: "engine-devel" <engine-devel at ovirt.org>
> >> Sent: Thursday, August 1, 2013 11:24:18 AM
> >> Subject: [Engine-devel] server/api/ full_version tag stability
> >>
> >> Hello list,
> >>
> >> In order to smarten up the ovirt-node registration flow I will ask the
> >> engine
> >> via rest API for it's version number, so that I can take decisions about
> >> capabilities for networking.
> >>
> >> I found that https:/server/api/ provides an xml document with a
> >> <full_version>
> >> tag that suits my purposes and I wanted to make sure that the stability of
> >> such
> >> element can be depended upon by asking you about it.
> >>
> >> IMHO, it could be nice instead that we would have an api endpoint (if it
> >> is
> >> not
> >> there and I missed it) that would provide capability tags information such
> >> as:
> >> bridgeless_nets, vm_live_snapshot, etc.
> >
> > It also should be anonymous API.
> 
> iirc, the rest api doesn't support yet anonymous access.

Indeed it doesn't, and unfortunately one flow of node registration doesn't have
any credentials, so we'll have to add a checkbox in the registration UI (and
on the kernel cmdline params for pxe booting).

> 
> i think the api should allow getting the version anonymously.
Agreed, version and if possible, capabilities.
> 
> other possible places are the registration servlet or the health
> servlet, both anonymous today.

If it were possible to get the version from the registration servlet it would
solve the problem with the registration flow.