openstack/devstack - devstack - OpenDev: Free Software Needs Free Tools

clean.sh picks the parent of LOGFILE and wipes it clean! So if you
set it to a log file in the users root directory, you lose everything
We should delete just the LOGFILE and cleanup LOGDIR and SCREEN_LOGDIR if
they are explicitly set.
Change-Id: I45745427dcaed3dcf0b78cc9ed680833d9d555e8

When the n-cell service is enabled, we create networks in both the
API cell and the child cell. Recent changes to tempest have tests
querying networks from the API and passing them for a server create.
In order for this to work in cells, the UUIDs for the network in
the API cell and the child cell must match, else the network won't
be found in the child.
This change adds the --uuid option to the nova-manage network create
command for cells only.
Related-Bug: #1441931
Depends-On: Ib29e632b09905f557a7a6910d58207ed91cdc047
Change-Id: Ib5933b1405c0761ff727e04cda0c502a826c8eaf

the sleep 3 in screen_it was added to make devstack pass in the gate
with exceptionally slow test cloud nodes. In the gate we now bypass
the screen path entirely. However the sleep 3 remains and can add a
couple minutes delay into local development runs.
We're not sure yet how low this can safely be tuned, so step 1 is to
make it configurable, then get devstack team members to try various
options to see what works.
Change-Id: I0e6476176fc8589efc4e40e78c2231f704d14e45

The install_infra() call needs to be done earlier since
pip_install_gr() depends on it. Also the fact that python module names
are supposed to be lower case but some use camel case is a problem
(for example with XenAPI).
Change-Id: I7012d77134fa0d9c746d87e837934e7dcb337e5c
Closes-Bug: #1441820 

This creates a new pip_install_gr that installs from global
requirements allowed versions. Now that stable branches are getting
capped all of devstack needs to be fixed to do things like this.
Change-Id: I8fd0ef2bfc544ca2576fab09d3018f760b8848fe

The qemu-system package, and not qemu-kvm, should be installed on either
trusty- or utopic-based ARMv8 (aarch64) Ubuntu releases. Additionally,
libguestfs is not available so that is not installed.
No changes are required for vivid.
Change-Id: Id9dc1fc465bd7acab17c991c292fb531016758ad
Signed-off-by: Andrew McDermott <andrew.mcdermott@linaro.org>

there was a missing -or which meant we weren't running this on most of
the files in the repository.
Change-Id: If926afc8f12f6beb80d7a9af7c787b3dcc360a89

One of the earlier patchset while updating stackrc
missed on adding "+=" while adding multiple services.
Closes-Bug: #1439983
Change-Id: I74f788e15b7da05a93fc8d99c562e51386b65053

Setup of OVS may fail, if ports that are added,
are already exist. Add "--may-exist" directive to OVS
add-port command to prevent this behaviour.
Change-Id: I2280be9a63a4a6fbc747b5e32b602697b555ffa8
Closes-Bug: #1394162 

Now that tempest is querying for a network before making server create
calls the fixed network needs to be known by the API cell. Server
creates should work for networks defined in both databases, but defining
a new network via the API will continue to not work.
Change-Id: I32461add0d20940a55385c8b34cd493e2561615e

In current implemetation these two urls are defined from Nova
definitions. And urls point to nova. But standalone EC2API
project has another urls that are defined in keystone catalog
in plugin setup.
I suggest to use urls from catalog to be able to test
stackforge/ec2-api by current tempest.
Change-Id: Ibec8c36a8c2fc7ea3d8fab57819adae5f7378045

euca-bundle-image can be run only if euca2ools is installed.
but now it doesn't installed and several tests for EC2 doesn't run.
Change-Id: Ib3824052d5f4155d3cb5c0ef6fe334d44de5153c

This commit ensures we also set the qcow image location in the
tempest config when we update qcow version. The tempest config has
a default value for img_file (which is incorrect) but before we can
remove the defaults in tempest we need to ensure devstack is using
it properly first. The only reason the tests weren't failing here is
because tempest falls back to using uec images (which devstack was
correctly setting config for) if qcow isn't found. The img_dir was
also hardcoded assuming a uec image, however if qcow is intended to be
used you'll need to be able to override that, which is added as
part of this commit.
Change-Id: I05af346b3c9be9560dc8846dd1f437cfbb2d5005

This patch changes the two config options required for Ironic to
successfully test cleaning in devstack.
First, we disable erase_devices clean step. Erase devices in VMs
ends up running shred on the drives for the agent driver, which is
incredibly slow and completely unneeded in devstack.
Additionally, we allow Ironic more time to complete the unprovision
after the nova instance is deleted. This time is spend in the CLEANING
state to clean up the node.
This is related to the Ironic blueprint "implement-cleaning-states".
Change-Id: I77081165a80491da3e66d8a4554b6d71fc3d9353

2 files had execute bits set on them, fix as a cleanup. These files
should not be directly executed.
Change-Id: Ic0fdb85d77a3b47ef777524faf4fcdb0d8cedece

This changes the default service list in devstack to minimize what is
running out of the box, so that it's likelihood of working in a 4G vm
is much higher.
This removes heat from the default enabled service list.
It drops the ec2 only needed n-obj and n-crt services.
It drops all the alternative consoles (xvnc, consoleauth). novnc is
fine for libvirt which is the default.
It adds dstat, because that's turned out to be so useful in debugging
things.
Change-Id: I84457260dff6f42a5c6ebcc2c60fb6e01aec9567

Enabling it by default because:
 - This allows you to get the relevant logs right away when something
 in the libvirt code path fails, without having to submit another
 change and keep doing a 'recheck' to re-run the CI check/gate jobs
 until you hit the bug.
 - The libvirt log filters specified in the function
 'configure_libvirt' are much more _selective_ and not a catch-all
 debug option where you end up with the unhelpful situation of having
 to find a "specific piece of hay in a haystack"[1].
FWIW, I always have it enabled in local test environments, and I don't
see the resulting libvirtd.log growing beyond a couple of MB for
three-four days of usage.
[1] http://lists.openstack.org/pipermail/openstack-dev/2014-January/024414.html
Change-Id: I5e0b35446075b419fe473e1db8d0bfedd7009741

We are trying to get a working 64bit qemu cpu model in the gate for nova
live migration testing. It appears that we need to make this change
prior to nova starting.
Make the change in configure_libvirt() to handle this along with the
other libvirt config updates. This allows us to restart the libvirt
service once. This function calls a python tool which parses and updates
the XML if necessary.
Change-Id: I00667713bfba67ab8cedbcb1660ff94d4f4bcc07

A lot of libvirt interactions with QEMU are via the QEMU monitor
console, which allows you to either query or modify the state of a
virtual machine. Spefici examples include: querying the status of live
block operations, live snapshot operations, live migration, etc.
Enabling the 'qemu_monitor' log filter allows us to capture precisely
what commands libvirt is sending to QEMU.
Note that the log level was intentionally set to '1' (i.e. debug) for
this specific filter, because (a) it's not extremely verbose, (b) when
something breaks, it's helpful to have the exact sequence of
interactions between libvirt and QEMU.
Change-Id: Iba95b6bd7c9f197c8d48c7d978f538e50d4e31fa

There are a couple of targets in here that some might find useful in
doing DevStack testing in multiple remote VMs.
There are some of the usual boring targets too, like stack and unstack,
that do exactly what you would expect.
Change-Id: I7974cac4cc527bacf6f183ac1f344428b05f2fdc

This previously defatuled to 'private' and aligned with devstack's
defaults but it has since been updated to 'None'. This sets the config
value according to devstack's.
Change-Id: I3f480d5480521a93992bedfe602eb20a4999263d
Closes-bug: #1438415 

This is needed otherwise we fall back to the nbd code path which is
super hacky. This shouldn't have been deleted for the venv path.
Change-Id: If5cb6cb4944bd0ed3548d53c98443b76725d1c0c

PyEClib was introduced recently to swift-master. It tries
to build liberasurecode which requires the `make` binary.
Change-Id: I8acfed4f7b46a29eac36f6acbe1d66e7fff800db