Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to integrate OpenStack and Tungsten Fabirc?

2025-02-24 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Network Security >

Share

Shulou(Shulou.com)06/01 Report--

This article is sorted out from the speech given by Krzysztof Kajkowski, the engineering director of CodiLime, at "the Establishment of TF Chinese Community and the first full meeting". Click to download the PDF document https://tungstenfabric.org.cn/assets/uploads/files/openstack-powered-by-tf.pdf.

For more information about the meeting, please reply to "Inaugural meeting" on the official account of "TF Chinese Community".

Krzysztof Kajkowski, Engineering Director of CodiLime

Hello, everyone. I am Kris from CodiLime, from Poland. I have been working in the Tungsten Fabirc (hereinafter referred to as TF) community for five years.

What I'm going to show you is the integration of OpenStack and Tungsten Fabric. Because TF SDN can run with other ML2 drivers, users can run work based on OVS, SR-IOV and vRouter at the same time, and migrate OVS-based computing to vRouter-based in real time.

Here is the basic structure, with OpenStack at the bottom and three deployment patterns above, namely SR-IOV, OVS, and TF.

In the following demonstration, I will create multiple virtual machines through OpenStack's Web UI, and the virtual machines can communicate over the network.

OpenStack will orchestrate and manage these virtual machines, and in the background we run the plug-in of ML2 to create VM and network in TF's vRouter.

This plug-in is the integration solution of TF and OpenStack, which enables OpenStack to communicate with SR-IOV, OVS, and so on.

The network we are running here is the vMX of Juniper Network. In L2 connection communication, we use vMX for routing and switching. It's a little more complicated on L3, where vMX works as a router.

All of these background functions are pre-configured in Demo.

The presentation is divided into four parts: first, to create instances for each node (that is, OVS, TF, SR-IOV); then I will show how the instances communicate with each other; we will also demonstrate how the instances communicate with the Internet Internet; and finally, I will show how to migrate the virtual machine on the OVS to the TF.

I created a demo called VM-MIGRATE from OpenStack UI and migrated through vRouter.

First, let's start OpenStack to create the instance.

First create an instance of OVS, and then start another instance of vRouter on the same network with the network address of 50.50.50.X, all of which are run through OpenStack.

Add another instance of SR-IOV, which shows the ports of the network.

Let's start by creating these three instances, all on the same network.

This is the interface of TF, and we saw these saved instances above. So there is no problem, which means that OpenStack has realized the communication with TF through vRouter.

Next, let's take a look at the network communication between these instances.

We log in to the instance of OVS through the control panel.

Then we ping connected to vRouter's network.

Ping is also connected to SR-IOV 's network.

We are connected to the Internet again under ping.

So we can see that there is no problem with ping communication between the three newly created instances, and all of them are ping connected to the Internet.

Finally, let's show the migration scenario.

Sometimes you don't need to create a new instance, you just need to migrate the virtual machine, but remember to do a network verification test later.

Let's create an instance of VM-MIGRATE.

You can see that this example has already appeared on TF.

We can see its type on OpenStack, which is an OVS type, but it will change later.

Now start the migration. Click migrate, select a node, we select the fourth node, and then submit.

Now that the VM is in the process of being migrated, it should eventually be migrated to note 4.

OK, no problem, you can see that it has become the fourth node, and the IP address has not changed.

If we look at its instance type again, it has become vRouter.

Look at it again from TF. Yes, there is also an example.

Let's check its network connectivity again.

OK, it has no problem with the network connection with OVS, vRouter and SR-IOV.

And now it's a connection to the Internet, and it's all right.

That's all for my live demonstration, thank you!

Https://v.qq.com/x/page/y30216ollak.html (speech + Demo video, 14 minutes long)

Learn more about Tungsten Fabric

Introduction to TF Chinese Community

Main features and use cases of TF

How does TF work?

Detailed explanation of vRouter architecture

Follow Wechat: TF Chinese Community

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Network Security

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report