There were a few references of keystoneclient in
exercises/neutron-adv-test.sh, this patch will change those
commands to their openstackclient equivalents.
Change-Id: I88892fcfacd3dd6354ec269b270cee3da358447a
Ironic on Devstack does not currently suppport security groups or
anything volume related. Add some special casing so exercises can
be run without error against the Ironic driver.
Change-Id: I2a54d8cca06fc17894e74b4401af9423cef95635
Updated the only instance of a keystoneclient command, to
check if the identity service is enabled.
Change-Id: If86f71c1610a79690d6c6a8eb423b6fa234372bb
with I1c9bea2fdeebc4199c4f7d8fca4580a6fb7fed5b nova removed
docker from it's driver tree.
We shouldn't have driver support inside of devstack that's not
part of upstream projects (this has been a line we've been
pretty clear on with Neutron drivers in the past).
Remove docker driver accordingly.
Change-Id: Ib91d415ea1616d99a5c5e7bc3b9015392fda5847
Every once in a while I see this error running floating_ips.sh:
/devstack/exercises/floating_ips.sh:184:ping_check
/devstack/functions:356:_ping_check_neutron
/devstack/lib/neutron:904:die
[ERROR] /devstack/lib/neutron:904 [Fail] Could ping server
I think the problem is that it immediately tries to ping right
after the icmp rule is deleted. Add a timeout and check so we
at least wait one second.
Change-Id: I753ec257fa12f6d2ddff1a5b1909e32d8995e173
Without lib/neutron, boot_from_volume.sh generates the following
error:
+ _ping_check_neutron private 10.11.12.5 30
/devstack/functions: line 356: _ping_check_neutron: command not found
Change-Id: Ib72c3f24d614570d69bf5dda35cbaf5847b1d1b9
* Remove the check for neutron enabled on a block of variable settings, there
is no conflict and serves no purpose.
* Also floating_ips.sh and volume.sh needed to properly source lib/neutron
for do ping_check() to work properly.
The current error in check-devstack-dsvm-neutron is not related to this fix.
Change-Id: I1c458aaa787ffb98c945aefc3afa80c6861a405f
Check that function calls look like ^function foo {$ in bash8, and fix
all existing failures of that check. Add a note to HACKING.rst
Change-Id: Ic19eecb39e0b20273d1bcd551a42fe400d54e938
This converts the special cases in the is_service_enabled() function to call
individual functions declared by the projects. This allows projects that
are not in the DevStack repo and called via the extras.d plugin to handle
an equivalent service alias.
* Ceilometer
* Cinder
* Glance
* Neutron
* Nova
* Swift
TODO: remove the tests from is_service_enabled() after a transition period
Patch Set 2: Rebased
Change-Id: Ic78be433f93a9dd5f46be548bdbd4c984e0da6e7
This patch silences commands that echoed copyright notices to the
devstack logs. The copyright notices are moved to the top of the
file as comments.
Change-Id: I8d474a366af2954c168ba8d07329392f56e8e75a
Because neutron-debug create-probe needs admin role only, demo tenants
cannot create ports. neutron-debug is wrapped in order to run it only
with admin tenant.
Change-Id: Ib65e8639858c597345c6a5fdc0192b40f34a0300
Closes-Bug: #1269090
(Formerly known as Nicira NVP plugin).
Following Neutron change 79fbeb7ebebc0dfbe143aee96fbc250d1b9e7582,
this patch introduces the new naming scheme for Neutron VMware NSX
plugin configuration.
Related-blueprint: nvp-third-part-support (aka bp vmware-nsx-third-party)
Partial-implements blueprint: nicira-plugin-renaming
Change-Id: If7790887661507bfdec6d2b97c0f99609039aa73
This patch fixes a couple of issues, that prevents marconi from running
on devstack.
Change-Id: I47060a0334ad6f90f1402b34c83bb6ad22f723d4
Closes-Bug: #1260820
Marconi has an optional dependency on keystone for authentication. This
code was tested with everything enabled and also with the following
localrc:
STACK_USER=fedora
SERVICE_TOKEN=secrete
ADMIN_PASSWORD=secrete
MYSQL_PASSWORD=secrete
RABBIT_PASSWORD=secrete
SERVICE_PASSWORD=secrete
disable_all_services
enable_service qpid
enable_service key
enable_service mysql
enable_service marconi-server
Implements blueprint marconi-devstack-integration
Implements blueprint devstack-support
Change-Id: I13495bcc5c5eb66cee641894e9f84a0089460c8b
No other hypervisor has a dedicated exercise, docker should be
tested just by testing the nova APIs, not on it's own.
Change-Id: Ifc788815380e8502449171410dea8260786a1e79
Address miscellaneous issues with Markdown formatting in comments which
are consumed by shocco when generating the online documentation.
Change-Id: I953075cdbddbf1f119c6c7e35f039e2e54b79078
A few Markdown-oriented issues were causing Docutils errors to
leak into the end-user docs on http://devstack.org
Change-Id: I51fa9698afb1bfb48596478d83bd1fdcd84ac52e
When 'keystone token-get' fails, the caller can't detect the failure.
This cause troulbe shooting a bit complicated.
Change-Id: I3c58c5fd0e92a87e87546ea797904e08646a1097
Closes-Bug: #1238412
The actual regex checks a result in python format and
because of the change in the bug 1132961, Jekins failed.
I have update the regex to work with the old result
and the new result.
Change-Id: I393e1358f99be5f20d9ac8b3e214355a453ecfcb
Closes-Bug: 1239726
- Added changes to stackrc for the Trove Repos.
- Added support to devstack for "install", "configure",
"init", and "run"
implements blueprint:trove-devstack-integration
Change-Id: Ib3f6daad33e629f764a174b80762c808ce8588e2
* Add basic support for hypervisor plugins in lib/nova_plugins
* Add lib/nova_plugins/hypervisor-docker to use Docker as a Nova
hypervisor.
* Add tools/install_docker.sh to install the Docker daemon and
registry container, download base image and import
* Configure Nova to use docker plugin
* Add docker exercise and skip unsupported ones
Nova blueprint: new-hypervisor-docker
Change-Id: I9e7065b562dce2ce853def583ab1165886612227
The cause of some gating failure looks like
because of getting ip address on instance.
However current exercise didn't log the return value.
In this commit, we add get_instance_ip function with
error hanlding support, and apply it on the execise.
Change-Id: I8e17ba68093faafe58a98eb780a032368eea38aa
1) Use the newer cell_type configuration option instead of overriding
the compute_api_class.
2) A nova-cells service is started for both the API cell (region) and
the compute cell (child). The screen names were both 'n-cell' which
caused both services to log to the same log file. The screen names have
been changed to n-cell-region and n-cell-child.
3) Security groups are not supported with cells. Multiple exercises are
patched to use the 'default' security group instead of creating a new
one. Additionally, if one uses the 'default' security group, do not try
to delete it, as one can never delete the default.
4) Disable the floating_ips and aggregates exercises when n-cell is
enabled, as they are not supported by cells.
5) Related to #4, disable the floating_ips tests within euca.sh
6) Update the README.md. No services need to be disabled, and one only
needs to enable the n-cell service.
Change-Id: I9782d1e3cda3c9dd3daefa15c043f5b06473cb87
In devstack, the exercises/euca.sh test the "VOLUME". it should always
check the volume which was just created. Because there may be volumes
left by the last failed euca.sh, then the variable VOLUME
VOLUME=`euca-describe-volumes | cut -f2`
will be assigned a list of volumes, which is not expected.
Fixes bug #1191424
Change-Id: Ie004c9cfeaef4a8a313866d21d45c7b41f1b2ba0
* exercises/euca.sh: The match filtering InvalidInstanceID.NotFound
is cleaned up to eliminate numerous leaning toothpicks, and now also
actually works. The previous version was incorporating literal
square brackets into the pattern where I think a character list
match may have been intended instead, but was not actually necessary
anyway.
Change-Id: I765a20000e7b6ba6deadce8cad3bbc9559fcdd0d
There are Quantum plugins that do not require the use of an agent.
This patch relaxes the constraint in quantum-adv-test.sh by adding
the ability to customize the logic that verifies whether the test
can run or not, depending on the Quantum plugin of your choice.
Fixes bug #1177904
Change-Id: I6e2c17f43d9e1475b2eb175cceb5107a83f9aa74
Fixes test for detecting when a volume has been successfully
attached to an instance to not just rely on the state being
in-use, but also be marked as "attached". The attachment
state will be displayed when https://review.openstack.org/#/c/27098/
goes through. The attachment state is not currently displayed
by euca-describe-volumes because of the extraneous data returned
by the API as per bug #1074901.
In the meantime the "attaching" status of the volume itself, rather
than the attachment state, suffices for the test to work properly, but in the long
term this will disappear as it is not a valid ec2 API state and
volumes will move straight to the in-use state.
Fixes bug #1170548
Change-Id: Id38f37e1a0efc991f60da35145f809d98b5f41cd