Open Stack

Hello Chaoyi,

Thanks for your answer.

Related to Route Target parameter (RT) : I referred to the figure displaying pods interconnection through an E-VPN L2 network ("Tricircle in a nutshell" presentation).

My question is : how are there populated and/or exchanged through the E-VPN interconnection ?

Thanks,

Best Regards,

            Dina

De : joehuang [mailto:joehuang at huawei.com]
Envoyé : mercredi 23 novembre 2016 04:20
À : SOL Dina IMT/OLN; openstack-dev
Objet : RE: [openstack-dev][tricircle]Questions about Tricircle L2 and L3 implementation

Hello, Dina,

Thank you for your comments, it'll be good to discuss tricircle related topic in openstack-dev so that more people can be involved in if necessary, and keep the project transparent. So I copied the reply to  openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>.

For L2VxLAN, the VNI identifiers will be allocated in central Neutron, and then same VNI segment will be used for local Neutron during get_network or get_port from Nova, the local plugin in local Neutron will query the network segment info. and persist same uuid and VNI in local Neutron. But VxLAN based cross Neutron L2 networking has not started yet, the spec has not submitted for review yet, currently only VLAN based L2/L3 networking were implemented, supported features could be found in the release notes:https://github.com/openstack/tricircle/blob/master/releasenotes/notes/initial-release-notes.yaml .

 VxLAN L2 networking and VxLAN as the bridge network for L3 networking will rely on the patch for "formalize the tunnel termination point by adding it to the port binding data model" which is mentioned in "Eliminating L2pop as a mechanism driver" http://lists.openstack.org/pipermail/openstack-dev/2016-November/107061.html

Before VxLAN L2 networking and VxLAN as the bridge network for L3 networking, this spec is being reviewed, https://review.openstack.org/#/c/396564/, please join the review to see whether it can meet your demands, especially for the cross Neutron networking models.

What is "RT parameters"?

Tricircle supported L3 networking based on shared VLAN bridge network, you can refer to "6.6  L3 Networking across Neutron", but just as what mentioned in the release notes,  only VLAN L2 network and shared VLAN as the bridge network for L3 networking are supported.

There are todo list for the usage documentation in ocata release, you are welcome to join the contribution, no matter documentation or source code or review.

Best Regards
Chaoyi Huang (joehuang)
________________________________
From: dina.sol at orange.com<mailto:dina.sol at orange.com> [dina.sol at orange.com]
Sent: 22 November 2016 21:54
To: joehuang
Subject: Questions about Tricircle L2 and L3 implementation
Hello Chaoyi Huang,

I have read Tricirle wiki documentation and some presentations.
May I ask you I have few questions about Tricircle implementation ?
Here there are :

1°) L2 VxLAN
How are choosen VNI identifiers ?
How are choosen RT parameters ? Is a control plane used or all is configured within a pool ?

2°) L3
Does Tricircle support L3 interconnection ?
Have you documentation about that ?

Thanks,
Best Regards,

            Dina SOL
--------------------------------
[logo-Orange]
Dina Sol
Orange/ IMT/ OLN/ WTC/ IEE/ NAVI (Network Automation and Virtualized Infrastructure)
Orange Labs
2, avenue Pierre Marzin
22307 Lannion Cedex
tel : 00 33 (0)2 96 07 11 22
Dina.Sol at orange.com<mailto:Dina.Sol at orange-ftgroup.com>



_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161123/fa65d452/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1001 bytes
Desc: image001.jpg
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161123/fa65d452/attachment.jpg>