| Age | Commit message (Collapse) | Author | Files | Lines |
|
Remove the docker directory (yay) and old build tools.
This will result in an f21 failing gate - however, I have a patch
submission to remove that gate from our project configuration.
Change-Id: I3c461cedb6906422c8076f60c470e773d6cdcf33
Partially-Implements: blueprint remove-docker-dir
|
|
Change-Id: Ife6623aab20c4259af28d2b1374fc838b934d053
Partially-Implements: blueprint remove-docker-dir
|
|
RDO doesn't keep their RPM dependencies up to date with latest
neutron changes to requirements.txt, so we have to pip install
the package.
Change-Id: Ic49a4dd3b85e9daf60c87b245b9784818fcb3bb2
Closes-Bug: #1486241
|
|
There is no such package. It is called python-neutronclient.
Since we know deployments work well without this dependency,
might as well just remove the error since it pops up in the
gating.
Change-Id: Ic0daf85201cf283ee0560a9905e5079e421efbc4
Partially-Implements: blueprint gate-source-builds
|
|
oslo.messaging is breaking neutron-server or vice-versa. Either way
pinning oslo.messaging to the current stable fixes the issue. When
2.2.1 is stable or the delorean repos fix the issue we can remove the
pinning
Change-Id: I353aba463d0b1e11f4b58e5edd5241a636701172
Closes-Bug: #1483667
|
|
Change-Id: Id4e2f081396aaf54030b6f8887e887c8a7b264c3
Partially-Implements: blueprint remove-config-internal
|
|
Change-Id: I5db2eee21c3d5780d9be9f6527de3d7fb606a3e8
Partially-implements: blueprint remove-config-internal
|
|
The neutron-agents l3 agent requires access to the OVS database via
access to /run. It also needs to have ovs-vsctl binary available in
the container.
Change-Id: I903537b570cd60c9bb1088e9408a5f6ea4988d8f
Closes-Bug: #1477376
|
|
Change-Id: I5fb6a35ade17ea89e306d3d00694b0f922a58e4a
Closes-Bug: #1475332
|
|
|
|
The "hacking" package used in most OpenStack repos pulls in
additional pep8 rules. This commit should fix all of them
other than a hand full in the build.py file which will
be fixed in a separate commit
Change-Id: I40a0a30d338592ad64123e3da5523b9ad95a7a9c
Partially-Implements: blueprint enable-flake8
|
|
Otherwise it complains about missing the ebtables binary.
Change-Id: I6bc0c0b1bacdf4a75929424ad9f11f6982e62c87
Closes-bug: #1473500
|
|
Change-Id: I0de312a587ecd83158da4c7e05ca6495c7a981a8
Partially-Implements: blueprint enable-flake8
|
|
Add missing oslo dependency.
Closes-bug: #1469891
Change-Id: Ia7b0a5bc0d59f561a1cb6cdb0a50478cad9246d4
|
|
Partially Implements: Blueprint standard-start
Change-Id: Ic7334c1bed2a2b5055bd5c1e39b9f9ac32c30c6a
|
|
Missing KOLLA_TAG variable
Change-Id: Ic97841cb9d27a9fc5cb7967f3da1b2f016988d20
Closes-bug: #1469332
|
|
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
|
|
|
|
Affecting one ore more neutron containers
Change-Id: I2788c1921eb82ad0d0524fc99a436c5fe9ff50d8
Closes-bug: #1468863
|
|
Implements the neutron-openvswitch-agent plugin container.
Co-Authored-By: Sam Yaple <sam@yaple.net>
Partially Implements blueprint: openvswitch-container
Change-Id: Ie0fa318541e16d730b7007d3620c7873e898ed4a
|
|
An ordering problem with the Dockerfile resultled in this
container and all thin containers failing to build. This patch
Fixes that problem.
Change-Id: I4a7ba1554bdcba3f2147eb4eaa628d1cc19f84fd
Co-Authored-By: Jeff Peeler <jpeeler@redhat.com>
Closes-Bug: #1468486
|
|
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
|
|
Change-Id: I49e9e187feb48cbebe299a350749be7ffd3c7450
Partially-Implements: blueprint bashate-gate
|
|
Change-Id: I91ede62a58cd224b7b93f4652174c09c387386d6
Partially-Implements: blueprint bashate gate
|
|
Change-Id: Ie3fdcf5d3e1cda3b85a6532e462ad78e98e1a378
Partially-Implements: blueprint bashate-gate
|
|
Change-Id: Ie95c44b92e3d0af56916f0e335afc8fd461b2790
Partially-Implements: blueprint bashate-gate
|
|
Change-Id: I0ecd173e49fcb9bca9702d506e1af785d3a4983a
Partially-Implements: blueprint bashate-gate
|
|
Change-Id: I4cfdce7ae4d2727d543aef46d0cd63a96a48a9cb
Partially-Implements: blueprint bashate-gate
|
|
As a restructure, nothing is changed from the original behaviour and
naming despite the file structure changing. The symlinks to build had
to be updated generating lots of "deleted" and "new_file".
The new structure is:
docker/${base_distro}/${type}/${container}
base_distro == centos, ubuntu, fedora, etc
type == source, binary, rdo
type rdo is a symlink to binary for backwards compatibility
Two new flags are added to the build-all script to support the ability
to support different base distros and a flag to support binary or source
containers.
There are several added folders that are empty to hold the directory
structure for future containers of these types.
To use a prefix other than centos-rdo- you can set PREFIX in the toplevel
directory .buildconf file
Change-Id: Ifc7bac0d827470f506c8b5c004a833da9ce13b90
|