6677e1ef8f
When re-running openstack-hosts after a greenfield deployment the repo servers will be reconfigured to make use of the pypi cache implemented on the repo host. There is therefore no real reason why it should not be done sooner during the greenfield deploy - otherwise the deployment is inconsistent. Also, in a situation where the deployment has no containers, not implementing the configuration to use the repo pypi cache results in the rest of the deployment not being able to find the packages which were built from source. It instead makes all pip installs go to pypi and never even attempt the cache. Finally, once the repo build is complete the repo-use playbook is run to ensure that pip is reconfigured to use it - but the facts to set the default pip index were set prior to the repo being built, so the reconfiguration leaves the default pip index to that of pypi. as such, in this patch, we re-verify and re-set the applicable vars to ensure that the repo is used. Depends-On: https://review.openstack.org/563106 Depends-On: https://review.openstack.org/563111 Change-Id: I2e7f9bc6cbf15b3309f843ffc24b4643563906a0 |
||
---|---|---|
deploy-guide/source | ||
doc | ||
etc | ||
inventory | ||
osa_toolkit | ||
playbooks | ||
releasenotes | ||
scripts | ||
tests | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
ansible-role-requirements.yml | ||
ansible-role-requirements.yml.example | ||
bindep.txt | ||
global-requirement-pins.txt | ||
LICENSE.txt | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
Vagrantfile |
Team and repository tags
OpenStack-Ansible
OpenStack-Ansible is an official OpenStack project which aims to deploy production environments from source in a way that makes it scalable while also being simple to operate, upgrade, and grow.
For an overview of the mission, repositories and related Wiki home page, please see the formal Home Page for the project.
For those looking to test OpenStack-Ansible using an All-In-One (AIO) build, please see the Quick Start guide.
For more detailed Installation and Operator documentation, please see the Deployment Guide.
If OpenStack-Ansible is missing something you'd like to see included, then we encourage you to see the Developer Documentation for more details on how you can get involved.
Developers wishing to work on the OpenStack-Ansible project should always base their work on the latest code, available from the master GIT repository at Source.
If you have some questions, or would like some assistance with
achieving your goals, then please feel free to reach out to us on the OpenStack Mailing Lists
(particularly openstack-operators or openstack-dev) or on IRC in
#openstack-ansible
on the freenode network.
OpenStack-Ansible Roles
OpenStack-Ansible offers separate role repositories for each individual role that OpenStack-Ansible supports. For individual role configuration options, see the Role Documentation.
An individual role's source code can be found at: https://git.openstack.org/cgit/openstack/openstack-ansible-<ROLENAME>.