| Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ife6623aab20c4259af28d2b1374fc838b934d053
Partially-Implements: blueprint remove-docker-dir
|
|
Change-Id: I01220077d8d25db5f69802ad27e745d90826d69b
Closes-Bug: #1489664
|
|
Make the changes needed to support Ubuntu
Additionally, adjust the way supervisor is installed. Rather than
installing via pip, install via a package.
Change-Id: I1e7f538a180e4e35166d5afa8ba3f165b7e9f6d5
Partially-Implements: blueprint install-from-ubuntu
Closes-Bug: #1487715
|
|
Change-Id: Ie9b04c5e8dd4d2058172120d81c229ce747f5d27
Partially-Implements: blueprint remove-config-internal
|
|
Change-Id: I5db2eee21c3d5780d9be9f6527de3d7fb606a3e8
Partially-implements: blueprint remove-config-internal
|
|
Allows the user to configure neutron_plugin_agent value for Ansible.
Current allowed values are openvswitch and linuxbridge.
Implements: blueprint ansible-neutron-linuxbridge
Change-Id: I0572464a5459d2f9da09b6da22db16e240511f99
|
|
- Updated the required variables to be sorted so
that they are better visible one on each line
- Removed variable defaults from each service scripts
and added them to tools/genenv file which holds
all default values
Change-Id: Ia7b1b08ba3f963b46b81434ce84f476d56890a93
Closes-Bug: #1476494
Closes-Bug: #1467652
|
|
|
|
neutron-server was not properly using ml2_conf.ini
nova did not have ovs utils, and it had incorrect libvirt permissions
Change-Id: I43d2110d0b5fc1940d887dace95787e1ebbe142d
Partitially-Implements: blueprint ansible-service
|
|
Change-Id: Ie347964d42e7060c69047b1aeece1cf0ad311ae6
Partially-Implements: blueprint ansible-service
|
|
This issues presented as sudo requiring a TTY. We properly update the
sudoers config to remove the tty requirement
Change-Id: I7f31bccdc1774f8afd078267cf23704d95eda8b8
Closes-Bug: 1477351
|
|
Add initial Ansible support for Neutron
Change-Id: Idad011945bff914535d1ac0eb09cc9d3b0882fbe
Partially-Implements: blueprint ansible-service
|
|
Change-Id: I5fb6a35ade17ea89e306d3d00694b0f922a58e4a
Closes-Bug: #1475332
|
|
Partially Implements: Blueprint standard-start
Change-Id: Ic7334c1bed2a2b5055bd5c1e39b9f9ac32c30c6a
|
|
Due to a revert in the Docker code, thin neutron containers do not work
at this time. The neutron plugin agents do not need to exist in the same
container as the other agents however. This allows for using either
linuxbridge or openvswitch
The docker commit that did the revert:
https://github.com/docker/docker/commit/ff770d33cdee5ab4dc0bdeb06dcfea49aa72ab8e
Closes-Bug: 1469307
Change-Id: Idf79c31c74c34b93f5a9bac49730aca49bbdb861
|
|
Implements the neutron-openvswitch-agent plugin container.
Co-Authored-By: Sam Yaple <sam@yaple.net>
Partially Implements blueprint: openvswitch-container
Change-Id: Ie0fa318541e16d730b7007d3620c7873e898ed4a
|
|
Key difference here is the ip_wrapper.py file. This file and docker 1.7
allow for the network namespaces to be created in the host mount
namespace and propogated into the containers.
Co-Authored-By: Paul Bourke <paul.bourke@oracle.com>
Change-Id: I73bcd1c97bbaf742af883dbf281a8d76aff8aebf
|
|
The only files in the docker image directories that differ majorly between
distros are the Dockerfiles (e.g. different package manager mechanisms,
different repo sources, etc).
The supporting files such as the start.sh/check.sh and config files should
largely stay the same between base images.
This change moves these files up into a "common" directory, and symlinks them
in the same way that the build script is managed. This means when adding a new
base distro only new Dockerfiles need to be created. Also, if a distro does
happen to require a vastly different start.sh script for example, one can
choose to simply not symlink to the common and instead drop in a custom one.
Implements: blueprint refactor-base-image-layout
Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284
|