| 2016-06-09 18:02:25 |
Siddanagouda Khot |
bug |
|
|
added bug |
| 2016-06-09 18:04:38 |
Siddanagouda Khot |
neutron: assignee |
|
Siddanagouda Khot (siddanmk) |
|
| 2016-06-09 18:05:08 |
Siddanagouda Khot |
tags |
|
bgpvpn vni vxlan |
|
| 2016-06-09 18:36:12 |
Siddanagouda Khot |
affects |
neutron |
bgpvpn |
|
| 2016-06-09 23:54:40 |
Siddanagouda Khot |
description |
Current bgpvpns table in Neutron maintains VPN information. Adding a new column 'VNI' to cater to EVPN/VxLAN requirements. |
Current bgpvpns table in Neutron maintains VPN information. Adding a new column 'VNI' to cater to EVPN/VxLAN requirements.
=====================================================
Add ‘VNI’ column in bgpvpns table in Neutron database
=====================================================
Problem Description
===================
[1] describes the OpenStack BGP EVPN route advertisement solution. This solution uses BGPVPN [2] to store and retrieve VPN information. Current bgpvpns table in BGPVPN doesn’t have VNI column. Adding ‘VNI’ column addresses the EVPN/VxLAN [3] reqiurement.
Proposed Change
===============
Add ‘VNI’ column to bgpvpn table in Neutron database which is also mentioned in [2]
Data Model Impact
-----------------
Current bgpvpns table has following fields:
- name
- id
- tenant_id
- type
- route_targets
- import_targets
- export_targets
- route_distinguishers
A new ‘vni’ filed will be added:
vni = sa.Column(sa.Integer)
Respective CRUD functions update:
class BGPVPNPluginDb(common_db_mixin.CommonDbMixin):
route_targets=rt,
import_targets=i_rt,
export_targets=e_rt,
- route_distinguishers=rd
+ route_distinguishers=rd,
+ vni=bgpvpn['vni']
)
REST API Impact
---------------
As mentioned in [2]
Security Impact
---------------
As mentioned in [2]
Notifications Impact
--------------------
A notification should be provided when the value of the VNI changes.
Other End User Impact
---------------------
None
Performance and Scale Impact
----------------------------
As mentioned in [2]
IPv6 Impact
-----------
As mentioned in [2]
Other Deployer Impact
---------------------
As mentioned in [2]
Dependencies
============
As mentioned in [2]
Testing
=======
Tempest Tests
-------------
As mentioned in [2]
Functional Tests
----------------
As mentioned in [2]
API Tests
---------
As mentioned in [2]
Documentation Impact
====================
User Documentation
------------------
As mentioned in [2]
Developer Documentation
-----------------------
Refer to the BGPVPN developer documentation.
References
==========
[1] OpenStack BGP EVPN IP Prefix advertisement: http://docs-draft.openstack.org/54/322654/2/check/gate-neutron-specs-docs/e06688e//doc/build/html/specs/newton/bgp-evpn-advertisement.html
[2] BGPVPN: http://docs.openstack.org/developer/networking-bgpvpn/
[3] A NVO solution for EVPN draft: https://tools.ietf.org/html/draft-ietf-bess-evpn-overlay-03 |
|
| 2016-06-09 23:55:26 |
Siddanagouda Khot |
description |
Current bgpvpns table in Neutron maintains VPN information. Adding a new column 'VNI' to cater to EVPN/VxLAN requirements.
=====================================================
Add ‘VNI’ column in bgpvpns table in Neutron database
=====================================================
Problem Description
===================
[1] describes the OpenStack BGP EVPN route advertisement solution. This solution uses BGPVPN [2] to store and retrieve VPN information. Current bgpvpns table in BGPVPN doesn’t have VNI column. Adding ‘VNI’ column addresses the EVPN/VxLAN [3] reqiurement.
Proposed Change
===============
Add ‘VNI’ column to bgpvpn table in Neutron database which is also mentioned in [2]
Data Model Impact
-----------------
Current bgpvpns table has following fields:
- name
- id
- tenant_id
- type
- route_targets
- import_targets
- export_targets
- route_distinguishers
A new ‘vni’ filed will be added:
vni = sa.Column(sa.Integer)
Respective CRUD functions update:
class BGPVPNPluginDb(common_db_mixin.CommonDbMixin):
route_targets=rt,
import_targets=i_rt,
export_targets=e_rt,
- route_distinguishers=rd
+ route_distinguishers=rd,
+ vni=bgpvpn['vni']
)
REST API Impact
---------------
As mentioned in [2]
Security Impact
---------------
As mentioned in [2]
Notifications Impact
--------------------
A notification should be provided when the value of the VNI changes.
Other End User Impact
---------------------
None
Performance and Scale Impact
----------------------------
As mentioned in [2]
IPv6 Impact
-----------
As mentioned in [2]
Other Deployer Impact
---------------------
As mentioned in [2]
Dependencies
============
As mentioned in [2]
Testing
=======
Tempest Tests
-------------
As mentioned in [2]
Functional Tests
----------------
As mentioned in [2]
API Tests
---------
As mentioned in [2]
Documentation Impact
====================
User Documentation
------------------
As mentioned in [2]
Developer Documentation
-----------------------
Refer to the BGPVPN developer documentation.
References
==========
[1] OpenStack BGP EVPN IP Prefix advertisement: http://docs-draft.openstack.org/54/322654/2/check/gate-neutron-specs-docs/e06688e//doc/build/html/specs/newton/bgp-evpn-advertisement.html
[2] BGPVPN: http://docs.openstack.org/developer/networking-bgpvpn/
[3] A NVO solution for EVPN draft: https://tools.ietf.org/html/draft-ietf-bess-evpn-overlay-03 |
Current bgpvpns table in Neutron maintains VPN information. Adding a new column 'VNI' to cater to EVPN/VxLAN requirements.
=====================================================
Add ‘VNI’ column in bgpvpns table in Neutron database
=====================================================
Problem Description
===================
[1] describes the OpenStack BGP EVPN route advertisement solution. This solution uses BGPVPN [2] to store and retrieve VPN information. Current bgpvpns table in BGPVPN doesn’t have VNI column. Adding ‘VNI’ column addresses the EVPN/VxLAN [3] reqiurement.
Proposed Change
===============
Add ‘VNI’ column to bgpvpn table in Neutron database which is also mentioned in [2]
Data Model Impact
-----------------
Current bgpvpns table has following fields:
- name
- id
- tenant_id
- type
- route_targets
- import_targets
- export_targets
- route_distinguishers
A new ‘vni’ filed will be added:
vni = sa.Column(sa.Integer)
Respective CRUD functions update:
class BGPVPNPluginDb(common_db_mixin.CommonDbMixin):
route_targets=rt,
import_targets=i_rt,
export_targets=e_rt,
- route_distinguishers=rd
+ route_distinguishers=rd,
+ vni=bgpvpn['vni']
)
References
==========
[1] OpenStack BGP EVPN IP Prefix advertisement: http://docs-draft.openstack.org/54/322654/2/check/gate-neutron-specs-docs/e06688e//doc/build/html/specs/newton/bgp-evpn-advertisement.html
[2] BGPVPN: http://docs.openstack.org/developer/networking-bgpvpn/
[3] A NVO solution for EVPN draft: https://tools.ietf.org/html/draft-ietf-bess-evpn-overlay-03 |
|
| 2016-06-09 23:56:34 |
Siddanagouda Khot |
summary |
Enhancement: Add 'VNI' column in bgpvpns table in Neutron database. |
[RFE] Add 'VNI' column in bgpvpns table in Neutron database. |
|
| 2016-06-10 08:38:35 |
Thomas Morin |
bgpvpn: status |
New |
Confirmed |
|
| 2016-06-10 08:38:45 |
Thomas Morin |
bgpvpn: importance |
Undecided |
Wishlist |
|
| 2016-06-14 16:08:17 |
Mickey Spiegel |
bug |
|
|
added subscriber Mickey Spiegel |
| 2016-06-15 02:05:00 |
Steve Ruan |
bug |
|
|
added subscriber steve |
| 2016-06-21 09:00:16 |
Thomas Morin |
bug |
|
|
added subscriber Diego Garcia del Rio |
| 2016-06-21 15:21:14 |
Thomas Morin |
bgpvpn: assignee |
Siddanagouda Khot (siddanmk) |
steve (ruansx) |
|
| 2016-06-22 09:33:19 |
OpenStack Infra |
bgpvpn: status |
Confirmed |
In Progress |
|
| 2016-07-01 01:15:18 |
Mickey Spiegel |
description |
Current bgpvpns table in Neutron maintains VPN information. Adding a new column 'VNI' to cater to EVPN/VxLAN requirements.
=====================================================
Add ‘VNI’ column in bgpvpns table in Neutron database
=====================================================
Problem Description
===================
[1] describes the OpenStack BGP EVPN route advertisement solution. This solution uses BGPVPN [2] to store and retrieve VPN information. Current bgpvpns table in BGPVPN doesn’t have VNI column. Adding ‘VNI’ column addresses the EVPN/VxLAN [3] reqiurement.
Proposed Change
===============
Add ‘VNI’ column to bgpvpn table in Neutron database which is also mentioned in [2]
Data Model Impact
-----------------
Current bgpvpns table has following fields:
- name
- id
- tenant_id
- type
- route_targets
- import_targets
- export_targets
- route_distinguishers
A new ‘vni’ filed will be added:
vni = sa.Column(sa.Integer)
Respective CRUD functions update:
class BGPVPNPluginDb(common_db_mixin.CommonDbMixin):
route_targets=rt,
import_targets=i_rt,
export_targets=e_rt,
- route_distinguishers=rd
+ route_distinguishers=rd,
+ vni=bgpvpn['vni']
)
References
==========
[1] OpenStack BGP EVPN IP Prefix advertisement: http://docs-draft.openstack.org/54/322654/2/check/gate-neutron-specs-docs/e06688e//doc/build/html/specs/newton/bgp-evpn-advertisement.html
[2] BGPVPN: http://docs.openstack.org/developer/networking-bgpvpn/
[3] A NVO solution for EVPN draft: https://tools.ietf.org/html/draft-ietf-bess-evpn-overlay-03 |
Current bgpvpns table in Neutron maintains VPN information. Adding a new column 'VNI' to cater to EVPN/VxLAN requirements.
=====================================================
Add ‘VNI’ column in bgpvpns table in Neutron database
=====================================================
Problem Description
===================
[1] describes the OpenStack BGP EVPN route advertisement solution. This solution uses BGPVPN [2] to store and retrieve VPN information. Current bgpvpns table in BGPVPN doesn’t have VNI column. Adding ‘VNI’ column addresses the EVPN/VxLAN [3] reqiurement.
Proposed Change
===============
Add ‘VNI’ column to bgpvpn table in Neutron database which is also mentioned in [2]
Data Model Impact
-----------------
Current bgpvpns table has following fields:
- name
- id
- tenant_id
- type
- route_targets
- import_targets
- export_targets
- route_distinguishers
A new ‘vni’ filed will be added:
vni = sa.Column(sa.Integer)
Respective CRUD functions update:
class BGPVPNPluginDb(common_db_mixin.CommonDbMixin):
route_targets=rt,
import_targets=i_rt,
export_targets=e_rt,
- route_distinguishers=rd
+ route_distinguishers=rd,
+ vni=bgpvpn['vni']
)
References
==========
[1] OpenStack BGP EVPN IP Prefix advertisement: http://docs-draft.openstack.org/54/322654/2/check/gate-neutron-specs-docs/e06688e//doc/build/html/specs/newton/bgp-evpn-advertisement.html
[2] BGPVPN: http://docs.openstack.org/developer/networking-bgpvpn/
[3] A NVO solution for EVPN draft: https://tools.ietf.org/html/draft-ietf-bess-evpn-overlay-03
Proposed fix: https://review.openstack.org/332711 |
|
| 2017-05-16 16:29:17 |
Vivekanandan Narasimhan |
bgpvpn: assignee |
Steve Ruan (ruansx) |
|
|
| 2017-05-16 16:29:25 |
Vivekanandan Narasimhan |
bgpvpn: assignee |
|
Vivekanandan Narasimhan (vivekanandan-narasimhan) |
|
| 2017-08-21 15:36:42 |
Thomas Morin |
bgpvpn: milestone |
|
8.next |
|
| 2017-09-14 05:02:10 |
Deepthi V V |
bgpvpn: assignee |
Vivekanandan Narasimhan (vivekanandan-narasimhan) |
Deepthi V V (deepthivv88) |
|
| 2018-01-29 09:04:21 |
Thomas Morin |
bgpvpn: status |
In Progress |
Fix Released |
|
