- Users - oVirt List Archives

New Case Study
by Brian Proffitt 17 Sep '14

17 Sep '14

A new case study has been posted on the oVirt web site, revealing the details of Spanish consulting firm Nimbus Concept, which is doing a great job using oVirt, Gluster and OpenStack to deliver great solutions to its customers! Learn more at: http://www.ovirt.org/Nimbus_Concept_Case_Study -- Brian Proffitt Community Liason oVirt Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

1 0

OVIRT-3.5-TEST-DAY-3 Instance types
by Alexander Wels 17 Sep '14

17 Sep '14

Hi, For the 3rd test day I was assigned to test the new instance types. The following instance types are available: custom: Aka what it was before tiny: 512M memory and 1 cpu small: 2048M memory and 1 cpu medium: 4096M memory and 1 cpu large: 8192M memory and 2 cpus x-large: 16384M memory and 4 cpus I verified that each selection modifies the properties accordingly. As well as the ability to change instance types after creating the VMs and that those changes are reflected. If you change a property lets say the memory after selecting an instance type it changes to custom automatically but keeps all the other pre-selected options the same. The only thing that won't change the instance type to custom if you change the 'optimized for' from server to desktop. This normally changes the soundcard enabled check box in the console tab but if an instance type is selected it doesn't. I don't know if this is on purpose or not. So all in all it works as expected, with a potential minor issue. Alexander

1 0

OVIRT-3.5-TEST-DAY-3 - Providing Neutron Appliance
by ybronhei 17 Sep '14

17 Sep '14

Hey, following the great demo in http://youtu.be/naLFSFwHI94 we successfully managed to use neutron to setup isolates network for 2 vms by using the neutron appliance image we didn't open new bugs on it, but we plan to use and play with it later on and we'll update if something will be found we saw that the mirrors for f19 are broken but it doesn't worth a bug, just wiki update (in http://repos.fedorapeople.org/repos/openstack/openstack-icehouse/rdo-releas…) -- Yaniv Bronhaim.

1 0

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

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

17 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

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 7

[OVIRT-3.5-TEST-DAY-3] dwh and reports on separate host
by Martin Sivak 17 Sep '14

17 Sep '14

Hi, I installed fresh engine on CentOS 6.5 (inside a VM) and dwh + reports to other CentOS 6.5 VM. Except being a bit confused by the certificate signing step during the setup all went well and I can see that the dwh service is running and I can access the reports site. I started in the afternoon, because I had to reinstall my hosts first, so I might try poking around tomorrow as well. Also I do not have extra hosts atm, but I hope to have my nested virtualization environment back tomorrow to actually put some data to the reports. -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ

1 0

Virtual Machines reporting as paused
by Thomas Scofield 17 Sep '14

17 Sep '14

A large number of my virtual machines are reporting in a paused state but they are actually up and running. Unfortunately I don't look at this cluster very often so I don't know exactly when it got into this state, I believe it may have happened a couple months back when I deployed a change to /etc/vdsm/vdsm.conf to throttle virtual machines migrations. I deployed this change via puppet and had puppet cycle the vdsm daemon. All of the vdsm daemons in the cluster were restarted in a short period of time. Since this happened some time back all the logs have rotated off. I have tried restarting vdsmd and libvirtd, but that doesn't appear to return the virtual machines to an up state. The output of "vdsClient -s 0 getAllVmStats" reports them as paused, "virsh -r list --all" reports them as running. From the GUI I can click run and the VM will show “Up” in the GUI and vdsClient. But if I restart vdsm, the VM's revert back to displaying a paused state. I did find that the *.recovery files in /var/run/vdsm contain a status of Paused even when the GUI and vdsClient are reporting it as up. I did try and change the status in this file while vdsm was down and then start vdsm, but it had no effect and the entry in the *.recovery file which reverted to paused. p335 sasS'status' p336 S'Paused' Any idea what might have caused the VM's to report as paused and how to recover from it? I am running ovirt-3.3.4-1 and vdsm-4.13.3-4

2 2

utostarting VMs after restart
by Grzegorz Szypa 17 Sep '14

17 Sep '14

Hi, where are located the scripts starting VMs in the environment oVirt? I would like to add skrytpt taking off virtual machines to the list of competing services during system startup. Is it possible to do such a thing? So that the effect was evident starting in webmin-portal. -- G.Sz.

3 5

[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