This adds functional tests to tox, along with a number of prerequisite
steps. Since this is primarily a bash project, pbr usage has been avoided.
Tests are to be written in python and put in the tests directory.
Running tox -e setupenv will execute a setup script
(tests/setup_docker.sh) to ensure the running instance of docker meets
the minimum version requirement.
Running tox -e images will execute the image building script
(tools/build-all-docker-images) and will parse the resulting output to report
failures.
Running tox -e startenv will generate the environment file, run
"tools/kolla start", and run first time initialization (eventually).
Running tox -e functional is for actually testing the deployed OpenStack
environment via a series of tests utilizing the client APIs.
Change-Id: Iff6dfdca43f0c44d471e7540a7836e56a0de4507
Change the sed seperator to accept a namespace with a private registry
and add an option to specify the registry. Below is an example for a
registry located at 192.168.0.10:5000.
$ ./build-all-docker-images -r 192.168.0.10:5000
The final image name would be something like this:
'192.168.0.10:5000/kollaglue/centos-rdo-base'
All build, push, and pull commands will still function the same.
Change-Id: Ic0ff96bb8119ddfab15b99e9f1e21cfe8d321dab
Previously, the Heat demo suffered from the following limitations:
1. The number of Nova instances to spawn and the image flavor were
hard coded in the Heat template.
2. No outputs existed. This required users to run nova-list to
obtain the IP's of VMs.
3. No documentation existed.
This patch addresses the above limitations.
Change-Id: I495aa9c73a91200c01cecc1719ee5532c1f6c9cb
Previously, vnc was not completely working properly because
nova.conf config flags were not properly implemented in t he correct
containers.
This patch moves the nova.conf config flags for vnc to the proper
containers. Additionally, the patch modifies the proxy client ip
param to be consistent with the param within nova.conf and adds
all the novnc params to docs.
Change-Id: I1944baca64ccd113bbca582784b08f90dc0eff69
The --router:external option is a boolean flag that doesn't take a value
(neutron client version 2.5.0). Passing True results in the following
error:
Invalid values_specs True
This patch simply removes the 'True' value.
Change-Id: If4b5305f37d50c14c767393eb21223b0e0b59494
Make a Magnum demonstration that creates a baymodel and bay. Just
run demos/magnum/launch to make it work. This depends on Neutron.
Borrow the v1beta3 redis example from the examples repository in
Kubernetes.
Change-Id: I448a5890bfe0c1675914ae7dbd02fad03f4b1eeb
Having the dasboard in /dashboard doesn't feel right, especially
since there is no automatic redirect when people browse to the ip or
hostname. Which would be a natural first try. Moving to / now to make
the process behave in a simpler fashion.
Because of a packaging error the js/css wouldn't load properly, next
to that there is an issue with a supposed missing 'manage.py
compress' run. This is handled through Kolla now as well (for the
time being).
There is another supposed bug in packaging that makes webfont.ttf
return a 404. This is because of a missing alias for /static stuff,
and with moving the whole thing to / this gets adressed as well.
Change-Id: I64cd7c9effad6cf9ec7c6a41f34e1184640c8adc
pkill -9 docker was killing setup_docker.sh execution, so add -x flag.
Added check for root permissions and host type.
Added executing user to docker group.
Change-Id: I82cfad64fa737666d888e2ab9350c8d42e2150bf
Previously these services would not start because the start
script requires the associated log file to exist. The default
settings for these 2 log files are blank causing the failure.
Since the log files are not required for the services to start,
this patch removes the parameter requirement from both start
scripts.
Change-Id: I84d3d128728075e52282b49d9df229917a34a7b5
Previously, the keystone compose yml was referencing juno instead
of kilo when all other services are using kilo. This patch upates
the yml to use the keystone image with the kilo tag.
Change-Id: Ib4f551ad303bd44f0a5c45fc9d5f7d53f376caf7
Previously cleanup-containers suffered from the following
limitations:
1. The docker rm command would fail if all the containers were not
stopped.
2. The script would throw an error if no containers existed.
3. Artifacts such as veths, bridges, etc.. would remain on the host
after containers were removed. These artifacts should be removed
if the containers are removed.
Change-Id: I5eadb23fec9e34125a32f6c3e39c241d97932910
In Kilo Nova deprecated proxying options in the DEFAULT group. Instead
they were moved to the "neutron" group. This resulted in the metadata
service not serving up metadata.
See this bug for more information:
https://bugzilla.redhat.com/show_bug.cgi?id=1217999
Change-Id: I4f7eac0100d31c5329f8d1857f6d7da1bb6784da
Neutron was loading a bunch of modules that are not currently
supported in Kolla. Remove them as they were causing problems
loading Neutron.
Partially-Implements: blueprint port-kilo
Change-Id: If53071bbb0a22aa05219b9e99ca6d693f96db4ce
Both of these paths were missing from the configuration
but they appear necessary for Kilo. I'm not clear on why
it worked ok in Juno, perhaps different defaults.
Change-Id: I8b7c375627ada860356f9b9fcc205751083b804c
Partially-Implements: blueprint port-klo
The default dnsmasq configuration file doesn't operate with the Kilo
agents in /etc/neutron when used with the --config-dir option. Instead move
it to a subdirectory.
Change-Id: Iab8a54e879f8e630ba38205750ca9670e82834df
Partially-Implements: blueprint port-kilo
policy.json comes from the openstack-neutron package and is required
for the agents to run. So install it. fwaas_driver.ini has been deleted
in master and in the kilo branch, but the agents won't run without the
file present. So copy one from the Juno release.
fwaas_driver.ini is probably not actually required, but there is a
configuration problem somewhere in our Neutron code base. We are out
of time for the Kilo branch, so this short term workaround should be fine.
Change-Id: I154599925308765349634b1a53e598599fc20ec1
Partially-Implements: blueprint port-kilo
Glance has two undefined dependencies. Without installing these
dependencies out of band, glance will not operate.
Change-Id: I096881467d8e0022d58e6c6f745e610d9332dd82
Partially-Implements: blueprint port-kilo
In Kilo, nova no longer reads the config files automatically. They must
be specified in the command line to run the nova-* tools.
Change-Id: Ifbdf4fd3f952f7bb65e9937b46cf9b96e262c3b0
Paritally-Impleents: blueprint port-kilo
All VNC-specific configuration bits are moved from nova-api-base to
nova-compute and the new nova-novncproxy and nova-consoleauth
containers. The compose specification has been updated to reflect this.
A future patch will make the desired backend configurable (spice/vnc).
Change-Id: I8b64abf125fd1ecd7d3463515e3717dd9bd60420
Blueprint: novnc-container
Change nova networking config to work properly with Neutron Juno and later.
Partially-implements: blueprint port-kilo
Change-Id: I18c324c34b4c3af8526d32b3e42f426ec519750b
This represents making build-docker-images --release build
with the icehouse tag and causes docker-compsoe to pull from
the icehouse tag.
Partially-implements: blueprint port-kilo
Change-Id: I66b2c39abc55c0f47152dd90e696fc46b9c58f50
Zaqar was introduced in Juno, so remove it prior to branching
icehouse, then add it back in after branching icehouse.
Partially-implements: port-kilo
Change-Id: Icce95b4d404e6d8238206716e74f6826bc860860
This sets up nova networking properly to work with Neutron in the Icehouse
release.
Partially-implements: blueprint port-kilo
Change-Id: I0d37411c61d0d705d1ddf39c25c6610ea04f56f1
Add Heat-api-cfn for wait conditions
Magnum needs wait conditions in order to operate properly. heat-api-cfn
is where wait conditions connect.
Change-Id: I56742dd96e4607dc0042d0cef4e18c922f9ed736
Implements: blueprint container-heat-api-cfn
Rather then upgrading to a specific version of OpenStack, just
upgrade to Head. This works for both juno and kilo.
Change-Id: I6305218eabd7de0878e24c8fdae968ac6d612175
Partially-implements: blueprint port-kilo