Network deployment method, device, equipment and computer-readable storage medium

Abstract

The present invention discloses a network deployment method, apparatus, device and computer-readable storage medium, which are applied to the field of computer technology, including: obtaining virtual machines and bare metal of a cloud infrastructure platform, and containerized application bare metal of a container orchestration platform; the containerized application bare metal is the bare metal in which the container orchestration platform is deployed; the switch port mode of the virtual machine and the port mode of the containerized application bare metal are set to multi-virtual local area network port mode, and the switch port mode of the bare metal is set to single virtual local area network port mode; and the networks of the virtual machine, bare metal and containerized application bare metal configured with port modes are interconnected based on virtual private cloud subnet information. The present invention configures the containerized application bare metal integrated with the container orchestration platform, as well as the ports of the virtual machine and the bare metal, so that the cloud infrastructure platform and the container orchestration platform can access the same virtual private cloud network, thereby achieving network interconnection.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a network deployment method, apparatus, device, and computer-readable storage medium. Background Art

[0002] OpenStack (a cloud infrastructure platform) and Kubernetes (an open-source container orchestration platform) are currently mainstream cloud application management solutions. OpenStack is used for managing virtual machines and bare metal, while Kubernetes is used for managing containers. Cloud platforms typically incorporate both OpenStack and Kubernetes. Network interoperability between OpenStack and Kubernetes is crucial. Services hosted by OpenStack virtual machines and implemented by Kubernetes need to call each other, but network interoperability between OpenStack and Kubernetes is currently not possible.

[0003] It can be seen that how to achieve network interoperability between Openstack and Kubernetes is a technical problem that technical personnel in this field urgently need to solve. Summary of the Invention

[0004] In view of this, the object of the present invention is to provide a network deployment method, apparatus, device and computer-readable storage medium to solve the technical problem in the prior art that Openstack and Kubernetes cannot communicate with each other.

[0005] To solve the above technical problems, the present invention provides a network deployment method, comprising:

[0006] Obtain virtual machines and bare metal of the cloud infrastructure platform, as well as containerized application bare metal of the container orchestration platform; wherein the bare metal is a physical server without an operating system configured, and the containerized application bare metal is bare metal on which the container orchestration platform is deployed through the cloud platform;

[0007] Setting the switch port mode of the virtual machine to a multi-virtual LAN port mode, setting the switch port mode of the bare metal to a single virtual LAN port mode, and setting the port mode of the containerized application bare metal to a multi-virtual LAN port mode;

[0008] The virtual private cloud subnet information is obtained, and based on the virtual private cloud subnet information, the network of the virtual machine configured with the port mode, the bare metal, and the containerized application bare metal are interconnected.

[0009] On the one hand, the obtaining of virtual private cloud subnet information and interconnecting the virtual machine configured with the port mode, the bare metal, and the containerized application bare metal network based on the virtual private cloud subnet information include:

[0010] When it is determined that the virtual private cloud subnet information is a set virtual private cloud port, determining to add a tag of the set virtual private cloud port to the network virtualization message to obtain a tagged network virtualization message;

[0011] When it is determined that the tagged network virtualization message is sent to the virtual machine of the cloud infrastructure platform, based on the tagged network virtualization message, the switch port corresponding to the virtual machine is changed to be consistent with the set virtual private cloud port;

[0012] When it is determined that the tagged network virtualization message is sent to the bare metal of the cloud infrastructure platform, based on the tagged network virtualization message, the switch port corresponding to the bare metal is changed to be consistent with the set virtual private cloud port; after the tagged network virtualization message passes through the switch port corresponding to the bare metal, the tag is automatically removed and then enters the bare metal;

[0013] When it is determined that the tagged network virtualization message is sent to the containerized application bare metal, it is determined that the sub-interface of the service network of the containerized application bare metal is set to be consistent with the set virtual private cloud port, and the tagged network virtualization message is transmitted to the network virtualization unit of the container orchestration platform using the sub-interface of the current service network, and is sent to the container in the containerized application bare metal using the network virtualization unit.

[0014] On the one hand, before obtaining the virtual machines and bare metal of the cloud infrastructure platform and the containerized application bare metal of the container orchestration platform, the following steps are also included:

[0015] Physically connect the cloud platform's business network and management network to the switch, and establish a network connection between the cloud platform and bare metal.

[0016] Determine the service subnet information of the containerized application image and the cloud infrastructure platform, and based on the service subnet information and the memory file system of the cloud infrastructure platform, write the containerized application image to the bare metal and map it to the corresponding hard disk to obtain the containerized application bare metal;

[0017] The containerized application bare metal is started from the hard disk based on the set connection network setting.

[0018] On the one hand, determining the service subnet information of the containerized application image and the cloud infrastructure platform, and writing the containerized application image to the bare metal based on the service subnet information and the memory file system of the cloud infrastructure platform, and mapping it to the corresponding hard disk to obtain the containerized application bare metal, includes:

[0019] Utilizing a bare metal management component in the cloud platform to generate bare metal identifiable network information based on the business subnet information of the cloud infrastructure platform;

[0020] By setting the connection network, the startup mode of the current bare metal node is set to remote startup, and the current bare metal node is restarted and powered on;

[0021] The remotely started bare metal utilizes a switch to obtain the memory file system from the bare metal management component, and powers on the memory file system to mount the remotely started bare metal to the physical node where the bare metal management component is located;

[0022] Using the mounted bare metal management component, the containerized application image and the network information recognizable by the bare metal are written to the bare metal, and mapped to the hard disk of the node where the mounted bare metal management component is located, to obtain the initial containerized application bare metal;

[0023] Using the bare metal management component to set the initial containerized application bare metal to boot from the hard disk through the set network connection, and causing the initial containerized application bare metal to restart and power on;

[0024] The port configuration component is used to perform configuration based on the business subnet information, and the build script is automatically executed to build the initial containerized application bare metal to the cloud infrastructure platform, and the initial containerized application bare metal is connected to the virtual private cloud network to obtain the containerized application bare metal.

[0025] On the one hand, the service subnet information is one or more combinations of the attribute requirements of the sub-interface, the virtual LAN to which the sub-interface belongs, the physical interface to which the sub-interface belongs, the actual physical port information, the network address of the sub-interface, the mask of the sub-interface, and the routing information of the sub-interface.

[0026] On the one hand, after obtaining virtual private cloud subnet information and interconnecting the virtual machine, the bare metal, and the containerized application bare metal configured with the port mode based on the virtual private cloud subnet information, the method further includes:

[0027] The business network address of the containerized bare metal application is configured on the target sub-interface; wherein the network address and network configuration included in the target sub-interface are different from the network addresses and network configurations of other sub-interfaces to achieve logical isolation between different businesses.

[0028] On the one hand, after obtaining virtual private cloud subnet information and interconnecting the virtual machine, the bare metal, and the containerized application bare metal configured with the port mode based on the virtual private cloud subnet information, the method further includes:

[0029] Using a network connectivity test method to test whether the virtual machine of the cloud infrastructure platform and the containerized application container in the containerized application bare metal have received data packets sent by each other;

[0030] If the virtual machine of the cloud infrastructure platform and the containerized application container in the containerized application bare metal can receive data packets sent by each other, then it is determined that the cloud infrastructure platform and the containerized application are successfully interconnected;

[0031] If the virtual machine of the cloud infrastructure platform and the containerized application container in the containerized application bare metal cannot receive data packets sent by each other, it is determined that the interconnection between the cloud infrastructure platform and the containerized application has failed.

[0032] An embodiment of the present invention further provides a network deployment device, including:

[0033] A cloud platform service acquisition module is used to acquire virtual machines and bare metal of the cloud infrastructure platform, as well as containerized application bare metal of the container orchestration platform; wherein the bare metal is a physical server without an operating system configured, and the containerized application bare metal is bare metal on which the container orchestration platform is deployed through the cloud platform;

[0034] a port mode determination module, configured to set the switch port mode of the virtual machine to a multi-virtual LAN port mode, set the switch port mode of the bare metal to a single virtual LAN port mode, and set the port mode of the containerized application bare metal to a multi-virtual LAN port mode;

[0035] The network interconnection module is used to obtain virtual private cloud subnet information and interconnect the networks of the virtual machine, the bare metal, and the containerized application bare metal configured with the port mode based on the virtual private cloud subnet information.

[0036] An embodiment of the present invention further provides a network deployment device, including:

[0037] memory for storing computer programs;

[0038] A processor is used to execute the computer program to implement the steps of the above-mentioned network deployment method.

[0039] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned network deployment method are implemented.

[0040] The present invention also provides a computer program product, comprising a computer program / instruction, which implements the steps of the above-mentioned network deployment method when executed by a processor.

[0041] To solve the above technical problems, an embodiment of the present invention provides a network deployment method, which may include: obtaining virtual machines and bare metal of a cloud infrastructure platform, and containerized application bare metal of a container orchestration platform; wherein, bare metal is a physical server without an operating system configured, and containerized application bare metal is a bare metal on which a container orchestration platform is deployed through a cloud platform; setting the switch port mode of the virtual machine to a multi-virtual LAN port mode, setting the switch port mode of the bare metal to a single virtual LAN port mode, and setting the port mode of the containerized application bare metal to a multi-virtual LAN port mode; obtaining virtual private cloud subnet information, and interconnecting the networks of the virtual machines, bare metal, and containerized application bare metal that have been configured with port modes based on the virtual private cloud subnet information.

[0042] It can be seen from the above technical solution that the beneficial effect of the present invention is that: compared with the current cloud infrastructure platform and containerized applications that cannot interconnect and cannot directly send data packets, the present invention obtains the containerized application bare metal on which the container orchestration platform has been deployed, and configures the ports of the containerized application bare metal and the virtual machines and bare metal of the cloud infrastructure platform, so that the containerized application bare metal of the container orchestration platform can be connected to the virtual private cloud network, thereby interconnecting and communicating with the virtual machines and bare metal of the cloud infrastructure platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present invention, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0044] Figure 1 A flowchart of a network deployment method provided by an embodiment of the present invention;

[0045] Figure 2 A schematic diagram of a bare metal deployment architecture for implementing a container orchestration platform accessing a VPC network, provided in an embodiment of the present invention;

[0046] Figure 3 A schematic diagram of the interconnection between a virtual machine, bare metal, and containerized application bare metal provided in an embodiment of the present invention;

[0047] Figure 4A schematic diagram of the structure of a network deployment device provided by an embodiment of the present invention;

[0048] Figure 5 A schematic diagram of the structure of a network deployment device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0049] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.

[0050] The terms "including" and "having," as used in the present description and accompanying drawings, and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements and may include steps or elements that are not listed.

[0051] In order to enable those skilled in the art to better understand the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0052] Next, a flowchart of a network deployment method provided by an embodiment of the present invention is described in detail. Figure 1 A network deployment method provided in an embodiment of the present invention may include:

[0053] S101, obtain virtual machines and bare metal of the cloud infrastructure platform, and containerized application bare metal of the container orchestration platform; wherein, bare metal is a physical server without an operating system configured, and containerized application bare metal is bare metal on which the container orchestration platform is deployed through the cloud platform.

[0054] This embodiment does not limit the specific execution entity. For example, the execution entity in this embodiment may be a cloud platform; or the execution entity in this embodiment may be a node on the cloud platform. The cloud infrastructure platform in this embodiment is OpenStack, an open source cloud computing management platform project designed to provide an Infrastructure as a Service (IaaS) solution. It is not a single piece of software, but rather consists of multiple core components that work together to manage, schedule, and automate resource pools, thereby providing users with infrastructure services such as computing, storage, and networking. The OpenStack virtual machines in this embodiment are virtual instances in the OpenStack cloud environment. They run on physical servers using virtualization technology to provide computing resources to users. Bare Metal in this embodiment refers to a server, generally used to designate a physical server that does not have an operating system installed, and can be referred to simply as Bare Metal. The container orchestration platform in this embodiment is Kubernetes, an open source platform for managing containerized applications across multiple hosts in a cloud platform. The containerized application bare metal in this embodiment is a bare metal with a container orchestration platform installed. When installing the container orchestration platform, the container orchestration platform image can be used for installation, and related network configuration can be performed so that the containerized application bare metal can communicate with the cloud infrastructure platform.

[0055] It should be further explained that, based on the above embodiment, in order to improve the accuracy of generating containerized application bare metal, before obtaining the virtual machines and bare metal of the cloud infrastructure platform, as well as the containerized application bare metal of the container orchestration platform, the following steps may also be performed: physically connecting the cloud platform's service network and management network to a switch, and establishing a set connection network connection between the cloud platform and the bare metal; determining the service subnet information of the containerized application image and the cloud infrastructure platform, and based on the service subnet information and the cloud infrastructure platform's memory file system, writing the containerized application image to the bare metal and mapping it to the corresponding hard disk to obtain the containerized application bare metal; and setting up the containerized application bare metal to boot from the hard disk based on the set connection network. In this embodiment, the cloud platform's service network is a network used for communication between virtual machines and between virtual machines and computers outside the platform; the cloud platform's management network is a network dedicated to management and control within the cloud platform. The switch in this embodiment is the switch corresponding to the containerized application bare metal. The set connection network in this embodiment can be a BMC network, a technology used to connect different systems and applications to achieve real-time data sharing and integration. The business subnet information in this embodiment includes one or more combinations of the attribute requirements of the sub-interface, the virtual local area network to which the sub-interface belongs, the physical interface to which the sub-interface belongs, the actual physical port information, the network address of the sub-interface, the mask of the sub-interface, and the routing information of the sub-interface. This embodiment establishes a physical connection and sets a connection to the connection network, so that the containerized application bare metal and the cloud platform can communicate through the business network and the set connection network and management network. The business subnet information in this embodiment is information such as the port, IP address, mask, and route that characterizes the business subnet. The memory file system in this embodiment is a file system that simulates the physical memory of a computer as disk space.

[0056] It should be further explained that, based on the above embodiment, in order to improve the accuracy of the bare metal configuration of the containerized application, the above determination of the service subnet information of the containerized application image and the cloud infrastructure platform, and writing the containerized application image to the bare metal based on the service subnet information and the memory file system of the cloud infrastructure platform, and mapping it to the corresponding hard disk to obtain the containerized application bare metal, includes:

[0057] S1: Use the bare metal management component in the cloud platform to generate bare metal identifiable network information based on the business subnet information of the cloud infrastructure platform.

[0058] For easier understanding, please refer to Figure 2 , Figure 2 A schematic diagram of a bare metal deployment architecture for implementing a container orchestration platform to access a VPC network is provided in an embodiment of the present invention. Figure 2As can be seen, the overall architecture includes the cloud platform, switches, and the bare metal disk on which Kubernetes is deployed. The cloud platform includes the ironic-conductor component (bare metal management component), which writes the system image containing the Kubernetes platform installation package and installation script, along with the required configdrive data, to the OpenStack bare metal disk and completes the system image installation. The cloud-init component reads data from configdrive-data to configure subports. The deploy-k8s.sh script completes the Kubernetes platform setup. The k8s-image is the container orchestration platform image. The in-memory file system (IMFS) is a virtual file system that treats computer memory as a disk, simulating a hard disk file system in memory. configdrive-data refers to the data used to configure the bare metal disk within the cloud platform. The genericswitch component is used to control the switch when the ironic-conductor component deploys bare metal on the cloud platform, modifying the port mode and VLAN ID of the port directly connected to the OpenStack bare metal switch. A switch includes both service ports and logical ports. Service ports typically refer to service interfaces provided by a server or system for external use, handling business logic and data interaction. Logical ports are virtual interfaces that enable data exchange but do not physically exist and require configuration. Containerized bare metal applications can include the cloud-init component, configdrive-data, deploy-K8s.sh, and PF sub-interfaces. PF sub-interfaces are logical sub-interfaces in network devices that are further divided based on physical functions (PFs). Before step S1, it is necessary to deploy the cloud platform on the physical node, physically connect the cloud platform node's service network and management network ports to the switch (connecting network cables), and physically connect the OpenStack bare metal node to the switch's service ports. Establish a BMC network connection between the cloud platform node and the OpenStack bare metal node. The cloud platform node can use the BMC to control the OpenStack bare metal node to start, shut down, and configure the startup mode. This configuration ensures physical connectivity between the cloud platform, switch, and OpenStack bare metal node. Deploy the cloud platform on its physical nodes and ensure that the ironic-conductor pod and genericswicth pod services are normal.The cloud platform's front-end interface specifies the Kubernetes image and the service subnet where the OpenStack Bare Metal instance resides. The front-end interface then calls the Ironic API to send the K8s image and the service subnet (corresponding to the service subnet information) to the Ironic-Conductor pod for processing. Step S1: After Ironic-Conductor receives the data, it generates configdrive-data (network information recognizable by Bare Metal) based on the received network information. This requires configuring the network card sub-interface on the OpenStack node. This embodiment does not limit the specific format of the network information recognizable by Bare Metal. For example, the generated configdrive-data is designed in the following format: Links=[{"id":"test","type":"vlan","vlan_id":10,"vlan_link":"tapf00f587e-60","vlan_mac_address":"3c:fd:fe:e1:d1:19"},{"id":"tapf00f587e-60","vif_id":"f00f587e-6001-4322-9527-d6d4c448dd5a ","type":"phy","mtu":1500,"ethernet_mac_address":"3c:fd:fe:el:d1:19"}]; networks=[{"id":"network0","type":"i pv4","link:"test","ip_address":"8.8.8.215","netmask":"255.255.255.0","routes":[],"network_id":"99ce3ce6-a99d 4be1-0629-03clafbcfbfc"}], where the Links link contains two attributes, as shown in the above format. The "id":"test" attribute indicates the attribute requirements of the subinterface, and type: "vlan" indicates that this is a VLAN (virtual local area network) link. vlan_id indicates the VLAN to which the subinterface belongs. vlan_link indicates the physical interface to which the subinterface belongs. The other attribute "id":"tapf00f587e-60" indicates the actual physical port information. vif_id: "f00f587e-6001-4322-9527-d6d4c448dd5a" is the ID of the virtual interface. phy: "phy" indicates that this is a physical interface.mtu: 1500 - Maximum Transmission Unit (MTU), the maximum packet size that the interface can handle. "ethernet_mac_address": "3c:fd:fe:el:d1:19"}; after the operating system is powered on, the port can be found using the MAC address specified by ethernet_mac_address. The Networks (network configuration) property contains the subinterface's IP address, mask, and routing information, such as id: "network0" - a unique identifier for this network. type: "ipv4" - indicates that this is an IPv4 network. "link: "test" configures the subinterface test with the IP address 8.8.8.215 and the mask 255.255.255.0. routes: [] - Routing configuration. An empty array here indicates no additional routing rules. network_id: "99ce3ce6-a99d-4be1-0629-03clafbcfbfc" - a unique identifier for the network.

[0059] S2: Set the startup mode of the current bare metal node to remote startup by setting the connection network, and restart the current bare metal.

[0060] The specific process of this embodiment can be to set the startup mode of the Openstack bare metal node to pxe startup (remote startup) through the BMC network (setting the connection network), and perform a reboot (restart and power on) operation on the Openstack bare metal.

[0061] S3: The remotely started bare metal utilizes a switch to obtain the memory file system from the bare metal management component, and powers on the memory file system to mount the remotely started bare metal to the physical node where the bare metal management component is located.

[0062] The specific process of this embodiment involves restarting and powering on OpenStack Bare Metal, using the PF port through the switch to retrieve the in-memory file system from the ironic-conductor component of the cloud platform. After retrieving the in-memory file system, the power-on operation is performed. After the in-memory file system is powered on, the in-memory file system mounts the OpenStack Bare Metal hard disk to the physical node where the ironic-conductor module resides using ISCSI. ISCSI (Internet Small Computer System Interface) is a protocol that allows SCSI (Small Computer System Interface) commands and data transmission over IP networks.

[0063] S4: Use the mounted bare metal management component to write the containerized application image and bare metal-recognizable network information to the bare metal, and map it to the hard disk of the node where the mounted bare metal management component is located to obtain the initial containerized application bare metal.

[0064] In this embodiment, ironic-conductor (the bare metal management component) writes the Kubernetes image (containerized application image) and configdrive-data (network information recognizable by Bare Metal) files to the OpenStack Bare Metal hard disk mapped to the ironic-conductor node. The ironic-conductor module then completes writing the Kubernetes system disk and configdrive-data files.

[0065] S5: Using the bare metal management component to set the initial containerized application bare metal to start from the hard disk by setting a network connection, and restarting and powering on the initial containerized application bare metal.

[0066] Before step S5, this embodiment can use the ironic-conductor component to link with the generic switch to log in to the switch through the switch management network and configure the switch port directly connected to the Openstack bare metal to trunk mode through the PLUG_PORT_TO_NETWORK command, and transparently transmit all VLANs.

[0067] PLUG_PORT_TO_NETWORK = (

[0068] 'interface {port}' / / Specify the network interface (port) to be configured

[0069] 'switchport mode trunk' / / Configure the specified port as Trunk

[0070] 'switchport trunk vlan allow all') / / Allow the Trunk port to pass traffic from all VLANs

[0071] In this embodiment, after the Openstack bare metal completes writing the ironic-conductor module image, ironic-conductor sets the Openstack bare metal to boot from the hard disk through the BMC network and reboots.

[0072] S6: Use the port configuration component to perform configuration based on the business subnet information, and automatically execute the build script to build the initial containerized application bare metal to the cloud infrastructure platform, connect the initial containerized application bare metal to the virtual private cloud network, and obtain the containerized application bare metal.

[0073] In this example, after the system is powered on, the cloud-init component (the port configuration component) reads the data in configdrive-data to configure the subports. The system then automatically executes the deploy-k8s.sh script to complete the Kubernetes platform setup. This completes the provisioning of a bare metal cloud platform that can be used to connect Kubernetes to a VPC network.

[0074] S102: Set the switch port mode of the virtual machine to multi-virtual LAN port mode, set the bare metal switch port mode to single virtual LAN port mode, and set the containerized application bare metal port mode to multi-virtual LAN port mode.

[0075] The multi-virtual LAN port mode in this embodiment is Trunk VLAN. In Trunk mode, one port can transmit data streams of multiple VLANs and can be connected to multiple VLANs. This mode is mainly used to connect ports between switches. The single virtual LAN port mode in this embodiment is Access VLAN. In Access mode, one port can only belong to one VLAN and it only transmits data streams of a single VLAN, that is, this port can only be connected to one VLAN. It should be noted that when the switch port mode of the virtual machine, the bare metal switch port mode, and the containerized application bare metal port mode have been set to the corresponding mode before configuration, here is just a check to ensure that the port mode is correct.

[0076] S103: Acquire virtual private cloud subnet information, and interconnect the networks of virtual machines, bare metal, and containerized application bare metal configured with port mode based on the virtual private cloud subnet information.

[0077] The virtual private cloud subnet information in this embodiment refers to a subnet of a VPC (virtual private cloud). A VPC is a proprietary network, a user-defined private network on the cloud. This embodiment does not limit the specific virtual private cloud subnet information. For example, the virtual private cloud subnet information in this embodiment can be a VLAN network of VLAN 100; or the virtual private cloud subnet information in this embodiment can be a VLAN network of VLAN 200. This embodiment interconnects the networks of virtual machines, bare metal, and containerized bare metal configured in port mode based on the virtual private cloud subnet information, enabling interoperability among the virtual private cloud networks, thereby enabling communication between virtual machines, bare metal, and containerized bare metal.

[0078] It should be further explained that, based on the above embodiment, obtaining the virtual private cloud subnet information and interconnecting the virtual machines, bare metal, and containerized application bare metal networks configured in port mode based on the virtual private cloud subnet information may include:

[0079] S1031: When it is determined that the virtual private cloud subnet information is to set a virtual private cloud port, it is determined to add a tag of the set virtual private cloud port to the network virtualization message to obtain a tagged network virtualization message.

[0080] S1032: When it is determined that the tagged network virtualization message is sent to the virtual machine of the cloud infrastructure platform, based on the tagged network virtualization message, the switch port corresponding to the virtual machine is changed to be consistent with the set virtual private cloud port.

[0081] In this embodiment, steps S1031 and S1032 indicate that this embodiment is under unified VPC subnet management under the same tenant. Assuming that the subnet is a VLAN network of VLAN 100, the Openstack virtual machine (VM) traffic entering the network virtualization message is tagged with VLAN 100 (corresponding to the sub-interface) and enters the switch through the service network (PF) network card. The switch ingress is configured in Trunk mode to transparently transmit the VLAN 100 message.

[0082] S1033, when it is determined that the tagged network virtualization message is sent to the bare metal of the cloud infrastructure platform, based on the tagged network virtualization message, the switch port corresponding to the bare metal is changed to be consistent with the set virtual private cloud port. When the tagged network virtualization message passes through the switch port corresponding to the bare metal, the tag is automatically removed and then enters the bare metal.

[0083] This embodiment shows that if the message is sent to the bare metal node, after being forwarded by the switch, it will enter the access VLAN port of the switch directly connected to the Openstack bare metal uplink network. Here, the access VLAN is configured as 100. After passing through the port, the VLAN is stripped off and the message directly enters the bare metal node to achieve intercommunication.

[0084] S1034, when it is determined that the tagged network virtualization message is sent to the containerized application bare metal, it is determined that the sub-interface of the service network of the containerized application bare metal is set to be consistent with the set virtual private cloud port, and the tagged network virtualization message is transmitted to the network virtualization unit of the container orchestration platform using the sub-interface of the current service network, and is sent to the container in the containerized application bare metal using the network virtualization unit.

[0085] In this embodiment, if the message is sent to the K8s node of the containerized bare metal application, the cloud platform will create VLAN sub-interface 100 of the service network PF when issuing the bare metal. The traffic will pass through the switch's Trunk VLAN to release the VLAN 100 message and then pass through the service network PF to enter the service network PF sub-interface to achieve traffic interoperability. If it is to enter the K8s container PODS, the traffic will enter the network virtualization module after entering the service network PF, and then the traffic will be sent to the corresponding pod, thereby achieving traffic interoperability. From the perspective of achieving interoperability under the unified VPC, for bare metal used to deploy the K8s container platform, when the cloud platform issues the bare metal, it is necessary to automatically switch the switch port directly connected to the bare metal to Trunk mode and configure Trunk all (allowing the switch port to transmit data from all VLANs (virtual local area networks). This configuration is usually used for connections between switches so that data from different VLANs can be transmitted between these switches). When configuring a bare metal network, you need to configure a subinterface on the bare metal network card that connects to the service network. This subinterface assigns the bare metal's VLAN to the bare metal network card. After completing these steps, you can use a script to launch the Kubernetes container platform and network virtualization module to achieve interoperability among the Kubernetes container networks.

[0086] It should be further explained that in order to reduce the mutual impact between various businesses, after obtaining the virtual private cloud subnet information and interconnecting the networks of the virtual machines, bare metal, and containerized application bare metal configured in port mode based on the virtual private cloud subnet information, it can also include: configuring the business network address of the containerized application bare metal on the target sub-interface; wherein the network address and network configuration included in the target sub-interface are different from the network addresses and network configurations of other sub-interfaces to achieve logical isolation between different businesses. In this embodiment, during the process of issuing bare metal on the cloud platform, the bare metal business network address must fall on the sub-interface of the bare metal business network card for business network isolation.

[0087] It should be further explained that after obtaining the virtual private cloud subnet information and interconnecting the networks of the virtual machines, bare metal, and containerized application bare metal configured with the port mode based on the virtual private cloud subnet information, it can also include: using a network connectivity test method to test whether the virtual machines of the cloud infrastructure platform and the containerized application containers in the containerized application bare metal receive data packets sent by each other; if the virtual machines of the cloud infrastructure platform and the containerized application containers in the containerized application bare metal can receive data packets sent by each other, then it is determined that the cloud infrastructure platform and the containerized application are successfully interconnected; if the virtual machines of the cloud infrastructure platform and the containerized application containers in the containerized application bare metal cannot receive data packets sent by each other, then it is determined that the cloud infrastructure platform and the containerized application have failed to interconnect. This embodiment will detect whether the interconnection is based on the heartbeat to ensure that data packets can be sent normally.

[0088] In order to improve the accuracy of interoperability detection, it is possible to determine whether the networks are interoperable by querying routing information, firewall settings, VPC network configuration, and network monitoring tools; wherein, use commands to obtain routing information of virtual machines, bare metal, and containerized application bare metal, and check whether there are routing entries pointing to each other's networks. If so, it means that the networks between the two are interoperable; check firewall settings to ensure that the firewall rules between Openstack and Kubernetes do not block communication between each other, and ensure that relevant ports and IP addresses are allowed to pass; determine that virtual machines, bare metal, and containerized application bare metal are all in the same VPC network, and determine that the VPC ID, subnet range, and routing rules are consistent; use network monitoring tools to capture and analyze network traffic between virtual machines, bare metal, and containerized application bare metal to determine whether the communication between them is normal and whether there is a network failure. This embodiment uses multiple strategies when determining network interoperability between virtual machines, bare metal, and containerized application bare metal, thereby improving the accuracy of determining interoperability.

[0089] For easier understanding, please refer to Figure 3 , Figure 3 A schematic diagram of the interconnection between a virtual machine, bare metal, and containerized application bare metal provided in an embodiment of the present invention, from Figure 3 As can be seen, the virtual machines of the cloud infrastructure platform, the bare metal of the cloud infrastructure platform, and the cloud infrastructure platform with bare metal containerized applications deployed share a VPC network. The port modes corresponding to the virtual machines, bare metal, and bare metal containerized applications are trunk VLAN, access VLAN, and trunk VLAN, respectively.

[0090] A network deployment method provided by an embodiment of the present invention may include: S101, obtaining virtual machines and bare metal of a cloud infrastructure platform, and containerized application bare metal of a container orchestration platform; wherein the bare metal is a physical server without an operating system configured, and the containerized application bare metal is the bare metal of a container orchestration platform deployed in the bare metal through a cloud platform; S102, setting the switch port mode of the virtual machine to a multi-virtual LAN port mode, setting the switch port mode of the bare metal to a single virtual LAN port mode, and setting the port mode of the containerized application bare metal to a multi-virtual LAN port mode; S103, obtaining virtual private cloud subnet information, and interconnecting the networks of the virtual machines, bare metal, and containerized application bare metal that have been configured with port modes based on the virtual private cloud subnet information. Compared with the current situation where cloud infrastructure platforms and containerized applications cannot interconnect and send data packets directly, the present invention obtains the bare metal of the containerized application on which the container orchestration platform has been deployed, and configures the ports of the bare metal of the containerized application and the virtual machines and bare metal of the cloud infrastructure platform, so that the virtual machines and bare metal of the cloud infrastructure platform can interconnect and communicate with the bare metal of the containerized application of the container orchestration platform.

[0091] Understandably, OpenStack and Kubernetes are currently mainstream cloud application management solutions, used for managing virtual machines, bare metal, and containers, respectively. Cloud platforms typically incorporate both OpenStack and Kubernetes, with both virtual machines and bare metal running on OpenStack's VPC network. OpenStack VPC networking offers rich functionality and has been used by users for a long time. Consider integrating Kubernetes into OpenStack's VPC network to enable virtual machines, bare metal, and Kubernetes containers deployed on bare metal within the cloud platform to share the same OpenStack VPC network, enabling interoperability and improving the competitiveness of cloud platform products.

[0092] The following introduces a network deployment device provided by an embodiment of the present invention. The network deployment device described below and the network deployment method described above can be referenced to each other.

[0093] Figure 4 A schematic structural diagram of a network deployment device provided in an embodiment of the present invention may include:

[0094] The cloud platform service acquisition module 100 is used to acquire virtual machines and bare metal of the cloud infrastructure platform, as well as containerized application bare metal of the container orchestration platform; wherein the bare metal is a physical server without an operating system configured, and the containerized application bare metal is bare metal on which the container orchestration platform is deployed through the cloud platform;

[0095] A port mode determination module 200 is configured to set the switch port mode of the virtual machine to a multi-virtual LAN port mode, set the switch port mode of the bare metal to a single virtual LAN port mode, and set the port mode of the containerized application bare metal to a multi-virtual LAN port mode;

[0096] The network interconnection module 300 is used to obtain virtual private cloud subnet information and interconnect the networks of the virtual machine, the bare metal, and the containerized application bare metal configured with the port mode based on the virtual private cloud subnet information.

[0097] Furthermore, based on the above embodiment, the network interconnection module 300 may include:

[0098] a network virtualization message determining unit, configured to, when determining that the virtual private cloud subnet information is a set virtual private cloud port, determine to add a tag of the set virtual private cloud port to the network virtualization message to obtain a tagged network virtualization message;

[0099] a first port setting unit, configured to, when determining that the tagged network virtualization message is sent to the virtual machine of the cloud infrastructure platform, change the switch port corresponding to the virtual machine to be consistent with the set virtual private cloud port based on the tagged network virtualization message;

[0100] A second port setting unit is configured to, when determining that the tagged network virtualization message is sent to the bare metal of the cloud infrastructure platform, change the switch port corresponding to the bare metal to be consistent with the set virtual private cloud port based on the tagged network virtualization message, and automatically remove the tag after the tagged network virtualization message passes through the switch port corresponding to the bare metal and enters the bare metal;

[0101] The third port setting unit is used to, when determining that the tagged network virtualization message is sent to the containerized application bare metal, determine to set the sub-interface of the service network of the containerized application bare metal to be consistent with the set virtual private cloud port, use the sub-interface of the current service network to transmit the tagged network virtualization message to the network virtualization unit of the container orchestration platform, and use the network virtualization unit to send it to the container in the containerized application bare metal.

[0102] Furthermore, based on any of the above embodiments, the network deployment apparatus may further include:

[0103] The connection network determination module is used to physically connect the business network and management network of the cloud platform to the switch, and to establish a connection network connection between the cloud platform and the bare metal.

[0104] A containerized application image deployment module is configured to determine the service subnet information of the containerized application image and the cloud infrastructure platform, and based on the service subnet information and the memory file system of the cloud infrastructure platform, write the containerized application image to the bare metal and map it to the corresponding hard disk to obtain the containerized application bare metal;

[0105] A startup mode determination module is used to set the containerized application bare metal to start from the hard disk based on the set connection network.

[0106] Furthermore, based on the above embodiment, the containerized application image deployment module may include:

[0107] A bare metal identifiable network information determining unit, configured to generate bare metal identifiable network information based on the service subnet information of the cloud infrastructure platform using a bare metal management component in the cloud platform;

[0108] A bare metal power-on unit, configured to set the startup mode of the current bare metal node to remote startup through the set connection network, and restart and power on the current bare metal;

[0109] A memory file system power-on unit, configured to obtain the memory file system from the bare metal management component using a switch based on the remotely started bare metal, and power on the memory file system to mount the remotely started bare metal to the physical node where the bare metal management component is located;

[0110] Using the mounted bare metal management component, the containerized application image and the network information recognizable by the bare metal are written to the bare metal, and mapped to the hard disk of the node where the mounted bare metal management component is located, to obtain the initial containerized application bare metal;

[0111] a hard disk boot setting unit, configured to use the bare metal management component to set the initial containerized application bare metal to boot from the hard disk through the set network connection, and to restart and power on the initial containerized application bare metal;

[0112] A configuration unit is used to use a port configuration component to perform configuration based on the business subnet information, and automatically execute a build script to build the initial containerized application bare metal to a cloud infrastructure platform, connect the initial containerized application bare metal to a virtual private cloud network, and obtain the containerized application bare metal.

[0113] Further, based on the above embodiment, the business subnet information is one or more combinations of the attribute requirements of the sub-interface, the virtual LAN to which the sub-interface belongs, the physical interface to which the sub-interface belongs, the actual physical port information, the network address of the sub-interface, the mask of the sub-interface, and the routing information of the sub-interface.

[0114] Furthermore, based on any of the above embodiments, the network deployment apparatus may further include:

[0115] A business isolation module is used to configure the business network address of the containerized application bare metal on the target sub-interface; wherein the network address and network configuration included in the target sub-interface are different from the network addresses and network configurations of other sub-interfaces to achieve logical isolation between different businesses.

[0116] Furthermore, based on any of the above embodiments, the network deployment apparatus may further include:

[0117] A testing module, configured to test, using a network connectivity testing method, whether a virtual machine of the cloud infrastructure platform and a containerized application container in the containerized application bare metal container receive data packets sent by the other party;

[0118] an interconnection success determination module, configured to determine that the cloud infrastructure platform and the containerized application are successfully interconnected if the virtual machine of the cloud infrastructure platform and the containerized application container in the containerized application bare metal can receive data packets sent by each other;

[0119] The interconnection failure determination module is used to determine that the interconnection between the cloud infrastructure platform and the containerized application has failed if the virtual machine of the cloud infrastructure platform and the containerized application container in the containerized application bare metal cannot receive data packets sent by each other.

[0120] It should be noted that the order of the modules and units in the above network deployment device can be changed without affecting the logic.

[0121] Figure 4 The description of the features in the corresponding embodiment can be found in Figure 4 The relevant descriptions of the corresponding embodiments will not be repeated here one by one.

[0122] The network deployment device provided by an embodiment of the present invention may include: a cloud platform service acquisition module 100, used to acquire virtual machines and bare metals of a cloud infrastructure platform, and containerized application bare metals of a container orchestration platform; wherein the bare metal is a physical server without an operating system configured, and the containerized application bare metal is a bare metal on which a container orchestration platform is deployed through a cloud platform; a port mode determination module 200, used to set the switch port mode of the virtual machine to a multi-virtual LAN port mode, set the switch port mode of the bare metal to a single virtual LAN port mode, and set the port mode of the containerized application bare metal to a multi-virtual LAN port mode; a network interconnection module 300, used to obtain virtual private cloud subnet information, and interconnect the networks of the virtual machine, the bare metal, and the containerized application bare metal that have been configured with port modes based on the virtual private cloud subnet information. Compared with the current situation where cloud infrastructure platforms and containerized applications cannot interconnect and send data packets directly, the present invention obtains the bare metal of the containerized application on which the container orchestration platform has been deployed, and configures the ports of the bare metal of the containerized application and the virtual machines and bare metal of the cloud infrastructure platform, so that the virtual machines and bare metal of the cloud infrastructure platform can interconnect and communicate with the bare metal of the containerized application of the container orchestration platform.

[0123] A network deployment device provided by an embodiment of the present invention is introduced below. The network deployment device described below and the network deployment method described above can refer to each other.

[0124] Figure 5 A schematic diagram of the structure of a network deployment device provided by an embodiment of the present invention is shown as follows: Figure 5 As shown, the network deployment device includes: a memory 60 for storing computer programs;

[0125] The processor 61 is configured to implement the steps of the network deployment method in the above embodiment when executing a computer program.

[0126] The network deployment device provided in this embodiment may include but is not limited to a smart phone, a tablet computer, a laptop computer, or a desktop computer.

[0127] The processor 61 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 61 may be implemented using at least one of the following hardware forms: a digital signal processing (DSP), a field-programmable gate array (FPGA), or a programmable logic array (PLA). The processor 61 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a central processing unit (CPU); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 61 may be integrated with a graphics processing unit (GPU), which is responsible for rendering and drawing content required to be displayed on the display screen. In some embodiments, the processor 61 may also include an artificial intelligence (AI) processor for handling computational operations related to machine learning.

[0128] The memory 60 may include one or more computer-readable storage media, which may be non-transitory. The memory 60 may also include high-speed random access memory, and non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 60 is at least used to store the following computer program 601, wherein, after the computer program is loaded and executed by the processor 61, it can implement the relevant steps of the network deployment method disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 60 may also include an operating system 602 and data 603, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 602 may include Windows, Unix, Linux, etc. The data 603 may include but is not limited to network deployment data, etc.

[0129] In some embodiments, the network deployment device may further include a display screen 62 , an input / output interface 63 , a communication interface 64 , a power supply 65 , and a communication bus 66 .

[0130] Those skilled in the art will understand that Figure 5 The structure shown in the figure does not constitute a limitation on the network deployment device, and may include more or fewer components than shown in the figure.

[0131] It is understood that if the network deployment method in the above-mentioned embodiment is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the current technology, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and performs all or part of the steps of the various embodiments of the present invention. The aforementioned storage medium includes: a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), an electrically erasable programmable ROM, a register, a hard drive, a removable disk, a CD-ROM, a magnetic disk, or an optical disk, and other media that can store program code.

[0132] Based on this, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned network deployment method are implemented.

[0133] Based on this, an embodiment of the present invention further provides a computer program product, including a computer program / instruction, which implements the steps of the above-mentioned network deployment method when executed by a processor.

[0134] The above describes in detail a network deployment method provided by an embodiment of the present invention. The various embodiments are described in a progressive manner throughout this specification, with each embodiment focusing on its differences from other embodiments. Reference can be made to the descriptions of the embodiments for similar or identical parts. The devices disclosed in the embodiments are described briefly because they correspond to the methods disclosed in the embodiments. For relevant details, refer to the description of the methods.

[0135] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0136] The above is a detailed introduction to a network deployment method, apparatus, device, and computer-readable storage medium provided by the present invention. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core ideas. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present invention, several improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the scope of protection of the claims of the present invention.

Claims

1. A network deployment method, characterized in that: include: Obtain virtual machines and bare metal of the cloud infrastructure platform, as well as containerized application bare metal of the container orchestration platform; wherein the bare metal is a physical server without an operating system configured, and the containerized application bare metal is bare metal on which the container orchestration platform is deployed through the cloud platform; Setting the switch port mode of the virtual machine to a multi-virtual LAN port mode, setting the switch port mode of the bare metal to a single virtual LAN port mode, and setting the port mode of the containerized application bare metal to a multi-virtual LAN port mode; Acquire virtual private cloud subnet information, and interconnect the virtual machine, the bare metal, and the containerized application bare metal configured with the port mode based on the virtual private cloud subnet information; The obtaining of virtual private cloud subnet information and interconnecting the virtual machine configured with the port mode, the bare metal, and the containerized application bare metal network based on the virtual private cloud subnet information include: When it is determined that the virtual private cloud subnet information is a set virtual private cloud port, determining to add a tag of the set virtual private cloud port to the network virtualization message to obtain a tagged network virtualization message; When it is determined that the tagged network virtualization message is sent to the virtual machine of the cloud infrastructure platform, based on the tagged network virtualization message, the switch port corresponding to the virtual machine is changed to be consistent with the set virtual private cloud port; When it is determined that the tagged network virtualization message is sent to the bare metal of the cloud infrastructure platform, based on the tagged network virtualization message, the switch port corresponding to the bare metal is changed to be consistent with the set virtual private cloud port; after the tagged network virtualization message passes through the switch port corresponding to the bare metal, the tag is automatically removed and then enters the bare metal; When it is determined that the tagged network virtualization message is sent to the containerized application bare metal, it is determined that the sub-interface of the service network of the containerized application bare metal is set to be consistent with the set virtual private cloud port, and the tagged network virtualization message is transmitted to the network virtualization unit of the container orchestration platform using the sub-interface of the current service network, and is sent to the container in the containerized application bare metal using the network virtualization unit.

2. The network deployment method according to claim 1, wherein: Before obtaining the virtual machines and bare metal of the cloud infrastructure platform and the bare metal of the containerized application of the container orchestration platform, the following steps are also included: Physically connect the cloud platform's business network and management network to the switch, and establish a network connection between the cloud platform and bare metal. Determine the service subnet information of the containerized application image and the cloud infrastructure platform, and based on the service subnet information and the memory file system of the cloud infrastructure platform, write the containerized application image to the bare metal and map it to the corresponding hard disk to obtain the containerized application bare metal; The containerized application bare metal is started from the hard disk based on the set connection network setting.

3. The network deployment method according to claim 2, wherein: The determining of the service subnet information of the containerized application image and the cloud infrastructure platform, and writing the containerized application image to the bare metal based on the service subnet information and the memory file system of the cloud infrastructure platform, and mapping the image to the corresponding hard disk to obtain the containerized application bare metal, includes: Utilizing a bare metal management component in the cloud platform to generate bare metal identifiable network information based on the business subnet information of the cloud infrastructure platform; By setting the connection network, the startup mode of the current bare metal node is set to remote startup, and the current bare metal node is restarted and powered on; The remotely started bare metal utilizes a switch to obtain the memory file system from the bare metal management component, and powers on the memory file system to mount the remotely started bare metal to the physical node where the bare metal management component is located; Using the mounted bare metal management component, the containerized application image and the network information recognizable by the bare metal are written to the bare metal, and mapped to the hard disk of the node where the mounted bare metal management component is located, to obtain the initial containerized application bare metal; Using the bare metal management component to set the initial containerized application bare metal to start from the hard disk through the set connection network, and causing the initial containerized application bare metal to restart and power on; The port configuration component is used to perform configuration based on the business subnet information, and the build script is automatically executed to build the initial containerized application bare metal to the cloud infrastructure platform, and the initial containerized application bare metal is connected to the virtual private cloud network to obtain the containerized application bare metal.

4. The network deployment method according to claim 2, wherein: The service subnet information is one or more combinations of the attribute requirements of the sub-interface, the virtual local area network to which the sub-interface belongs, the physical interface to which the sub-interface belongs, the actual physical port information, the network address of the sub-interface, the mask of the sub-interface, and the routing information of the sub-interface.

5. The network deployment method according to claim 1, wherein: After obtaining virtual private cloud subnet information and interconnecting the virtual machine configured with the port mode, the bare metal, and the containerized application bare metal network based on the virtual private cloud subnet information, the method further includes: The business network address of the containerized bare metal application is configured on the target sub-interface; wherein the network address and network configuration included in the target sub-interface are different from the network addresses and network configurations of other sub-interfaces to achieve logical isolation between different businesses.

6. The network deployment method according to claim 1, wherein: After obtaining virtual private cloud subnet information and interconnecting the virtual machine configured with the port mode, the bare metal, and the containerized application bare metal network based on the virtual private cloud subnet information, the method further includes: Using a network connectivity test method to test whether the virtual machine of the cloud infrastructure platform and the containerized application container in the containerized application bare metal have received data packets sent by each other; If the virtual machine of the cloud infrastructure platform and the containerized application container in the containerized application bare metal can receive data packets sent by each other, then it is determined that the cloud infrastructure platform and the containerized application are successfully interconnected; If the virtual machine of the cloud infrastructure platform and the containerized application container in the containerized application bare metal cannot receive data packets sent by each other, it is determined that the interconnection between the cloud infrastructure platform and the containerized application has failed.

7. A network deployment device, characterized in that: include: A cloud platform service acquisition module is used to acquire virtual machines and bare metal of the cloud infrastructure platform, as well as containerized application bare metal of the container orchestration platform; wherein the bare metal is a physical server without an operating system configured, and the containerized application bare metal is bare metal on which the container orchestration platform is deployed through the cloud platform; a port mode determination module, configured to set the switch port mode of the virtual machine to a multi-virtual LAN port mode, set the switch port mode of the bare metal to a single virtual LAN port mode, and set the port mode of the containerized application bare metal to a multi-virtual LAN port mode; A network interconnection module is used to obtain virtual private cloud subnet information and interconnect the networks of the virtual machine configured with the port mode, the bare metal, and the containerized application bare metal based on the virtual private cloud subnet information; Among them, the network interconnection module includes: a network virtualization message determining unit, configured to, when determining that the virtual private cloud subnet information is a set virtual private cloud port, determine to add a tag of the set virtual private cloud port to the network virtualization message to obtain a tagged network virtualization message; a first port setting unit, configured to, when determining that the tagged network virtualization message is sent to the virtual machine of the cloud infrastructure platform, change the switch port corresponding to the virtual machine to be consistent with the set virtual private cloud port based on the tagged network virtualization message; A second port setting unit is configured to, when determining that the tagged network virtualization message is sent to the bare metal of the cloud infrastructure platform, change the switch port corresponding to the bare metal to be consistent with the set virtual private cloud port based on the tagged network virtualization message, and automatically remove the tag after the tagged network virtualization message passes through the switch port corresponding to the bare metal and enters the bare metal; The third port setting unit is used to, when determining that the tagged network virtualization message is sent to the containerized application bare metal, determine to set the sub-interface of the service network of the containerized application bare metal to be consistent with the set virtual private cloud port, use the sub-interface of the current service network to transmit the tagged network virtualization message to the network virtualization unit of the container orchestration platform, and use the network virtualization unit to send it to the container in the containerized application bare metal.

8. A network deployment device, characterized in that: include: memory for storing computer programs; A processor, configured to execute the computer program to implement the steps of the network deployment method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the network deployment method according to any one of claims 1 to 6.

Images