- Devel - oVirt List Archives

[ATN] Introduction of RESTAPI metamodel
by Juan Hernández 26 Oct '15

26 Oct '15

Hello, I will soon merge the following patches that introduce a new way to specify the contracts of the RESTAPI: restapi: Introduce metamodel https://gerrit.ovirt.org/45852 restapi: Use metamodel https://gerrit.ovirt.org/46478 restapi: Generate JAX-RS interfaces from model https://gerrit.ovirt.org/47337 These patches introduce a new "metamodel" concept, and move the current specification of the RESTAPI based on XML schema and JAX-RS interfaces to a new "model" built on the new metamodel. What does this mean for you in practical terms? Currently when you want to introduce or modify one of the data types used by the RESTAPI you start by modifying the XML schema. Once the patches are merged the XML schema will never be touched, as it will be automatically generated from the "model". For example, imagine that you need to add a new "color" attribute to the "VM" entity. To do so with the new model you will have to modify the following file, which is the specification of the "Vm" entity, written as a Java interface: https://gerrit.ovirt.org/#/c/46478/16/backend/manager/modules/restapi/model… In that interface you will have to add a line like this: String color(); Note that this Java interface is just the specification of the entity, it won't be used at all during runtime. Instead of that the XML schema will be generated from it, and then Java will be generated from the XML schema, as we do today (this will change in the future, but not yet). Same for the services. If you want to add a new "paint" action to the "Vm" resource then you won't modify the JAX-RS interfaces, instead of that you will modify the following file, which is the specification of the "Vm" service, written as a Java interface: https://gerrit.ovirt.org/#/c/47337/6/backend/manager/modules/restapi/model/… In that interface you will need to add a sub-interface representing the action: interface Paint { } The JAX-RS interface will be generated from that. Currently these sub-interfaces are empty. In the future they will contain the specifications of the parameters (currently in the rsdl_metadata.yml file). These changes will currently affect only the specification of the RESTAPI, not the implementation, so in in the "Backend*Resource" classes things won't change yet. If you have doubts, please let me know. Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

2 1

[ANN] oVirt 3.5.5 Final Release is now available
by Sandro Bonazzola 26 Oct '15

26 Oct '15

The oVirt Project is pleased to announce the availability of the oVirt 3.5.5 Final Release, as of October 26th, 2015. This release is available now for Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar), Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar) and Fedora 21. This release of oVirt 3.5.5 includes updated packages for: - oVirt Engine - oVirt Hosted Engine HA - oVirt Hosted Engine Setup - VDSM - oVirt Data Warehouse - oVirt Reports - oVirt Engine SDK - oVirt Engine client - QEMU KVM See the release notes [1] for a list of fixed bugs. Please refer to release notes [1] for Installation / Upgrade instructions. a new oVirt Live ISO is already available [2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.5.5_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.5/iso/ovirt-live/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ANN] oVirt 3.6.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 22 Oct '15

22 Oct '15

[ANN] oVirt 3.6.0 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 3.6 for testing, as of October 22nd, 2015. This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar), Fedora 21 and Fedora 22. Highly experimental support for Debian 8.1 Jessie has been added too. This release of oVirt 3.6.0 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. New oVirt Node ISO and oVirt Live ISO will be available soon as well[2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.6_Release_Notes [2] http://plain.resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ANN] oVirt 3.6.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 22 Oct '15

22 Oct '15

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 3.6 for testing, as of October 22nd, 2015. This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar), Fedora 21 and Fedora 22. Highly experimental support for Debian 8.1 Jessie has been added too. This release of oVirt 3.6.0 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. New oVirt Node ISO and oVirt Live ISO will be available soon as well[2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.6_Release_Notes [2] http://plain.resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Hello and a question about VM Custom Property
by zhukaijie 21 Oct '15

21 Oct '15

Hello, recently I have read something about VM custom properties. There is a question I'm thinking about. If a VM A has a custom property named PARAM. I set VM A'S PARAM a value. Then before I start the VM from web, where is the PARAM value stores? Does it store in Postgresql? Thank you.

2 1

Hello and a question about VM Custom Property
by zhukaijie 21 Oct '15

21 Oct '15

Hello, recently I have read something about VM custom properties. There is a question I'm thinking about. If a VM A has a custom property named PARAM. I set VM A'S PARAM a value. Then before I start the VM from web, where is the PARAM value stores? Does it store in Postgresql? Thank you.

1 0

Re: [ovirt-devel] Question about the ovirt-engine-sdk-java
by Michael Pasternak 20 Oct '15

20 Oct '15

------=_Part_291056_1850182726.1445347932554 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Salifou, OK, i see now, then you have two options: a) To extend the sdk: 1. extend java-sdk by allowing to inject custom headers in every request=C2= =A0(not trivial as all ovirt SDKs are auto-generated,but if its common case= , you may find yourself getting help from community/maintainers) 2. fork java-sdk customizing it for your needs I'd recommend the former as fork will leave you with no support/maintenance= from community plus you'll haveto implement new=C2=A0features by your own = (what will become a moving target very quickly)=20 b) Proxying the sdk You can implement dynamic proxy wrapping SDK's HttpProxy.java#execute and i= ntercept the context from there,but you've to stay tuned as backward compat= ibility is for interface and not for SDK internals,so "potentially" you can= find your code broken in one of the following upgrades hope it helps.=C2=A0 On Monday, October 19, 2015 6:05 PM, Salifou Sidi M. Malick <ssidimah@= redhat.com> wrote: =20 Hi Micheal, Thanks for replying. Unfortunately the headers are dynamic ... Here is the story: We implemented a custom RHEV-M AAA module for a client in order to allow their custom portal to make RHEV-M API=20 calls.=20 The custom AAA module requires extra dynamic data in the HTTP=20 request (as request headers for now but request parameters=20 should be fine too).=20 Their is no problem if they go with the REST API, I am just=20 trying to anticipate/identify potential integration problem ... It seems like they will have to use the REST API or modify the=20 java sdk ...=C2=A0=20 Thanks a lot, Salifou ----- Original Message ----- From: "Michael Pasternak" <mishka8520(a)yahoo.com> To: "Salifou Sidi M. Malick" <ssidimah(a)redhat.com> Cc: "Users" <users(a)ovirt.org> Sent: Sunday, October 18, 2015 5:45:05 AM Subject: Re: Question about the ovirt-engine-sdk-java Hi=C2=A0Salifou, Actually java sdk is=C2=A0intentionally=C2=A0hiding transport level interna= ls so developers could stay in java domain,if your headers are static, easi= est way would be using reverse proxy in a middle to intercept requests,=C2= =A0 can you tell me why do you need this? =20 =C2=A0 =C2=A0 On Friday, October 16, 2015 1:14 AM, Salifou Sidi M. Malick <= ssidimah(a)redhat.com> wrote: =C2=A0=20 Hi Micheal, I have a question about the ovirt-engine-sdk-java. Is there a way to add custom request headers to each RHEVM API call? Here is an example of a request that I would like to do: $ curl -v -k \ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -H "ID: user1(a)ad.xyz.com" \ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -H "PASSWORD: Pwssd" \ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -H "TARGET: kobe" \ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://vm0.smalick.com/api/hosts I would like to add ID, PASSWORD and TARGET as HTTP request header.=20 Thanks, Salifou =20 ------=_Part_291056_1850182726.1445347932554 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <html><head></head><body><div style=3D"color:#000; background-color:#fff; f= ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve= tica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id=3D"yiv487097= 0104"><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_1_1445338067930_25413">= <br><br></div><div class=3D"yiv4870970104yqt0049005238" id=3D"yiv4870970104= yqtfd33472"><div id=3D"yui_3_16_0_1_1445338067930_25382"><div style=3D"colo= r:#000;background-color:#fff;font-family:HelveticaNeue-Light, Helvetica Neu= e Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-s= ize:13px;" id=3D"yui_3_16_0_1_1445338067930_25381"><div id=3D"yiv4870970104= yui_3_16_0_1_1445338067930_23478"><span style=3D"font-family:'Helvetica Neu= e', 'Segoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif;">Hi Salifou,= </span><br clear=3D"none"></div><div class=3D"yiv4870970104qtdSeparateBR" i= d=3D"yui_3_16_0_1_1445338067930_25383"><br clear=3D"none"><br clear=3D"none= "></div> </div></div></div></div><div class=3D".yiv4870970104yahoo_quoted" = id=3D"yui_3_16_0_1_1445338067930_25398"><div id=3D"yiv4870970104yui_3_16_0_= 1_1445338067930_23388" style=3D"font-family:HelveticaNeue-Light, Helvetica = Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fon= t-size:13px;"><div id=3D"yiv4870970104yui_3_16_0_1_1445338067930_23387" sty= le=3D"font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida G= rande, sans-serif;font-size:16px;"><div class=3D"yiv4870970104y_msg_contain= er" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_23484"><div id=3D"yiv4870= 970104"><div id=3D"yiv4870970104yui_3_16_0_1_1445338067930_23483"><div id= =3D"yiv4870970104yui_3_16_0_1_1445338067930_23482" style=3D"color:#000;back= ground-color:#fff;font-family:HelveticaNeue-Light, Helvetica Neue Light, He= lvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px;">= <div id=3D"yiv4870970104"><div id=3D"yiv4870970104yui_3_16_0_1_144533806793= 0_7276"><div id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7275" style=3D"c= olor:#000;background-color:#fff;font-family:HelveticaNeue-Light, Helvetica = Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fon= t-size:13px;"><div dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_144533806793= 0_4283"><span></span></div><div dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1= _1445338067930_4283"><span style=3D"font-family: 'Helvetica Neue', 'Segoe U= I', Helvetica, Arial, 'Lucida Grande', sans-serif;" id=3D"yui_3_16_0_1_1445= 338067930_25412">OK, i see now, then you have two options:</span><br></div>= <div dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span = class=3D"yiv4870970104" style=3D"font-family:'Helvetica Neue', 'Segoe UI', = Helvetica, Arial, 'Lucida Grande', sans-serif;"><br clear=3D"none"></span><= /div><div dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><= span class=3D"yiv4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_= 7286" style=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, = 'Lucida Grande', sans-serif;">a) To extend the sdk:</span></div><div dir=3D= "ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yi= v4870970104" style=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, = Arial, 'Lucida Grande', sans-serif;"><br clear=3D"none"></span></div><div d= ir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class= =3D"yiv4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4800" styl= e=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Gr= ande', sans-serif;">1. extend java-sdk by allowing to inject custom headers= in every request</span><span class=3D"yiv4870970104" style=3D"font-family:= 'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif= ;"> </span><span class=3D"yiv4870970104" id=3D"yiv4870970104yui_3_16_0= _1_1445338067930_8082" style=3D"font-family:'Helvetica Neue', 'Segoe UI', H= elvetica, Arial, 'Lucida Grande', sans-serif;">(not trivial as all ovirt SD= Ks are auto-generated</span><span style=3D"font-family:'Helvetica Neue', 'S= egoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif;">,</span></div><di= v dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span cla= ss=3D"yiv4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_9090" st= yle=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida = Grande', sans-serif;">but if its common case, you may find yourself getting= help from community/maintainers)</span></div><div dir=3D"ltr" id=3D"yiv487= 0970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yiv4870970104" style= =3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Gra= nde', sans-serif;"><br clear=3D"none"></span></div><div dir=3D"ltr" id=3D"y= iv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yiv4870970104" = id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4801" style=3D"font-family:'H= elvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Grande', sans-serif;"= >2. fork java-sdk customizing it for your needs</span></div><div dir=3D"ltr= " id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yiv487= 0970104" style=3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Aria= l, 'Lucida Grande', sans-serif;"><br clear=3D"none"></span></div><div dir= =3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D= "yiv4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4974" style= =3D"font-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Gra= nde', sans-serif;">I'd recommend the former as fork will leave you with no = support/maintenance from community plus you'll have</span></div><div dir=3D= "ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_4283"><span class=3D"yi= v4870970104" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7285" style=3D"f= ont-family:'Helvetica Neue', 'Segoe UI', Helvetica, Arial, 'Lucida Grande',= sans-serif;">to implement new </span><span id=3D"yiv4870970104yui_3_1= 6_0_1_1445338067930_5162" style=3D"font-family:'Helvetica Neue', 'Segoe UI'= , Helvetica, Arial, 'Lucida Grande', sans-serif;">features by your own (wha= t will become a moving target very quickly)</span></div> <br clear=3D"none= "><div class=3D"yiv4870970104qtdSeparateBR" dir=3D"ltr" id=3D"yiv4870970104= yui_3_16_0_1_1445338067930_7274">b) Proxying the sdk</div><div class=3D"yiv= 4870970104qtdSeparateBR" dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_144533= 8067930_7274"><br clear=3D"none"></div><div class=3D"yiv4870970104qtdSepara= teBR" dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7274">You c= an implement dynamic proxy wrapping SDK's HttpProxy.java#execute and interc= ept the context from there,</div><div class=3D"yiv4870970104qtdSeparateBR" = dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7274">but you've = to stay tuned as backward compatibility is for interface and not for SDK in= ternals,</div><div class=3D"yiv4870970104qtdSeparateBR" dir=3D"ltr" id=3D"y= iv4870970104yui_3_16_0_1_1445338067930_7274">so "potentially" you can find = your code broken in one of the following upgrades</div><div class=3D"yiv487= 0970104qtdSeparateBR" dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_144533806= 7930_7274"><br clear=3D"none"></div><div class=3D"yiv4870970104qtdSeparateB= R" dir=3D"ltr" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_7274">hope it = helps. <br clear=3D"none"><br clear=3D"none"></div><div class=3D"yiv48= 70970104yqt0562777282" id=3D"yiv4870970104yqt81591"></div></div></div></div= ><div class=3D"yiv4870970104yqt7829638567" id=3D"yiv4870970104yqt81845"><di= v id=3D"yiv4870970104yui_3_16_0_1_1445338067930_8533"> <div id=3D"yiv487097= 0104yui_3_16_0_1_1445338067930_8532" style=3D"font-family:HelveticaNeue-Lig= ht, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, = sans-serif;font-size:13px;"> <div id=3D"yiv4870970104yui_3_16_0_1_144533806= 7930_8531" style=3D"font-family:HelveticaNeue, Helvetica Neue, Helvetica, A= rial, Lucida Grande, sans-serif;font-size:16px;"> <div dir=3D"ltr" id=3D"yi= v4870970104yui_3_16_0_1_1445338067930_8554"> <font id=3D"yiv4870970104yui_3= _16_0_1_1445338067930_8559" size=3D"2" face=3D"Arial"> On Monday, October 1= 9, 2015 6:05 PM, Salifou Sidi M. Malick <ssidimah(a)redhat.com> wrote:<= br clear=3D"none"> </font> </div> <br clear=3D"none"><br clear=3D"none"> <= div class=3D"yiv4870970104y_msg_container" id=3D"yiv4870970104yui_3_16_0_1_= 1445338067930_8712">Hi Micheal,<br clear=3D"none"><br clear=3D"none">Thanks= for replying. Unfortunately the headers are dynamic ...<br clear=3D"none">= <br clear=3D"none">Here is the story:<br clear=3D"none"><br clear=3D"none">= We implemented a custom RHEV-M AAA module for a client<br clear=3D"none">in= order to allow their custom portal to make RHEV-M API <br clear=3D"none">c= alls. <br clear=3D"none"><br clear=3D"none">The custom AAA module requires = extra dynamic data in the HTTP <br clear=3D"none">request (as request heade= rs for now but request parameters <br clear=3D"none">should be fine too). <= br clear=3D"none"><br clear=3D"none">Their is no problem if they go with th= e REST API, I am just <br clear=3D"none">trying to anticipate/identify pote= ntial integration problem ...<br clear=3D"none"><br clear=3D"none">It seems= like they will have to use the REST API or modify the <br clear=3D"none">j= ava sdk ...  <br clear=3D"none"><br clear=3D"none">Thanks a lot,<br cl= ear=3D"none">Salifou<br clear=3D"none"><br clear=3D"none"><div class=3D"yiv= 4870970104yqt8023103542" id=3D"yiv4870970104yqtfd83808"><br clear=3D"none">= ----- Original Message -----<br clear=3D"none">From: "Michael Pasternak" &l= t;<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:mishka8520@yahoo.com= " target=3D"_blank" href=3D"mailto:mishka8520@yahoo.com">mishka8520(a)yahoo.c= om</a>><br clear=3D"none">To: "Salifou Sidi M. Malick" <<a rel=3D"nof= ollow" shape=3D"rect" id=3D"yiv4870970104yui_3_16_0_1_1445338067930_23606" = ymailto=3D"mailto:ssidimah@redhat.com" target=3D"_blank" href=3D"mailto:ssi= dimah(a)redhat.com">ssidimah(a)redhat.com</a>><br clear=3D"none">Cc: "Users"= <<a rel=3D"nofollow" shape=3D"rect" ymailto=3D"mailto:users@ovirt.org" = target=3D"_blank" href=3D"mailto:users@ovirt.org">users(a)ovirt.org</a>><b= r clear=3D"none">Sent: Sunday, October 18, 2015 5:45:05 AM<br clear=3D"none= ">Subject: Re: Question about the ovirt-engine-sdk-java<br clear=3D"none"><= br clear=3D"none">Hi Salifou,<br clear=3D"none">Actually java sdk is&n= bsp;intentionally hiding transport level internals so developers could= stay in java domain,if your headers are static, easiest way would be using= reverse proxy in a middle to intercept requests, <br clear=3D"none"><= br clear=3D"none">can you tell me why do you need this?<br clear=3D"none"> = <br clear=3D"none"><br clear=3D"none"><br clear=3D"none">    On = Friday, October 16, 2015 1:14 AM, Salifou Sidi M. Malick <<a rel=3D"nofo= llow" shape=3D"rect" ymailto=3D"mailto:ssidimah@redhat.com" target=3D"_blan= k" href=3D"mailto:ssidimah@redhat.com">ssidimah(a)redhat.com</a>> wrote:<b= r clear=3D"none">  <br clear=3D"none"><br clear=3D"none"> Hi Micheal,= <br clear=3D"none"><br clear=3D"none">I have a question about the ovirt-eng= ine-sdk-java.<br clear=3D"none"><br clear=3D"none">Is there a way to add cu= stom request headers to each RHEVM API call?<br clear=3D"none"><br clear=3D= "none">Here is an example of a request that I would like to do:<br clear=3D= "none"><br clear=3D"none">$ curl -v -k \<br clear=3D"none">    &n= bsp;     -H "ID: <a rel=3D"nofollow" shape=3D"rect" ymailto=3D"ma= ilto:user1@ad.xyz.com" target=3D"_blank" href=3D"mailto:user1@ad.xyz.com">u= ser1(a)ad.xyz.com</a>" \<br clear=3D"none">         = -H "PASSWORD: Pwssd" \<br clear=3D"none">        &nbsp= ; -H "TARGET: kobe" \<br clear=3D"none">          = <a rel=3D"nofollow" shape=3D"rect" target=3D"_blank" href=3D"https://vm0.sm= alick.com/api/hosts">https://vm0.smalick.com/api/hosts</a><br clear=3D"none= "><br clear=3D"none"><br clear=3D"none">I would like to add ID, PASSWORD an= d TARGET as HTTP request header. <br clear=3D"none"><br clear=3D"none">Than= ks,<br clear=3D"none">Salifou<br clear=3D"none"><br clear=3D"none"><br clea= r=3D"none"></div><br clear=3D"none"><br clear=3D"none"></div> </div> </div= > </div></div></div></div></div><br clear=3D"none"><br clear=3D"none"></di= v> </div> </div> </div></div></body></html> ------=_Part_291056_1850182726.1445347932554--

1 0

Termin gestrichen: oVirt Node weekly meeting - Mo 19. Okt. 2015 16:00 - 16:30 (fdeutsch@redhat.com)
by fdeutsch＠redhat.com 19 Oct '15

19 Oct '15

Dieser Termin wurde gestrichen und aus Ihrem Kalender entfernt. Titel: oVirt Node weekly meeting Hey, this is an invitation to the weekly oVirt Node devel meetings. Anyone interested or related to Node development is welcome. Wann: Mo 19. Okt. 2015 16:00 - 16:30 Berlin Wo: irc://irc.oftc.net#ovirt Kalender: fdeutsch(a)redhat.com Wer * Fabian Deutsch - Organisator * tlitovsk(a)redhat.com * devel(a)ovirt.org * wdaniel(a)redhat.com Einladung von Google Kalender: https://www.google.com/calendar/ Sie erhalten diese E-Mail unter devel(a)ovirt.org, da Sie ein Gast bei diesem Termin sind. Lehnen Sie diesen Termin ab, um keine weiteren Informationen zu diesem Termin zu erhalten. Sie können auch unter https://www.google.com/calendar/ ein Google-Konto erstellen und Ihre Benachrichtigungseinstellungen für Ihren gesamten Kalender steuern. Wenn Sie diese Einladung weiterleiten, kann jeder Empfänger Ihre Antwort auf die Einladung ändern. Weitere Informationen finden Sie unter https://support.google.com/calendar/answer/37135#forwarding

1 0

[QE][ACTION REQUIRED] oVirt 3.6.0 status
by Sandro Bonazzola 15 Oct '15

15 Oct '15

Hi, We planned to start composing next milestone of oVirt 3.6.0 on *2015-10-12 08:00 UTC* from 3.6 branches. There are still 234 bugs [1] targeted to 3.6.0. Whiteboard RC GA Total docs 5 0 15 dwh 1 0 1 external 0 1 1 gluster 40 0 40 i18n 2 0 2 infra 23 6 29 integration 0 1 1 network 27 1 28 node 4 0 4 reports 1 0 1 sla 36 2 38 storage 49 9 58 ux 10 0 10 virt 5 1 6 Total 213 21 234 Maintainers must scrub them and push non critical bugs to ZStream releases. There is 1 acknowledged blocker for 3.6.0: Bug 1196640 - [Monitoring] Network utilisation is not shown for the VM And there are 21 bugs suggested as blockers for 3.6.0: Bug ID Status Whiteboard Summary 1259441 NEW gluster Can't create new Gluster storage domain - Permission denied 1261822 NEW integration BUILD WGT 3.6 1259468 NEW network Setupnetworks fails from time to time with error 'Failed to bring interface up' 1262026 NEW network Host booted up after upgrading it 3.5.4->3.6 with rhevm bridge with DEFROUTE=no. 1262051 NEW network Host move from 'up' to 'connecting' and back to 'up' from time to time 1243811 POST sla vm with dedicate host fails to run on other host, if dedicated host is in maintenance 1262293 POST sla Creating a VM with Foreman fails if cluster has more than one CPU profile 1239297 ASSIGNED storage Logical disk name is not showing up 1118349 NEW storage [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError 1250540 NEW storage Re-attaching fresh export domain fails - hsm::2543::Storage.HSM::(disconnectStorageServer) Could not disconnect from storageServer 1253790 NEW storage [BLOCKED] consume fix for "iscsi_session recovery_tmo revert back to default when a path becomes active" 1253975 NEW storage [vdsm] extendVolumeSize task is not cleared in case of a live merge failure for a volume that was extended 1151838 NEW storage [vdsm] Scan alignment fails with a VirtAlignError 1238239 NEW storage Deployment of hosted engine failed on ISCSI storage with 'Error block device action' 1257240 NEW storage Template's disk format is wrong 1261953 NEW storage [vdsm] Host fails to connect to storage pool 'MiscBlockReadException: Internal block device read failure' 1261980 NEW storage failed LSM due to connection lost with qemu process 1138144 NEW storage [BLOCKED]Failed to autorecover storage domain after unblocking connection with host 1253756 POST storage [BLOCKED] libvirt reports physical=0 for COW2 volumes on block storage 1251008 POST storage [BLOCKED] libvirt reports physical=0 for COW2 volumes on block storage 1258901 POST storage [UX] Toggling wad property while vm is up shouldn't be greyed out There are 17 bugs marked as regressions to be solved in 3.6.0 [2] Given current bugs status, release criteria are not met [3] so we need to review bug status for planning the RC. Action items: - Developers: check suggested blockers, fix acknowledged blockers, regressions and re-target remaining blockers. - Please check Jenkins status for 3.6 jobs and sync with relevant maintainers if there are issues. - Please fill release notes, the page has been created here [4] - Please test oVirt 3.6 nightly snapshot and check for regressions from 3.5 [1] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir… status%3Anew%2Cassigned%2Cpost [2] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3Aovir… [3] http://www.ovirt.org/OVirt_3.6_Release_Management#Candidate_Release_Criteria [4] http://www.ovirt.org/OVirt_3.6_Release_Notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 4

[ANN] oVirt 3.6.0 Second Release Candidate is now available for testing
by Sandro Bonazzola 15 Oct '15

15 Oct '15

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 3.6 for testing, as of October 15th, 2015. This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar), Fedora 21 and Fedora 22. Highly experimental support for Debian 8.1 Jessie has been added too. This release of oVirt 3.6.0 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. New oVirt Node ISO and oVirt Live ISO will be available soon as well[2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.6_Release_Notes [2] http://plain.resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrorsCurrent_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0