RPM packaging templates for OpenStack
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul 7c47068ee7 Merge "futurist: update to 2.4.1" 3 days ago
airship Adding airship folder for packaging airship components 3 years ago
epoch Add epoch to Tempest 6 years ago
openstack Merge "futurist: update to 2.4.1" 3 days ago
tools Adding airship folder for packaging airship components 3 years ago
.gitignore Update .gitignore to ignore out logs 6 years ago
.gitreview OpenDev Migration Patch 3 years ago
.zuul.yaml Zuul: Remove project name 4 years ago
CONTRIBUTING.rst [community goal] Update contributor documentation 9 months ago
LICENSE Add initial README/LICENSE 7 years ago
README.rst Switch to OFTC 11 months ago
bindep.txt Move other-requirements.txt to bindep.txt 6 years ago
global-requirements.txt Remove global-requirements.txt copy 4 years ago
test-requirements.txt Use python3 as python for envs as spec_cleaner dropped python2 4 years ago
tox.ini Update the constraints url 3 years ago


Team and repository tags


RPM Packaging for OpenStack README

RPM packaging for OpenStack provides RPM spec file templates and tooling for building OpenStack packages for RPM based distributions.

RPM packaging for OpenStack is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.

For more information, please follow the link to the wiki page:


In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:


Developers wishing to work on the RPM packaging for OpenStack project should always base their work on the latest code, available from the master GIT repository at:


Developers should also join the discussion on the mailing list, at:


or join the IRC channel on