- Devel - oVirt List Archives

[Engine-devel] RESTAPI: what is the purpose for /api/disks collection
by Michael Pasternak 11 Jun '12

11 Jun '12

IIUC originally this collection was suppose to keep all disks that can be shared between different vms and/or available to be attached to certain vm. At the moment this collection contains all disks in system while engine does not provide any search capabilities for it, in my view it not really useful, till we add search capabilities for being able: 1. locate <shareable>true</shareable> disks 2. distinguish between <shareable>true|false</shareable> and <active>true|false</active> disks 3. maybe even worth taking <active>false</active>&&<shareable>false</shareable> out of this collection and place them under api/clusters/xxx/disks (or under DC). this way /api/disks will only have disks that can be shared. your thoughts? -- Michael Pasternak RedHat, ENG-Virtualization R&D

5 11

[Engine-devel] live migration and different technologies
by Itamar Heim 11 Jun '12

11 Jun '12

Hi Daniel, on the quantum-ovirt call today the question of live migration between multiple technologies was raised. iirc, you implemented the abstraction in libvirt between what the guest sees and the actual host networking implementation for live migration. can you please share if there are any considerations around live migrations across different network implementations (bridge, sr-iov, ovs, qbg, openflow, etc.) thanks, Itamar

3 4

[Engine-devel] Does RHEVM/Ovirt API violates the stateless requriement of REST?
by Jaroslav Henner 11 Jun '12

11 Jun '12

Hi. I think the fact that when updating (PUT), we may send only the updated xml elements violates following. http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm ------8<------8<------8<------8<------ Figure 5-2: The client-server style 5.1.3 Stateless We next add a constraint to the client-server interaction: communication must be stateless in nature, as in the client-stateless-server (CSS) style of Section 3.4.3 (Figure 5-3), such that each request from client to server must contain all of the information necessary to understand the request, and cannot take advantage of any stored context on the server. Session state is therefore kept entirely on the client. ------8<------8<------8<------8<------ Am I right? If so, this is quite huge violation. Much much bigger than some state of SESSION_ID/TOKEN. Would caches/proxies work well with current design? Jaroslav Henner.

2 1

[Engine-devel] Testing queries
by Allon Mureinik 11 Jun '12

11 Jun '12

Hi guys, following some questions from last week regarding writing unit-tests for query objects, I whipped up this quick wiki page: http://ovirt.org/wiki/Testing_Queries Enjoy, Allon

1 0

[Engine-devel] Do we need genericApi project?
by Michael Kublin 10 Jun '12

10 Jun '12

Hi, I found that we have a ovirt-engine/frontend/api/genericapi project, which is for my opinion is not at use any more. If there are any reason that we want to keep it , maybe someone using it and I missed these? Thanks Michael

5 6

[Engine-devel] [ovirt-engine-sdk] Simplify the process of the RSDL code generation
by ShaoHe Feng 10 Jun '12

10 Jun '12

This is a multi-part message in MIME format. --------------060000080308030607050901 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, Now I'm using the code generation suites of ovirt-engine-sdk, I find it is very troublesome. IMO, we can simplify the process. And I want to engaged in it. there are two tools parse the api.xsd and generate the params.py code. They are generateds_gui.py and generateDS.py. but there still some code can not be generate by these tools. now we should add these codes manually. the not NOT_GENERATED codes are as follow in the current params.py code: 1. import python module 2. a new attribute of GeneratedsSuper class 3. modify the get_root_tag function. 4. modify the parseString function to shut up the stdout. 5. _rootClassMap 6 . _elementToClassMap 7. findRootClass And I have two ideas about the code generation. For we should not modify the generateDS.py tools. But we can improve it. I think the 1, 2, 3, 7, can be hard-code, and 4, 5 and 6 can be configured. So I want to add an configure file to tell how to add the extra code that are not generated by generateDS.py tools. And new python program, as extension of generateDS.py to read the configure file and generate these codes. Or without the configure file, just make the new python program that supports an interactive commands. --------------060000080308030607050901 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi all, Now I'm using the code generation suites of ovirt-engine-sdk, I find it is very troublesome. IMO,  we can simplify the process. And I want to engaged in it. there are two tools parse the api.xsd and generate the params.py code.  They are generateds_gui.py and generateDS.py. but there still some code can not be generate by these tools. now we should add these codes manually. the not NOT_GENERATED codes are as follow in the current  params.py code: 1.  import python module 2.  a new attribute of GeneratedsSuper class 3.  modify the get_root_tag function. 4.  modify the parseString function to shut up the stdout. 5.  _rootClassMap 6 . _elementToClassMap 7. findRootClass And I have two ideas about the code generation. For we should not modify the generateDS.py tools.  But we can improve it. I think the 1, 2, 3, 7, can be hard-code, and 4, 5 and 6 can be configured. So I want to add an configure file to tell how to add the extra code that are not generated  by generateDS.py tools. And  new python program, as extension of generateDS.py to read the configure file and generate these codes. Or without the configure file, just make the new python program that supports an interactive commands. <span style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 24px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color: rgb(245, 245, 245); display: inline !important; float: none; "> </body> </html> --------------060000080308030607050901--

3 12

Re: [Engine-devel] Ovirt on Fedora17
by Gianluca Cecchi 08 Jun '12

08 Jun '12

On Wed Jun 6 12:07:55 EDT 2012 Oved Ourfalli wrote: > Hey, > > You should really send such question to engine-devel, as someone might have encountered such an issue, so there might be a solution for that. > Can you also attach the vdsm.log file (in the host, under the directory /var/log/vdsm/vdsm.log). > > Thank you, > Oved > >> From: ovirt at qip.ru >> To: "Oved Ourfalli" <ovedo at redhat.com> >> Sent: Wednesday, June 6, 2012 5:55:44 PM >> Subject: Re: Re: Ovirt on Fedora17 >> >> I use rpms from >> >> http:// jenkins .ovirt.org/job/ovirt_engine_create_ rpms >> /lastSuccessfulBuild/artifact/output/*zip*/output.zip Hello, I'm going to test ovrit on F17 too (both as oVirt-engine server and oVirt node). Based on http://fedoraproject.org/wiki/Features/oVirt I supposed we don't need special repo any more and we can install ovirt-engine and dependencies form default F17 repos... Is it so? Or should I enable any particular repo as in F16? Thanks in advance Gianluca

4 7

[Engine-devel] quantum-ovirt integration meeting summary
by Livnat Peer 07 Jun '12

07 Jun '12

Hi All, This is a summary of the first quantum-oVirt integration meeting. In the meeting Garry Kotton started presenting his proposal for the integration, for more details on his proposal look in - http://www.ovirt.org/wiki/Quantum_and_oVirt We did not cover much of the wiki as some question arose: * What is the end goal of the integration? is it to replace the current network configuration implementation in oVirt by quantum or have them side by side. - we need to remember non-VM networks (like storage and migration networks) * Will oVirt use multiple quantum instances, one per technology, or will oVirt use a single quantum instance that should support multiple plug-ins (not supported in Quantum ATM) * We'll oVirt support a mix of different technologies in a DC, Cluster, host? - Can we assume homogeneous clusters for the sake of simplicity (in a single cluster we'll support either open Vswitch or UCSM or ..) - Logical Network is defined in the scope of a data center, that means we need to maintain layer 2 connectivity and within a cluster we need to guarantee VM live migration (does libvirt abstract it for us?) other notes - * The UUIDs that are returned by Quantum will be managed by oVirt and for a single network implemented in two different technologies in quantum oVirt will be responsible to sync the different IDs. * The integration should be as seamless as possible to the user of oVirt * support of existing VLAN in quantum should be introduces in quantum in a 3-4 weeks time-frame Comments are welcomed, I'll schedule a follow up next week. Thanks, Livnat

3 2

[Engine-devel] Improve classpath building
by Juan Hernandez 07 Jun '12

07 Jun '12

Hello all, I would like to propose an improvement in the way we build class-paths in the tools associated to the engine. At the moment we have at least two different ways to build classpaths: 1. Hard coded in the scripts, with maybe some variables: CP=$EAR_LIB/engine-encryptutils.jar:$EAR_LIB/engine-compat.jar:... This depends a lot on where we place the jar files, and we need to place them in different places in different environments if we want to adhere to common packaging practices. 2. Use the build-classpath script: CP=`build-classpath engine-encryptutils engine-compat ...` This depends less on the place we put them, but it doesn't work in development environments where some jars are not installed to the proper system locations. None of these is good for all environments. I would like to replace this classpath building logic with an script that performs the task in an smarter way and that works in all our environments (production, development, Fedora, RHEL, etc). My proposal is to create a "engine-java" script that we should use always when invoking java programs. This script will receive the same parameters that the "java" launcher receives, but the "-cp" or "-classpath" options will contain not the absolute name of the jar files, but just a simple jar name instead, something like "commons-logging", "commons-codec" or "engineencryptutils". The script will extract the "-cp" or "-classpath" options given and use them to do a search of the jar files in the locations where they can be in different environments: /usr/share/java /usr/share/java/ovirt-engine /usr/share/ovirt-engine/engine.ear /usr/share/ovirt-engine/engine.ear/lib <your jboss development installation>/engine.ear <your jboss development installation>/engine.ear/lib In addition the script will check that all the give jar files exist and will abort the execution if any of them is missing. Find attached the initial version of the proposed script. Let me know what you think. 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.

3 7

[Engine-devel] Duplicate LdapProviderType and LdapVendorNameEnum reappear.
by snmishra＠linux.vnet.ibm.com 07 Jun '12

07 Jun '12

Hi, As part of http://gerrit.ovirt.org/#/c/4727/ patch, we had removed duplicate classes for LdapProviderType and LdapVendorNameEnum. But I noticed that they have reappeared upstream. Is it intentional or accidental? Thanks Sharad Mishra IBM

2 1