Currently, there is no dns servers prioritization for subnets
for Neutron.
Generally speaking, it is useful to keep the order of dns
nameservers consistent. Add a new column named 'order' in table
'dnsnameservers' and add nameserver into DB one by one.
Closes-Bug: #1218629
Implements: blueprint keep-dns-nameserver-orderconsistency
Change-Id: Id937aea411397d39370368a4eb45be26c4eefa9e
Metaplugin is removed in Liberty.
Remove all metaplugin related codes.
DocImpact
APIImpact
Co-Authored-By: Itsuro Oda <oda@valinux.co.jp>
Change-Id: I9cf36e1fd3a009c175e0d475af407a30f4e5c408
Closes-Bug: #1465126
There may be projects that have not being created yet, so revise
the wording a bit to provide clarity that new projects can also
submit for inclusion right off the bat.
Change-Id: I862dc3d1835472066c23c3df8e049ae17bf47c2b
Now note in devref/contribute.rst is formated as a section,
so it will appear at catalog which is pretty ugly.
This fix uses note admonition to replace it and specifies Mitaka
as the release name instead of Mxxx.
Change-Id: Ic4afb086e7d4eace035ebe74d1244eabe1ff8915
In wiki it is intended to keep track of neutron changes that may affect
external plugins and drivers. The information should be kept in a living
document in the devref area of the neutron code tree.
Change-Id: Ic73ffd02fbaea48fcb6ad29dd5c9e91870064cb1
Closes-Bug: #1470598
Most of the text is stolen from the corresponding spec:
Ib27c6eb8c901536f1f30d0911dedd4db13d76e9f
Co-Authored-By: Mike Bayer <mike_mp@zzzcomputing.com>
Change-Id: Ib10c13f841f7cebb90c57f4b0d08fc2c3701da97
Eugene stepped down as bug czar a month or so ago, update it to reflect
the fact I've been triaging bugs since then and will be the contact
point now.
Change-Id: I598ac4ea742e39987e5554184e0df4fc718104ab
Signed-off-by: Kyle Mestery <mestery@mestery.com>
New migration rule scheme is introduced. Now, changes are classified
into the following branches:
- expand (additive changes only)
- contract (contraction changes, including data migration)
Make 'neutron-db-manage revision' generate two separate migration
scripts, one per branch.
Now that we support multiple heads, renamed HEAD file in HEADS. We still
don't allow more branching, so keep validation for the number of
branches.
For backwards compatibility, calling to 'upgrade head' applies both
branches in proper order.
Note that advanced services will be moved to the new migration scheme in
separate patches for respective repos.
This patch does not introduce autogenerate support for multiple branches
for 'revision' command (that depends on a new alembic version yet
unreleased; but alembic/master already has everything to support us).
The patch does not implement 'expand' or 'contract' commands that are
anticipated by the spec proposal. Those will come in consequent patches.
Upgrade impact is backwards compatible: those who are interested in
reducing downtime while applying some migration rules can opt in it by
modifying their upgrade practices, while everything should still work
the old way for those who don't care.
blueprint online-schema-migrations
DocImpact
UpgradeImpact
Change-Id: I3823900bc5aaf7757c37edb804027cf4d9c757ab
Since networking-plumgrid has been approved [1] in
governance to be part of Neutron. So as per the
concept of Lieutenants for Neutron, this patch defines
clear point of contact for networking-plumgrid.
[1] https://review.openstack.org/#/c/197168/
Change-Id: I01706b69aac5ac3970913320ff717dc561ea4f8f
Make sure we document the fact that neutron.openstack.common.* contents
are not meant to be used by external repositories (except, temporarily,
*aas repos).
If I could bootstrap the oslo-incubator subtree from scratch, I would
put it under neutron._openstack, to indicate that it's for internal
usage only. But we can't do it now, so instead I update devref.
Change-Id: I42252a7b0a07759c57995b2fc1f8d20ecba7d33b
We made previous attempt to get rid of all warnings, but it turned out
that gate does not execute tox's docs job but runs build_sphinx
directly.
The latter behaviour should be fixed, but while at it, we
should prepare neutron job to be executed in gate by cleaning up all
warnings.
Closes-Bug: #1466554
Change-Id: I8c265eae2175425568479116d1faef7d87fdcc02
The project is being bootstrapped in [1,2], this change reflects
that in the sub_projects doc.
[1] I3825a1e02713f45e2c769eaa8fd0f1ab48d14372
[2] Iec53129d7c19620d690e71032c83907f03c66d9f
Change-Id: I7c235bfe444bbb9afc7d4d8c92704c9bfc09ab49
Let's remove the empty table, to cut down the risk of inconsistency,
and further explain what the list of affiliated project is for.
Change-Id: I3c8970db8de4fc211233903e8220cda72d47e193
Several git repos were just moved from stackforge to openstack.
Reflect the move in various places where the URL was in docs and
comments. In passing, also change URLs to git.openstack.org instead
of github, as that is the official home of all of these repos.
Change-Id: I6c79a192d6604cef01e88d5b305fcc2b0f9c6b30
Co-Authored-By: Kyle Mestery <mestery@mestery.com>
Signed-off-by: Russell Bryant <rbryant@redhat.com>
Signed-off-by: Kyle Mestery <mestery@mestery.com>
The current core reviewers hierarchy didn't have a place for the
parts of ML2 that weren't related to agent communication. For now
we can put all of ML2 under the built-in control-plane until we
decide it needs to be put somewhere else.
Change-Id: Ic4924e0041c4cbb955d8fac0f96ec56406d6466e
Question about the use of the two bridges has come up in the past
multiple times, so let's fill the gap in the developer documentation.
A user-facing documentation patch will have to follow up, if we want
to be very thorough.
Change-Id: I6dac0f9bdaf7b3b7bff8745d4103ccc71df61a0a
changzhi