8511b8dc74
The docs job currently fails due to the missing docs configuration. This change adds the docs structure and updates the requirements in. Change-Id: I9fd6a95c3bedb108af816acdd6cb08ffdab30821 |
||
---|---|---|
doc/source | ||
tripleo_repos | ||
.gitignore | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
tripleo-repos
A tool for managing tripleo repos from places like dlrn and Ceph.
See: https://github.com/openstack-packages/DLRN
Also ensures yum-plugin-priorities is installed since the dlrn repos require that to work sanely.
Note
The tool will remove any delorean* repos at the target location to avoid conflicts with older repos. This means you must specify all of the repos you want to enable in one tripleo-repos call.
Examples
Install current master dlrn repo and the deps repo:
tripleo-repos current
Install current-tripleo dlrn repo and the deps repo:
tripleo-repos current-tripleo
Install the current-tripleo-dev repo. This will also pull current and deps, and will adjust the priorities of each repo appropriately:
tripleo-repos current-tripleo-dev
Install the mitaka dlrn repo and deps:
tripleo-repos -b mitaka current
Write repos to a different path:
tripleo-repos -o ~/test-repos current
Install the current-tripleo, deps, and ceph repos. NOTE: The Ceph repo is installed from a package and thus does not respect -o:
tripleo-repos current-tripleo ceph
TripleO
To use this for TripleO development, replace the tripleo.sh --repo-setup step with the following:
git clone https://github.com/cybertron/tripleo-repos
cd tripleo-repos
sudo ./setup.py install
sudo tripleo-repos current-tripleo-dev ceph
Now you're ready to install the undercloud:
tripleo.sh --undercloud
And to build images:
export OVERCLOUD_IMAGES_DIB_YUM_REPO_CONF="$(ls /etc/yum.repos.d/delorean* /etc/yum.repos.d/CentOS-Ceph-*)"
tripleo.sh --overcloud-images
Note
This is a tool for bootstrapping the repo setup for TripleO, so it should not have any runtime OpenStack dependencies or we end up in a chicken-and-egg pickle, and let's be honest - no one wants a chicken and egg pickle.