CN106101301A - Distributed virtual DHCP service provides system and method - Google Patents

Abstract

The present invention provides a kind of distributed virtual DHCP service to provide system, including: one or more tenants, corresponding one or more of each tenant adapts to the virtual machine of respective virtual network, the plurality of virtual machine is connected to a virtual switch, each virtual network starts a dnsmasq process be responsible for providing DHCP service via the corresponding NameSpace of virtual switch, each NameSpace.The system that the application proposes can avoid the waste of address resource, can realize DHCP traffic isolation simultaneously, and support multi-user operation.

Description

Distributed virtual DHCP service providing system and method

technical field

The present invention relates to the technical field of communication, and more specifically, to a cloud computing multi-tenant-oriented distributed virtual DHCP service providing system and method.

Background technique

Dynamic Host Configuration Protocol (DHCP) is usually applied in large-scale local area network environment, and its main function is to centrally manage and allocate IP addresses, so that hosts in the network environment can dynamically obtain IP addresses, Gateway addresses and DNS server addresses and other information, and increase the utilization rate of addresses.

The DHCP protocol adopts the client/server model, and the dynamic allocation task of the host address is driven by the network host. When the DHCP server receives the information from the network host to apply for an address, it will send relevant address configuration and other information to the network host to realize the dynamic configuration of the network host address information.

Currently, in a cloud computing environment, a virtual machine can manually configure an IP address, or use a virtual DHCP service to obtain an IP address, which is more convenient than the manual method. The way to realize the DHCP service in the current cloud computing products is generally to start a dnsmasq process on the network control node to process the DHCP request of the virtual machine.

Since the dnsmasq that provides the DHCP service runs on one host, there is a single point of failure problem. In order to avoid this problem, it will be deployed in a cluster mode, allowing the dnsmasq process to run on multiple hosts. This brings a new problem, because each dnsmasq process needs a listen IP to listen to the DHCP request of the virtual machine, when too many dnsmasq deployments will take up too many IP resources. On the contrary, if dnsmasq is deployed too little, it will reduce the stability.

Contents of the invention

The present invention provides a cloud computing multi-tenant-oriented distributed virtual DHCP service provision system and method that overcomes the above problems or at least partially solves the above problems.

According to one aspect of the present invention, a distributed virtual DHCP service provision system is provided, including: one or more tenants, each tenant corresponds to one or more virtual machines adapted to their respective virtual networks, and the multiple virtual machines are connected to To a virtual switch, each virtual network corresponds to a namespace via the virtual switch, and each namespace starts a dnsmasq process responsible for providing DHCP services.

Wherein, each tenant establishes one or more virtual networks, each virtual network corresponds to a virtual machine, each virtual machine is connected to a virtual machine switch, and an independent VLAN tag is set at the connection.

Wherein, each virtual network is configured with a virtual DHCP service, and an IP address range is set.

Wherein, the dnsmasq process is arranged in a namespace, each virtual network corresponds to a namespace, and all dnsmasq processes corresponding to a virtual DHCP use the same Listen IP.

Wherein, the namespace is connected to the virtual machine switch through a port pair, and a VLAN tag corresponding to the virtual network is set at the connection of each namespace.

Wherein, the system further includes: a second virtual switch connected to the virtual switch, the second virtual switch is used to set prohibition of sending DHCP messages from the host, and this setting is performed separately for each virtual machine;

The DHCP service on each host allows the use of the same Listen IP address.

Wherein, the method for providing DHCP service based on the above-mentioned system includes:

The network control node receives the request to establish a virtual DHCP service, and sends the request to the agent program on each host;

The agent program is responsible for establishing the command space, starting dnsmasq in it, and establishing the port pair of the virtual switch;

Correspondingly connecting the namespace, the virtual machine and the first virtual switch respectively, and marking the connection with a VLAN tag.

The device and method proposed in this application can avoid waste of address resources, realize DHCP flow isolation, and support multi-user operations.

Description of drawings

FIG. 1 is a schematic diagram of an architecture of a device for providing a distributed virtual DHCP service according to an embodiment of the present invention.

detailed description

The specific implementation manners of the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. The following examples are used to illustrate the present invention, but are not intended to limit the scope of the present invention.

Fig. 1 shows a block diagram of a cloud computing multi-tenant-oriented distributed virtual DHCP service providing system according to an embodiment of the present invention. As shown in Fig. 1, the system generally includes: a plurality of tenants, and each tenant corresponds to one or more The virtual machines adapted to their respective virtual networks are connected to a virtual switch, each virtual network corresponds to a namespace via the virtual switch, and each namespace starts a dnsmasq process responsible for providing DHCP services.

Among them, as shown in Figure 1, there are two hosts shown in the figure, and each host has two tenants, including tenant A and tenant B. Among them, tenant A has built two virtual networks, and tenant B has built a virtual network. . Wherein, a virtual machine is established in each virtual network. In order to allow each virtual machine to obtain an IP through the DHCP service, a virtual DHCP service is configured on the virtual network, and an IP address range is set.

Wherein, the virtual machine is connected to the virtual machine switch, and a VLAN tag is set at the connection. For example, a VLAN 100 tag is set on the port connecting virtual machine 1 to virtual machine switch 1, a VLAN 200 tag is set on the port connecting virtual machine 2 to virtual machine switch 1, and a VLAN is set on the port connecting virtual machine 3 to virtual machine switch 1 300 tabs.

In addition, in order to distinguish the DHCP service of each virtual network, the system establishes multiple namespaces, starts the dnsmasq process in the namespace, each virtual network corresponds to a namespace, and starts a dnsmasq process in each namespace to provide DHCP services , which allows IP addresses between different dnsmasq to overlap. Among them, the reason why the dnsmasq process on each host can use the same Listen IP is: on the virtual machine switch at the exit of the host, the outflow of DHCP packets is restricted, and the virtual machine or dnsmasq on each host will not receive dhcp message. The dhcp message is not intercepted by a specific program. The dnsmasq process is only responsible for responding to the dhcp message (following the normal processing process of DHCP). The interception work is performed by the flow rules set on the virtual machine switch.

Among them, these namespaces are connected to the virtual machine switch 1 through the port pair, and the VLAN tag corresponding to the virtual network is marked, for example, the VLAN 100 tag is set on the namespace port corresponding to the virtual network 1, corresponding to the VLAN 200 tags are set on ports in the namespace, and VLAN 300 tags are set on ports in the namespace corresponding to virtual network 3 . In this way, the DHCP traffic can be isolated from each other, and at the same time, it can communicate with the virtual machines on its own network.

According to the above situation, the same system as that in Figure 1 is deployed on each host, except that the connected virtual machines may be different.

In addition, a virtual switch 2 connected to the virtual switch 1 is arranged on each host at the same time, and a rule for prohibiting sending of DHCP packets from the host is set on the virtual switch 2 . The rules are set individually for each virtual machine so that other virtual machines are not affected, since customers may want to use an external DHCP service, both internal and external DHCP services are supported. Since the internal DHCP traffic will not leave the host, the DHCP service on each host can use the same Listen IP address, that is to say, the entire distributed DHCP service only uses one IP address in the entire network segment as the listening address.

In the application process of the system, the network control node receives the request to establish a virtual DHCP service, and the network control program will send this task to the agent program on each host, and the agent program is responsible for establishing the command space. Start dnsmasq inside, and establish a port pair, connect the namespace to the virtual switch, and put a VLAN tag on the connection. Wherein, the Flow rule established on the virtual switch 2 is set in the virtual switch 2 through the agent program when the virtual machine is established.

It can be seen that this application uses the DHCP message inside the host to intercept, instead of using the traditional DHCP message request process, for example, the outflow of the DHCP message from the host is restricted on the host egress virtual switch. One virtual machine network in this application corresponds to one DHCP service, instead of corresponding to multiple DHCP services on the host as traditionally. This application can support multiple tenants, each tenant corresponds to a virtual network, and the corresponding DHCP address segment is independent.

According to the second embodiment of the present application, a distributed virtual DHCP service provision method for cloud computing multi-tenant is provided, the method includes: the network control node receives a request for establishing a virtual DHCP service, and sends the request to each The agent program on the host; the agent program is responsible for establishing the command space, starting dnsmasq in it, and establishing the port pair of the virtual switch, respectively connecting the namespace, the virtual machine and the first virtual switch, and marking the connection with VLAN Label.

In addition, a second virtual switch is arranged, which is set individually for each virtual machine, and DHCP packets are prohibited from being sent from the host. This will not affect other virtual machines, and since customers may want to use an external DHCP service, both internal and external DHCP services are supported. Since the internal DHCP traffic will not leave the host, the DHCP service on each host can use the same Listen IP address, that is to say, the entire distributed DHCP service only uses one IP address in the entire network segment as the listening address.

Among them, multiple tenants, each tenant corresponds to one or more virtual machines adapted to their respective virtual networks, the multiple virtual machines are connected to a virtual switch, each virtual network corresponds to a namespace via a virtual switch, and each named The space starts a dnsmasq process responsible for providing DHCP services.

Among them, a virtual machine is established in each virtual network. In order to allow each virtual machine to obtain an IP through the DHCP service, a virtual DHCP service is configured on the virtual network, and an IP address range is set.

Wherein, the virtual machine is connected to the virtual machine switch, and a VLAN tag is set at the connection. For example, a VLAN 100 tag is set on the port connecting virtual machine 1 to virtual machine switch 1, a VLAN 200 tag is set on the port connecting virtual machine 2 to virtual machine switch 1, and a VLAN is set on the port connecting virtual machine 3 to virtual machine switch 1 300 tabs.

In addition, in order to distinguish the DHCP service of each virtual network, the system establishes multiple namespaces, starts the dnsmasq process in the namespace, each virtual network corresponds to a namespace, and starts a dnsmasq process in each namespace to provide DHCP services , which allows IP addresses between different DHCPs to overlap.

Among them, these namespaces are connected to the virtual machine switch 1 through the port pair, and the VLAN tag corresponding to the virtual network is marked, for example, the VLAN 100 tag is set on the namespace port corresponding to the virtual network 1, corresponding to the VLAN 200 tags are set on ports in the namespace, and VLAN 300 tags are set on ports in the namespace corresponding to virtual network 3 . In this way, the DHCP traffic can be isolated from each other, and at the same time, it can communicate with the virtual machines on its own network.

Finally, the method of the present application is only a preferred embodiment, and is not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (7)

1. A distributed virtual DHCP service providing system, characterized in that it includes: one or more tenants, each tenant corresponds to one or more virtual machines adapted to their respective virtual networks, and the multiple virtual machines are connected to a A virtual switch, each virtual network corresponds to a namespace via a virtual switch, and each namespace starts a dnsmasq process responsible for providing DHCP services. 2. The system according to claim 2, wherein each tenant establishes one or more virtual networks, each virtual network corresponds to a virtual machine, each virtual machine is connected to a virtual machine switch, and in Set independent VLAN tags at the connection. 3. The system according to claim 1, wherein each virtual network is configured with a virtual DHCP service and an IP address range is set. 4. The system according to claim 1, wherein the dnsmasq process is arranged in a namespace, each virtual network corresponds to a namespace, and all dnsmasq processes corresponding to a virtual DHCP use the same ListenIP. 5. The system according to claim 1, wherein the namespace is connected to the virtual machine switch through a port pair, and a VLAN tag corresponding to the virtual network is set at the connection of each namespace. 6. The system according to claim 1, wherein the system further comprises: a second virtual switch connected to the virtual switch, the second virtual switch is configured to prohibit sending of DHCP messages from the host, the Settings are made individually for each virtual machine; The DHCP service on each host allows the use of the same Listen IP address. 7. A method for providing DHCP services based on the system of claims 1-6, characterized in that, comprising: The network control node receives the request to establish a virtual DHCP service, and sends the request to the agent program on each host; The agent program is responsible for establishing the command space, starting dnsmasq in it, and establishing the port pair of the virtual switch; Correspondingly connecting the namespace, the virtual machine and the first virtual switch respectively, and marking the connection with a VLAN tag.