Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore
Change-Id: I45b5b8582b67b39823a6e21221c491842b390b96
With https://review.opendev.org/#/c/716277/, we've started using
osc 5.2.0 which is not backward compatible. Let's bump the
requirement.
Change-Id: Ic135ea0296a139496c9f699f5dbc5c8d3d1f0777
This change replaces all of the ansible shell commands with the
python library, ansible-runner. This library is supported by
upstream ansible, is approved by the openstack foundation, is
supported in global requirements, and provides a better, more
programatic interface into running ansible playbooks.
All tests that interacted with the old shell commands have been
updated to now test using the library.
Change-Id: I8db50da826e2fbc074f4e7986d6fd00f6d488648
Signed-off-by: Kevin Carter <kecarter@redhat.com>
We switched the tripleo-container-image-prepare script in
tripleo-common, but a user will likely run the 'openstack tripleo
container image prepare' command. Currently it uses the default which is
the threading executor.
Poke tripleo common lower/requirements as well.
Change-Id: Ifc5b46633a1f9fc9378eaa17170f6664d566c3c4
Related-Bug: #1844446
We need latest tripleo-common from depends-on to fix the related
bug.
Depends-On: https://review.opendev.org/691370
Change-Id: I3ee7b20db1dd67294b26048185df5a6c58822601
Related-Bug: 1849788
The validations are sequentially executed through ansible-playbook and
could take some time to complete. This patch adds support of running all
the validations in parallel through a ThreadPoolExecutor in order to
save processing time.
Without this patch, it takes almost ~5min to run all the validations but
only ~1min10 with the ThreadPoolExecutor.
- Add --worker/-w argument to give the maximum number of threads that
can be used to execute the given validations
- Python 2.7: use futures backport instead, ThreadPoolExecutor is default
- Use six in tripleo_validator.py for python 3 compatibility
Change-Id: Ia805a556bc26700a3eb520ed72e90b37546901b8
Signed-off-by: Gael Chamoulaud <gchamoul@redhat.com>
This converts Docker*Image params into
Container*Image varients when using tripleo deploy.
In the future we can use it for a few other ad-hoc
Docker* variable substitutions as well to make things
more generic.
Change-Id: Ib1dc0c08ce7971a03639acc42b1e738d93a52f98
The push=False flag with use with kolla-build.conf is not working if we
use buildah, clear example is the
tripleo-build-containers-centos-7-buildah job, it's suppose to work like
docker one but it's pushing too.
Closes-Bug: #1822752
Change-Id: I01788b3c11ac701b2cf8c151f95ccad7046532de
We change behaviour of what is returned by
set_neutron_driver for default network.
So we also need to change this test in tripleoclient
Depends-On: https://review.openstack.org/#/c/643365/
Change-Id: Iea3d6c7591b29f7474be97c939be60f368a04133
Closes-Bug: #1820065
Support Buildah instead of Docker by calling:
$ openstack container image build --use-buildah
And it will build TripleO containers with Buildah and not Docker.
Co-Authored-By: Alex Schultz <aschultz@redhat.com>
Change-Id: I7608136cb213bdca81348a0c3c751b488f48d712
Sometimes it would be beneficial to not build a specific container that
we might normally build. This change adds an --exclude option that can
be used to skip a container when passing it to kolla-build.
Change-Id: Ia871e0a46078a33270516f98ec0e08c1c3a0b43f
Depends-On: https://review.openstack.org/#/c/624530/
Before executing the Undercloud upgrade we need to generate
the containers image like:
openstack overcloud container image prepare \
--namespace
.
In this case we need to have available
the correct images, otherwise we will miss
services and correct versions.
Change-Id: I108180643000ebf349648358c5ced48fce2b3dcb
Resolves: rhbz#1607421
This change adds a new install artifact that contains the heat temporary
directory, hieradata override file, and the ansible scripts used during
the undercloud install.
This includes a new lower limit of tripleo-common 9.0.1
Depends-On: Ie00f71b12f56262985c47810be0e80402e9e558e
Depends-On: I16f19a121212d989e1184103054eb890ec4b9297
Change-Id: I62d34ea7817d5e62613ddcdbb69f2a7463273ccf
Related-Bug: #1761810
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Update the requirement for tripleo-common to reflect reality, and update
the constraint for tenaciy.
Change-Id: Ifdf8dd1c782d6d6ac575d6fd5364dcb083e805a9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Use the websocket api to get and print the real time
ansible execution for minor update instead of using the
zaqarclient call directly.
This is safer and avoid brutal claim of the messages.
Change-Id: I7e324b9e037197082c23a19b4e4b8832daaf5aee
instack-undercloud has support for using a user-provided certificate and
key. This is done through the undercloud_service_certificate
configuration option. This commit adds support for the same
functionality for the containerized undercloud.
It relies on pyca/cryptography, so I added it to the requirements.txt
file. And what it does is that it will read the PEM file and add the
parameter_defaults that are needed to enable TLS.
Change-Id: I26dbde57131f6328d0c5e400dcdfdf62cdd43a41
On minor update, when the execution is still running
but there is no claim message anymore, we should
capture the zaqar exception to not print it to the
console
Change-Id: I802ffd553c54e4a4f9998420645aa078f508b9f0
Closes-Bug: #1734957
The simplejson extends json library. It provides sufficient information about
JSON syntax errors, which often occurs during instackenv.json file creation.
Change-Id: Ied1c080678af728820e02b7b99c51762b49b1449
Closes-Bug: #1693442
Depends on external: https://review.rdoproject.org/r/#/c/7872/
This broke undercloud upgrades - tripleoclient imports
instack_undercloud.undercloud, then upgrades the package.
This means the upgrade call then runs against the old version
of the module, which is incompatible with some of the new
puppet stuff.
Closes-Bug: 1701362
This reverts commit b6e71724e0.
Change-Id: Ie79dfff667437305ff4109da5a9c42ae358b1a3e
For about 2 years we've been indirectly calling the undercloud
install function through a bash script. Originally this was done
to allow for some backwards compatibility with mismatched packages,
but later it was kept because a direct call broke logging. This
is no longer a problem, probably due to some changes in how logging
in instack-undercloud works.
Change-Id: If07880e4bc25cffe485704772d64f62288a1a53d
Depends-On: Iff76f639bcacb5bcc1274fd837e47d34041afa15
Related bp undercloud-upgrade
os-cloud-config has been deprecated in Ocata and we don't need it in
tripleoclient anymore. Let's remove the code that was here for legacy.
Keystone endpoints have been managed by Puppet, so we don't need the
legacy code anymore.
Change-Id: I5662de11620db74fa67fb12c55a3bbd66ed8d3ad
Andreas Jaeger