- Devel - oVirt List Archives

[Engine-devel] UX: Display VM Downtime in the UI
by Adam Litke 19 Dec '13

19 Dec '13

Hi UX developers, My recent change: http://gerrit.ovirt.org/#/c/22429/ adds support for tracking the time a VM was last stopped and presenting it in the REST API. I would also like to expose this information in the admin portal. This feature has been requested by end users and is useful for managing lots of VMs which may not be used frequently. My idea is to change the 'Uptime' column in the VMs tab to 'Uptime / Downtime' or some equivalent and more compact phrasing. If the VM is Up, then last_start_time would be used to calculate uptime. If the VM is Down, then last_stop_time would be used to calculate downtime. This helps to make efficient use of the column space. I am not sure how column sorting is being implemented, but if we combine uptime and downtime into a single column we have an opportunity to provide a really intuitive sort where the longest uptime machines are at the top and the longest downtime machines are at the bottom. This could be accomplished by treating uptime as a positive interval and downtime as a negative interval. Questions for you all: - Do you support the idea of changing the Uptime column to include Downtime as well or would you prefer a new column instead? - Is there a better heading for the new column or is 'Uptime / Downtime' good enough? - How should we handle sorting? Thanks for your input!

3 6

[Engine-devel] Can not login to gerrit with Yahho Id
by Eli Mesika 19 Dec '13

19 Dec '13

Hi I have a Yahoo ID I am using to register to gerrit. It stops working today, I am getting in to Yahoo account but not getting to gerrit Is that a new issue in gerrit ? Please help Thanks Eli

1 0

[Engine-devel] Increasing the HTTP keep alive to 30 seconds
by Juan Hernandez 19 Dec '13

19 Dec '13

Hello, We have an RFE that has been open for quite a long time requesting an increase of the keep alive time in the HTTP communications between the GUI applications and the web server: https://bugzilla.redhat.com/833799 Implementing it should be as simple as modifying the setup application so that it includes the modified KeepAlive directives in the web server configuration, something like this: KeepAlive on KeepAliveTimeout 30 Is someone with knowledge of the setup application interested on taking this? Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

2 1

[Engine-devel] No-arg constructor required by default in backend "common" module's classes
by Vojtech Szocs 18 Dec '13

18 Dec '13

Hi guys, in order to avoid potential errors related to GWT RPC serialization, a recent patch [1] introduced the requirement for no-arg constructor in backend "common" module's classes. [1] http://gerrit.ovirt.org/#/c/21733/ (Even though we're planning to move away from GWT RPC to using REST API, for the time being, this should prevent RPC related errors caused by missing no-arg constructor, which are sometimes hard to trace.) For a select few classes *not* involved in RPC communication, you can add these in checkstyle-suppressions.xml file. Vojtech

1 0

[Engine-devel] [jenkins] Request to be able to create jobs for jsonrpc project
by Piotr Kliczewski 18 Dec '13

18 Dec '13

I am working on new project vdsm-jsonrpc-java which is async client library using json which will be used for communication between engine and vdsm. I would like to create jenkins jobs for this project but have no account nor authority to do so. Can you please +1 my request? Thanks, Piotr

2 1

[Engine-devel] Polling vs Pushing engine events
by Sven Kieske 18 Dec '13

18 Dec '13

Hi, we got the following problem: we create / start / stop hole vms /data centers / storage etc (basically: everything ovirt can handle via REST-API) But if you want to know e.g. the status of a vm (or anything) you need to constantly poll the API. This is not what we desire to do, as it does not scale very well (e.g. polling 100 vms). Is there a standardized way of pushing information from the engine? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

4 5

[Engine-devel] GUI widget for adding/removing entries
by Lior Vernia 17 Dec '13

17 Dec '13

Hello, Lately a patch has been merged that introduces a widget for adding/removing entries (e.g. network interfaces when creating/editing a VM): http://gerrit.ovirt.org/#/c/19530/ This kind of widgets is becoming common in oVirt, so the idea is to make adding one easy rather than copying & pasting code. AddRemoveRowWidget takes care of the plus/minus button logic, disabling an entry that hasn't been edited, and the arranging in rows. In order to use it, one is required to override a couple of abstract methods that are dependent upon the specific entry implementation. An example may be found in ProfilesInstanceTypeEditor, which handles adding/removing network interfaces in the new/edit VM dialog. Yours, Lior.

4 14

[Engine-devel] oVirt 3.3.2 RC
by Sandro Bonazzola 16 Dec '13

16 Dec '13

The oVirt team is pleased to announce that the 3.3.2 Release Candidate is now available in ovirt-updates-testing [1]. We planned to release it on Wed Dec 18th 2013 but it will probably be postponed to next week for allowing more testing on the RC. The release date will be decided in next oVrit sync meeting on Wed Dec 18th. Feel free to join us testing it[2] and verifying the bugzilla entries actually under verification [3]. Release notes for this update are available on the wiki [4]. A new oVirt Node build will be available soon as well. [1] http://resources.ovirt.org/releases/updates-testing [2] http://www.ovirt.org/Testing/Ovirt_3.3.2_testing [3] http://red.ht/19NoJKf [4] http://www.ovirt.org/OVirt_3.3.2_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Engine-devel] [jenkins] dao tests broken
by Eyal Edri 16 Dec '13

16 Dec '13

fyi, dao tests are broken for some time now, who can look into it? current failing tests are: Tests in error: testAdUserConstrcutor(org.ovirt.engine.core.common.users.VdcUserTest): org.ovirt.engine.core.common.businessentities.LdapUser.setPassword(Ljava/lang/String;)V testAdUserAndFalseBooleanConstrcutor(org.ovirt.engine.core.common.users.VdcUserTest): org.ovirt.engine.core.common.businessentities.LdapUser.setPassword(Ljava/lang/String;)V testAdUserAndTrueBooleanConstrcutor(org.ovirt.engine.core.common.users.VdcUserTest): org.ovirt.engine.core.common.businessentities.LdapUser.setPassword(Ljava/lang/String;)V getUserFQN(org.ovirt.engine.core.common.users.VdcUserTest): org.ovirt.engine.core.common.businessentities.LdapUser.setPassword(Ljava/lang/String;)V http://jenkins.ovirt.org/job/ovirt_engine_dao_unit_tests/5446/console looks like it started after commit : http://jenkins.ovirt.org/job/ovirt_engine_dao_unit_tests/5438/ core: scheduling: handle cpu load duration (detail / gitweb) Eyal.

5 5

[Engine-devel] [engine-devel] instance type as top-level entity
by Tomas Jelinek 16 Dec '13

16 Dec '13

Hey all, I have started to work on the instance types[1] again and hit an issue. Since the instance types are supposed to be top-level entities (e.g. without the connection to DC/Cluster) but they are modeled as templates it is not possible to store them to DB since the DB constraints violation on vm_static table (e.g. the vds_group_id has to be unique and point to an existing vds_group). So, I see 4 options: 1: drop the constraints on the vm_static.vds_group_id (the vds_groups_vm_static constraint) (most simple approach but would open the door to some issues which are now guard on the DB level) 2: do the same magic [well, hacks :) ] as with the "blank" template which is in the same situation (not exactly a nice solution to have the instance types wired to one specific cluster just to satisfy the constraint but return them all the time) 3: do not store this data in vm_static but create some new table called e.g. instance_type which would contain all of the fields from vm_static which are needed by it (actually the best approach AFAIK but to do it correctly it would require some more refactoring to do some hierarchy of tables and not copy the fields from table to table) 4: make the instance types not top-level (e.g. bound to specific DC/Cluster) (would bring some issues for example with the default instance types which should be present for all the DC/Clusters) Thoughts? Thank you, Tomas [1]: http://www.ovirt.org/Features/Instance_Types

3 4