Packaging/GenericTooling

Packaging Tooling
This page is primarily concerned with tooling that can satisfy the needs of operators requiring a build process that can produce OpenStack packages given a set of git repos.

History
At the 2014 OpenStack summit in Paris, a group of Operators met to discuss collaboration opportunities for tooling related to the operation of OpenStack clusters. Packaging was one of the major topics. The etherpad can be found here

Following this, a mailing list thread was created on openstack-operators@openstack.org to discuss the available options and a potential path towards consolidation of packaging tools.

Requirements
A tool that consumes a list of OpenStack git repos and produces packages


 * Numerous requests for both deb and rpm support
 * Some folks don't like the idea of using things that are not rpmbuild/dpkg-buildpackage
 * Nice to be able to start from a stable base (eg RDO) and go from there
 * Most folks not particularly attached to their tooling and would happily switch
 * Patch support
 * Basic requirement dependency analysis (aka blowup if not possible to satisfy requirements)
 * No humans involved in the build/update process (automatable)
 * Easily able to add new projects (since new projects seem to appear every day...)

Nice to haves

 * Single file that defines what repositories to select from
 * For example, https://github.com/stackforge/anvil/blob/master/conf/origins/icehouse.yaml
 * Dependency building (aka if some dependency is needed but not available in distro repositories, automatically build it to)
 * Documentation (for example http://anvil.readthedocs.org/)
 * Resumeable (aka you can restart the build if 80% of packages were built and that one failed)

Meetings
Weekly meetings tentatively proposed for 1500 UTC on Mondays

Agendas

agenda 07-12-14