Jump to: navigation, search

Difference between revisions of "Packaging/GenericTooling"

(Available Software)
(Available Software: mention OpenBuildService)
 
(2 intermediate revisions by 2 users not shown)
Line 19: Line 19:
 
| [http://anvil.readthedocs.org/ Anvil] || python + rpmbuild... || WIP || yes || WIP || no || yes || [https://github.com/stackforge/anvil  github] || [http://www.godaddy.com GoDaddy], [http://www.yahoo.com Yahoo], [http://www.cray.com/ Cray] || Josh Harlow
 
| [http://anvil.readthedocs.org/ Anvil] || python + rpmbuild... || WIP || yes || WIP || no || yes || [https://github.com/stackforge/anvil  github] || [http://www.godaddy.com GoDaddy], [http://www.yahoo.com Yahoo], [http://www.cray.com/ Cray] || Josh Harlow
 
|-
 
|-
| Delorean || rpmbuild || no || yes || no || no || ? || [https://github.com/openstack-packages/delorean/ github] || RedHat || Derek Higgins
+
| Delorean || rpmbuild || no || yes || no || no || yes || [https://github.com/openstack-packages/delorean/ github] || RedHat || Derek Higgins
 
|-
 
|-
 
| debian-jeinkins-glue || jenkins+pbuilder || yes || no || no || no || ? || [http://jenkins-debian-glue.org/ off. site] || Ubuntu? ||  
 
| debian-jeinkins-glue || jenkins+pbuilder || yes || no || no || no || ? || [http://jenkins-debian-glue.org/ off. site] || Ubuntu? ||  
 
+
|-
 +
| Open Build Service || OpenBuildService || no(but possible) || yes || no || no(but possible) || yes || https://build.opensuse.org/project/subprojects/Cloud:OpenStack || openSUSE || opensuse-cloud@opensuse.org ||
 
|}
 
|}
  
Line 42: Line 43:
 
* Single file that defines what repositories to select from
 
* Single file that defines what repositories to select from
 
* For example, https://github.com/stackforge/anvil/blob/master/conf/origins/icehouse.yaml
 
* 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, build it to)
+
* 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/)
 
* Documentation (for example http://anvil.readthedocs.org/)
 
* Resumeable (aka you can restart the build if 80% of packages were built and that ''one'' failed)
 
* Resumeable (aka you can restart the build if 80% of packages were built and that ''one'' failed)

Latest revision as of 12:34, 10 August 2017

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.

Available Software

Title Build mechanism Deb Output Rpm Ouput Venv Output Image Output Dependency Building Url Company Contact
Giftwrap fpm yes yes yes no  ? github Bluebox Craig Tracey
Anvil python + rpmbuild... WIP yes WIP no yes github GoDaddy, Yahoo, Cray Josh Harlow
Delorean rpmbuild no yes no no yes github RedHat Derek Higgins
debian-jeinkins-glue jenkins+pbuilder yes no no no  ? off. site Ubuntu?
Open Build Service OpenBuildService no(but possible) yes no no(but possible) yes https://build.opensuse.org/project/subprojects/Cloud:OpenStack openSUSE opensuse-cloud@opensuse.org

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

Meetings

Weekly meetings tentatively proposed for 1500 UTC on Mondays

Agendas

agenda 07-12-14