tox.ini started failing with Tox4 which had some
incompatible changes.
Fixing tox.ini for tox4 changes.
The latest version of docker broke kuryr-libnetwork since
it removes external k/v support. We have to hardcode
to an older version of docker to workaround.
The CI failed to delete subnetpool since the subnet haven't
been deleted yet. This commit also fixed it.
Depends-On: https://review.opendev.org/c/openstack/devstack-plugin-container/+/875113
Change-Id: Id48bb7d92f2f5d9d08b44acf651dbba3bf2e924e
This reverts commit 9cc51ae2c8.
Reason for revert: it seems distutils has fixed the path so we revert our fix
Change-Id: Ibbe1bdc19dceb1e6fbbf467bfd44aa18f0a7cb78
The python-neutronclient is deprecated and under maintain.
All CLI users should switch to openstackclient instead.
Change-Id: I87e0b4501c198d7cccd5350424a01c6afb3a2836
The variable $TARGET_BRANCH will be set by devstack. It will point
to the right branch that the devstack is based on. For example,
if the devstack is on a stable branch, TARGET_BRANCH will point to
that stable branch. Using this variable will save us the manual
effort to update the branch whenever we cut a release.
Change-Id: I45f93aa328c4e166d131d18c579651e4e96c3254
When users unstack and clean on devstack, the old config files
should be removed to avoid potential issues. As a result, users
will get a fresh new install on the next ./stack.sh
Change-Id: Ifd89dd7528d63a5e92dc9f02e939810c8fa2a247
The endpoints 'network_driver_program_external_connectivity'
and 'network_driver_revoke_external_connectivity' will dynamically
create security group and security group rules to open the ports
exposed by the docker container. However, such processing invokes
too much neutron API calls thus significantly slowing down the
container start/stop. However, such processing is not mandatory
because users can manually configure the SGs to achieve the
equivalent.
This patch make the processing of exposed ports configurable.
As a result, it can be disabled if users want a better performance.
Change-Id: I6d6d176512e6b30bb7372408aec1a7bac12335ab
If the etcd cluster is installed via devstack, it will refuse
connection from localhost. Need to use the IP address instead.
Change-Id: I6e6a0c0d8476a229ca66a528519f8759b50e6321
In before, devstack doesn't use a setuptool-generated script to run
kuryr server. The static script it uses doesn't work in python3
devstack because it still point to the python2 executable. This
commit fixed this issue.
Change-Id: Ib222bf2e84f4b06b0dc3981fc3554510658d4ef0
Devstack provides a variable for etcd port for now [1]. It is better
to use this variable instead of hard-coding the port.
[1] https://review.openstack.org/#/c/467714/
Change-Id: I0034d6e30dcf605e91d5609f2448aa1264a69c4f
ETCD is now a base service [1], which means it will be installed by
default in devstack. We don't need to re-install it in our devstack
plugin.
[1] https://review.openstack.org/#/c/445432/
Change-Id: Id8be0adb7b5d9c736b8acc680e9e72f82a225dec
This patch add a script to create v2plugin rootfs.
1. use local unix socket for v2plugin
2. add config.json for v2plugin
3. Add scripts to build v2plugin rootfs
4. Update devstack to use v2plugin
Change-Id: I91d352a963840f33d1d2f9cea17ab6ac777d22bc
Related-Bug: #1668486
Partially-Implements: BP docker-v2plugin
If both Fuxi and Kuryr-libnetwork are enabled in devstack, the script
will fail since etcd-server was spawned twice. This commit added a
check for existing etcd process and spawn one if not existed.
Closes-Bug: #1683852
Change-Id: Iecef71df1c0b58db62c20462932ba179c91a1695
In before, we checked docker installation by:
$ rpm -q docker-engine
However, this doesn't work for all cases in fedora 24.
* If docker was installed by "sudo dnf install docker-engine", the
package will be named as "docker". Therefore, it should be checked
by "rpm -q docker".
* If docker was installed by devstack (by using
https://get.docker.com/), the package will be named as
"docker-engine". Therefore, it should be checked by
"rpm -q docker-engine".
This commit added check for "docker" as well.
Closes-Bug: #1647459
Change-Id: If89d8b62ffa542f0491f43d42a119741882eb3cd
neutron qos feature will be used in follow up patches, so enable
this feature in vagrant by default. Neutron qos feature also need
to be enable in CI job in project-config later.
Change-Id: I8d9123c01ab187b34474ff38dd85ed567e658d92
Partially-implements: bp kuryr-libnetwork-qos
Currently, devstack will install kuryr-lib 0.1.0 for
kuryr-libnetwork. But we still need to check if kuryr-libnetwork
can work with kuryr-lib master code. This patch introduce
LIBS_FROM_GIT to let devstack install latest kuryr-lib code.
And let kuryr-libnetwork use kuryr-lib master code by default
in vagrant.
Change-Id: Id05dab5bd6a4aa2efe5f6991e9fd5fc38c1cf91b
Partially-implements: bp cross-project-ci
Closes-bug: #1630971
The last devstack patch introduced usage of the service project and a
Kuryr user, however, it was with the services role, while Kuryr needs
the 'admin' role.
Closes-bug: #1625482
Change-Id: If517f77c7aec3fad81af101ccc174167f16ae37b
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
In order to have Docker easily usable for the fullstack testing, we made
it listen to the port 2375. This had an unintended and very bothering
side effect in forcing cli usage to have to pass '-H :2375' to every
signle docker command.
It was driving me crazy, so this should make both the normal cli usage
and the fullstack usage work without hassle.
Change-Id: I0d6162937e018664516de406197ca0a464b4ee71
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
In order to integrate with Kolla and to support newer deployments that
have only keystonev3 enabled, we leverage keystoneauth1.
I want to thank Fawad for taking a stab at fixing this earlier.
Depends-On: Ia56b22963f5a2130a722403a14ee1a233ac6cff9
Closes-bug: #1622302
Change-Id: Id57420ef94ea9bd71b6581c4cdc24697465a3445
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
Co-authored-by: Liping Mao <limao@cisco.com>
With the advent of this tool. Generating the config for local usage and
packaging will be much simpler.
Closes-bug: #1619252
Change-Id: I95f8f0ec76fb8a75153f6dac12c6ec1d2f485e8b
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
When we install kuryr-libnetwork, there may be some exception
in install etcd data store, like network timeout, IO error.
Then we may met file exists error reinstall.
We can clean up the etcd directory in unstack script.
Change-Id: I77dd701dcda7866b2d09dd9b334a64df21f5762c
Closes-Bug: #1611187
Commit c96032ecc1 changed the devstack
plugin to avoid reinstalling docker if the service was running.
However, there are a few meaningful cases where the service is not
running but the package is however installed and the user does not
want devstack to reinstall it.
This patch uses the distro package manager to find whether
docker-engine is insstalled already, rather than systemd or init.d.
The docker installation script will take care of cases where docker
was manually installed from binaries.
Change-Id: I6f66fdd3c35739486a6453b484eab81dfb4a9545
Docker 1.11.0 fails to activate libnetwork plugins specified with .json files.
Using .spec files still works. Adding a .spec file and configuring devstack to
work around the bug.
Change-Id: I041a5e9a526c2e63c92f3d01411afda8b7beb601
Closes-Bug: #1572369
Signed-off-by: Frederick F. Kautz IV <fkautz@redhat.com>