Shulou(Shulou.com)05/31 Report--

How to solve the OpenStack cloud interconnection problem, many novices are not very clear, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

Abstract: it is recommended to use Neutron API to establish trusted network interconnection of OpenStack cloud.

Applications and networks have become distributed. Applications are segmented into micro-services, so the network is made up of different clouds from different regions. With this, more and more security issues have emerged, and the need to control all resources has increased. SD-WAN is available to enterprises. But what if there are fewer data centers or endpoints and are distributed in multiple regions?

There may be a situation where you need to interconnect two or more independent data centers, or use NFV PoP supported by OpenStack. These data centers are thought to be located in different areas. These data centers initially wanted to interconnect on demand. In addition, interconnections may require private addressing and isolation to share data end-to-end with dedicated communication channels. A sub-VPN as a service (VPNaaS) that combines on-demand and private addressing and isolation capabilities. After choosing an appropriate solution after the VPN review, we have different VPN options available. But this solution involves IPSec, which has performance overhead. In addition, in order to achieve the correct interconnection, you need a solution to avoid packet isolation overhead.

One of the architectures of OpenStack cloud interconnection can be to add a choreographer between clouds, and the resources of the associated clouds are interconnected. But this architecture has several drawbacks.

The choreographer may require administrator privileges to establish a network in resources in the data center. This is difficult when it comes to different organizations. In addition, adding a choreographer exposes API to different attacks, so this is considered a complex system.

One recommended option is to extend Neutron API to interconnect resources, such as virtual routers in data centers supported by OpenStack. It includes User Facing API and Neutron to Neutron API.

In User Facing API, there is a symmetrical call-the central administrator makes a call to the Neutron module in the data center. After approval from the two data centers, a connection will be established.

In Neutron to Neutron API, API will allow each Neutron component to check whether a symmetric interconnect is defined on the other side. In this way, Neutron components in different regions coordinate to establish private isolated interconnections without orchestration or network device configuration.

This solution was discussed at the OpenStack Summit in Berlin in 2018. This solution applies to the following use cases:

-- OpenStack is in the data center

-- An OpenStack cloud involves multiple regions

Multiple OpenStack clouds with mutually coordinated trust entities

Different OpenStack cloud instances use different SDN solutions.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

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.