May 2012 - Devel - oVirt List Archives

[Engine-devel] RFC: Writeup on VDSM-libstoragemgmt integration
by Deepak C Shetty 26 Jun '12

26 Jun '12

Hello All, I have a draft write-up on the VDSM-libstoragemgmt integration. I wanted to run this thru' the mailing list(s) to help tune and crystallize it, before putting it on the ovirt wiki. I have run this once thru Ayal and Tony, so have some of their comments incorporated. I still have few doubts/questions, which I have posted below with lines ending with '?' Comments / Suggestions are welcome & appreciated. thanx, deepak [Ccing engine-devel and libstoragemgmt lists as this stuff is relevant to them too] -------------------------------------------------------------------------------------------------------------- 1) Background: VDSM provides high level API for node virtualization management. It acts in response to the requests sent by oVirt Engine, which uses VDSM to do all node virtualization related tasks, including but not limited to storage management. libstoragemgmt aims to provide vendor agnostic API for managing external storage array. It should help system administrators utilizing open source solutions have a way to programmatically manage their storage hardware in a vendor neutral way. It also aims to facilitate management automation, ease of use and take advantage of storage vendor supported features which improve storage performance and space utilization. Home Page: http://sourceforge.net/apps/trac/libstoragemgmt/ libstoragemgmt (LSM) today supports C and python plugins for talking to external storage array using SMI-S as well as native interfaces (eg: netapp plugin ) Plan is to grow the SMI-S interface as needed over time and add more vendor specific plugins for exploiting features not possible via SMI-S or have better alternatives than using SMI-S. For eg: Many of the copy offload features require to use vendor specific commands, which justifies the need for a vendor specific plugin. 2) Goals: 2a) Ability to plugin external storage array into oVirt/VDSM virtualization stack, in a vendor neutral way. 2b) Ability to list features/capabilities and other statistical info of the array 2c) Ability to utilize the storage array offload capabilities from oVirt/VDSM. 3) Details: LSM will sit as a new repository engine in VDSM. VDSM Repository Engine WIP @ http://gerrit.ovirt.org/#change,192 Current plan is to have LSM co-exist with VDSM on the virtualization nodes. *Note : 'storage' used below is generic. It can be a file/nfs-export for NAS targets and LUN/logical-drive for SAN targets. VDSM can use LSM and do the following... - Provision storage - Consume storage 3.1) Provisioning Storage using LSM Typically this will be done by a Storage administrator. oVirt/VDSM should provide storage admin the - ability to list the different storage arrays along with their types (NAS/SAN), capabilities, free/used space. - ability to provision storage using any of the array capabilities (eg: thin provisioned lun or new NFS export ) - ability to manage the provisioned storage (eg: resize/delete storage) Once the storage is provisioned by the storage admin, VDSM will have to refresh the host(s) for them to be able to see the newly provisioned storage. 3.1.1) Potential flows: Mgmt -> vdsm -> lsm: create LUN + LUN Mapping / Zoning / whatever is needed to make LUN available to list of hosts passed by mgmt Mgmt -> vdsm: getDeviceList (refreshes host and gets list of devices) Repeat above for all relevant hosts (depending on list passed earlier, mostly relevant when extending an existing VG) Mgmt -> use LUN in normal flows. 3.1.2) How oVirt Engine will know which LSM to use ? Normally the way this works today is that user can choose the host to use (default today is SPM), however there are a few flows where mgmt will know which host to use: 1. extend storage domain (add LUN to existing VG) - Use SPM and make sure *all* hosts that need access to this SD can see the new LUN 2. attach new LUN to a VM which is pinned to a specific host - use this host 3. attach new LUN to a VM which is not pinned - use a host from the cluster the VM belongs to and make sure all nodes in cluster can see the new LUN Flows for which there is no clear candidate (Maybe we can use the SPM host itself which is the default ?) 1. create a new disk without attaching it to any VM 2. create a LUN for a new storage domain 3.2) Consuming storage using LSM Typically this will be done by a virtualization administrator oVirt/VDSM should allow virtualization admin to - Create a new storage domain using the storage on the array. - Be able to specify whether VDSM should use the storage offload capability (default) or override it to use its own internal logic. 4) VDSM potential changes: 4.1) How to represent a VM disk, 1 LUN = 1 VMdisk or 1 LV = 1 VMdisk ? which bring another question...1 array == 1 storage domain OR 1 LUN/nfs-export on the array == 1 storage domain ? Pros & Cons of each... 1 array == 1 storage domain - Each new vmdisk (aka volume) will be a new lun/file on the array. - Easier to exploit offload capabilities, as they are available at the LUN/File granularity - Will there be any issues where there will be too many LUNs/Files ... any maxluns limit on linux hosts that we might hit ? -- VDSM has been tested with 1K LUNs and it worked fine - ayal - Storage array limitations on the number of LUNs can be a downside here. - Would it be ok to share the array for hosting another storage domain if need be ? -- Provided the existing domain is not utilising all of the free space -- We can create new LUNs and hand it over to anyone needed ? -- Changes needed in VDSM to work with raw LUNs, today it only has support for consuming LUNs via VG/LV. 1 LUN/nfs-export on the array == 1 storage domain - How to represent a new vmdisk (aka vdsm volume) if its a LUN provisioned using SAN target ? -- Will it be VG/LV as is done today for block domains ? -- If yes, then it will be difficult to exploit offload capabilities, as they are at LUN level, not at LV level. - Each new vmdisk will be a new file on the nfs-export, assuming offload capability is available at the file level, so this should work for NAS targets ? - Can use the storage array for hosting multiple storage domains. -- Provision one more LUN and use it for another storage domain if need be. - VDSM already supports this today, as part of block storage domains for LUNs case. Note that we will allow user to do either one of the two options above, depending on need. 4.2) Storage domain metadata will also include the features/capabilities of the storage array as reported by LSM. - Capabilities (taken via LSM) will be stored in the domain metadata during storage domain create flow. - Need changes in oVirt engine as well ( see 'oVirt Engine potential changes' section below ) 4.3) VDSM to poll LSM for array capabilities on a regular basis ? Per ayal: - If we have a 'storage array' entity in oVirt Engine (see 'oVirt Engine potential changes' section below ) then we can have a 'refresh capabilities' button/verb. - We can periodically query the storage array. - Query LSM before running operations (sounds redundant to me, but if it's cheap enough it could be simplest). Probably need a combination of 1+2 (query at very low frequency - 1/hour or 1/day + refresh button) 5) oVirt Engine potential changes - as described by ayal : - We will either need a new 'storage array' entity in engine to keep credentials, or, in case of storage array as storage domain, just keep this info as part of the domain at engine level. - Have a 'storage array' entity in oVirt Engine to support 'refresh capabilities' as a button/verb. - When user during storage provisioning, selects a LUN exported from a storage array (via LSM), the oVirt Engine would know from then onwards that this LUN is being served via LSM. It would then be able to query the capabilities of the LUN and show it to the virt admin during storage consumption flow. 6) Potential flows: - Create snapshot flow -- VDSM will check the snapshot offload capability in the domain metadata -- If available, and override is not configured, it will use LSM to offload LUN/File snapshot -- If override is configured or capability is not available, it will use its internal logic to create snapshot (qcow2). - Copy/Clone vmdisk flow -- VDSM will check the copy offload capability in the domain metadata -- If available, and override is not configured, it will use LSM to offload LUN/File copy -- If override is configured or capability is not available, it will use its internal logic to create snapshot (eg: dd cmd in case of LUN). 7) LSM potential changes: - list features/capabilities of the array. Eg: copy offload, thin prov. etc. - list containers (aka pools) (present in LSM today) - Ability to list different types of arrays being managed, their capabilities and used/free space - Ability to create/list/delete/resize volumes ( LUN or exports, available in LSM as of today) - Get monitoring info with object (LUN/snapshot/volume) as optional parameter for specific info. eg: container/pool free/used space, raid type etc. Need to make sure above info is listed in a coherent way across arrays (number of LUNs, raid type used? free/total per container/pool, per LUN?. Also need I/O statistics wherever possible.

10 24

[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

[Engine-devel] LOCALFS path validation
by Amador pahim 04 Jun '12

04 Jun '12

This is a multi-part message in MIME format. --------------040303020501050109020008 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello, I'm starting to know the engine code. I chose a little unstandardized behaviour to follow through the devel process. I have a patch and I'd like to know if you fell relevant to correct this issue: - Description: Adding a LOCAL storage [1], webadmin does not validate path against regex, sendind the invalid path (with final slash) to vdsm [2] [3]. But, adding a NFS storage, the path is validated before contacting vdsm [4] avoiding extra vdsm processing and quickly/clearly informing user about what's wrong. - Expected result: Same behaviour to NFS and LOCALFS storage path validation. Validate LOCALFS path in webadmin before send it to vdsm [5]. - Newbie doubt: Wouldn't be better to validate the both local and nfs path on the backend, achieving all user interfaces/APIs? [1] - https://picasaweb.google.com/lh/photo/FWNiou2Y12GZO3AjfCH6K7QAv8cs6edaj3fEc… [2] - https://picasaweb.google.com/lh/photo/Pof6Z8ohgQAkRTDpEJKG-LQAv8cs6edaj3fEc… [3] - https://gist.github.com/2762656 [4] - https://picasaweb.google.com/lh/photo/Fd3zWegWE0T5C2tDo_tPZrQAv8cs6edaj3fEc… [5] - https://picasaweb.google.com/lh/photo/PgzYrZHkkvm-WtFk_UFZLrQAv8cs6edaj3fEc… I look forward to hearing your comments. Best Regards, -- Pahim --------------040303020501050109020008 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"> Hello, I'm starting to know the engine code. I chose a little unstandardized behaviour to follow through the devel process. I have a patch and I'd like to know if you fell relevant to correct this issue: - Description: Adding a LOCAL storage [1], webadmin does not validate path against regex, sendind the invalid path (with final slash) to vdsm [2] [3]. But, adding a NFS storage, the path is validated before contacting vdsm [4] avoiding extra vdsm processing and quickly/clearly informing user about what's wrong. - Expected result: Same behaviour to NFS and LOCALFS storage path validation. Validate LOCALFS path in webadmin before send it to vdsm [5]. - Newbie doubt: Wouldn't be better to validate the both local and nfs path on the backend, achieving all user interfaces/APIs? [1] - <a class="moz-txt-link-freetext" href="https://picasaweb.google.com/lh/photo/FWNiou2Y12GZO3AjfCH6K7QAv8cs6edaj3fEc…">https://picasaweb.google.com/lh/photo/FWNiou2Y12GZO3AjfCH6K7QAv8cs6edaj3fEc…</a> [2] - <a class="moz-txt-link-freetext" href="https://picasaweb.google.com/lh/photo/Pof6Z8ohgQAkRTDpEJKG-LQAv8cs6edaj3fEc…">https://picasaweb.google.com/lh/photo/Pof6Z8ohgQAkRTDpEJKG-LQAv8cs6edaj3fEc…</a> [3] - <a class="moz-txt-link-freetext" href="https://gist.github.com/2762656">https://gist.github.com/2762656</a> [4] - <a class="moz-txt-link-freetext" href="https://picasaweb.google.com/lh/photo/Fd3zWegWE0T5C2tDo_tPZrQAv8cs6edaj3fEc…">https://picasaweb.google.com/lh/photo/Fd3zWegWE0T5C2tDo_tPZrQAv8cs6edaj3fEc…</a> [5] - <a class="moz-txt-link-freetext" href="https://picasaweb.google.com/lh/photo/PgzYrZHkkvm-WtFk_UFZLrQAv8cs6edaj3fEc…">https://picasaweb.google.com/lh/photo/PgzYrZHkkvm-WtFk_UFZLrQAv8cs6edaj3fEc…</a> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> I look forward to hearing your comments. Best Regards, -- Pahim </body> </html> --------------040303020501050109020008--

4 6

[Engine-devel] Maven 3 here we come!
by Doron Fediuck 03 Jun '12

03 Jun '12

Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed. For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended. Talking about advanced features, an interesting challenge is feedback on parallel builds [2]. So whoever wants to try it out and report if it improves run time without breaking anything, will be appreciated. Happy migration! [1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html [2] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html -- /d "Email returned to sender -- insufficient voltage."

6 9

Re: [Engine-devel] [oVirt Jenkins] ovirt_engine_find_bugs - Build # 915 - Still Unstable!
by Eyal Edri 01 Jun '12

01 Jun '12

FYI, These set of patches introduced new HIGH findbugs warnings: http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/913/changes: webadmin: Gluster Volume Options - populating from help xml (details) webadmin: Gluster Brick sub tab - removing columns (details) webadmin: Support for mode specific Tabs and Sub Tabs (details) restapi: Gluster Resources Implementation classes (details) restapi: RSDL metadata for gluster related REST api (details) restapi: Gluster Volumes Collection implementation (details) engine: Add ID fields to gluster brick and option (details) webadmin: Gluster Volume - add bricks enabling (#823284) (details) webadmin: Gluster Volume - upadting actions (#823273) (details) webadmin: Gluster Volume - validations fixed (#823277) (details) bugs appear to be in GlusterVolumeEntity.java: http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/913/findbugsResult/HIGH… http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/913/findbugsResult/HIGH… Please review and handle, Eyal Edri oVirt Infra Team ----- Original Message ----- > From: "Jenkins oVirt Server" <jenkins(a)ovirt.org> > To: eedri(a)redhat.com, engine-patches(a)ovirt.org, oliel(a)redhat.com, yzaslavs(a)redhat.com, amureini(a)redhat.com, > dfediuck(a)redhat.com > Sent: Tuesday, May 22, 2012 12:11:33 PM > Subject: [oVirt Jenkins] ovirt_engine_find_bugs - Build # 915 - Still Unstable! > > Project: http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/ > Build: http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/915/ > Build Number: 915 > Build Status: Still Unstable > Triggered By: Started by upstream project "ovirt_engine" build number > 1,240 > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #913 > [gchaplik] webadmin: Gluster Volume Options - populating from help > xml > > [gchaplik] webadmin: Gluster Brick sub tab - removing columns > > [gchaplik] webadmin: Support for mode specific Tabs and Sub Tabs > > [sanjal] restapi: Gluster Resources Implementation classes > > [sanjal] restapi: RSDL metadata for gluster related REST api > > [sanjal] restapi: Gluster Volumes Collection implementation > > [sanjal] engine: Add ID fields to gluster brick and option > > [gchaplik] webadmin: Gluster Volume - add bricks enabling (#823284) > > [gchaplik] webadmin: Gluster Volume - upadting actions (#823273) > > [gchaplik] webadmin: Gluster Volume - validations fixed (#823277) > > > Changes for Build #914 > [emesika] core:dbfunctions.sh script needs to be compatible with DWH > > [mpastern] restapi: fix rsdl regression > > > Changes for Build #915 > [dfediuck] core: Use same ids for artifacts and plugins > > [amureini] core: Allow admin permissions in user views > > [amureini] core: Roles commands cleanup > > [amureini] core: Cleanup Permissions Commands > > [amureini] core: Roles commands - use the cached getRole() > > [amureini] core: is_inheritable property to MLA entities > > > > > ----------------- > Failed Tests: > ----------------- > No tests ran. > > ------------------ > Build Log: > ------------------ > [...truncated 4148 lines...] > [INFO] Assembling webapp [userportal] in > [/ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/userportal-gwtp/target/userportal-3.1.0-0001] > [INFO] Processing war project > [INFO] Copying webapp resources > [/ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/userportal-gwtp/src/main/webapp] > [INFO] Webapp assembled in [147 msecs] > [INFO] Building war: > /ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/userportal-gwtp/target/userportal-3.1.0-0001.war > [INFO] WEB-INF/web.xml already added, skipping > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ > userportal --- > [INFO] Installing > /ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/userportal-gwtp/target/userportal-3.1.0-0001.war > to > /home/jenkins/workspace/ovirt_engine_find_bugs/.repository/org/ovirt/engine/ui/userportal/3.1.0-0001/userportal-3.1.0-0001.war > [INFO] Installing > /ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/userportal-gwtp/pom.xml > to > /home/jenkins/workspace/ovirt_engine_find_bugs/.repository/org/ovirt/engine/ui/userportal/3.1.0-0001/userportal-3.1.0-0001.pom > [INFO] > [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default-cli) @ > userportal --- > [INFO] Fork Value is true > [INFO] > [INFO] --- maven-checkstyle-plugin:2.6:check (default) @ webadmin --- > [INFO] Starting audit... > Audit done. > > [INFO] > [INFO] --- maven-resources-plugin:2.5:testResources > (default-testResources) @ webadmin --- > [debug] execute contextualize > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > /ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/webadmin/src/test/resources > [INFO] > [INFO] --- maven-compiler-plugin:2.3.2:testCompile > (default-testCompile) @ webadmin --- > [INFO] No sources to compile > [INFO] > [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ webadmin > --- > [INFO] Tests are skipped. > [INFO] > [INFO] --- maven-war-plugin:2.1.1:war (default-war) @ webadmin --- > [INFO] Packaging webapp > [INFO] Assembling webapp [webadmin] in > [/ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/webadmin/target/webadmin-3.1.0-0001] > [INFO] Processing war project > [INFO] Copying webapp resources > [/ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/webadmin/src/main/webapp] > [INFO] Webapp assembled in [147 msecs] > OpenJDK 64-Bit Server VM warning: CodeCache is full. Compiler has > been disabled. > OpenJDK 64-Bit Server VM warning: Try increasing the code cache size > using -XX:ReservedCodeCacheSize= > [INFO] Building war: > /ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/webadmin/target/webadmin-3.1.0-0001.war > [INFO] WEB-INF/web.xml already added, skipping > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ > webadmin --- > [INFO] Installing > /ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/webadmin/target/webadmin-3.1.0-0001.war > to > /home/jenkins/workspace/ovirt_engine_find_bugs/.repository/org/ovirt/engine/ui/webadmin/3.1.0-0001/webadmin-3.1.0-0001.war > [INFO] Installing > /ephemeral0/ovirt_engine_find_bugs/frontend/webadmin/modules/webadmin/pom.xml > to > /home/jenkins/workspace/ovirt_engine_find_bugs/.repository/org/ovirt/engine/ui/webadmin/3.1.0-0001/webadmin-3.1.0-0001.pom > [INFO] > [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default-cli) @ > webadmin --- > [INFO] Fork Value is true > [java] Warnings generated: 14 > [INFO] Done FindBugs Analysis.... > [java] Warnings generated: 56 > [INFO] Done FindBugs Analysis.... > [INFO] > [INFO] > ------------------------------------------------------------------------ > [INFO] Building oVirt Server EAR 3.1.0-0001 > [INFO] > ------------------------------------------------------------------------ > [WARNING] The POM for > org.codehaus.mojo:gwt-maven-plugin:jar:1.3.2.google is missing, no > dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.codehaus.mojo:gwt-maven-plugin:1.3.2.google: Plugin > org.codehaus.mojo:gwt-maven-plugin:1.3.2.google or one of its > dependencies could not be resolved: Failed to read artifact > descriptor for org.codehaus.mojo:gwt-maven-plugin:jar:1.3.2.google > [WARNING] > ***************************************************************** > [WARNING] * Your build is requesting parallel execution, but project > * > [WARNING] * contains the following plugin(s) that are not marked as > * > [WARNING] * @threadSafe to support parallel building. > * > [WARNING] * While this /may/ work fine, please look for plugin > updates * > [WARNING] * and/or request plugins be made thread-safe. > * > [WARNING] * If reporting an issue, report it against the plugin in > * > [WARNING] * question, not against maven-core > * > [WARNING] > ***************************************************************** > [WARNING] The following plugins are not marked @threadSafe in oVirt > Server EAR: > [WARNING] org.apache.maven.plugins:maven-dependency-plugin:2.1 > [WARNING] > ***************************************************************** > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ > engine-server-ear --- > [INFO] Deleting /ephemeral0/ovirt_engine_find_bugs/ear/target > [INFO] > [INFO] --- maven-ear-plugin:2.6:generate-application-xml > (default-generate-application-xml) @ engine-server-ear --- > [INFO] Generating application.xml > [INFO] > [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) > @ engine-server-ear --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > /ephemeral0/ovirt_engine_find_bugs/ear/src/main/java > [INFO] skip non existing resourceDirectory > /ephemeral0/ovirt_engine_find_bugs/ear/src/main/resources > [INFO] > [INFO] --- maven-ear-plugin:2.6:ear (default-ear) @ engine-server-ear > --- > [INFO] Copying artifact[jar:org.ovirt.engine.core:common:3.1.0-0001] > to[lib/engine-common.jar] > [INFO] Copying artifact[jar:org.ovirt.engine.core:compat:3.1.0-0001] > to[lib/engine-compat.jar] > [INFO] Copying artifact[jar:org.ovirt.engine.core:dal:3.1.0-0001] > to[lib/engine-dal.jar] > [INFO] Copying artifact[jar:org.ovirt.engine.core:utils:3.1.0-0001] > to[lib/engine-utils.jar] > [INFO] Copying > artifact[jar:org.ovirt.engine.core:engineencryptutils:3.1.0-0001] > to[lib/engine-encryptutils.jar] > [INFO] Copying > artifact[jar:org.ovirt.engine.core:vdsbroker:3.1.0-0001] > to[lib/engine-vdsbroker.jar] > [INFO] Copying > artifact[war:org.ovirt.engine.core:root-war:3.1.0-0001] to[root.war] > (unpacked) > [INFO] Copying artifact[war:org.ovirt.engine.ui:rmw-war:3.1.0-0001] > to[ovirtengineweb.war] (unpacked) > [INFO] Copying artifact[war:org.ovirt.engine.ui:rm-war:3.1.0-0001] > to[ovirtengine.war] (unpacked) > [INFO] Copying > artifact[war:org.ovirt.engine.ui:components-war:3.1.0-0001] > to[components.war] (unpacked) > [INFO] Copying > artifact[war:org.ovirt.engine.api:restapi-webapp:3.1.0-0001] > to[restapi.war] (unpacked) > [INFO] Copying > artifact[war:org.ovirt.engine.ui:userportal:3.1.0-0001] > to[userportal.war] (unpacked) > [INFO] Copying artifact[war:org.ovirt.engine.ui:webadmin:3.1.0-0001] > to[webadmin.war] (unpacked) > [INFO] Copying > artifact[ejb:org.ovirt.engine.ui:genericapi:3.1.0-0001] > to[engine-genericapi.jar] (unpacked) > [INFO] Copying > artifact[ejb:org.ovirt.engine.core:scheduler:3.1.0-0001] > to[engine-scheduler.jar] (unpacked) > [INFO] Copying artifact[ejb:org.ovirt.engine.core:bll:3.1.0-0001] > to[engine-bll.jar] (unpacked) > [INFO] Copying artifact[jar:commons-codec:commons-codec:1.4] > to[lib/commons-codec-1.4.jar] > [INFO] Copying > artifact[jar:org.hibernate:hibernate-validator:4.0.2.GA] > to[lib/hibernate-validator-4.0.2.GA.jar] > [INFO] Copying artifact[jar:javax.validation:validation-api:1.0.0.GA] > to[lib/validation-api-1.0.0.GA.jar] > [INFO] Copying artifact[jar:org.slf4j:slf4j-api:1.5.6] > to[lib/slf4j-api-1.5.6.jar] > [INFO] Copying artifact[jar:javax.xml.bind:jaxb-api:2.1] > to[lib/jaxb-api-2.1.jar] > [INFO] Copying artifact[jar:javax.xml.stream:stax-api:1.0-2] > to[lib/stax-api-1.0-2.jar] > [INFO] Copying artifact[jar:javax.activation:activation:1.1] > to[lib/activation-1.1.jar] > [INFO] Copying artifact[jar:com.sun.xml.bind:jaxb-impl:2.1.3] > to[lib/jaxb-impl-2.1.3.jar] > [INFO] Copying > artifact[jar:org.hibernate:hibernate-annotations:3.4.0.GA] > to[lib/hibernate-annotations-3.4.0.GA.jar] > [INFO] Copying artifact[jar:org.hibernate:ejb3-persistence:1.0.2.GA] > to[lib/ejb3-persistence-1.0.2.GA.jar] > [INFO] Copying > artifact[jar:org.hibernate:hibernate-commons-annotations:3.1.0.GA] > to[lib/hibernate-commons-annotations-3.1.0.GA.jar] > [INFO] Copying artifact[jar:org.hibernate:hibernate-core:3.3.0.SP1] > to[lib/hibernate-core-3.3.0.SP1.jar] > [INFO] Copying artifact[jar:antlr:antlr:2.7.6] > to[lib/antlr-2.7.6.jar] > [INFO] Copying artifact[jar:dom4j:dom4j:1.6.1] > to[lib/dom4j-1.6.1.jar] > [INFO] Copying artifact[jar:xml-apis:xml-apis:1.0.b2] > to[lib/xml-apis-1.0.b2.jar] > [INFO] Copying > artifact[jar:org.codehaus.jackson:jackson-mapper-asl:1.9.4] > to[lib/jackson-mapper-asl-1.9.4.jar] > [INFO] Copying > artifact[jar:org.codehaus.jackson:jackson-core-asl:1.9.4] > to[lib/jackson-core-asl-1.9.4.jar] > [INFO] Copying > artifact[jar:org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:1.0.0.Final] > to[lib/jboss-interceptors-api_1.1_spec-1.0.0.Final.jar] > [INFO] Copying > artifact[jar:org.ovirt.engine.core:engine-tools-common:3.1.0-0001] > to[lib/engine-tools-common-3.1.0-0001.jar] > [INFO] Copying > artifact[jar:commons-beanutils:commons-beanutils:1.8.2] > to[lib/commons-beanutils-1.8.2.jar] > [INFO] Copying artifact[jar:com.jcraft:jsch:0.1.42] > to[lib/jsch-0.1.42.jar] > [INFO] Copying artifact[jar:org.apache.mina:mina-core:2.0.1] > to[lib/mina-core-2.0.1.jar] > [INFO] Copying artifact[jar:org.apache.sshd:sshd-core:0.6.0] > to[lib/sshd-core-0.6.0.jar] > [INFO] Copying artifact[jar:commons-lang:commons-lang:2.4] > to[lib/commons-lang-2.4.jar] > [INFO] Copying artifact[jar:org.apache.xmlrpc:xmlrpc-client:3.1.3] > to[lib/xmlrpc-client-3.1.3.jar] > [INFO] Copying artifact[jar:org.apache.xmlrpc:xmlrpc-common:3.1.3] > to[lib/xmlrpc-common-3.1.3.jar] > [INFO] Copying > artifact[jar:org.apache.ws.commons.util:ws-commons-util:1.0.2] > to[lib/ws-commons-util-1.0.2.jar] > [INFO] Copying > artifact[jar:org.springframework:spring-jdbc:2.5.6.SEC02] > to[lib/spring-jdbc-2.5.6.SEC02.jar] > [INFO] Copying > artifact[jar:org.springframework:spring-tx:2.5.6.SEC02] > to[lib/spring-tx-2.5.6.SEC02.jar] > [INFO] Copying > artifact[jar:org.springframework.ldap:spring-ldap-core:1.3.0.RELEASE] > to[lib/spring-ldap-core-1.3.0.RELEASE.jar] > [INFO] Copying > artifact[jar:commons-httpclient:commons-httpclient:3.1] > to[lib/commons-httpclient-3.1.jar] > [INFO] Copying artifact[jar:org.quartz-scheduler:quartz:2.1.2] > to[lib/quartz-2.1.2.jar] > [INFO] Copying artifact[jar:c3p0:c3p0:0.9.1.1] > to[lib/c3p0-0.9.1.1.jar] > [INFO] Copying > artifact[jar:org.ovirt.engine.core:searchbackend:3.1.0-0001] > to[lib/searchbackend-3.1.0-0001.jar] > [INFO] Copying > artifact[jar:commons-collections:commons-collections:3.1] > to[lib/commons-collections-3.1.jar] > [INFO] Copying > artifact[jar:org.springframework:spring-core:2.5.6.SEC02] > to[lib/spring-core-2.5.6.SEC02.jar] > [INFO] Copying > artifact[jar:org.springframework:spring-beans:2.5.6.SEC02] > to[lib/spring-beans-2.5.6.SEC02.jar] > [INFO] Copying > artifact[jar:org.springframework:spring-context:2.5.6.SEC02] > to[lib/spring-context-2.5.6.SEC02.jar] > [INFO] Copying artifact[jar:aopalliance:aopalliance:1.0] > to[lib/aopalliance-1.0.jar] > [INFO] Copying > artifact[jar:org.springframework:spring-agent:2.5.6.SEC02] > to[lib/spring-agent-2.5.6.SEC02.jar] > [INFO] Copying > artifact[jar:org.springframework:spring-aop:2.5.6.SEC02] > to[lib/spring-aop-2.5.6.SEC02.jar] > [INFO] Copy ear sources to > /ephemeral0/ovirt_engine_find_bugs/ear/target/engine > [INFO] Could not find manifest file: > /ephemeral0/ovirt_engine_find_bugs/ear/target/engine/META-INF/MANIFEST.MF > - Generating one > [INFO] Building jar: > /ephemeral0/ovirt_engine_find_bugs/ear/target/engine.ear > [INFO] > [INFO] --- maven-dependency-plugin:2.1:copy (copy-quartz-jar) @ > engine-server-ear --- > [INFO] Configured Artifact: org.quartz-scheduler:quartz:2.1.2:jar > [INFO] Copying quartz-2.1.2.jar to > /ephemeral0/ovirt_engine_find_bugs/ear/target/quartz/quartz-2.1.2.jar > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ > engine-server-ear --- > [INFO] Installing > /ephemeral0/ovirt_engine_find_bugs/ear/target/engine.ear to > /home/jenkins/workspace/ovirt_engine_find_bugs/.repository/org/ovirt/engine/engine-server-ear/3.1.0-0001/engine-server-ear-3.1.0-0001.ear > [INFO] Installing /ephemeral0/ovirt_engine_find_bugs/ear/pom.xml to > /home/jenkins/workspace/ovirt_engine_find_bugs/.repository/org/ovirt/engine/engine-server-ear/3.1.0-0001/engine-server-ear-3.1.0-0001.pom > [INFO] > [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default-cli) @ > engine-server-ear --- > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] oVirt Engine Root Project ......................... SUCCESS > [11.175s] > [INFO] oVirt Build Tools root ............................ SUCCESS > [0.154s] > [INFO] oVirt checkstyle .................................. SUCCESS > [2.925s] > [INFO] oVirt Checkstyle Checks ........................... SUCCESS > [32.541s] > [INFO] oVirt Modules - backend ........................... SUCCESS > [0.137s] > [INFO] oVirt Manager ..................................... SUCCESS > [0.633s] > [INFO] oVirt Modules - manager ........................... SUCCESS > [1.512s] > [INFO] CSharp Compatibility .............................. SUCCESS > [1:18.689s] > [INFO] Encryption Libraries .............................. SUCCESS > [42.599s] > [INFO] oVirt Tools ....................................... SUCCESS > [0.205s] > [INFO] oVirt Tools Common Library ........................ SUCCESS > [25.939s] > [INFO] Common Code ....................................... SUCCESS > [2:09.368s] > [INFO] Common utilities .................................. SUCCESS > [1:43.075s] > [INFO] Data Access Layer ................................. SUCCESS > [1:39.624s] > [INFO] engine beans ...................................... SUCCESS > [0.237s] > [INFO] engine scheduler bean ............................. SUCCESS > [40.875s] > [INFO] Vds broker ........................................ SUCCESS > [1:44.474s] > [INFO] Search Backend .................................... SUCCESS > [59.374s] > [INFO] Backend Logic @Service bean ....................... SUCCESS > [2:17.939s] > [INFO] oVirt RESTful API Backend Integration ............. SUCCESS > [0.154s] > [INFO] oVirt RESTful API interface ....................... SUCCESS > [0.315s] > [INFO] oVirt Engine API Definition ....................... SUCCESS > [1:32.846s] > [INFO] oVirt Engine API Commom Parent POM ................ SUCCESS > [0.328s] > [INFO] oVirt Engine API Common JAX-RS .................... SUCCESS > [58.151s] > [INFO] oVirt RESTful API Backend Integration Type Mappers SUCCESS > [1:29.592s] > [INFO] oVirt RESTful API Backend Integration JAX-RS Resources > SUCCESS [1:34.159s] > [INFO] oVirt RESTful API Backend Integration Webapp ...... SUCCESS > [12.297s] > [INFO] oVirt Engine Web Root ............................. SUCCESS > [33.235s] > [INFO] oVirt Configuration Tool .......................... SUCCESS > [46.202s] > [INFO] Notifier Service package .......................... SUCCESS > [0.143s] > [INFO] Notifier Service .................................. SUCCESS > [56.794s] > [INFO] Notifier Service Resources ........................ SUCCESS > [9.712s] > [INFO] oVirt Modules - frontend .......................... SUCCESS > [3.064s] > [INFO] oVirt APIs ........................................ SUCCESS > [1.472s] > [INFO] oVirt generic API ................................. SUCCESS > [32.572s] > [INFO] oVirt Modules - webadmin .......................... SUCCESS > [0.146s] > [INFO] oVirt Modules - ui ................................ SUCCESS > [0.250s] > [INFO] Extensions for GWT ................................ SUCCESS > [1:17.416s] > [INFO] UI Utils Compatibility (for UICommon) ............. SUCCESS > [47.857s] > [INFO] Frontend for GWT UI Projects ...................... SUCCESS > [47.153s] > [INFO] UICommon .......................................... SUCCESS > [3:17.484s] > [INFO] UICommonWeb ....................................... SUCCESS > [3:41.508s] > [INFO] oVirt GWT UI common infrastructure ................ SUCCESS > [1:44.412s] > [INFO] WebAdmin .......................................... SUCCESS > [3:28.888s] > [INFO] UserPortal ........................................ SUCCESS > [2:12.619s] > [INFO] oVirt WARs ........................................ SUCCESS > [0.134s] > [INFO] WPF Application Module ............................ SUCCESS > [8.143s] > [INFO] oVirt Web Application Module ...................... SUCCESS > [32.504s] > [INFO] Components Web Application Module ................. SUCCESS > [6.230s] > [INFO] oVirt Server EAR .................................. SUCCESS > [17.227s] > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 23:52.051s (Wall Clock) > [INFO] Finished at: Tue May 22 05:10:14 EDT 2012 > [INFO] Final Memory: 302M/781M > [INFO] > ------------------------------------------------------------------------ > [FINDBUGS] Collecting findbugs analysis files... > [FINDBUGS] Parsing 30 files in > /home/jenkins/workspace/ovirt_engine_find_bugs > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/beans/scheduler/target/findbugsXml.xml > of module with 1 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/beans/vdsbroker/target/findbugsXml.xml > of module with 0 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/bll/target/findbugsXml.xml > of module with 439 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/common/target/findbugsXml.xml > of module with 335 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/compat/target/findbugsXml.xml > of module with 71 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/dal/target/findbugsXml.xml > of module with 27 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/engineencryptutils/target/findbugsXml.xml > of module with 10 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/restapi/interface/common/jaxrs/target/findbugsXml.xml > of module with 18 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/restapi/interface/definition/target/findbugsXml.xml > of module with 1 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/restapi/jaxrs/target/findbugsXml.xml > of module with 23 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/restapi/types/target/findbugsXml.xml > of module with 10 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/root/target/findbugsXml.xml > of module with 5 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/searchbackend/target/findbugsXml.xml > of module with 13 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/utils/target/findbugsXml.xml > of module with 122 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/modules/vdsbroker/target/findbugsXml.xml > of module with 238 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/tools/engine-config/target/findbugsXml.xml > of module with 7 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/tools/engine-notifier/engine-notifier-service/target/findbugsXml.xml > of module with 11 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/backend/manager/tools/engine-tools-common/target/findbugsXml.xml > of module with 0 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/build-tools-root/ovirt-checkstyle-extension/target/findbugsXml.xml > of module with 1 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/api/genericapi/target/findbugsXml.xml > of module with 1 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/wars/rmw-war/target/findbugsXml.xml > of module with 0 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/webadmin/modules/frontend/target/findbugsXml.xml > of module with 21 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/webadmin/modules/gwt-common/target/findbugsXml.xml > of module with 65 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/webadmin/modules/gwt-extension/target/findbugsXml.xml > of module with 29 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/webadmin/modules/uicommon/target/findbugsXml.xml > of module with 420 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/webadmin/modules/uicommonweb/target/findbugsXml.xml > of module with 602 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/webadmin/modules/uicompat/target/findbugsXml.xml > of module with 40 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/webadmin/modules/userportal-gwtp/target/findbugsXml.xml > of module with 14 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/webadmin/modules/userportal/target/findbugsXml.xml > of module with 118 warnings. > [FINDBUGS] Successfully parsed file > /home/jenkins/workspace/ovirt_engine_find_bugs/frontend/webadmin/modules/webadmin/target/findbugsXml.xml > of module with 56 warnings. > [FINDBUGS] Computing warning deltas based on reference build #912 > [FINDBUGS] Using set difference to compute new warnings > Build step 'Publish FindBugs analysis results' changed build result > to UNSTABLE > Email was triggered for: Unstable > Sending email for trigger: Unstable > >

2 2

[Engine-devel] Build and run with Fedora 17 jboss-as packages
by Juan Hernandez 31 May '12

31 May '12

Hello, The changes required to build and run the engine using the jboss-as packages in Fedora 17 have been recently merged: http://gerrit.ovirt.org/4416 This means that from now on in order to install the RPMs you will need a Fedora 17 machine. In addition this also changes how the application server is used. We have been running the engine as an application deployed to the default instance of the application server. Starting now the engine will run a private instance of the application server owned by the user ovirt ovirt and managed by systemd, so please remember that you don't longer need/should start the jboss-as service, but the ovirt-engine systemd service: systemctl start ovirt-engine.service systemctl stop ovirt-engine.service The locations of the files/directories used by this private instance of the application server are also different: 1. You are probably familiar with the standalone.xml file. This is no longer used, we use the /etc/ovirt-engine/engine-service.xml instead. 2. The location of the engine.ear file is still the same (/usr/share/ovirt-engine/engine.ear), but the deployment marker file engine.ear.dodeploy is not created in the same directory. Instead of that a symlink to the engine.ear file is created in /var/lib/ovirt-engine/deployments directory and the engine.ear.dodeploy file is created there by the start/stop script. 3. Locations of log files are also slightly different. The main log file is still /var/log/ovirt-engine/engine.log, but the server.log file is no longer in the jboss-as directory, but in /var/log/ovirt-engine as well. In addition there is a /var/log/ovirt-engine/console.log file that stores the standard and error output of the engine. There are other changes, but probably less relevant to most of you. I made many tests, but I am sure that issues will appear, so please keep an eye on this and let me know of any issues you may encounter. Regards, Juan Hernandez

2 1

[Engine-devel] Shared Memory
by Amador Pahim 31 May '12

31 May '12

Hello, Not sure if it was already discussed, but I'd like to talk about oVirt "Shared Memory". Webadmin has the Shared Memory percent information in host general tab [1]. Initially, I thought that Shared Memory was the KSM de-duplication results. But comparing with my KSM stats, it does not make sense. My env: 3,5 GB virt-host. 6 identical VMs running with 1GB RAM each. Webadmin host details: Memory Sharing: Active Shared Memory: 0% KSM - How many shared pages are being used: $ cat /sys/kernel/mm/ksm/pages_sharing 109056 KSM - How many more sites are sharing them i.e. how much saved $ cat /sys/kernel/mm/ksm/pages_sharing 560128 Converting to Mbytes: $ echo $(( (109056 * $(getconf PAGE_SIZE)) / (1024 * 1024) )) 426 $ echo $(( ( 560128 * $(getconf PAGE_SIZE)) / (1024 * 1024) )) 2188 With those KSM results, I could expect something but 0 in "Shared Memory". Tracing the origin of "Shared Memory" in oVirt code, I realized it's coming from memShared value (from getVdsStats vdsm command), which is provided in Mbytes: $ vdsClient -s 192.168.10.250 getVdsStats | grep memShared memShared = 9 Finding memShared function in vdsm, we have: $VDSM_ROOT/vdsm/API.py ... stats['memShared'] = self._memShared() / Mbytes ... def _memShared(self): """ Return an approximation of memory shared by VMs thanks to KSM. """ shared = 0 for v in self._cif.vmContainer.values(): if v.conf['pid'] == '0': continue try: statmfile = file('/proc/' + v.conf['pid'] + '/statm') shared += int(statmfile.read().split()[2]) * PAGE_SIZE_BYTES except: pass return shared ... memShared is calculated adding the shared pages value (3rd field) from /proc/<VM_PID>/statm file from all running VMs, converting to bytes through PAGE_SIZE value and transforming to Mbytes at the end. This field in statm file currently is (it changed along kernel history) the count of pages instantiated in the process address space which are shared with a file, including executable, library or shared memory. Despite vdsm code comment, KSM shared pages are not accounted here. KSM works de-duplicating and sharing memory pages without process awareness. Engine is calculating the percent considering total physical memory - memSize value from getVdsCapabilities vdsm command: $ vdsClient -s 192.168.10.250 getVdsCapabilities | grep memSize memSize = 3574 Calculating the percent: $ echo "scale=2; 9 * 100 / 3574" | bc .25 So, we have arround 0,25%, rounded to 0%. "Shared Memory" is coherent, but not reflecting the real page deduplication benefits. And unnoticed administrators - me included - are led to think that Shared Memory is related with KSM results. IMO, memShared is not providing any representative information. On the other hand, the missing KSM results are really important to oVirt administrators, providing information about how much memory they are over committed by, for capacity management, and how much money oVirt is saving in memory. In order to offer those KSM stats to engine, I sent a patch [2] (waiting approval) adding "ksmShared" and "ksmSharing" values to vdsm getVdsStats command in a standard way, with key names that fits with existing KSM ones (ksmCpu, ksmPages and ksmState). Before patch: $ vdsClient -s 192.168.10.250 getVdsStats | grep ksm ksmCpu = 1 -> the ksmd process cpu load ksmPages = 664 -> pages to scan before ksmd goes to sleep ksmState = True -> is ksm running? With the patch: $ vdsClient -s 192.168.10.250 getVdsStats | grep ksm ksmCpu = 1 ksmPages = 664 ksmShared = 426 -> how many Mbytes of memory are being shared ksmSharing = 2188 -> how many more sites are sharing them i.e. how much Mbytes are being saved ksmState = True Finally my questions: 1 - Is sharedMem value (from /proc/PID/statm) that significant to be kept in host details? If yes, why? 2 - What about - and how (%, Mb, ...) - to add the vdsm new ksmShared and ksmSharing stats in host details? Sorry about my long history. I look forward to hearing your comments. All the best, -- Pahim [1] - http://www.pahim.org/wp-content/uploads/2012/05/Screenshot-oVirt-Enterprise… [2] - http://gerrit.ovirt.org/4755

2 2

[Engine-devel] Adding atomic restore snapshot command at backend
by Michael Pasternak 31 May '12

31 May '12

Currently 'restore snapshot' done in two steps on a client side: 1. TryBackToAllSnapshotsOfVm 2. RestoreAllSnapshots This implementation creates race condition on 1 and therefore unstable & bug prone, i suggested refactoring 2 to include 1 as single atomic operation at backend. -- Michael Pasternak RedHat, ENG-Virtualization R&D

4 7

[Engine-devel] Using 3.1.0 instead of 3.1.0-0001 for next release?
by Juan Hernandez 30 May '12

30 May '12

Hello, I think we have the opportunity now to clean the version number and use 3.1.0 instead of 3.1.0-0001 for the next release. I submitted the corresponding change to gerrit for review: http://gerrit.ovirt.org/4914 As far as I can tell there are no issues introduced by this change and it allows a cleaner versioning schema for the RPM packages. Please let me now if you foresee any issue. Regards, Juan Hernandez

2 3

[Engine-devel] Enabling guest memory balloon device
by Doron Fediuck 30 May '12

30 May '12

Hi All, In the following wiki, there's a design for enabling the balloon device, which is currently disabled in engine setups. Other than enabling the device, this is also a step forward in the path to vdsm and MoM sub-project integration. More details can be found here: http://www.ovirt.org/wiki/Features/Design/memory-balloon P.S. UI mockups should be updated soon. -- /d “Funny,” he intoned funereally, “how just when you think life can't possibly get any worse it suddenly does.” --Douglas Adams, The Hitchhiker's Guide to the Galaxy

2 2

[Engine-devel] planned changes for api capabilities resource
by Michael Pasternak 30 May '12

30 May '12

the motivation: =============== 1. current design is not restfull 2. is not consistent with the rest of api impl. impacts: ======== as this resource not used programmatically, we do not expect any backward compatibility issues planned change is: ================= from: http://localhost:8080/api/capabilities <capabilities> <version major="3" minor="1"> ... <version/> <version major="3" minor="0"> ... <version/> </capabilities> to: http://localhost:8080/api/capabilities/xxx <capabilities> ... </capabilities> (where xxx is a version number) -- Michael Pasternak RedHat, ENG-Virtualization R&D

3 8

[Engine-devel] Cancelled: ovirt-quantum integration
by Livnat Peer 30 May '12

30 May '12

--=_1e17596e-9255-4d59-9fa1-7cf66b4572c4 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit The following meeting has been cancelled: Subject: ovirt-quantum integration Organiser: "Livnat Peer" <lpeer(a)redhat.com> Time: Wednesday, 30 May, 2012, 4:00:00 PM - 5:00:00 PM GMT +02:00 Jerusalem Invitees: engine-devel(a)ovirt.org; ovedo(a)redhat.com; mkenneth(a)redhat.com; irenab(a)mellanox.com; atal(a)redhat.com; Ricky.Hopper(a)netapp.com; simon(a)redhat.com; gkotton(a)redhat.com *~*~*~*~*~*~*~*~*~* Garry is sick, he won't be available today, I'll reschedule this meeting soon. --=_1e17596e-9255-4d59-9fa1-7cf66b4572c4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html><body><h3>The following meeting has been cancelled:</h3> <table border='0'> <tr><th align=left>Subject:</th><td>ovirt-quantum integration </td></tr> <tr><th align=left>Organiser:</th><td>"Livnat Peer" <lpeer(a)redhat.com> </td></tr> </table> <table border='0'> <tr><th align=left>Time:</th><td>Wednesday, 30 May, 2012, 4:00:00 PM - 5:00:00 PM GMT +02:00 Jerusalem </td></tr></table> <table border='0'> <tr><th align=left>Invitees:</th><td>engine-devel(a)ovirt.org; ovedo(a)redhat.com; mkenneth(a)redhat.com; irenab(a)mellanox.com; atal(a)redhat.com; Ricky.Hopper(a)netapp.com; simon(a)redhat.com; gkotton(a)redhat.com </td></tr> </table> <div>*~*~*~*~*~*~*~*~*~*</div> Garry is sick, he won't be available today, I'll reschedule this meeting soon.</body></html> --=_1e17596e-9255-4d59-9fa1-7cf66b4572c4 Content-Type: text/calendar; charset=utf-8; method=CANCEL; name=meeting.ics Content-Transfer-Encoding: 7bit BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:CANCEL BEGIN:VTIMEZONE TZID:Asia/Jerusalem BEGIN:STANDARD DTSTART:19710101T020000 TZOFFSETTO:+0200 TZOFFSETFROM:+0300 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=9;BYDAY=2SU TZNAME:IST END:STANDARD BEGIN:DAYLIGHT DTSTART:19710101T020000 TZOFFSETTO:+0300 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1FR TZNAME:IDT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:a81eb649-a67e-4f3f-a2d5-bc34bb93c556 SUMMARY:Cancelled: ovirt-quantum integration COMMENT:The following meeting has been cancelled: ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:engine- devel(a)ovirt.org ATTENDEE;CN=Oved Ourfalli;PARTSTAT=ACCEPTED:mailto:ovedo@redhat.com ATTENDEE;CN=Miki Kenneth;PARTSTAT=ACCEPTED:mailto:mkenneth@redhat.com ATTENDEE;CN=Irena Berezovsky;PARTSTAT=TENTATIVE:mailto:irenab@mellanox.com ATTENDEE;CN=avi tal;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED:mailto:atal@redha t.com ATTENDEE;CN="Hopper, Ricky";PARTSTAT=TENTATIVE:mailto:Ricky.Hopper@netapp.co m ATTENDEE;CN=Simon Grinberg;PARTSTAT=ACCEPTED:mailto:simon@redhat.com ATTENDEE;CN=Gary Kotton;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED:mailto:gkotto n(a)redhat.com ORGANIZER;CN=Livnat Peer:mailto:lpeer@redhat.com DTSTART;TZID="Asia/Jerusalem":20120530T160000 DTEND;TZID="Asia/Jerusalem":20120530T170000 STATUS:CANCELLED CLASS:PUBLIC X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE LAST-MODIFIED:20120530T114520Z DTSTAMP:20120530T114520Z SEQUENCE:1 DESCRIPTION:The following meeting has been cancelled:\n\nSubject: ovirt-quan tum integration \nOrganiser: "Livnat Peer" <lpeer(a)redhat.com> \n\nTime: Wedn esday\, 30 May\, 2012\, 4:00:00 PM - 5:00:00 PM GMT +02:00 Jerusalem\n \nInv itees: engine-devel(a)ovirt.org\; ovedo(a)redhat.com\; mkenneth(a)redhat.com\; ire nab(a)mellanox.com\; atal(a)redhat.com\; Ricky.Hopper(a)netapp.com\; simon@redhat. com\; gkotton(a)redhat.com \n\n\n*~*~*~*~*~*~*~*~*~*\n\nGarry is sick\, he won 't be available today\, I'll reschedule this meeting soon. X-ALT-DESC;FMTTYPE=text/html:<html><body><h3>The following meeting has been cancelled:</h3>\n\n\n<table border='0'>\n<tr><th align=left>Subject:</th> <td>ovirt-quantum integration </td></tr>\n<tr><th align=left>Organiser:</th> <td>"Livnat Peer" &lt\;lpeer(a)redhat.com&gt\; </td></tr>\n</table>\n\n<tab le border='0'>\n<tr><th align=left>Time:</th><td>Wednesday\, 30 May\, 2012\, 4:00:00 PM - 5:00:00 PM GMT +02:00 Jerusalem\n </td></tr></table>\n\n<ta ble border='0'>\n<tr><th align=left>Invitees:</th><td>engine-devel(a)ovirt.org \; ovedo(a)redhat.com\; mkenneth(a)redhat.com\; irenab(a)mellanox.com\; atal@redha t.com\; Ricky.Hopper(a)netapp.com\; simon(a)redhat.com\; gkotton(a)redhat.com </td ></tr>\n</table>\n<div>*~*~*~*~*~*~*~*~*~*</div> Garry is sick\, he won't be available today\, I'll reschedule this meeting soon.</body></html> END:VEVENT END:VCALENDAR --=_1e17596e-9255-4d59-9fa1-7cf66b4572c4--

1 0

[Engine-devel] quantum ovirt integration meeting
by Livnat Peer 30 May '12

30 May '12

Hi All, Garry is sick and can not make it for today's meeting. Since he wrote the wiki proposal we'll reschedule this meeting to later this week or early next week. I'll send update soon. thanks, Livnat

1 0

[Engine-devel] Question about host compatibility version
by Ashok Vemuri 29 May '12

29 May '12

Hello, I have a newbie question regarding host/cluster compatibility versions. I hope someone could clarify this for me. We have an old lab setup in which we were managing KVM hostnodes using RHEV Manager (version 2.2.4.51796) . We are now trying to upgrade to the latest version of oVirt Engine (version 3.1.0_0001-1.8.el6). Now, when I add the old KVM node to oVirt Engine, I am getting following error message: Host's Compatibility Version doesn't match the Cluster's Compatibility Version Can someone tell me if oVirt Engine is backward-compatible with older hostnodes? Or do I need to upgrade one or more components (such as VDSM) on the hostnode to be compatible with new engine? Here is the version information from the hostnode I'm trying to add: OS : RHEV Hypervisor - 5.6 - 9.3.el5_6 Kernel : 2.6.18 - 238.5.1.el5 KVM : 83 - 224.el5 VDSM : 2.2.63.23 SPICE : 0.3.0 - 54.el5_5.2 Thanks, Ashok

2 1

[Engine-devel] api capabilities query and presenting SupportedVdsmVersions
by Yair Zaslavsky 29 May '12

29 May '12

Hi, After seeing an email regarding api/capabilities and looking at the code, and dealing regardless of that with VDSM versions - I have a question - is it interesting for us to display the list of supported VDSM versions under api/capabilities? Kind regards, Yair

2 1

[Engine-devel] ovirt-quantum integration
by Livnat Peer 29 May '12

29 May '12

--=_73e637f2-67d2-4803-854d-d64af2a541c0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit The following is a new meeting request: Subject: ovirt-quantum integration Organiser: "Livnat Peer" <lpeer(a)redhat.com> Time: Wednesday, 30 May, 2012, 4:00:00 PM - 5:00:00 PM GMT +02:00 Jerusalem Invitees: engine-devel(a)ovirt.org *~*~*~*~*~*~*~*~*~* Hi All, We'll have a discussion on oVirt-Quantum integration tomorrow. In the meeting we'll discuss - http://www.ovirt.org/wiki/Quantum_and_oVirt Thanks, Livnat Bridge ID: 972506565679 Dial-in information: Reservationless-Plus Toll Free Dial-In Number (US & Canada): (800) 451-8679 Reservationless-Plus International Dial-In Number: (212) 729-5016 Conference code: 972506565679 Global Access Numbers Local: Australia, Sydney Dial-In #: 0289852326 Austria, Vienna Dial-In #: 012534978196 Belgium, Brussels Dial-In #: 027920405 China Dial-In #: 4006205013 Denmark, Copenhagen Dial-In #: 32729215 Finland, Helsinki Dial-In #: 0923194436 France, Paris Dial-In #: 0170377140 Germany, Berlin Dial-In #: 030300190579 Ireland, Dublin Dial-In #: 014367793 Italy, Milan Dial-In #: 0236269529 Netherlands, Amsterdam Dial-In #: 0207975872 Norway, Oslo Dial-In #: 21033188 Singapore Dial-In #: 64840858 Spain, Barcelona Dial-In #: 935452328 Sweden, Stockholm Dial-In #: 0850513770 Switzerland, Geneva Dial-In #: 0225927881 United Kingdom Dial-In #: 02078970515 United Kingdom Dial-In #: 08445790676 United Kingdom, LocalCall Dial-In #: 08445790678 United States Dial-In #: 2127295016 Global Access Numbers Tollfree: Argentina Dial-In #: 8004441016 Australia Dial-In #: 1800337169 Austria Dial-In #: 0800005898 Bahamas Dial-In #: 18002054776 Bahrain Dial-In #: 80004377 Belgium Dial-In #: 080048325 Brazil Dial-In #: 08008921002 Bulgaria Dial-In #: 008001100236 Chile Dial-In #: 800370228 Colombia Dial-In #: 018009134033 Costa Rica Dial-In #: 08000131048 Cyprus Dial-In #: 80095297 Czech Republic Dial-In #: 800700318 Denmark Dial-In #: 80887114 Dominican Republic Dial-In #: 18887512313 Estonia Dial-In #: 8000100232 Finland Dial-In #: 0800117116 France Dial-In #: 0805632867 Germany Dial-In #: 8006647541 Greece Dial-In #: 00800127562 Hong Kong Dial-In #: 800930349 Hungary Dial-In #: 0680016796 Iceland Dial-In #: 8008967 India Dial-In #: 0008006501533 Indonesia Dial-In #: 0018030179162 Ireland Dial-In #: 1800932401 Israel Dial-In #: 1809462557 Italy Dial-In #: 800985897 Jamaica Dial-In #: 18002050328 Japan Dial-In #: 0120934453 Korea (South) Dial-In #: 007986517393 Latvia Dial-In #: 80003339 Lithuania Dial-In #: 880030479 Luxembourg Dial-In #: 80026595 Malaysia Dial-In #: 1800814451 Mexico Dial-In #: 0018664590915 New Zealand Dial-In #: 0800888167 Norway Dial-In #: 80012994 Panama Dial-In #: 008002269184 Philippines Dial-In #: 180011100991 Poland Dial-In #: 008001210187 Portugal Dial-In #: 800814625 Russian Federation Dial-In #: 81080028341012 Saint Kitts and Nevis Dial-In #: 18002059252 Singapore Dial-In #: 8006162235 Slovak Republic Dial-In #: 0800001441 South Africa Dial-In #: 0800981148 Spain Dial-In #: 800300524 Sweden Dial-In #: 200896860 Switzerland Dial-In #: 800650077 Taiwan Dial-In #: 00801127141 Thailand Dial-In #: 001800656966 Trinidad and Tobago Dial-In #: 18002024615 United Arab Emirates Dial-In #: 8000650591 United Kingdom Dial-In #: 08006948057 United States Dial-In #: 8004518679 Uruguay Dial-In #: 00040190315 Venezuela Dial-In #: 08001627182 --=_73e637f2-67d2-4803-854d-d64af2a541c0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><h3>The following is a new meeting request:</h3> <table border=3D'0'> <tr><th align=3Dleft>Subject:</th><td>ovirt-quantum integration </td></tr> <tr><th align=3Dleft>Organiser:</th><td>"Livnat Peer" <lpeer(a)redhat.com&= gt; </td></tr> </table> <table border=3D'0'> <tr><th align=3Dleft>Time:</th><td>Wednesday, 30 May, 2012, 4:00:00 PM - 5:= 00:00 PM GMT +02:00 Jerusalem </td></tr></table> <table border=3D'0'> <tr><th align=3Dleft>Invitees:</th><td>engine-devel(a)ovirt.org </td></tr> </table> <div>*~*~*~*~*~*~*~*~*~*</div> Hi All, We'll have a discussion on= oVirt-Quantum integration tomorrow. In the meeting we'll discuss - h= ttp://www.ovirt.org/wiki/Quantum_and_oVirt Thanks, Livnat Bri= dge ID: 972506565679 Dial-in information: Reservationless-Plus Toll F= ree Dial-In Number (US & Canada): (800) 451-8679 Reservationless-Plu= s International Dial-In Number: (212) 729-5016 Conference code: 97250656= 5679 Global Access Numbers Local: Australia, Sydney Dial-In #: 02= 89852326 Austria, Vienna Dial-In #: 012534978196 Belgium, Brussels Di= al-In #: 027920405 China Dial-In #: 4006205013 Denmark, Copenhagen Di= al-In #: 32729215 Finland, Helsinki Dial-In #: 0923194436 France, Par= is Dial-In #: 0170377140 Germany, Berlin Dial-In #: 030300190579 Irel= and, Dublin Dial-In #: 014367793 Italy, Milan Dial-In #: 0236269529 N= etherlands, Amsterdam Dial-In #: 0207975872 Norway, Oslo Dial-In #: 2103= 3188 Singapore Dial-In #: 64840858 Spain, Barcelona Dial-In #: 935452= 328 Sweden, Stockholm Dial-In #: 0850513770 Switzerland, Geneva Dial-= In #: 0225927881 United Kingdom Dial-In #: 02078970515 United Kingdom= Dial-In #: 08445790676 United Kingdom, LocalCall Dial-In #: 08445790678= United States Dial-In #: 2127295016 Global Access Numbers To= llfree: Argentina Dial-In #: 8004441016 Australia Dial-In #: 18003371= 69 Austria Dial-In #: 0800005898 Bahamas Dial-In #: 18002054776 Ba= hrain Dial-In #: 80004377 Belgium Dial-In #: 080048325 Brazil Dial-In= #: 08008921002 Bulgaria Dial-In #: 008001100236 Chile Dial-In #: 800= 370228 Colombia Dial-In #: 018009134033 Costa Rica Dial-In #: 0800013= 1048 Cyprus Dial-In #: 80095297 Czech Republic Dial-In #: 800700318<b= r>Denmark Dial-In #: 80887114 Dominican Republic Dial-In #: 18887512313<= br>Estonia Dial-In #: 8000100232 Finland Dial-In #: 0800117116 France= Dial-In #: 0805632867 Germany Dial-In #: 8006647541 Greece Dial-In #= : 00800127562 Hong Kong Dial-In #: 800930349 Hungary Dial-In #: 06800= 16796 Iceland Dial-In #: 8008967 India Dial-In #: 0008006501533 In= donesia Dial-In #: 0018030179162 Ireland Dial-In #: 1800932401 Israel= Dial-In #: 1809462557 Italy Dial-In #: 800985897 Jamaica Dial-In #: = 18002050328 Japan Dial-In #: 0120934453 Korea (South) Dial-In #: 0079= 86517393 Latvia Dial-In #: 80003339 Lithuania Dial-In #: 880030479<br= >Luxembourg Dial-In #: 80026595 Malaysia Dial-In #: 1800814451 Mexico= Dial-In #: 0018664590915 New Zealand Dial-In #: 0800888167 Norway Di= al-In #: 80012994 Panama Dial-In #: 008002269184 Philippines Dial-In = #: 180011100991 Poland Dial-In #: 008001210187 Portugal Dial-In #: 80= 0814625 Russian Federation Dial-In #: 81080028341012 Saint Kitts and = Nevis Dial-In #: 18002059252 Singapore Dial-In #: 8006162235 Slovak R= epublic Dial-In #: 0800001441 South Africa Dial-In #: 0800981148 Spai= n Dial-In #: 800300524 Sweden Dial-In #: 200896860 Switzerland Dial-I= n #: 800650077 Taiwan Dial-In #: 00801127141 Thailand Dial-In #: 0018= 00656966 Trinidad and Tobago Dial-In #: 18002024615 United Arab Emira= tes Dial-In #: 8000650591 United Kingdom Dial-In #: 08006948057 Unite= d States Dial-In #: 8004518679 Uruguay Dial-In #: 00040190315 Venezue= la Dial-In #: 08001627182 </body></html> --=_73e637f2-67d2-4803-854d-d64af2a541c0 Content-Type: text/calendar; charset=utf-8; method=REQUEST; name=meeting.ics Content-Transfer-Encoding: 7bit BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:Asia/Jerusalem BEGIN:STANDARD DTSTART:19710101T020000 TZOFFSETTO:+0200 TZOFFSETFROM:+0300 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=9;BYDAY=2SU TZNAME:IST END:STANDARD BEGIN:DAYLIGHT DTSTART:19710101T020000 TZOFFSETTO:+0300 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1FR TZNAME:IDT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:a81eb649-a67e-4f3f-a2d5-bc34bb93c556 SUMMARY:ovirt-quantum integration ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:engine- devel(a)ovirt.org ORGANIZER;CN=Livnat Peer:mailto:lpeer@redhat.com DTSTART;TZID="Asia/Jerusalem":20120530T160000 DTEND;TZID="Asia/Jerusalem":20120530T170000 STATUS:CONFIRMED CLASS:PUBLIC X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE LAST-MODIFIED:20120529T113915Z DTSTAMP:20120529T113915Z SEQUENCE:0 DESCRIPTION:The following is a new meeting request:\n\nSubject: ovirt-quantu m integration \nOrganiser: "Livnat Peer" <lpeer(a)redhat.com> \n\nTime: Wednes day\, 30 May\, 2012\, 4:00:00 PM - 5:00:00 PM GMT +02:00 Jerusalem\n \nInvit ees: engine-devel(a)ovirt.org \n\n\n*~*~*~*~*~*~*~*~*~*\n\nHi All\,\n\nWe'll h ave a discussion on oVirt-Quantum integration tomorrow.\nIn the meeting we'l l discuss -\nhttp://www.ovirt.org/wiki/Quantum_and_oVirt\n\nThanks\, Livnat\ n\nBridge ID: 972506565679\nDial-in information:\nReservationless-Plus Toll Free Dial-In Number (US & Canada): (800) 451-8679\nReservationless-Plus Inte rnational Dial-In Number: (212) 729-5016\nConference code: 972506565679\n\nG lobal Access Numbers Local:\nAustralia\, Sydney Dial-In #: 0289852326\nAustr ia\, Vienna Dial-In #: 012534978196\nBelgium\, Brussels Dial-In #: 027920405 \nChina Dial-In #: 4006205013\nDenmark\, Copenhagen Dial-In #: 32729215\nFin land\, Helsinki Dial-In #: 0923194436\nFrance\, Paris Dial-In #: 0170377140\ nGermany\, Berlin Dial-In #: 030300190579\nIreland\, Dublin Dial-In #: 01436 7793\nItaly\, Milan Dial-In #: 0236269529\nNetherlands\, Amsterdam Dial-In # : 0207975872\nNorway\, Oslo Dial-In #: 21033188\nSingapore Dial-In #: 648408 58\nSpain\, Barcelona Dial-In #: 935452328\nSweden\, Stockholm Dial-In #: 08 50513770\nSwitzerland\, Geneva Dial-In #: 0225927881\nUnited Kingdom Dial-In #: 02078970515\nUnited Kingdom Dial-In #: 08445790676\nUnited Kingdom\, Loc alCall Dial-In #: 08445790678\nUnited States Dial-In #: 2127295016\n\n\nGlob al Access Numbers Tollfree:\nArgentina Dial-In #: 8004441016\nAustralia Dial -In #: 1800337169\nAustria Dial-In #: 0800005898\nBahamas Dial-In #: 1800205 4776\nBahrain Dial-In #: 80004377\nBelgium Dial-In #: 080048325\nBrazil Dial -In #: 08008921002\nBulgaria Dial-In #: 008001100236\nChile Dial-In #: 80037 0228\nColombia Dial-In #: 018009134033\nCosta Rica Dial-In #: 08000131048\nC yprus Dial-In #: 80095297\nCzech Republic Dial-In #: 800700318\nDenmark Dial -In #: 80887114\nDominican Republic Dial-In #: 18887512313\nEstonia Dial-In #: 8000100232\nFinland Dial-In #: 0800117116\nFrance Dial-In #: 0805632867\n Germany Dial-In #: 8006647541\nGreece Dial-In #: 00800127562\nHong Kong Dial -In #: 800930349\nHungary Dial-In #: 0680016796\nIceland Dial-In #: 8008967\ nIndia Dial-In #: 0008006501533\nIndonesia Dial-In #: 0018030179162\nIreland Dial-In #: 1800932401\nIsrael Dial-In #: 1809462557\nItaly Dial-In #: 80098 5897\nJamaica Dial-In #: 18002050328\nJapan Dial-In #: 0120934453\nKorea (So uth) Dial-In #: 007986517393\nLatvia Dial-In #: 80003339\nLithuania Dial-In #: 880030479\nLuxembourg Dial-In #: 80026595\nMalaysia Dial-In #: 1800814451 \nMexico Dial-In #: 0018664590915\nNew Zealand Dial-In #: 0800888167\nNorway Dial-In #: 80012994\nPanama Dial-In #: 008002269184\nPhilippines Dial-In #: 180011100991\nPoland Dial-In #: 008001210187\nPortugal Dial-In #: 800814625 \nRussian Federation Dial-In #: 81080028341012\nSaint Kitts and Nevis Dial-I n #: 18002059252\nSingapore Dial-In #: 8006162235\nSlovak Republic Dial-In # : 0800001441\nSouth Africa Dial-In #: 0800981148\nSpain Dial-In #: 800300524 \nSweden Dial-In #: 200896860\nSwitzerland Dial-In #: 800650077\nTaiwan Dial -In #: 00801127141\nThailand Dial-In #: 001800656966\nTrinidad and Tobago Di al-In #: 18002024615\nUnited Arab Emirates Dial-In #: 8000650591\nUnited Kin gdom Dial-In #: 08006948057\nUnited States Dial-In #: 8004518679\nUruguay Di al-In #: 00040190315\nVenezuela Dial-In #: 08001627182 X-ALT-DESC;FMTTYPE=text/html:<html><body><h3>The following is a new meeting request:</h3>\n\n\n<table border='0'>\n<tr><th align=left>Subject:</th><t d>ovirt-quantum integration </td></tr>\n<tr><th align=left>Organiser:</th><t d>"Livnat Peer" &lt\;lpeer(a)redhat.com&gt\; </td></tr>\n</table>\n\n<table border='0'>\n<tr><th align=left>Time:</th><td>Wednesday\, 30 May\, 2012\, 4 :00:00 PM - 5:00:00 PM GMT +02:00 Jerusalem\n </td></tr></table>\n\n<tabl e border='0'>\n<tr><th align=left>Invitees:</th><td>engine-devel(a)ovirt.org < /td></tr>\n</table>\n<div>*~*~*~*~*~*~*~*~*~*</div> Hi All\, We'll have a discussion on oVirt-Quantum integration tomorrow. In the meeting we'll discuss - http://www.ovirt.org/wiki/Quantum_and_oVirt Thanks \, Livnat Bridge ID: 972506565679 Dial-in information: Reservat ionless-Plus Toll Free Dial-In Number (US &amp\; Canada): (800) 451-8679 Reservationless-Plus International Dial-In Number: (212) 729-5016 Confere nce code: 972506565679 Global Access Numbers Local: Australia\, Sy dney Dial-In #: 0289852326 Austria\, Vienna Dial-In #: 012534978196 Be lgium\, Brussels Dial-In #: 027920405 China Dial-In #: 4006205013 Denm ark\, Copenhagen Dial-In #: 32729215 Finland\, Helsinki Dial-In #: 092319 4436 France\, Paris Dial-In #: 0170377140 Germany\, Berlin Dial-In #: 030300190579 Ireland\, Dublin Dial-In #: 014367793 Italy\, Milan Dial- In #: 0236269529 Netherlands\, Amsterdam Dial-In #: 0207975872 Norway\ , Oslo Dial-In #: 21033188 Singapore Dial-In #: 64840858 Spain\, Barce lona Dial-In #: 935452328 Sweden\, Stockholm Dial-In #: 0850513770 Swi tzerland\, Geneva Dial-In #: 0225927881 United Kingdom Dial-In #: 0207897 0515 United Kingdom Dial-In #: 08445790676 United Kingdom\, LocalCall Dial-In #: 08445790678 United States Dial-In #: 2127295016 Glo bal Access Numbers Tollfree: Argentina Dial-In #: 8004441016 Australia Dial-In #: 1800337169 Austria Dial-In #: 0800005898 Bahamas Dial-In # : 18002054776 Bahrain Dial-In #: 80004377 Belgium Dial-In #: 080048325 Brazil Dial-In #: 08008921002 Bulgaria Dial-In #: 008001100236 Chi le Dial-In #: 800370228 Colombia Dial-In #: 018009134033 Costa Rica Di al-In #: 08000131048 Cyprus Dial-In #: 80095297 Czech Republic Dial-In #: 800700318 Denmark Dial-In #: 80887114 Dominican Republic Dial-In # : 18887512313 Estonia Dial-In #: 8000100232 Finland Dial-In #: 0800117 116 France Dial-In #: 0805632867 Germany Dial-In #: 8006647541 Gree ce Dial-In #: 00800127562 Hong Kong Dial-In #: 800930349 Hungary Dial- In #: 0680016796 Iceland Dial-In #: 8008967 India Dial-In #: 000800650 1533 Indonesia Dial-In #: 0018030179162 Ireland Dial-In #: 1800932401 Israel Dial-In #: 1809462557 Italy Dial-In #: 800985897 Jamaica Dia l-In #: 18002050328 Japan Dial-In #: 0120934453 Korea (South) Dial-In #: 007986517393 Latvia Dial-In #: 80003339 Lithuania Dial-In #: 880030 479 Luxembourg Dial-In #: 80026595 Malaysia Dial-In #: 1800814451 M exico Dial-In #: 0018664590915 New Zealand Dial-In #: 0800888167 Norwa y Dial-In #: 80012994 Panama Dial-In #: 008002269184 Philippines Dial- In #: 180011100991 Poland Dial-In #: 008001210187 Portugal Dial-In #: 800814625 Russian Federation Dial-In #: 81080028341012 Saint Kitts and Nevis Dial-In #: 18002059252 Singapore Dial-In #: 8006162235 Slovak R epublic Dial-In #: 0800001441 South Africa Dial-In #: 0800981148 Spain Dial-In #: 800300524 Sweden Dial-In #: 200896860 Switzerland Dial-In #: 800650077 Taiwan Dial-In #: 00801127141 Thailand Dial-In #: 0018006 56966 Trinidad and Tobago Dial-In #: 18002024615 United Arab Emirates Dial-In #: 8000650591 United Kingdom Dial-In #: 08006948057 United Sta tes Dial-In #: 8004518679 Uruguay Dial-In #: 00040190315 Venezuela Dia l-In #: 08001627182 </body></html> BEGIN:VALARM ACTION:DISPLAY TRIGGER;RELATED=START:-PT5M DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR --=_73e637f2-67d2-4803-854d-d64af2a541c0--

1 0

[Engine-devel] REST-API: Exposing correlation-ID
by Ori Liel 29 May '12

29 May '12

Correlation-ID feature allows 'tagging' a call to a Backend command with a String ID, and this ID will be appended to all log messages that result from this command. http://www.ovirt.org/wiki/Features/TaskManagerDetailed In REST-API, we would like to enable the user to pass a correlation-ID when he activates actions. I have two questions: 1) what's the name you'd give this parameter? job-id? batch-id? flow-id? command-id? correlation-id??? 2) I've already implemented this as a url parameter. Are there objections? The only viable alternative I see is as an http header, which doesn't feel right. It's not an option to pass it in the XML body, because sometimes there is no body, for example, in DELETE commands. Thanks Ori.

12 29

[Engine-devel] oVirt 3.1 Blocker - BZ#822158 - fail to join host to cluster
by Ofer Schreiber 29 May '12

29 May '12

Hey Yair, BZ#822158 (https://bugzilla.redhat.com/show_bug.cgi?id=822158) is currently marked as oVirt 3.1 release blocker. I'd like to get some updates from you, As the assignee for this bug: 1. What is the current status of this bug? 2. Any time estimation for a complete fix? Thanks, -- Ofer Schreiber oVirt Release Manager

2 1

[Engine-devel] upgrade.sh error after commit e592cb210b6bceba6414e4b89c8456b21532f479
by ovirt＠qip.ru 28 May '12

28 May '12

This is a message in Mime Format. If you see this, your mail reader does not support this format. --=_55ab36880aaf9d39b66e859d698414a9 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable # ./upgrade.sh -u postgres=0ARunning upgrade script upgrade/03_01_1120_v= m_device_add_alias_column.sql=0Apsql:upgrade/03_01_1120_vm_device_add_al= ias_column.sql:1: invalid command \'');=0A=0A-- --=_55ab36880aaf9d39b66e859d698414a9 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable # ./upgrade.sh -u postgres Running upgrade script upgrade/03_01_1= 120_vm_device_add_alias_column.sql psql:upgrade/03_01_1120_vm_device_= add_alias_column.sql:1: invalid command \''); -- <= br> --=_55ab36880aaf9d39b66e859d698414a9--

2 1

[Engine-devel] oVirt automated test suites
by Shu Ming 25 May '12

25 May '12

Hi, I need a reasonable test suites to test VDSM APIs. I know most of tests are done from the engine side manually. But I think we need a reasonable test suites to define the typical workflows of engine usage calling into VDSM APIs and make sure all the functions are doing well. As engine publics REST-APIs, an automated test suites can be created on top of the REST-APs without much difficult. Any other comments about this idea? -- Shu Ming<shuming(a)linux.vnet.ibm.com> IBM China Systems and Technology Laboratory

2 1

[Engine-devel] Host Network status isn't being updated
by Itzik Brown 25 May '12

25 May '12

--_000_4488206DC085244C886DBC9E7038B68925186CD0mtrdag02mtlcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I add a network using ovirt-engine: Adding a network to a data center then attaching the network to a cluster(N= on required network). Then I do the following on the host (running vdsm): #brctl addbr mynetwork #brctl addif mynetwork eth3 The refresh rate as indicated by ovirt-engine GUI is 5 seconds. I don't see that the network is attached to the interface until I manually = restart vdsm. Any suggestion? Thanks, Itzik --_000_4488206DC085244C886DBC9E7038B68925186CD0mtrdag02mtlcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> Hi,<o:p></o:p> <o:p> </o:p> I add a network using ovirt-engine:<o:p></o:p> Adding a network to a data center then attaching the= network to a cluster(Non required network).<o:p></o:p> <o:p> </o:p> Then I do the following on the host (running vdsm):<= o:p></o:p> #brctl addbr mynetwork<o:p></o:p> #brctl addif mynetwork eth3 <o:p></o:p> <o:p> </o:p> The refresh rate as indicated by ovirt-engine GUI is= 5 seconds.<o:p></o:p> I don't see that the network is attached to the inte= rface until I manually restart vdsm.<o:p></o:p> <o:p> </o:p> Any suggestion?<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> Itzik<o:p></o:p> </div> </body> </html> --_000_4488206DC085244C886DBC9E7038B68925186CD0mtrdag02mtlcom_--

3 4

[Engine-devel] CPU Pinning @engine
by Doron Fediuck 24 May '12

24 May '12

Hi All, Currently the VDSM has a CPU pinning hook. We'd like to add better support of it into the engine itself. Here's a design draft to cover it: http://www.ovirt.org/wiki/Features/Design/cpu-pinning Please review and comment if needed. Thanks! -- /d Never say "OOPS!" always say "Ah, Interesting!"

8 24

[Engine-devel] custom properties sheet feature page
by Einav Cohen 23 May '12

23 May '12

Hi, Please review/comment on the Custom Properties Sheet feature page: http://www.ovirt.org/wiki/Features/CustomPropertiesSheet ---- Thanks, Einav

6 21

[Engine-devel] restapi: New params for import VM/Template
by Gilad Chaplik 23 May '12

23 May '12

Hi All, I am adding the ability to import a VM or a Template to a storage-domain, when this VM or Template already exists in the destination storage domain. Until now, Backend failed this. Now I want to enable the user to specify that he wishes this VM/Template will be created again by a different name, i.e - cloned. [feature page: http://www.ovirt.org/wiki/Features/ImportMoreThanOnce] I plan to achieve this using a new parameter, but I want to reach an agreement about this parameter's name. I thought simply to call it "clone". Another thing that I'll do in the patch-set is add the currently-missing ability to specify whether the snapshots of the VM, which is being imported, will be collapsed into a single snapshot (we have this ability in GUI). I am also deliberating about the name of this parameter. I thought about "collapse_snapshots" (same as in GUI). Does anyone think "clone" and "collapse_snapshots" are inappropriate and has better suggestions? Thanks, Gilad

6 20

[Engine-devel] is gerrit.ovirt.org down?
by Shireesh Anjal 22 May '12

22 May '12

I have been unable to access the web UI or work with the repository for around half an hour now... ~Shireesh

4 3

[Engine-devel] network features review
by Livnat Peer 22 May '12

22 May '12

Hi All, This is a summary of comments we(*) gathered while reviewing the current network related functionality in oVirt, we'll open the relevant RFE/Bugs but wanted to share first to get comments: Default Gateway: ---------------- current status - In the UI/API we expose to the user the possibility to configure the default gateway for the host. We expose this option only when editing the management network. comments - Apparently we do not configure the host default gateway but the network gateway. 1. We need to fix the phrasing to gateway (not default gateway) 2. Why do we block it for networks which are not the management network 3. We need to support configuring the host default gateway. Non VM (Bridge-less) Network: ----------------------------- current status - During bootstrap we configure the management network on the host. We did not implement configuring bridge-less management network during bootstrap. comments - 1. Supporting bridge-less network is a new feature,the design of this feature did not include changing the bootstrap process which make this feature non-useful when it comes to management network. Today one can edit a network only when it is not attached to clusters, at this point you can change the management network to be non-VM network, the problem is that we configure the management network on the host during bootstrap and we do not get a parameter if to create a bridge or not (we always create a bridge). What we end up with is - we can't change the management network once we added clusters/hosts but if changing it before attaching a cluster we ignore it in the bootstrap process. Check connectivity: -------------------- current status - The 'check connectivity' functionality is available only when editing the management network, it validates that we did not loose connectivity to the host, if we did the changes are rolled backed automatically. comments - 1. Sometimes when changing configuration of another network we can 'damage' the connectivity to the host. We want to expose the check connectivity functionality on any network configuration change. VLAN tagging of management Network ----------------------------------- current status - The user can set a VLAN tag on the management network. comments - 1. Any configuration of the management network needs support in the bootstrap process (see explanation above for bridge-less network) 2. In case of VLAN tagging it is even more complicated, when adding a host to oVirt we add it's address and it can not be changed after the host was added to the system. in the bootstrap process we set the management network on the nic oVirt engine used to ssh through, unless the VLAN device is already configured and the IP used for the ssh is already on this VLAN (for which it will work) we can't set the network to be on another IP address. Rollback network configuration: -------------------------------- current status - We have the option to make changes to the host network configuration and not persist the changes (they won't survive machine reboot) comments - 1. We are missing the functionality of rolling back the changes (without rebooting the machine), this functionality is the complementary behavior of 'save network configuration'. Predefined bonds: ----------------- current status - In the bootstrap process we create bonds0-5 on the hosts and then we use them when creating a bond on the host comments - 1. Creating the bonds in the host during the bootstrap process is not needed and we can let the user choose the bond name (limited to bondX) and create bonds only upon request. Editing Network properties while Network is attached to cluster/s ------------------------------------------------------------------ current status - Changing the network properties is blocked if the network is attached to a cluster. comments - 1. We should relax this approach. to start with we can enable editing when there are no active hosts in the cluster/s. doing more than the above requires substantially more work both in VDSM and engine. Thank you, Livnat (*) we == {Dan Kenigsberg, Igor Lvovsky, Mike Kolesnik, Moti Asayag, Muli Salem, Alona Kaplan, Livnat Peer} (**) We have even longer list for the UI changes needed, for them we'll open bugs directly to avoid another long email.

6 9

[Engine-devel] oVirt and Quantum
by Gary Kotton 22 May '12

22 May '12

Hi, As part of a POC we have integrated Quantum (http://wiki.openstack.org/Quantum) into oVirt (http://www.ovirt.org/) This has been tested with the OVS and Linux Bridge plugins. The details of the integration can be found at - https://fedoraproject.org/wiki/Quantum_and_oVirt. Any comments and suggestions would be greatly appreciated. Thanks Gary

5 14

[Engine-devel] F17 maven build failure
by Ofer Schreiber 21 May '12

21 May '12

Hey, I'm trying to build ovirt-engine in Fedora 17, and getting the following error: [INFO] oVirt Modules - manager ........................... FAILURE [1:05.421s] .... [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.6:check (default) on project manager-modules: Execution default of goal org.apache.maven.plugins:maven-checkstyle-plugin:2.6:check failed: Plugin org.apache.maven.plugins:maven-checkstyle-plugin:2.6 or one of its dependencies could not be resolved: The following artifacts could not be resolved: checkstyle:checkstyle:jar:5.0, antlr:antlr:jar:2.7.6, commons-beanutils:commons-beanutils-core:jar:1.7.0, com.google.collections:google-collections:jar:0.9: Could not find artifact checkstyle:checkstyle:jar:5.0 -> [Help 1] Any idea how can I resolve it? --- Ofer Schreiber

2 5

[Engine-devel] port mirroring REST API
by Livnat Peer 21 May '12

21 May '12

Hi All, After digging into the port mirroring feature I suggest a different modeling of it in the API. The current modeling is to add to vnic a boolean property of port-mirroring, e.g. api/vms/{vm-id}/nics <nics> <nic> ... <network href="/api/networks/{network-id}" id="{network-id}"/> <port-mirroring> true </port mirroring> </nic> </VM> This modeling imply 2 limitations: 1. The vnic must be connected to the network it wants to monitor 2. the nic can mirror only a single network Both of the above limitations are correct to the current implementation. Going forward we might want to introduce the above functionalities and the above modeling won't hold. Instead of the above I suggest to change the port-mirroring property to a list of networks. <nics> <nic> ... <network href="/api/networks/{network-id}" id="{network-id}"/> <port-mirroring> <network href="/api/networks/{network-id}" id="{network-id}"/> .... </port mirroring> </nic> </VM> In this version we'll validate that the network under port-mirroring is equal to the network the vnic is connected to, in future versions we can remove this validation without changing the API. Thanks, Livnat

3 7

[Engine-devel] Engine DB - user locked
by Elad Tabak 21 May '12

21 May '12

Hi, After an attempt to clear the DB by running './create_db_devel.sh -u postgres', I got an error: *Failed to create database engine* I then run 'dropdb -U postgres engine', and then 'create_db_devel.sh' again, but still I get the same error. When I tried to login from the admin web interface, I get authentication error. This is from the jboss log: USER_FAILED_TO_AUTHENTICATE_ACCOUNT_IS_LOCKED_OR_DISABLED I also tried running './create_db_devel.sh -u postgres -d engine_new', but it gives the same error ("Failed to create database engine_new"). I tried restarting the posgresql service, it didn't help. Please advice. Thanks, Elad

3 6

[Engine-devel] Advanced Nfs Options + NFSv4 GUI mockup
by Einav Cohen 21 May '12

21 May '12

Please review the mock-up on the feature page: http://www.ovirt.org/wiki/Features/AdvancedNfsOptions#User_Experience Comments are welcome. ---- Thanks, Einav

6 14

[Engine-devel] MAC address validation
by Mike Kolesnik 21 May '12

21 May '12

--=_866d6214-3639-45a0-b94a-0b67e454d998 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, We have a bug open on engine to validate MAC address: https://bugzilla.redhat.com/show_bug.cgi?id=756437 The format supported by engine (for Ethernet) is FF:FF:FF:FF:FF:FF (F is any hex char). Is there any other format we must support? Regards, Mike --=_866d6214-3639-45a0-b94a-0b67e454d998 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Hi, We have a bug open on engine to validate MAC address: https://bugzilla.redhat.com/show_bug.cgi?id=756437 The format supported by engine (for Ethernet) is FF:FF:FF:FF:FF:FF (F is any hex char). Is there any other format we must support? <div>Regards, Mike </div> </div></body></html> --=_866d6214-3639-45a0-b94a-0b67e454d998--

5 4

[Engine-devel] IMPORTANT: Root web application moved
by Juan Hernandez 20 May '12

20 May '12

Hello, I have recently merged a change that moves the root web application to the .ear directory: http://gerrit.ovirt.org/3782 This change could break your environment if you apply the patch and you don't do a clean installation. You may find an error like this in your server log and the application can fail to deploy: JBAS014777: Services which failed to start: service jboss.web.deployment.default-host./: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: Failed to start service That means that you have more than one / application. Please make sure that you don't have the old ROOT.war in your deployment directory. Just remove it and the corresponding ROOT.war.dodeploy file. Also make sure that you don't have the following parameter in your standalone.xml file: enable-welcome-root="true" Change the value to "false". None of this actions are needed if you are building new RPMs and doing a clean installation. If you still have problems starting the application server after applying this change please let me know. Regards, Juan Hernandez

2 3

[Engine-devel] DiskImage public mupper
by Michael Pasternak 20 May '12

20 May '12

what should be exposed to user as disk.id: DiskImage.id or DiskImage.ImageId ? -- Michael Pasternak RedHat, ENG-Virtualization R&D

2 4

[Engine-devel] Java 7: Fix namespaces use in OVF writer
by Juan Hernandez 18 May '12

18 May '12

Hello, I recently submitted a change to fix the way we manage namespaces in the OVF writer: http://gerrit.ovirt.org/4540 The problem is that it doesn't work with the StAX reference implementation included with Java 7. With the patched OVF writer I generated the attached OVF file. I would appreciate if someone can take a quick look at it and tell me if it is correct. I would also appreciate if you can send me known good OVF files generated by the engine, to compare them with the ones produced with the patched OVF writer. Thanks in advance, 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 2

[Engine-devel] Where is the git workspace of "engine-iso-uploader"?
by Shu Ming 18 May '12

18 May '12

Hi, From this page, I am told that it should be in the same workspace as ovirt-engine. http://www.ovirt.org/project/subprojects/ However, I can not find it in ovirt-engine workspace. Where does it go? -- Shu Ming<shuming(a)linux.vnet.ibm.com> IBM China Systems and Technology Laboratory

2 4

[Engine-devel] Feedback requested on name change
by Alex Lourie 17 May '12

17 May '12

This is a multi-part message in MIME format. --------------090408020509030405010906 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit We have now separated tools repositories which are built independently from ovirt-engine, for example "ovirt-image-uploader". Our rpms (ovirt-engine) has a dependency on those tools, using the following option: <snip> ... Requires: %{name}-image-uploader ... <snip> %{name} is substituted by 'ovirt-engine' during build, creating a dependency on "*ovirt-engine-image-uploader*". This, in turn, makes a non-resolved dependency, as the actual package name built for image-uploader is "*ovirt-image-uploader*". We can resolve this by either changing the dependency in our rpms or by changing the tools package names (relevant also for iso-uploader and log-collector). Please let me know which way seems preferable for this. Thanks. -- Alex Lourie. --------------090408020509030405010906 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"> We have now separated tools repositories which are built independently from ovirt-engine, for example "ovirt-image-uploader". Our rpms (ovirt-engine) has a dependency on those tools, using the following option: <snip> ... Requires: %{name}-image-uploader ... <snip> %{name} is substituted by 'ovirt-engine' during build, creating a dependency on "ovirt-engine-image-uploader". This, in turn, makes a non-resolved dependency, as the actual package name built for image-uploader is "ovirt-image-uploader". We can resolve this by either changing the dependency in our rpms or by changing the tools package names (relevant also for iso-uploader and log-collector). Please let me know which way seems preferable for this. Thanks. <pre class="moz-signature" cols="72">-- Alex Lourie.</pre> </body> </html> --------------090408020509030405010906--

2 1

[Engine-devel] RefObject
by Laszlo Hornyak 17 May '12

17 May '12

hi, Thank you for the reviews on the refobject removal patches! Here are some more :) http://gerrit.ovirt.org/4465 http://gerrit.ovirt.org/4501 http://gerrit.ovirt.org/4502 Thank you, Laszlo

1 0

[Engine-devel] Random seeding in unit tests
by Allon Mureinik 16 May '12

16 May '12

If you ever need a comfortable way to inject a random seed to your test (e.g., for reproducing a specific run), check out the new RandomUtilsSeedingRule: http://ovirt.org/wiki/RandomUtilsSeedingRule

1 0

[Engine-devel] git-review error.
by snmishra＠linux.vnet.ibm.com 15 May '12

15 May '12

Hi, I am trying to push a patch to gerrit for review. $ ./git-review -t nullpointer remote: Resolving deltas: 0% (0/6) To ssh://snmishra@gerrit.ovirt.org:29418/ovirt-engine.git ! [remote rejected] HEAD -> refs/publish/master/nullpointer (prohibited by Gerrit) error: failed to push some refs to 'ssh://snmishra@gerrit.ovirt.org:29418/ovirt-engine.git' I can ssh to gerrit.ovirt.org without password, so that seems to be setup correctly. git-review version is 1.17. I am on 'nullpointer' branch. Thanks in advance for your help. Regards Sharad Mishra

4 4

[Engine-devel] add host failed
by hkran＠linux.vnet.ibm.com 15 May '12

15 May '12

Hi, when I add a host to newly setup ovirt-engine,the system told me that install failed What can I do to figure out what is wrong with it? 2012-May-15, 11:51:37 Host mddd installation failed. Please refer to log files for further details.. 2012-May-15, 11:51:37 Failed to install Host mddd. Step: INSTALLER LIB; Details: deployUtil.py download failed. Pathname could not be resolved (verify computer/domain name).. 2012-May-15, 11:51:31 Installing Host mddd. Step: INSTALLER; Details: Test platform succeeded. 2012-May-15, 11:51:14 Installing Host mddd. Step: RHEV_INSTALL; Details: Connected to Host 9.115.118.194 with SSH key fingerprint: e1:bf:2a:93:f4:1e:4c:fe:22:ca:68:5d:36:06:3b:68. 2012-May-15, 11:51:12 Host mddd parameters were updated by admin@internal. 2012-May-15, 11:46:27 User admin@internal logged in. thanks!

2 1

[Engine-devel] reviewer needed for cleanup patchset
by Laszlo Hornyak 14 May '12

14 May '12

Hi, I need someone who could verify and/or approve my changeset to remove usage of the deprecated RefObject class. http://gerrit.ovirt.org/4235 http://gerrit.ovirt.org/4236 http://gerrit.ovirt.org/4237 http://gerrit.ovirt.org/4238 http://gerrit.ovirt.org/4239 Thank you, Laszlo

1 0

[Engine-devel] The correct way to create test dependencies between
by Allon Mureinik 14 May '12

14 May '12

Hi guys, I've recently come up with (what I believe is) an elegant way to mock the Config object using JUnit @Rules and Mockito (The gritty details can be found at http://gerrit.ovirt.org/4155) This presented me with another issue: On the one hand, the code depends on junit and mockito jars, which are not available in the main scope, only in the test scope. On the other hand, in vanilla Maven there is no dependency between tests of different projects, so placing this class in util's test would make it inaccessible to bll tests. The solution Maven suggests for these kind of issues is creating a test jar (http://maven.apache.org/guides/mini/guide-attached-tests.html) In addition to the regular jar the module produces, you'll get another -test jar, which other modules can depend on using the <type>test-jar</type>, which could of course be put in <scope>test</scope>. Before pushing forward with this approach, I'd like to know if anyone has a principle objection to it. Thanks, Allon

3 3

[Engine-devel] value too long for type character varying(20) in function "insertvds_interface"
by Itzik Brown 14 May '12

14 May '12

Hi, When running VDSM on host with Infiniband HCAs I get the following errors in /usr/share/jboss-as/standalone/log/server.log on the ovirt-engine host. WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (QuartzScheduler_Worker-17) ResourceManager::refreshVdsRunTimeInfo::Failed to refresh VDS , vds = 783eb0ac-9a91-11e1-a8e4-000c29de7759 : xena003, error = DataIntegrityViolationException: CallableStatementCallback; SQL [{call insertvds_interface(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}]; ERROR: value too long for type character varying(20) Where: SQL statement "INSERT INTO vds_interface(addr, bond_name, bond_type, gateway, id, is_bond, bond_opts, mac_addr, name, network_name, speed, subnet, boot_protocol, type, VDS_ID, vlan_id, mtu, bridged) VALUES(v_addr, v_bond_name, v_bond_type, v_gateway, v_id, v_is_bond, v_bond_opts, v_mac_addr, v_name, v_network_name, v_speed, v_subnet, v_boot_protocol, v_type, v_vds_id, v_vlan_id, v_mtu, v_bridged)" More detailed log: http://pastebin.com/AHD3di5i VDSM: From git repository commit 8a14b63fbbafbdb9ee7f85a9b702bff310f4f668 oVirt-engine: From git repository comit b24dddf094e08afa6a2032a487b37476318a872d Any suggestions? Regards, Itzik

5 5

[Engine-devel] PosixFS: GUI mock-ups have been updated
by Einav Cohen 13 May '12

13 May '12

Please review the mock-ups on the feature page: http://www.ovirt.org/wiki/Features/PosixFSConnection#Changes_in_GUI Comments are welcome. ---- Thanks, Einav

8 37

[Engine-devel] Questions on NIC hotplug (http://www.ovirt.org/wiki/Features/Design/DetailedHotlugNic)
by Yaniv Kaul 13 May '12

13 May '12

1. I wasn't sure from the description, but can one change the Network to which a NIC is connected to when it's up? (looks like a much lighter and reasonable action than unplugging-changing-plugging. Also very easy to do in the physical world). I'm quite sure there's a request for such a feature. 2. The REST API usage of 'activate' and 'deactivate' is certainly not inline with the UI's terminology, which is not only a shame, but is also (to me) confusing with setting the NIC's link up/down (which is possible in QEMU, not sure if we do it in oVirt). the UI concept of arrows also seem to support 'up'/'down' ... 3. Donno if it's just the mock ups, but lets try to use 'Network Card' over 'NIC' where possible. 4. I'm not sure why do we need the 'plug' and 'unplug' buttons, and can't do it in the 'Edit' dialog box. I think it's confusing. 5. How do I create a non-plugged NIC via the API? How do I see if a VM's NIC is plugged or not via the API? 6. SDK example would be great too.

3 2

[Engine-devel] Fwd: Supporting native USB in oVirt
by Oved Ourfalli 11 May '12

11 May '12

Hey, We are now working on adding the support for native USB devices on oVirt, and we have some difficulties. Please see the details/discussion below. Thank you for your help, Oved ----- Forwarded Message ----- From: "Itamar Heim" <iheim(a)redhat.com> To: "Michal Privoznik" <mprivozn(a)redhat.com> Cc: "Oved Ourfalli" <ovedo(a)redhat.com>, "Dave Allan" <dallan(a)redhat.com>, "Jiri Denemark" <jdenemar(a)redhat.com>, "Igor Lvovsky" <ilvovsky(a)redhat.com>, "Eli Mesika" <emesika(a)redhat.com>, "Hans de Goede" <hdegoede(a)redhat.com>, "Dan Kenigsberg" <danken(a)redhat.com>, "Andrew Cathrow" <acathrow(a)redhat.com> Sent: Wednesday, May 9, 2012 1:18:40 PM Subject: Re: Supporting native USB in oVirt On 05/09/2012 01:12 PM, Michal Privoznik wrote: > On 08.05.2012 09:19, Oved Ourfalli wrote: >> Hi, >> >> We are now working on adding the support for native USB devices on oVirt. >> As far as we understand, in order to use it we need to pass the following devices with the following restrictions (according to the EHCI spec): >> 1. EHCI USB controller - with the highest function number, #7. >> >> devices='{type:controller,device:usb,model:ich9-ehci1,address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x7}}' >> >> 2. 3 UHCI USB controllers, on the same bus and PCI slot as the EHCI controller. Set the multifunction bit to on, on the controller with function #0. >> >> devices='{type:controller,device:usb,model:ich9-uhci1,master:{startport:0},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x0,multifunction:on}}' >> devices='{type:controller,device:usb,model:ich9-uhci2,master:{startport:2},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x1}}' >> devices='{type:controller,device:usb,model:ich9-uhci3,master:{startport:4},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x2}}' >> >> 3. USB redirect devices (according to the needed number of USB slots, maximum 6) on the same bus, each one having a different port. >> >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:1}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:2}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:3}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:4}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:5}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:6}}' >> >> 4. If we want more than 6 USB slots, we need to have 2 EHCI controllers, and 6 UHCI controllers, that are consistent with the restrictions above, on different bus. >> (we need them to be on different bus, since the connection between the redirect devices and the controllers is the bus). >> >> According to Hans (cc-ed), if we let libvirt pick its own addresses, it will put each controller of the composite USB controller device on its own pci slot, which is a violation of the EHCI spec. > >> >> The problem is that the oVirt engine is not aware of addresses. They aren't managed by it. >> They are chosen automatically by libvirt, returned to the engine, and they saved in the engine database in order to provide the ability to retain the same PCI addresses after VM restart. >> >> So, in order to support the EHCI spec, oVirt will have to be aware of addresses, manage them (allocate them, check for collisions, update on every libvirt change regarding that, etc...). Obviously, it doesn't feel right, and in fact it is also not feasible, to manage these addresses in the oVirt domain. >> >> Is all the above correct, or are we missing something? >> If so, can you address the issues above, and provide the ability to manage these devices in libvirt? > > Let's have this conversation upstream (libvirt-list(a)redhat.com) Many > developers are there so if there's anything libvirt can do, we should > agree on concept there.

5 9

[Engine-devel] oVirt UserPortal changes
by Vojtech Szocs 10 May '12

10 May '12

Hi everyone, there were some important changes regarding UserPortal introduced recently, so I'll try to summarize the main points here. Please refer to [http://gerrit.ovirt.org/4273] for more details. - legacy (SmartGWT-based) UserPortal is no longer built/compiled during standard oVirt Maven build In case you still want to build/deploy original UserPortal: 1. uncomment "userportal-legacy" sections in ear/pom.xml 2. in frontend/webadmin/modules/pom.xml, include <module>userportal</module> within the <modules> section 3. use "gwt-user-legacy" profile when building oVirt - profile "gwt-user-gwtp" is replaced with "gwt-user", this triggers compilation of new (GWTP-based) UserPortal For example, to build oVirt with WebAdmin and new UserPortal: mvn clean install -Psetup,dep,gwt-admin,gwt-user - UserPortal host page URL has changed to: http(s)://<server-address>[:<port>]/UserPortal/org.ovirt.engine.ui.userportal.UserPortal/UserPortal.html This reflects the URL of original UserPortal. Feel free to contact me if you have any questions. Thanks, Vojtech

1 0

[Engine-devel] create_db_devel.sh failing
by Shireesh Anjal 10 May '12

10 May '12

Creating views... psql:create_views.sql:215: ERROR: column l.phisical_volume_id does not exist LINE 84: l.phisical_volume_id, ^ Failed to create database engine Regards, Shireesh

2 1

[Engine-devel] Stuck at the firewall.conf in vds_bootstrap
by Shu Ming 09 May '12

09 May '12

Hi, My vds_installer was stuck at running vds_bootstrap when I tried to add one host node in my ovirt-engine. For some reasons, the /tmp/firewall.conf.* file was not downloaded and that caused vds_bootstrap's failure. Is there any quick way to disable the "-f" option for vds_bootstrap in engine server or in host node? That will not allow vdsm to overwrite the firewall configurations in host. --- From the vds_install.xxxxxx.log in my host, here is the command where the vds_installer was stuck. /tmp/vds_bootstrap_1a9728df-e3b4-4d7b-8258-835038587bad.py -v -O cstl -t 2012-05-09T16:00:04 -f /tmp/firewall.conf.1a9728df-e3b4-4d7b-8258-835038587bad http://ovirt-engine-112:80/Components/vds/ 9.181.129.110 1a9728df-e3b4-4d7b-8258-835038587bad -- Shu Ming<shuming(a)linux.vnet.ibm.com> IBM China Systems and Technology Laboratory

1 1

[Engine-devel] oVirt Workshop at LinuxCon Japan 2012
by Leslie Hawthorn 09 May '12

09 May '12

Hello everyone, As part of our efforts to raise awareness of and educate more developers about the oVirt project, we will be holding an oVirt workshop at LinuxCon Japan, taking place on June 8, 2012. You can find full details of the workshop agenda on the LinuxCon Japan site. [0] Registration for the workshop is now open and is free of charge for the first 50 participants. We will also look at adding additional participant slots to the workshop based on demand. Attendees who register for LinuxCon Japan via the workshop registration link [1] will also be eligible for a discount on their LinuxCon Japan registration. Please spread the word to folks you think would find the workshop useful. If they have already registered for LinuxCon Japan, they can simply edit their existing registration to include the workshop. [0] - https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-work… [1] - http://www.regonline.com/Register/Checkin.aspx?EventID=1099949 Cheers, LH -- Leslie Hawthorn Community Action and Impact Open Source and Standards @ Red Hat identi.ca/lh twitter.com/lhawthorn

1 0

[Engine-devel] Storage Device Management in VDSM and oVirt
by Shireesh Anjal 09 May '12

09 May '12

Hi all, As part of adding Gluster support in ovirt, we need to introduce some Storage Device management capabilities (on the host). Since these are quite generic and not specific to Gluster as such, we think it might be useful to add it as a core vdsm and oVirt feature. At a high level, this involves following: - A "Storage Devices" sub-tab on "Host" entity, displaying information about all the storage devices* - Listing of different types of storage devices of a host - Regular Disks and Partitions* - LVM* - Software RAID* - Various actions related to device configuration - Partition disks* - Format and mount disks / partitions* - Create, resize and delete LVM Volume Groups (VGs) - Create, resize, delete, format and mount LVM Logical Volumes (LVs) - Create, resize, delete, partition, format and mount Software RAID devices - Edit properties of the devices - UI can be modeled similar to the system-config-lvm tool The items marked with (*) in above list are urgently required for the Gluster feature, and will be developed first. Comments / inputs welcome. Thanks, Shireesh

8 20

[Engine-devel] Using JBoss F17 RPMs
by Ofer Schreiber 09 May '12

09 May '12

As you probably know, we're aiming to use the new JBoss Fedora RPMs in the next version of oVirt. If anyone have some info (or patches, we love patches) on how to do this change right, we would like to know. Any input is appreciated. Thanks, --- Ofer Schreiber oVirt Release Manager

1 0

[Engine-devel] restapi: 'gluster' prefix
by Ori Liel 09 May '12

09 May '12

We are introducing Gluster functionality into ovirt-engine REST-API. Gluster entities are 'Volumes' and 'Bricks'. The question is: should they be called: 'volume'/'brick' or 'gluster_volume/gluster_brick'? (with or without the 'gluster' prefix)? There was a short conversation about this in a patch in Gerrit: http://gerrit.ovirt.org/#change,3918 Since there are conflicting opinions, I'm bringing it here for a resolution. Thanks, Ori.

5 16

[Engine-devel] auth issue
by Hui Kai Ran 09 May '12

09 May '12

Hi, all When I access the REST API like this ==================================== import urllib2 theurl = 'http://9.181.129.112:8080/api' username = 'admin@internal' password = 'abcd1234' # a great password passman = urllib2.HTTPPasswordMgrWithDefaultRealm() passman.add_password('ENGINE', theurl, username, password) authhandler = urllib2.HTTPBasicAuthHandler(passman) opener = urllib2.build_opener(authhandler) urllib2.install_opener(opener) pagehandle = urllib2.urlopen(theurl) ========================================= urlopen failed. then We do that another way like this, it is ok ======================================== import urllib2 import sys import re import base64 import xml.etree.ElementTree as etree username='admin@internal' password='abcd1234' request = urllib2.Request("http://9.181.129.112:8080/api") base64string = base64.encodestring('%s:%s' % (username, password)).replace('\n', '') request.add_header("Authorization", "Basic %s" % base64string) result = urllib2.urlopen(request) by catching the packets transfered, we found the response from ovirt-engine server as below for failing case: ================================================================ GET /api HTTP/1.1 Accept-Encoding: identity Host: 9.181.129.112:8080 Connection: close User-Agent: Python-urllib/2.7 HTTP/1.1 401 Unauthorized Server: Apache-Coyote/1.1 WWW-Authenticate: Basic realm = "ENGINE" Content-Type: text/html;charset=utf-8 Content-Length: 956 Date: Fri, 04 May 2012 09:18:06 GMT Connection: close Is there anything wrong for oVirt-engine? Thanks!

3 2

[Engine-devel] ovirt engine sync call
by Livnat Peer 09 May '12

09 May '12

Hi, If you have something you think should be discussed today in the engine core sync call let me know and we'll add it to the agenda. Thanks, Livnat

1 0

Re: [Engine-devel] [vdsm] RFD: NEW API getAllTasks
by Doron Fediuck 08 May '12

08 May '12

On 07/05/12 21:33, Adam Litke wrote: > The current APIs for retrieving all task information do not actually return all > task information. I would like to introduce a new API that corrects this and > other issues with the current API while preserving backwards compatibility with > ovirt-engine for as long as is necessary. > > The current APIs: > > getAllTasksInfo(spUUID=None, options = None): > - Returns a dictionary that maps a task UUID to a task verb. > - Despite having 'all' in the name, this API only returns tasks that have an > 'spm' tag. > - This call returns only one piece of information for each task. > - The spUUID parameter is deprecated and ignored. > > getAllTasksStatuses(spUUID=None, options = None): > - Returns a dictionary of task status information. > - Despite having 'all' in the name, this API only returns tasks that have an > 'spm' tag. > - The spUUID parameter is deprecated and ignored. > > > I propose the following new API: > > getAllTasks(tag=None, options=None): > - Returns a dictionary of task information. The info from both of the above > functions would be merged into a single result set. > - If tag is None, all tasks are returned. otherwise, only tasks matching the > tag are returned. > - The spUUID parameter is dropped. options is for future extension and is > currently not used. > > This new API includes all functionality that is available in the old calls. In > the future, ovirt-engine could switch to this API and preserve the current > semantics by passing tag='spm' to getAllTasks. Meanwhile, API users that really > want all tasks (gluster and the REST API) can get what they need. > > Thoughts on this idea? > (Adding engine-devel, as this relates to the engine API). AFAIR, in the original design (when a-sync tasks where introduced into vdsm), most (if not all) of the tasks were SPM tasks, and this is the reason for this behavior. Improving the API is welcomed. The suggested design should work. I'd like to verify: - Backwards compatibility works; so running engine's shouldn't be replaced. Dan: any news on this? - Going forward with potential changes in SPM concepts should be supported as well. Dan/Ayal/Livnat: do you think it works? ie- anything else needed than alternate 'spm' tag? -- /d "All computers wait at the same speed."

2 1

Re: [Engine-devel] Supporting native USB in oVirt
by Eli Mesika 08 May '12

08 May '12

----- Original Message ----- > From: "Dan Kenigsberg" <danken(a)redhat.com> > To: "Oved Ourfalli" <ovedo(a)redhat.com>, "Dave Allan" <dallan(a)redhat.com> > Cc: "Dave Allan" <dallan(a)redhat.com>, "Jiri Denemark" <jdenemar(a)redhat.com>, "Michal Privoznik" > <mprivozn(a)redhat.com>, "Itamar Heim" <iheim(a)redhat.com>, "Igor Lvovsky" <ilvovsky(a)redhat.com>, "Eli Mesika" > <emesika(a)redhat.com>, "Hans de Goede" <hdegoede(a)redhat.com>, "Andrew Cathrow" <acathrow(a)redhat.com> > Sent: Tuesday, May 8, 2012 11:41:25 AM > Subject: Re: Supporting native USB in oVirt > > On Tue, May 08, 2012 at 03:19:32AM -0400, Oved Ourfalli wrote: > > Hi, > > > > We are now working on adding the support for native USB devices on > > oVirt. > > As far as we understand, in order to use it we need to pass the > > following devices with the following restrictions (according to > > the EHCI spec): > > 1. EHCI USB controller - with the highest function number, #7. > > > > devices='{type:controller,device:usb,model:ich9-ehci1,address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x7}}' > > > > 2. 3 UHCI USB controllers, on the same bus and PCI slot as the EHCI > > controller. Set the multifunction bit to on, on the controller > > with function #0. > > > > devices='{type:controller,device:usb,model:ich9-uhci1,master:{startport:0},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x0,multifunction:on}}' > > devices='{type:controller,device:usb,model:ich9-uhci2,master:{startport:2},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x1}}' > > devices='{type:controller,device:usb,model:ich9-uhci3,master:{startport:4},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x2}}' > > I'd like to make it clear that the suggested API request Engine to > pass > a "master" attribute for the controller device, with a nested > dictionary > within. This makes sense, as I am certain that libvirt's modeling of > the > device has merits. However, AFAIK Engine does not do stuff like that > at > the momemnt. And should not do in future IMHO, this should be transparent to the engine core that should know only the USB device. > > > > > 3. USB redirect devices (according to the needed number of USB > > slots, maximum 6) on the same bus, each one having a different > > port. > > > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:1}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:2}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:3}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:4}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:5}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:6}}' > > > > 4. If we want more than 6 USB slots, we need to have 2 EHCI > > controllers, and 6 UHCI controllers, that are consistent with the > > restrictions above, on different bus. > > (we need them to be on different bus, since the connection between > > the redirect devices and the controllers is the bus). > > > > According to Hans (cc-ed), if we let libvirt pick its own > > addresses, it will put each controller of the composite USB > > controller device on its own pci slot, which is a violation of the > > EHCI spec. > > Is there an open libvirt bug for this? > > > > > The problem is that the oVirt engine is not aware of addresses. > > They aren't managed by it. > > They are chosen automatically by libvirt, returned to the engine, > > and they saved in the engine database in order to provide the > > ability to retain the same PCI addresses after VM restart. > > Yes, we should be able to trust libvirt's assignement, certainly for > the > masses of VMs. Few VMs of certain customer may want to tweak the > location of their devices. Maybe Engine does not need to expose this > feature at the moment (I think it is better that each device address > is > considered a "blob" by Engine), but the Engine/Vdsm API should > support > that. I know that in future we may need to tweak the device location. But still, the general principle of address allocation should be kept simple: If you send an address, this address is honored by libvirt If you don't, you will get a valid one from libvirt. I think that engine should not handle any addresses apart from persisting the address in DB. > > > > > So, in order to support the EHCI spec, oVirt will have to be aware > > of addresses, manage them (allocate them, check for collisions, > > update on every libvirt change regarding that, etc...). Obviously, > > it doesn't feel right, and in fact it is also not feasible, to > > manage these addresses in the oVirt domain. > > That's not obvious to me. Engine could have a hard-coded addresses > for > the usb device gang. Libvirt could arrange the rest of the devices > around it, so Engine should not worry about collisions. Libvirt's > stable > API relieves Engine from worrying about "every libvirt change > regarding > that" - it is libvirt responsibility to make sure that every future > libvirt version would handle the USB addresses properly. A big hole for future bugs that will fall between libvirt & engine responsibility. I don't like that idea of spreading responsibilities between separate components and prefer that addresses will have one manager that is obviously libvirt. > > > > > Is all the above correct, or are we missing something? > > If so, can you address the issues above, and provide the ability to > > manage these devices in libvirt? > > > > Regards, > > Oved >

1 0

Re: [Engine-devel] Supporting native USB in oVirt
by Oved Ourfalli 08 May '12

08 May '12

cc-ing engine-devel. Oved ----- Original Message ----- > From: "Hans de Goede" <hdegoede(a)redhat.com> > To: "Oved Ourfalli" <ovedo(a)redhat.com> > Cc: "Dave Allan" <dallan(a)redhat.com>, "Jiri Denemark" <jdenemar(a)redhat.com>, "Michal Privoznik" > <mprivozn(a)redhat.com>, "Itamar Heim" <iheim(a)redhat.com>, "Igor Lvovsky" <ilvovsky(a)redhat.com>, "Eli Mesika" > <emesika(a)redhat.com>, "Dan Kenigsberg" <danken(a)redhat.com>, "Andrew Cathrow" <acathrow(a)redhat.com> > Sent: Tuesday, May 8, 2012 10:48:32 AM > Subject: Re: Supporting native USB in oVirt > > Hi, > > On 05/08/2012 09:19 AM, Oved Ourfalli wrote: > > Hi, > > > > We are now working on adding the support for native USB devices on > > oVirt. > > As far as we understand, in order to use it we need to pass the > > following devices with the following restrictions (according to > > the EHCI spec): > > 1. EHCI USB controller - with the highest function number, #7. > > > > devices='{type:controller,device:usb,model:ich9-ehci1,address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x7}}' > > > > 2. 3 UHCI USB controllers, on the same bus and PCI slot as the EHCI > > controller. Set the multifunction bit to on, on the controller > > with function #0. > > > > devices='{type:controller,device:usb,model:ich9-uhci1,master:{startport:0},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x0,multifunction:on}}' > > devices='{type:controller,device:usb,model:ich9-uhci2,master:{startport:2},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x1}}' > > devices='{type:controller,device:usb,model:ich9-uhci3,master:{startport:4},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x2}}' > > > > 3. USB redirect devices (according to the needed number of USB > > slots, maximum 6) on the same bus, each one having a different > > port. > > > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:1}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:2}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:3}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:4}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:5}}' > > devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:6}}' > > > > To the best of my knowledge, the above is all correct. > > > 4. If we want more than 6 USB slots, we need to have 2 EHCI > > controllers, and 6 UHCI controllers, that are consistent with the > > restrictions above, on different bus. > > (we need them to be on different bus, since the connection between > > the redirect devices and the controllers is the bus). > > Correct, note that this may change in the future. Specifically I'm > thinking about > adding support for USB-2 hubs, and then have libvirt automatically > add new > redir-devices when all but one are in use. This is all just an idea > at the moment, > so don't count on it, I just wanted you to know that we are thinking > about making > it easier to make the number of devices dynamic in the future. So for > now you > could consider simply limiting redirection to max 6 devices. > > > According to Hans (cc-ed), if we let libvirt pick its own > > addresses, it will put each controller of the composite USB > > controller device on its own pci slot, which is a violation of the > > EHCI spec. > > Correct. > > > The problem is that the oVirt engine is not aware of addresses. They aren't managed by it. > > They are chosen automatically by libvirt, returned to the engine, and they saved in the engine database in order to provide the ability to retain the same PCI addresses after VM restart. > > > >So, in order to support the EHCI spec, oVirt will have to be aware of addresses, manage them (allocate them, check for collisions, update on every libvirt change regarding that, etc...). Obviously, it doesn't feel right, and in fact it is also not feasible, to manage these addresses in the oVirt domain. > > > > Is all the above correct, or are we missing something? > > If so, can you address the issues above, and provide the ability to manage these devices in libvirt? > Regards, > > Hans >

1 0

Re: [Engine-devel] Problem with detachment of host interface using ovirt-sdk
by Itzik Brown 07 May '12

07 May '12

Juan, I used the repository git://gerrit.ovirt.org/ovirt-engine-sdk Commit 3c721e60ab3af3ad07e1a20bc6fdbcdbc1344df0 The test script : #!/usr/bin/python import sys from ovirtsdk.api import API from ovirtsdk.xml import params OVIRT_ENGINE_SERVER = 'server1' OVIRT_ENGINE_PORT = '8080' OVIRT_ENGINE_USER = 'admin@internal' OVIRT_ENGINE_PASSWORD = 'password' url = 'http://%s:%s' % (OVIRT_ENGINE_SERVER, OVIRT_ENGINE_PORT) api = API(url = url, username = OVIRT_ENGINE_USER , password = OVIRT_ENGINE_PASSWORD) host = 'host1' if_name = 'eth4' net_name = 'net1' nic = api.hosts.get(name=host).nics.get(name=if_name) net = params.Network(name=net_name) act = params.Action(network=net) nic.detach(act) api.hosts.get(name=host).commitnetconfig() Thanks, Itzik

2 1

[Engine-devel] [Jenkins] new High priority bug in ovirt-engine
by Eyal Edri 06 May '12

06 May '12

fyi, a new HIGH priority bug was pushed to ovirt-engine, please check. bug details: http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/765/findbugsResult/HIGH… Found in file: VmPropertiesUtils.java:362, GC_UNRELATED_TYPES Introduced after these commits: engine: Create Gluster Volume enhancements (detail / gitweb) core: removing async tasks and compensation data on upgrade (detail / gitweb) engine: support versions for vm properties (detail / gitweb) webadmin: support versions for vm properties (detail / gitweb) core: Fixing bll tests (detail / gitweb) engine: New query to fetch Gluster Volume by ID (detail / gitweb) Eyal.

2 1

[Engine-devel] vds_bootstrap.py 's residency
by Shu Ming 03 May '12

03 May '12

Hi, I am checking the VDSM and ovirt-engine workspace for "vds_bootstrap.py" file. It was found that vds_bootstrap.py file was in VDSM workspace and was packaged into vdsm-bootstrap rpm package. Also, it was found that in the host installation process, host node will try to get the "vds_bootstrap.py" from the engine server. But "vds_bootstrap.py" is not included in any engine packages. Does that mean we should install vdsm-bootstrap package into engine server? Why not package this file into engine packages instead of vdsm packages? -- Shu Ming<shuming(a)linux.vnet.ibm.com> IBM China Systems and Technology Laboratory

3 2

Re: [Engine-devel] Logical network Usages collection problematic approach
by Eoghan Glynn 03 May '12

03 May '12

> The new design of logical network 'usages' collection came out a bit > problematic or shall i say annoying. > The idea is to send the entire collection elements every time a user > wants to update a single usage otherwise the missing elements will be > automatically removed from the collection. > > Example: > having <usages><usage>VM</usage><usages> > 1. in order to add 'display' usage to the collection i must send 'vm' > as well. > 2. to remove an element from the collection, i must send the entire > collection without the desired element > (note: in this case it is only one extra element for every update but > in other cases it could be much more) Yep, this seems to conflict with the general idiom around the interpretation of missing properties in a PUT representation - i.e. any properties omitted from the representation are ignored and not changed. > The solution should be: > <usages><vm>true</vm><display>false</display></usages> > That way we can send a single usage having different boolean text > without including the entire collection elements. I wonder would a POST/DELETE idiom be more natural, if the individual usages would be pressed into service as a psuedo-OID, e.g: POST .../networks/network_id/usages HTTP/1.1 <usage id="VM"/> 201 Created Location: .../networks/network_id/usages/VM <usage id="VM" href=".../networks/network_id/usages/VM"/> -- GET .../networks/network_id/usages HTTP/1.1 200 OK Location: .../networks/network_id/usages/VM <usages> <usage id="VM" href=".../networks/network_id/usages/VM"/> </usages> -- POST .../networks/network_id/usages HTTP/1.1 <usage id="display"/> 201 Created Location: .../networks/network_id/usages/display <usage id="display" href=".../networks/network_id/usages/display"/> -- GET .../networks/network_id/usages HTTP/1.1 200 OK <usages> <usage id="VM" href=".../networks/network_id/usages/VM"/> <usage id="display" href=".../networks/network_id/usages/display"/> <usages> -- DELETE .../networks/network_id/usages/VM 204 No Content -- GET .../networks/network_id/usages HTTP/1.1 200 OK <usages> <usage id="display" href=".../networks/network_id/usages/display"/> <usages> So from each usage would appear like a first class resource from the perspective of the creation/deletion idiom. If the client providing the ID is considered inconsistent, this could be a "name" child element instead, e.g.: POST .../networks/network_id/usages HTTP/1.1 <usage> <name>display</name> </usage> 201 Created Location: .../networks/network_id/usages/display <usage id="display" href=".../networks/network_id/usages/display"> <name>display</name> </usage> Cheers, Eoghan

2 2

[Engine-devel] Naming convention in db upgrade script temporary functions
by Eli Mesika 03 May '12

03 May '12

Hi >From now on, please use the prefix __temp_<function name> for temporary functions defined in a db upgrade scripts The reasons are 1) Each time that you have to rename your upgrade script after sync with master you have to rename the function as well 2) As a result, may function are pushed with a wrong suffix (for example upgrade 03_01_0950 had a function name suffix of 08200) Since the reason for that numbering was in the first place for avoiding dropping real installed functions, now you will have just to put in a temporary function created in an upgrade script just the prefix "__temp_" Hope that this will make handling upgrade scripts more accurate and less painful. This was documented as well at the oVirt db upgrade wiki page: http://www.ovirt.org/wiki/OVirt-database-upgrade-procedure (see section 1.5 Temporary Functions in Upgrade scripts)

1 0

[Engine-devel] Fwd: Checkstyle- Webadmin & userportal localization
by Alona Kaplan 02 May '12

02 May '12

Hi, Yesterday some changes were made in oVirt's checkstyle (http://gerrit.ovirt.org/#change,3760) 1. Renaming built-tools to build-tools-root and separating it into two packages: * checksyles- for checkstyle xml files. * ovirt-checkstyle-extension- for adding new (not built-in) checkstyle checks. 2. Adding to the checkstyle.xml a new check- NlsCheck, which fails the compilation in case non-externalized strings appear in the code. [To understand more about the need of this check, see http://gerrit.ovirt.org/#change,3612] >From now on, all strings in the web-admin/user-portal java code should be one of the following: - Externalized (in case the string should be localized) - Have a "//$NON-NLS-N$" comment next to them (in case the string shouldn't be externalized, e.g. HashName of a component) If there is a non externalized string in a web-admin/user-portal java file and there is no "//$NON-NLS-N$" comment next to it, mvn compilation will fail. Note: NlsCheck is currently configured to run only on web-admin/user-portal projects. If you want NlsCheck check to run on another project, please add the following to the configuration of the checkstyle in the project's pom file: <propertyExpansion>runNlsCheck=true</propertyExpansion> Alona.

3 2

[Engine-devel] Updating ovirt engine from 3.0 to the 3.1.0 version
by Shu Ming 02 May '12

02 May '12

Hi, I built a set of ovirt engine RPM packages from near the latest ovirt engine source code. However, when I try to access the engine server with URL "http://ovirt-engine-112:80", the browser displayed a blank page without http error returned. Any clue about what is going on here? Why didn't the engine administrator home page be shown? And the packages were also installed successfully in my target system, checked this by "rpm -q -a|grep engine". I) upgraded the packages to the 3.1 [root@ovirt-engine-112 ~]# rpm -q -a |grep engine ovirt-engine-restapi-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-dbscripts-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-log-collector-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-genericapi-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-backend-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-setup-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-jbossas-1.2-2.fc16.x86_64 ovirt-engine-jboss-deps-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-config-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-webadmin-portal-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-userportal-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-tools-common-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-image-uploader-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-notification-service-3.1.0_0001-1.8.fc16.x86_64 ovirt-engine-iso-uploader-3.1.0_0001-1.8.fc16.x86_64 gtk2-engines-2.20.2-2.fc15.x86_64 Step II) Then I used "engine-setup" to setup the engine. It seems that everything is ok, see the log below. ------------- [root@ovirt-engine-112 ~]# engine-setup Welcome to oVirt Engine setup utility HTTP Port [80] : HTTPS Port [443] : Host fully qualified domain name, note that this name should be fully resolvable [ovirt-engine-112] : ERROR: domain is not a valid domain name User input failed validation, do you still wish to use it? (yes|no): yes Password for Administrator (admin@internal) : Warning: Weak Password. Confirm password : Organization Name for the Certificate: cstl The default storage type you will be using ['NFS'| 'FC'| 'ISCSI'] [NFS] : Enter DB type for installation ['remote'| 'local'] [local] : Local database password : Warning: Weak Password. Confirm password : Should the installer configure NFS share on this server to be used as an ISO Domain? ['yes'| 'no'] [yes] : Mount point path: /iso-dom ERROR: mount point already exists in /etc/exports Mount point path: /iso-dom Display name for the ISO Domain: iso-domains Firewall ports need to be opened. You can let the installer configure iptables automatically overriding the current configuration. The old configuration will be backed up. Alternately you can configure the firewall later using an example iptables file found under /usr/share/ovirt-engine/conf/iptables.example Configure iptables ? ['yes'| 'no']: yes oVirt Engine will be installed using the following configuration: ================================================================= http-port: 80 https-port: 443 host-fqdn: ovirt-engine-112 auth-pass: ******** org-name: cstl default-dc-type: NFS db-remote-install: local db-local-pass: ******** nfs-mp: /iso-dom iso-domain-name: iso-domains config-nfs: yes override-iptables: yes Proceed with the configuration listed above? (yes|no): yes Installing: Configuring oVirt-engine... [ DONE ] Creating CA... [ DONE ] Editing JBoss Configuration... [ DONE ] Setting Database Configuration... [ DONE ] Setting Database Security... [ DONE ] Creating Database... [ DONE ] Updating the Default Data Center Storage Type... [ DONE ] Editing oVirt Engine Configuration... [ DONE ] Editing Postgresql Configuration... [ DONE ] Configuring the Default ISO Domain... [ DONE ] Configuring Firewall (iptables)... [ DONE ] Starting JBoss Service... [ DONE ] Handling HTTPD... [ DONE ] **** Installation completed successfully ****** (Please allow oVirt Engine a few moments to start up.....) Additional information: * SSL Certificate fingerprint: C6:01:83:93:4B:2C:2A:38:65:C8:49:C9:17:34:FE:4B:1C:10:D5:FF * SSH Public key fingerprint: 69:8c:bd:05:43:17:0a:43:a3:cc:62:7e:f7:be:0c:42 * A default ISO share has been created on this host. If IP based access restrictions are required, please edit /iso-dom entry in /etc/exports * The firewall has been updated, the old iptables configuration file was saved to /usr/share/ovirt-engine/conf/iptables.backup.011513-04282012_2225 * The installation log file is available at: /var/log/ovirt-engine/engine-setup_2012_04_28_01_13_01.log * Please use the user "admin" and password specified in order to login into oVirt Engine * To configure additional users, first configure authentication domains using the 'engine-manage-domains' utility * To access oVirt Engine please go to the following URL: http://ovirt-engine-112:80 [root@ovirt-engine-112 ~]# -- Shu Ming<shuming(a)linux.vnet.ibm.com> IBM China Systems and Technology Laboratory

2 8

[Engine-devel] Disk Cloning When Creating a VM via a Template
by Schoenbrun, Dustin 02 May '12

02 May '12

--_000_0A1534657992624AACDCA570F1D3E20003C29F05SACEXCMBX03PRDh_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Greetings, I know that floating disks are coming in the next version of oVirt, but in = the interim I want to know internally what the procedure is when a disk is = cloned when creating a VM from a template. I see the AddVmImages() method = in the AddVmFromTemplateCommand.java file, but could someone walk me throug= h exactly what is going on when the disk gets cloned? Thanks! -- Dustin --_000_0A1534657992624AACDCA570F1D3E20003C29F05SACEXCMBX03PRDh_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> Greetings,<o:p></o:p> <o:p> </o:p> I know that floating disks are coming in the next ve= rsion of oVirt, but in the interim I want to know internally what the proce= dure is when a disk is cloned when creating a VM from a template.  I s= ee the AddVmImages() method in the AddVmFromTemplateCommand.java file, but could someone walk me through exactly what is going on when the = disk gets cloned?  Thanks!<o:p></o:p> <o:p> </o:p> -- Dustin<o:p></o:p> <o:p> </o:p> </div> </body> </html> --_000_0A1534657992624AACDCA570F1D3E20003C29F05SACEXCMBX03PRDh_--

3 4

[Engine-devel] Logical network Usages collection problematic approach
by avi tal 01 May '12

01 May '12

Hi, The new design of logical network 'usages' collection came out a bit problematic or shall i say annoying. The idea is to send the entire collection elements every time a user wants to update a single usage otherwise the missing elements will be automatically removed from the collection. Example: having <usages><usage>VM</usage><usages> 1. in order to add 'display' usage to the collection i must send 'vm' as well. 2. to remove an element from the collection, i must send the entire collection without the desired element (note: in this case it is only one extra element for every update but in other cases it could be much more) The solution should be: <usages><vm>true</vm><display>false</display></usages> That way we can send a single usage having different boolean text without including the entire collection elements.

2 1

Re: [Engine-devel] [vdsm] reserve virtio-balloon device created by libvirt
by Itamar Heim 01 May '12

01 May '12

On 04/29/2012 04:19 PM, Dan Kenigsberg wrote: > On Sun, Apr 29, 2012 at 07:24:52AM -0400, Andrew Cathrow wrote: >> >> >> ----- Original Message ----- >>> From: "Dan Kenigsberg"<danken(a)redhat.com> >>> To: "Gal Hammer"<ghammer(a)redhat.com> >>> Cc: vdsm-devel(a)lists.fedorahosted.org >>> Sent: Sunday, April 29, 2012 7:19:10 AM >>> Subject: Re: [vdsm] reserve virtio-balloon device created by libvirt >>> >>> On Mon, Apr 23, 2012 at 04:00:55PM +0300, Gal Hammer wrote: >>>> On 23/04/2012 12:26, Mark Wu wrote: >>>>> Hi guys, >>>>> >>>>> I saw that an option to create balloon device was added by Gal in >>>>> http://gerrit.ovirt.org/1573 >>>>> I have a question about it. Why don we preserve the old default >>>>> behaviour? I know it's not supported by ovirt-engine now, but I >>>>> can't >>>>> figure out what will break if it's not disabled explicitly. So do >>>>> you >>>>> think we can just make use of the balloon device added by libvirt? >>>> >>>> We didn't change the old behavior. >>>> >>>> Libvirt creates by default a memory-balloon device, so vdsm >>>> defaults >>>> was to disable it by adding a "none"-type device. This was done >>>> because vdsm didn't include an option to add such device. >>>> >>>> My patch added an option to create a memory-balloon through vdsm. >>>> If >>>> the user didn't request to add the device, the behavior is same as >>>> before, disabling the memory-balloon. >>> >>> I feel that it would be best not to flip Vdsm's default at the >>> moment, >>> even though it is the opposite of libvirt's. I would consider to flip >>> them only after your (Mark's) patches are in, tested, and proven >>> worthwhile for the common case. >>> >>> Currently, without any management for the balloon, reserving a guest >>> PCI >>> device was deemed wasteful. >> >> On the other side of the fence >> - We know that we do need to do ballooning >> - In the (next?) release we'll end up adding this support >> - There's no harm (see next point) in adding the device now in fact it saves a config change on upgrade. > > Well, there is a surprise factor, for someone running a guest generated > in a previous version. Suddenly, after Vdsm upgrade, it would see an > additional device. At the least, I would like Vdsm to have a > configurable option to keep the old behavior. please take into consideration engine has an algorithm testing max number of devices and it should be aware of newly introduced devices by vdsm or it will overflow. > >> - While it takes up a PCI slot it's going to be very, very rare deployments that will ever see the limit, libvirt/virtmanager/virt-install has done this forever without seeing push back. > > > _______________________________________________ > vdsm-devel mailing list > vdsm-devel(a)lists.fedorahosted.org > https://fedorahosted.org/mailman/listinfo/vdsm-devel

3 2

Re: [Engine-devel] [vdsm] vdsm on openSuSE
by Doron Fediuck 01 May '12

01 May '12

On 30/04/12 19:23, Itamar Heim wrote: > On 04/30/2012 06:45 PM, Sascha Littel wrote: >> Am Montag, 30. April 2012, 16:45:12 schrieben Sie: >>> Hi Sasha, >>> This may be an issue of SSH authentication method. >>> Can you please check you SSH server in the host- >>> Password auth should be password and not Keyboard-interactive. >>> This may lead to SSH auth failure as you engine log indicates. >> Thanks dude this was the hint I need. I changed the PasswordAuthentication in >> /etc/ssh/sshd_config. Now I can add the vdsm into the oVirt engine host. Now >> the real work can beginn. > > Doron - can we catch this error and give this hint to users as something worth checking? > (added engine-devel, as this extends to the engine side). AFAICT, we get auth failure, with no reason. In order to handle it we can go in to ways (need to decide)- 1. Add the keyboard-interactive auth to Mina SSHD. There's a guy who added it[a] and we may try and ask for hints from him. I know that patches are welcomed there as well ;) 2. Try to diagnose the failure we get, or scan Mina's err / debug stream. I suspect we should be able to see something like: debug1: Authentications that can continue: password,publickey ... debug3: preferred gssapi-with-mic,publickey,keyboard-interactive,password So if server does not report 'password' as an option we could give a better auth-failure message. It will be nice if someone from our community could pick this up, and if not this would be a nice feature for one of the coming versions. [a] http://mail-archives.apache.org/mod_mbox/mina-dev/201112.mbox/%3CCACPdTxMmw… >>> >>>> Am Montag, 30. April 2012, 13:09:25 schrieben Sie: >>>>> On 04/30/2012 02:07 PM, Sascha Littel wrote: >>>>>> Am Montag, 30. April 2012, 05:04:09 schrieben Sie: >>>>>>> On 04/29/2012 10:24 PM, S. Littel wrote: >>>>>>>> Hi everybody, I'm working currently on a running version of vdsm >>>>>>>> 4.9.1 for openSuSE 11.3. I'm changing many lines in the start/stop >>>>>>>> scripts e.g. paths, rc commands. Most of this work looks fine but >>>>>>>> if I try to get a connection between the oVirt engine (runs on a >>>>>>>> openSuSE 12.1) and the vdsm host I get a ssl error. Also after >>>>>>>> setting ssl in vdsm.conf to false and changing the settings in >>>>>>>> oVirt engine database I still get this error. >>>>>>> >>>>>>> which settings are you changing in the db? >>>>>> >>>>>> I changed the seetings in the database with this 2 commands: >>>>> did you restart engine after changing these? >>>> >>>> Yes. I found this page in the oVirt Wiki: >>>> http://ovirt.org/w/index.php?title=OVirt_- >>>> _disable_SSL_in_VDSM&diff=3036&oldid=prev >>>> >>>>>> psql engine -U postgres -c "UPDATE vdc_options set option_value = >>>>>> 'false' where option_name = 'SSLEnabled'" >>>>>> >>>>>> psql engine -U postgres -c "UPDATE vdc_options set option_value = >>>>>> 'false' where option_name = 'UseSecureConnectionWithServers'" >>>>>> >>>>>>> UseSecureConnectionWithServers? >>>>>> >>>>>> Yes. >>>>>> >>>>>>>> So the general question, is there someone working on a openSuSE 11.3 >>>>>>>> or 11.4 version of vdsm? Or someone who has experience how to get >>>>>>>> it work? >>>>>>>> >>>>>>>> Regards >>>>>>>> >>>>>>>> Sascha Littel >>>>>> >>>>>> Here is the failure massage from the vdsm-reg.log I get on the vdsm >>>>>> host: >>>>>> >>>>>> SSLError: [Errno 185090050] _ssl.c:328: error:0B084002:x509 >>>>>> certificate routines:X509_load_cert_crl_file:system lib >>>>>> MainThread::DEBUG::::deployUtil::1413::root::getRemoteFile end. >>>>>> MainThread::DEBUG::::deployUtil::621::root::handleSSHKey start >>>>>> MainThread::ERROR::::deployUtil::614::root::restorecon >>>>>> /root/.ssh/authorized_keys failed >>>>>> >>>>>> And this is the failure message from engine.log on the oVirt engine >>>>>> host: >>>>>> >>>>>> ERROR [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper] >>>>>> (http--0.0.0.0-8443-1) Could not connect to server >>>>>> xen007.f1.aiges.net: Failed connecting >>>>>> >>>>>> to xen007.f1.aiges.net using given password! Please verify your >>>>>> password is >>>>>> >>>>>> correct and that the host accepts password-based authentication >>>>>> WARN [org.ovirt.engine.core.bll.AddVdsCommand] (http--0.0.0.0-8443-1) >>>>>> CanDoAction of action AddVds failed. >>>>>> Reasons:VDS_CANNOT_CONNECT_TO_SERVER,VAR__ACTION >>>>>> __ADD,VAR__TYPE__HOST >>>>>> >>>>>> Regards >>>>>> >>>>>> Sascha Littel >> >> > -- /d Never say "OOPS!" always say "Ah, Interesting!"

2 1