[Engine-devel] qemu machine type / datacenter machine version
by Ryan Harper
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
12 years, 6 months
[Engine-devel] Purpose of Attached Inactive/Maintenance state of export domain?
by David Jaša
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
12 years, 6 months
Re: [Engine-devel] qemu machine type / datacenter machine version
by Andrew Cathrow
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
12 years, 6 months
[Engine-devel] Backing up the DB
by Adam Litke
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
12 years, 6 months
[Engine-devel] VDSM REST API
by Adam Litke
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
12 years, 7 months
