For unit and functional:
The commit d00a50aad11465d904663dea14b3814017bcff75 moved the
plugins.ml2.config module to conf.plugins.ml2.config
For functional tests only:
Modify the post_test_hook.sh script to accomodate the new changes in
os-testr. This fix for networking-ovn is basically a copy & paste from
the neutron one [0].
[0] https://review.openstack.org/#/c/503138/
Change-Id: I4fbcbfdd6d5f9fa77414df15302da517f23986bd
oslo.config provides sphinx extensions to generate config reference
and sample config files. This commit enables the auto-generation of
the networking config reference.
Part of doc-migration work
Change-Id: I1e5323328c5e8f09dc291ee7d083e2d6c7638a9c
* Use oslo-config-generator config file to generate ml2_conf.ini.
This can be used by oslo_config sphinxext in a follow-up patch.
* Generate metadata_agent.ini sample automatically.
Previously metadata_agent.ini was maintained manually.
* Update .gitignore not to ignore etc directory.
I see no good reason not to maintain etc directory in the repo.
* Update devstack plugin to ensure the output directory
where the ml2_conf sample file will be generated.
Preparation for auto-generated config reference
as part of doc-migration community-wide effort.
Change-Id: I64c6c66f9e14b558733254e9c9c2c64d647b70f8
When we write a grenade plugin, we need most of the functions
in plugin.sh. Hence moving the functions to a library, it will
enable both the plugin functionalities to operate on the same library.
Change-Id: Idf37e1561318dcf84e89b402c0be3ac4b3cfc266
Release management team has modified the way it releases
projects and a new process and guideline has been established.
This change adds support for the same. More information on
this can be found at [1].
Within OpenStack, reno can be used to create release notes
using the following command:
tox -e venv -- reno new slug-goes-here
where slug-goes-here is a prefix to your notes.
More info on reno usage can be found at [2].
[1]: http://lists.openstack.org/pipermail/openstack-dev/2015-November/078301.html
[2]: http://docs.openstack.org/developer/reno/usage.html
Change-Id: Iad4573a738dcc972b003c20b1a3895dfd3094c2b
This updates the Vagrant setup to deploy a 3-node Ubuntu Trusty
setup (1 control node, 2 compute nodes). The Vivid image this
was previously trying to download was HUGE, and it's not clear
why running on Vivid is better considering the gate uses
Trusty.
Also, adjust the names of the nodes this spawns to be a bit
more sane. They are now spawned as:
ovn-controller
ovn-compute1
ovn-compute2
One final change adds some additional configuration into
local.conf which allows this all to come up and run.
Closes-Bug: #1499917
Change-Id: Ife6cfbe18ea1053ca52b8ff0f074987c178a713c
Signed-off-by: Kyle Mestery <mestery@mestery.com>
The following commit 8912cb89 causes the networking-ovn.ini file to
be autogenerated and placed in the top level etc of the networking-ovn
project which does not exist. This patch adds etc to .gitignore so I
can make sure I don't accidently add it to the repo.
Change-Id: Ia03e9b7f289afce665d3ac35ce2bbb33fec73911
Take same approach used here: https://review.openstack.org/#/c/127918/
In order to avoid the need to re-ignore new editors
Change-Id: I634b6172006506be06175a2640dc8f6adccaf603
Lucas Alvares Gomes