The lbaas team considers neutron-lbaas, neutron-lbaas-dashboard,
and octavia as a unit that should not be separated. Update the
table to make that more clear.
Change-Id: I12302ef8678a3b6e6e9209de2fd24b77a5239de4
Signed-off-by: Russell Bryant <rbryant@redhat.com>
These were from a time long since past, and turned out not be useful
even then.
Change-Id: Ic524f10e414e08010804092f72a114de93681e5c
Signed-off-by: Kyle Mestery <mestery@mestery.com>
Update the list of Neutron sub-projects to make it clear which ones are
currently under the Neutron team under OpenStack governance. No changes are
made here. It only updates this document to reflect projects.yaml in the
governance repository.
Change-Id: I4a96a9d66689a1eca0e202f1f1365236f47b9da1
Signed-off-by: Russell Bryant <rbryant@redhat.com>
Update the upgrade defref doc to more correctly explain the output
from the has_offline_migrations command
Change-Id: Ie68c31354f664165a0c124fb151e8fb449eec8ec
Related-Bug: #1519118
For networks in the same address scope, network traffic routes
directly. This happens not only between internal networks, but also
between internal network and external network. No SNAT is applied
when routing traffic to the external network because addresses on the
internal network are assumed to be viable on the external network.
For networks in different scopes, network traffic can't route
directly. Between internal networks in different scopes, traffic is
blocked. DNAT for floating IPs will still work. Also, shared SNAT to
the external network will still work as it does today.
Change-Id: I439633ebef432b1a2eecee09b647207d5a271bf6
Co-Authored-By: Hong Hui Xiao <xiaohhui@cn.ibm.com>
Implements: blueprint address-scopes
If the required extensions are missing, we currently log an error
that is going to be practically ignored. That said, the unfulfilled
requirement will most definitely going to lead to other failures,
so we might as well fail fast.
This patch also cleans up some <barf>dns-integration nonsense</barf>
within the ML2 framework: the extension must not be declared statically
as it's being loaded by the extension manager, and this fixes the lousy
unit tests we have to live with. As for the db base plugin, some cleanup
is still overdue, but it will have to be taken care of in a follow-up
patch.
Closes-bug: #1538623
Change-Id: Id50eeb52c5d209170042b48821a29af3421c2f5c
The infra and i18n team is now setting up the new infra setup
for translations. This commit updates the corresponding devref
document on the subproject guidelines.
For more detail, see the infra spec available at
http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html.
This basically renames $reponame/locale/$reponame.pot to
$modulename/locale/$modulename.pot.
Change-Id: I7e402453a53fc7b13193f65c71aa1764f1c18924
Alembic migration documentation for developers is updated to explain the need
to update neutron/db/migration/models/head.py when adding models to the
database
Change-Id: I2894058269cbabfd0cbfa83c7f076701e2087a11
Partial-Bug: #1537510
This command should be used by operators and deployment tools to
determine whether full neutron-server shutdown is needed for database
upgrade.
The change also makes neutron-db-manage tool to return the cumulative
result of commands being issued (in most cases it will still be 0 only,
since our command handlers implicitly return None).
DocImpact: Update doc to add new command 'has_offline_migrations' to
'neutron-db-manage' tool. The command determines whether full
neutron-server shutdown is needed for database upgrade.
Closes-Bug: #1519118
Change-Id: I7c5a4882ad4f80459ebe69c9a9c43cc60ce50200
Co-Authored-By: Martin Hickey <martin.hickey@ie.ibm.com>
An interface with an external DNS service is defined for Neutron. A reference
implementation is also included, based on Designate. The interface and the
driver will enable users to publish in the external DNS service the dns_name
and dns_domain attributes associated with floating ips, ports and networks. As
a consequence, the floating ips and networks api is extended to manage dns_name
and dns_domain attributes. The dns_name attribute was added to ports in a
preceding commit
DocImpact: Introduce config option external_dns_driver to specify a driver
for external dns integration. For more info, see
doc/source/devref/external_dns_integration.rst
APIImpact
Implements: blueprint external-dns-resolution
Change-Id: Ic298ad2558410ab9a614f22e1757d1fc8b22c482
Methods _create_ha_network, add_ha_port don't have wrapping
transaction in them, so they are prone to race conditions.
This commit adds a transaction to them. To avoid problem with
rolling back outmost transaction during exception handling,
internal methods have been wrapped in nested transaction.
Nested transaction is required in places like this:
def create():
create_something()
try:
_do_other_thing()
except Exception:
with excutils.save_and_reraise_exception():
delete_something()
def _do_other_thing():
with context.session.begin(subtransactions=True):
....
When exception is raised in _do_other_thing it
is caught in except block, but the object cannot be deleted in
except section because internal transaction has been rolled back.
A new method safe_creation and has been added
that provides a common way of handling such situations.
Closes-bug: #1501686
Change-Id: I952f6f7f8684743aa7f829bd92b1dc41b2c6aecf
The OPNFV project [1] is a reference implementation of the
ETSI NFV architecture built on open source components.
OpenStack, and Neutron in particular, are key elements of
this story, and many requirements and issues are driven and
submitted by OPNFV folks that work in both communities.
This tag makes sure that we can keep all of them together for
tracking purposes.
[1] http://superuser.openstack.org/articles/openstack-and-opnfv-strengthen-collaboration-for-telcos
Change-Id: Ie1675ef6f177558f579097fe035494b9380232d0
We switched to constrained jobs a while back, but these links were
showing the non constrained ones, making these graphs useless.
This patch updates them to reflect the jobs that are currently
running, however the docs job is left for later as right now
switching would make graphite fail with:
'TypeError: reduce() of empty sequence with no initial value'
I suspect that's because the job has never failed so far.
Change-Id: I60cab40f3c12099d8437616d8301aecd858ef54c
os.popen() is deprecated since version 2.6. Resolved with use of
subprocess module.
Change-Id: I2ff32c4dc37c543696125ac755dc4adb69ddacdf
Partial-Bug: #1529836
The L3 agent needs to know the address scope of the fixed ip of each
floating ip because floating ips are a way to cross scope boundaries.
Without the scope information, there could be ambiguity and no way to
know which scope to send it to.
[1] https://review.openstack.org/#/c/189741/
Change-Id: Id9f8c12954a6efbf4d9b99c011652eefbe5f5145
Partially-Implements: blueprint address-scopes
This patch adds unit tests to ML2 and L3 that ensure that the
number of DB calls during list operations for ports, networks,
subnets, routers, and floating IPs remains constant regardless
of the number of ports.
These will prevent changes from slipping in that result in
a separate DB query for each object in a list operation
(for changes to the extensions used by ML2 and the DVR plugin).
Related-Bug: #1525295
Related-Bug: #1513782
Related-Bug: #1525423
Related-Bug: #1525740
Related-Bug: #1526644
Change-Id: I1958fc7c318bbf73238a3ad5be133fa7800c8290
There have been a number of regressions caused by our inability
to thoroughly review relatiohships' loading strategies. We should
at least make an attempt to remind ourselves, and since I am guilty
as charged, this patch is my attempt to redemption.
Change-Id: I879cfceaa51386e9d6c683e7e02487df92b7e290
The rationale is that we would have a single tag to track all
bugs that are about admin and user ease of use, logging quality,
and debuggability.
Change-Id: Ie42e08c924c9e742bdc6d9f4b68bdfbd1a622ba4
Below changes are done as part of this patch.
* Mention about ONOS l3 support.
* Proposing Mr. Albert Dongfeng as a lieutenant for networking-onos.
Change-Id: I87827b08ed868f68cbd49c1fa7b91352d3c46605