- Devel - oVirt List Archives

reporting and removing unmanaged networks after deprecating org.ovirt.engine.core.common.action.VdcActionType#SetupNetworks
by Martin Mucha 03 Feb '15

03 Feb '15

Hi, I'd like to discuss how to properly report unmanaged networks and how to ask for their removal after org.ovirt.engine.core.common.action.VdcActionType#SetupNetworks is removed. We thought about several possibilities and so far the best one is following one. Reporting unmanaged networks on specific nic: ——————————————————————————————————————————————— We'd like to return new collection under: GET http://localhost:8080/api/hosts/{id}/nics/{id}/unmanagednetworks returning (reporting) unmanaged networks like this: <unmanaged_networks> <unmanaged_network> <nic_name>...</nic_name> <unmanaged_network_name>...</unmanaged_network_name> <vland_id>...</vland_id> </unmanaged_network> <unmanaged_network> ... </unmanaged_network> </unmanaged_networks> Removing unmanagedNetworks: ————————————————————————————— DELETE http://localhost:8080/api/hosts/{id}/nics/{id}/unmanagednetworks/{unmanaged… ======================= any ideas, hints, complaints, recommendations, confirmations are welcomed. Martin.

3 2

Get involved in oVirt project! February edition
by Sandro Bonazzola 03 Feb '15

03 Feb '15

Hi, do you want to get involved in oVirt project? Here are some bugs you can hopefully fix in less that one day or you can just try to reproduce providing info: Bug ID Whiteboard Status Summary 1059952 integration NEW hosted-engine --deploy (additional host) will fail if the engine is not using the default self-signed CA 1065350 integration NEW hosted-engine should prompt a question at the user when the host was already a host in the engine 1073421 integration NEW [RFE] allow additional parameter for engine-backup to omit audit_log data 1080823 integration NEW [RFE] make override of iptables configurable when using hosted-engine 1083104 integration NEW engine-setup --offline does not update versionlock Do you want something easier? Bug ID Whiteboard Status Summary 1174285 i18n NEW [de-DE] "Live Snapshot Support" reads "Live Snapsnot Support" 772931 infra NEW [RFE] Reports should include the name of the oVirt engine 1143817 integration NEW [TEXT ONLY] - Hosted Engine - Instructions for FQDN are not clear enough 1156060 integration NEW [text] engine admin password prompt consistency 1115059 network NEW Incomplete error message when adding VNIC profile to running VM 734120 storage NEW [RFE] VDSM: use virt-sparsify/zerofree to reduce image size Do you love "DevOps?", you count stable builds in jenkins ci while trying to fall a sleep? Then oVirt infra team is looking for you!, join the infra team and dive in to do the newest and coolest devops tools today! Here are some of our open tasks you can help with: https://fedorahosted.org/ovirt/report/1 You don't have programming skills, not enough time for DevOps but you want still to contribute? Here are some bugs you can take care of, also without writing a line of code: Bug ID Whiteboard Status Summary 1074545 docs NEW Error in API documentation: Create API object in python sdk 1099995 docs NEW Migrate to Hosted Engine How-To does not state all pre-reqs 1099998 docs NEW Hosted Engine documentation has several errors 1159784 docs NEW [RFE] Document when and where new features are available when upgrading cluster / datacenters 1074301 infra NEW [RFE] ovirt-shell has no man page 1120585 integration NEW update image uploader documentation 1120586 integration NEW update iso uploader documentation 1120588 integration NEW update log collector documentation Do you prefer to test things? We have some test cases[5] you can try using nightly snapshots[6] Do you want to contribute test cases? Most of the features[7] included in oVirt are missing a test case, you're welcome to contribute one! Is this the first time you try to contribute to oVirt project? You can start from here [1][2]! Don't know gerrit very well? You can find some more docs here [3]. Any other question about development? Feel free to ask on devel(a)ovirt.org or on irc channel[4]. [1] http://www.ovirt.org/Develop [2] http://www.ovirt.org/Working_with_oVirt_Gerrit [3] https://gerrit-review.googlesource.com/Documentation [4] http://www.ovirt.org/Community [5] http://www.ovirt.org/Category:TestCase [6] http://www.ovirt.org/Install_nightly_snapshot [7] http://www.ovirt.org/Category:Feature -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

CORS enabled for oVirt REST API
by Jenny Kang 02 Feb '15

02 Feb '15

Hello, As part of my OPW project, I'm trying to build a mobile web UI for oVirt but I'm having some troubles. I cannot access the oVirt REST API because it doesn't allow cross origin resource sharing (CORS). The only way to access the API is to host the UI on the same IP as the engine. If it is enabled then people would be able to run the mobile UI directly from the desktop without hosting it anywhere. Do you have any suggestions on how to access oVirt REST API from another host inside the browser? Any plans on enabling CORS on the REST API? Thank you! Cheers Jenny

5 7

[ANN] Async release for ovirt-engine is now available.
by Sandro Bonazzola 02 Feb '15

02 Feb '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The oVirt Team has just released a new version of ovirt-engine package for 3.5.1.1 that fixes a severe regression introduced in 3.5.1[1]. We recommend to all users who have already upgraded to 3.5.1 to update to this package. Thanks, [1] https://bugzilla.redhat.com/1185615 - NPE in AddDiskCommand during ovf volume creation. - -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUz1RxAAoJEHw3u57E4QAOZrEP/25VMKJFKB2mis6PXLC4LAE6 Z4c6gXNBFN+jMIDB7N4NIVH8YXN+wMm/iy2V16aG7MObFueIyHc2GuuFRKPdOh7k PL91aQsXolrfpU0nr7dTk6UvWIXb37NKr3IlIX2mc/03YqzA4fqOJGt53a2OSCWI bAI9TRlg1aZWdAEUQ0iBsJqvXw8GuFo+1HuuvIZhtK8zCEOd1djfmyYw89Upd7/k VpfCqatQL+Zl2dltO5tktlW5gUnmo6pBtZzKlAS1ajDhwb5NPGbFU/JlJ5ToWQD5 W6bZ84N4bGnG3LfLkYFWJhRWY2+5Vsj3Kry5mKoJZdUwjI+6LODi6uyzGCT1DegJ mUrPljMv0c0BBJzVcmiDPn2BXFLuXbkmvMgpbWqlBNSixhoXCKE8jdfSElEZ0AWZ Vav98YhNSSv1R4bf/DBj1SQVLNaW+BdU22kmqDsZK4futmOh3V38jTvTQUrpYFnu 8kYFj2GvUyC1R3W7PgswHnr1weWtEbZnvsLRBlXw/QLC2zgMUqrWlbGDKHD+e/I7 RJ0HYyUM1BIrpDjcawdA48rjm2O3Y58dUcferFJdMYzX595R1QvUo+05J9mYLJGE pLRtExjWvMGJfK30zV9LB4y6VvIbj+gwMK3NfN7vBkK7I311Rqqv3KDS6RheZECL ic6WURcJRolasO/uOH5Z =zAuW -----END PGP SIGNATURE-----

2 2

oVirt 3.6 Feature: Cumulative Network Usage Statistics
by Lior Vernia 01 Feb '15

01 Feb '15

Hello users and developers, Just put up a feature page for the aforementioned feature; in summary, to report total RX/TX statistics for hosts and VMs in oVirt. This has been requested several times on the users mailing list, and is especially useful for accounting in VDI deployments. You're more than welcome to review the feature page: http://www.ovirt.org/Features/Cumulative_RX_TX_Statistics Note that this only deals with network usage - it'll be great if we have similar features for CPU and disk usage! Yours, Lior.

3 5

[DB] Diffrent UUIDs for inserted data per installation
by Eli Mesika 29 Jan '15

29 Jan '15

Hi I am trying to cleanup all the data insertion to the engine DB and make it more general The main drive to that is DB version squashing that was done manually and therefor was error prone ... I know that both storage_pool_id (a.k.a DC) and vds_group_id (a.k.a Cluster) needs to get a different UUID per installation. But I had found that UUIDs are generated per installation for also : table | column/s ------------------------------------ [cpu_profiles] : id [gluster_services] : id [mac_pools] : id [permissions] : id, object_id [vm_device]: device_id, vm_id [vm_static] : vm_guid [vnic_profiles] : id Please let me know if any of the above should be generated using the uuid_generate_v1() function on each installation or we can have static IDs for those. Thanks Eli Mesika

4 4

Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot:
by Sandro Bonazzola 29 Jan '15

29 Jan '15

Upgrade job is failing while upgrading from 3.4.4 to 3.5.2-snapshot: 2015-01-27 15:02:46 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks plugin.execute:866 execute-output: ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150127150216-p4ixpj.log', '-u', 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A', '-J', '-q') stderr: psql:/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql:145: ERROR: type "command_entities" does not exist FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql 2015-01-27 15:02:46 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py", line 422, in _validateZombies self._clearZombieTasks() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py", line 156, in _clearZombieTasks 'Failed to clear zombie tasks. Please access support ' RuntimeError: Failed to clear zombie tasks. Please access support in attempt to resolve the problem 2015-01-27 15:02:46 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Setup validation': Failed to clear zombie tasks. Please access support in attempt to resolve the problem Please fix ASAP. Reference: http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/label… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

5 7

DAO test is failing on master
by Sandro Bonazzola 28 Jan '15

28 Jan '15

http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/1002… 15:50:12 Failed tests: 15:50:12 scheduleARecurringJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest): Unexpected exception occured -Failed to obtain DB connection from data source 'EngineDS': java.sql.SQLException: Connections could not be acquired from the underlying database! 15:50:12 scheduleAJob(org.ovirt.engine.core.utils.timer.DBSchedulerUtilQuartzImplTest): Unexpected exception occured -Failed to obtain DB connection from data source 'EngineDS': java.sql.SQLException: Connections could not be acquired from the underlying database! Not sure if it's infra or devel issue. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 8

[QE][ACTION REQUIRED] oVirt 3.6.0 status
by Sandro Bonazzola 28 Jan '15

28 Jan '15

Hi, I haven't many news for 3.6 this week: ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [1] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 22: 2015-05-19 Foreman 1.8.0: 2015-03-01 GlusterFS 3.7: 2015-04-29 OpenStack Kilo: 2015-04-30 QEMU 2.3.0: 2015-03-27 The tracker bug for 3.6.0 [2] currently shows no blockers. There are 530 bugs [3] targeted to 3.6.0. Excluding node and documentation bugs we have 489 bugs [4] targeted to 3.6.0. [1] http://goo.gl/9X3G49 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [3] https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_release%3A3.6.0%… [4] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Move bugs to ON_QA based on snapshot builds?
by Lior Vernia 28 Jan '15

28 Jan '15

Hello everyone, I wanted to suggest that we automate the change of oVirt 3.6 bug status from MODIFIED to ON_QA based on nightly snapshot builds. The motivation should be clear: when bugs are fixed on the master branch, the fix becomes readily available for verification as soon as the next snapshot is built (and there's indeed someone to verify on the master branch - the same person who was working on the master branch and opened the bug!). We currently only move them to ON_QA on milestone builds (e.g. alpha, beta), but I don't think that's right for an open source project - the status of bugs (targeted to the nearest release) should be up-to-date with the actual state of the master branch. We've encountered the problem testing features for 3.6 the last couple of weeks, and since it's gonna be a long version this situation will likely occur often. So far I've been moving bugs to ON_QA myself, but I don't really want to follow the snapshot builds manually (nor move the bugs to ON_QA as soon as they're merged, in case the snapshot build doesn't happen). The downside would be that bugs could be VERIFIED at an early point in the development, and later regressions could occur that would render the verification obsolete. But this could happen just the same between release milestones... Thoughts? Yours, Lior.

4 4