ovirt-hosted-engine-setup: extending maintainers team
by Sandro Bonazzola
If you follow ovirt-hosted-engine-setup development, you probably noticed
that I'm the only existing maintainer there.
During the 3.6 development Simone Tiraboschi contributed a huge amount of
patches and is currently unofficially maintaining iSCSI and FC storage
support and the virtual appliance configuration flow.
I'd like to officially nominate Simone as ovirt-hosted-engine-setup
co-maintainer.
Please approve.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
9 years, 3 months
[oVirt 3.6 Localization Question #27] "Any Host in Data Center" and "Any Data Center"
by Yuko Katabami
This is a multi-part message in MIME format.
--------------010205070801050703080702
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Hello all,*
*Could anyone help us with the following question?*
File:***UIConstants*
Resource ID:** * "anyDataCenter" and "anyHostInDataCenter"
*String: *"Any Host in Data Center" and "Any Data Center"
*Question: *Where those strings are located in the UI? A Docs team
writer helped us to look for them in the code but could not find them in
frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/frontend/org.ovirt.engine.ui.uicompat.UIConstants
Thanks in advance,
Yuko Katabami*
*
**
--------------010205070801050703080702
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello all,<b><br>
<br>
</b>Could anyone help us with the following question?<b><br>
<br>
File:</b><b> </b>UIConstants<b><br>
Resource ID:</b><b> </b>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
"anyDataCenter" and
<meta http-equiv="content-type" content="text/html; charset=utf-8">
"anyHostInDataCenter"<br>
<b>String: </b>"Any Host in Data Center" and "Any Data Center"<br>
<b>Question: </b>Where those strings are located in the UI? A Docs
team writer helped us to look for them in the code but could not
find them in
frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/frontend/org.ovirt.engine.ui.uicompat.UIConstants<br>
<br>
<br>
Thanks in advance,<br>
<br>
Yuko Katabami<b><br>
</b>
<div class="moz-signature"><font color="#000000" face="arial,
sans-serif" size="2"> <b></b><br>
</font>
</div>
</body>
</html>
--------------010205070801050703080702--
9 years, 3 months
[RFC] proposal to drop fc20 support in 3.5.z after 3.5.4 release
by Sandro Bonazzola
Hi,
since Fedora 20 reached EOL long ago, I propose to drop fedora 20 support
within 3.5.z, being 3.5.4 the last supported release.
According to current schedule 3.5.5 should be the last 3.5.z release since
3.6.0 will be out very close to 3.5.5. We're currently experiencing issues
in keeping fc20 build support in Jenkins CI and we need to decide if we
want to put effort in keeping fc20 support in 3.5.z.
Comments are welcome.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
9 years, 3 months
[ANN] oVirt 3.6.0 First Beta Release is now available for testing
by Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the First Beta
release of oVirt 3.6 for testing, as of August 4th, 2015.
oVirt is an open source alternative to VMware vSphere, and provides an
excellent KVM management interface for multi-node virtualization.
The First Beta release is available now for Fedora 22,
Red Hat Enterprise Linux 6.7, CentOS Linux 6.6 (or similar) and
Red Hat Enterprise Linux 7.1, CentOS Linux 7.1 (or similar).
The First Beta release can also be deployed on Hypervisor Hosts running
Fedora 21 and Fedora 22.
Experimental support for Debian 8.1 Jessie has been added too.
This First Beta release of oVirt 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 Node ISO[2] is already available and an oVirt Live ISO will be
available soon as well.
Please note that mirrors[3] may need usually one day before being
synchronized.
Please refer to the release notes for known issues in this release.
[1] http://www.ovirt.org/OVirt_3.6_Release_Notes
[2] http://plain.resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-node/
[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
9 years, 3 months
Failed Snapshot as 'Current' after failed Live Storage Migration
by Christopher Pereira
This is a multi-part message in MIME format.
--------------000701090209060705020903
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
A live storage migration task failed due to a network error:
2015-08-03 21:23:16,437 WARN
[org.ovirt.engine.core.bll.CreateAllSnapshotsFromVmCommand]
(org.ovirt.thread.pool-12-thread-45) [] Could not perform live
snapshot due to error, VM will still be configured to the new
created snapshot: VdcBLLException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
VDSGenericException: VDSNetworkException: Message timeout which can
be caused by communication issues (Failed with error
VDS_NETWORK_ERROR and code 5022)
2015-08-03 21:23:16,450 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-12-thread-45) [] Correlation ID: null, Call
Stack: org.ovirt.engine.core.common.errors.VdcBLLException:
VdcBLLException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
VDSGenericException: VDSNetworkException: Message timeout which can
be caused by communication issues (Failed with error
VDS_NETWORK_ERROR and code 5022)
at
org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:117)
at
org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33)
at
org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2029)
at
org.ovirt.engine.core.bll.CreateAllSnapshotsFromVmCommand$2.runInTransaction(CreateAllSnapshotsFromVmCommand.java:400)
...
As a consequence, Engine is showing a failed snapshot as "Current",
while libvirt is still reporting the previous correct snapshot.
I guess next time Engine will probably try to resume the failed snapshot
and VM won't start anymore.
What is the correct way to solve this issue?
BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1018867
--------------000701090209060705020903
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
A live storage migration task failed due to a network error:<br>
<blockquote>2015-08-03 21:23:16,437 WARN
[org.ovirt.engine.core.bll.CreateAllSnapshotsFromVmCommand]
(org.ovirt.thread.pool-12-thread-45) [] Could not perform live
snapshot due to error, VM will still be configured to the new
created snapshot: VdcBLLException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
VDSGenericException: VDSNetworkException: Message timeout which
can be caused by communication issues (Failed with error
VDS_NETWORK_ERROR and code 5022)<br>
2015-08-03 21:23:16,450 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-12-thread-45) [] Correlation ID: null, Call
Stack: org.ovirt.engine.core.common.errors.VdcBLLException:
VdcBLLException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
VDSGenericException: VDSNetworkException: Message timeout which
can be caused by communication issues (Failed with error
VDS_NETWORK_ERROR and code 5022)<br>
at
org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:117)<br>
at
org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33)<br>
at
org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2029)<br>
at
org.ovirt.engine.core.bll.CreateAllSnapshotsFromVmCommand$2.runInTransaction(CreateAllSnapshotsFromVmCommand.java:400)<br>
...<br>
</blockquote>
As a consequence, Engine is showing a failed snapshot as "Current",
while libvirt is still reporting the previous correct snapshot.<br>
I guess next time Engine will probably try to resume the failed
snapshot and VM won't start anymore.<br>
What is the correct way to solve this issue?<br>
<br>
BZ:<br>
<a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=1018867">https://bugzilla.redhat.com/show_bug.cgi?id=1018867</a><br>
</body>
</html>
--------------000701090209060705020903--
9 years, 3 months
[ACTION REQUIRED] oVirt Engine 3.6 branch created
by Sandro Bonazzola
Hi,
oVirt Engine 3.6 branch has been created from
* 122a3a0 - (HEAD -> master, tag: ovirt-engine-3.6.0_beta1.1,
origin/ovirt-engine-3.6) core: VM pinning to multiple hosts (dwh fix)
<Dudi Maroshi>
We're still setting permissions for the maintainers there but be aware that
all patches targeted to 3.6.0 will need to be cherry-picked on the 3.6
branch too.
Thanks
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
9 years, 3 months