tempest is already defined in stackrc as default.
Without this definition in local.conf,
tempest is installed successfully.
If it still needs "enable_service tempest" definition
on local.conf,
devstack itself has some problem.
In my environment, tempest installation works
without this definition on local.conf.
Change-Id: I25cda0142538d21bb9656b471e65ca5b018e8378
By default, most Openstack services are bound to 0.0.0.0
and service endpoints are registered as IPv4 addresses.
With this change we introduce two new variables to control
this behavior:
SERVICE_IP_VERSION - can either be "4" or "6".
When set to "4" (default if not set) devstack will operate
as today - most services will open listen sockets on 0.0.0.0
and service endpoints will be registered using HOST_IP as the
address.
When set to "6" devstack services will open listen sockets on ::
and service endpoints will be registered using HOST_IPV6 as the
address.
There is no support for "4+6", more work is required for that.
HOST_IPV6 - if SERVICE_IP_VERSION=6 this must be an IPv6
address configured on the system.
Some existing services, like the Openvswitch agent, will continue
to use IPv4 addresses for things like tunnel endpoints. This is
a current restriction in the code and can be updated at a later
time. This change is just a first step to supporting IPv6-only
control and data planes in devstack.
This change is also partly based on two previous patches,
https://review.openstack.org/#/c/140519/ and
https://review.openstack.org/#/c/176898/
Change-Id: I5c0b775490ce54ab104fd5e89b20fb700212ae74
Co-Authored-By: Sean Collins <sean@coreitpro.com>
Co-Authored-By: Baodong Li <baoli@cisco.com>
Co-Authored-By: Sridhar Gaddam <sridhar.gaddam@enovance.com>
Co-Authored-By: Adam Kacmarsky <adam.kacmarsky@hp.com>
Co-Authored-By: Jeremy Alvis <jeremy.alvis@hp.com>
Currently if you `cat` the file, the bash prompt will be at a weird
position. And if you programmaticaly add a new line to this file,
the line will be, in fact, appended to the previous line.
Change-Id: I19ba018d9a934f8fdc07cc9bec50a0105f2710f9
I expect the sample local.conf file to contain all the required
variables. However, after copying samples/local.conf, the stack.sh
script still asks for SERVICE_TOKEN.
This commit adds the SERVICE_TOKEN definition to local.conf so that a
new user can just copy samples/local.conf, edit it, and have a running
stack.sh without the mild annoyance of having more variables to set.
Change-Id: Ifb163c7f67c80037d8b10458f2df458a20da4667
The SWIFT_DATA_DIR default value stated in the last comment of
samples/localrc has been updated to match actual SWIFT_DATA_DIR
default value ($DEST/data/swift instead of $DEST/swift/data).
Addresses Bug: #1238665
Change-Id: I2510f72eb3eda467799202b356abb606930f4d94
The enable_service() and disable_service() functions in
https://review.openstack.org/9407 require the functions
file be sourced before stackrc.
* exercise.sh
* samples/local.sh (this will require manual addition to the user's
local.sh if they based it on the sample)
* tools/build_bm.sh
Change-Id: I1bed687867e870bef5748289d712376435a776af
Run $TOP_DIR/local.sh at the end of stack.sh if it exists and is executable.
This allows the user to automatically perform local actions on every re-stack,
such as creating custom flavors or specific tenants/users. Like localrc, this
file is not distributed with DevStack so user modifications will be undisturbed.
Add local.sh to .gitignore
Examples of local.sh and localrc are in the samples/ directory.
Change-Id: I0be6b4d80ce084981cac8a3a8f1dc9bc8c3bbd4e