03a57d6668
Before the repo server is up, only bare metal hosts need pip installed, openstack-hosts-setup take care of that part by default, with the openstack_host role calling pip_install. Once the repo server is up, the pypi cache will be available to be used. This implements the changes to detect whether it is available - this is important for the plays doing pip installs before the repo server is available. Once it is available the same plays will use it. To be available, we need to wait for haproxy playbook to load balance towards the repo container, or the baremetal node if need be. Once the repo server and the load balancer are up, we can configure everything to use the repo server, and this will be done with the repo-use.yml playbook, which is calling the pip_install role. We also remove the use of the pip_lock_to_internal_repo from group variables, as we want to change the pip.conf dynamically depending on the availability of the default index. Finally, we set the AIO in OpenStack-Infra to make use of the appropriate infra mirror for the nginx reverse proxy. Because the gates are blocked without this patch, this patch should land in priority. The current upstream state prevents that, so we temporarily disable the ceph testing, which fails due to [1]. On top of it, we need to bump shas to a known working state, else tempest would fail. To avoid circular dependencies, we include the content of patch [2], which is the sha bump pending this work. [1]: https://bugs.launchpad.net/cinder/+bug/1737015 [2]: https://review.openstack.org/#/c/522850/ Change-Id: If19442918baa9ddacf7c19940c9b5007694bee61 Depends-On: I56f22f46ff849a7049ac7ae873af7a4bc526fa63 Depends-On: Ic4fd64f4dc82121a65088f3d7f4ae53f373df608 Depends-On: I7bd31f2d89d3fe9d48e32c79ddef7a8ef1392eb7 Depends-On: Icd93c0c801bfee1b4fdc8154d078067722c0640a Depends-On: I1e9782eb0fd72690a9644c7a01e8c83a4486872b Co-Authored-by: Jesse Pretorius <jesse.pretorius@rackspace.co.uk>
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>.