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

What are the network components in OpenStack Neutron

2025-01-28 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Network Security >

Share

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

This article will explain in detail what are the network components in OpenStack Neutron. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

Environment introduction

Types

The control node and the computing node are together to form an all-in-one

Memory

8G

Hard disk

200G

Network card

2 yuan

Network component concept

OpenStack Networking (neutron), which allows you to create and plug in interface devices managed by other OpenStack services. Plug-in implementation can accommodate different network devices and software, providing flexibility for OpenStack architecture and deployment.

It contains the following components:

Neutron-server

Receive and route API requests to the appropriate OpenStack network plug-in to achieve the desired purpose.

OpenStack network plug-ins and agents

Plug-in ports, create networks and subnets, and provide IP addresses, which vary depending on vendor and technology. OpenStack networks are based on plug-ins and agents to bridge Cisco virtual and physical switches, NEC OpenFlow products, Open vSwitch,Linux bridging and VMware NSX products.

Message queue

Most OpenStack Networking installations are used to route information between neutron-server and various agent processes. Also acts as a database for specific plug-ins to store network state

The OpenStack network mainly interacts with OpenStack computing to provide instances of network connectivity to it.

Network (neutron) concept

The OpenStack Network (neutron) manages the access layer of all virtual network infrastructure (VNI) and physical network infrastructure (PNI) in the OpenStack environment. OpenStack networks allow tenants to create advanced virtual network topologies such as firewall, load balancer, × ×, and so on.

Network services provide abstract concepts of networks, subnets, and routing these objects. Each abstract concept has its own function to simulate the corresponding physical devices: the network includes subnets, and routes are routed and forwarded between different subnets and networks.

At least one external network must be included for any given network. Unlike other networks, an external network is not just a defined virtual network. Instead, it represents a view that can be accessed from a physical, external network outside of the OpenStack installation. The IP address on the external network is accessible to any physical device on the external network.

Any Networking setting has one or more internal networks except external networks. These software-defined networks connect directly to virtual machines. Only virtual machines on a given network, or those on subnets connected to similar routes through interfaces, can directly access virtual machines connected to that network.

Routing between networks is necessary if the external network wants to access the instance or vice versa. Each route is equipped with a gateway for connecting to the external network and one or more interfaces connected to the internal network. Just like a physical route, subnets can access machines in other subnets on the same route, and machines can also access routed gateways to access external networks.

Security groups are also supported by network services. Security groups allow administrators to define firewall rules in security groups. An instance can belong to one or more security groups, and the network configures rules in these security groups, blocking or opening ports, port ranges, or traffic types for this instance.

Network architecture

The network consists of the following agents

Agent

Description

Plug-in agent

Runs on each host to perform local virtual switch configuration

Dhcp agent

Provide dhcp services to tenant network

L3 agent

Provide layer 3 / NAT forwarding service to provide external network access

Metering agent

Provide three-layer traffic metering for tenant network

Network creation create external network

Log in to the management page and click Project-Network-Network Topology

Click create Network in the upper right corner, check sharing, and create subnets. The purpose of sharing is to make the network available to all tenants, so that all tenants can link to the external network.

Enter the name, network address, gateway and other information. Note that the address here should be the public network address in principle.

Uncheck the box to activate DHCP, and then write down the address pool range and DNS. Because it is a public network address, you need to remove DHCP. Generally, public network addresses are bought with money and need to be applied by tenants, so you cannot DHCP. Click create when you are finished.

Complete external network creation

Define external network

Just now we created a network, but it is not marked as an external network. Now let's define it as external. Click Administrator, Network, and then click Edit Network on the right.

To check the external network here, click Save

Create a private internal network

Return to Project-Network-Network Topology to create a network

Enter a name and check create subnet, but do not check sharing, because this network is the private private network of admin, the tenant.

Enter name, address, gateway

Enter the address pool, because it is an intranet, so start DHCP

The creation is completed, as shown below

Create a router

As shown in the figure above, there are both external and internal networks, but there is no connection between the two networks. obviously, the machines in the intranet cannot be connected to the network, so routers are needed to provide routing.

In the upper right corner of this page, click the New Route button

Enter a name and select the appropriate external network. If you do not have any networks here, please return to the section defining external networks.

Add private network interface

Click to add interface

Select the private network interface and enter the IP address as the gateway

Check the network

As shown in the following figure, the internal and external networks are connected through the router

This is the end of this article on "what are the network components in OpenStack Neutron?". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

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