[openstack-dev] [Fuel] Packaging CI for Fuel

Vladimir Kozhukalov vkozhukalov at mirantis.com
Fri Mar 18 10:11:05 UTC 2016


> Are there any effort on OpenStack packaging?

The short answer is yes. We are putting efforts to migrate all
our packaging activities to the community RPM/DEB projects.

Long story is as follows:

At the moment Fuel is distributed as a set of RPM packages. This
Packaging CI that Aleksandra mentioned is nothing more
but a copy of CI that we have been using at Mirantis for about
two years. At the moment we are working hard to split Fuel
into upstream (community) and downstream (part of MOS) and this
CI is a part of this work.

Currently, OpenStack RPM project is at the early development stage.
It is another project (not Fuel) and I hope it will be finally
possible to build RPM packages using OpenStack Infrastructure.
We (Fuel) are in contact with OpenStack RPM team and we are planning
to move all Fuel RPM specs under this project. I hope this migration
will be finished in Newton cycle.

Besides, packaging is not just preparing RPM/DEB specs. We also
need tools to build packages as well as CI strategy
 - get spec here
 - get source code there
 - prepare build environment
 - build packages
 - publish packages to testing repository
 - test packages
 - publish packages to current public repository
Fuel Packaging CI already does this. And the fact that we made a public
Packaging CI instance reflects our intention to share our experience.

I'd also like to mention our recent initiative Packetary [1] which is
a tool that is to cover the whole RPM/DEB packaging domain
(building packages, building repositories, clonning repositories).
It is not something totally new, it is to become a single convenient API to
widely used tools like createrepo, python-debian, mock, sbuild, etc.
This tools could be potentially used as a part of whatever CI or by
a regular user via CLI.

As for DEB packaging, as Thomas wrote, he is currently working on making
this possible to build DEB packages (including Fuel) using OpenStack

[1] https://wiki.openstack.org/wiki/Packetary

Vladimir Kozhukalov

On Fri, Mar 18, 2016 at 12:11 AM, Thomas Goirand <zigo at debian.org> wrote:

> On 03/16/2016 06:22 PM, Emilien Macchi wrote:
> > Are they any effort on OpenStack packaging?
> >
> > http://governance.openstack.org/reference/projects/packaging-deb.html
> > http://governance.openstack.org/reference/projects/packaging-rpm.html
> >
> > I would like to see packaging built & tested by OpenStack Infra, so
> > downstream CI (Fuel, Puppet OpenStack, TripleO, Kolla, etc) could use
> > it as a single place and efforts would converge.
> Hi Emilien,
> As you know, things were a bit stuck, with the Debian image patch not
> being approved. But it has changed, and we do have a debian-jessie image
> in infra now. Therefore, I've move to the next step, which is actually
> building packages. Here's the CR:
> https://review.openstack.org/#/c/294022/
> I've been able to test the pkgdeb-install-sbuild.sh script that I'm
> proposing to setup sbuild on a copy of the Debian image (thanks a lot to
> Pabelanger and Fungi copy the image, and give it to me for download),
> and sbuild was setup properly. The pkgdeb-build-pkg.sh also worked,
> though I'm not 100% sure yet about the content of
> /home/jenkins/workspace/${JOB_NAME}, if it will have the correct branch
> or what, but everything else should be working to build packages.
> Once packages are built, then we will want to publish them somewhere.
> That's the part where there's lots of unknown. This has so far never
> been done on OpenStack infra. Hopefully, our new PTL will probably help
> here (or someone else from infra)! :) Also, managing a Debian repository
> isn't really hard to do: one can generate the necessary artifacts with a
> small shell script which uses apt-ftparchive (you can look how its done
> at src/pkgos-scan-repo in openstack-pkg-tools).
> Finally, we'll need a way to build backports from Sid and also publish
> them.
> That's where we are now. Let's go back to the first step, which is the
> CR linked above. Help and comments welcome.
> Cheers,
> Thomas Goirand (zigo)
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160318/e6c02009/attachment.html>

More information about the OpenStack-dev mailing list