Method for managing virtual machine network cards of different product types in cloud computing platform

Abstract

The invention particularly relates to a virtual machine network card management method for different product types in a cloud computing platform. The method for managing the virtual machine network cards of different product types in the cloud computing platform comprises the following steps: creating a virtual machine private network, a cloud server and a cloud physical host, calling an interface of an elastic network card module, creating and binding an elastic network card, storing information of the elastic network card, and setting a network card type. Creating an auxiliary network card, selecting a security group, filling description information, and binding the created auxiliary network card to a corresponding cloud server or a cloud physical host; and configuring an access rule for the security group associated with the elastic network card, and performing security filtering on the access flow of the cloud physical host. According to the method for managing the virtual machine network cards of different product types in the cloud computing platform, the operation is simple and rapid, the security is high, the flexibility is strong, the method does not depend on a certain independent physical hardware device, the virtual machine network cards of different product types do not influence each other, and the security of virtual machine communication data is ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of cloud computing, and in particular to a method for managing virtual machine network cards of different product types in a cloud computing platform. Background Art

[0002] Currently, various industries are gradually beginning to integrate their business systems through cloud computing platforms. For security reasons, VPC technology can be used for secure isolation on the network.

[0003] VPC stands for Virtual Private Cloud. VPC technology allows tenants to have an area in the cloud that is logically isolated from other tenants and use various cloud resources in this area. Tenants can fully control the virtual network on the cloud.

[0004] At present, the management of virtual machine network cards of different product types in computing platforms faces difficulties and problems in network isolation and interoperability, performance optimization, security assurance, cost control, and management complexity. In order to solve these problems, the present invention proposes a management method for virtual machine network cards of different product types in a cloud computing platform. Summary of the invention

[0005] In order to overcome the defects of the prior art, the present invention provides a simple and efficient method for managing virtual machine network cards of different product types in a cloud computing platform.

[0006] The present invention is achieved through the following technical solutions:

[0007] A method for managing virtual machine network cards of different product types in a cloud computing platform comprises the following steps:

[0008] Step S1: Create a virtual machine private network

[0009] The tenant logs in to the console system and creates a private network for the virtual machine. The steps to create a private network, namely the VxLAN network, are as follows:

[0010] Step S1.1, fill in the name of the virtual private network, select the network segment CIDR to be created, the network segment CIDR includes three network segments: 192.168.0.0 / 16, 172.16.0.0 / 12 and 10.0.0.0 / 8;

[0011] Step S1.2, fill in the subnet information, including subnet name, subnet CIDR and subnet DNS; if you do not fill in the subnet DNS, the default DNS configuration information will be used;

[0012] When creating a virtual machine private network, you can create three subnets at the same time. After the virtual machine private network is successfully created, the network ID and name, network segment CIDR, number of subnets, number of routing tables and creation time are displayed on the interface;

[0013] Step S1.3, construct a virtual private network subnet list to display the subnet ID and name, network segment CIDR, network to which it belongs, number of available IPs, total number of IPs, number of routing tables, and creation time;

[0014] Step S2: Create a cloud physical host and primary network card

[0015] The tenant logs in to the console, configures the basic information of the cloud server, network and security group information, and system information, and submits the order after confirming that everything is correct;

[0016] When creating a cloud server, call the interface of the elastic network card module, create an elastic network card and bind it to the cloud server, store the elastic network card information, and set the network card type to the cloud server, that is, ecs;

[0017] When creating a cloud physical host, call the interface of the elastic network card module, create an elastic network card and bind it to the cloud physical host, store the elastic network card information, and since the host type is a cloud physical host, set the network card type to cloud physical host, that is, cps;

[0018] Build an ENI list to display the stored ENI information;

[0019] In step S2, the basic information includes the region, available zone, architecture, specifications, image and disk to be created;

[0020] The network and security group information includes virtual private network, subnet and security group information, wherein the subnet is selected from the virtual private network subnet list;

[0021] System information includes login method, password and confirmation method, cloud server name, and the number of cloud servers to be created.

[0022] Step S3: Create an auxiliary network card

[0023] The tenant logs in to the console and views the ENI list information, including the ENI ID and name, ENI type, virtual private network to which the ENI belongs, subnet to which the ENI belongs, primary intranet IP, status, bound instance type, and bound instance.

[0024] Create a secondary network card, configure the network card name, select the virtual private network and subnet, fill in the primary intranet IP, select the security group, fill in the description information, and bind the created secondary network card to the corresponding cloud server or cloud physical host;

[0025] In step S3, when viewing the elastic network card list, the network card query filter condition is the product type type;

[0026] In the ENI list, enter type=server to filter and display NIs whose type is empty, ecs, or cps.

[0027] After the auxiliary network card is successfully created, it is bound to the intranet resources. The intranet resource type is cloud server or cloud physical host. The corresponding cloud server list is displayed according to the selected resource type. Select the cloud server to bind the network card and update the binding status of the auxiliary network card to Bound.

[0028] Step S4: Associate security groups

[0029] The tenant logs in to the console, views the details of the ENIC according to the auxiliary network card ID, and associates the security group to view the security group information bound to the ENIC, including the security group ID, name, and description. By configuring ingress and egress rules for the security group associated with the ENIC, the ingress and egress traffic of the cloud physical host can be securely filtered.

[0030] In step S4, the ENI must be associated with at least one security group, and the security group details and the ENI information bound to it are viewed according to the security group ID;

[0031] When you cancel the association between an ENI and a security group, if the ENI is bound to only one security group, a message will pop up saying that the security group cancellation has failed. Otherwise, the association between the ENI and the corresponding security group is canceled, and the security group list interface will no longer display the security group.

[0032] In step S4, the tenant logs in to the console to view the security group list information and security group details;

[0033] The security group list information includes the security group ID, name, associated cloud server, whether it is the default security group, and description;

[0034] View the list of associated cloud servers through the Associate Cloud Server menu. The list information includes cloud server ID, name, status and IP address. The IP address includes intranet IP and Internet IP.

[0035] View the list of associated cloud physical hosts through the Associate Cloud Physical Host menu. The list information includes the cloud physical host ID, name, status, and IP address. The IP address includes the intranet IP and the extranet IP.

[0036] When the number of security groups bound to a cloud server or cloud physical host exceeds 5, a prompt message is issued; the binding relationship with the security group is released for the corresponding cloud server or cloud physical host, the associated cloud server list or associated cloud physical host list is updated, and the corresponding cloud server or cloud physical host is deleted.

[0037] A virtual machine network card management system for different product types in a cloud computing platform, including a northbound interface module, a database module, a cloud server management module and an elastic network card management module;

[0038] The northbound interface module is used to provide a REST API to the outside world, so as to provide tenants with the functions of creating networks, creating cloud servers, and creating and binding elastic network cards;

[0039] The database module is used to store relevant tenants, virtual private networks, subnets, security groups, security group rules, elastic network cards and elastic public IP information; all relevant information established by tenants through the cloud server management module and the elastic network card management module is stored in the database module;

[0040] The cloud server management module is used to manage cloud servers, including creating cloud servers, creating cloud physical hosts, viewing cloud server lists, deleting cloud servers, modifying cloud server names, changing the network to which cloud servers belong, updating the security group bound to cloud servers, binding cloud servers to elastic public IPs, and unbinding cloud servers from elastic public IPs;

[0041] When the cloud server management module creates a cloud server, it calls the interface of the elastic network card management module, creates an elastic network card and binds it to the cloud server, stores the elastic network card information, and the network card type is a cloud server, i.e., ecs;

[0042] When the cloud server management module creates a cloud physical host, it calls the elastic network card management interface and determines that the host type is a cloud physical host. Then the network card type is a cloud physical host, that is, cps;

[0043] Cloud servers and cloud servers belong to different menus and have independent functions. The cloud server list displays the primary network card information, including the network and subnet to which it belongs, and the intranet IP. The cloud server details page displays all associated network cards, including the primary network card and auxiliary network cards. Click the network card ID to jump to the elastic network card details interface to view the specific network card information.

[0044] The elastic network card management module is used to manage elastic network cards, including querying the elastic network card list, viewing elastic network card details, creating elastic network cards, deleting elastic network cards, updating elastic network card names, binding elastic public network cards to elastic public network IPs, unbinding elastic public network cards from elastic network cards, viewing elastic network card associated security groups, elastic network card associated security groups, and elastic network card unassociated security groups;

[0045] Among them, the elastic network card includes the primary network card and the auxiliary network card. The primary network card is created along with the cloud server or cloud physical host.

[0046] The elastic network card management module displays the network card information of cloud servers and cloud physical hosts through the elastic network card list, and other cloud server network cards are not displayed for the time being;

[0047] The elastic network card management module encapsulates elastic network card association and disassociation with security groups into common APIs, and returns different prompt information according to product types. The prompt information includes the product type, which is convenient for later maintenance and development of customized requirements.

[0048] A virtual machine network card management device for different product types in a cloud computing platform, characterized in that it includes a memory and a processor; the memory is used to store a computer program, and the processor is used to implement the above method steps when executing the computer program.

[0049] A readable storage medium, characterized in that: a computer program is stored on the readable storage medium, and the computer program implements the above method steps when executed by a processor.

[0050] The beneficial effects of the present invention are: the management method of virtual machine network cards of different product types in the cloud computing platform is simple and fast to operate, highly secure, and highly flexible, and does not rely on a single physical hardware device. Virtual machine network cards of different product types do not affect each other, thereby ensuring the security of virtual machine communication data. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0052] Attached Figure 1 It is a schematic diagram of the method for managing virtual machine network cards of different product types in the cloud computing platform of the present invention.

[0053] Attached Figure 2 The present invention is a schematic diagram of the architecture for implementing virtual machine network card management for different product types in the cloud computing platform.

[0054] Attached Figure 3 The figure is a schematic diagram of the management principle of virtual machine network cards of different product types in the cloud computing platform of the present invention. DETAILED DESCRIPTION

[0055] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0056] Elastic Network Interface (ENI) is a virtual network card that can be bound to a VPC (virtual private cloud) type ECS (Elastic Compute Service) instance. With elastic network cards, high-availability cluster construction, low-cost failover, and refined network management can be achieved. Elastic network cards are independent virtual network cards that can be migrated between multiple cloud servers to achieve flexible expansion and migration of services. Elastic network cards can be created with ECS instances and bound to cloud servers, or auxiliary elastic network cards can be created separately and then bound to ECS instances. By managing virtual machine network cards of different product types, after the cloud server is successfully created, the network card information is stored according to the cloud server type, such as the cloud server network card type is ecs, the cloud physical host network card type is cps, etc. The network card type is the product type, which ensures the consistency of the cloud server and network card type. For virtual machine network cards of different product types, the virtual machine network cards do not affect each other. By configuring entry and exit rules for the security group associated with the network card, the inbound and outbound traffic of the cloud server is securely filtered, ensuring the security of the virtual machine communication data and realizing the network card management of the virtual machine, including creation, deletion, modification, and query.

[0057] The method for managing virtual machine network cards of different product types in the cloud computing platform includes the following steps:

[0058] Step S1: Create a virtual machine private network

[0059] The tenant logs in to the console system and creates a private network for the virtual machine. The classic network, namely the VLAN network, needs to be created with the administrator's permissions. The steps to create a private network, namely the VxLAN network, are as follows:

[0060] Step S1.1, fill in the name of the virtual private network, select the network segment CIDR (Classless Inter-Domain Routing) to be created, the network segment CIDR includes three network segments: 192.168.0.0 / 16, 172.16.0.0 / 12 and 10.0.0.0 / 8;

[0061] Step S1.2, fill in the subnet information, including subnet name, subnet CIDR and subnet DNS (Domain Name System); if you do not fill in the subnet DNS, the default DNS configuration information will be used;

[0062] When creating a virtual machine private network, you can create three subnets at the same time. After the virtual machine private network is successfully created, the network ID and name, network segment CIDR, number of subnets, number of routing tables and creation time are displayed on the interface;

[0063] Step S1.3, construct a virtual private network subnet list to display the subnet ID and name, network segment CIDR, network to which it belongs, number of available IPs, total number of IPs, number of routing tables, and creation time;

[0064] Click the subnet number and the interface jumps to the subnet list interface corresponding to the virtual private network.

[0065] Step S2: Create a cloud physical host and primary network card

[0066] The tenant logs in to the console, configures the basic information of the cloud server, network and security group information, and system information, and submits the order after confirming that everything is correct;

[0067] When creating a cloud server, call the interface of the elastic network card module, create an elastic network card and bind it to the cloud server, store the elastic network card information, and set the network card type to the cloud server, that is, ecs;

[0068] When creating a cloud physical host, call the interface of the elastic network card module, create an elastic network card and bind it to the cloud physical host, store the elastic network card information, and determine that the host type is a cloud physical host based on the host type. Then set the network card type to cloud physical host, that is, cps;

[0069] Build an ENI list to display the stored ENI information;

[0070] In step S2, the basic information includes the region, available zone, architecture, specifications, image and disk to be created;

[0071] The network and security group information includes virtual private network, subnet and security group information, wherein the subnet is selected from the virtual private network subnet list;

[0072] System information includes login method, password and confirmation method, cloud server name, and the number of cloud servers to be created.

[0073] Step S3: Create an auxiliary network card

[0074] The tenant logs in to the console and views the ENI list information, including the ENI ID and name, ENI type, virtual private network to which the ENI belongs, subnet to which the ENI belongs, primary intranet IP, status, bound instance type, and bound instance.

[0075] Create a secondary network card, configure the network card name, select the virtual private network and subnet, fill in the primary intranet IP, select the security group, fill in the description information, and bind the created secondary network card to the corresponding cloud server or cloud physical host;

[0076] In step S3, when checking the elastic network card list, the network card query filter condition is the product type. Since the network card type field was not planned before, after adding the network card type, the network card default value was not set, resulting in the type field being empty;

[0077] In the elastic network card list, enter type=server to filter and display network cards with type empty, ecs, or cps. Cloud server and cloud physical host network cards are displayed normally. Network cards of other product types do not need to be displayed on the product interface. They only have storage functions and do not provide operation functions on the interface.

[0078] After the auxiliary network card is successfully created, it is bound to the intranet resources. The intranet resource type is cloud server or cloud physical host. The corresponding cloud server list is displayed according to the selected resource type. Obtaining the cloud server list belongs to different product APIs. The front end needs to determine the API address and parameters to be called according to the resource type, select the cloud server from the drop-down list, call the OpenStack4j interface to bind the network card to the cloud server, and update the binding status of the auxiliary network card to bound.

[0079] Step S4: Associate security groups

[0080] The tenant logs in to the console, views the details of the ENIC according to the auxiliary network card ID, and associates the security group to view the security group information bound to the ENIC, including the security group ID, name, and description. By configuring ingress and egress rules for the security group associated with the ENIC, the ingress and egress traffic of the cloud physical host can be securely filtered.

[0081] In step S4, the ENI must be associated with at least one security group, and the security group details and the ENI information bound to it are viewed according to the security group ID;

[0082] When you cancel the association between an ENI and a security group, if the ENI is bound to only one security group, a message will pop up saying that the security group cancellation has failed. Otherwise, the association between the ENI and the corresponding security group is canceled, and the security group list interface will no longer display the security group.

[0083] Click Associate ENIC. A list of auxiliary NICs to be bound is displayed in the drop-down box. Select an ENIC and click OK. In the Associate ENIC interface, you can see that the NIC and the security group are successfully bound. To associate the primary NIC with the security group, go to the ENIC details interface or the cloud server interface.

[0084] Click Cancel association in the operation bar on the right side of the ENI. You will be prompted to confirm whether you want to cancel the association between the ENI "testeni" and the security group "test-sg". After clicking Confirm, the association between the security group and the ENI is canceled.

[0085] In step S4, the tenant logs in to the console to view the security group list information and security group details;

[0086] The security group list information includes the security group ID, name, associated cloud server, whether it is the default security group, and description;

[0087] View the list of associated cloud servers through the Associate Cloud Server menu. The list information includes cloud server ID, name, status and IP address. The IP address includes intranet IP and Internet IP.

[0088] View the list of associated cloud physical hosts through the Associate Cloud Physical Host menu. The list information includes the cloud physical host ID, name, status, and IP address. The IP address includes the intranet IP and the extranet IP.

[0089] When the number of security groups bound to a cloud server or cloud physical host exceeds 5, a prompt message will be issued, which will be "failed to associate with cloud server. A cloud server can be associated with a maximum of 5 security groups" or "failed to associate with cloud physical host. A cloud physical host can be associated with a maximum of 5 security groups".

[0090] The corresponding cloud server or cloud physical host is unbound from the security group, the associated cloud server list or the associated cloud physical host list is updated, and the corresponding cloud server or cloud physical host is deleted.

[0091] The virtual machine network card management system of different product types in the cloud computing platform includes northbound interface module, database module, cloud server management module and elastic network card management module;

[0092] The northbound interface module is used to provide a REST API (Representational State Transfer Application Programming Interface) to the outside world to provide tenants with the functions of creating networks, creating cloud servers, and creating and binding elastic network cards; for example, providing tenant ID, network segment CIDR, and region to create networks, create subnets, delete subnets, delete virtual private networks, create elastic network cards, delete elastic network cards, bind elastic network cards to cloud servers, unbind elastic network cards from cloud servers, associate elastic network cards with security groups, and cancel elastic network card association with security groups.

[0093] The database module is used to store relevant tenants, virtual private networks, subnets, security groups, security group rules, elastic network cards and elastic public IP information; all relevant information established by tenants through the cloud server management module and the elastic network card management module is stored in the database module;

[0094] The cloud server management module is used to manage cloud servers, including creating cloud servers, creating cloud physical hosts, viewing cloud server lists, deleting cloud servers, modifying cloud server names, changing the network to which cloud servers belong, updating the security group bound to cloud servers, binding cloud servers to elastic public IPs, and unbinding cloud servers from elastic public IPs;

[0095] When the cloud server management module creates a cloud server, it calls the interface of the elastic network card management module, creates an elastic network card and binds it to the cloud server, stores the elastic network card information, and the network card type is a cloud server, i.e., ecs;

[0096] When the cloud server management module creates a cloud physical host, it calls the elastic network card management interface and determines that the host type is a cloud physical host. Then the network card type is a cloud physical host, that is, cps;

[0097] Cloud servers and cloud servers belong to different menus and have independent functions. The cloud server list displays the primary network card information, including the network and subnet to which it belongs, and the intranet IP. The cloud server details page displays all associated network cards, including the primary network card and auxiliary network cards. Click the network card ID to jump to the elastic network card details interface to view the specific network card information.

[0098] The elastic network card management module is used to manage elastic network cards, including querying the elastic network card list, viewing elastic network card details, creating elastic network cards, deleting elastic network cards, updating elastic network card names, binding elastic public network cards to elastic public network IPs, unbinding elastic public network cards from elastic network cards, viewing elastic network card associated security groups, elastic network card associated security groups, and elastic network card unassociated security groups;

[0099] Among them, the elastic network card includes the primary network card and the secondary network card. The primary network card is created along with the cloud server or cloud physical host.

[0100] The elastic network card management module displays the network card information of cloud servers and cloud physical hosts through the elastic network card list, and other cloud server network cards are not displayed for the time being;

[0101] The elastic network card management module encapsulates elastic network card association and disassociation with security groups into common APIs, and returns different prompt information according to product types. The prompt information includes the product type, which is convenient for later maintenance and development of customized requirements.

[0102] The virtual machine network card management device of different product types in the cloud computing platform includes a memory and a processor; the memory is used to store a computer program, and the processor is used to implement the above method steps when executing the computer program.

[0103] The readable storage medium stores a computer program, and when the computer program is executed by a processor, the above method steps are implemented.

[0104] The method for managing virtual machine network cards of different product types in the cloud computing platform selects the network and subnet on the cloud server management platform to create a virtual machine, and calls the interface of the elastic network card management module to create an elastic network card under the network and bind the cloud server. After the cloud server is successfully created, the network card information is stored according to the cloud server type, such as the cloud server network card type is ecs, the cloud physical host network card type is cps, etc. The network card type is the product type, which ensures the consistency of the cloud server and the network card type. For virtual machine network cards of different product types configured, the virtual machine network cards do not affect each other. By configuring entry and exit rules for the security group associated with the network card, the inbound and outbound traffic of the cloud server is securely filtered, which ensures the security of the virtual machine communication data and realizes the network card management of the virtual machine, including creation, deletion, modification, and query.

[0105] The embodiment described above is only one specific implementation of the present invention. Common changes and substitutions made by those skilled in the art within the scope of the technical solution of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for managing virtual machine network cards of different product types in a cloud computing platform, characterized by: The following steps are involved: Step S1: Create a virtual machine private network The tenant logs in to the console system and creates a private network for the virtual machine. The steps to create a private network, namely the VxLAN network, are as follows: Step S1.1, fill in the name of the virtual private network, select the network segment CIDR to be created, the network segment CIDR includes three network segments: 192.168.0.0 / 16, 172.16.0.0 / 12 and 10.0.0.0 / 8; Step S1.2, fill in the subnet information, including subnet name, subnet CIDR and subnet DNS; if you do not fill in the subnet DNS, the default DNS configuration information will be used; When creating a virtual machine private network, you can create three subnets at the same time. After the virtual machine private network is successfully created, the network ID and name, network segment CIDR, number of subnets, number of routing tables and creation time are displayed on the interface; Step S1.3, construct a virtual private network subnet list to display the subnet ID and name, network segment CIDR, network to which it belongs, number of available IPs, total number of IPs, number of routing tables, and creation time; Step S2: Create a cloud physical host and primary network card The tenant logs in to the console, configures the basic information of the cloud server, network and security group information, and system information, and submits the order after confirming that everything is correct; When creating a cloud server, call the interface of the elastic network card module, create an elastic network card and bind it to the cloud server, store the elastic network card information, and set the network card type to the cloud server, that is, ecs; When creating a cloud physical host, call the interface of the elastic network card module, create an elastic network card and bind it to the cloud physical host, store the elastic network card information, and since the host type is a cloud physical host, set the network card type to cloud physical host, that is, cps; Build an ENI list to display the stored ENI information; Step S3: Create an auxiliary network card The tenant logs in to the console and views the ENI list information, including the ENI ID and name, ENI type, virtual private network to which the ENI belongs, subnet to which the ENI belongs, primary intranet IP, status, bound instance type, and bound instance. Create a secondary network card, configure the network card name, select the virtual private network and subnet, fill in the primary intranet IP, select the security group, fill in the description information, and bind the created secondary network card to the corresponding cloud server or cloud physical host; Step S4: Associate security groups The tenant logs in to the console, views the details of the ENIC according to the auxiliary ENIC ID, and associates the security group to view the security group information bound to the ENIC, including the security group ID, name, and description. By configuring inbound and outbound rules for the security group associated with the ENI, you can perform security filtering on the inbound and outbound traffic of the cloud physical host.

2. The method for managing virtual machine network cards of different product types in a cloud computing platform according to claim 1, characterized in that: In step S2, the basic information includes the region, available zone, architecture, specifications, image and disk to be created; The network and security group information includes virtual private network, subnet and security group information, wherein the subnet is selected from the virtual private network subnet list; System information includes login method, password and confirmation method, cloud server name, and the number of cloud servers to be created.

3. The method for managing virtual machine network cards of different product types in a cloud computing platform according to claim 1, characterized in that: In step S3, when viewing the elastic network card list, the network card query filter condition is the product type type; In the ENI list, enter type=server to filter and display NIs whose type is empty, ecs, or cps. After the auxiliary network card is successfully created, it is bound to the intranet resources. The intranet resource type is cloud server or cloud physical host. The corresponding cloud server list is displayed according to the selected resource type. Select the cloud server to bind the network card and update the binding status of the auxiliary network card to Bound.

4. The method for managing virtual machine network cards of different product types in a cloud computing platform according to claim 1, characterized in that: In step S4, the ENI must be associated with at least one security group, and the security group details and the ENI information bound to it are viewed according to the security group ID; When you cancel the association between an ENI and a security group, if the ENI is bound to only one security group, a message will pop up saying that the security group cancellation has failed. Otherwise, the association between the ENI and the corresponding security group is canceled, and the security group list interface will no longer display the security group.

5. The method for managing virtual machine network cards of different product types in a cloud computing platform according to claim 1, characterized in that: In step S4, the tenant logs in to the console to view the security group list information and security group details; The security group list information includes the security group ID, name, associated cloud server, whether it is the default security group, and description; View the list of associated cloud servers through the Associate Cloud Server menu. The list information includes cloud server ID, name, status and IP address. The IP address includes intranet IP and Internet IP. View the list of associated cloud physical hosts through the Associate Cloud Physical Host menu. The list information includes the cloud physical host ID, name, status, and IP address. The IP address includes the intranet IP and the extranet IP. When the number of security groups bound to a cloud server or cloud physical host exceeds 5, a prompt message is issued; the binding relationship with the security group is released for the corresponding cloud server or cloud physical host, the associated cloud server list or associated cloud physical host list is updated, and the corresponding cloud server or cloud physical host is deleted.

6. A virtual machine network card management system for different product types in a cloud computing platform, characterized by: Includes northbound interface module, database module, cloud server management module and elastic network card management module; The northbound interface module is used to provide a REST API to the outside world, so as to provide tenants with the functions of creating networks, creating cloud servers, and creating and binding elastic network cards; The database module is used to store relevant tenants, virtual private networks, subnets, security groups, security group rules, elastic network cards and elastic public IP information; All relevant information established by tenants through the cloud server management module and the elastic network card management module is stored in the database module; The cloud server management module is used to manage cloud servers, including creating cloud servers, creating cloud physical hosts, viewing cloud server lists, deleting cloud servers, modifying cloud server names, changing the network to which cloud servers belong, updating the security group bound to cloud servers, binding cloud servers to elastic public IPs, and unbinding cloud servers from elastic public IPs; The elastic network card management module is used to manage elastic network cards, including querying the elastic network card list, viewing elastic network card details, creating elastic network cards, deleting elastic network cards, updating elastic network card names, binding elastic public network cards to elastic public network IPs, unbinding elastic public network cards from elastic network cards, viewing elastic network card associated security groups, elastic network card associated security groups, and elastic network card unassociated security groups; Among them, the elastic network card includes the primary network card and the auxiliary network card. The primary network card is created along with the cloud server or cloud physical host.

7. The virtual machine network card management system of different product types in the cloud computing platform according to claim 6, characterized in that: When the cloud server management module creates a cloud server, it calls the interface of the elastic network card management module, creates an elastic network card and binds it to the cloud server, stores the elastic network card information, and the network card type is a cloud server, i.e., ecs; When the cloud server management module creates a cloud physical host, it calls the elastic network card management interface and determines that the host type is a cloud physical host. Then, the network card type is a cloud physical host, namely, cps. The cloud server management module manages the cloud server and cloud server through separate menus.

8. The virtual machine network card management system of different product types in the cloud computing platform according to claim 6, characterized in that: The elastic network card management module displays the network card information of cloud servers and cloud physical hosts through the elastic network card list, and other cloud server network cards are not displayed for the time being; The elastic network card management module encapsulates elastic network card association and disassociation with security groups into common APIs, and returns different prompt information according to product types. The prompt information includes the product type, which is convenient for later maintenance and development of customized requirements.

9. A virtual machine network card management device for different product types in a cloud computing platform, characterized by: The method comprises a memory and a processor; the memory is used to store a computer program, and the processor is used to implement the method according to any one of claims 1 to 5 when executing the computer program.

10. A readable storage medium, characterized in that: The readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images