March 2016 - Devel - oVirt List Archives

[URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed
by Sandro Bonazzola 08 Mar '16

08 Mar '16

Hi, I think I already raised the issue several times, but let me raise this again. VDSM building / automated versioning is badly broken. Currently, 3.6 snapshot is building: vdsm-4.17.19-32.git171584b.el7.centos.src.rpm <http://jenkins.ovirt.org/job/vdsm_3.6_build-artifacts-el7-x86_64/178/artifa…> because the last tag on the 3.6 branch was 4.17.19 and new tags have been created in different branches. This make impossible to upgrade from stable (4.17.23) to latest snapshot. This also break dependencies on other projects requiring the latest released version like hosted engine. Please fix the automated versioning system vdsm is currently using or get rid of it. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 23

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

08 Mar '16

------=_Part_84_1710939013.1457436534280 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_master_scan-open-tasks_merged//45… ------=_Part_84_1710939013.1457436534280--

1 0

How can users use oVirtCli to complete "run once"?
by zhukaijie 08 Mar '16

08 Mar '16

As you know. In web, users can use "RUN ONCE" button to run a VM with some params (such as certain custom properties). But can oVirtCli be used to complete "RUN ONCE"? Thank you.

3 2

oVirt Integration Development Team weekly status - 2016-03-07
by Sandro Bonazzola 07 Mar '16

07 Mar '16

- oVirt integration open bugs: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… - 3.6.3 - Built and released oVirt 3.6.3 GA distribution - Built and released oVirt Live 3.6.3 GA media - Release notes: http://www.ovirt.org/release/3.6.3/ - Announce: http://lists.ovirt.org/pipermail/announce/2016-March/000237.html - Fixing latest blockers for 3.6.3 - Adding Fedora 23 support to ovirt-log-collector - Published documentation about HE upgrade from el6 3.5 to el7 3.6 - 4.0.0 - Re-factored ovirt-release package for easy Jenkins and NGN consumption - started 4.0 pre integration and migration from 3.6 testing - SpagoBi: progress packaging spagobi and spagobi-dependencies - Infra: - Fixed several jobs issues - CentOS Virt SIG: - Rafael joined CentOS Virt SIG - CentOS Virt SIG - oVirt How To: http://wiki.centos.org/HowTos/oVirt - Meeting minutes will be available on https://www.centos.org/minutes/2016/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

master ovirt-engine requires ovirt-engine-sdk-python >= 4.0.0.0
by Yedidyah Bar David 07 Mar '16

07 Mar '16

Hi all, I am trying, on a rhel7 vm: yum install -y http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm yum install ovirt-engine Fails with: --> Finished Dependency Resolution Error: Package: ovirt-iso-uploader-4.0.0-0.0.master.20160208072812.gita433ce3.el7.centos.noarch (ovirt-master-snapshot) Requires: ovirt-engine-sdk-python >= 4.0.0.0 Available: ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.0.3-1.el7.centos Available: ovirt-engine-sdk-python-3.6.2.1-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.2.1-1.el7 Installing: ovirt-engine-sdk-python-3.6.3.0-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.3.0-1.el7 Error: Package: ovirt-image-uploader-4.0.0-0.0.master.20160211135948.git43cc942.el7.centos.noarch (ovirt-master-snapshot) Requires: ovirt-engine-sdk-python >= 4.0.0.0 Available: ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.0.3-1.el7.centos Available: ovirt-engine-sdk-python-3.6.2.1-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.2.1-1.el7 Installing: ovirt-engine-sdk-python-3.6.3.0-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.3.0-1.el7 Tried also: yum install http://jenkins.ovirt.org/job/ovirt-engine-sdk_master_build-artifacts-el7-x8… which works, but does not satisfy the above dep. Should it? Any other place to find 4.0 python sdk? Thanks, -- Didi

4 6

nested hosts \ vdsm hooks on rhel 7.2
by emarcian 07 Mar '16

07 Mar '16

Hi, Has anyone ever used vdsm hooks in RHEL 7.2 on to of 3.6 ? I faced some issues with that, related to emulated machines [root@localhost ~]# tail -f /var/log/vdsm/vdsm.log |grep ':ERROR:' Thread-18::ERROR::2016-03-06 07:43:57,019::caps::195::root::(_get_emulated_machines_from_domain) Error while looking for kvm domain (x86_64) libvirt capabilities -Eldad

2 2

logging VDSM-generated libvirt XML properly
by Martin Polednik 07 Mar '16

07 Mar '16

Hello developers! I've been chasing a bug that lead me to an idea of improving our XML logging. Now, to see a VMs generated libvirt XML, we have to rely on vdsm.log. The issue is that the log is rotating and therefore, it is easy to miss the correct XML when dealing with busy hypervisor. Since we're built on libvirt, I was thinking of doing similar thinks that libvirt does with qemu commandline. Each running domain(VM) has it's command line logged in /var/log/libvirt/qemu/${vmname}. This is great for debugging as you can mostly just take the cmdline and restart the VM. There is an issue with using the cmdline directly - networking. Libvirt uses additional script to create and up a bridge. Therefore, it is easier to use the XML and shape it to one's needs. I propose that we properly log the generated XML in a similar fashion as libvirt generates the cmdline. This means we would have path like /var/log/vdsm/libvirt/${vmname}, where generated XML would be stored. To minimize the logging requirements, only last definition of VM with that name may be stored. Additionally, exception level errors related to that VM could also be stored there. What do you think, can we afford the space and additional writes per VM to help the debugging process? Regards, mpolednik

2 2

In AIO environment, why engine and vdsm communicate timeout
by 李坚 07 Mar '16

07 Mar '16

4 3

Engine High Availability
by Sunny Shin 06 Mar '16

06 Mar '16

Hi All, In the new architecture page ( http://www.ovirt.org/documentation/architecture/architecture/) overall architecture picture shows that engine supports active-active high availability. However, as per engine HA page ( http://www.ovirt.org/develop/release-management/features/engine/engine-high…) active-active HA is not supported yet and there are several implementation issues. So, could anyone give me a brief explanation about discrepancy between these two pages, and about the plan to implement this feature if not implemented yet? Sunny

2 9

Allow access to Cockpit by default after adding a host? Or make it configurable in Engine?
by Fabian Deutsch 04 Mar '16

04 Mar '16

Hey, Node Next will ship Cockpit by default. When the host is getting installed, Cockpit can be reached by default over it's port 9090/tcp. But after the host was added to Engine, Engine/vdsm is setting up it's own iptables rules which then prevent further access to Cockpit. How do we want users to control the access to Cockpit? So where shall users be able to open or close the Cockpit firewall port. Initially I thought that we can open up the cockpit port by default, but this might be a security issue. (Brute force attacks to crack user passwords through the web interface). - fabian

3 5

oVirt Engine 3.6.4 branch was created + backport guide for 3.6.z
by Tal Nisan 03 Mar '16

03 Mar '16

Hi everyone, The ovirt-engine-3.6.4 branch has been created following the last (hopefully) respin of 3.6.3 Note the the branch was created from the 3.6.3 branch today and contains all the content of 3.6.3 obviously. As I am asked a lot of questions questions concerning the backport flow for 3.6.z bugs, here it is: 3.6.5 bugs should be included in: - master - ovirt-engine-3.6 3.6.4 bugs should be included in: - master - ovirt-engine-3.6 - ovirt-engine-3.6.4. As for 3.6.6 only bugs i.e. those that are solved in the timeline before branching out of 3.6.5 but you do not want them to be included in 3.6.5, those should NOT be merged on ovirt-engine-3.6 until 3.6.5 will be branched out (date TBD, probably a couple of weeks before the release date). For further questions feel free to contact me.

1 0

[ANN] oVirt 3.6.3 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 03 Mar '16

03 Mar '16

The oVirt Project is pleased to announce the availability of the Fourth Release Candidate of oVirt 3.6.3 for testing, as of February 24th, 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 - vdsm - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup 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 will be available soon [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/release/3.6.3/ * 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/release/3.6.3/ [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

2 4

python3-ovirt-engine-sdk4-4.0.0-0.0.20160302git42dbb0c.x86_64 missing deps on el7
by Sandro Bonazzola 03 Mar '16

03 Mar '16

Hi, python3 is not available on el7, causing: *00:17:51.028* Num Packages in Repos: 20203*00:17:51.028* package: python3-ovirt-engine-sdk4-4.0.0-0.0.20160302git42dbb0c.x86_64 from check-custom-el7*00:17:51.028* unresolved deps: *00:17:51.028* python3-pycurl*00:17:51.028* python3 Please fix the spec file avoiding to build python3 modules on el7, thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

[ACTION REQUIRED] Legacy code removal
by Sandro Bonazzola 03 Mar '16

03 Mar '16

Hi, for oVirt 4.0 we're going to drop backward compatibility with oVirt < 3.6, you're kindly invited to cleanup the code dropping legacy support for older version. More in detail, for 4.0 we'll assume: * Support for EL6 hosts will be dropped * oVirt Engine support for EL6 will be dropped * Upgrade / Migration (if oVirt Engine was running on EL6) will be supported only from oVirt 3.6 * Network API support for oVirt < 3.6 will be dropped, the remaining API should be backward compatible * oVirt Engine will support cluster compatibility >= 3.6 * We won't support in place upgrade for oVirt Engine from 3.6 EL6 to 4.0 EL7: we'll support only migration. * oVirt DWH will only have 3.6 \ 4.0 compatibility views in 4.0. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Cockpit port open by default after adding host
by Fabian Deutsch 02 Mar '16

02 Mar '16

Hey, we use cockpit on Node Next, and we configure firewalld to open the port by default. However, after adding the host to Engine, the port is getting closed again because iptables is the used. How do you recommend to get the cockpit port opened by default? - fabian

2 4

Move host-deploy package installations into package?
by Fabian Deutsch 02 Mar '16

02 Mar '16

Hey, IIUIC host-deploy is currently installing some packages manually: https://gerrit.ovirt.org/gitweb?p=ovirt-host-deploy.git;a=blob;f=src/plugin… Can't these dependencies moved to vdsm - or if not - can't they be moved to a ovirt-host package? Then we'd have all package related informations in one place. I find it odd that host-deploy is taking care of package installation, imo it should be sufficient to install a single package and have a host ready. host-deploy can then focus on just configuring the existing packages. Thoughts? - fabian

3 3

Iscsi and other BAD buggy
by Вячеслав Бадалян 02 Mar '16

02 Mar '16

Hello. ZERO) https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt Sorry, entering a bug into the product *oVirt* has been disabled And lets go. A) If host with ovirt have iscsi target we will have bug troubles. Its looks like 1. Create targetcli from LVM 2. All ok 3. Reboot 4/ LVM found oVIrt partitions and connect it. 5. targetcli can't get device. It's allready busy. If you add some filter to don's search iscsi devices then ovirt does not work correctly. B) Some throuble with glusterD. VSDM do mount of hosted engine volume and this host is aslo GluserD Server. Bug troubles. C) If i reboot 1 of 3 gluster servers then hosted engine will very slowly. Have many errors in dmes, Agent-ha reboot VM. Vm can't conect to don't full cluster and stuck in Paused mode. Realy... Its all look so bad... i mirgrate to NFS :( D) Network conffugurate realy bad. If i need to change network i can't do it. oVirt save posted from web settings. Bug vsdm-networking MUST fallback to previos setup if i mistake or SERVIS does not start. E). Ovirt reports does not install. [java] org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'actionModelService' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.ExceptionInInitializerError 2016-02-28 09:20:59 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_reports.jasper.deploy plugin.execute:941 execute-output: ('./js-ant', '-DmasterPropsSource=/tmp/tmp3paFhC/config', 'import-minimal-ce') stderr: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 BUILD FAILED /usr/share/jasperreports-server/buildomatic/bin/import-export.xml:263: The following error occurred while executing this line: /usr/share/jasperreports-server/buildomatic/bin/import-export.xml:142: Java returned: 255 Total time: 24 seconds 2016-02-28 09:20:59 DEBUG otopi.context context._executeMethod:156 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 146, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-reports/jasper/deploy.py", line 656, in _deploy self._buildJs(config=config, cmd=cmd) File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-reports/jasper/deploy.py", line 215, in _buildJs 'buildomatic', File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 946, in execute command=args[0], RuntimeError: Command './js-ant' failed to execute 2016-02-28 09:20:59 ERROR otopi.context context._executeMethod:165 Failed to execute stage 'Misc configuration': Command './js-ant' failed to execute 2016-02-28 09:20:59 DEBUG otopi.transaction transaction.abort:134 aborting 'Yum Transaction' 2016-02-28 09:20:59 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:95 Yum Performing yum transaction rollback Загружены модули: fastestmirror, versionlock -- -- С уважением, Бадалян Вячеслав Борисович ООО "Открытые бизнес-решения" Технический директор +7 (495) 666-0-111 http://www.open-bs.ru

4 6

Re: [ovirt-devel] In AIO environment, why engine and vdsm communicate timeout
by lijian 02 Mar '16

02 Mar '16

This is a multi-part message in MIME format. ------=_NextPart_56D64ED3_8055F6B0_0FD12B2F Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgTWHvvIwKCgogcHJvdmlkZSBvdmVydC1lbmdpbmUgbG9n77yMSSB3aWxsIHByb3ZpZGUg dmRkbSBsb2cuIHRoYW5rcyEKCgrigJTigJTigJTigJTigJTigJTigJTigJTigJTigJTigJTi gJTigJTigJTigJTigJTigJTigJTigJTigJTigJTigJQKb3ZpcnQgZGV2ZWxvcGVyCgoKUGxl YXNlIHNoYXJlIHZkc20gYW5kIGVuZ2luZSBsb2dzIHNvIEkgY291bGQgdW5kZXJzdGFuZCB3 aGF0IGhhcHBlbmVkLiBPbiBUdWUsIE1hciAxLCAyMDE2IGF0IDEyOjM4IFBNLCDmnY7lnZog bGlqaWFuQGNsb3VkLXRpbWVzLmNvbSB3cm90ZTogIERlYXIgb3ZpcnQgZGV2ZWxvcGVycywg ICBJbiBvdmlydCAzLjUueCB2ZXJzaW9uLCB0aGVyZSBpcyBhIHByb2JsZW0gY29tbXVuaWNh dGluZyB0aW1lb3V0IGJldHdlZW4gIG92aXJ0LWVuZ2luZSBhbmQgdmRzbSBpbiBBSU8gZW52 aXJvbm1lbnQuIFRoZSBkZWZhdWx0IHRpbWVvdXQgaXMgMTgwICBzZWNvbmRzLCBidXQgdmRz bSByZXR1cm5pbmcgYSByZXF1ZXN0IGNvc3QgNTAwIHNlY29uZHMuIFRoZSBBSU8gaG9zdCBp cyAgbGlnaHQgbG9hZCBhbmQgZG8geW91IGtub3cgd2h5IHNvIHNsb3dseS4gICAgSSByZW1l bWJlciB0aGF0IGl0IGRvbid0IGhhdmUgdGhpcyBwcm9ibGVtIGluIDIueCB2ZXJzaW9uLiBw bGVhc2UgaGVscCBtZSwgIHRoYW5rcyEgICAgIFRoYW5rcyAgQmVzdCBSZWdhcmRzICAgLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLSAgIG92aXJ0IGRlbGVsb3BlciAgICAgIF9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fICBEZXZlbCBtYWlsaW5nIGxpc3QgIERl dmVsQG92aXJ0Lm9yZyAgaHR0cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZv L2RldmVs ------=_NextPart_56D64ED3_8055F6B0_0FD12B2F Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0iZm9udDoxNHB4LzEuNSAnTHVjaWRhIEdyYW5kZScsICflvq7ova/pm4Xp u5EnO2NvbG9yOiMzMzM7Ij48cCBzdHlsZT0iZm9udDoxNHB4LzEuNSAnTHVjaWRhIEdyYW5k ZSc7bWFyZ2luOjA7Ij5IaSBNYe+8jDwvcD48cCBzdHlsZT0iZm9udDoxNHB4LzEuNSAnTHVj aWRhIEdyYW5kZSc7bWFyZ2luOjA7Ij48YnI+PC9wPjxwIHN0eWxlPSJmb250OjE0cHgvMS41 ICdMdWNpZGEgR3JhbmRlJzttYXJnaW46MDsiPiZuYnNwOyBwcm92aWRlIG92ZXJ0LWVuZ2lu ZSBsb2fvvIxJIHdpbGwgcHJvdmlkZSB2ZGRtIGxvZy4gJm5ic3A7dGhhbmtzITwvcD48YnI+ PGRpdj48ZGl2IHN0eWxlPSJmb250OiAxNHB4LzEuNSAnTHVjaWRhIEdyYW5kZSc7Ij48cCBz dHlsZT0ibWFyZ2luOiA1cHggMHB4OyBmb250LWZhbWlseTogdmVyZGFuYSwgVGFob21hLCBB cmlhbCwg5a6L5L2TLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE2cHg7IGxpbmUtaGVpZ2h0 OiBub3JtYWw7IHdpZG93czogMTsiPuKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKA lOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlDwvcD48cCBzdHlsZT0ibWFyZ2lu OiA1cHggMHB4OyBmb250LWZhbWlseTogdmVyZGFuYSwgVGFob21hLCBBcmlhbCwg5a6L5L2T LCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE2cHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IHdp ZG93czogMTsiPm92aXJ0IGRldmVsb3BlcjwvcD48L2Rpdj48L2Rpdj48ZGl2IGNsYXNzPSJm b3htYWlsX2Jsb2NrcXVvdGVfZnJvbWhlcmVfZWxlbWVudCIgc3R5bGU9ImZvbnQ6IDEycHgv MS41ICdMdWNpZGEgR3JhbmRlJztwYWRkaW5nOjJweCAwIDJweCAwOyI+PGJyPjwvZGl2Pjxk aXYgY2xhc3M9Im1haWxfcXVvdGVfOEZBRDk1MUQyNzNENDZBM0FEQTJERkI2ODA0REMzQzgi IHN0eWxlPSJmb250OiAxNHB4LzEuNSAnTHVjaWRhIEdyYW5kZSc7Y29sb3I6IzMzMzsiPjxw cmUgc3R5bGU9IndoaXRlLXNwYWNlOnByZS13cmFwOyI+UGxlYXNlIHNoYXJlIHZkc20gYW5k IGVuZ2luZSBsb2dzIHNvIEkgY291bGQgdW5kZXJzdGFuZCB3aGF0IGhhcHBlbmVkLgoKT24g VHVlLCBNYXIgMSwgMjAxNiBhdCAxMjozOCBQTSwg5p2O5Z2aICZsdDs8YSBocmVmPSJtYWls dG86bGlqaWFuQGNsb3VkLXRpbWVzLmNvbSIgdGl0bGU9Im1haWx0bzpsaWppYW5AY2xvdWQt dGltZXMuY29tIj5saWppYW5AY2xvdWQtdGltZXMuY29tPC9hPiZndDsgd3JvdGU6CiZndDsg RGVhciBvdmlydCBkZXZlbG9wZXJzLAoKJmd0OwomZ3Q7ICAgSW4gb3ZpcnQgMy41LnggdmVy c2lvbiwgdGhlcmUgaXMgYSBwcm9ibGVtICBjb21tdW5pY2F0aW5nIHRpbWVvdXQgYmV0d2Vl bgomZ3Q7IG92aXJ0LWVuZ2luZSBhbmQgdmRzbSBpbiBBSU8gZW52aXJvbm1lbnQuIFRoZSBk ZWZhdWx0IHRpbWVvdXQgaXMgMTgwCiZndDsgc2Vjb25kcywgYnV0IHZkc20gcmV0dXJuaW5n IGEgcmVxdWVzdCBjb3N0IDUwMCBzZWNvbmRzLiBUaGUgQUlPIGhvc3QgaXMKJmd0OyBsaWdo dCBsb2FkIGFuZCBkbyB5b3Uga25vdyB3aHkgc28gc2xvd2x5LgomZ3Q7CiZndDsKJmd0OyAg IEkgcmVtZW1iZXIgdGhhdCBpdCBkb24ndCBoYXZlIHRoaXMgcHJvYmxlbSBpbiAyLnggdmVy c2lvbi4gcGxlYXNlIGhlbHAgbWUsCiZndDsgdGhhbmtzIQomZ3Q7CiZndDsKJmd0OwomZ3Q7 ICAgVGhhbmtzICZhbXA7IEJlc3QgUmVnYXJkcwomZ3Q7CiZndDsgLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LQomZ3Q7CiZndDsgIG92aXJ0IGRlbGVsb3BlcgomZ3Q7CiZndDsKJmd0OwomZ3Q7CiZndDsg X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KJmd0OyBE ZXZlbCBtYWlsaW5nIGxpc3QKJmd0OyA8YSBocmVmPSJtYWlsdG86RGV2ZWxAb3ZpcnQub3Jn IiB0aXRsZT0ibWFpbHRvOkRldmVsQG92aXJ0Lm9yZyI+RGV2ZWxAb3ZpcnQub3JnPC9hPgom Z3Q7IDxhIGhyZWY9Imh0dHA6Ly9saXN0cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9k ZXZlbCIgdGl0bGU9Imh0dHA6Ly9saXN0cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9k ZXZlbCI+aHR0cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RldmVsPC9h PgoKCjwvcHJlPjwvZGl2PjwvZGl2Pg== ------=_NextPart_56D64ED3_8055F6B0_0FD12B2F--

1 0

[ANN] oVirt 3.6.3 Final Release is now available
by Sandro Bonazzola 01 Mar '16

01 Mar '16

The oVirt Project is pleased to announce today the general availability of oVirt 3.6.3. This latest community release includes numerous bug fixes and several new features, such as: - The WebSocketProxy VDC option(and a few others) can now be updated without need to restart the engine. - OVIRT-CLI now use remote-viewer instead of spicec for spice based console - unassigned host status now reflects more the real status - cloud-init service after appliance deployment is now disabled oVirt is an open-source, openly-governed enterprise virtualization management application, developed by a global community. You can use the oVirt management interface (oVirt Engine) to manage hardware nodes, storage and network resources, and to deploy and monitor virtual machines running in your data center. If you are familiar with VMware products, oVirt is conceptually similar to vSphere. oVirt serves as the bedrock for Red Hat's Enterprise Virtualization product, and it is the "upstream" project where new features are developed prior to their inclusion in Red Hat's supported product offering. Additional Resources: * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.3/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Read more about oVirt Project community events: http://www.ovirt.org/events/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0