- Devel - oVirt List Archives

Changing the name of VDSM in oVirt 4.0.
by Yaniv Dary 02 Feb '16

02 Feb '16

Hi, I wanted to bring this up to get feedback on this proposed change. VDSM doesn't align to other project under the oVirt umbrella like ovirt-engine, ovirt-node, ovirt-guest-agent etc.. I suggest for ease of use and tracking we change the versioning to align to the engine (4.0.0 in oVirt 4.0 GA) to make it easy to know which version was in which release and also change the package naming to something like ovirt-host-manager\ovirt-host-agent. What do you think on this? What do you think the name should be? Yaniv Dary Technical Product Manager 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 : ydary

21 24

oVirt UI now supports GWT Super Dev Mode
by Vojtech Szocs 02 Feb '16

02 Feb '16

Hi everyone, in ovirt-engine master branch, it's now possible [1] to use GWT Super Dev Mode [2] to debug oVirt web applications (WebAdmin, UserPortal): [1] https://gerrit.ovirt.org/#/c/50742/ [2] http://www.gwtproject.org/articles/superdevmode.html Please refer to commit msg [1] for details on GWT Super Dev Mode. In general, SDM is good for "iterative" development when one changes UI code and wants to see the change reflected in browser very quickly (compared to existing GWT debug mechanism, aka Classic Dev Mode). On the other hand, SDM does *not* allow using Java IDE to debug UI code, so one has to rely on browser's JavaScript developer tools. Existing (Java IDE based) debug mechanism still works as expected, the Super Dev Mode is just an alternative. Note on SDM usage by Scott: it's almost easier to run in Chrome's incognito mode so cached JS and mapped sources aren't an issue. Regards, Vojtech

2 2

Hello and A Question about oVirt
by zhukaijie 02 Feb '16

02 Feb '16

Hello, now I have defined a custom property named 'A' in oVirt Engine. Administrator is responsible for entering the value (and arbitrary string ) of 'A' before starting the VM. After an users trys to start the VM in oVirt, VDSM will add the value of 'A' in the qemu:arg of libvirt domain xml, so that the value of 'A' will be added into the QEMU Cmd as a param. However, just like the password of VNC or SPICE, I want to hide the value of 'A' in '*' format in both Libvirt domain xml and QEMU Cmd, So could you please tell me how to achieve it? Thank you very much and happy 2016.

3 2

Re: [ovirt-devel] Debian porting
by Milan Zamazal 01 Feb '16

01 Feb '16

lucas castro <lucascastroborges(a)gmail.com> writes: > Who is working on ovirt debian porting, I'm working on inclusion of Vdsm into Debian. ovirt-guest-agent is already included in Debian (packaged by another Debian maintainer). I'm not aware about any plans to package Engine for Debian nor I plan to do so. There are also Vdsm Debian packages provided by oVirt at http://resources.ovirt.org/pub/ovirt-3.6/debian/, but I don't recommend using them if you are going to use packages from standard Debian distribution once they are ready. While the packages to be included in Debian started from those provided by oVirt, there are many fixes in them and upgrading from oVirt repository packages to packages from Debian is not supported (may change if there is strong demand for that). So mixing those is likely to cause troubles. As for Vdsm in Debian, I've already uploaded most of the supporting packages (Python libraries, MoM) to Debian unstable. Vdsm itself is in preparation. One blocker is old version of sanlock package in Debian and missing sanlock-python package. I wrote to the Debian package maintainer a few days ago, no response so far. In the meantime, it's possible to use sanlock packages by oVirt from the URL mentioned above. (Please note I can't simply upload Debian package of another maintainer without his consent, so we must be patient.) > And how can I help ? If you'd like to help with Vdsm packaging in Debian, you can do so in any of the following ways: - Providing input on your needs. - Providing feedback on what to do with /rhev/data-center mounts directory in Vdsm. It's FHS incompatible and must be changed for Debian (the current location in the package is /run/vdsm/rhev/data-center). The unpleasant thing is that AFAIK migrations are not possible with current Vdsm across machines with mounts at different locations, so we should be careful. - Testing vdsm* packages once they are ready. They're not yet but once they are, testing them will be very welcome. - Providing feedback on the packaging. The git repository is on Alioth: https://anonscm.debian.org/cgit/collab-maint/vdsm.git/ . BTW, if anybody needs commit access (and doesn't have it) to the repository, tell me. Just please coordinate with me in any case so that we avoid duplicate work or conflicting plans. - The `vdsm*' packages are currently lintian clean, but completely untested, even installation may not work. If you'd like to check the installation and to fix contingent bugs preventing it, it's welcome. You'll also need safelease (https://anonscm.debian.org/cgit/collab-maint/safelease.git/) not yet in Debian but ready to upload, I'll do so soon. - Testing whether all the Vdsm related packages from unstable (python-cpopen, python-threading, ioprocess, safelease, mom, vdsm*) work on Debian 8 (jessie) as well. Ideally, they might work unchanged, but in case they don't we may be considering backporting them. - You can also review patches in debian/patches. Maybe some of the changes should be incorporated upstream, maybe some of them should be improved.

3 3

vdsm_master_storage-tests_wip_testing disabled since May 2015
by Sandro Bonazzola 01 Feb '16

01 Feb '16

Hi: http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Disabled/job/vdsm_mast… is disabled since may 2015 and marked as wip. Looks like it's not really a WIP... Can we delete it? If noone take ownership, we'll delete it on February 1st. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

Automation CI for vdsm
by Yaniv Bronheim 31 Jan '16

31 Jan '16

Hi all, We want to run functional tests as part of Vdsm CI for each patch before merge. Therefore we need to declare how to automate this process without overloading our jenkins machines. The functional tests will run using lago (https://github.com/ovirt/lago) - It will initiate multiply vms, install vdsm and manipulate it by nosetests or other procedures such as upgrade, removal and so on. Currently standard CI provides check-patch and check-merged scripts ( http://ovirt-infra-docs.readthedocs.org/en/latest/CI/Build_and_test_standar…) the problem with check-merged is that it will run after merge which doesn't help if something fails. We want to allow developers to trigger the script once reviews and verification are ready (last step before merge). To do so we agreed to add Continues Integration flag for each vdsm patch. Once this flag will be signed with +1 it will trigger Jenkins CI to run the check-merged script (adding new button to gerrit is not an option - you can image that flag as a trigger button), on success Jenkins CI flag will turn to +2. on fail we'll get -1 and once new patchset is ready the developer will remove the +1 and add it back to the Continues Integration flag to re-trigger the job. Please ack the process before we move on with that The patch for those scripts still under review and testing - https://gerrit.ovirt.org/#/c/48268 Thanks -- *Yaniv Bronhaim.*

8 11

oVirt goes to FOSDEM 2016 - the full scoop!
by Mikey Ariel 30 Jan '16

30 Jan '16

FOSDEM 2016 is just a few short weeks away, and I'm happy to share with you the full details about our community presence at the conference. ======= Virt & IaaS Devroom ======= Just a reminder that the full schedule is published on the FOSDEM website[1], and we have some great presentations from our community members for you to learn from. ======= oVirt/Foreman Stand ======= This year we will share a stand with our friends from the Foreman project. Stop by to say hello, grab swag, and enjoy some cool demos! **STAND VOLUNTEERS WANTED** If you're attending FOSDEM and would like to help us out, we'd love to have you there! This is a great opportunity to chat about oVirt with FOSDEM attendees and meet other community members from all over the world. Special surprise swag is reserved for booth volunteers! Please sign up for booth shifts in the etherpad[2] (lines 11-33). One of our core contributors will also be at the booth to support and co-pilot each shift. ======= Social Event on Saturday ======= In previous years, we had informal social gatherings for our community members on Saturday evening. These evenings are yet another excellent opportunity to meet and chat with the oVirt community outside the hectic FOSDEM venue. This year we'd like to hold an event again if there is enough demand, so please write your name/IRCnick/Twitter/G+/email in the etherpad[2] (line 86 and down) **by January 15**. If there is enough interest, we will reserve a nice pub in the center of Brussels and buy the first round :) See you in Brussels! [1] https://fosdem.org/2016/schedule/track/virtualisation_and_iaas/ [2] http://etherpad.ovirt.org/p/ovirt-fosdem-2016 -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady

4 4

[ANN] oVirt 3.6.3 First Release Candidate is now available for testing
by Sandro Bonazzola 28 Jan '16

28 Jan '16

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.3 for testing, as of January 28th, 2016 This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar) and Fedora 22. Highly experimental support for Debian 8.3 Jessie has been added too. This release candidate includes updated packages for: - ovirt-engine - ovirt-engine-cli - ovirt-engine-reports - ovirt-log-collector - vdsm - mom This release of oVirt 3.6.3 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO is also already available [2]. Please note that mirrors[3] may need usually one day before being synchronized. * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/OVirt_3.6.3_Release_Notes * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Read more about oVirt Project community events: http://www.ovirt.org/Upcoming_events [1] http://www.ovirt.org/OVirt_3.6.3_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[oVirt jenkins] Weekly report on open tasks for ovirt-engine
by jenkins＠ovirt.org 27 Jan '16

27 Jan '16

------=_Part_65_1366742175.1453916533009 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Files scanned: '**/*.java, **/*.py'. Strings searched: FIXME | TODO | @deprecated Report: http://jenkins.ovirt.org/job/ovirt-engine_3.6_scan-open-tasks_merged//8/tas… ------=_Part_65_1366742175.1453916533009--

1 0

SyNc meeting - Vdsm 26.1
by Yaniv Bronheim 27 Jan '16

27 Jan '16

(ybronhei, piotr, fromani, mzamazal, edwafh, ydary) Hi, Yaniv Dary raised the desire to modify vdsm name to ovirt-host-agent. The motivation is to align with ovirt components (ovirt-agent, ovirt-engine, ovirt-host-deploy, ovirt-node .... and so on). In addition, vdsm versions are not aligned with ovirt versions at all (historical reasons which we keep to avoid upgrade issues). GSS gets many questions about the differences between vdsm and other components in ovirt, and this will make their life easier. Basically, we all agreed that it is a good direction to have consistency with other components in ovirt but ovirt-host-agent sounds less than what vdsm actually does (sounds like ovirt-host-manager fits better). Yaniv will send official mail to devel list and we'll discuss it more deeply there. Francesco backported health patches merged to ovirt-3.5, will be published as part of vdsm v4.16.33 (https://gerrit.ovirt.org/#/c/52699 h ttps://gerrit.ovirt.org/#/c/52700 <https://gerrit.ovirt.org/#/c/52700> https://gerrit.ovirt.org/#/c/52701) it can help for later investigations with 3.5 vdsms. Milan works on debian packing, he arranges the mess we have under our current Debian folder. He currently discovered issues with sanlock package in debian which he still investigates. Greetings, -- *Yaniv Bronhaim.*

2 1