From vszocs at redhat.com Mon Nov 11 06:36:42 2013 Content-Type: multipart/mixed; boundary="===============0039859825769601936==" MIME-Version: 1.0 From: Vojtech Szocs To: users at ovirt.org Subject: Re: [Users] Fwd: oVirt UI plugins feature announcements Date: Mon, 11 Nov 2013 06:36:37 -0500 Message-ID: <2127666100.21532867.1384169797733.JavaMail.root@redhat.com> In-Reply-To: 1383903144.3516.60.camel@pc-ovido02.lan.ovido.at --===============0039859825769601936== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Ren=C3=A9 Koch (ovido)" > To: "Vojtech Szocs" > Cc: "users" > Sent: Friday, November 8, 2013 10:32:24 AM > Subject: Re: [Users] Fwd: oVirt UI plugins feature announcements > = > On Thu, 2013-11-07 at 17:24 -0500, Vojtech Szocs wrote: > > Hi guys, sharing some updates on oVirt UI plugins feature, see below for > > details. > > = > > Let me know if you have any questions. > > = > > Vojtech > > = > > = > > ----- Forwarded Message ----- > > From: "Vojtech Szocs" > > To: "engine-devel" > > Cc: "Einav Cohen" , "Itamar Heim" > > Sent: Thursday, November 7, 2013 11:21:21 PM > > Subject: oVirt UI plugins feature announcements > > = > > Hello everyone, > > = > > I'd like to share some important updates on oVirt UI plugins feature. > > = > > First of all, UI plugins wiki [1] is finally complete. API reference > > (application events, API functions, API options, entity types) now > > includes all the details and snippets of example code. I've also added > > section "Why load plugins via iframe element?" explaining reasons behind > > this design decision. > > = > > [1] http://www.ovirt.org/Features/UIPlugins > = > = > Great! Thanks a lot for the documentation - this makes life much easier! > = > = > > = > > You might have noticed the changes in oVirt Engine URI layout [2], these > > are already reflected in UI plugins wiki. For existing plugins, this me= ans > > changing URLs like this: > > = > > /webadmin/webadmin/plugin/ExamplePlugin/start.html > > = > > to this: > > = > > /ovirt-engine/webadmin/plugin/ExamplePlugin/start.html > > = > > [2] http://gerrit.ovirt.org/#/c/20473/ > = > = > Which version of oVirt uses the new URI - I assume 3.4? (and do you know > if the URI will be changed in RHEV as well)? Correct, new URI layout takes effect in oVirt 3.4, not sure about RHEV but = I think "ovirt-engine" in URI might change there. > = > I think it's important to mention this change in oVirt upgrade/release > notes to let users know that they have to change the UI plugin URI. When > packaging an UI plugin it's not a problem to check the oVirt version in > a %post section and run a sed command over the JSON file... I assume the URI layout change BZ [https://bugzilla.redhat.com/961677] will= have some release notes attached. For UI plugins, I was talking with Alon about this, we could promote the us= e of relative URIs to make UI plugins unaware of absolute URI layout. For example, in plugin descriptor: "url": "plugin/ExamplePlugin/start.html" // relative to WebAdmin base con= text path, i.e. /ovirt-engine/webadmin would result in: