openstack team mailing list archive

[Soren Hansen <soren@xxxxxxxxxxx>]

2011/7/7 Todd Deshane <todd.deshane@xxxxxxx>:
> I'd like to propose adding packaging scripts (a Makefile and a RPM
> spec file) [0] to the nova tree in plugins/xenserver/xenapi to make
> the setup process for Xen Cloud Platform (XCP) OpenStack admins
> simpler (specifically removing the need to have a nova source code
> check to *use* the plugins, like the developers do [1]).

If these packages are to be distributed through Xen.org anyway, why
does the average openstack admin need to build them?

> The Kronos audience will not use this RPM, but instead will want
> Debian packages. So at that point, we could either extend the Makefile
> and add Debian packaging information or alternatively we could use the
> OpenStack Ubuntu packagers [4] infrastructure to build and distribute
> the Debian packages containing the XenAPI OpenStack plugins.

I'd much prefer the latter. (Note: I'm one of the drivers of the
openstack-ubuntu-packagers team)

> To summarize the implicit questions:
>
> 1) Is the plan to have the RPM build scripts in the nova tree acceptable?

My gut feeling is "no". We intentionally kept the Ubuntu/Debian
packaging outside nova proper. It'll never keep up with the actual
packaging anyway and doing packaging is a separate effort from doing
"upstream" development.

That said, I'd be happy to have the binary RPM be built on our
infrastructure, but I believe the code belongs outside.

> 2) Is it desirable to keep the Ubuntu packaging code in [4] or will it
> be just as fine to have the build script in the nova tree?

Answered above :)

> 3) Does the overall distinction between Citrix XenServer, XCP, and
> project Kronos make sense?

I think so.


-- 
Soren Hansen        | http://linux2go.dk/
Ubuntu Developer    | http://www.ubuntu.com/
OpenStack Developer | http://www.openstack.org/