September 2014 - Devel - oVirt List Archives

Stable branch gerrit hook and Related-To: bug
by Martin Sivak 21 Sep '14

21 Sep '14

Hi, I would like to ask if it might be possible for the gerrit hook to stop giving -1 to patches that do not have bug-url, but have related-to. The reason for this is that I have a rather large patchset that is adding a new feature. No single patch by itself fixes the referenced bug and there are also patches that are not related to the feature itself, but were backported because they did some refactoring that was needed for the code to apply and/or work properly. -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ

9 19

Change functionality of some DB common functions
by Eli Mesika 21 Sep '14

21 Sep '14

Hi Up to now , using some common DB functions of delete/rename/change type of column were exiting silently if you had a typo in the table/column name We had a DWH patch made by Shirly that had changed column type for several columns but one of the changes had a typo in the column name This was only found bu QE and potentially could passed QE and found only in production. I had changes those functions not to allow such cases in patch http://gerrit.ovirt.org/#/c/32959 I think that this is a minor change for developers that will get exceptions now for such mistakes , but the benefit for production is clear and obvious to me. I will be glad to get your feedback on this patch Thanks Eli Mesika

2 1

Propose Shirly Radco as DWH & Reports Maintainer.
by Yaniv Dary 20 Sep '14

20 Sep '14

Hi, Shirly Radco has contributed many features, bug fixes and documentation enhancements for DWH & Reports and has taken a major role in the project progress and management in the last 9 months. I would like to propose Shirly as a DWH & Reports projects Maintainer. I would like to thank Shirly for her great contribution and hope she will keep up the good work! --- Yaniv Dary BI Software Engineer Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary(a)redhat.com IRC : Yaniv D

5 4

bug 1041569 question was: ovirt-d] [QE][ACTION REQUIRED] oVirt 3.5.0 status (fwd)
by R P Herrold 19 Sep '14

19 Sep '14

I was running down the open ovirt bugs, and notice this one, which has an outlink to a post by you (Eric) on a mailing lsit last month > And the following dependencies still open: > Bug 1041569 - [NFR] libvirt: Returning the watermark for all > the images opened for writing https://www.redhat.com/archives/libvir-list/2014-August/msg00207.html wherein you refer to a 'watermark'. To me as a non-lingo aware (as to libvirt / libguestfs) developer, a watermark is a pattern overlaid onto an image (a pattern placed on the glue side of a postage stamp, or a 'DRAFT" notice on a document) I _think_ you are referring to a 'high water mark' limit which, if exceeded would result in content being lost (there is mention of ENOSPC) Is this accurate? If so, isn't this information filesystem specific and so something which the outsider 'container' cannot and should be expected to reliably know? (I am thinking here of inode exhaustion even when a Linux type FS seemingly has space per: du ; the problem is worse with a 'sparse' capable filesystem in play; and seems wholly unanswerable with a Windows FS or some other variant) I don't see how the hypervisor could accurately ever know this without 'cracking open' and asking the inside tenant .. and for privacy and data integrity / security reasons, the hypervisor should not ever be doing this Thanks -- Russ herrold

2 1

OVIRT-3.5-TEST-DAY-3: NUMA support
by Greg Padgett 19 Sep '14

19 Sep '14

Hi, I was slated to test NUMA support along with Adam Litke. As we had to borrow a NUMA-enabled host (thanks Gilad) to perform the tests, I coordinated with Adam to get the testing done and ended up using the host most of the day. Tests performed: Basic sanity test: create/start/stop/destroy VMs with varying NUMA configurations. The running VMs appeared to have the correct NUMA node assignments (presuming the libvirt xml was respected), and everything worked as expected. REST API: GET operations succeeded and appeared correct for the various NUMA-related VM and Host resources. I didn't get the opportunity to perform the POST/PUT/DELETE operations. UI: I built the engine and webadmin with some pending patches to get this functionality. I was cautioned that the patches were fairly new, but nevertheless I was able to create VMs with varying NUMA configurations, and didn't notice any regressions. Thanks, Greg

1 0

[Mentor Opportunities] Outreach Program for Women
by Brian Proffitt 19 Sep '14

19 Sep '14

All: I am pleased to announce that oVirt will be participating in the next round of the GNOME Foundation's Outreach Program for Women, an internship program designed to foster more gender-diverse participation within the free and open source software communities. Currently, we have at least one intern position lined up for the program (with hopefully more if our board members decide to sponsor more internships). Right now, we are seeking developers who would be willing to act as mentors from the oVirt project. Details about the program and mentor requirements are available on our OPW landing page[1]. Essentially, this program is very much like the Google Summer of Code project, where we match up interns with projects within oVirt that they can finish up during this round of OPW (December 9, 2014 to March 9, 2015). There is one key difference, that mentors should note: the application process is very interactive, and potential interns are expected to work with program mentors even as they are applying. oVirt mentors will work with participants before and after the application process to help integrate potential interns into the oVirt ecosystem, and continue working with accepted interns as the program progresses. Interested mentors should do the following: 1. Check out the application process[2] for interns so you can see what they are required to do and, in turn, know what will be expected from mentors. 2. Visit the Information for Mentors section[3] of the oVirt OPW page to walk through the process. 3. Fill in the Mentor Information section[4] with your name and contact info. If you have any questions about the program, please let me know. We would like to have mentors lined up as soon as possible, given the upcoming application deadline and the need to have applicants involved with oVirt as soon as possible. We had a pretty good experience with Google Summer of Code, and it will be very cool to continue a similar experience with this new internship program! Peace, Brian -- Brian Proffitt Community Liason oVirt Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC [1] http://www.ovirt.org/Outreach_Program_for_Women [2] http://wiki.gnome.org/OutreachProgramForWomen#Application_Process [3] http://www.ovirt.org/Outreach_Program_for_Women#Information_for_Mentors [4] http://www.ovirt.org/Outreach_Program_for_Women#Mentor_Information

1 0

[ENGINE] thoughts about LinqUtils
by Yair Zaslavsky 19 Sep '14

19 Sep '14

Hi Engine developers (and others :) ), I would like to share some thoughts & questions with you about the future of LinqUtils 1. Location of LinqUtils Currently LinqUtils resides at utils. However, as LinqUtils contains some non engine related code, I think it should be moved to the new uutils (universal utils) project. uutils was introduced during the work on AAA, in order to provide a set of utilities that are not engine related, and hopefully in the future will be published as a separate artifcat on maven central (Alon, feel free to correct me here :) ) 2. The name LinqUtils - Linq comes from c#. I think these days are way behind us (3 years or so now?) i would like to suggest renaming the class. CollectionUtils? Any other suggestions are more than welcome Thanks, Yair

11 24

[QE][ACTION REQUIRED] oVirt 3.5.0 status
by Sandro Bonazzola 19 Sep '14

19 Sep '14

Hi, We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Monday morning Go / No go Meeting decisions) on Monday 2014-09-22. Maintainers: - Please be sure that 3.5 snapshot satisfy release criteria[9] - Please be sure that no pending patches are going to block the release - If any patch must block the GA release please raise the issue as soon as possible. - If any packages need a rebase please raise the issue as soon as possible. - Be aware that packages that doesn't need a rebase must be re-built with final release versioning from the RC2 tag. The bug tracker [1] shows the following proposed blockers to be reviewed: Bug ID Whiteboard Status Summary 1144079 integration POST local engine-reports-setup does not write conf file to allow accessing reports from engine 1138340 sla POST vdsm relies on unsupported 'min_guarantee' VM configuration parameter 1143873 network NEW firewall-cmd gets stuck when run as superVDSM subsubprocess 1142256 integration NEW remote engine-reports-setup does not write conf file to allow accessing reports from engine And the following dependencies still open: Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images opened for writing The following bugs are keyworded as Regression and not marked as blockers[10] Bug ID Whiteboard Status Summary 1142709 infra NEW Trying to deploy hosted-engine via iSCSI device fails 1138144 storage NEW 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 1110444 ux POST bookmark selection does not work on first try 1138314 virt NEW Fail to start vm with payload. Feature freeze is now effective, and branch has been created. All new patches must be backported to 3.5 branch too. Features completed are marked in green on Features Status Table [2] There are still 86 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 62 bugs [4] targeted to 3.5.0. More in detail [5]: Whiteboard NEW ASSIGNED POST Total docs 13 1 0 14 gluster 8 4 2 14 i18n 0 0 1 1 infra 0 1 2 3 integration 3 1 2 6 network 0 1 0 1 node 7 4 0 11 ppc 2 0 4 6 sla 12 0 7 19 virt 8 0 3 11 Total 53 12 21 86 Maintainers / Assignee: - Please ensure that completed features are marked in green on Features Status Table [2] - If you find a blocker bug please remember to add it to the tracker [1] - Please fill release notes, the page has been created here [6] - Please review results from Third Test Day on the etherpad [7] and on the mailing lists - Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0: it will ease gathering the blocking bugs for next releases. Community: - You're welcome to join us testing last release candidate or nightly builds and getting involved in oVirt Quality Assurance[8] [1] http://bugzilla.redhat.com/1073943 [2] http://goo.gl/4SuYdE [3] http://red.ht/1pVEk7H [4] http://red.ht/1zT2mSq [5] http://red.ht/1q7SqNL [6] http://www.ovirt.org/OVirt_3.5_Release_Notes [7] http://etherpad.ovirt.org/p/3.5-testday-3 [8] http://www.ovirt.org/OVirt_Quality_Assurance [9] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29 [10] http://goo.gl/uavikG Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 3

OVIRT-3.5-TEST-DAY-3: CPU SLA for capping
by Martin Perina 19 Sep '14

19 Sep '14

Hi, I tested the support to limit CPU utilization of hosts. Setting it up in the GUI worked correctly, but for running VM settings are ignored. I used XMLRPC protocol to avoid [1]. To simulate VM CPU utilization I used stress tool [2]. Testing steps: 1. Create a VM with the same number of CPUs as Host 2. Create CPU type QoS in DC and set the limit to desired value 3. In Cluster create new CPU profile with above QoS and remove the default CPU profile 4. Start the VM and execute (N is a number of CPUs in VM) stress --cpu N 5. Connect to Host and execute sar -u 1 10 No matter what the limit was set to (1, 50, 100), host CPUs were always utilized to 100%. So I create bug to cover this [3]. Martin Perina [1] http://bugzilla.redhat.com/1142851 [2] http://people.seas.harvard.edu/~apw/stress/ [3] http://bugzilla.redhat.com/1144280

1 0

Re: [ovirt-devel] Broken dependencies: vdsm
by Balamurugan Arumugam 18 Sep '14

18 Sep '14

[Adding vdsm-devel/ovirt-devel] ----- Original Message ----- > From: "Kaleb S. KEITHLEY" <kkeithle(a)redhat.com> > To: "Balamurugan Arumugam" <barumuga(a)redhat.com>, "Dan Kenigsberg" <danken(a)redhat.com> > Cc: "Lalatendu Mohanty" <lmohanty(a)redhat.com>, buildsys(a)fedoraproject.org, "Development discussions related to > Fedora" <devel(a)lists.fedoraproject.org>, glusterfs-owner(a)fedoraproject.org > Sent: Monday, September 15, 2014 9:27:03 PM > Subject: Re: Broken dependencies: vdsm > > Posting to -devel because I can't post to vdsm-owner or virt-maintenance. > > On 09/15/2014 10:09 AM, Kaleb S. KEITHLEY wrote: > > gluster server. AFAIK it's a mistake for vdsm to have these as > > dependencies. > > Correcting myself. glusterfs-cli is okay, and should, AFAIK, be in > RHEL6, although I'm not seeing that it is. > > glusterfs-server is not in RHEL6, and won't ever be in RHEL6, and AFAIK > it's a mistake for vdsm to have it as a dependency. > Looks like to me too. Lets check with vdsm-devel/ovirt-devel? Regards, Bala

2 1

OVIRT-3.5-TEST-DAY-3: replace XML-rpc with JSON-rpc
by Francesco Romani 18 Sep '14

18 Sep '14

Hi everyone of this test day I played with the new JSON-rpc transport, which is enabled by default. I set up from scratch two hypervisors running on RHEL 6.5, while Engine was running on F19. I created everything from scratch and tested all the flows I known good enough, including less-then-common stuff. The list includes creating storage domains, VMs, hotplug/unplug disks, snapshots, migration, hibernation and dehibernation. On top of that, I prepared an environment to run more tests, that included create 200 VMs, started/stopped 100 of them to test. I kept an eye on the logs other than Engine. Everything I tried went OK, and logs look good to me. I run in a few hiccups, which I mention for the sake of completeness: - VDSM refused to start or run VMs initially: libvirt config included relics from past environment on the same box, not JSON-rpc fault. Fixed with new config and (later) a reboot. - Trying recovery, Engine took longer than expected to sync up with VDSM. I have not hard data and feeling is not enough to file a BZ, so I didn't. - Still trying recovery, one and just one time Engine had stale data from VDSM (reported two VMs as present which actually aren't). Not sure it was related to JSON-rpc, can't reproduce, so not filed a BZ. Since I need to continue profiling anyway (better late than never I guess), I include a couple of test to see if JSON-rpc makes any difference to JSON-rpc. Results will be posted on devel(a)ovirt.org and/or on the oVirt wiki. -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

3 5

Testday 3 results
by Doron Fediuck 18 Sep '14

18 Sep '14

Hi All, I was glad to see the amount of participation yesterday. Kudus to everyone who took a part in making oVirt 3.5.0 better! Here are some stats from yesterday's logs: Top 10 active IRC users[1]: 206 Zordrak 177 winfr34k 44 sbonazzo 35 fromani 24 msivak_ 19 Sven 19 jhernand 18 tiraboschi 16 danken 16 capri Bugzilla: 1. Bugs by team: http://goo.gl/RXjm8k 2. Bugs by reporter: http://goo.gl/c89Sdy 3. Results: - 96 new bugs - Top 5 reporters: sbonazzo(a)redhat.com 15 redhat.bugzilla(a)jdmp.org.uk 6 tnisan(a)redhat.com 5 glazarov(a)redhat.com 4 info(a)netbulae.com 4 Please alert if there are any 3.5.0 blockers. Thanks, Doron [1] Excluding the weekly meeting part as it wasn't relevant.

1 0

OVIRT-3.5-TEST-DAY-3: Documentation
by Sandro Bonazzola 17 Sep '14

17 Sep '14

Hi, my assignment for third test day was on Documentation- 3.5 feature pages: Check what's missing and what's wrong the feature documentation looks outdated as far as I've been able to check it. More in detail: http://www.ovirt.org/Features/Gluster_Volume_Capacity test result: failed bug opened: Bug 1142616 - Feature page: Gluster Volume Capacity needs to be updated http://www.ovirt.org/Features/AAA_3.5 test result: failed bug opened: Bug 1142623 - Feature page: AAA 3.5 needs to be updated http://www.ovirt.org/Fence_kdump test result: failed bug opened: Bug 1142628 -Feature page: Fence kdump needs to be updated http://www.ovirt.org/Features/Design/JsonRpc test result: failed bug opened: Bug 1142639 - Feature page: Features/Design/JsonRpc needs to be updated http://www.ovirt.org/Features/AdvancedForemanIntegration test result: failed bug opened: Bug 1142649 - Feature page: AdvancedForemanIntegration needs to be updated http://www.ovirt.org/Features/Design/DetailedHostPMProxyPreferences test result: failed bug opened: Bug 1142652 - Feature page: DetailedHostPMProxyPreferences needs to be updated http://www.ovirt.org/Features/PMHealthCheck and http://www.ovirt.org/Features/Design/DetailedPMHealthCheck test result: failed bug opened: Bug 1142662 - Feature page: PMHealthCheck needs to be updated http://www.ovirt.org/Custom_Fencing test result: failed bug opened: Bug 1142665 - Feature page: Custom Fencing needs to be updated www.ovirt.org/Features/Design/CommandCoordinator test result: failed bug opened: Bug 1142671 - Feature page: CommandCoordinator needs to be updated http://www.ovirt.org/Features/oVirt_Windows_Guest_Tools test result: passed additional notes: maybe a test case explaining how to test the feature will be useful http://www.ovirt.org/Features/Self_Hosted_Engine_iSCSI_Support test result: passed http://www.ovirt.org/Features/Separate-DWH-Host test result: failed bug opened: Bug 1142783 - Feature page: Separate DWH Host needs to be updated http://www.ovirt.org/Features/Separate-Reports-Host test result: passed additional notes: consider creating TestCase page from testing section http://www.ovirt.org/Features/WebSocketProxy_on_a_separate_host test result: passed additional notes: consider creating TestCase page from testing section http://www.ovirt.org/Features/Network_Custom_Properties test result: passed additional notes: consider creating TestCase page from testing section http://www.ovirt.org/Features/NeutronVirtualAppliance test result: passed additional notes: feature is not complete, it should be retargeted to 3.6. additional notes: consider creating TestCase page from testing section http://www.ovirt.org/Features/Node/GenericNodeRegistration test result: failed bug opened: Bug 1142803 - Feature page: Generic Node Registration needs to be updated http://www.ovirt.org/Node_Hosted_Engine test result: failed bug opened: Bug 1142806 - Feature page: Node Hosted Engine needs to be updated http://www.ovirt.org/Feature/oVirtAppliance test result: failed bug opened: Bug 1142814 - Feature page: oVirt Appliance needs to be updated http://www.ovirt.org/Features/CPU_SLA test result: passed additional notes: feature is not complete, it should be retargeted to 3.6. additional notes: please create TestCase page for providing info on how to test the feature http://www.ovirt.org/Features/blkio-support test result: failed bug opened: Bug 1142822 - Feature page: Support blkio SLA features needs to be updated http://www.ovirt.org/Features/Optaplanner test result: passed additional notes: it's a tech preview in 3.5 additional notes: please create TestCase page for providing info on how to test the feature additional notes: please also use feature template: http://www.ovirt.org/Feature_template http://www.ovirt.org/Features/NUMA_and_Virtual_NUMA test result: failed existing bug: Bug 1069303 - OVIRT35 - [RFE] Provide NUMA support in oVirt additional notes: feature is not complete, it should be retargeted to 3.6. additional notes: please create TestCase page for providing info on how to test the feature additional notes: please also use feature template: http://www.ovirt.org/Feature_template http://wiki.ovirt.org/Features/oVirtSchedulerAPI#REST test result: failed bug opened: Bug 1142846 - Feature page: oVirt Scheduler API needs to be updated At this point I have proxy error while connecting to oVirt site, so I think that's all on my side for today testing. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

OVIRT-3.5-TEST-DAY-3: backup/restore and disaster recovery
by Simone Tiraboschi 17 Sep '14

17 Sep '14

Hi, today I had to test how to recover a broken system using backup/restore tool [1] or disaster recovery procedure [2]. Unfortunately I really had a lot of troubles just trying to setup my test environment so no good news on that side. I was using two host: one for the engine, the other as an hypervisor. Both with latest fedora 19 updates. For a fault of mine I add oVirt 3.5 RC2 repository on the engine host but I forgot to do the same on the second host and it generates a lot of problems. I installed the ovirt engine, release 3.5 RC2, on the first host and from the web admin UI I was trying to add the second host. I discovered that using jsonrpc mode it doesn't check/enforce or at least advice about cluster compatibility level failing silently. I opened a bug for that [3]. Than I start using xmlrpc mode that suggested me to downgrade the cluster compatibility mode to 3.3; I did that but it still failed adding my host apparently due to SELinux or Gluster errors; I opened a bug also for that [4]. So I understood that I forgot to add oVirt 3.5 repo on the second host; I opened a bug against host-deploy with install rpms but doesn't handle RPM repos. On my opinion it would make the setup more user friendly or at least more controllable for us [5]. So I added the yum repository and I tried again; I noticed that host-deploy upgrades vdsm stuff but it wasn't enough to get 3.5 compatibility level so, investigating it a bit, I noticed that host-deploy upgrades vdsm stuff but completely ignores libvirt one generating a nonworking setup; I opened a bug also for that [6]. At the end, after manually upgrade libvirt rpms I was able to add my host. Than I briefly tested backup/restore and disaster recovery procedures which seam to work as expected. So, at the end, on my opinion we have still to work a bit more to make the setup more user friendly. Simone [1] http://www.ovirt.org/Ovirt-engine-backup [2] http://www.ovirt.org/Features/ImportStorageDomain#Disaster_Recovery_flows [3] https://bugzilla.redhat.com/show_bug.cgi?id=1142945 [4] https://bugzilla.redhat.com/show_bug.cgi?id=1142941 [5] https://bugzilla.redhat.com/show_bug.cgi?id=1142953 [6] https://bugzilla.redhat.com/show_bug.cgi?id=1142959

1 0

[QE][ACTION REQUIRED] oVirt 3.5.0 status
by Sandro Bonazzola 17 Sep '14

17 Sep '14

Hi, We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Test Day results and oVirt Sync Meeting decisions) on Monday 2014-09-22. Maintainers: - Please be sure that 3.5 snapshot satisfy release criteria[9] - Please be sure that no pending patches are going to block the release - If any patch must block the GA release please raise the issue as soon as possible. - If any packages need a rebase please raise the issue as soon as possible. - Be aware that packages that doesn't need a rebase must be re-built with final release versioning from the RC2 tag. The bug tracker [1] shows the following proposed blockers to be reviewed: Bug ID Whiteboard Status Summary 1142256 integration POST engine-setup does not write conf file to allow accessing reports And the following dependencies still open: Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images opened for writing Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt block storage The following bugs are keyworded as Regression and not marked as blockers[10] Bug ID Whiteboard Status Summary 1135909 infra POST [Event log] Wrong warning about available swap memory of host [1023MB], when actually host has [1024MB] memory size 1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError 1110444 ux POST bookmark selection does not work on first try 1138314 virt NEW Fail to start vm with payload. Feature freeze is now effective, and branch has been created. All new patches must be backported to 3.5 branch too. Features completed are marked in green on Features Status Table [2] There are still 83 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 58 bugs [4] targeted to 3.5.0. More in detail [5]: Whiteboard NEW ASSIGNED POST Total docs 14 1 0 15 gluster 9 4 2 15 i18n 0 0 1 1 integration 1 1 1 3 node 6 4 0 10 ppc 2 0 4 6 sla 5 0 8 13 storage 0 0 3 3 virt 12 0 5 17 Total 49 10 24 83 Maintainers / Assignee: - Please ensure that completed features are marked in green on Features Status Table [2] - If you find a blocker bug please remember to add it to the tracker [1] - Please fill release notes, the page has been created here [6] - Please review results from Third Test Day [7] - Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0: it will ease gathering the blocking bugs for next releases. Community: - You're welcome to join us testing next release candidate and getting involved in oVirt Quality Assurance[8] [1] http://bugzilla.redhat.com/1073943 [2] http://goo.gl/4SuYdE [3] http://red.ht/1pVEk7H [4] http://red.ht/1zT2mSq [5] http://red.ht/1q7SqNL [6] http://www.ovirt.org/OVirt_3.5_Release_Notes [7] http://etherpad.ovirt.org/p/3.5-testday-3 [8] http://www.ovirt.org/OVirt_Quality_Assurance [9] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29 [10] http://goo.gl/uavikG Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

5 6

OVIRT-3.5-TEST-DAY-3: CPU SLA for capping
by Juan Hernandez 17 Sep '14

17 Sep '14

Hello, I tested the support for limiting the use of CPU of VMs. Setting it up in the GUI worked correctly, but when starting the VM the settings are ignored. Apparently the reason is a mismatch between the parameters that the engine sends and what VDSM expects: https://bugzilla.redhat.com/1142851 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.

1 0

Package vdsm-4.13.4-0.el6.x86_64.rpm is not signed again in 3.3.5. repo
by Sven Kieske 17 Sep '14

17 Sep '14

Hi, well the message in the topic already explains what is wrong. This happend already once some days ago and dcaro fixed it, but somehow this occurs again. It would be kind of someone could fix it. Thanks -- 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

1 0

[QE][ACTION NEEDED] oVirt 3.4.4 status
by Sandro Bonazzola 17 Sep '14

17 Sep '14

Hi, We're going to start composing oVirt 3.4.4 GA on *2014-09-23 08:00 UTC* from 3.4 branch. Maintainers: - Please be sure that 3.4 snapshot allow to create VMs before *2014-09-22 15:00 UTC* - Please be sure that no pending patches are going to block the release before *2014-09-22 15:00 UTC* - If any patch must block the GA release please raise the issue as soon as possible. A bug tracker [1] has been opened and shows no open blockers. There are still 6 bugs [2] targeted to 3.4.4. Excluding node and documentation bugs we still have 3 bugs [3] targeted to 3.4.4. Bug ID Whiteboard Status Summary 988341 node NEW Should not create bond when report an error in configuration process 1097735 node NEW "Reboot" button failed to work in progress_page with serial console to install ovirt-node iso. 1023481 node ASSIGNED Sane and working default libvirt config 1059309 sla NEW [events] 'Available memory of host $host (...) under defined threshold...' is logged only once 1127460 storage NEW VM abnormal stop after LV refreshing when using thin provisioning on block storage 1135061 storage POST Require qemu-kvm-rhev on EL to support live snapshots Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.4.4 should not be released without them fixed. - Please update the target to 3.5.1 or later for bugs that won't be in 3.4.4: 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.4 nightly snapshot, please add yourself to the test page [5] [1] http://bugzilla.redhat.com/1118689 [2] http://red.ht/1qwhPXB [3] http://red.ht/1r8jnap [4] http://www.ovirt.org/OVirt_3.4.4_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.4.4_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt Engine Virtual Appliance for 3.5 is ready for testing
by Fabian Deutsch 17 Sep '14

17 Sep '14

Hello! The ready-to-use Engine appliance is now building again and should contain the the latest and greatest 3.5rc2 packages. That appliance can be used for testing hosted engine, as well as testing oVirt Engine 3.5 in general. The ova (intended to be used with hosted engine setup) and the qcow2 (intended to be used for testing) images can be found here: http://jenkins.ovirt.org/view/All/job/ovirt-appliance_master_merged/ All relevant packages are pre-installed, but the appliance still needs to be configured. To configure the appliance you need to run: $ engine-setup --offline --config-append=ovirt-engine-answers inside the appliance after downloading it. Please let us know if you have any issues. Greetings fabian

2 2

GWT :: pretty CSS option now part of draft mode
by Vojtech Szocs 16 Sep '14

16 Sep '14

Hi, with patch [1] merged to master, enabling "pretty" (non-obfuscated) CSS for GWT applications can now be done simply by activating draft mode: $ make clean install-dev [usual makefile options] DEV_BUILD_GWT_DRAFT="1" Previously, developers had to mess with DEV_EXTRA_BUILD_FLAGS [2] but this is no longer necessary -- just use draft mode and you're all set. Frontend debug wiki http://www.ovirt.org/DebugFrontend was updated to reflect this change. Regards, Vojtech [1] http://gerrit.ovirt.org/#/c/31342/ [2] DEV_EXTRA_BUILD_FLAGS="-Dgwt.cssResourceStyle=pretty"

1 0

oVirt Node Weekly Meeting Minutes - September 16th 2014
by Fabian Deutsch 16 Sep '14

16 Sep '14

Minutes: http://ovirt.org/meetings/ovirt/2014/ovirt.2014-09-16-13.00.html Minutes (text): http://ovirt.org/meetings/ovirt/2014/ovirt.2014-09-16-13.00.txt Log: http://ovirt.org/meetings/ovirt/2014/ovirt.2014-09-16-13.00.log.html ================================= #ovirt: oVirt Node Weekly Meeting ================================= Meeting started by fabiand at 13:00:25 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2014/ovirt.2014-09-16-13.00.log.html . Meeting summary --------------- * Agenda (fabiand, 13:00:45) * Action Item Review (fabiand, 13:00:50) * oVirt 3.5 (fabiand, 13:00:54) * Jenkins (fabiand, 13:00:58) * Next-Gen Node (fabiand, 13:01:16) * Other Items (fabiand, 13:01:23) * oVirt 3.5 (fabiand, 13:04:11) * Testing and some smaller bug ficxing happend last Friday (fabiand, 13:04:24) * rbarry created a new iso (fabiand, 13:04:41) * ovirt-node-iso-3.5.0.ovirt35.20140912.el6.iso contains 3.5rc2 packages (fabiand, 13:06:44) * ovirt-node rpms need to be published (fabiand, 13:06:51) * ACTION: fabiand to generate rpms for 3.5rc2 iso (fabiand, 13:10:54) * ACTION: fabiand to ask dcaro to publish iso (fabiand, 13:11:05) * Action Item Review (fabiand, 13:13:05) * LINK: http://lists.ovirt.org/pipermail/devel/2014-September/008713.html (fabiand, 13:13:16) * fabiand to fix appliance job during the next week (fabiand, 13:13:33) * LINK: http://jenkins.ovirt.org/view/All/job/ovirt-appliance_master_merged/ (fabiand, 13:13:42) * appliance rootfs is built, ova is currentl not created, but WIP (fabiand, 13:14:36) * Jenkins (fabiand, 13:15:00) * Next-Gen Node (fabiand, 13:19:53) * Stable job which builds the runtime layout (fabiand, 13:20:21) * LINK: http://www.ovirt.org/OVirt_3.5_release-management (fabiand, 13:20:41) * Stable job to run functional tests on runtime layout image (fabiand, 13:20:53) * LINK: http://www.ovirt.org/OVirt_3.5_release-management (fabiand, 13:21:53) * Idea to do configuration using puppet - early investigationsdone by rbarry (fabiand, 13:32:14) * ripping the guts out of ovirt.node.config.defaults and shipping small puppet manifests which match each bit (kdump, ntp, rsyslog, etc al), assigning variables with hiera and pushing from there (fabiand, 13:32:28) * etcd hiera provider is also interesting to configure many nodes at once (fabiand, 13:32:48) * ACTION: rbarry to create a wiki page summarizing all the compoents which need a module, also specifying if it can be done with puppet or needs something else (fabiand, 13:33:30) * Other Items (fabiand, 13:37:50) Meeting ended at 13:43:19 UTC. Action Items ------------ * fabiand to generate rpms for 3.5rc2 iso * fabiand to ask dcaro to publish iso * rbarry to create a wiki page summarizing all the compoents which need a module, also specifying if it can be done with puppet or needs something else Action Items, by person ----------------------- * fabiand * fabiand to generate rpms for 3.5rc2 iso * fabiand to ask dcaro to publish iso * rbarry * rbarry to create a wiki page summarizing all the compoents which need a module, also specifying if it can be done with puppet or needs something else * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * fabiand (113) * rbarry (14) * dougsland (6) * vidalinux (5) * Netbulae (4) * ovirtbot (4) * [trip] (1) * winfr34k (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[ANN] oVirt 3.5 Third Test Day - Wed Sep 17th
by Sandro Bonazzola 15 Sep '14

15 Sep '14

Hi all, On Wed Sep 17th (instead of Sep 16th) we'll have oVirt 3.5.0 third test day. On this day all relevant engineers will be online ready to support any issues you find during install / operating this new release. Just make sure you have 1 host or more to test drive the new release. If you're curious to see how it works, this is your chance. Thanks again for everyone who will join us tomorrow! Location #ovirt irc channel Please communicate here to allow others to see any issues What In this test day you have a license to kill ;) Follow the documentation to setup your environment, and test drive the new features. Please remember we expect to see some issues, and anything you come up with will save you when you'll install final release Remember to try daily tasks you'd usually do in the engine, to see there are no regressions. Write down the configuration you used (HW, console, etc) in the report etherpad[1]. Documentation Release notes: http://www.ovirt.org/OVirt_3.5_Release_Notes Features pages links: http://bit.ly/17qBn6F If you find errors in the wiki please annotate it as well in report etherpad [1] Prerequisites / recommendations Use CentOS or RHEL 6.5 only. 6.4 is unsupported due to various issues (sanlock, libvirt, etc). Use Fedora 19 or 20. Latest RPMs repository to be enabled for testing the release are listed in the release notes page [2]. NEW issues / reports For any new issue, please update the reports etherpad [1] Feature owners, please make sure: your feature is updated and referenced on release page [2]. you have testing instruction for your feature either on test day page [3] or in your feature page. your team regression testing section is organized and up to date on test day page [3]. [1] http://etherpad.ovirt.org/p/3.5-testday-3 [2] http://www.ovirt.org/OVirt_3.5_Release_Notes [3] http://www.ovirt.org/OVirt_3.5_TestDay Thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[URGENT][ACTION REQUIRED] oVirt engine on branch 3.5 doesn't build anymore
by Sandro Bonazzola 15 Sep '14

15 Sep '14

Hi, we should release oVirt 3.5.0 RC2 today but looks like it doesn't build anymore. Can you please fix it as soon as possible? See: http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged/221/ Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 11

[RFC] Release process
by Sandro Bonazzola 15 Sep '14

15 Sep '14

Hi, while we're near to release 3.5.0 I would like to start the discussion on the release process for 3.5.z and 3.6.0. The reference page for the release process has been last updated 2 years ago and is not reflecting the way we're managing the releases anymore. In order to start the discussion here's what we are currently doing: = oVirt maintenance releases = * After a new 3.y.0 release, maintenance releases are scheduled every month until a new 3.y+1.0 release is published. * After first 3.y.0 release candidate is published a new release management wiki page is created (see http://www.ovirt.org/OVirt_3.4.z_release-management) * For each 3.y.z release, the release management page is updated ** Defining the schedule for RC and GA date ** Pointing to the new release note page to be created (see http://www.ovirt.org/OVirt_3.4.4_Release_Notes) ** Pointing to a testing page to be created (see http://www.ovirt.org/Testing/oVirt_3.4.4_Testing) ** Pointing to a blocker bug to be created (see http://bugzilla.redhat.com/1118689) * Weekly status email are sent to users and devel lists * QA page is updated with pointers to the new release (see http://www.ovirt.org/OVirt_Quality_Assurance) * Release manager update the release notes pages starting from RC Usually RC date is scheduled one week before GA. RC releases are created by taking the latest nightly snapshot available after verifying that the build passes basic sanity test and repository closure. A new stabilization branch is created with the same git hash used for building the snapshot. Between RC and GA release criteria are tested on the RC and if the release met the criteria a GA release will be built just updating the versioning code to drop master, git hash and timestamp suffix from tarballs and rpms. A new RC will be created and GA postponed by one week if release criteria are not met. = oVirt Release Process = * After a new 3.y.0 release, a new 3.y+1.0 release is tentatively scheduled after 6 months. * A new release management page is created (see http://www.ovirt.org/OVirt_3.5_release-management) * A new tracker bug is created (see http://bugzilla.redhat.com/1073943) * A discussion is started on devel and users mailing list gathering idea for next release features * Teams prepare a list of accepted features collecting / creating bug tracker, devel owner, qa owner, feature page for each of them * Several presentations are scheduled by the teams presenting the accepted features * An alpha release is scheduled 4 months before GA * Feature freeze is scheduled 3 months before GA * A beta release is scheduled 2 months before GA, git tree is branched for stabilization * A release candidate is scheduled 1 month before GA * Weekly status email are sent starting 3 weeks before alpha release. * Test days are scheduled after every milestone release * Release manager update the release notes pages starting from Alpha All milestones releases are created by taking the latest nightly snapshot available after verifying that the build passes basic sanity test and repository closure. RC will be postponed until all known blockers are fixed Between RC and GA release criteria are tested on the RC and if the release met the criteria a GA release will be built just updating the versioning code to drop master, git hash and timestamp suffix from tarballs and rpms. A new RC will be created and GA postponed by one week if release criteria are not met. [[Category:Release management]] What I think we're missing / doing wrong: * A discussion about release criteria *after* accepted features list is ready * A clear schedule like http://fedoraproject.org/wiki/Releases/21/Schedule * A clear feature freeze policy like https://fedoraproject.org/wiki/Changes_Freeze_Policy * A clear policy about changes we must allow and not allow between RC and GA * Alpha release should come after feature freeze * A string freeze schedule, allowing translators to have enough time to translate new strings * Maintainers should pay more attention to release notes and test day pages -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 2

[ACTION NEEDED] Please fix vdsm build dependencies on master
by Sandro Bonazzola 15 Sep '14

15 Sep '14

Hi, looks like VDSM is missing python-ethtool as BuildRequire on EL6 and FC20: http://jenkins.ovirt.org/job/vdsm_master_install-rpm-sanity-fc20_created/35… http://jenkins.ovirt.org/job/vdsm_master_install-rpm-sanity-el6_created/368… Please fix. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 3