--_32f83bcc-43c9-436c-808b-5c521bcabddb_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
On Tue=2C Oct 20=2C 2015 at 4:51 AM=2C Dan Kenigsberg <danken at
redhat.c=
om> wrote:=0A=
=0A=
> On Mon=2C Oct 19=2C 2015 at 09:16:06PM +0200=2C Johan Kooijman wrote:=
=0A=
> > Never seen an update to this ticket. Are there any
plans?=0A=
> >=0A=
> > On Tue=2C Jun 24=2C 2014 at 3:35 PM=2C Sven Kieske <S.Kieske at mittw=
ald.de>=0A=
> wrote:=0A=
> >=0A=
> > >=0A=
> > >=0A=
> > > Am 24.06.2014 15:13=2C schrieb Nathana=EBl Blanchet:=0A=
> > > > Hi all=2C=0A=
> > > >=0A=
> > > > now rhel7 is out=2C it will become a part of the ovirt project in=
a=0A=
> near=0A=
> > > > future. Given taht official LXC support aims to complete the KVM=
=0A=
> > > > virtualization part=2C is LXC planned to be
supported for linux =
VM by=0A=
> > > > ovirt=2C like openvz is with proxmox?=0A=
> > >=0A=
> > > very good question=2C can't wait to read an answer!=0A=
> > > +1 from here.=0A=
>=0A=
> I'm not aware of current plans. We can consider this when ovirt-4.0=0A=
> feature request season opens.=0A=
>=0A=
> Until then=2C can you share your own use case for runnig LXC?=0A=
>=0A=
=0A=
It seems like Proxmox have quite the install base especially due to the=
=0A=
ability to mix containers and "fat" VMs. AFAIK that's
the only feature th=
ey=0A=
have that is ahead of oVirt. And that install base should tell us
this is=
=0A=
indeed a feature needed and widely used.=0A=
=0A=
=0A=
>=0A=
> I'd love to see a vdsm hook that translates the qemu-kvm domxml into an=
=0A=
> lxc one=2C as a first step. Anyone?=0A=
>=0A=
=0A=
That can be a fun project to do=2C but I'm not volunteering just yet =3B)=
=0A=
=0A=
=0A=
>=0A=
> Dan.=0A=
> _______________________________________________=0A=
> Users mailing list=0A=
> Users at ovirt.org=0A=
>
http://lists.ovirt.org/mailman/listinfo/users=0A=
>=0A=
+1
A couple of related questions:
*) what can we expect from the deprecation of libvirt LXC driver in RHEL? (=
CentOS would follow suit=2C barring an extraordinary effort from the Virtua=
lization SIG=2C akin to the Xen-on-CentOS one)
*) dreaming of a future convergence of oVirt-node and Atomic would be... we=
ll=2C just dreaming? =3B)
Giuseppe
=
--_32f83bcc-43c9-436c-808b-5c521bcabddb_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'><pre><span
style=3D"white-space:=
pre-wrap=3B">>=3B On Tue=2C Oct 20=2C 2015 at 4:51 AM=2C Dan Kenigsberg =
<=3Bdanken at redhat.com>=3B wrote:=0A=
>=3B =0A=
>=3B >=3B On Mon=2C Oct 19=2C 2015 at 09:16:06PM +0200=2C Johan Kooijma=
n wrote:=0A=
>=3B >=3B >=3B Never seen an update to this ticket. Are there any pl=
ans?=0A=
>=3B >=3B >=3B=0A=
>=3B >=3B >=3B On Tue=2C Jun 24=2C 2014 at 3:35 PM=2C Sven Kieske
<=
=3BS.Kieske at mittwald.de>=3B=0A=
>=3B >=3B wrote:=0A=
>=3B >=3B >=3B=0A=
>=3B >=3B >=3B >=3B=0A=
>=3B >=3B >=3B >=3B=0A=
>=3B >=3B >=3B >=3B Am 24.06.2014 15:13=2C schrieb Nathana=EBl
Blan=
chet:=0A=
>=3B >=3B >=3B >=3B >=3B Hi all=2C=0A=
>=3B >=3B >=3B >=3B >=3B=0A=
>=3B >=3B >=3B >=3B >=3B now rhel7 is out=2C it will become
a par=
t of the ovirt project in a=0A=
>=3B >=3B near=0A=
>=3B >=3B >=3B >=3B >=3B future. Given taht official LXC
support =
aims to complete the KVM=0A=
>=3B >=3B >=3B >=3B >=3B virtualization part=2C is LXC
planned to=
be supported for linux VM by=0A=
>=3B >=3B >=3B >=3B >=3B ovirt=2C like openvz is with
proxmox?=0A=
>=3B >=3B >=3B >=3B=0A=
>=3B >=3B >=3B >=3B very good question=2C can't wait to read
an ans=
wer!=0A=
>=3B >=3B >=3B >=3B +1 from here.=0A=
>=3B >=3B=0A=
>=3B >=3B I'm not aware of current plans. We can consider this when ovi=
rt-4.0=0A=
>=3B >=3B feature request season opens.=0A=
>=3B >=3B=0A=
>=3B >=3B Until then=2C can you share your own use case for runnig LXC?=
=0A=
>=3B >=3B=0A=
>=3B =0A=
>=3B It seems like Proxmox have quite the install base especially due to =
the=0A=
>=3B ability to mix containers and "fat" VMs. AFAIK that's the only
featu=
re they=0A=
>=3B have that is ahead of oVirt. And that install base should tell us th=
is is=0A=
>=3B indeed a feature needed and widely used.=0A=
>=3B =0A=
>=3B =0A=
>=3B >=3B=0A=
>=3B >=3B I'd love to see a vdsm hook that translates the qemu-kvm domx=
ml into an=0A=
>=3B >=3B lxc one=2C as a first step. Anyone?=0A=
>=3B >=3B=0A=
>=3B =0A=
>=3B That can be a fun project to do=2C but I'm not volunteering just yet=
=3B)=0A=
>=3B =0A=
>=3B =0A=
>=3B >=3B=0A=
>=3B >=3B Dan.=0A=
>=3B >=3B _______________________________________________=0A=
>=3B >=3B Users mailing list=0A=
>=3B >=3B Users at ovirt.org=0A=
>=3B >=3B
http://lists.ovirt.org/mailman/listinfo/users=0A=
>=3B >=3B=0A=
</span></pre><div>+1</div><div><br></div><div>A
couple of related questions=
:</div><div><br></div><div>*) what can we expect from the
deprecation of li=
bvirt LXC driver in RHEL? (CentOS would follow suit=2C barring an extraordi=
nary effort from the Virtualization SIG=2C akin to the Xen-on-CentOS one)</=
div><div><br></div><div>*) dreaming of a future convergence of
oVirt-node a=
nd Atomic would be... well=2C just dreaming?
=3B)</div><div><br></div><div>=
Giuseppe</div><div><br></div>
</div></body>
</html>=
--_32f83bcc-43c9-436c-808b-5c521bcabddb_--