--_=__=_XaM3_.1395917815.2A.679374.42.20528.52.42.007.1564170271
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
+1=0A=0AI'll try soon and migrate our 3.3.x to 3.4!=0A=0Abest regards=0Aa=
=0A=0A=0ADa: announce-bounces(a)ovirt.org=0AA: "users" users(a)ovirt.org, ann=
ounce(a)ovirt.org=0ACc: =0AData: Thu, 27 Mar 2014 05:52:21 -0400 (EDT)=0AOg=
getto: [Users] [Ann] oVirt 3.4 GA Releases=0A=0A=0A> The oVirt Project is=
pleased to announce the general availability of its fifth formal release=
, oVirt 3.4, as of March 27, 2014.=0A> =0A> oVirt is an open source alter=
native to VMware vSphere, and provides an excellent KVM management interf=
ace for multi-node virtualization. oVirt is available now for Fedora 19, =
Red Hat Enterprise Linux 6.5, and CentOS 6.5 (or similar).=0A> =0A> New f=
eatures include:=0A> =0A> oVirt 3.4 Release Notes=0A> =0A> * Hosted Engin=
e: oVirt 3.4 features hosted engine, which enables oVirt engine to be run=
as a virtual machine (VM) on the host it manages. Hosted engine solves t=
he chicken-and-the egg problem for users: the basic challenge of deployin=
g and running an oVirt engine inside a VM. This clustered solution enable=
s users to configure multiple hosts to run the hosted engine, ensuring th=
e engine still runs in the event of any one host failure.=0A> =0A> * Enha=
nced Gluster Support: Gluster Volume Asynchronous Tasks Management enable=
s users to re-balance volumes and remove bricks in Gluster operations/reb=
alance and remove bricks in Gluster volumes.=0A> =0A> * Preview: PPC64: E=
ngine Support for PPC64 will add PPC64 architecture awareness to the ovir=
t-engine code, which currently makes various assumptions based on the x86=
architecture. When specifying virtual machine devices, for example, what=
is suitable for x86 architecture may not be for POWER (or may not be ava=
ilable yet). VDSM Support for PPC64 introduces the capability of managing=
KVM on IBM POWER processors via oVirt. Administrators will be able to pe=
rform management functionalities such as adding or activating KVM, creati=
ng clusters of KVM and performing VM lifecycle management on any IBM POWE=
R host. Migration is still a work in progress for KVM on IBM POWER proces=
sor.=0A> =0A> * Preview: Hot-plug CPUs: oVirt 3.4 adds a preview of a Hot=
-plug CPU feature that enables administrators to ensure customer's servic=
e-level agreements are being met, the full utilization of spare hardware,=
and the capability to dynamically to scale vertically, down or up, a sys=
tem's hardware according to application needs without restarting the virt=
ual machine.=0A> =0A> This release of oVirt also includes numerous bug fi=
xes. See the release notes [1] for a complete list of the new features an=
d bugs fixed.=0A> =0A> The existing repository ovirt-stable has been upda=
ted for delivering this release without the need of enabling any other re=
pository.=0A> =0A> A new oVirt Node build is also available [2].=0A> =0A>=
[1]
http://www.ovirt.org/OVirt_3.4_Release_Notes=0A> [2]
http://resource=
s.ovirt.org/releases/3.4/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34=
.el6.iso=0A> =0A> -- =0A> Brian Proffitt - oVirt Community Manager=0A> IR=
C: bkp @ #ovirt OFTC=0A> _______________________________________________=0A=
Announce mailing list=0A> Announce(a)ovirt.org=0A>
http://lists.ovirt.org= /mailman/listinfo/announce
--_=__=_XaM3_.1395917815.2A.679374.42.20528.52.42.007.1564170271
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
=0A<div class=3D"xam_msg_class">=0A<div style=3D"font: normal 13px
Arial;=
color:rgb(31, 28, 27);">+1<br><br>I'll try soon and migrate our
3.3.x to=
3.4!<br><br>best regards<br>a<br><br>=0A<div><span
style=3D"font-family:=
Arial; font-size:11px; color:#5F5F5F;">Da</span><span
style=3D"font-famil=
y:Arial; font-size:12px; color:#5F5F5F; padding-left:5px;">: announce-bou=
nces(a)ovirt.org</span></div>=0A<div><span
style=3D"font-family:Arial; font=
-size:11px; color:#5F5F5F;">A</span><span
style=3D"font-family:Arial; fon=
t-size:12px; color:#5F5F5F; padding-left:5px;">: "users"
users(a)ovirt.org,=
announce(a)ovirt.org</span></div>=0A<div><span
style=3D"font-family:Arial;=
font-size:11px; color:#5F5F5F;">Cc</span><span
style=3D"font-family:Aria=
l; font-size:12px; color:#5F5F5F; padding-left:5px;">:
</span></div>=0A<d=
iv><span style=3D"font-family:Arial; font-size:11px;
color:#5F5F5F;">Data=
</span><span style=3D"font-family:Arial; font-size:12px; color:#5F5F5F; p=
adding-left:5px;">: Thu, 27 Mar 2014 05:52:21 -0400
(EDT)</span></div>=0A=
<div><span style=3D"font-family:Arial; font-size:11px;
color:#5F5F5F;">Og=
getto</span><span style=3D"font-family:Arial; font-size:12px; color:#5F5F=
5F; padding-left:5px;">: [Users] [Ann] oVirt 3.4 GA
Releases</span></div>=
=0A<br>=0A<div>> The oVirt Project is pleased to announce the general
=
availability of its fifth formal release, oVirt 3.4, as of March 27, 2014=
.</div><div>> </div><div>> oVirt is an open source
alternative to V=
Mware vSphere, and provides an excellent KVM management interface for mul=
ti-node virtualization. oVirt is available now for Fedora 19, Red Hat Ent=
erprise Linux 6.5, and CentOS 6.5 (or similar).</div><div>>
</div><div=
> New features include:</div><div>>
</div><div>> oVirt 3.4 Rele=
ase
Notes</div><div>> </div><div>> * Hosted Engine:
oVirt 3.4 featu=
res hosted engine, which enables oVirt engine to be run as a virtual mach=
ine (VM) on the host it manages. Hosted engine solves the chicken-and-the=
egg problem for users: the basic challenge of deploying and running an o=
Virt engine inside a VM. This clustered solution enables users to configu=
re multiple hosts to run the hosted engine, ensuring the engine still run=
s in the event of any one host failure.</div><div>>
</div><div>> * =
Enhanced Gluster Support: Gluster Volume Asynchronous Tasks Management en=
ables users to re-balance volumes and remove bricks in Gluster operations=
/rebalance and remove bricks in Gluster volumes.</div><div>>
</div><di=
v>> * Preview: PPC64: Engine Support for PPC64 will add PPC64 architec=
ture awareness to the ovirt-engine code, which currently makes various as=
sumptions based on the x86 architecture. When specifying virtual machine =
devices, for example, what is suitable for x86 architecture may not be fo=
r POWER (or may not be available yet). VDSM Support for PPC64 introduces =
the capability of managing KVM on IBM POWER processors via oVirt. Adminis=
trators will be able to perform management functionalities such as adding=
or activating KVM, creating clusters of KVM and performing VM lifecycle =
management on any IBM POWER host. Migration is still a work in progress f=
or KVM on IBM POWER processor.</div><div>>
</div><div>> * Preview: =
Hot-plug CPUs: oVirt 3.4 adds a preview of a Hot-plug CPU feature that en=
ables administrators to ensure customer's service-level agreements are be=
ing met, the full utilization of spare hardware, and the capability to dy=
namically to scale vertically, down or up, a system's hardware according =
to application needs without restarting the virtual
machine.</div><div>&g=
t; </div><div>> This release of oVirt also includes numerous bug
fixes=
. See the release notes [1] for a complete list of the new features and b=
ugs fixed.</div><div>> </div><div>> The existing
repository ovirt-s=
table has been updated for delivering this release without the need of en=
abling any other repository.</div><div>>
</div><div>> A new oVirt N=
ode build is also available [2].</div><div>>
</div><div>> [1] http:=
//www.ovirt.org/OVirt_3.4_Release_Notes</div><div>> [2]
http://resourc=
es.ovirt.org/releases/3.4/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm3=
4.el6.iso</div><div>> </div><div>> --
</div><div>> Brian Proffit=
t - oVirt Community Manager</div><div>> IRC: bkp @ #ovirt
OFTC</div><d=
iv>>
_______________________________________________</div><div>> An=
nounce mailing list</div><div>>
Announce(a)ovirt.org</div><div>&gt; http=
://lists.ovirt.org/mailman/listinfo/announce</div></div>=0A</div>=0A
--_=__=_XaM3_.1395917815.2A.679374.42.20528.52.42.007.1564170271--