Would it make sense to leverage packagekit to abstract away the distro
packaging differences?
From: "Alon Bar-Lev" <alonbl(a)redhat.com>
To: "Zhou Zheng Sheng" <zhshzhou(a)linux.vnet.ibm.com>
Cc: "engine-devel" <engine-devel(a)ovirt.org>
Sent: Wednesday, November 20, 2013 9:53:29 AM
Subject: Re: [Engine-devel] Things to be done to support Ubuntu hosts
----- Original Message -----
> From: "Zhou Zheng Sheng" <zhshzhou(a)linux.vnet.ibm.com>
> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> Cc: "engine-devel" <engine-devel(a)ovirt.org>
> Sent: Wednesday, November 20, 2013 3:53:17 AM
> Subject: Re: Things to be done to support Ubuntu hosts
>
> on 2013/11/16 02:52, Alon Bar-Lev wrote:
> >
> >
> > ----- Original Message -----
> >> From: "Zhou Zheng Sheng" <zhshzhou(a)linux.vnet.ibm.com>
> >> To: "engine-devel" <engine-devel(a)ovirt.org>
> >> Cc: "Itamar Heim" <iheim(a)redhat.com>, "Alon
Bar-Lev" <alonbl(a)redhat.com>
> >> Sent: Thursday, November 14, 2013 8:57:19 AM
> >> Subject: Things to be done to support Ubuntu hosts
> >>
> >> Hi,
> >>
> >> Recently Ubuntu support is added to VDSM, and .deb binray packages can
> >> be downloaded from
launchpad.net PPA [1]. Most of the key features such
> >> as storage management and VM lifecycle work on Ubuntu. The cross
> >> distribution network management patches are upstream as well. One big
> >> piece left is making ovirt-host-deploy support Ubuntu, so that we can
> >> manage Ubuntu hosts from Engine, thus close the gap on host side.
> >>
> >> In May 2013 I made some hacks to ovirt-host-deploy and otopi. I made it
> >> skipped parts not supported on Ubuntu and configure the environment
> >> manually, and successfully added Ubuntu host to Engine [2].
> >> Unfortunately I have no plans to continue on it, but I'd like to make
a
> >> summary of the things I hacked to help anyone who wants to submit
> >> patches in future. I was to add a WIKI page but I found there were not
> >> many items, so a mail would be enough.
> >>
> >> 1. Package management operations
> >> Both otopi and ovirt-host-deploy query for dependency packages and
> >> install them on demand. The otopi package management just supports yum,
> >> we need to add apt-get support. Package names are different in Ubuntu,
> >> so I made a list mapping the names. The list in in VDSM source
> >> directory, debian/dependencyMap.txt .
> >
> > Please try putting the following file on host:
> >
> > /etc/ovirt-host-deploy.conf.d/10-ubuntu.conf
> > ---
> > ODEPLOY/offlinePackager=bool:True
> > ---
> >
> > This will replace the disable section of packaging in your patch.
> > It will make host-deploy not to install any package and assume all is
> > pre-installed.
> >
>
> Great! Do we have plan to implement apt-get support in ovirt-host-deploy?
Plans - yes.
Not sure when exactly.
I prefer first to handle the ovirt-engine porting to ubuntu at first
opportunity.
>
> >>
> >> 2. Network configuration operations
> >> ovirt-host-deploy asks VDSM's configNetwork.py to create bridge
network.
> >> Cross distribution support patches for configNetwork.py are under
> >> review. ovirt-host-deploy supports Ubuntu bridge configuration as long
> >> as they are merged.
> >
> > This is not happening any more at 3.3, so no need to change anything.
> >
> > I think that in 3.3 with the above offline packaging use, you can use
> > vanilla otopi/host-deploy.
> >
> > Regards,
> > Alon Bar-Lev
> >
> >>
> >> [1]
https://launchpad.net/~zhshzhou/+archive/vdsm-ubuntu
> >> [2]
http://www.ovirt.org/images/5/57/Shanghai-VDSM-on-Ubuntu.pdf
> >>
> >> Here goes the detailed hack patch. The hack was base on v1.0.1, I
> >> rebased it to the latest master. The rebased patch are not tested. If
> >> you find this email useless, it's actually a good news, which means
> >> there is not a lot of work and problems ahead ;-)
> >>
> >> Hack patch for ovirt-host-deploy.
> >>
> >> From 120493a242046d19794ef3da83b32486d372aa39 Mon Sep 17 00:00:00 2001
> >> From: Zhou Zheng Sheng <zhshzhou(a)linux.vnet.ibm.com>
> >> Date: Wed, 13 Nov 2013 18:02:26 +0800
> >> Subject: [PATCH] Ubuntu Hacks
> >>
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel