Because the stable/ocata branch was created from a commit without a tag,
reno can't figure out where to stop scanning on its own. Give it
instructions to stop scanning at 2.0.0, the earliest Ocata-series
release.
Change-Id: I5df03ab71d438799ac0526c6adb99b7abe3e6ba8
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit introduces the NAT support for networking-ovn. The proposal for
NAT support can be found @ [1]
TODO:
1. Add functional test cases (To be followed up in a different patch)
2. Add sync code (Opened a bug to track this)
3. Add unit tests for the new ovsdb APIs (Opened a bug to track this)
[1] https://etherpad.openstack.org/p/Integration_with_OVN_L3_Gateway
Change-Id: I9b78ceb6b42e96c1ba58ed269e369b46113edd7e
Closes-Bug: 1514995
Closes-Bug: 1551717
For v6 subnets, the 'DHCP_Options.options' in the OVN NB DB were set to empty.
This patch now sets this column for v6 subnets and also sets the
'Logical_Switch_Ports.dhcpv6_options' appropriately. If extra DHCPv6 options
are defined for a port, a new row in DHCP_Options table is created just like
the way it is done for DHCPv4.
Beside 'enable_dhcp' attribute check to a subnet, for v6 subnets, we will also
check its 'ipv6_address_mode', to make sure v6 subnets with 'slaac' as
'ipv6_address_mode' attribute value will have no DHCP_Options rows for them
be created.
Co-authored-by: Zongkai LI <lzklibj@cn.ibm.com>
Change-Id: I9cf5a7ef7676c4461c05d6cb2aabbcb95b20f4d7
Releasenote translation publishing is being prepared. 'locale_dirs'
needs to be defined in conf.py to generate translated version of the
release notes.
Note that this repository might not get translated release notes - or
no translations at all - but we add the entry here nevertheless to
prepare for it.
Change-Id: I2ad3ab26a59dfdbdf8d74c5ab577e7820369e232
ovn-controller stores the datapath type and supported interface
types of the host in the external_ids column of the chassis table.
When the bind_port() function is called, this patch determines the
vif_type by reading these values from the chassis row where the port is to
be bound.
If the value of datapath type is 'netdev' and has 'dpdkvhostuser' in
the supported interface types, vif_type will be set to 'vhostuser',
else vif_type will be set to 'ovs'.
The config param 'vif_type' is deprecated and no longer used.
Co-Authored-By: Richard Theis <rtheis@us.ibm.com>
Change-Id: Ia97198a5bceb5d8d39d8556346f3709846f3c5ad
Closes-bug: #1606458
This patch adds a driver interface for the trunk service plugin proposed
at https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms
One has to enable the service_plugin 'trunk' in the neutron
configuration file to try this feature.
Change-Id: I4e835e11d59cd7b9fedfdc56583b03dd2ee4c023
Add support for multi-provider and multi-segmented networks
in support of neutron routed networks.
Change-Id: I311ad8bb965aa0665465cdb14769a03ac0207e45
Partially-Implements: blueprint routed-networks
OVN native L3 and DHCP don't provide metadata support so config drive
must be used when both are enabled. However, if the conventional DHCP
agent is enabled it can be configured to provide metadata support.
This patch set provides the necessary DevStack and Vagrant deployment
fixes to properly configure DHCP and metadata support. In addition,
documentation and release notes have been updated accordingly. And
finally, the q-meta service was removed from devstackgatekuryrrc,
since the gate job is setup for OVN native services.
Co-Authored-By: Matt Kassawara <mkassawara@gmail.com>
Change-Id: I9f6b23247df01c40c127b0e9daecd12f5721ff50
Related-Bug: #1514488
This patch set provides documentation (feature, install and
testing) updates along with release notes updates for the
OVN native DHCP support.
Change-Id: I05905568a28f577e479354019318bdd3740a9d38
Related-Bug: #1514488
The 'revisions' extension is now part of the default neutron
service plugins [1] and is picked up automatically by the
networking-ovn ML2 driver.
[1] https://review.openstack.org/#/c/303966/
Change-Id: If35c4aa74fa738f51f7493881e343b7ec45293e6
Update the OVN DevStack plugin to use the geneve tenant network
type. This includes related install documentation updates for
ml2_conf.ini.
This patch set also validates network creation precommit. The
validation will ensure a valid network type is used and that
a multi-provider network isn't created (they will be supported
with routed networks).
A follow-on patch set will support vlan tenant network type.
Depends-On: Id75651dfe57a07045a6932a0369668f33c7eef09
Change-Id: I3e25999b24c23413596f1a95f22f794712814ce8
Partial-Bug: #1588966
This patch set converts networking-ovn from a core
plugin to an ML2 mechanism driver.
This patch set completes the following conversion work:
- DevStack and Vagrant deployment updates for ML2
- Documentation and release note updates for ML2
- Removes core plugin code and refactors remaining code
over to ML2 mechanism driver
The conversion work remains:
- Resolve the ML2 unit test TODOs
- Resolve concerns about ML2 mechanism driver _ovn
property raised in [1].
[1] https://review.openstack.org/#/c/323460/
Co-Authored-By: Richard Theis <rtheis@us.ibm.com>
Co-Authored-By: John Kasperski <jckasper@us.ibm.com>
Change-Id: Iffa596baa5c7520c1ca5ecddaab790c52e761460
Closes-Bug: #1578198
Closes-Bug: #1550278
Add the initial newton release note for networking OVN.
The note is based on the currently documented features
and may be updated throughout the release.
Change-Id: I86cc6c48196f8eeb9a0ccb4341485e740515fbe1
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