multisegment Openstack infrastructure

asked 2013-11-12 06:06:47 -0500

azraev gravatar image

Hello, everybody Let me ask you a question. So, for example, customer wants to have 2 network segments in the infrastructure. Most of the infrastracture is KVM-based. It means, most of all compute nodes are Linux servers with KVM. But, there is another segment - VMware ESXi under the vCenter. It is possible to use OVS plugin for "KVM" segment. For VMware it is possible to use NVP (NSX) plugin. Also, we may deprecate OVS plugin and use NVP for all compute nodes including KVM (NVP plugin may work with OVS agents). That is an easy way, but it is not the best one (i guess) Is there a way to use both of plugins (NVP + OVS) in one environment simultaneously? For instance, for one segment the one plugin is used, for another segment - the second plugin? May be, more than one Network Node with different plugins on it? But, how to make them work together? Thanks in advance

edit retag flag offensive close merge delete

2 answers

Sort by ┬╗ oldest newest most voted
0

answered 2013-11-13 03:39:46 -0500

simone.tiraboschi gravatar image

Traditional Quantum/Neutron plugins are substantially monolithic meaning that you can use only one at a time. You have fours alternative solutions with different architecture and side effects:

  • the first one is straightforward: simply use NSX for all managing also OVS with it.
  • the second one involves the usage of ML2 plugin: the ML2 plugin is a framework that enables the use of different L2 technologies at the same time via modular mechanism drivers. Unfortunately, as far as I know, the OVS mechanism driver is ready to use but the NVP no, so this, that should be the reference architecture, is not feasible for you. Neutron/ML2
  • the third one is based on Neutron Metaplugin: you can have different L2 networks managed by different plugins and have them communicate only at level three. Metaplugin specs
  • at last you can also completely segregate your cloud segments having two distinct cells: one for the KVM world and one for the VMWare world. Two distinct cells share only keystone and nova-api being completely independent. Segregating Your Cloud

ciao, Simone

edit flag offensive delete link more

Comments

Thank you very much for your answer. My first thougt was to use NSX for all OVS in the cloud. In such a situation, the segregation of the cloud is an interesting way to solve a problem. Best regards, Art

azraev gravatar imageazraev ( 2013-11-13 04:51:20 -0500 )edit
0

answered 2014-01-10 04:28:52 -0500

azraev gravatar image

One more thing. We can use GRE tunneling with OVS. Also, GRE is supported by VMware NSX too. Is there a way to connect VMs from different part of the cloud? Of course, we may also give the VM a floating IP and an access to the outside.But the question is - can we have a Layer 2 connectivity for VM1 (from "KVM part") and VM2 (from "VMware part")? It seems to me, it is not possible now. Asking just for sure. Best regards, Artem

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2013-11-12 06:06:47 -0500

Seen: 182 times

Last updated: Jan 10 '14