As repo_build role has been succesfully replaced with
python_venv_build role, we have no need in it's futher maintaining and
releasing.
Depends-On: https://review.opendev.org/717715
Change-Id: Ibf9ce1d602c5cfa9ed7431ca37de02df3335b36a
Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: Ia7d1dc0ba5701335c171d0a5b7cb0c9733c8b90c
Sem-Ver: feature
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: Ie5002038eada0b7b5e54339cd7f7d5e5a21d0399
Sem-Ver: feature
The default upgrade-strategy could change from one version of PIP to
another and the results may be unpredictable. We can control the PIP
behavior during upgrades using the 'upgrade-strategy' option and default
that to 'only-if-required' so PIP only upgrades what's really necessary.
This also ensure that getting the latest pip passes the idempotence test
now that we only upgrade only what's really necessary.
Depends-On: I998182eca9851d2cc745930fc73ca37bfefd0951
Link: https://pip.pypa.io/en/stable/user_guide/#only-if-needed-recursive-upgrade
Co-Authored-By: Jean-Philippe Evrard <jean-philippe@evrard.me>
Change-Id: I2ba89e25c0010c9a5b515a3d0c9c731b30876e74
The pip_required_pip_packages variable was introduced in
order to facilitate installing extra packages required
for SNI support. In Pike these extra package installs
were removed due to interference with distribution
packages installed, and the distro package installation
for this support was deemed better.
This variable and the related tasks therefore no longer
server any function and should be removed.
Change-Id: I76fb9ae324ff69e8fc8b23f7b610d2aca48d0949
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
.
Change-Id: Id38830565773da550326e8edf17f353768d074fd
This patch implements an initial set of jobs intended to match
the current job execution method. It does not intend to improve
how the jobs are executed - only to replicate what is currently
in openstack-infra/openstack-zuul-jobs and provide the platform
to iterate on.
Change-Id: I1c1ebe6a86472acc8c19926e8d2790c3e1ba4812
Allow deployers to choose a specific mirror by setting the
'pip_install_opensuse_mirror_url' variable
Change-Id: I4f4cc284ab7d1c3378e01737f9fade3afe251824
This patch allows deployers to set pip_install_centos_mirror_url
and override the default RDO repository (mirrors.centos.org).
Change-Id: I7b0dd5d14c82a74be955071e638c122ffb45ab31
As part of the docs migration work[0] for Pike we need to switch to use the
openstackdocstheme.
[0]https://review.openstack.org/#/c/472275/
Change-Id: Ie9560ee3fe7b75ae7d51c0665e54f961dd434c93
This patch removes the epel-release package whenever the pip_install
role is applied and should eliminate package conflicts between RDO
and EPEL. The RDO package path is also adjusted to download the RDO
package from repos.fedorapeople.org (which slashes 3 HTTP redirects
out of the 5 when using rdoproject.org).
This is a breaking change for OSA deployments which are already
deployed on CentOS. Some containers may need to be rebuilt after
making this change.
Related-bug: 1670012
Change-Id: I2e69fac6368c032e237ca35839dd09dab9b0c5c0
Add new variables file for SUSE based distributions. SUSE doesn't
provide a keyring package and all requires packages are available in
the default repositories so we skip the relevant tasks.
Change-Id: Ied2960ba3870da8dd88c6f616357ace359b83694
Adds a conditional switch to install the compiler and python
development libraries. The switch is enabled by default to
preserve the old behavior.
Change-Id: If484e14a49c97467a38f9ab6e4b0e3351f60d4ed
Releasenote translation publishing is being prepared. 'locale_dirs'
needs to be defined in conf.py to generate translated version of the
release notes.
Note that this repository might not get translated release notes - or
no translations at all - but we add the entry here nevertheless to
prepare for it.
Change-Id: I2c106196a8c30ffab7529e6a39ec6ac72aacc6fd
The current method of installing the distribution packages required is
set in the tasks and cannot be changed by a deployer.
Currently the apt task always installs the latest package. This results
in unexpected binary changes when a deployer may simply be trying to
execute a configuration change.
This patch adds the ability for a deployer to change the desired state
so that the results are predictable.
Change-Id: I7ddc32b286071b29c197b18370cf49af235527fa
This patch updates the sphinx configuration for docs and releasenotes
to make it easier to replicate across repositories and to comply with
pep8 testing without exceptions.
Change-Id: I2cdbe015043e49a22fc521a4247f9c451eab57a0
The py_pkgs lookup plugin looks for any variables containing
'pip_packages' to find names of Python packages to build.
https://github.com/openstack/openstack-ansible-plugins/blob/master/lookup/py_pkgs.py#L57
Integrated OSA gate testing is currently failing since each character
within '/tmp/pip_install/' is being considered as a package name.
Rename the 'pip_packages_tmp' variable to 'pip_tmp_packages' to avoid it
being evaluated by py_pkgs.
Change-Id: I4d0f40dbb254571b9871d407962627393083d618
Optionally support the download and installation of pip and its dependencies
via the deployment host to remove the dependence of internet connectivity on
remote containers.
When pip_offline_install is true, download get-pip.py and the pip
installation wheels to the deployment host. These wheels along with get-pip.py
are copied to the remote container and the installation is performed
offline.
Change-Id: Ic6583c54976b6fb083d9c67d055897c15bce05dc
Since lockdown is really just a form of specific pip
configuration and since the pip_install role already does
some pip configuration, it seems logical and desirable for
these functions to take place in the same role.
This change should pave the way for a simplification of
role dependencies and the removal of explicit pip_lockdown
role usage with various playbooks that will already have a
dependency on pip_install.
Change-Id: Ia0fc276c2b501f16d4acf73bbbcad6f80804628e