VMPayload changes in oVirt 3.1

Hugh Brock hbrock at redhat.com
Mon Aug 13 13:23:15 UTC 2012


On Mon, Aug 13, 2012 at 09:21:00AM -0400, jvlcek wrote:
> On 08/13/2012 09:06 AM, Hugh Brock wrote:
> > On Mon, Aug 13, 2012 at 10:13:18AM +0200, Michal Fojtik wrote:
> >> On Aug 11, 2012, at 5:31 PM, Justin Clift <jclift at redhat.com> 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
> > Seems to me we need to get working now on compatibility across rhev
> > 3.0/oVirt 3.1 and (eventually) rhev 3.1. We're going to have to support
> > both versions anyway, so let's get it done now. 
> >
> > Michal let me know if you need any help making this happen.
> >
> > --Hugh
> >>> 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
> >>>
> 
> 
> My understanding is that RHEVm3.1 is not planned for the CloudForms 1.1
> release therefore making this feature something that is priorities after the
> work for 1.1.

I'll leave the prioritization up to you guys, just don't let the product
tail wag the upstream dog.

--Hugh

-- 
== Hugh Brock, hbrock at redhat.com                                   ==
== Engineering Manager, Cloud BU                                   ==
== Aeolus Project: Manage virtual infrastructure across clouds.    ==
== http://aeolusproject.org                                        ==

"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."
--Robert McCloskey



More information about the aeolus-devel mailing list