WO2020024413A1 - Procédé de commande du déploiement d'une plateforme informatique en nuage, serveur et support d'informations - Google Patents

Procédé de commande du déploiement d'une plateforme informatique en nuage, serveur et support d'informations Download PDF

Info

Publication number
WO2020024413A1
WO2020024413A1 PCT/CN2018/107908 CN2018107908W WO2020024413A1 WO 2020024413 A1 WO2020024413 A1 WO 2020024413A1 CN 2018107908 W CN2018107908 W CN 2018107908W WO 2020024413 A1 WO2020024413 A1 WO 2020024413A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
server
module
control node
control
Prior art date
Application number
PCT/CN2018/107908
Other languages
English (en)
Chinese (zh)
Inventor
王翼
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020024413A1 publication Critical patent/WO2020024413A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Definitions

  • 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.
  • OpenStack Open Source cloud computing management platform project.
  • 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.
  • 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.
  • an embodiment of the present application provides a method for controlling cloud computing platform deployment.
  • the method includes:
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 1 is a schematic flowchart of a cloud computing platform deployment control method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a cloud computing platform deployment control method according to another embodiment of the present application.
  • FIG. 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.
  • FIG. 1 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:
  • OpenStack 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.
  • 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.
  • OpenStack 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the first service can provide all services for OpenStack.
  • 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.
  • 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.
  • 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.
  • the initialization steps include:
  • the platform can test the installation environment of each node to determine whether the installation environment is complete.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the cloud The control method for computing platform deployment includes the following steps:
  • 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.
  • 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.
  • 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.
  • step 204 may be performed.
  • the above target server can be determined as the control node.
  • 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.
  • 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.
  • the first service is all the services of the OpenStack.
  • 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.
  • 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.
  • 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.
  • 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.
  • the iptables driver uses iptable rules to implement the firewall;
  • the OpenVSwitch driver uses flow entries in the flow table to implement firewall rules.
  • Firewall Service 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.
  • security groups also need FWaas as a supplement because they lack the ability to create specific rules to deny all traffic.
  • firewall parameters 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.
  • the method further includes: detecting a system data processing state, and adding or deleting a node according to the system data processing state.
  • 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.
  • control nodes when a problem is detected in one of the control nodes, it can be switched to another control node to ensure service availability.
  • the target server 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
  • FIG. 3 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.
  • 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.
  • the foregoing determining module 310 is specifically configured to:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 4 is a schematic structural diagram of another server disclosed in an embodiment of the present application.
  • 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.
  • PCI peripheral component interconnection standard
  • EISA Extended Industry Standard Architecture
  • 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.
  • 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.
  • a fingerprint sensor for collecting fingerprint information and orientation information of a user
  • a microphone for collecting fingerprint information and orientation information of a user
  • 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.
  • 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.
  • the disclosed device may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the modules is only a logical function division.
  • multiple units or components may be combined or may be combined. Integration into another system, or some features can be ignored or not implemented.
  • 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.
  • the integrated module 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.
  • 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.
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Debugging And Monitoring (AREA)
  • Stored Programmes (AREA)

Abstract

Des modes de réalisation de la présente invention concernent un procédé de commande du déploiement d'une plateforme informatique en nuage, un serveur et un support d'informations. Le procédé consiste : à déterminer un nœud de commande servant à commander un nœud de fonction ; à acquérir une première instruction de déploiement comprenant des informations d'attribution de rôle de nœud ; à initialiser et à activer un premier service dans le nœud de commande, de telle sorte que le nœud de commande ajoute des serveurs cibles et attribue un rôle de nœud à ce dernier en fonction des informations d'attribution de rôle de nœud ; à déterminer les serveurs cibles en tant que nœuds de fonction à commander par le nœud de commande ; à configurer des paramètres de déploiement des nœuds de fonction en fonction d'un script de déploiement, et à initialiser et à activer un second service associé au rôle de nœud ; et à détecter si les nœuds déterminés sont reliés, et si non, à régler les paramètres de déploiement des nœuds de fonction non reliés en fonction du script de déploiement, de telle sorte que les nœuds de fonction non reliés deviennent reliés. L'invention permet un réglage et une liaison automatiques d'un grand nombre de nœuds, ce qui permet de former une plate-forme complète et utilisable, de réduire le nombre d'étapes de déploiement manuel, et d'améliorer l'efficacité de déploiement.
PCT/CN2018/107908 2018-08-03 2018-09-27 Procédé de commande du déploiement d'une plateforme informatique en nuage, serveur et support d'informations WO2020024413A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810884475.X 2018-08-03
CN201810884475.XA CN109067877B (zh) 2018-08-03 2018-08-03 一种云计算平台部署的控制方法、服务器及存储介质

Publications (1)

Publication Number Publication Date
WO2020024413A1 true WO2020024413A1 (fr) 2020-02-06

Family

ID=64831714

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107908 WO2020024413A1 (fr) 2018-08-03 2018-09-27 Procédé de commande du déploiement d'une plateforme informatique en nuage, serveur et support d'informations

Country Status (2)

Country Link
CN (1) CN109067877B (fr)
WO (1) WO2020024413A1 (fr)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111371579B (zh) * 2018-12-26 2023-04-07 中兴通讯股份有限公司 云平台部署方法、装置、服务器及存储介质
CN109981348A (zh) * 2019-02-26 2019-07-05 启迪云计算有限公司 一种云节点混合部署方法
CN109995878A (zh) * 2019-04-12 2019-07-09 成都四方伟业软件股份有限公司 资源库共享方法及分布式集群系统
CN111045599A (zh) * 2019-10-31 2020-04-21 平安科技（深圳）有限公司 分布式存储系统的参数配置方法、装置及计算机设备
CN111897539B (zh) * 2020-07-20 2024-03-29 国云科技股份有限公司 一种根据服务角色的进行应用部署的方法及装置
CN112003754A (zh) * 2020-08-25 2020-11-27 北京浪潮数据技术有限公司 一种OpenStack集群的可视化节点注册方法
CN112995169B (zh) * 2021-02-22 2022-12-06 中国工商银行股份有限公司 防火墙部署方法和装置
CN113064600B (zh) * 2021-04-20 2022-12-02 支付宝(杭州)信息技术有限公司 部署应用的方法和装置
CN114221808B (zh) * 2021-12-14 2024-02-06 平安壹钱包电子商务有限公司 安全策略部署方法、装置、计算机设备及可读存储介质
CN114244836B (zh) * 2021-12-17 2023-12-05 杭州视洞科技有限公司 一种混合云场景中服务器批量管理方法
CN114244891B (zh) * 2021-12-22 2024-01-23 北京天融信网络安全技术有限公司 一种容器间的通信方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106506636A (zh) * 2016-11-04 2017-03-15 武汉噢易云计算股份有限公司 一种基于OpenStack的云平台集群方法及系统
US20170244601A1 (en) * 2016-02-23 2017-08-24 Cisco Technology, Inc. Collaborative hardware platform management
CN107769938A (zh) * 2016-08-16 2018-03-06 北京金山云网络技术有限公司 一种Openstack平台支持多网络区域的系统和方法
CN107819851A (zh) * 2017-11-10 2018-03-20 郑州云海信息技术有限公司 一种Openstack单节点部署与虚拟化系统ICS的对接方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103501350B (zh) * 2013-10-17 2017-05-31 中国联合网络通信集团有限公司 一种云计算平台中SaaS应用部署的方法及装置
US9609023B2 (en) * 2015-02-10 2017-03-28 International Business Machines Corporation System and method for software defined deployment of security appliances using policy templates
CN104754032A (zh) * 2015-02-27 2015-07-01 浪潮集团有限公司 一种部署OpenStack的方法及装置
CN105426208A (zh) * 2015-11-16 2016-03-23 山东超越数控电子有限公司 一种云计算系统OpenStack离线自动安装方法
CN107172208B (zh) * 2017-06-30 2021-09-14 联想(北京)有限公司 服务器的部署方法及其系统
CN107483243A (zh) * 2017-08-09 2017-12-15 鹤云来科技有限公司 一种OpenStack平台的自动部署方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170244601A1 (en) * 2016-02-23 2017-08-24 Cisco Technology, Inc. Collaborative hardware platform management
CN107769938A (zh) * 2016-08-16 2018-03-06 北京金山云网络技术有限公司 一种Openstack平台支持多网络区域的系统和方法
CN106506636A (zh) * 2016-11-04 2017-03-15 武汉噢易云计算股份有限公司 一种基于OpenStack的云平台集群方法及系统
CN107819851A (zh) * 2017-11-10 2018-03-20 郑州云海信息技术有限公司 一种Openstack单节点部署与虚拟化系统ICS的对接方法

Also Published As

Publication number Publication date
CN109067877A (zh) 2018-12-21
CN109067877B (zh) 2021-08-24

Similar Documents

Publication Publication Date Title
WO2020024413A1 (fr) Procédé de commande du déploiement d'une plateforme informatique en nuage, serveur et support d'informations
US10986174B1 (en) Automatic discovery and configuration of server nodes
US7783788B1 (en) Virtual input/output server
US9547624B2 (en) Computer system and configuration management method therefor
US20190222488A1 (en) Portable and flexible deployment of servers
US8830870B2 (en) Network adapter hardware state migration discovery in a stateful environment
US8307362B1 (en) Resource allocation in a virtualized environment
US9929903B2 (en) System and method for automated network configuration
US9588807B2 (en) Live logical partition migration with stateful offload connections using context extraction and insertion
CN108322467B (zh) 基于ovs的虚拟防火墙配置方法、电子设备及存储介质
CN114070723B (zh) 裸金属服务器的虚拟网络配置方法、系统及智能网卡
US20070168563A1 (en) Single logical network interface for advanced load balancing and fail-over functionality
EP3332325B1 (fr) Procédés, appareil, et systèmes pour assurer l'accès à des ports série de machines virtuelles dans des applications virtuelles auto-déployées
CN104572372A (zh) 一种服务器性能测试环境搭建系统及方法
US20070124573A1 (en) Method for rapid startup of a computer system
WO2020232890A1 (fr) Procédé et dispositif de création d'application d'équilibrage de charge, dispositif informatique et support de stockage
CN104506403B (zh) 一种支持多级隔离的虚拟网络管理方法
CN109857464B (zh) 用于平台部署与操作移动操作系统的系统及其方法
US20040221298A1 (en) Network device drivers using a communication transport
US10778467B2 (en) Method for providing virtual CPE service by using single internet line and network function virtualization cloud
US8995424B2 (en) Network infrastructure provisioning with automated channel assignment
CN113918174A (zh) 裸金属服务器的部署方法、部署控制器及服务器集群
WO2020263640A1 (fr) Service de traitement de paquets sans serveur avec intégration de réseau virtuel isolé
US20230325203A1 (en) Provisioning dpu management operating systems using host and dpu boot coordination
US20240028375A1 (en) Control plane lifecycle management with dpu devices

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18928509

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 25.03.2021.)

122 Ep: pct application non-entry in european phase

Ref document number: 18928509

Country of ref document: EP

Kind code of ref document: A1