Bare metal node capacity expansion and instance deployment method and device in multi-tenant scene, equipment and medium

Abstract

The invention discloses a bare metal node capacity expansion and instance deployment method and device in a multi-tenant scene, equipment and a medium, and relates to the technical field of computers. Comprising the steps of deploying a basic environment of an open stack cloud platform; adjusting the code of the bare metal component and a related configuration file, and restarting a bare metal service and a bare metal inspector service after the adjustment is completed, so that the bare metal component supports a preset fast channel deployment mode; and based on the deployment network, executing an expansion operation of a bare metal node by using the preset fast channel deployment mode to obtain an expansion node, and based on the tenant network, executing a deployment operation of a bare metal instance on the expansion node by using the preset fast channel deployment mode to complete deployment of the bare metal instance. Therefore, minute-level expansion and instance deployment of bare metal nodes isolated by a multi-tenant network can be realized on the premise of ensuring network security.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, device, and medium for scaling up bare metal nodes and deploying instances in a multi-tenant scenario. Background Technology

[0002] Against the backdrop of the rapid development of cloud-native technologies and Infrastructure as a Service (IaaS), OpenStack, as a mainstream open-source cloud platform, has been widely used in the management of virtualization and bare metal resources. Among these, the bare metal service (Ironic) provides users with the ability to directly manipulate physical servers, suitable for high-performance computing, security isolation, and scenarios with specific hardware dependencies. When a cloud physical host goes live, it needs to complete two main steps: bare metal node expansion and instance deployment. During the node expansion phase, the Ironic Inspector automatically detects node hardware information and cleans up the system disk, making the node available. During the instance deployment phase, Ironic installs the tenant's operating system onto the node, making the node active.

[0003] However, in existing technologies, bare metal node expansion involves two node restarts: one for hardware information self-check and the other for system disk cleanup. Instance deployment also involves two restarts: one for writing the operating system image to the RAM disk and the other for booting the tenant operating system. Since each bare metal node restart requires performing low-level operations such as Basic Input / Output System (BIOS) initialization and hardware detection, each restart is significantly time-consuming, resulting in an average overall expansion time of 15–20 minutes and an average instance deployment time of 10–15 minutes. This is far higher than the 1–2 minute deployment efficiency of virtual machine instances, severely restricting the agility and usability of bare metal services.

[0004] To optimize the above process, the OpenStack community introduced the Fast-Track deployment mode. By configuring `fast_track = true` in the Ironic configuration file (ironic.conf) and meeting conditions such as image startup, continuous node operation, and Ironic Python Agent (IPA) heartbeat maintenance, it achieves only one restart during node scaling and instance deployment, halving the operation time. However, the Fast-Track mode provided by the community is based on a flat network architecture design and does not consider the actual need for isolation between the provisioning network and the tenant network in multi-tenant scenarios. In production environments, to ensure security, the provisioning network (used for hardware self-testing, system disk cleanup, and image writing) must be isolated from the tenant network (used for tenant operating system operation). This is typically achieved using technologies such as Virtual Local Area Network (VLAN) or Virtual Extensible Local Area Network (VxLAN) to implement network segmentation. The community solution removes the deployment network after cleaning up the system disk, causing Ironic to lose communication with the still-running Ironic Python Agent. A reboot is ultimately required to remount the deployment network, rendering Fast-Track ineffective. Therefore, the existing Fast-Track mode has serious flaws in multi-tenant scenarios, failing to balance efficiency and security, thus limiting its practical application in production environments.

[0005] As can be seen from the above, how to achieve minute-level scaling and instance deployment of bare metal nodes with multi-tenant network isolation while ensuring network security is an urgent problem to be solved. Summary of the Invention

[0006] In view of this, the purpose of this invention is to provide a method, apparatus, device, and medium for bare metal node expansion and instance deployment in a multi-tenant scenario, which can achieve minute-level expansion and instance deployment of bare metal nodes in a multi-tenant network isolated environment while ensuring network security. The specific solution is as follows:

[0007] Firstly, this application provides a method for scaling up bare metal nodes and deploying instances in a multi-tenant scenario, including:

[0008] The basic environment for deploying the OpenStack Cloud Platform includes computing components that provide computing services, bare metal components that provide bare metal services, network components that provide network services, image components that provide image services, and authentication components that provide authentication services. The network components are used to interact with physical switches by enabling general switch plugins to provide mutually isolated deployment networks and tenant networks.

[0009] The code and related configuration files of the bare metal component are adjusted, and the bare metal service and bare metal inspector service are restarted after the adjustment is completed so that the bare metal component supports the preset fast channel deployment mode; the bare metal inspector service is used to automatically detect the hardware information of bare metal nodes.

[0010] Based on the deployment network, the bare metal node is expanded using the preset fast channel deployment mode to obtain expanded nodes. Based on the tenant network, the bare metal instance is deployed on the expanded nodes using the preset fast channel deployment mode to complete the deployment of the bare metal instance.

[0011] Optionally, the adjustment of the code and related configuration files of the bare metal component includes:

[0012] Adjust the fast channel parameters in the configuration file of the bare metal component and ensure that the bare metal instance and the bare metal node meet the preset conditions; the preset conditions are that the bare metal instance is in mirror boot mode and the automatic cleanup configuration item is enabled, the power of the bare metal node is on, and the node driver internal information includes a proxy Uniform Resource Locator and a heartbeat signal that has not timed out.

[0013] The parameter for not losing power after self-test in the configuration file of the bare metal inspector is adjusted; the bare metal inspector is used to provide the bare metal inspector service.

[0014] Modify the code logic of the bare metal component so that after the system disk cleanup operation is completed using the preset fast channel deployment mode, the deployment network port is retained, and port remnants are eliminated according to the preset port management policy; the preset port management policy is a policy to eliminate port remnants according to subsequent operations.

[0015] Optionally, eliminating port remnants according to a preset port management policy includes:

[0016] If the subsequent operation is to perform the system disk cleanup operation again, the bare metal component deletes all existing deployed network ports of the current node before creating a new deployment network port, and updates the cleanup virtual interface identifier in the network component corresponding to this cleanup operation.

[0017] If the subsequent operation is to deploy a bare metal instance, the bare metal component removes the residual cleanup virtual interface identifier corresponding to the previous cleanup operation from the current node's internal information;

[0018] The cleanup virtual interface identifier is used to uniquely identify a deployment network port created and used by the bare metal component for the cleanup operation within the network component.

[0019] Optionally, the bare metal component removes the residual cleanup virtual interface identifier corresponding to the previous cleanup operation from the current node's internal information, including:

[0020] The bare metal component performs a removal and cleanup network operation during the environment preparation phase to remove the cleanup virtual interface identifiers that remain in the current node's internal information and correspond to the previous cleanup operation.

[0021] Optionally, restarting the bare metal service and bare metal inspector service after the adjustment is completed includes:

[0022] For non-containerized deployment environments, upgrade the binary packages of the bare metal service and bare metal inspector service and restart the corresponding service processes;

[0023] For containerized deployment environments, replace the images of the bare metal service and bare metal inspector service and restart the corresponding container groups.

[0024] Optionally, the step of performing a bare-metal node expansion operation based on the deployment network and using the preset fast channel deployment mode to obtain expanded nodes includes:

[0025] Based on the deployed network, the access switch information of the bare metal node is configured in the network component using the preset fast channel deployment mode, and the intelligent platform management interface authentication information of the bare metal node is obtained. Based on the access switch information, the access port of the bare metal node is set as the virtual local area network corresponding to the deployed network on the physical switch.

[0026] Register a bare metal node according to the authentication information of the intelligent platform management interface, and initiate a self-test request to the bare metal inspector service so that the bare metal inspector service can start the memory disk environment based on the self-test request, detect the hardware information of the bare metal node, and configure the bare metal node based on the detection results;

[0027] The bare metal component performs a system disk cleanup operation on the bare metal node and changes the state of the bare metal node to an available state to obtain an expanded node.

[0028] Optionally, the step of deploying bare metal instances on the expansion node using the preset fast channel deployment mode based on the tenant network to complete the deployment of bare metal instances includes:

[0029] Based on the tenant network, bare metal instances are created using the preset fast channel deployment mode according to the pre-set tenant operating system image, network configuration and instance specifications, and the bare metal instances are scheduled to the expansion node using the computing component;

[0030] The bare metal component is used to call the proxy service running on the expansion node to write the tenant operating system image to the system disk of the expansion node and restart the expansion node to make the expansion node active, thereby completing the deployment of the bare metal instance.

[0031] Secondly, this application provides a bare metal node expansion and instance deployment device in a multi-tenant scenario, including:

[0032] The environment deployment module is used to deploy the basic environment of the OpenStack Cloud Platform. The basic environment includes computing components that provide computing services, bare metal components that provide bare metal services, network components that provide network services, image components that provide image services, and authentication components that provide authentication services. The network components are used to enable interaction with physical switches by enabling general switch plugins, so as to provide mutually isolated deployment networks and tenant networks.

[0033] The service adjustment module is used to adjust the code and related configuration files of the bare metal component, and restart the bare metal service and bare metal inspector service after the adjustment is completed, so that the bare metal component can support the preset fast channel deployment mode; the bare metal inspector service is used to automatically detect the hardware information of the bare metal node.

[0034] The operation execution module is used to perform a bare metal node expansion operation based on the deployment network and using the preset fast channel deployment mode to obtain an expansion node, and to perform a bare metal instance deployment operation on the expansion node based on the tenant network and using the preset fast channel deployment mode to complete the deployment of the bare metal instance.

[0035] Thirdly, this application provides an electronic device, comprising:

[0036] Memory, used to store computer programs;

[0037] A processor is used to execute the computer program to implement the aforementioned method for scaling up bare metal nodes and deploying instances in a multi-tenant scenario.

[0038] Fourthly, this application provides a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the aforementioned method for expanding bare metal nodes and deploying instances in a multi-tenant scenario.

[0039] This application provides a method for bare metal node expansion and instance deployment in a multi-tenant scenario. First, the basic environment of an open stack cloud platform is deployed. This basic environment includes a computing component providing computing services, a bare metal component providing bare metal services, a network component providing network services, an image component providing image services, and an authentication component providing authentication services. The network component is used to interact with physical switches by enabling a general switch plugin, providing isolated deployment networks and tenant networks. The code and related configuration files of the bare metal component are adjusted, and the bare metal service and bare metal inspector service are restarted after adjustment to enable the bare metal component to support a preset fast-channel deployment mode. The bare metal inspector service is used to automatically detect the hardware information of bare metal nodes. Based on the deployment network, the bare metal node expansion operation is performed using the preset fast-channel deployment mode to obtain expanded nodes. Then, based on the tenant network, the bare metal instance deployment operation is performed on the expanded nodes using the preset fast-channel deployment mode to complete the bare metal instance deployment.

[0040] As can be seen from the above, this application creatively solves the core deficiency of the community version's default fast-channel deployment mode, which cannot support multi-tenant network isolation scenarios, by systematically adjusting the code logic and configuration of the bare metal service component in the OpenStack Cloud Platform. This enables the bare metal service component to stably run in fast-channel mode while ensuring strict isolation between the deployment network and the tenant network. The scaling up and instance deployment of bare metal nodes require only one node restart, reducing the overall operation time to half that of traditional methods, significantly improving resource delivery efficiency and agility. Thus, it is possible to achieve minute-level scaling up and instance deployment of bare metal nodes in multi-tenant network isolation while ensuring network security. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0042] Figure 1 This application discloses a flowchart of a method for scaling up and deploying bare metal nodes in a multi-tenant scenario.

[0043] Figure 2 This is a schematic diagram of a bare metal node expansion and instance deployment device in a multi-tenant scenario disclosed in this application;

[0044] Figure 3 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0045] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0046] In existing technologies, bare metal node expansion involves two node restarts: one for hardware information self-checking and the other for system disk cleanup. Instance deployment also involves two restarts: one for writing the operating system image to the memory disk and the other for booting the tenant operating system. Because each bare metal node restart requires performing low-level operations such as basic input / output system initialization and hardware detection, each restart is significantly time-consuming, resulting in an average overall expansion time of 15–20 minutes and an average instance deployment time of 10–15 minutes. This is far higher than the 1–2 minute deployment efficiency of virtual machine instances, severely restricting the agility and usability of bare metal services.

[0047] To optimize the above process, the OpenStack community introduced a Fast Track deployment mode. By configuring `fast_track = true` in the Ironic configuration file and meeting conditions such as image startup, continuous node operation, and Ironic Python Agent (IPA) heartbeat maintenance, it achieves a single restart during node scaling and instance deployment, halving the operation time. However, the Fast-Track mode provided by the community is based on a flat network architecture design and does not consider the actual needs of network deployment and tenant network isolation in multi-tenant scenarios. In production environments, to ensure security, the deployment network (used for hardware self-testing, system disk cleanup, and image writing) must be isolated from the tenant network (used for running the tenant's operating system). This is typically achieved using virtual LANs (VLANs) or virtual scalable LANs (VSLs). Community solutions remove the deployment network after system disk cleanup, causing Ironic to lose communication with the still-running Ironic Python Agent. A reboot is ultimately required to remount the deployment network, rendering Fast-Track ineffective. Therefore, the existing Fast-Track model has serious flaws in multi-tenant scenarios, failing to balance efficiency and security, thus limiting its practical application in production environments. To address this, this application provides a bare-metal node scaling and instance deployment solution for multi-tenant scenarios, enabling minute-level scaling and instance deployment of bare-metal nodes with multi-tenant network isolation while ensuring network security.

[0048] See Figure 1 As shown in the figure, this application discloses a method for scaling up bare metal nodes and deploying instances in a multi-tenant scenario, including:

[0049] Step S11: Deploy the basic environment of the OpenStack cloud platform.

[0050] In this embodiment, the open stack supports multiple deployment methods, allowing users to choose different tools and solutions based on usage scenarios and needs. For example, for personal development and testing scenarios, deployment can be done manually or using development stack tools. For enterprise production environments, deployment can be done using containers, automated operations and maintenance, and open stack tools. The basic environment includes, but is not limited to, computing components providing computing services, bare metal components providing bare metal services, network components providing network services, image components providing image services, and authentication components providing authentication services. The network component enables interaction with physical switches by enabling a general-purpose switch plugin, providing isolated deployment networks and tenant networks. The computing component interfaces with the bare metal service driver, resulting in cloud physical hosts. The authentication component provides authentication services, ensuring the availability and security of the bare metal service application programming interface. The image component provides memory disk deployment images and tenant operating system images for the cloud physical hosts.

[0051] Step S12: Adjust the code and related configuration files of the bare metal component, and restart the bare metal service and bare metal inspector service after the adjustment is completed so that the bare metal component supports the preset fast channel deployment mode.

[0052] In this embodiment, the OpenStack community introduced the Fast-Track method for the bare metal node scaling and instance deployment process. This ensures that each node only needs to be restarted once during scaling and instance deployment, thereby reducing the scaling and deployment time by half. It's important to note that for the instance deployment process, the Fast-Track parameter needs to be configured to true in the bare metal service configuration file, and the following condition must also be met: the bare metal instance must be booted from an image rather than a volume. This is because volume booting uses Fibre Channel or Internet Small Computer System Interface (ISSI) protocols to mount the volume and directly pre-boot the execution environment into the operating system contained in the system volume; the instance deployment process is different. The common approach is to boot the cloud physical host from an image, which involves writing the image to the server's local disk and then booting the bare metal server from the local disk. The node is powered on, meaning it remains powered on even after scaling up or deleting instances. Furthermore, the node driver's internal information attributes include a Uniform Resource Locator (URI) for the proxy service, i.e., the listening address of the bare metal Python proxy service. The bare metal service can use this URI to call the bare metal Python proxy service to interact with it. This means that after scaling up or deleting instances, redeploying the instance can directly call the bare metal Python proxy service to write the system disk image. It's also important to note that the node driver's internal information attribute package... The heartbeat time includes the last heartbeat time of the agent, and the heartbeat time does not exceed the system-configured fast channel timeout (default 5 minutes). Otherwise, the bare metal Python agent service's heartbeat is considered disconnected, and the bare metal service cannot directly call the bare metal Python agent service. Deployment still requires two restarts, which applies to the memory disk startup as disk writing the tenant operating system image and tenant operating system startup. In addition, to ensure that the memory disk is always running before the bare metal instance is deployed, the automatic cleanup configuration item needs to be enabled. This means that after deleting the instance, automatic cleanup will be performed, and the cleanup will start the memory disk, thus providing a foundation for the bare metal Python agent service to keep running and ensuring that the next instance deployment can enter the fast channel logic. Specifically, the adjustment of the code and related configuration files of the bare metal component can include: adjusting the fast channel parameters in the configuration file of the bare metal component, and ensuring that the bare metal instance and the bare metal node meet the preset conditions. The preset conditions are that the bare metal instance is in image startup mode, the automatic cleanup configuration item is enabled, the bare metal node is powered on, and the node driver internal information includes the agent's Uniform Resource Locator and the heartbeat signal that has not expired.

[0053] Furthermore, regarding the bare metal node expansion process, two restarts are used for node hardware information self-check and system disk cleanup operations, respectively. To ensure that only one restart occurs during the bare metal expansion cycle, node restarts must be avoided during system disk cleanup. First, the shutdown parameter needs to be set to false in the checker configuration file, thus preventing the node from shutting down after the node hardware information self-check. Then, after the checker self-check is completed, the already started memory disk environment can send heartbeat signals to the bare metal management service, which can then be used for automatic cleanup. The bare metal Python agent service is required to be able to identify manageable and available states when performing node discovery, thereby allowing the agent service to discover available bare metal nodes after node expansion. The system bootloader configuration file contains the agent application programming interface address parameter, allowing the agent service to send heartbeats to the bare metal service based on the address in this parameter after self-check, completing the interaction between the agent service and the bare metal service. Finally, during the system disk cleanup operation, the bare metal service can directly call the running agent service to complete the cleanup operation. Specifically, adjusting the code and related configuration files of the bare metal component may include: adjusting the self-test non-power-down parameter in the bare metal inspector's configuration file; the bare metal inspector is used to provide the bare metal inspector service; the bare metal inspector service is used to automatically detect the hardware information of the bare metal node; modifying the code logic of the bare metal component so as to retain the deployment network port after completing the system disk cleanup operation using the preset fast channel deployment mode, and eliminate port remnants according to the preset port management policy; the preset port management policy is a policy to eliminate port remnants according to subsequent operations.

[0054] It's important to note that the community-provided fast-track deployment method has flaws. It doesn't support multi-tenant scenarios, lacks practical usability, and the lack of isolation between the deployment network and tenant networks poses security risks. Therefore, considering multi-tenant scenarios where the deployment network and tenant networks are isolated, after completing the system disk cleanup operation, in fast-track deployment mode, the ports of the deployment network must not be cleared. To address the potential for port remnants, two scenarios can be considered. First, if system disk cleanup is performed again afterward, a new deployment network port will be created. However, the code logic will delete all old deployment network ports before creating the new one and updating the cleanup virtual interface port identifier information for the bare metal port. In this scenario, no port remnants will occur. Second, if other operations are performed after system disk cleanup, such as deploying a bare metal instance, the deployment network port will be added. When adding a port, although the old deployed network port is cleared first, residual cleanup virtual interface port identifiers remain in the internal information of the bare metal port. This causes the network component to fail when updating the Dynamic Host Configuration Protocol (DHCP) options for the port, specifically, an error occurs when updating DHCP during the preparation phase for the memory disk boot environment. The reason is that when updating DHCP, the node's current internal information is retrieved. If a cleanup virtual interface port identifier remains, the system will configure DHCP according to that identifier. However, this virtual interface port was deleted when the network port was added, thus causing the error. To address this, the residual cleanup virtual interface port identifier information needs to be cleared. Specifically, the step of eliminating port remnants according to a preset port management strategy may include: if the subsequent operation is to perform a system disk cleanup operation again, the bare metal component deletes all existing deployed network ports of the current node before creating a new deployment network port, and updates the cleanup virtual interface identifier in the network component corresponding to this cleanup operation; if the subsequent operation is to perform a bare metal instance deployment operation, the bare metal component clears the residual cleanup virtual interface identifier corresponding to the previous cleanup operation from the internal information of the current node; wherein, the cleanup virtual interface identifier is used to uniquely identify a deployment network port created and used by the bare metal component for the cleanup operation in the network component.

[0055] It's worth noting that ports need to be cleaned up before deploying instances. This port cleanup can be performed during the preparation phase. This is because the community performs a process of unconfiguring tenant networks during the preparation phase for rebuild scenarios; therefore, this approach can be replicated by performing a network removal and cleanup operation. Specifically, the bare metal component clearing the residual cleanup virtual interface identifiers corresponding to the previous cleanup operation from the current node's internal information can include: the bare metal component performing a network removal and cleanup operation during the deployment environment preparation phase to clear the residual cleanup virtual interface identifiers corresponding to the previous cleanup operation from the current node's internal information.

[0056] Furthermore, the changes to the bare metal service and bare metal inspector service are updated and restarted to ensure the previous code and configuration modifications take effect. Specifically, restarting the bare metal service and bare metal inspector service after adjustments can include: for non-containerized deployment environments, upgrading the binary packages of the bare metal service and bare metal inspector service and restarting the corresponding service processes; for containerized deployment environments, replacing the images of the bare metal service and bare metal inspector service and restarting the corresponding container groups. In other words, by upgrading service components or replacing container images and restarting the services, the modifications to the code and configuration files in the previous step take effect in the actual runtime environment, thereby ensuring that the improved fast-track deployment mode can be normally enabled and stably run in different deployment environments (including traditional and containerized environments).

[0057] Step S13: Based on the deployment network, perform a bare metal node expansion operation using the preset fast channel deployment mode to obtain an expansion node, and based on the tenant network, perform a bare metal instance deployment operation on the expansion node using the preset fast channel deployment mode to complete the deployment of the bare metal instance.

[0058] In this embodiment, preparing the access switch information for the bare metal node requires configuration in the network component configuration file, including the switch name, Internet Protocol address, username, password, and switch type. Then, the access port of the bare metal node is set to the virtual LAN of the deployed network within the switch. The bare metal node is registered using the username and password of the node's intelligent platform management interface. After successful registration, a self-test operation is initiated on the node. The bare metal checker service starts a memory-disk environment to detect the node's CPU, memory, disk, graphics processor, host bus adapter card, and other hardware information. Based on this information, the bare metal node is configured, and then the system disk is automatically cleaned up. After successful expansion, the node's status changes to "available," meaning the node is usable. Specifically, the process of expanding bare metal nodes using the preset fast-channel deployment mode based on the deployment network to obtain expanded nodes may include: configuring the access switch information of the bare metal node in the network component and obtaining the intelligent platform management interface authentication information of the bare metal node based on the deployment network and using the preset fast-channel deployment mode; setting the access port of the bare metal node to the virtual LAN corresponding to the deployment network on the physical switch based on the access switch information; registering the bare metal node according to the intelligent platform management interface authentication information and initiating a self-test request to the bare metal inspector service, so that the bare metal inspector service can start the memory disk environment based on the self-test request, detect the hardware information of the bare metal node and configure the bare metal node based on the detection results; the bare metal component performs a system disk cleanup operation on the bare metal node and changes the status of the bare metal node to an available state to obtain expanded nodes.

[0059] Furthermore, by specifying the tenant's operating system image, network, and instance specifications, a bare metal instance is created. The compute component automatically schedules the instance to a node that is in an available state. Due to the fast-track mode, the bare metal service directly calls the bare metal Python proxy service to write the image to the system disk, and then restarts the node. Finally, the node becomes ACTIVE, meaning that the bare metal node has completed system provisioning. Specifically, the step of deploying the bare metal instance on the expansion node based on the tenant network and using the preset fast-track deployment mode to complete the deployment of the bare metal instance can include: creating a bare metal instance based on the tenant network and using the preset fast-track deployment mode according to the pre-set tenant operating system image, network configuration, and instance specifications; scheduling the bare metal instance to the expansion node using the compute component; using the bare metal component to call the proxy service running on the expansion node to write the tenant's operating system image to the system disk of the expansion node; and restarting the expansion node to make the expansion node active, thereby completing the deployment of the bare metal instance.

[0060] As can be seen from the above, this application embodiment innovatively solves the technical problem that the community version's fast track mode cannot adapt to multi-tenant scenarios by constructing an open stack cloud platform basic environment that supports network isolation and making targeted improvements to the bare metal service components. Specifically, by retaining the deployment network port after system disk cleanup and establishing a sound port remnant handling mechanism, it ensures that the entire process of bare metal node expansion and instance deployment can stably run in fast track mode under the premise of strict isolation between the deployment network and the tenant network. This allows nodes to be restarted only once during expansion and deployment, reducing the overall operation time by half, while meeting the security requirements of multi-tenant network isolation in the production environment. It achieves a unified improvement in efficiency and security, providing reliable technical support for the actual deployment of bare metal services on the cloud platform.

[0061] See Figure 2 As shown in the figure, this application discloses a bare metal node expansion and instance deployment device in a multi-tenant scenario, including:

[0062] Environment deployment module 11 is used to deploy the basic environment of the Open Stack Cloud Platform; the basic environment includes computing components that provide computing services, bare metal components that provide bare metal services, network components that provide network services, image components that provide image services, and authentication components that provide authentication services; wherein, the network components are used to enable interaction with physical switches by enabling general switch plugins, so as to provide mutually isolated deployment networks and tenant networks.

[0063] The service adjustment module 12 is used to adjust the code and related configuration files of the bare metal component, and restart the bare metal service and bare metal inspector service after the adjustment is completed, so that the bare metal component can support the preset fast channel deployment mode; the bare metal inspector service is used to automatically detect the hardware information of bare metal nodes.

[0064] The operation execution module 13 is used to perform a bare metal node expansion operation based on the deployment network using the preset fast channel deployment mode to obtain an expansion node, and to perform a bare metal instance deployment operation on the expansion node based on the tenant network using the preset fast channel deployment mode to complete the deployment of the bare metal instance.

[0065] In some specific embodiments, the service adjustment module 12 may specifically include:

[0066] The first configuration file adjustment unit is used to adjust the fast channel parameters in the configuration file of the bare metal component and ensure that the bare metal instance and the bare metal node meet the preset conditions. The preset conditions are that the bare metal instance is in mirror boot mode and the automatic cleanup configuration item is enabled, the power supply of the bare metal node is on, and the internal information of the node driver includes a proxy Uniform Resource Locator and a heartbeat signal that has not timed out.

[0067] The second configuration file adjustment unit is used to adjust the self-test non-power-off parameter in the configuration file of the bare metal inspector; the bare metal inspector is used to provide the bare metal inspector service;

[0068] The code adjustment submodule is used to modify the code logic of the bare metal component so that the deployment network port is retained after the system disk cleanup operation is completed using the preset fast channel deployment mode, and port remnants are eliminated according to the preset port management policy; the preset port management policy is a policy to eliminate port remnants according to subsequent operations.

[0069] The first restart unit is used to upgrade the binary packages of the bare metal service and the bare metal inspector service and restart the corresponding service processes for non-containerized deployment environments.

[0070] The second restart unit is used to replace the images of the bare metal service and the bare metal inspector service and restart the corresponding container group for a containerized deployment environment.

[0071] Accordingly, the code adjustment submodule may specifically include:

[0072] The first port residue elimination unit is used to delete all existing deployed network ports of the current node and update the cleanup virtual interface identifier in the network component corresponding to this cleanup operation before creating a new deployment network port if the subsequent operation is to perform the system disk cleanup operation again.

[0073] The second port residual elimination unit is used to remove the residual cleanup virtual interface identifier corresponding to the previous cleanup operation from the current node's internal information if the subsequent operation is to perform a bare metal instance deployment operation.

[0074] The cleanup virtual interface identifier is used to uniquely identify a deployment network port created and used by the bare metal component for the cleanup operation within the network component;

[0075] Accordingly, the second port residue elimination unit may specifically include:

[0076] The identifier clearing subunit is used by the bare metal component to perform a removal and cleanup network operation during the preparation of the deployment environment, so as to clear the cleanup virtual interface identifiers that remain in the internal information of the current node and are corresponding to the previous cleanup operation.

[0077] In some specific embodiments, the operation execution module 13 may specifically include:

[0078] The information access unit is used to configure the access switch information of the bare metal node in the network component and obtain the intelligent platform management interface authentication information of the bare metal node based on the deployment network and using the preset fast channel deployment mode, and set the access port of the bare metal node to the virtual local area network corresponding to the deployment network on the physical switch based on the access switch information.

[0079] The hardware self-test unit is used to register bare metal nodes according to the authentication information of the intelligent platform management interface and to initiate a self-test request to the bare metal inspector service, so as to use the bare metal inspector service to start the memory disk environment based on the self-test request, detect the hardware information of the bare metal node and configure the bare metal node based on the detection results.

[0080] The node expansion unit is used by the bare metal component to perform a system disk cleanup operation on the bare metal node and change the state of the bare metal node to an available state to obtain an expanded node;

[0081] The instance creation unit is used to create bare metal instances based on the tenant network, using the preset fast channel deployment mode according to the pre-set tenant operating system image, network configuration and instance specifications, and to schedule the bare metal instances to the expansion node using the computing component;

[0082] The instance deployment unit is used to call the proxy service running on the expansion node using the bare metal component, write the tenant operating system image to the system disk of the expansion node, and restart the expansion node to make the expansion node active, thereby completing the deployment of the bare metal instance.

[0083] Furthermore, embodiments of this application also disclose an electronic device, Figure 3 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the bare metal node expansion and instance deployment method in the multi-tenant scenario disclosed in any of the foregoing embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be a computer.

[0084] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0085] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0086] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the bare metal node expansion and instance deployment method in a multi-tenant scenario as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0087] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned method for bare metal node expansion and instance deployment in a multi-tenant scenario. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0088] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0089] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0090] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0091] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0092] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for scaling up and deploying bare metal nodes in a multi-tenant scenario, characterized in that, include: The basic environment for deploying the OpenStack Cloud Platform includes computing components that provide computing services, bare metal components that provide bare metal services, network components that provide network services, image components that provide image services, and authentication components that provide authentication services. The network components are used to interact with physical switches by enabling general switch plugins to provide mutually isolated deployment networks and tenant networks. The code and related configuration files of the bare metal component are adjusted, and the bare metal service and bare metal inspector service are restarted after the adjustment is completed so that the bare metal component supports the preset fast channel deployment mode; the bare metal inspector service is used to automatically detect the hardware information of bare metal nodes. Based on the deployment network, the bare metal node is expanded using the preset fast channel deployment mode to obtain expanded nodes. Based on the tenant network, the bare metal instance is deployed on the expanded nodes using the preset fast channel deployment mode to complete the deployment of the bare metal instance.

2. The method for scaling up and deploying bare metal nodes in a multi-tenant scenario according to claim 1, characterized in that, The adjustments to the code and related configuration files of the bare metal component include: Adjust the fast channel parameters in the configuration file of the bare metal component and ensure that the bare metal instance and the bare metal node meet the preset conditions; the preset conditions are that the bare metal instance is in mirror boot mode and the automatic cleanup configuration item is enabled, the power of the bare metal node is on, and the node driver internal information includes a proxy Uniform Resource Locator and a heartbeat signal that has not timed out. The parameter for not losing power after self-test in the configuration file of the bare metal inspector is adjusted; the bare metal inspector is used to provide the bare metal inspector service. Modify the code logic of the bare metal component so that after the system disk cleanup operation is completed using the preset fast channel deployment mode, the deployment network port is retained, and port remnants are eliminated according to the preset port management policy; the preset port management policy is a policy to eliminate port remnants according to subsequent operations.

3. The method for scaling up and deploying bare metal nodes in a multi-tenant scenario according to claim 2, characterized in that, The step of eliminating port remnants according to a preset port management policy includes: If the subsequent operation is to perform the system disk cleanup operation again, the bare metal component deletes all existing deployed network ports of the current node before creating a new deployment network port, and updates the cleanup virtual interface identifier in the network component corresponding to this cleanup operation. If the subsequent operation is to deploy a bare metal instance, the bare metal component removes the residual cleanup virtual interface identifier corresponding to the previous cleanup operation from the current node's internal information; The cleanup virtual interface identifier is used to uniquely identify a deployment network port created and used by the bare metal component for the cleanup operation within the network component.

4. The method for scaling up and deploying bare metal nodes in a multi-tenant scenario according to claim 3, characterized in that, The bare metal component removes the residual cleanup virtual interface identifier corresponding to the previous cleanup operation from the current node's internal information, including: The bare metal component performs a removal and cleanup network operation during the environment preparation phase to remove the cleanup virtual interface identifiers that remain in the current node's internal information and correspond to the previous cleanup operation.

5. The method for scaling up and deploying bare metal nodes in a multi-tenant scenario according to claim 1, characterized in that, The process of restarting the bare metal service and bare metal inspector service after adjustment includes: For non-containerized deployment environments, upgrade the binary packages of the bare metal service and bare metal inspector service and restart the corresponding service processes; For containerized deployment environments, replace the images of the bare metal service and bare metal inspector service and restart the corresponding container groups.

6. The method for scaling up and deploying bare metal nodes in a multi-tenant scenario according to claim 1, characterized in that, The process of scaling up bare metal nodes using the preset fast-channel deployment mode based on the deployment network to obtain expanded nodes includes: Based on the deployed network, the access switch information of the bare metal node is configured in the network component using the preset fast channel deployment mode, and the intelligent platform management interface authentication information of the bare metal node is obtained. Based on the access switch information, the access port of the bare metal node is set as the virtual local area network corresponding to the deployed network on the physical switch. Register a bare metal node according to the authentication information of the intelligent platform management interface, and initiate a self-test request to the bare metal inspector service so that the bare metal inspector service can start the memory disk environment based on the self-test request, detect the hardware information of the bare metal node, and configure the bare metal node based on the detection results; The bare metal component performs a system disk cleanup operation on the bare metal node and changes the state of the bare metal node to an available state to obtain an expanded node.

7. The method for scaling up and deploying bare metal nodes in a multi-tenant scenario according to claim 1, characterized in that, The step of deploying bare metal instances on the expansion node using the preset fast channel deployment mode based on the tenant network to complete the deployment of bare metal instances includes: Based on the tenant network, bare metal instances are created using the preset fast channel deployment mode according to the pre-set tenant operating system image, network configuration and instance specifications, and the bare metal instances are scheduled to the expansion node using the computing component; The bare metal component is used to call the proxy service running on the expansion node to write the tenant operating system image to the system disk of the expansion node and restart the expansion node to make the expansion node active, thereby completing the deployment of the bare metal instance.

8. A device for scaling up bare metal nodes and deploying instances in a multi-tenant scenario, characterized in that, include: The environment deployment module is used to deploy the basic environment of the OpenStack Cloud Platform. The basic environment includes computing components that provide computing services, bare metal components that provide bare metal services, network components that provide network services, image components that provide image services, and authentication components that provide authentication services. The network components are used to enable interaction with physical switches by enabling general switch plugins, so as to provide mutually isolated deployment networks and tenant networks. The service adjustment module is used to adjust the code and related configuration files of the bare metal component, and restart the bare metal service and bare metal inspector service after the adjustment is completed, so that the bare metal component can support the preset fast channel deployment mode; the bare metal inspector service is used to automatically detect the hardware information of the bare metal node. The operation execution module is used to perform a bare metal node expansion operation based on the deployment network and using the preset fast channel deployment mode to obtain an expansion node, and to perform a bare metal instance deployment operation on the expansion node based on the tenant network and using the preset fast channel deployment mode to complete the deployment of the bare metal instance.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor is configured to execute the computer program to implement the bare metal node scaling and instance deployment method in a multi-tenant scenario as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Used to store a computer program, wherein the computer program, when executed by a processor, implements the bare metal node scaling and instance deployment method in a multi-tenant scenario as described in any one of claims 1 to 7.

Images