- Devel - oVirt List Archives

[Engine-devel] VM Payload feature
by Oved Ourfalli 10 Apr '12

10 Apr '12

Hey all, Continuing the discussion about Aeolus instance data injection to a VM (http://lists.ovirt.org/pipermail/engine-devel/2012-January/000423.html) we propose a new VM Payload feature. The following wiki page contains a description page of the feature. http://www.ovirt.org/wiki/Features/VMPayload Please read and review. There are several approaches there, and we wish to head your opinions and thoughts about them. Once we agree on an approach, we will start designing. Thank you, Oved

10 18

[Engine-devel] Is there a preferred workflow when adding additional error messages to VDSM _and_ Engine?
by Lee Yarwood 10 Apr '12

10 Apr '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, I'm currently working on a patch to correct the logic used by vdsm when reviewing the logical and physical block size of physical volumes [1]. Once/If this is approved I'd like to look into making the exceptions thrown from vdsm and the errors displayed within engine more descriptive. Before I start throwing patches into gerrit I was wondering *if* there is a preferred workflow when adding additional exceptions and error messages across both projects. For example, committing changes to vdsm before engine, engine before vdsm or both at the same time. I'm also wondering if there is a way to say that vdsm gerrit changeid x relies on engine gerrit changeid y etc? Thanks in advance, Lee - -- Lee Yarwood Software Maintenance Engineer Red Hat UK Ltd 200 Fowler Avenue IQ Farnborough, Farnborough, Hants GU14 7JP Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson(USA), Charlie Peters (USA) GPG fingerprint : A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPgFjGAAoJELymbjP2ci12MScIANRBXgWPSjeSZvSM2+bZmDrD FefJfxMcCQFtTqWYePXIxFgqeeRcFc57+6alExBRU2g9nKZJEIPn2vj640XSTGlt n5T4ItED1IVydzuEXFOAvgaTmZfKzTQkxQWp8QgL6pC7cYgnp2nL7gkbkedx1JyI gCgCGomrHeWP2++vUS8UjtCccZdTJiOiWqoH2sBCKgEVcmFMgvYREK6hTou4DHU4 DcpureWuLvM4HWUlyfl37eXQOmy66A7uHGp3xF5sykQZ9aozaiMFjSoCqQOEVqO6 jHRnsQB6FfF/xU+F/UQK5PKZOm7e+KvrMjhIDfR+/DX3t0rkrtc69gg2O6duy4o= =vdud -----END PGP SIGNATURE-----

4 3

[Engine-devel] deprecating auto-detection of Ldap provider types
by Roy Golan 09 Apr '12

09 Apr '12

auto-detection featured few bugs lately which convinced me that it must be deprecated/removed from the code in favor of adding manual set of the provider type. main reasons for that: a. the provider is type is known by the user b. identifying a provider by the rootDSE attributes is error-prone, not reliable etc... specially if the support matrix is growing c. auto-detection logic is duplicated (and not shared) between the backend code and the manage-domains tool (nevermind the reasons now) A manual set of the provider type requires a new configuration field for a domain and the question is the upgrade path which may look like * set the provider type to default Active Directory (because its more likely to be the provider type) * things not working - use the engine-manage-domains and choose the provider type. * optionally - keep the auto-detection (of the tool only!) if user wants to use it. your suggestion and thoughts... Thanks, Roy

5 7

[Engine-devel] qemu machine type / datacenter machine version
by Ryan Harper 08 Apr '12

08 Apr '12

I was playing around with ovirt-engine datacenter definitions and I seems that the capatibility version in the gui controls the qemu machine type specified (3.0 -> pc-0.14). I was wondering where that's configured setup. I grepped through my deployed system and saw a hit here: [root@f16-engine ovirt-engine]# rpm -qf /usr/share/ovirt-engine ovirt-engine-3.0.0_0001-1.2.fc16.x86_64 [root@f16-engine ovirt-engine]# grep -nri "pc-0.14" * db-backups/tmprN1EDt.sql:12119:INSERT INTO vdc_options (option_id, option_name, option_value, version) VALUES (236, 'EmulatedMachine', 'pc-0.14', '3.0'); db-backups/tmpj4XRCI.sql:12138:INSERT INTO vdc_options (option_id, option_name, option_value, version) VALUES (236, 'EmulatedMachine', 'pc-0.14', '3.0'); dbscripts/upgrade/03_00_0530_update_EmulatedMachine_config_to_pc.sql:2:select fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0'); dbscripts/create_db.sh.log:7571:select fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0'); dbscripts/create_db.sh.log:25529:select fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0'); dbscripts/create_db.sh.log:43487:select fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0'); Is there any way to define different compatibiilty versions or edit that? If I've got a new end-point running qemu-kvm that doesn't have pc-0.14 defined (Say RHEL6.x) the machines won't lauch when you specific -M pc-0.14. Thoughts? -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ryanh(a)us.ibm.com

3 4

[Engine-devel] Purpose of Attached Inactive/Maintenance state of export domain?
by David Jaša 08 Apr '12

08 Apr '12

Hi, As I'm using export domain to shove VMs and templates betweend RHEV setups pretty often lately, I'm wondering about $SUBJ. What is it good for? Is it just for situation when main Data storage domain goes down? If so, I'll probably file a RFE to be able to get the domain from Unattached to Active state and vice versa via single click as having to wait half minute before I can do a successive click is quite a big annoyance. David -- David Jaša, RHCE SPICE QE based in Brno GPG Key: 22C33E24 Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24

2 1

Re: [Engine-devel] qemu machine type / datacenter machine version
by Andrew Cathrow 08 Apr '12

08 Apr '12

It is only configured in the database today. A good short term solution would be exposing this in the engine-config tool to save users having to hack the database, and potentially set this during setup. But long term we need to incorporate the notion of per VM config versions, right now we take the config version from the cluster, which isn't the best approach. We need to merge the two concepts - host/cluster capabilities and VM config version. Itamar Heim <iheim(a)redhat.com> wrote: On 04/05/2012 06:27 PM, Ryan Harper wrote: > I was playing around with ovirt-engine datacenter definitions and I > seems that the capatibility version in the gui controls the qemu machine > type specified (3.0 -> pc-0.14). I was wondering where that's > configured setup. > > I grepped through my deployed system and saw a hit here: > > [root@f16-engine ovirt-engine]# rpm -qf /usr/share/ovirt-engine > ovirt-engine-3.0.0_0001-1.2.fc16.x86_64 > [root@f16-engine ovirt-engine]# grep -nri "pc-0.14" * > db-backups/tmprN1EDt.sql:12119:INSERT INTO vdc_options (option_id, option_name, option_value, version) VALUES (236, 'EmulatedMachine', 'pc-0.14', '3.0'); > db-backups/tmpj4XRCI.sql:12138:INSERT INTO vdc_options (option_id, option_name, option_value, version) VALUES (236, 'EmulatedMachine', 'pc-0.14', '3.0'); > dbscripts/upgrade/03_00_0530_update_EmulatedMachine_config_to_pc.sql:2:select fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0'); > dbscripts/create_db.sh.log:7571:select fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0'); > dbscripts/create_db.sh.log:25529:select fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0'); > dbscripts/create_db.sh.log:43487:select fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0'); > > Is there any way to define different compatibiilty versions or edit that? If I've got a new end-point running qemu-kvm that doesn't have pc-0.14 defined (Say RHEL6.x) the machines won't lauch when you specific -M pc-0.14. > > Thoughts? > > check this and reply to it: http://lists.ovirt.org/pipermail/users/2012-March/001439.html _______________________________________________ Engine-devel mailing list Engine-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel

2 1

[Engine-devel] Backing up the DB
by Adam Litke 07 Apr '12

07 Apr '12

Hi all, I have a working development environment for ovirt-engine and I want to verify someone else's gerrit change. Is there a documented proceedure for backing up the engine db so that, after checking out the new code and updating the db schema, I can revert to my old code and DB (schema and data). Thanks! -- Adam Litke <agl(a)us.ibm.com> IBM Linux Technology Center

7 12

[Engine-devel] VDSM REST API
by Adam Litke 06 Apr '12

06 Apr '12

Hi all, At the oVirt Workshop in Beijing I learned about how the ovirt-shell dynamically discovers: the collections, resource schemas, and allowed actions based on an RSDL file and API xsd schema. I am working on a REST API for vdsm and would like to make my API compatible with the ovirt-engine api such that the same ovirt-shell program could work with either the engine api or the vdsm api. There are many differences between ovirt-engine and vdsm (namely that one is implemented in Java and the other in Python). I think the easiest way to test whether this is possible is to try and create a new, minimalist REST service with python Cherrypy. Such a service would have a root URL with no collections or actions. From my understanding I will need to write the following files: /api - A basic XML representation of the API root resource /api?schema - An xsd that describes the simple API /api?rsdl - An rsdl (XML file) that describes the available links for /api, I want to start with something dead-simple: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <api> <messages> <message id='foo' href='bar'> Hello from vdsm! </message> </messages> </api> Once I can use ovirt-shell to list messages and show messages I will be happy to build on it. Can anyone help me figure out the minimal xsd and rsdl that would be needed for such an API to be consumable by ovirt-shell? Thanks for your help! -- Adam Litke <agl(a)us.ibm.com> IBM Linux Technology Center

3 2

[Engine-devel] Please review: All In One Feature page
by Alex Lourie 04 Apr '12

04 Apr '12

Hi All I've written a new wiki page [1] for a feature we've developed, called All in One. This allows configuring VDSM on the same host with rhevm (ovirt) automatically during setup. Please review and provide feedback :-) Thanks [1] http://www.ovirt.org/wiki/Feature/AllInOne

5 10

[Engine-devel] [Jenkins] Warning - the following commits inserted 2 new HIGH priority bugs into into engine code
by Eyal Edri 04 Apr '12

04 Apr '12

core: Ovirt-engin-backend: Run Once does not send Attach CD/Floppy (detail / gitweb) webadmin: Changing a call at webamin from UpdateVmDiskCommand to HotPlug/HotUnPlugCommand (detail / gitweb) core : Changes for required error messages in order to supposrt a new commands (detail / gitweb) core : Introducing HotPlug and HotUnplug commands (detail / gitweb) url: http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/491/ Both in class: VmInfoBuilder.java http://jenkins.ovirt.org/job/ovirt_engine_find_bugs/491/findbugsResult/new/… Please check, Eyal Edri oVirt Infra Team

1 0