Enabling service 'dib' will install the following repos:
* diskimage-builder
* tripleo-image-elements
* os-collect-config
* os-refresh-config
* os-apply-config
These repos are already pre-fetched in devstack-gate.
This will facilitate gating on changes in these projects by building
a custom image then running the heat-slow job against that image.
diskimage_builder is pip installed from the current git checkout
if the dib service is enabled. This allows devstack gating on
diskimage-builder changes while also allowing diskimage-builder to
be installed from releases for other scenarios (for example, ironic).
Change-Id: Ia911cdee86f5b2e2ba1557e5aa8bf392b92ef555
These projects contain agents which can be installed on custom
images. Installing these repos will allow a future change to
build a custom image containing these projects. This will allow
gating on any changes in these projects by running heat-slow
on the custom image.
The corresponding devstack-gate change is
https://review.openstack.org/#/c/92055/
Change-Id: I7b1343c094f755f79ddeb1bac3ff4c0daa3fb70c
When creating the trove datastore, get the guest image id from glance.
The trove guest image gets uploaded along with all the other
images specified in $IMAGE_URLS. It is not necessary to upload
it again in init_trove.
Also: add xenapi case to stackrc for trove guest image
Closes-Bug: 1339818
Change-Id: I2973af27ab93182fcd674f874daba1036d767d52
This ensures that SERVICE_PROTOCOL is available to other consumers
of the devstack environment like grenade.
Change-Id: I702d7d239e50dd1446d55c076c7a7c57768486ff
Closes-Bug: 1335953
Cirros may be also built in other architectures other than
x86_64 (ex: ppc). This option should be broader,
so adding a new variable CIRROS_ARCH
Change-Id: I9fcd3f15e04bb581cf647ad49172c7d698e8e574
Some tests, such as test_minimum_basic_scenario, assume qcow and if
a qcow image does not exit, falls back to the euc image.
This change ensures these tests work in the stock XenServer environment.
Change-Id: I718f178f7e5e0fa4eebd17a49caf5254124092e3
This is the first step in supporting multiple Cinder backend types at
once. It initially converts the existing hard-coded multi-lvm support
to a new cinder_backends driver form. Eventually the cinder_plugins
will be converted to this form so they can be enabled more than just
one at a time using CINDER_ENABLED_BACKENDS.
The default configuration should be identical to the previous defaults,
including for both True and False values of CINDER_MULTI_LVM_BACKEND.
The existing cinder_plugins are expected to be removed when this is
complete. They should continue to work until they have been converted.
Add wait for c-api to ensure it is started before continuing.
Change-Id: I93b8ef32832269d730c76a6dc24ddb4f20c6d9df
Added a global toggle for enabling HTTPD + mod_wsgi for services
that default deploy to running under Apache. When the variable
``ENABLE_HTTPD_MOD_WSGI_SERVICES`` is set to ``True`` any service
that recommends deploying under HTTPD + mod_wsgi, will be run
under Apache.
If ``ENABLE_HTTPD_MOD_WSGI_SERVICES`` is set to ``False`` the
any service that is defaulted to running under HTTPD + mod_wsgi
will (if capable) be run in an alternate deployment strategy (e.g.
eventlet).
Updated Swift and Keystone to have individual toggles for deploying
under HTTPD + mod_wsgi. This is done to allow for gate to run on
the services under mod_wsgi where appropriate. Toggles are
``KEYSTONE_USE_MOD_WSGI`` and ``SWIFT_USE_MOD_WSGI`` and are both
defaulted to "False" (do not deploy under HTTPD + mod_wsgi).
Change-Id: Id3b121b8f1cde369d184b586e0d875bdbda34813
the previous addition to trove was done in a way that it was not
possible to discover from nodepool. This fixes our ability to do
that, especially with non-default on services.
Change-Id: I8ca682354e0d4e2eb9cf05f40c6dd783de1c6355
Add the keystonemiddleware repository to devstack to support testing
with tempest and stable branches.
Change-Id: Ib635465e6568d9cd51d6e432ec8b8633a27d19ce
The heat-slow job using the Fedora-20 image as L2 guest, the
currently used version is affected by the heartbleed issue and
the Mb-Bios bug issue observed with emulation.
This version of the Fedora cloud image uses the no_timer_check
kernel parameter, which solves the MP-Bios Bug issue.
The Image tested with ~3000 heat-slow job, without any issue.
Change-Id: I9ce9b7769c2d91e630b0362f2c2c6ac9066defbc
Closes-Bug: #1312199
Closes-Bug: #1297560
When the qume used with Linux image without
a para-virtualized timer, various timing issues can happen,
if the qemu process preempted in the wrong time, for example
at timer test.
The issues less like happens on low load, high core number
host system, but it can happen.
For soft qemu (TCG) generally recommended to explicitly disable the
timer check.
Pre-caching the Fedora `gate edition` image, which contains the
the no_timers_check option.
Related-Bug: #1297560
Partial-Bug: #1312199
Change-Id: Id5cd01a92a047b7859914e5bb017c15ee443b4d5
It would be useful for development, reviewing and testing to add
support for django_openstack_auth to devstack.
This change adds the integration tests to the openstack_auth
list of test: https://review.openstack.org/#/c/86528/
Change-Id: Ifbd336b83f6b2beb23996b599ec820232c13efdd
Closes-Bug: #1262121
Glance will reject images that it doesn't understand, and only certain drivers can
use qcow2 images. This means for systems without qcow2 support, devstack
will fail to run until this change is merged.
Change-Id: Ic92815f3d32880e987456c0428953dddaa81c94c
The default image used is cirros 0.3.0, which is out-dated and
does not support cloud-init for config drive. By upgrading to
0.3.2, we gain config drive support testing in our tempest runs.
Change-Id: Ibe7f70f1fb457d210b891b19ba3b5be94b2343f0
This is not supported and we missed a comment in stackrc that still
said otherwise. Fix the comment and abort in the sanity check section
if 'swift' is detected in ENABLED_SERVICES.
Change-Id: I78222d7ee2ea8a281962129d5bcf06c118469510
clean up the logic around producing a valid cfn image for heat
testing. If heat is enabled, add the f20 x86_64 imageurl to the
list of images that we support, and set that as the tempest
orchestration image.
The crux of this change is left commented out for now because we
need a two phase update of nodepool content before we can move
away from the old image (otherwise fedora mirrors will kill us
with bad downloads).
Change-Id: I1da9f259a3267b1bd27e9899755204c8fff41153
Get rid of lib/baremetal usage so that it can be simply
deleted when that time comes:
Copy upload_baremetal_deploy function to lib/ironic;
Rename it to upload_baremetal_ironic_deploy;
Remove any $BM_* variables references from lib/ironic;
Rename $BM_IMAGE_BUILD_* environment variables to $DIB_*;
Improve logic around deploy k&r building;
Add check for $OFFLINE mode;
Change-Id: I4302b32328df9156bf8738773a127db914e8edde
Cirros 0.3.2 is fixing the host name setting issue, which
is required for turning on the tempest instance validation tests.
Change-Id: I1b87740ab02c4eb0a8df653a35e1f85d40abda51
Related-Bug: #1132686
The debian image that defaults to being using with vmware is huge,
and it turns out it's not actually used in VMWare ci so we don't
really know if it's working. Instead use the vmdk that is used
in VMWare ci, which we know will boot, as we get results everyday.
Change-Id: I014746af293852525e2bd128c4d19f5889ecd55d
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
The bm_poseur git repository link has been broken
for over 11 months. The virtualized/fake baremetal
environment is not working and has not worked in a
long time. Now, on the tail of enabling 'enable -o errexit',
this functionality now has a hard break.
Change-Id: I3cbd8db58c422bc5273d2433278aaa5e449ecfd9
Closes-Bug: 1285954
During my CI testing of each devstack change I can often see git get
itself stuck and hang indefinitely. I'm not sure if it's transient
network issues, or issues at the remote end (seen with both github.com
and git.openstack.org) but it hits fairly frequently. Retrying the
command usually gets it going again. Searching for "git hanging" and
similar shows its not entirely uncommon...
This adds a watchdog timeout for remote git operations based on a new
environment variable GIT_TIMEOUT. It will retry 3 times before giving
up. The wrapper is applied to the main remote git calls.
Change-Id: I5b0114ca26b7ac2f25993264f761cba9ec8c09e1
