WO2020024413A1

WO2020024413A1 - Method for controlling deployment of cloud computing platform, server, and storage medium

Info

Publication number: WO2020024413A1
Application number: PCT/CN2018/107908
Authority: WO
Inventors: 王翼
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-08-03
Filing date: 2018-09-27
Publication date: 2020-02-06
Also published as: CN109067877B; CN109067877A

Abstract

Embodiments of the present application disclose a method for controlling deployment of a cloud computing platform, a server, and a storage medium. The method comprises: determining a control node for controlling a function node; acquiring a first deployment instruction comprising node role assignment information; initializing and activating a first service in the control node, such that the control node adds target servers and assigns a node role to the same according to the node role assignment information; determining the target servers as function nodes to be controlled by the control node; configuring deployment parameters of the function nodes according to a deployment script, and initializing and activating a second service related to the node role; and detecting whether the determined nodes are connected, and if not, adjusting the deployment parameters of the unconnected function nodes according to the deployment script, such that the unconnected function nodes become connected. The invention achieves automatic adjustment and connection of a large number of nodes, thereby forming a complete and usable platform, reducing the number of manual deployment steps, and improving deployment efficiency.

Description

Control method, server and storage medium for cloud computing platform deployment

This application claims the priority of a Chinese patent application filed on August 3, 2018 with the Chinese Patent Office, application number 201810884475.X, and application name "A Control Method, Server, and Storage Medium for Cloud Computing Platform Deployment" The entire contents are incorporated herein by reference.

Technical field

The present application relates to the field of computer technology, and in particular, to a control method for deploying a cloud computing platform, a server, and a storage medium.

Background technique

With the maturity of cloud technology solutions, cloud computing platforms have become more and more widely used in various fields. Among them, the OpenStack cloud platform is an open source cloud computing management platform project. Several major components are combined to complete specific work. OpenStack supports almost all types of cloud environments. The goal of the project is to provide a cloud computing management platform that is simple to implement, scalable at scale, rich, and standardized.

Each module of the Openstack cloud platform currently on the market needs to be manually deployed manually, with a high error rate, poor node connectivity, and low efficiency.

Summary of the invention

The embodiments of the present application provide a cloud computing platform deployment control method, server, and storage medium, which can automatically debug and connect a large number of nodes to form a complete and usable platform, reduce the deployment steps of manual operations, and improve deployment efficiency.

In a first aspect, an embodiment of the present application provides a method for controlling cloud computing platform deployment. The method includes:

Determine the control node used to control the function node;

Obtaining a first deployment instruction containing node role allocation information;

Initialize and start a first service in the control node, so that the control node adds a target server and assigns a node role to the target server according to the node role assignment information;

Determining the target server as a functional node controlled by the control node;

Setting configuration parameters of the function node according to a configuration script, initializing and starting a second service related to the node role;

It is detected whether the determined functional nodes are connected. If not, the configuration parameters of the disconnected functional nodes are debugged according to the configuration script, so that the disconnected functional nodes are connected.

In a second aspect, an embodiment of the present application provides a server including: a determination module, an acquisition module, an initial module, a setting module, a configuration module, a detection module, and a debugging module, where:

The determining module is configured to determine a control node for controlling a function node;

The obtaining module is configured to obtain a first deployment instruction including node role allocation information;

The initial module is configured to initialize and start a first service in the control node, so that the control node adds a target server according to the node role allocation information and assigns a node role to the target server;

The setting module is configured to determine the target server as a function node controlled by the control node;

The configuration module is configured to set configuration parameters of the functional node according to a configuration script, and the transmission module is further configured to initialize and start a second service related to the role of the node;

The detecting module is configured to detect whether the determined functional nodes are connected;

The debugging module is configured to debug configuration parameters of the disconnected functional nodes according to the configuration script when the nodes are disconnected, so that the disconnected functional nodes are connected.

According to a third aspect, an embodiment of the present application further provides a server, including a processor, an input device, an output device, and a memory. The processor, the input device, the output device, and the memory are connected to each other. The memory is used for A computer program is stored, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to the first aspect and any possible implementation manner thereof.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, where the computer program includes program instructions, and the program instructions, when executed by a processor, cause all the The processor executes the method of the first aspect and any possible implementation manners.

In the embodiment of the present application, by determining the control nodes and setting the function nodes controlled by the control nodes according to the node role allocation information, a large number of nodes can be automatically debugged and connected to form a complete and usable cloud computing platform, reducing manual deployment steps and improving deployment. effectiveness.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic flowchart of a cloud computing platform deployment control method according to an embodiment of the present application;

2 is a schematic flowchart of a cloud computing platform deployment control method according to another embodiment of the present application;

3 is a schematic structural diagram of a server according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of another server provided by an embodiment of the present application.

detailed description

In the following, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Reference to "an embodiment" herein means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are they independent or alternative embodiments that are mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

In order to better understand the embodiments of the present application, the method of applying the embodiments of the present application will be described below.

Please refer to FIG. 1, which is a schematic flowchart of a cloud computing platform deployment control method according to an embodiment of the present application. This method may be applied to a server of a cloud computing platform. As shown in FIG. 1, the method may include:

101. Determine a control node for controlling a function node.

The embodiments of the present application can be applied to the deployment of a cloud computing platform. To facilitate understanding, first introduce OpenStack and the cloud platform. It is a distributed system. Not only can each service be deployed in a distributed manner, but the components in the service can also be deployed in a distributed manner. This distributed nature gives OpenStack great flexibility, scalability, and high availability. The entire OpenStack is composed of four major parts: control nodes, compute nodes, network nodes, and storage nodes (these four nodes can also be installed on a single machine and deployed in a single machine). The nodes other than the control node can be collectively referred to as the above functional nodes. . among them:

The control node is responsible for the control of the remaining functional nodes, including the virtual machine establishment, migration, network allocation, storage allocation, etc .; the computing node is responsible for the virtual machine operation; the network node is responsible for the communication between the external network and the internal network; the storage node is responsible for the virtual Machine's extra storage management and more.

Therefore, in the deployment of the platform, the above control nodes can be determined first. The server configured by the control node can assign an IP address to each computing node, and can provide connections to the virtual machines and servers of each computing node, and handle security group rules (such as using Dnsmasq configuration). The server realizes the automatic allocation of virtual machine IP addresses, and uses a Linux bridge as a virtual network implementation mechanism) to facilitate management.

The overall architecture of OpenStack includes: different modules of the virtual machine VM and OpenStack (called "services" in OpenStack, and "services" are used hereinafter). The control node can include all OpenStack services, and the remaining nodes controlled by the control node contain different services according to their roles:

The network node contains only Neutron services. Neutron is responsible for managing the communication between the private network segment and the public network segment, as well as managing the communication / topology between the virtual machine network, managing fire prevention on the virtual machine, etc.

Compute nodes include three services: Nova, Neutron, and Telemeter:

1) Basic services

Nova: Provides virtual machine creation, running, migration, snapshot and other services around the virtual machine, and provides APIs to interface with the control node, and the control node issues tasks.

Neutron: Provides communication services between compute nodes and network nodes.

2) extended services

Telmeter: Provides a monitoring agent for computing nodes, and reports the condition of the virtual machine to the control node. It is a proxy service for Centimeter.

The storage node contains services such as Cinder and Swift:

Cinder: Block storage service, which provides corresponding block storage. In simple terms, it is a virtual disk that can be mounted on the corresponding virtual machine. It is not affected by factors such as the file system. For virtual machines, this operation is For example, a newly added hard disk can complete any operation on the disk, including mounting, unmounting, formatting, converting file systems, etc., and it is mostly used for space expansion when the virtual machine has insufficient space.

Swift: Object storage service, which provides corresponding object storage. In simple terms, it is a virtual disk space that can store files in this space. It can only store files. It cannot format and convert file systems. Most of them are used in Cloud disk / file.

The determination of the control node may be: the system detects that the eligible node is the above-mentioned control node (usually only one server meets the requirements), or the user can independently select a server as the control node.

102. Obtain a first deployment instruction including node role allocation information.

The above-mentioned first deployment instruction can be triggered by a user's operation, that is, the user can start a platform deployment task through a simple interactive operation. The first deployment instruction may include node role allocation information, where the node role allocation information is mainly used for the number of nodes and each The setting of each function node role, the node role may include one or more of a computing node, a storage node, and a network node.

Node role allocation information can be actively selected by the user, such as selecting a node role and the number of node roles, or it can be set automatically and randomly by the platform. At this time, the user only needs to start a deployment task. Optionally, the platform can store the node role assignment information set by the user, and the user can use the same deployment scheme without the need for repeated settings in order to facilitate subsequent automatic deployment tasks.

103. Initialize and start the first service in the control node, so that the control node adds a target server according to the node role allocation information and assigns a node role to the target server.

After receiving the above-mentioned first deployment instruction, a deployment task may be executed to initialize and start the first service in the control node, where the first service is all the services necessary for the control node. For example, in the OpenStack platform, the first service Can provide all services for OpenStack. Specifically, this step may include: opening the HTTP service of the control node, obtaining and entering the root password of the control node, initializing and starting all OpenStack services in the control node.

Specifically, the role of the assigned node is mainly to determine the function type of the functional node to configure the services of the functional node. After initializing and starting the first service in the control node, and after obtaining a first deployment instruction containing node role allocation information, the control node may add a target server and assign a node role to the target server according to the node role allocation information. To deploy function nodes.

The target server can be any server to which the control node can connect, that is, the control node can obtain the addresses of other servers and deploy these servers as functional nodes of the platform (or understood as a cluster); the target server can also be selected by the user Servers, that is, users can choose to enter the addresses of multiple servers to deploy functional nodes to these servers.

For example, the initialization steps include:

Initialize NTP service, and initialize keystone, nova, cinder, neutron related services;

Initialize rabbitmq service, Nova service, initialize Cinder service, initialize Neutron service, and initialize the database of each service.

Optionally, before configuring the node service of the control node, you can first configure the installation environment, which can mainly include modifying the host name, configuring the local network, upgrading the latest system, etc. These operations can be performed manually by the user or can be set to automatic carried out. The platform can test the installation environment of each node to determine whether the installation environment is complete.

104. Determine the target server as a functional node controlled by the control node.

Specifically, after the first service in the control node is initialized and started, the control node may deploy the node according to the node role allocation information, so that the platform may determine the target server as a functional node that can be controlled by the control node.

105. Set the configuration parameters of the function node according to the configuration script, and initialize and start the second service related to the role of the node.

After the node roles are assigned, the pre-stored configuration script can be obtained. It can be understood that different node roles correspond to different configuration algorithms. You can execute the corresponding configuration algorithm according to the node role of each functional node to set the node parameters. To implement related services. The above-mentioned node parameters may include network parameters and storage parameters of the nodes.

Specifically, adding a server as a computing node through the control node may include: obtaining the IP and root password of the server to be added through the control node, setting the node role of the server as a computing node, configuring the IP of the storage node of the computing node, and controlling the node. IP, virtualization type, set the network type of each network card of this compute node, initialize and start the computing-related OpenStack services.

Adding a server as a storage node through the control node may include: obtaining the IP and root password of the server to be added through the control node, setting the node role of the server as the storage node, configuring the IP of the storage node of the network node, the control node IP, and virtual Set the network type of each network card of the storage node to the binding type, and initialize and start the storage-related OpenStack services.

Adding a server as a network node through the control node may include: obtaining the IP and root password of the server to be added through the control node, setting the node role of the server to a network node, configuring the IP of the storage node of the network node, the control node IP, and virtualization Type, set the two network cards of this network node as the external network exit, initialize and start the network related OpenStack services.

106. Detect whether the determined functional nodes are connected. If they are not connected, debug the configuration parameters of the disconnected functional nodes according to the configuration script to make the disconnected functional nodes communicate.

The system can automatically detect the connection status between various functional nodes. The above detection can be periodic. If a functional node is detected to be disconnected somewhere, you can obtain the debugging algorithm pre-written in the configuration script for the role of the node. The connected functional nodes are debugged, and the parameters are reconfigured so that the disconnected functional nodes can work normally, thereby ensuring connectivity between the functional nodes.

This embodiment of the present application determines a control node for controlling a function node, obtains a first deployment instruction containing node role allocation information, and then initializes and starts a first service in the control node, so that the control node adds a target according to the node role allocation information. The server and the node role are assigned to the target server, so that the target server can be determined as the function node controlled by the control node. Further, the configuration parameters of the function node are set according to the configuration script, the second service related to the node role is initialized and started, and It can also detect whether the identified functional nodes are connected. If they are not connected, debug the configuration parameters of the disconnected functional nodes according to the configuration script to make the disconnected functional nodes connect. A large number of nodes can be automatically debugged and connected to form a complete and usable Compared with general manual deployment, the cloud computing platform improves deployment efficiency and avoids errors caused by manual participation.

Please refer to FIG. 2. FIG. 2 is a schematic flowchart of another cloud computing platform deployment control method disclosed in the embodiment of the present application. FIG. 2 is further optimized based on FIG. 1. As shown in FIG. 2, the cloud The control method for computing platform deployment includes the following steps:

201. Receive a control node setting instruction for a target server.

Specifically, a control node setting instruction may be received, and the control node setting instruction specifies that the target server is used as the control node, for example, is selected by the target server's IP address or name, and is then initially set as the control node, and step 202 may be performed. The user can choose to use the target server as the control node of the entire platform, and the server as the control node can use a proxy server (ProxyServer): ProxyServer provides an HTTP-based service interface to the outside. It will find the service address and forward the user based on the ring information. Request to the corresponding account, container, or object, and perform CRUD (add, delete, modify, and check) operations. Before accessing the service, you need to obtain the access token through the authentication server, and then add the header information X-Auth-Token to the sent request. The proxy server is responsible for the communication between the other components, and also handles a large number of failed requests.

202. Determine whether the target server has a system configuration including all OpenStack services installed.

The server serving as the OpenStack control node needs to have all OpenStack services installed to ensure the stability and comprehensive functions of the system. Therefore, you can test the target server to determine whether it has installed a system configuration that includes all OpenStack services. , Go to step 204; if not installed, go to step 203.

203. Obtain an image file for installing a system including all the services of the OpenStack, and install the image file on the target server.

Specifically, the obtaining of the above image file may be: an operating system obtained on a server on which all services of OpenStack have been installed, (deleting the startup script of all services of OpenStack) making the operating system as the above image file. After the above image file is successfully installed, step 204 may be performed.

204. Determine that the target server is the control node.

So far, the above target server can be determined as the control node. For the foregoing steps 201 to 204, reference may be made to the detailed description in step 101 of the embodiment shown in FIG. 1, and details are not described herein again.

205. Configure the installation environment of the control node.

Before configuring the node service, you can first configure the installation environment of the control node, which can include modifying the host name, configuring the local network, and upgrading the latest system. These operations can be performed manually by the user or set to be performed automatically. Optionally, the platform can detect the installation environment of each node to determine whether the installation environment is complete and ensure the stability of subsequent system operations.

206. Acquire a first deployment instruction including node role allocation information.

207. Initialize and start the first service in the control node, so that the control node adds a target server according to the node role allocation information and assigns a node role to the target server.

The first service is all the services of the OpenStack.

208. Determine the target server as a functional node controlled by the control node.

209. Set the configuration parameters of the function node according to the configuration script, and initialize and start the second service related to the role of the node.

The above-mentioned second service can be understood as a part of the OpenStack service, and the corresponding service is specifically determined according to the foregoing node role.

210. Detect whether the determined functional nodes are connected. If not, debug the configuration parameters of the disconnected functional nodes according to the configuration script to make the disconnected functional nodes communicate.

For the foregoing steps 206 to 210, reference may be made to the detailed description in steps 102 to 106 in the embodiment shown in FIG. 1, and details are not described herein again.

211. When an isolation instruction for the target node is detected, configure the firewall information of the target node to isolate the target node.

In the case where different nodes need to be isolated, an isolation instruction for the target node can be triggered. The above isolation instruction can be triggered by user operations. The user can configure the target node's firewall. For example, different storage nodes can be isolated from each other to ensure different storage. Data security on the node.

When configuring the node parameters, you can also perform the configuration of the firewall. The core concept of the OpenStack firewall is the concept of firewall policies and firewall rules. Policies are an ordered collection of rules. Rules specify the set of attributes (such as port ranges, protocols, and IP addresses) that make up the matching criteria, and actions to take (allow or deny) on matching traffic. Policies can be public and firewalls can be shared.

The firewall is implemented in various ways, depending on the driver used. For example, the iptables driver uses iptable rules to implement the firewall; the OpenVSwitch driver uses flow entries in the flow table to implement firewall rules. You can define n security groups, each security group can have n rules, and you can bind n security groups to each instance. There is always a default security group in Nova, which cannot be deleted. When you create an instance, if you do not specify a security group, the default security group is used by default.

Specifically, it can be implemented using Firewall Service (FWaaS), which is an advanced service of Neutron. Users can use it to create and manage firewalls to filter traffic.

Firewalls in traditional networks are generally placed on gateways to control access between subnets. The principle of FWaaS is similar. It applies firewall rules on the Neutron virtual router to control the data entering the tenant network. Security group rules are implemented on a Linux bridge qbr on a compute node connected to an instance, and firewall rules created by FWaaS are implemented on a virtual router implemented on the edge of a tenant network. FWaaS is not intended to replace the functionality of a security group, and it provides a more complementary security group, especially in its current state of implementation. FWaaS currently lacks some of the functions provided by the security group, including the inability to specify the direction of communication. In contrast, security groups also need FWaas as a supplement because they lack the ability to create specific rules to deny all traffic.

By configuring firewall parameters, FWaaS and security groups can be deployed at the same time to achieve double protection, which not only ensures node connectivity, but also improves security.

Optionally, the method further includes: detecting a system data processing state, and adding or deleting a node according to the system data processing state.

In a cloud computing platform, it is best to install multiple management nodes, because once the network is too large, the performance of one management node is limited, which will cause most resources to be idle. Installing multiple management nodes can achieve load balancing and make resources possible. Make the most of it.

Specifically, the above-mentioned node role allocation information can be adjusted by the platform, and the system data processing status (data processing amount) is periodically checked to determine whether the number of nodes is sufficient. If the data processing amount is large, the number of nodes can be appropriately increased The number of nodes in different roles can also be determined by the demand for different services. By automatically adding or removing nodes, the flexibility of platform deployment is improved, manual operations are reduced, and intelligent deployment is achieved.

Optionally, when a problem is detected in one of the control nodes, it can be switched to another control node to ensure service availability.

In the embodiment of the present application, by receiving a control node setting instruction for a target server, it is determined whether the target server has installed a system configuration including all OpenStack services, and if not, obtains an image file for installing a system including all OpenStack services, Install the image file on the target server, determine that the target server is the control node, configure the installation environment of the control node, obtain a first deployment instruction containing node role allocation information, initialize and start the first service on the control node To enable the control node to add a target server and assign a node role to the target server according to the node role allocation information, determine the target server as a functional node controlled by the control node, and then set the configuration parameters of the node according to a configuration script To initialize and start the second service related to the role of the node, detect whether the determined functional nodes are connected, and if not, debug the configuration parameters of the functional nodes that are not connected according to the above configuration script, so that The disconnected functional nodes are connected, and when the isolation instruction for the target node is detected, the firewall information of the target node can be configured to isolate the target node, and a large number of functional nodes can be automatically debugged and connected to form a complete and usable cloud. A computing platform that reduces manual deployment steps and improves deployment efficiency.

Please refer to FIG. 3, which is a schematic structural diagram of a server according to an embodiment of the present application. The server 300 includes a determination module 310, an initial module 320, an acquisition module 330, a setting module 340, a configuration module 350, a detection module 360, and debugging Module 370, where:

The foregoing determining module 310 is configured to determine a control node for controlling a function node;

The obtaining module 320 is configured to obtain a first deployment instruction including node role allocation information;

The initial module 330 is configured to initialize and start a first service in the control node, so that the control node adds a target server and assigns a node role to the target server according to the node role allocation information;

The setting module 340 is configured to determine the target server as a function node controlled by the control node;

The configuration module 350 is configured to set configuration parameters of the functional node according to a configuration script, and the transmission module is further configured to initialize and start a second service related to the role of the node;

The detection module 360 is configured to detect whether the determined functional nodes are connected;

The debugging module 370 is configured to debug configuration parameters of the disconnected nodes according to the configuration script when the functional nodes are disconnected, so that the disconnected nodes are connected.

Optionally, the above node role allocation information includes: the number of nodes and the node role of each node;

The foregoing node roles include one or more of a computing node, a storage node, and a network node.

As a possible implementation manner, the foregoing determining module 310 is specifically configured to:

Receiving control node setting instructions for the target server;

Determine whether the target server has a system configuration including the first service, and if so, determine that the target server is the control node.

As a possible implementation manner, the first service is all OpenStack services;

The server 300 further includes an installation module 380 for obtaining an image file for installing and installing a system including all the services of the OpenStack when the target server does not have a system configuration including the first service installed, and installing the above on the target server. Image file.

As a possible implementation manner, the installation module 380 is further configured to configure the installation environment of the control node before the initializing and starting the first service in the control node.

As a possible implementation manner, the server 300 further includes a node control module 390, configured to detect a system data processing state, and add or delete a function node according to the system data processing state.

As a possible implementation manner, the foregoing server 300 further includes:

The firewall module 3100 is configured to configure the firewall information of the target node to isolate the target node when an isolation instruction for the target node is detected.

As a possible implementation manner, the foregoing node control module 390 is further configured to switch to an alternative control node to control the functional node when it is detected that the control node is not in a working state.

According to the specific implementation of the embodiment of the present application, steps 101 to 106 and 201 to 211 involved in the method for controlling the deployment of the cloud computing platform shown in FIGS. 1 and 2 may be performed by each module in the server 300 shown in FIG. 3. carried out.

Through the server 300 in the embodiment of the present application, the server 300 determines a control node for controlling a function node, obtains a first deployment instruction including node role allocation information, initializes and starts a first service in the control node, so that the control node described above Add the target server and assign the node role to the target server according to the node role assignment information, determine the target server as a functional node controlled by the control node, and then set the node's configuration parameters according to the configuration script to initialize and start the second node-related role Services, and check whether the functional nodes are connected. If they are not connected, debug the configuration parameters of the non-connected functional nodes according to the above configuration script to make the non-connected functional nodes connect, and you can automatically debug and connect a large number of nodes to form a complete Available cloud computing platform reduces manual deployment steps and improves deployment efficiency.

Please refer to FIG. 4, which is a schematic structural diagram of another server disclosed in an embodiment of the present application. As shown in FIG. 4, the server 400 includes a processor 401 and a memory 402. The server 400 may further include a bus 403. The processor 401 and the memory 402 may be connected to each other through the bus 403. The bus 403 may be a peripheral component interconnection standard (Peripheral Component Interconnect, PCI) bus or Extended Industry Standard Architecture (EISA) bus, etc. The bus 403 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 4, but it does not mean that there is only one bus or one type of bus. The server 400 may further include an input-output device 404, and the input-output device 404 may include a display screen, such as a liquid crystal display screen. The memory 402 is configured to store one or more programs containing instructions; the processor 401 is configured to call the instructions stored in the memory 402 to execute some or all of the method steps mentioned in the embodiments of FIG. 1 and FIG. 2.

It should be understood that, in the embodiment of the present application, the processor 401 may be a central processing unit (CPU), and the processor may also be another general-purpose processor or a digital signal processor (DSP). , Application specific integrated circuit (ASIC), ready-made programmable gate array (Field-Programmable GateArray, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The input device 402 may include a touch panel, a fingerprint sensor (for collecting fingerprint information and orientation information of a user), a microphone, and the like, and the output device 403 may include a display (LCD, etc.), a speaker, and the like.

The memory 404 may include a read-only memory and a random access memory, and provide instructions and data to the processor 401. A portion of the memory 404 may also include non-volatile random access memory. For example, the memory 404 may also store device type information.

Through the server 400 in the embodiment of the present application, the server 400 can determine a control node for controlling a function node, obtain a first deployment instruction including node role allocation information, initialize and start a first service in the control node, so that the control node described above Add the target server and assign the node role to the target server according to the node role assignment information, determine the target server as a functional node controlled by the control node, and then set the node's configuration parameters according to the configuration script to initialize and start the second node-related role. Services, and check whether the functional nodes are connected. If they are not connected, debug the configuration parameters of the non-connected functional nodes according to the above configuration script to make the non-connected functional nodes connect. A large number of nodes can be automatically debugged and connected to form a complete system. Available cloud computing platform reduces manual deployment steps and improves deployment efficiency.

An embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program for electronic data exchange, and the computer program causes a computer to execute any one of the cloud types described in the foregoing method embodiments Some or all steps of a control method for computing platform deployment.

In the above embodiments, the description of each embodiment has its own emphasis. For a part that is not described in detail in one embodiment, reference may be made to related descriptions in other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed device may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or may be combined. Integration into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or modules, and may be electrical or other forms.

The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the objective of the solution of this embodiment.

When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on such an understanding, the technical solution of the present application essentially or part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory, Several instructions are included to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The foregoing memory includes: a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk, and other media that can store program codes.

Claims

A control method for cloud computing platform deployment, characterized in that the method includes:

Determine the control node used to control the function node;

Obtaining a first deployment instruction containing node role allocation information;

Initialize and start a first service in the control node, so that the control node adds a target server and assigns a node role to the target server according to the node role assignment information;

Determining the target server as a functional node controlled by the control node;

Setting configuration parameters of the function node according to a configuration script, initializing and starting a second service related to the node role;

It is detected whether the determined functional nodes are connected. If not, the configuration parameters of the disconnected functional nodes are debugged according to the configuration script, so that the disconnected functional nodes are connected.
The method according to claim 1, wherein the node role assignment information comprises:

The number of functional nodes and the node role of each functional node;

The node role includes one or more of a computing node, a storage node, and a network node.
The method according to claim 2, wherein the determining a control node for controlling a function node comprises:

Receiving control node setting instructions for the target server;

Determine whether the target server has a system configuration including the first service, and if it is installed, determine that the target server is the control node.
The method according to claim 3, wherein the determining a control node for controlling a function node further comprises:

It is determined that at least one server on which a system configuration including the first service is installed is the control node.
The method according to claim 3 or 4, wherein the first service is all OpenStack services;

If the target server does not have a system configuration including the first service, the method further includes:

Obtain an image file for installing a system containing all the services of the OpenStack, and install the image file on the target server.
The method according to claim 5, wherein before the initializing and starting the first service in the control node, the method further comprises:

Configure an installation environment of the control node.
The method according to claim 6, further comprising:

Detecting a system data processing state, and adding or deleting the functional node according to the system data processing state.
The method according to any one of claims 1-7, wherein the method further comprises:

When an isolation instruction for a target node is detected, firewall information of the target node is configured to isolate the target node.
The method according to claim 8, further comprising:

When it is detected that the control node is not in a working state, it is switched to an alternative control node to control the function node.
A server is characterized in that it includes: a determination module, an initial module, an acquisition module, a setting module, a configuration module, a detection module, and a debugging module, wherein:

The determining module is configured to determine a control node for controlling a function node;

The obtaining module is configured to obtain a first deployment instruction including node role allocation information;

The initial module is configured to initialize and start a first service in the control node, so that the control node adds a target server according to the node role allocation information and assigns a node role to the target server;

The setting module is configured to determine the target server as a function node controlled by the control node;

The configuration module is configured to set configuration parameters of the functional node according to a configuration script, and the transmission module is further configured to initialize and start a second service related to the role of the node;

The detecting module is configured to detect whether the determined functional nodes are connected;

The debugging module is configured to, when the functional nodes are disconnected, debug the configuration parameters of the disconnected functional nodes according to the configuration script, so that the disconnected functional nodes are connected.
The server according to claim 10, wherein the node role assignment information comprises:

The number of functional nodes and the node role of each functional node;

The node role includes one or more of a computing node, a storage node, and a network node.
The server according to claim 11, wherein the determining module is specifically configured to:

Receiving control node setting instructions for the target server;

Determine whether the target server has a system configuration including the first service, and if it is installed, determine that the target server is the control node.
The method according to claim 12, wherein the determining module is further configured to:

It is determined that at least one server on which a system configuration including the first service is installed is the control node.
The server according to claim 12 or 13, wherein the first service is all OpenStack services;

The server further includes an installation module for obtaining an image file for installing and installing a system including all the services of the OpenStack if the target server does not have a system configuration including the first service installed, and the target server is installed on the target server. Install the image file on.
The server according to claim 14, wherein the installation module is further configured to configure an installation environment of the control node before the initializing and starting the first service in the control node.
The server according to claim 15, further comprising a node control module for detecting a system data processing state, and adding or deleting the functional node according to the system data processing state.
The server according to any one of claims 10 to 16, further comprising a firewall module, configured to configure the firewall information of the target node when the isolation instruction for the target node is detected, so that the target node isolation.
The server according to claim 17, wherein the node control module is further configured to switch to an alternative control node to control the functional node when it is detected that the control node is not in a working state.
A server is characterized by comprising a processor, an input device, an output device, and a memory, and the processor, the input device, the output device, and the memory are connected to each other, wherein the memory is used to store a computer program, and the computer program Including program instructions, the processor is configured to call the program instructions and execute the method according to any one of claims 1-9.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes A method according to any one of 1-9 is required.