The ansible-devel functional test intends to run against tip of ansible
devel. Let Zuul handle that and depends-on once cross-source depends
exist by listing ansible/ansible as a required-project.
Remove the special install handling, as tox-install-siblings should be
taking care of it now.
Change-Id: I93459ffc116f9106d9eb8000a7e5a58bea507308
Depends-On: Ib5e35315fc9ffe6fa8873ad4975309d9820e1feb
Depends-On: I6d234247e3d45befd264e159c8b0fe77f01c7fdc
After an epic battle with time, the python-ironicclient has been
driven from the land of shade, and there will be joy!
Change-Id: I234e2fc9d1800607c22eb447dd3e77428221695e
All calls to nova are now done via REST. This means we can remove the
dependency.
Only two more to go ...
Change-Id: I01a0afef5986b7452fd73e04c48568ebb9817681
All calls to Designate API are now done with REST calls made
via keystoneauth1
Shade don't require python-designateclient package since now.
Change-Id: I55393dc04ec9eeaba885fee849e6466f199be479
The script to install the git versions of the libraries wasn't working
because it wasn't installing over top of the versions already installed
by pip. So by adding an uninstall first, we ensure that the git version
is actually installed.
Also, add a pbr freeze to the end so that we can verify, and some +x so
that we can see the output of our scripts.
And: novaclient 8.0 doesn't have these calls anymore. However, the tests we
had on legacy clouds were erroneously installing the wrong version of
novaclient so we did not catch it. Doh. This has to do the tests and the
calls in the same patch because the fix to the gate job to install the
correct verison of the library exposed the fact that we had be broken
for these for a few minutes.
Depends-On: I208e8c009d0438de19cd3eb08dc45ddebb45d3e9
Change-Id: I4fd882aeb8373b94c7f6b54d97b457042b324361
All calls to Neutron API are now done with REST calls made
via keystoneauth1.
Shade don't require python-neutronclient package for now.
Change-Id: I0aa6f32b10986e99d6f86cad9640d9d95b5d2cef
Remove heatclient and magnumclient from install-tips
We do not consume them anymore, so do not need to install them as part
of our tips testing.
Install from pip using upper-constraints. To ensure we work with
OpenStack releases.
Change-Id: I98f39d2e2a591eb84a1ebcd033eb51e1758f1f39
We don't even actually use troveclient in shade other than the
constructor. Make it an optional import.
Change-Id: I60b924eb8dfb48c53da0befb39cf84e6c1ea8863
shade has a functional test that intends to test shade against the
current tip of client libs. Unfortunately, what it's really doing is
installing latest release of the library into the shade virtualenv
that's used for functional testing and using tip of library for the
OpenStack install.
This is not a combo we care about.
Instead, install the library tips into the virtualenv. To do this, make
a functional-tips venv for tox, and make the post_test_hook optionally
use it.
Change-Id: Ibac2982e88439362c7af933c3a07c4d581ee6f2b
It's possible enabling OpenStack things can cause other images other
than cirros to be made available (looking at you Magnum). We should
make sure our Ansible tests only look for Cirros.
Change-Id: Iefc01f8033629937552861366b9ddaac8058b249
We haven't been able to test os_server because we haven't had a
way to reliably determine the image name (which changes from time
to time based on version) from the playbook. A stupidly clever
hack is to just grep out the name from a shell call to the openstack
client and pass that in to the playbook from the command line.
The playbook is simple for now for the initial commit. I expect new
tasks to be added to it later.
Change-Id: I3caedfd4c805126c8da1fc8bab06ccda3fd96528
This restores the ability to run the Ansible tests using Ansible
from the source repo rather than the production version from pip.
Using production will be the default, but this sets us up to add
a new job to test against the latest dev version, if we want.
Change-Id: I93cdec653dd672acfbc03576d100d19ab8595f2e
We were using the unreleased (from git) version of Ansible for our
Ansible test job because at the time, 2.0 had not been released. Now
that it is released, use pip to install it so that we are less likely
to get broken by development changes to Ansible.
Change-Id: Ie714f42d26569044b6a3ee761bd5fb7451833d96
It would be *really* cool and useful and stuff to be able to run
the Ansible playbooks against more than just devstack. This change
allows that. Now you can send the -c option to the tox command line:
tox -e ansible -- -c coolcloud
Or, specific tests:
tox -e ansible -- -c coolcloud auth network
Going against devstack is still:
tox -e ansible
tox -e ansible auth network
Change-Id: I666a09aee3d283865c3813d67edfb75123057c22
Now that the Ansible module tests can be run via tox, it
might be nice to allow developers the ability to selectively
run individual module tests (accomplished via Ansible tags) from
tox.
Change-Id: I38a3040a7157a9bcf1cda76e26ab11577e9f80a6
The keypair test needed adjusting so that it would work in
the gating environment, and anywhere an SSH key may not be
available.
Change-Id: Ic9bf41c2b4041911d05217ad3748e097326bac3a
In order to test clouds with no private networks, we need to delete
the ones made by devstack. This is how that works.
Change-Id: I6c9d4d62ea34372d53399aa2b8b27b762d53339b
Monty Taylor