- Users - oVirt List Archives

Why cloud-init fail
by John Xue 18 Sep '14

18 Sep '14

Hi, All I try to config cloud-init. according the guide: http://www.ovirt.org/Features/Cloud-Init_Integration install cloud-init in the guest vm, configure cloud-init option, but I can't save the configure in "Edit Virtual Machine" -> "Initial Run" -> any option. after click OK, and back to check my settings, all are lost. boot the guest vm, no settings are deployed. my version is: oVirt Engine Version: 3.4.3-1.el6 Thank you! -- Regards, John Xue

2 3

[OVIRT-3.5-TEST-DAY-3] Node Hosted Engine
by Liron Aravot 18 Sep '14

18 Sep '14

Hi All, Federico and I tested the node hosted engine. We started a vm using the posted ovirt node iso and actually didn't get to test the complete hosted engine setup due to failure which was unclear [3] (opened a bug for that). Bug were opened for clarity of the node menu as well [1], same as for the way to access the logs [2]. thanks, [1] https://bugzilla.redhat.com/show_bug.cgi?id=1143857 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1143861 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1143871

1 0

[OVIRT-3.5-TEST-DAY-3] backup/restore/dr + Node
by Ryan Barry 17 Sep '14

17 Sep '14

I installed a fresh engine on CentOS 6.5, and 3.5 nodes on two nested VMs. A significant portion of the day was spent testing basic Node functionality to ensure we didn't have any more SELinux denials, install problems on EFI, or other issues, after which I moved onto engine. DR was simply tested by pulling the network cable in the middle of an operation, disconnecting both nodes and waiting for storage arbitration to succeed, and uncleanly terminating the VM running engine then restarting. Backup and restore was tested with ovirt-engine-backup (which I haven't used before, and is quite nice).

2 1

OVIRT-3.5-TEST-DAY-3 - hosted engine over iSCSI
by Antoni Segura Puimedon 17 Sep '14

17 Sep '14

Hi list! I got hold of an iSCSI lun and set out to test deploying the hosted-engine over it (I've been successfully running hosted-engine over NFS since oVirt-3.4 and have successfully upgraded it to 3.5 and jsonrpc communication). Unfortunately, things didn't start well with a small issue when calling hosted-engine --deploy Due to the vdsm certs not being propertly generated: https://bugzilla.redhat.com/1142696 After working around that doing: vdsm-tool configure --force I repeated the deploy command and answered every question. It created the VM image, but ultimately failed to set up a password for VNC (for that is what I chose to access the VM). https://bugzilla.redhat.com/1142710 I attached the vdsm logs and will investigate more to try to give more info to the hosted engine devs ;-) Regards, Toni

3 2

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