September 2014 - Devel - oVirt List Archives

[Devel] Proposing Yedidyah Bar David as oVirt Hosted Engine Setup maintainer
by Sandro Bonazzola 14 Jan '15

14 Jan '15

Hi, I would like to propose Yedidyah Bar David as oVirt Hosted Engine Setup co-maintainer. Yedidyah contributed to oVirt Hosted Engine Setup since early design phase and contributed dozens of patches. Your response would be appreciated. Thanks in advance. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

7 8

virt-v2v integration feature
by Arik Hadas 27 Nov '14

27 Nov '14

Hi All, The proposed feature will introduce a new process of import virtual machines from external systems using virt-v2v in oVirt. I've created a wiki page that contains initial thoughts and design for it: http://www.ovirt.org/Features/virt-v2v_Integration You are more than welcome to share your thoughts and insights. Thanks, Arik

12 29

ovirt.js OPW project
by Jenny Kang 03 Oct '14

03 Oct '14

Hello! I'm a student and I'm interested in the OPW project, which funds women into open source projects. oVirt is one of the supported projects. I'm really interested in working on the new ovirt.js library which uses the ovirt rest api. I need a mentor for this project. Any suggestions if it's a good idea to work on this? And also anyone interested in mentoring me in this project? I'm not selected yet but I would love to commit some contributions to get a feel of what it's like to work on ovirt.js beforehand. Cheers, Jenny

4 5

virt-v2v intergration with vdsm
by Shahar Havivi 02 Oct '14

02 Oct '14

Hi, We are planning to add couple of verbs to vdsm in order to import external VMs from VMWare esx server directly to data domain. This ability will also be reflected in oVirt engine and will enable user to view and select VMs from esx server, currently if oVirt user want to import a VM he needs to invoke a virt-v2v command line that will transfer the VM to an export domain and then import the same VM from export domain to data domain, Our goal is to eliminate the additional copy and simplify the process. In order to achive that we need to add two verbs for vdsm: 1. getExternalVmList(uri): This call is for listing all VMs that are raised in a specified esx server given its uri. 2. convertExternalVm(): The actual call to virt-v2v for copy and convert the VM to data domain, importVm will be called after the oVirt engine create the right image structure (via createImage) The virt-v2v handling verbs and other needed logic will be presented in a new file vdsm/v2v.py More details on virt-v2v integration can be found in its feature page: http://www.ovirt.org/Features/virt-v2v_Integration Thanks, Shahar Havivi.

5 12

[QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go
by Sandro Bonazzola 02 Oct '14

02 Oct '14

Hi, We were supposed to start composing oVirt 3.5.0 GA today 2014-09-29 but we still have 3 blockers. 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 RC3 tag. - Please provide ETA for new blockers for rescheduling an RC4 and a GA release. The bug tracker [1] shows 3 blockers: Bug ID Whiteboard Status Summary 1147085 storage POST Memory volumes not deleted when removing a vm with snapshots 1146073 sla POST Failing to Attach a Storage Domain without Disk Profiles to a Data Center 3.5 1127460 storage NEW VM abnormal stop after LV refreshing when using thin provisioning on block storage The following bugs are keyworded as Regression and not marked as blockers[10] Bug ID Whiteboard Status Summary 1142647 gluster NEW supervdsm leaks memory when using glusterfs 1138144 storage NEW Failed to autorecover storage domain after unblocking connection with host 1147085 storage POST Memory volumes not deleted when removing a vm with snapshots 1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError 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 69 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 46 bugs [4] targeted to 3.5.0. More in detail [5]: Whiteboard NEW ASSIGNED POST Total docs 13 1 0 14 gluster 4 0 2 6 i18n 0 0 1 1 infra 1 0 0 1 integration 0 0 1 1 node 9 4 0 13 ppc 2 0 4 6 sla 10 0 3 13 storage 2 1 3 6 virt 3 1 4 8 Total 44 7 18 69 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 6

[ANN] oVirt 3.4.4 Release is now available
by Sandro Bonazzola 30 Sep '14

30 Sep '14

The oVirt development team is pleased to announce the general availability of oVirt 3.4.4 as of Sep 23th 2014. This release solidifies oVirt as a leading KVM management application and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5 (or similar). This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. The existing repository ovirt-3.4 has been updated for delivering this release without the need of enabling any other repository, however since we introduced package signing you need an additional step in order to get the public keys installed on your system if you're upgrading from an older release. Please refer to release notes [1] for Installation / Upgrade instructions. Please note that mirrors will need a couple of days 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.4.repo commenting the mirror line and removing the comment on baseurl line. A new oVirt Live ISO will be available too[2]. [1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.4/iso/ovirt-live-el6-3.4.4.iso -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 6

physical disk management for gluster in vdsm
by Balamurugan Arumugam 29 Sep '14

29 Sep '14

Hi All, Currently gluster management in ovirt is not complete if disks in hosts are not formatted/mounted. It expects those actions done prior in the host added to ovirt. We have a requirement to manage physical disks by 1. identify and populate physical disks. 2. identify and manage hardware raids. 3. create thick and thin logical volumes in unused physical disks. 4. format and mount logical volumes. 5. fstab management for new logical volumes. To have this feature, I would like to start a discussion here to explore possible options suitable for vdsm/engine. We have done a small PoC with OpenLMI[1] by having verbs in vdsm to achieve this. Also we explored ovirt-engine directly calling tog-pegasus/cim-server to get cim object to avoid two level of hopes ("ovirt-engine calls vdsm <-> vdsm calls openlmi locally <-> openlmi does the job" than "ovirt-engine calls vdsm <-> openlmi does the job") which also works. I would like to get your feedback about the PoC and suggestions/ideas how physical disk management can be. Regards, Bala [1] http://openlmi.org/

3 6

oVirt Node 3.5 20140912 for the TestDay
by Fabian Deutsch 29 Sep '14

29 Sep '14

Hey, to be able to give Node a go on the oVirt 3.5 TestDay, we provide a fresh build of Node including the 3.5rc2 package here: http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/ovirt-node-iso-3.5.0.ovirt… We did not see any SELinux denials, but if you experience any problems, please try to install Node in permissive mode by appending enfcoring=0 during the installation. Any feedback and bug reports are welcome. On behalf of the Node team - fabian

3 6

ovirt35 - deepdive - ioprocess
by Barak Azulay 28 Sep '14

28 Sep '14

------=_Part_57506628_1980468884.1411924485049 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit The following is a new meeting request: Subject: ovirt35 - deepdive - ioprocess Organizer: "Barak Azulay" <bazulay(a)redhat.com> Time: Tuesday, September 30, 2014, 4:30:00 PM - 5:00:00 PM GMT +02:00 Jerusalem Invitees: ykaplan(a)redhat.com; users(a)ovirt.org; devel(a)ovirt.org *~*~*~*~*~*~*~*~*~* This session will cover the move from OOP (RemoteFileHandler) to the new ioprocess. It will cover exactly: - what is it - why is such a mechanism required - OOP and it's limitations - ioprocess Google hangout link: https://www.youtube.com/watch?v=tnrFTHf0sB0 ------=_Part_57506628_1980468884.1411924485049 Content-Type: text/calendar; charset=utf-8; method=REQUEST; name=meeting.ics Content-Transfer-Encoding: 7bit BEGIN:VCALENDAR PRODID:Zimbra-Calendar-Provider VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:Asia/Jerusalem BEGIN:STANDARD DTSTART:16010101T020000 TZOFFSETTO:+0200 TZOFFSETFROM:+0300 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU TZNAME:IST END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETTO:+0300 TZOFFSETFROM:+0200 RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1FR TZNAME:IDT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:3c88714b-9ca4-4951-a569-40f0004286fd SUMMARY:ovirt35 - deepdive - ioprocess ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:ykaplan @redhat.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:users@o virt.org ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:devel@o virt.org ORGANIZER;CN=Barak Azulay:mailto:bazulay@redhat.com DTSTART;TZID="Asia/Jerusalem":20140930T163000 DTEND;TZID="Asia/Jerusalem":20140930T170000 STATUS:CONFIRMED CLASS:PUBLIC X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY TRANSP:OPAQUE LAST-MODIFIED:20140928T171445Z DTSTAMP:20140928T171445Z SEQUENCE:0 DESCRIPTION:The following is a new meeting request:\n\nSubject: ovirt35 - de epdive - ioprocess \nOrganizer: "Barak Azulay" <bazulay(a)redhat.com> \n\nTim e: Tuesday\, September 30\, 2014\, 4:30:00 PM - 5:00:00 PM GMT +02:00 Jerusa lem\n \nInvitees: ykaplan(a)redhat.com\; users(a)ovirt.org\; devel(a)ovirt.org \n\ n\n*~*~*~*~*~*~*~*~*~*\n\nThis session will cover the move from OOP (RemoteF ileHandler) to the new ioprocess. \nIt will cover exactly: \n- what is it \n - why is such a mechanism required \n- OOP and it's limitations \n- ioproces s \n\nGoogle hangout link: https://www.youtube.com/watch?v=tnrFTHf0sB0 BEGIN:VALARM ACTION:DISPLAY TRIGGER;RELATED=START:-PT5M DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR ------=_Part_57506628_1980468884.1411924485049--

1 0

Remote DataCenter/Cluster
by Sahina Bose 28 Sep '14

28 Sep '14

Hi, We ran into a requirement where we need to mark a DataCenter or Cluster as remote. This is for the feature Gluster Geo-replication management - where the same oVirt instance will be managing both the master volume and as well as the remote site volume The reason we want to call out a Datacenter as remote, is to ensure that the polling frequency on this is different from one that is co-located. Is there a similar requirement for virtualization? thanks sahina

4 5