On Aug 11, 2012, at 5:31 PM, Justin Clift <[email protected]> wrote:

Hi Justin,

Yes, we are aware of this new feature and I like it a lot. Actually we were
pushing this for a half year (there is even RFE open from us in RHEVM/oVirt BZ 
;-)

The problem we are facing now, is not 'how to implement that' (it's pretty 
straight forward),
but 'if we are going to implement it now()'.

Since the majority of people now are using RHEV-M 3.0 and we need to support 
that,
JRD and others hesitate to switch over to this feature and claim hook method 
'obsolete'.

What I think we can do here is to update rbovirt gem, we use as interface for 
oVirt API
and add this new feature there along with the old hook code. That can work 
together
for old hook method and also for new method.

There is also problem with Audrey agent. I think with this new method, the 
user-data
file will appear in different location (correct me if i'm wrong). It will mean
that Audrey will somehow need to know to what version (of what injection 
method) was
used when launching an instance.

Cheers,

  -- Michal

> Hi Michal,
> 
> Was trying to get user_data working on the newly released
> oVirt 3.1.  But, no joy so far.
> 
> With oVirt 3.1, its supposed to be an inbuilt feature now
> instead of needing a special hook installed.
> 
> Looking at the oVirt 3.1 which implemented, seems like
> it's advertised differently now.  No longer in the
> "Capabilities" list?
> 
>  
> http://gerrit.ovirt.org/#/c/3460/10/backend/manager/modules/restapi/interface/definition/src/main/resources/api.xsd
> 
> Looking at that side by side diff, does that seem right
> to you?
> 
> The full oVirt change set is here if that's interesting:
> 
>  http://gerrit.ovirt.org/#/c/3460/
> 
> Wish I'd thought to look at this yesterday.  Already
> reformatted the boxes. (no longer oVirt 3.1) ;>
> 
> + Justin
> 
> --
> Aeolus Community Manager
> http://www.aeolusproject.org
> 

Reply via email to