1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links
Change-Id: If0b076ecd9b6c82186e8d6e504da3aa9d11a7dd3
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
When use kuryr-libnetwork container with multi-thread and neutron
service under https, uwsgi will has ssl error.
Change-Id: I897d84742570dcc2d4daba1ea40882814a38679f
Related-Bug: #1675301
Openstack dropped support for Ubuntu-trusty,
changed to xenial to avoid conflicts with devstack
Change-Id: I9e192b47d7f30cb412a4177947225c39db749073
Closes-bug: #1673704
OVN native DHCP has landed, fix the example in the README.md file indicating how
to use OVN so it correctly uses OVN native DHCP with devstack.
Change-Id: If571ba9878d2b893f3e85f3b6b763d5b797bd598
Signed-off-by: Kyle Mestery <mestery@mestery.com>
Currently in devstack README.md path to vagrant file is wrong.
This patch fixes it.
Change-Id: I71bf1c6a0808113afbfa1ebd11f57200e21e3a72
Closes-bug: #1627489
Up until this patch, the Docker container for the Kuryr libnetwork
daemon was part of contrib and was being built by checking out the
latest master from github. That is not very helpful when developers
want to build the container to run their latest changes.
With this change, we move the Docker building to the root of the repo so
that it can use the current state of the repo to build and update the
README.rst to contain the information relative to building and using the
container.
Change-Id: Ie9032d62c73d873a29cabe84c64a19df13fdb749
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
Explicitly set type for integer environment variables:
* VAGRANT_KURYR_VM_MEMORY
* VAGRANT_KURYR_VM_CPUS
Despite there is a fix in the Vagrant git repo for that
issue, still exist systems where the issue is not fixed.
On those systems trying to limit the VM memory one will
get «no implicit conversion of String into Integer».
Thus convert the environment variables to int explicitly.
Change-Id: I80a39e0b072159b601dd8cadf839e596ea64e644
Bug-Url: https://github.com/vagrant-libvirt/vagrant-libvirt/issues/525
Bug-Url: https://github.com/vagrant-libvirt/vagrant-libvirt/pull/526
When I create two containers and one tiny vm, I find the
neutron-ovs-agent is crash due to lack of memory. I know
we can add memory by modify VAGRANT_KURYR_VM_MEMORY. But
I think create two containers and one tiny vm is very
basic requirement when test kuryr, the default ram should
support this.
Change-Id: I6758ffb104d8ed91135ec58b0c2b794e7fce10c9
Closes-Bug: #1582716
Bug description:
vagrant install readme notes vagrant up should take around 10min;
mine took 38min
Change-Id: Idc5312f30678850aaa25ac55b46e47a344f77b15
Closes-bug: #1577545
This adds the setting of DOCKER_HOST into the kuryr_rc file,
and moves the sourcing of said file into .bash_profile upon
user login. With this change, you can now login to the Vagrant
VM and run docker commands as the vagrant user.
Change-Id: If9b27b63b1dd017471714e18e70c2bf2138e65db
Signed-off-by: Kyle Mestery <mestery@mestery.com>
Some things have changed since this was written, namely that kuryr itself
is started as part of devstack and the kuryr subnetpool is created. Also,
the instructions for using user_local.conf to add another Neutron plugin
need some updating.
Change-Id: I5f9a7ee1fff2607f5fbf2117e34ad4bc9b095b1f
Signed-off-by: Kyle Mestery <mestery@mestery.com>
This adds the ability for the user to inject additional configuration
into local.conf during the provisioning step. One can change the
Neutron plugin, for example, using this configuration.
Change-Id: If778960edb1d9c3a23c7947c5ba3bf8a07bdfc3a
Signed-off-by: Kyle Mestery <mestery@mestery.com>
Create a new VAGRANT_KURYR_RUN_DEVSTACK environment variable to make the
`stack.sh` call optional.
Some people may want to edit the `local.conf` file before run `stack.sh`
manually in the VM. Useful for the devstack/plugin.sh development, for
instance.
It is defaulted to `true` for backwards compatibility.
Change-Id: Ia3fe8cb4416a75a3ec05cbb9ce698313daa555e4
This patch modifies the vagrant provision scripts slightly to allow to
deploy CentOS/RedHat machines via VAGRANT_KURYR_VM_BOX.
Change-Id: I8860e6fbb4c2929bfcd67aefbff208f7d13be8f8
Make the Vagranfile look better by indenting the options and let modify
some values to make it more configurable.
Change-Id: I22d62db25183db22a640af6ea0df06bdfe72a2d3
A recent enough box in atlas was nowhere to be found so I ended up
making a packer job to create one from the latest ubuntu trusty64
server.
Change-Id: Iefc88197d9948fc100e1df5026e6125c178a9782
This integrates the freshly added devstack plugin with the Kuryr
Vagrant setup.
Also cleans up a few nits found while here in plugin.sh
Change-Id: I5de55e7d6415d4bffe8bb7a2b2e5e15188815c36
Signed-off-by: Kyle Mestery <mestery@mestery.com>
Fix some spelling errors in the scripts and the Vagrant documentation.
Also, add a note about creating the default subnetpool in the Vagrant
documentation.
Change-Id: I13454328d7b4372d6773661b006466f3419c4fe0
Signed-off-by: Kyle Mestery <mestery@mestery.com>
This patch includes the parallels provider as an example and
sets two top variables to control over the RAM and CPUs.
Change-Id: Ib3379721990863259cc9095a715ae663f9a8c5ca
Experimental docker changes very frequently and this can lead to unexpected
behavior. It will be better to use docker latest release rather experimental.
Change-Id: Ic40155a3788e37158df65d43bc8629f4f30a7bbf
Closes-bug: #1507447
These changes will help developers to quickly setup kuryr along with
docker, keystone and neutron using vagrantfile. Complete steps are
mentioned in ReadMe.
Change-Id: Ia2e16c13a9ae0a6c59991d205f055e3ae8b7b33f
Closes-Bug: #1504018
gujin