- Devel - oVirt List Archives

[ATN] - on going outage in phx lab infra
by Eyal Edri 17 Nov '14

17 Nov '14

fyi, there is an issue with the ovirt-engine server on phx lab, which causes some of the jenkins vms to be inaccessible. we've contacted the local team to help, but it might take some time since they are in the US. till then, jobs might be queued for a long time and possibly failing. If you have an urgent patch to commit and can't wait, please verify it locally (maybe bit more than you are used to) before merging. the jenkins won't block you on if it's an infra issue. we'll update once the outage is over. Eyal.

1 0

Migrating from Fedora 19 to Fedora 20 with oVirt 3.5.0
by Sandro Bonazzola 17 Nov '14

17 Nov '14

Hi, just finished testing migration path from F19 to F20 for systems running oVirt. F19 is going EOL one month after F21 release which is currently planned for December 2nd. If you're running oVirt on Fedora 19 I suggest you to do it once finished to upgrade oVirt to 3.5.0. I've saved some notes in the test request bug[1]: Bug 1131828 - Test upgrade path from Fedora 19 with oVirt 3.5.z to Fedora 20 Enjoy! [1] https://bugzilla.redhat.com/show_bug.cgi?id=1131828 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 6

howto: Profiling JavaScript
by Greg Sheremeta 16 Nov '14

16 Nov '14

Hopefully someone finds this helpful :) http://www.ovirt.org/Profiling_JavaScript -- Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme(a)redhat.com

2 1

DWH cannot gain hourly history data from db because of the bloody time problem.
by 张亚琪 16 Nov '14

16 Nov '14

hi everybody, Recently, I have tested oVirt Reports. And I encountered a problem about some reports that cannot show data. And then I setup the DWH development environment. I found maybe this reason for missing data is the AggregationToHourly3.5. When data from datacenter_samples_history were inserted to datacenter_hourly_history, u will find nothing happened. Because the select sql before inserting data reads： "SELECT history_id, > > history_datetime, > > datacenter_id, > > datacenter_status, > > minutes_in_status, > > datacenter_configuration_version > > FROM datacenter_samples_history > > WHERE *history_datetime >= '"+context.lastHourAggr+*"' > > AND history_datetime < '"+TalendDate.addDate(context.lastHourAggr, >> 1,"HH")+"' > > ORDER BY history_datetime, > > datacenter_id, > > datacenter_status" > > And then I queried the table of datacenter_samples_history & history_configuration (has the field of lastHourAggr) in the db of ovirt_engine_history. The results are as follows: ovirt_engine_history=# select * from history_configuration; > > var_name | var_value | var_datetime > > -------------------+-----------+------------------------ > > MinimalETLVersion | 3.5.0 | > > default_language | en_US | > > firstSync | false | 2014-10-13 19:42:00+08 > > lastDayAggr | | 2014-11-14 00:00:00+08 > > * lastHourAggr | | *2014-*11-15* 06:00:00+08 > > HourlyAggFailed | false | > > (6 rows) > > > ovirt_engine_history=# select *history_datetime* from > datacenter_samples_history; history_datetime ---------------------------- 2014-*11-13* 03:07:00.23+08 2014-11-13 03:08:00.238+08 2014-11-13 03:09:00.229+08 2014-11-13 03:10:00.221+08 2014-11-13 03:11:00.229+08 2014-11-13 03:12:00.221+08 2014-11-13 03:13:00.237+08 2014-11-13 03:14:00.22+08 2014-11-13 03:15:00.221+08 2014-11-13 03:16:00.238+08 2014-11-13 03:17:00.238+08 > Obviously， history_datetime < lastHourAggr , the data will never be inserted to the datacenter_hourly_history. And the place where I bold is the root cause of the error. Then , I try to update the *lastHourAggr *in the table of history_configuration. Reports works successfully. However, the lastHourAggr will change to 2014-11-15 afterwards. But u know Today is 2014-11-14 ! I have no idea about why the value of lastHourAggr is 2014-11-15. Would u help me solve this problem. Thanks a lot !

2 1

oVirt Node 3.5 build available for testing
by Fabian Deutsch 14 Nov '14

14 Nov '14

Hey, finally we reached a stage again where we can provide an oVirt Node. The following oVirt Node ISO contains the oVirt 3.5.0 packages. Please go ahead, test it and provide feedback in case of issues. https://fedorapeople.org/~fabiand/node/3.5/ovirt-node-iso-3.5.0.ovirt35.201… To learn something more about oVirt Node please visit http://www.ovirt.org/Node http://www.ovirt.org/Quick_Start_Guide#Install_oVirt_Node Please note that this is still an pre-release, and we are aware that there are still issues with the hosted-engine part of Node. But this part will see some (already pending updates) in the near future. Greetings fabian

1 0

Error while building ovirt upstream
by Shubhendu Tripathi 13 Nov '14

13 Nov '14

Hi, Today I rebased with master and getting below error while building the engine. [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ vdsbroker --- [INFO] Compiling 312 source files to <Home>/work/ovirt-engine/backend/manager/modules/vdsbroker/target/classes [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] error: error reading <Home>/.m2/repository/org/ovirt/vdsm-jsonrpc-java/vdsm-jsonrpc-java-client/1.1.0-SNAPSHOT/vdsm-jsonrpc-java-client-1.1.0-SNAPSHOT.jar; error in opening zip file [INFO] 1 error Kindly help resolving the same. Regards, Shubhendu

3 6

[VOTE NEEDED] oVirt meetings schedule change proposal
by Sandro Bonazzola 13 Nov '14

13 Nov '14

Hi, last oVirt sync meeting was skipped and the previous one was at risk due to a bit of confusion on DST changes. oVirt sync meeting is the only meeting we have bound to UTC without DST changes. Current scheduled meeting list is available here: http://www.ovirt.org/Meetings#Meeting_Time_and_Place We don't have a reference timezone, we use: UTC, EDT, Asia/Jerusalem. The UTC time zone has been deemed obsolete. It has been replaced by Etc/UTC and it doesn't use DST. EDT is currently not observed in North America since DST isn't active. Locations are currently observing EST instead. Asia/Jerusalem is following DST changes. I suggest to unify the reference timezone. Since it seems that using UTC causes issues in re-scheduling other local timezone tasks, I guess best solution is to follow the DST changes. As nearest to UTC following DST I suggest Europe/London as timezone. Comments are welcome. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[QE][ACTION NEEDED] oVirt 3.5.1 RC status - branching
by Sandro Bonazzola 12 Nov '14

12 Nov '14

Hi, We're going to start composing oVirt 3.5.1 RC on *2014-11-25 08:00 UTC* from 3.5 branch. In order to stabilize the release a new branch ovirt-engine-3.5.1 will be created from the same git hash used for composing the RC. Maintainers: - Please be sure that 3.5 snapshot allow to create VMs before *2014-11-24 15:00 UTC* - Please be sure that no pending patches are going to block the release before *2014-11-24 15:00 UTC* - If any patch must block the RC release please raise the issue as soon as possible. A bug tracker [1] has been opened and shows 2 open blocker: Bug ID Whiteboard Status Summary 1142710 integration POST Volume creation failed while deploying Hosted Engine on iSCSI 1160846 sla NEW Can't add disk to VM without specifying disk profile when the storage domain has more than one disk profile The following bugs have been keyworded as Regression and not marked as blockers: Bug ID Whiteboard Status Summary 1106435 infra POST [AAA] builtin kerbldap provider does not show error if search fails 1138144 storage NEW [BLOCKED]Failed to autorecover storage domain after unblocking connection with host 1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError There are still 162 bugs [2] targeted to 3.5.1. Excluding node and documentation bugs we still have 134 bugs [3] targeted to 3.5.1. Maintainers / Assignee: - Please review bugs marked as Regression and add to blocker if they're real regressions. - Please add the bugs to the tracker if you think that 3.5.1 should not be released without them fixed. - Please update the target to 3.5.2 or later for bugs that won't be in 3.5.1: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] Community: - If you're testing oVirt 3.5 nightly snapshot, please add yourself to the test page [5] [1] http://bugzilla.redhat.com/1155170 [2] http://goo.gl/7G0PDV [3] http://goo.gl/6gUbVr [4] http://www.ovirt.org/OVirt_3.5.1_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.5.1_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

[ANN] oVirt snapshots available for testing on EL7
by Sandro Bonazzola 12 Nov '14

12 Nov '14

The oVirt team is pleased to announce that the 3.5 and master nightly snapshot repositories[1] have been update including builds for Red Hat Enterprise Linux 7 (or similar) for testing. Please note that mirrors may need usually one day before being synchronized. If you want to be sure to use latest rpms and don't want to wait for the mirrors, you can edit /etc/yum.repos.d/ovirt-3.5-snapshot.repo or /etc/yum.repos.d/ovirt-master-snapshot.repo commenting the mirror line and removing the comment on baseurl line. Thanks to everyone who will join us testing oVirt! If you're testing oVirt 3.5 nightly snapshot, please add yourself to the test page [2] [1] http://www.ovirt.org/Install_nightly_snapshot [2] http://www.ovirt.org/Testing/oVirt_3.5.1_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

[QE][ACTION REQUIRED] oVirt 3.6.0 status
by Sandro Bonazzola 12 Nov '14

12 Nov '14

Hi, Release criteria discussion started on 2014-10-22 and should end today as per current release process [1]. Current options are: 1) keeping the same release criteria we had for 3.5 [2] 2) review the proposed changes [3] and prepare new release criteria for 3.6 Release management for 3.6.0 has been created [4] The key milestones for this release must be scheduled: Key Milestones Release criteria discussion start: 2014-10-22 Release criteria ready: 2014-11-12 Feature freeze: 60 Days before release First Test Day: 45 days before release Release Candidate: 30 days before release Release: 6 months after oVirt 3.5.0 release Two different proposals have been made about above scheduling [5]: 1) extend the cycle to 10 months for allowing to include a large feature set 2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7 Feature proposed for 3.6.0 must now be collected in the 3.6 google doc [9] and reviewed by maintainers. A tracker bug for 3.6.0 has been created [6] and currently shows no blockers. There are 399 bugs [7] targeted to 3.6.0. Excluding node and documentation bugs we have 379 bugs [8] targeted to 3.6.0. [1] http://www.ovirt.org/Release_process [2] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria [3] http://lists.ovirt.org/pipermail/devel/2014-September/008695.html [4] http://www.ovirt.org/OVirt_3.6_Release_Management [5] http://lists.ovirt.org/pipermail/users/2014-November/028875.html [6] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [7] http://goo.gl/zwkF3r [8] http://goo.gl/ZbUiMc [9] http://goo.gl/9X3G49 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0