WO2019076369A1 - 一种云平台部署方法、装置、电子设备及可读存储介质 - Google Patents

一种云平台部署方法、装置、电子设备及可读存储介质 Download PDF

Info

Publication number
WO2019076369A1
WO2019076369A1 PCT/CN2018/111007 CN2018111007W WO2019076369A1 WO 2019076369 A1 WO2019076369 A1 WO 2019076369A1 CN 2018111007 W CN2018111007 W CN 2018111007W WO 2019076369 A1 WO2019076369 A1 WO 2019076369A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud platform
node
deployment
component
service
Prior art date
Application number
PCT/CN2018/111007
Other languages
English (en)
French (fr)
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 WO2019076369A1 publication Critical patent/WO2019076369A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • 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
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • 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/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • 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
    • 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 cloud computing technologies, and in particular, to a cloud platform deployment method, apparatus, electronic device, and readable storage medium.
  • OpenStack is an open source cloud computing management platform project that supports multiple types of cloud environments. The goal is to provide a cloud computing management platform that is simple to implement, scalable, rich, and standard.
  • Openstack When deploying a cloud platform based on Openstack, the deployment process of the cloud platform is slow because Openstack is composed of several major components to complete the specific work, and the components and deployment tools are numerous. The rapid deployment of Openstack-based cloud platforms has long been a problem that Openstack developers have tried to solve.
  • the purpose of the embodiment of the present application is to provide a cloud platform deployment method, device, electronic device, and readable storage medium, so as to implement rapid deployment of the cloud platform.
  • the specific technical solutions are as follows:
  • An embodiment of the present application provides a cloud platform deployment method, where the method includes: acquiring an installation package of multiple cloud platform components, determining a configuration file for automatically installing multiple installation packages; determining the multiple installations After the packets are not dependent, the plurality of installation packages and the configuration file are created as image files; the image files are respectively installed in each node of the cloud platform, so that the nodes are installed with the cloud platform components; The standard library configures and starts the services in the cloud platform components corresponding to the respective nodes.
  • the cloud platform deployment method of the embodiment of the present application further includes: if an operation instruction for deleting a node in the cloud platform is received, stopping a service in a component corresponding to the node to be deleted, and Deleting the information of the node to be deleted; if receiving the operation instruction of adding the node, installing the image file in the added node, configuring and starting the service in the cloud platform component corresponding to the added node through the standard library.
  • the configuring, by the standard library, the services in the cloud platform component corresponding to the nodes the following: configuring the current to-be-configured service through the standard library, after the current configured service configuration is successful, The service to be configured after the current service to be configured is configured by using the standard library; if the configuration of the current service to be configured fails, the service that has been successfully configured is retained, and the service before the current service to be configured is successfully configured through the standard library. .
  • the method before the configuring, by the standard library, the services in the cloud platform component corresponding to the nodes, the method further includes: according to the nodes and the cloud platform corresponding to the nodes The component, the deployment order of the nodes and the deployment order of the cloud platform components corresponding to the nodes are set by the standard library; and the services in the cloud platform component corresponding to the nodes are configured and started by the standard library, including: According to the deployment order of the nodes and the deployment order of the cloud platform components corresponding to the nodes, the services in the cloud platform components corresponding to the nodes are configured and started through the standard library.
  • the installing the image file in each node of the cloud platform includes: installing the image file in each node according to the configuration file in the image file. package.
  • the cloud platform component includes a first component; and the acquiring an installation package of the plurality of cloud platform components includes: when the installation package of the first component is included in the local server and the official server Obtaining an installation package of the first component from the local server; when the installation package of the first component is not included in the local server, and the installation package of the first component is included in the official server, The installation package of the first component is obtained in the official server.
  • the standard library is a Python standard library.
  • the embodiment of the present application provides a cloud platform deployment device, where the device includes: an installation package acquisition module, configured to acquire installation packages of multiple cloud platform components, and determine a configuration file for automatically installing multiple installation packages;
  • An image file creation module is configured to: after determining that there is no dependency between the plurality of installation packages, the plurality of installation packages and the configuration file are created as an image file; and the image file installation module is set to be respectively on the cloud platform.
  • the image file is installed in each node, so that each node installs a cloud platform component; the cloud platform component deployment module is configured to configure and start a service in the cloud platform component corresponding to each node by using a standard library.
  • the cloud platform deployment apparatus of the embodiment of the present application further includes: a node deletion module, configured to: if receiving an operation instruction for deleting a node in the cloud platform, in a component corresponding to the node to be deleted The service is stopped, and the information of the node to be deleted is deleted; the node is added to the module, and if the operation instruction of adding the node is received, the image file is installed in the added node, and the increase is configured through the standard library.
  • the node corresponds to the service in the component.
  • the cloud platform component deployment module is configured to configure the current to-be-configured service through the standard library, and after the current to-be-configured service is successfully configured, configure the current to-be-configured service through the standard library.
  • the service is configured. If the current configuration of the service to be configured fails, the service that has been configured successfully is saved.
  • the cloud platform deployment apparatus of the embodiment of the present application further includes: a deployment order setting module, configured to: before configuring, by the standard library, the services in the cloud platform component corresponding to each node, And setting a deployment order of the nodes and a deployment order of the cloud platform components corresponding to the nodes by using a standard library according to the cloud platform components corresponding to the nodes and the nodes; and setting the cloud platform component deployment module to The services in the cloud platform component corresponding to each node are configured and started by the standard library according to the deployment order of the nodes and the deployment order of the cloud platform components corresponding to the nodes.
  • the image file installation module is configured to install an installation package in the image file in each node according to the configuration file in the image file.
  • the cloud platform component includes a first component;
  • the installation package obtaining module includes: a first obtaining submodule, configured to include the first component in both the local server and the official server When the package is installed, the installation package of the first component is obtained from the local server;
  • the second acquisition submodule is configured to: when the local server does not include the installation package of the first component, and the official server includes When the package of the first component is installed, the installation package of the first component is obtained from the official server.
  • the standard library is a Python standard library.
  • An embodiment of the present application provides an electronic device, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory complete communication with each other through the communication bus;
  • the memory is configured to store a computer program, and the processor is configured to implement the cloud platform deployment method step of any of the foregoing when the program stored on the memory is executed.
  • the embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by the processor, implements the cloud platform deployment method steps of any of the foregoing.
  • the embodiment of the present application provides a computer program product, when it is run on a computer, causing the computer to execute the cloud platform deployment method steps described in any of the above.
  • the cloud platform deployment method, device, electronic device and readable storage medium determine the configuration file for automatically installing multiple installation packages by acquiring installation packages of multiple cloud platform components; After there is no dependency between the installation packages, multiple installation packages and configuration files are created as image files; the image files are installed on each node of the cloud platform, so that each node installs the cloud platform components; the standard library is configured and started.
  • the image file in the embodiment of the present application includes the installation package required for deploying all the roles in the cloud platform, and the installation package of the cloud platform component in the image file is automatically installed in each node, so that the cloud platform is The deployment process is faster.
  • the deployment process of the cloud platform is implemented by a standard library, and the standard library code structure is simple and easy to understand, and is easy to expand and maintain, so that the cloud platform can be quickly deployed.
  • the standard library code structure is simple and easy to understand, and is easy to expand and maintain, so that the cloud platform can be quickly deployed.
  • FIG. 1 is a flowchart of a cloud platform deployment method according to an embodiment of the present application
  • FIG. 2 is a flowchart of a cloud platform deployment method according to another embodiment of the present application.
  • FIG. 3 is a flowchart of a cloud platform deployment method according to still another embodiment of the present application.
  • FIG. 5 is a structural diagram of a cloud platform deployment apparatus according to an embodiment of the present application.
  • FIG. 6 is a structural diagram of a cloud platform deployment apparatus according to another embodiment of the present application.
  • FIG. 7 is a structural diagram of an electronic device according to an embodiment of the present application.
  • the Openstack cloud platform provides IaaS solutions through a variety of complementary services.
  • the IaaS includes: cloud query, cloud computing, cloud storage, cloud security, etc.
  • the deployment personnel are required to master the existing deployment tools. Relevant knowledge, so that it is possible to completely solve the problems encountered during the deployment process. Because some deployment tools are based on unfamiliar programming languages, deployers are more difficult to deploy when deploying to the cloud platform, resulting in a slower deployment of the cloud platform.
  • the Openstack community provides the deployment of the devstack tool for the Openstack test environment.
  • the devstack tool is based on bash (Bourne Again shell). It is difficult to understand, debugging is very difficult, and scalability is also poor.
  • bash is a kind of shell. An instance, where the shell is a program, the shell provides a row-oriented, interactive interface between the user and the operating system.
  • major Openstack companies have also launched their own deployment tools, but most of them are based on existing deployment tools such as puppet, chef and ansible.
  • the Openstack community can also deploy cloud platforms through these deployment tools.
  • the embodiment of the present application provides a cloud platform deployment method, device, electronic device, and readable storage medium, so as to implement rapid deployment of the cloud platform.
  • the cloud platform deployment method provided by the embodiment of the present application is first introduced in detail.
  • FIG. 1 is a flowchart of a cloud platform deployment method according to an embodiment of the present application, including the following steps:
  • Each cloud platform component can include at least one service.
  • the cloud platform component refers to components required for deploying the cloud platform, and the cloud platform component may include: keystone, neutron, nova, glance, cinder, heat, and ironic, and each cloud platform component has a corresponding Installation package.
  • the core functions of the cloud platform include: computing, storage and network, corresponding to nova, cinder and neutron.
  • nova also provides support for a variety of hypervisors, such as KVM (Kernel-based Virtual Machine) and Xen, etc., where Xen is an open source virtual machine monitor.
  • Cinder provides management of storage resources and can manage professional storage devices provided by various vendors.
  • Neutron provides management of network resources.
  • the configuration file can be used to automatically install the installation package.
  • the configuration file can record various parameters that are required to be manually filled in during the typical installation process.
  • the configuration file can record more Installation packages for cloud platform components, various parameters required during the installation process.
  • the configuration file for automatically installing the plurality of installation packages can be determined.
  • the configuration file can be a Kickstart file.
  • the Kickstart file is a configuration file that defines the Linux installation process.
  • the Kickstart file can not only record various parameters required for the installation package of multiple cloud platform components during the installation process, but also record There are various parameters required during the Linux installation, such as the time zone to be used in a Linux system, how to partition a drive, or which packages should be installed.
  • the Linux installation process can be automated with pre-defined requirements and automated installation of multiple cloud platform components can be automated. Automated installation can make the deployment process easier and faster when deploying a large number of nodes in the cloud platform.
  • the Kickstart file can include:
  • the above Kickstart file defines the Linux system authentication information, the Linux system language, the system language used in the Linux system, and the root password of the Linux system. And other information. Then, the Kickstart file can set the above information in the Linux system at the same time during the installation of the installation package.
  • the installation package and configuration files of each cloud platform component can be created as an image file, for example, the installation package and the mkisofs tool are used.
  • the configuration file is created as an image file, and mkisofs can make the specified directory and file into an ISO 9660 image file for burning the disc.
  • the image file contains the installation package required to deploy all the cloud platform components and the configuration file that guides each installation package for automatic installation. This way, the cloud platform deployment process can be made faster.
  • each node of the cloud platform refers to each server in the cloud platform, that is, each node is a server. If a computing service is deployed in a server, the server is a compute node, and if a storage service is deployed in a server, the server is a storage node.
  • the installed image files are the same for different nodes.
  • the operating system installed in different nodes is an operating system customized by the embodiment of the present application.
  • the customized operating system adds installation packages of each cloud platform component and their dependency packages based on centos7, wherein centos7 (Community Enterprise) Operating System 7, the seventh-generation community enterprise operating system) is one of the Linux distributions.
  • the installation package is an rpm format installation package.
  • the dependency package is mainly a Python standard library, such as requests, six, sqlalchemy, etc.
  • Python is an object-oriented interpreted computer programming language
  • the Python language is simple, easy to read and extensible
  • the Python standard library is a standard library already used in Openstack.
  • the embodiment of the present application uses the Python language.
  • the installation file can be automatically installed by using the configuration file.
  • installing the image file in each node of the cloud platform may include: according to the configuration file in the image file, respectively Install the installation package in the image file in each node.
  • the installation package of the cloud platform component installed in each node of the cloud platform may be the same; in this implementation manner, the installation package of each cloud platform component is installed in each node of the cloud platform, It can facilitate the subsequent configuration of the roles of each node in the cloud platform.
  • the role of each node in the cloud platform may be determined in advance, and the cloud platform component that needs to be installed in each role may be pre-stored in the configuration file.
  • the configuration file may be based on the configuration file. In the nodes of the cloud platform, only the cloud platform components corresponding to the roles required for the node are installed. In this case, the storage space of each node can be saved to some extent.
  • the standard library may be a Python standard library.
  • the main functions of the Python standard library include: 1. Text processing, including: text formatting, regular expression matching, text difference calculation and merging, Unicode support, binary data processing. And other functions; 2. File processing, including: file operations, creating temporary files, file compression and archiving, operation configuration files, etc.; 3. Operating system functions, including: thread and process support, IO multiplexing, date and time processing, Call system functions, logs and other functions; 4. Network communication, including: network sockets, SSL encryption communication, asynchronous network communication and other functions; 5.
  • Network protocol support HTTP (HyperText Transfer Protocol, Hypertext Transfer Protocol), FTP ( File Transfer Protocol, SMTP (Simple Mail Transfer Protocol), IMAP (Internet Mail Access Protocol), NNTP (Network News Transfer Protocol), etc.
  • Network protocol and provides a framework for writing web servers; 6.W3C Support, including: HTML (HyperText Markup Language), SGML (Standard Generalized Markup language), XML processing; 7. Other functions, including: international support, mathematical operations, Hash, etc. .
  • the Python standard library provides additional features such as system management, network communication, text processing, database interfaces, graphics systems, and XML (Extensible Markup Language) processing. Because the Python standard library is simple and easy to understand, it reduces the debugging and learning costs of deployers, and is easy to extend and maintain, so that deployers can quickly deploy to the cloud platform.
  • XML Extensible Markup Language
  • the Python standard library is a standard library already used in Openstack, and the cloud platform is deployed based on the Python standard library, so that anyone familiar with Openstack can quickly familiarize with the cloud platform deployment process.
  • each node in the cloud platform may be installed with an installation package of each cloud platform component, that is, each node is installed with the same installation package.
  • the cloud platform components to be configured corresponding to the nodes may be different, that is, each node may be configured with different services.
  • the service in each cloud platform component is fixed, and each cloud platform component can have multiple services, but different services in the same cloud platform component can be deployed in different nodes, that is, different nodes are enabled. Services in the same cloud platform component can be different.
  • the services in the cloud platform component can be set in the form of a configuration file.
  • One service in each cloud platform component can have multiple configuration files, and the process of configuring the service can be understood as a process of modifying the configuration file.
  • the configuration file of the agent service can include the following:
  • Admin_password cloudos
  • information such as auth_version (authentication version), hash_algorithms (hash algorithm), signing_dir (signature path) in the above configuration file may be set, and of course, the above information in the configuration file may be modified.
  • the authentication version is v2.0.
  • the authentication version may be modified to v2.1.
  • the special configuration information may also be added to the configuration file.
  • the startup service is to start the service, and the startup service command can be executed through the subprocess library in the Python standard library. If the service needs to be managed by pacemaker, you can execute the command that layermaker creates the resource; if the service does not need to be managed by pacemaker, you can execute the command with systemd. For example, you can call the startup command: systemctl start mysql to start the service.
  • Pacemaker is a cluster resource manager, which uses the message and member management capabilities provided by the cluster infrastructure (OpenAIS, heartbeat or corosync) to detect and recover from node or resource level failures, that is, nodes that avoid cloud platform failure. The impact of achieving maximum availability of cluster services.
  • OpenAIS cluster infrastructure
  • heartbeat or corosync corosync
  • the cloud platform deployment method of the embodiment of the present application determines a configuration file for automatically installing multiple installation packages by acquiring installation packages of multiple cloud platform components; after determining that there is no dependency between multiple installation packages, The installation package and the configuration file are created as image files.
  • the image files are installed on each node of the cloud platform to enable the nodes to install the cloud platform components.
  • the services in the cloud platform components corresponding to each node are configured and started.
  • the embodiment of the present application makes the deployment process of the cloud platform faster by customizing the image file and automatically installing the installation package of the cloud platform component in the image file in each node.
  • the deployment process of the cloud platform is implemented by a standard library, and the standard library code structure is simple and easy to understand, and is easy to expand and maintain, so that the cloud platform can be quickly deployed.
  • the configuring, and starting, the service in the cloud platform component corresponding to each node by using the standard library may include: configuring the current service to be configured through the standard library, and after the current configuration of the service to be configured is successful, The standard library is configured with the service to be configured after the current service to be configured. If the service configuration of the current service is unsuccessful, the service that has been successfully configured is saved.
  • the service successfully configured in each configuration process may be retained, so that the configuration cost of the cloud platform may be saved to a certain extent. That is, the service to be configured is configured through the standard library. After the current configuration of the service to be configured is successful, the service to be configured after the current service to be configured is configured through the standard library; if the current configuration of the service to be configured fails, the service that has been successfully configured is retained. The services before the current service to be configured are successfully configured through the standard library.
  • FIG. 2 is a flowchart of a cloud platform deployment method according to another embodiment of the present application, including the following steps:
  • S203 Install an image file in each node of the cloud platform, so that each node installs a cloud platform component.
  • the cloud platform includes many nodes. Generally, services provided by different nodes are different. Therefore, services deployed by different nodes are different.
  • the deployment order of the nodes can be set through the oslo_config library in the Python standard library; then the deployment order of the cloud platform components corresponding to each node is set separately. This can be set by defining a step file.
  • the nodes in the cloud platform include: a management node, a computing node, a network node, and a storage node.
  • the deployment order of each node and the deployment order of the cloud platform components corresponding to each node are as follows: the deployment order of each node may be: first deployment management Nodes, redeploy computing nodes, and then deploy network nodes, and finally deploy storage nodes; the deployment order of cloud platform components corresponding to each node is:
  • the steps of the management node deployment can be: 1) configure and start the pacemaker service, start the virtual IP address through the pacemaker, and use the IP address as the IP address to access the cloud platform; 2) configure and start the message middleware service (rabbitmq)
  • the message middleware is used for communication between services in the Openstack component; 3) configuring and starting the database service (mysql+galera), which is used for data storage of Openstack components; 4) configuring and starting the cache service (memcache)
  • the cache service can cache the authentication information in the user Openstack; 5) configure and start the Openstack component services including: keystone, neutron, nova, glance, cinder, heat, ironic, etc.; 6) configure and start the monitoring service (zabbix) ; 7) Configure and start the UI (User Interface) service.
  • the steps of the computing node deployment may be: 1) configuring and starting the network agent service; 2) configuring and starting the computing service (nova-compute); 3) configuring and starting the monitoring agent service.
  • the configuration of the network node can be: 1) configuring and starting the network dhcp (Dynamic Host Configuration Protocol) service; 2) configuring and starting the network layer 2 service; 3) configuring and starting the network layer 3 service; 4) Configure and start the network VPN (Virtual Private Network) service; 5) Configure and start the network load balancing service; 6) Configure and start the monitoring agent service.
  • network dhcp Dynamic Host Configuration Protocol
  • VPN Virtual Private Network
  • the storage node deployment steps can be: 1) discover all data disks of the node; 2) format all the data disks of the node and mount them; 3) start the storage service.
  • the deployment order of the cloud platform components corresponding to each node refers to: the deployment order of the services in the cloud platform components corresponding to each node, after determining the deployment order of each node and the deployment order of the cloud platform components corresponding to each node, You can define the step file.
  • the step file records the deployment order of the cloud platform components corresponding to each node. In this way, you can follow the step file to perform the deployment process.
  • the step file can include:
  • the number of execution steps of each service in the node is set in the above step file.
  • the step file can be used to determine the services that need to be deployed in the node and the process of deploying each service. During the deployment process, the number of steps in the step file is incremented by one for each deployment of a service. The current deployment progress can be determined by counting the number of steps in the step file.
  • the deployment when the node is deployed, the deployment may be performed according to the execution steps in S204. Recording the deployment of the node by the number of execution steps and the step count in the step file can clearly determine the progress of the deployment, and record the startup sequence between the services in the form of a step file to ensure that the associated service is normal. start up.
  • S201, S202, and S203 are the same as S101, S102, and S103 in the embodiment of FIG. 1, all implementations of S101, S102, and S103 are applicable to the embodiment shown in FIG. 2, and all of the same or similar beneficial effects can be achieved. , will not repeat them here.
  • the cloud platform deployment method of the embodiment of the present application determines a configuration file for automatically installing multiple installation packages by acquiring installation packages of multiple cloud platform components; after determining that there is no dependency between multiple installation packages,
  • the installation package and configuration file are created as image files; the installation packages of the cloud platform components in the image file are automatically installed in each node of the cloud platform; the deployment order of each node and each node are set according to the components corresponding to each node and each node.
  • the deployment order of the corresponding components is configured according to the deployment order of each node and the deployment order of the cloud platform components corresponding to each node, and the services in the cloud platform components corresponding to each node are configured and started through the standard library.
  • the image file is customized, and the image file is automatically installed in each node.
  • the nodes are deployed, the nodes are deployed according to the preset deployment sequence, so that the related services can be started normally.
  • the deployment process of the cloud platform is implemented by a standard library, and the standard library code structure is simple and easy to understand, and is easy to expand and maintain, so that the cloud platform can be quickly deployed.
  • FIG. 3 is a flowchart of a cloud platform deployment method according to another embodiment of the present application, including the following steps:
  • Each cloud platform component can include at least one service.
  • the information of the node to be deleted may include: an identifier of the node to be deleted in the cloud platform, an installation package installed by the node to be deleted, and operation log information executed by the node to be deleted in the cloud platform. and many more.
  • the cloud platform in the embodiment of the present application has strong scalability.
  • the service in the cloud platform component corresponding to the node to be deleted may be Stopping, for example, if the computing node in the cloud platform needs to be deleted, then all services in the computing node can be stopped, and after the service in the computing node is stopped, the computing node will no longer be included in the cloud platform.
  • the information of the computing node can also be deleted, so that the occupation of the storage space can be reduced.
  • nodes in addition to deleting nodes in the cloud platform, nodes may also be added in the cloud platform.
  • the method of deploying the service is the same as the method of deploying the service of the existing node in the cloud platform.
  • the installation of the image file in step S303 is performed, that is, the installation package of the cloud platform component is installed, and then the standard is adopted.
  • the method of configuring and starting the service in the cloud platform component corresponding to the added node, the method of configuring the standard library and the method of starting the service may be similar to the step S104 in the embodiment of FIG. 1 or the step S205 in the embodiment of FIG. 2, and details are not described herein again.
  • the services that need to be configured and started in different nodes may be different. Therefore, the services configured and started in the added nodes may be different from the services configured and started in the nodes already existing in the cloud platform.
  • step S305 and S306 are after step S304, but there is no order restriction between step S305 and step S306.
  • the specific implementation manners of step S305 and step S306 may be based on a REST (Representational State Transfer) API (Application Programming Interface), and REST refers to a set of architectural constraints and in principle.
  • the cloud platform deployment method of the embodiment of the present application determines a configuration file for automatically installing multiple installation packages by acquiring installation packages of multiple cloud platform components; after determining that there is no dependency between multiple installation packages,
  • the installation package and configuration file are created as image files; the installation packages of the cloud platform components in the image file are automatically installed in each node of the cloud platform; the deployment order of each node and each node are set according to the components corresponding to each node and each node.
  • the deployment order of the corresponding components is configured according to the deployment order of each node and the deployment order of the cloud platform components corresponding to each node, and the services in the cloud platform components corresponding to each node are configured and started through the standard library.
  • the image file is customized and the image file is automatically installed in each node.
  • the nodes When the nodes are deployed, the nodes are deployed according to the preset deployment sequence, so that the cloud platform deployment process is faster.
  • the deployment process of the cloud platform is implemented by a standard library, and the standard library code structure is simple and easy to understand, and the cloud platform can be quickly deployed.
  • the cloud platform deployment method of the embodiment of the present application has strong scalability. After the cloud platform is deployed, the node may be added to the cloud platform, or the node already deployed in the cloud platform may be deleted, so that the cloud platform may be The nodes are flexibly deployed.
  • FIG. 4 is a flowchart of node deployment according to an embodiment of the present application, including the following steps:
  • the current number of steps refers to the number of steps in the step file.
  • the current number of steps can be counted from step 1 when the node is initially deployed.
  • S402. Determine whether there are unexecuted steps, if yes, execute S403; if no, go to S406, that is, the deployment ends.
  • the step number file may include the number of execution steps, that is, the number of steps required to complete the deployment of the cloud platform, and the number of steps, and the step number file is used to conveniently determine the deployment progress of the cloud platform, and each deployment is completed.
  • the step count is incremented by 1, and the step count after the increment of 1 can be regarded as the current step number, and the above judgment is whether there is an unexecuted step number, and it may be determined whether the current step number is Not more than the number of execution steps.
  • the representation determines that there are unexecuted steps, that is, the cloud platform is not deployed yet, and S403 is continued; when the current number of steps is greater than the number of execution steps, the representation is judged There are no unexecuted steps, that is, the current deployment completes the cloud platform.
  • each deployment completes a service, and the execution completes a number of steps, and the current step number is incremented by one.
  • the service deployment corresponding to the current step number fails, that is, the judgment result of S404 is no
  • the current deployment may be suspended, and the record may be suspended.
  • the current number of steps that is, the progress of the current deployment is recorded; and, the current number of steps can be recorded, and the number of steps of the staff can be notified, and when the staff solves the problem, the progress of the current deployment can be recorded based on the record.
  • the deployment of the cloud platform is continued, that is, redeployment starts from the service corresponding to the current number of steps.
  • the number of steps that have been successfully executed is retained, and the number of steps after the current number of steps is executed after the current number of steps is successfully executed.
  • each service in the cloud platform component can be configured (and deployed) through the template library jinja2 in the Python standard library, and the startup service command is executed through the subprocess library in the Python standard library.
  • acquiring an installation package of the plurality of cloud platform components includes: when the installation package of the first component is included in the local server and the official server, obtaining the installation package of the first component from the local server; When the installation package of the second component is not included in the local server, and the second component is included in the official server, the installation package of the second component is obtained from the official server; wherein the first component and the second component are components in the cloud platform component .
  • the installation package of the cloud platform component is stored in the server, and the installation package of the cloud platform component with the same name may be stored in the local server and the official server.
  • the installation package of the first component refers to the installation package of the component with the same name in the local server and the official server. At this point, the installation package of the first component is obtained preferentially from the local server.
  • the installation package of the second component refers to the installation package of the component that does not exist in the local server and exists in the official server. At this time, if the installation package of the second component is obtained, the installation package of the second component needs to be obtained from the official server.
  • the local server refers to a server in the cloud platform. For example, for a cloud platform of a website, the cloud platform component is stored in a server corresponding to the website; the official server refers to an official server that publishes the cloud platform component.
  • the installation package of the cloud platform component stored in the local server and the official server may be periodically updated. Therefore, when the cloud platform is deployed, the cloud platform component usually obtained from the local server or the official website server is installed. The package is up to date.
  • an installation package of a cloud platform component may be obtained from a local server or an official server through Yum.
  • Yum (Yellow dog UpdaterModified) is a Shell front-end package manager that automatically downloads installation packages from a specified server and installs them. It automatically handles the dependencies between installation packages and installs all dependent packages at once, without cumbersome Download and install again and again.
  • the cloud platform deployment method of the embodiment of the present application sets the installation package of the first component in the local server to a higher priority, and preferentially obtains the installation package in the local server. Compared with the installation package stored in the official server, the installation package stored in the local server is more suitable for the function of the deployment cloud platform, so that the cloud platform can be deployed more quickly. Therefore, the cloud platform deployment method in the embodiment of the present application is simpler. Fast.
  • the cloud platform component includes a first component
  • the acquiring the installation package of the plurality of cloud platform components may include: when the local server and the official server include the installation component of the first component at the same time, Obtaining the installation package of the first component from the local server; when the installation package of the first component is not included in the local server, and the installation package of the first component is included in the official server, obtaining the installation of the first component from the official server package.
  • the cloud platform deployment method of the embodiment of the present application may be configured to: when at least the installation package of the first component is included in the local server, obtain the installation package of the first component from the local server; and when the local server does not include the first component When the installation package is included and the installation package of the first component is included in the official server, the installation package of the first component is obtained from the official server.
  • FIG. 5 is a structural diagram of a cloud platform deployment device according to an embodiment of the present application, including: an installation package obtaining module 501. , configured to obtain an installation package of multiple cloud platform components, and determine a configuration file for automatically installing multiple installation packages; the image file creation module 502 is configured to be configured to determine that there is no dependency between multiple installation packages.
  • the installation package and the configuration file are created as an image file;
  • the image file installation module 503 is configured to install an image file in each node of the cloud platform, respectively, so that the nodes install the cloud platform component;
  • the cloud platform component deployment module 504 set to configure and start the services in the cloud platform components corresponding to each node through the standard library.
  • the cloud platform deployment device of the embodiment of the present application determines a configuration file for automatically installing multiple installation packages by acquiring installation packages of multiple cloud platform components; after determining that there is no dependency between multiple installation packages, The installation package and the configuration file are created as image files.
  • the image files are installed on each node of the cloud platform to enable the nodes to install the cloud platform components.
  • the services in the cloud platform components corresponding to each node are configured and started.
  • the embodiment of the present application makes the deployment process of the cloud platform faster by customizing the image file and automatically installing the installation package of the cloud platform component in the image file in each node.
  • the deployment process of the cloud platform is implemented by a standard library, and the standard library code structure is simple and easy to understand, and is easy to expand and maintain, so that the cloud platform can be quickly deployed.
  • the device in the embodiment of the present application is a device that applies the cloud platform deployment method, and all the embodiments of the cloud platform deployment method are applicable to the device, and all of the same or similar beneficial effects can be achieved.
  • FIG. 6 is a structural diagram of a cloud platform deployment apparatus according to another embodiment of the present application, including:
  • the installation package obtaining module 601 is configured to acquire installation packages of the plurality of cloud platform components, and determine a configuration file for automatically installing the plurality of installation packages.
  • the image file creation module 602 is configured to create a plurality of installation packages and configuration files as image files after determining that there is no dependency between the plurality of installation packages.
  • the image file installation module 603 is configured to install an image file in each node of the cloud platform, respectively, so that the nodes install the cloud platform component.
  • the cloud platform component deployment module 604 is configured to configure and start a service in a cloud platform component corresponding to each node through a standard library.
  • the node deletion module 605 is configured to stop the service in the cloud platform component corresponding to the node to be deleted, and delete the information of the node to be deleted, if the operation instruction of deleting the node in the cloud platform is received.
  • the node adding module 606 is configured to: if an operation instruction of adding a node is received, install an image file in the added node, and configure and start a service in the cloud platform component corresponding to the added node through the standard library.
  • the cloud platform deployment device of the embodiment of the present application determines a configuration file for automatically installing multiple installation packages by acquiring installation packages of multiple cloud platform components; after determining that there is no dependency between multiple installation packages,
  • the installation package and configuration file are created as image files; the installation packages of the cloud platform components in the image file are automatically installed in each node of the cloud platform; the deployment order of each node and each node are set according to the components corresponding to each node and each node.
  • the deployment order of the corresponding components is configured according to the deployment order of each node and the deployment order of the cloud platform components corresponding to each node, and the services in the cloud platform components corresponding to each node are configured and started through the standard library.
  • the embodiment of the present application automatically installs an image file by automatically modifying an image file in each node; and the deployment process of the cloud platform is implemented by a standard library, and the standard library code structure is simple and easy to understand, and is convenient for expansion and maintenance, so that the cloud can be quickly deployed.
  • platform When deploying each node, deploy each node according to the preset deployment sequence to ensure that the associated services start normally.
  • the cloud platform deployment device of the embodiment of the present application has strong scalability. After the cloud platform is deployed, the node may be added to the cloud platform, or the node that has been deployed in the cloud platform may be deleted, so that the cloud can be The nodes in the platform are flexibly deployed.
  • the cloud platform component deployment module is configured to configure the current to-be-configured service through the standard library, and after the current to-be-configured service is successfully configured, configure the current to-be-configured service through the standard library.
  • the service is configured. If the current configuration of the service to be configured fails, the service that has been configured successfully is saved.
  • the cloud platform deployment apparatus further includes: a deployment order setting module, configured to: before configuring, by the standard library, the services in the cloud platform component corresponding to each node, according to each node and The cloud platform component corresponding to each node sets the deployment order of each node and the deployment order of the cloud platform components corresponding to each node through the standard library; the cloud platform component deployment module is set to follow the deployment order of each node and the cloud platform corresponding to each node.
  • the deployment order of components through the standard library configuration and start the services in the cloud platform components corresponding to each node.
  • the image file installation module is configured to install the installation package in the image file in each node according to the configuration file in the image file.
  • the installation package obtaining module includes: a first obtaining submodule, configured to obtain, when the local server and the official server include the installation package of the first component, from the local server An installation package of the first component, the second acquisition submodule is configured to: when the installation package of the first component is not included in the local server, and the installation package of the first component is included in the official server, The installation package of the first component is obtained in the official server.
  • the standard library is a Python standard library.
  • FIG. 7 is a structural diagram of an electronic device according to an embodiment of the present application, including: a processor 701, a communication interface 702, a memory 703, and a communication bus 704.
  • the processor 701, the communication interface 702, and the memory 703 complete communication with each other through the communication bus 704; the memory 703 is configured to store a computer program; and the processor 701 is configured to execute the program stored on the memory 703 to implement any of the above The steps of the cloud platform deployment method.
  • the communication bus 704 mentioned by the above electronic device may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus.
  • the communication bus 704 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 7, but it does not mean that there is only one bus or one type of bus.
  • the communication interface 702 is used for communication between the above electronic device and other devices.
  • the memory 703 may include a RAM (Random Access Memory), and may also include a non-volatile memory such as at least one disk storage. In an embodiment, the memory may also be at least one storage device located remotely from the aforementioned processor.
  • RAM Random Access Memory
  • non-volatile memory such as at least one disk storage.
  • the memory may also be at least one storage device located remotely from the aforementioned processor.
  • the processor 701 may be a general-purpose processor, including: a CPU (Central Processing Unit), an NP (Network Processor), or the like; or a DSP (Digital Signal Processing).
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • other programmable logic device discrete gate or transistor logic device, discrete hardware component.
  • the processor determines a configuration file for automatically installing a plurality of installation packages by acquiring an installation package of the plurality of cloud platform components by executing a program stored on the storage; After there is no dependency between the installation packages, multiple installation packages and configuration files are created as image files; the installation packages of the cloud platform components in the image files are automatically installed in each node of the cloud platform; corresponding to each node and each node
  • the component sets the deployment order of each node and the deployment order of the components corresponding to each node, and configures and starts the services in the cloud platform components corresponding to each node according to the deployment order of each node and the deployment order of the cloud platform components corresponding to each node.
  • the image file is customized, and the image file is automatically installed in each node.
  • the nodes are deployed according to the preset deployment sequence, so that the related services can be started normally.
  • the cloud platform deployment device of the embodiment of the present application has strong scalability. After the cloud platform is deployed, the node may be added to the cloud platform, or the node that has been deployed in the cloud platform may be deleted, so that the cloud can be The nodes in the platform are flexibly deployed.
  • the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by the processor, the steps of any one of the cloud platform deployment methods are implemented.
  • the instructions stored in the computer readable storage medium of the embodiment of the present application are run on a computer, thereby obtaining a configuration file for automatically installing a plurality of installation packages by acquiring installation packages of the plurality of cloud platform components; After there is no dependency between the installation packages, multiple installation packages and configuration files are created as image files; the installation packages of the cloud platform components in the image files are automatically installed in each node of the cloud platform; corresponding to each node and each node
  • the cloud platform component sets the deployment order of each node and the deployment order of the components corresponding to each node, and configures and starts the cloud platform components corresponding to each node according to the deployment order of each node and the deployment order of the cloud platform components corresponding to each node. service.
  • the image file is customized, and the image file is automatically installed in each node.
  • the nodes are deployed according to the preset deployment sequence, so that the related services can be started normally.
  • the cloud platform deployment device of the embodiment of the present application has strong scalability. After the cloud platform is deployed, the node may be added to the cloud platform, or the node that has been deployed in the cloud platform may be deleted, so that the cloud can be The nodes in the platform are flexibly deployed.
  • the instructions stored in the computer readable storage medium of the embodiment of the present application are run on a computer, thereby obtaining a configuration file for automatically installing a plurality of installation packages by acquiring installation packages of the plurality of cloud platform components; After there is no dependency between the installation packages, multiple installation packages and configuration files are created as image files; the installation packages of the cloud platform components in the image files are automatically installed in each node of the cloud platform; corresponding to each node and each node
  • the cloud platform component sets the deployment order of each node and the deployment order of the components corresponding to each node, and configures and starts the cloud platform components corresponding to each node according to the deployment order of each node and the deployment order of the cloud platform components corresponding to each node. service.
  • the image file is customized, and the image file is automatically installed in each node.
  • the nodes are deployed according to the preset deployment sequence, so that the related services can be started normally.
  • the cloud platform deployment device of the embodiment of the present application has strong scalability. After the cloud platform is deployed, the node may be added to the cloud platform, or the node that has been deployed in the cloud platform may be deleted, so that the cloud can be The nodes in the platform are flexibly deployed.
  • the cloud platform deployment method, the device, the electronic device, the computer readable storage medium, and the computer program product provided by the embodiment of the present application enable the cloud platform deployment process by customizing the image file and automatically installing the image file in each node. Faster.
  • the deployment process of the cloud platform is implemented by a standard library, and the standard library code structure is simple and easy to understand, and is easy to expand and maintain, so that the cloud platform can be quickly deployed.
  • the nodes in the cloud platform can be added or the nodes already deployed in the cloud platform can be deleted, so that the nodes in the cloud platform can be flexibly deployed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Multimedia (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例提供了一种云平台部署方法、装置、电子设备及可读存储介质，应用于云计算技术领域，云平台部署方法包括：获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中安装镜像文件，以使得各节点安装云平台组件；通过标准库配置并启动各节点对应的云平台组件中的服务。本申请实施例中的镜像文件包含了部署云平台中所有角色所需要的安装包，通过在各节点中自动化安装镜像文件中的云平台组件的安装包，从而可以快速部署云平台。

Description

一种云平台部署方法、装置、电子设备及可读存储介质
本申请要求于2017年10月19日提交中国专利局、申请号为201710976922.X发明名称为“一种云平台部署方法、装置、电子设备及可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及云计算技术领域，特别是涉及一种云平台部署方法、装置、电子设备及可读存储介质。
背景技术
OpenStack是一个开源的云计算管理平台项目，支持多种类型的云环境，目标是提供实施简单、可大规模扩展、丰富且标准统一的云计算管理平台。
当基于Openstack部署云平台时，由于Openstack由几个主要的组件组合起来完成具体工作，并且组件和部署工具繁多，因此，云平台的部署过程较慢。基于Openstack的云平台的快速部署，一直以来都是Openstack开发人员极力解决的问题。
发明内容
本申请实施例的目的在于提供一种云平台部署方法、装置、电子设备及可读存储介质，以实现云平台的快速部署。具体技术方案如下：
本申请实施例提供了一种云平台部署方法，所述方法包括：获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定所述多个安装包之间无依赖后，将所述多个安装包及所述配置文件创建为镜像文件；分别在云平台的各节点中安装所述镜像文件，以使得所述各节点安装云平台组件；通过标准库配置并启动所述各节点对应的云平台组件中的服务。
在一种实施方式中，本申请实施例的云平台部署方法，还包括：若接收到删除所述云平台中节点的操作指令，将待删除的节点对应的组件中的服务停止，并将所述待删除的节点的信息删除；若接收到增加节点的操作指令，在增加的节点中安装所述镜像文件，通过标准库配置并启动所述增加的节点对应的云平台组件中的服务。
在一种实施方式中，所述通过标准库配置并启动所述各节点对应的云平台组件中的服务，包括：通过标准库配置当前待配置服务，在所述当前待配 置服务配置成功之后，通过标准库配置所述当前待配置服务之后的待配置服务；若所述当前待配置服务配置失败，保留已经配置成功的服务，其中，所述当前待配置服务之前的服务均通过标准库配置成功。
在一种实施方式中，在所述通过标准库配置并启动所述各节点对应的云平台组件中的服务之前，所述方法还包括：根据所述各节点及所述各节点对应的云平台组件，通过标准库设置所述各节点的部署顺序及所述各节点对应的云平台组件的部署顺序；所述通过标准库配置并启动所述各节点对应的云平台组件中的服务，包括：按照所述各节点的部署顺序及所述各节点对应的云平台组件的部署顺序，通过标准库配置并启动所述各节点对应的云平台组件中的服务。
在一种实施方式中，所述分别在云平台的各节点中安装所述镜像文件，包括：根据所述镜像文件中的配置文件，分别在所述各节点中安装所述镜像文件中的安装包。
在一种实施方式中，所述云平台组件中包括第一组件；所述获取多个云平台组件的安装包，包括：当本地服务器和官方服务器中同时包含所述第一组件的安装包时，从所述本地服务器中获取第一组件的安装包；当所述本地服务器中不包含所述第一组件的安装包、且所述官方服务器中包含所述第一组件的安装包时，从所述官方服务器中获取所述第一组件的安装包。
在一种实施方式中，所述标准库为Python标准库。
本申请实施例提供了一种云平台部署装置，所述装置包括：安装包获取模块，设置为获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；镜像文件创建模块，设置为在确定所述多个安装包之间无依赖后，将所述多个安装包及所述配置文件创建为镜像文件；镜像文件安装模块，设置为分别在云平台的各节点中安装所述镜像文件，以使得所述各节点安装云平台组件；云平台组件部署模块，设置为通过标准库配置并启动所述各节点对应的云平台组件中的服务。
在一种实施方式中，本申请实施例的云平台部署装置，还包括：节点删除模块，设置为若接收到删除所述云平台中节点的操作指令，将待删除的节点对应的组件中的服务停止，并将所述待删除的节点的信息删除；节点增加模块，设置为若接收到增加节点的操作指令，在增加的节点中安装所述镜像文件，通过标准库配置并启动所述增加的节点对应的组件中的服务。
在一种实施方式中，所述云平台组件部署模块设置为，通过标准库配置当前待配置服务，在所述当前待配置服务配置成功之后，通过标准库配置所述当前待配置服务之后的待配置服务；若所述当前待配置服务配置失败，保留已经配置成功的服务，其中，所述当前待配置服务之前的服务均通过标准库配置成功。
在一种实施方式中，本申请实施例的云平台部署装置，还包括：部署顺序设置模块，设置为在所述通过标准库配置并启动所述各节点对应的云平台组件中的服务之前，根据所述各节点及所述各节点对应的云平台组件，通过标准库设置所述各节点的部署顺序及所述各节点对应的云平台组件的部署顺序；所述云平台组件部署模块设置为，按照所述各节点的部署顺序及所述各节点对应的云平台组件的部署顺序，通过标准库配置并启动所述各节点对应的云平台组件中的服务。
在一种实施方式中，所述镜像文件安装模块设置为，根据所述镜像文件中的配置文件，分别在所述各节点中安装所述镜像文件中的安装包。
在一种实施方式中，所述云平台组件中包括第一组件；所述安装包获取模块，包括：第一获取子模块，设置为当本地服务器和官方服务器中同时包含所述第一组件的安装包时，从所述本地服务器中获取第一组件的安装包；第二获取子模块，设置为当所述本地服务器中不包含所述第一组件的安装包、且所述官方服务器中包含所述第一组件的安装包时，从所述官方服务器中获取所述第一组件的安装包。
在一种实施方式中，所述标准库为Python标准库。
本申请实施例提供了一种电子设备，包括：处理器、通信接口、存储器和通信总线，其中，所述处理器、所述通信接口、所述存储器通过所述通信总线完成相互间的通信；所述存储器，设置为存放计算机程序；所述处理器，设置为执行所述存储器上所存放的程序时，实现上述任一所述的云平台部署方法步骤。
本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时，实现上述任一所述的云平台部署方法步骤。
本申请实施例提供了一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一所述的云平台部署方法步骤。
本申请实施例提供的云平台部署方法、装置、电子设备及可读存储介质，通过获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中安装镜像文件，以使得各节点安装完成云平台组件；通过标准库配置并启动各节点对应的云平台组件中的服务。本申请实施例中的镜像文件包含了部署云平台中所有角色所需要的安装包，通过自定义镜像文件，并在各节点中自动化安装镜像文件中的云平台组件的安装包，使得云平台的部署过程更加快捷。并且，云平台的部署过程通过标准库实现，标准库代码结构简单易懂，便于扩展和维护，从而可以快速部署云平台。当然，实施本申请的任一产品或方法必不一定需要同时达到以上所述的所有优点。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请一种实施例的云平台部署方法的流程图；
图2为本申请另一种实施例的云平台部署方法的流程图；
图3为本申请又一种实施例的云平台部署方法的流程图；
图4为本申请一种实施例的节点部署流程图；
图5为本申请一种实施例的云平台部署装置的结构图；
图6为本申请另一种实施例的云平台部署装置的结构图；
图7为本申请一种实施例的电子设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
Openstack云平台通过各种互补的服务提供了IaaS的解决方案，IaaS包括：云查询、云计算、云存储、云安全等，现有的云平台部署过程中，要求部署 人员掌握已有部署工具的相关知识，这样才有可能彻底解决部署过程中遇到的问题。由于某些部署工具基于并不熟悉的编程语言开发，因此，部署人员在对云平台进行部署时部署难度增加，导致云平台的部署过程较慢。
例如：Openstack社区中提供了devstack工具设置为Openstack测试环境的部署，devstack工具基于bash(Bourne Again shell)，晦涩难懂，调试起来非常困难，扩展性也较差，其中，bash是shell的一种实例，而shell是一个程序，shell在用户和操作系统之间提供了一个面向行的可交互接口。另外，各大Openstack公司也都推出了自己的部署工具，不过它们大多都基于现有的一些部署工具如：puppet、chef以及ansible等。同时，Openstack社区也可以通过这些部署工具对云平台进行部署。
但是，如果采用现有的部署工具，就要求部署人员掌握这些已有工具的相关知识，这样才有可能彻底解决部署过程中遇到的问题。而且这些工具中某些工具基于并不熟悉的编程语言开发(例如，chef采用Ruby，Ruby是一种简单快捷的面向对象程序设计的脚本语言)，那么，在添加自定义功能时难度将会增加。同时，由于Openstack社区考虑到各个厂家不同的需求，导致在进行云平台部署时部署工具的配置异常复杂，因此，云平台的部署过程较慢。
为了解决云平台部署过程复杂的问题，本申请实施例提供了一种云平台部署方法、装置、电子设备及可读存储介质，以实现云平台的快速部署。
下面首先对本申请实施例所提供的云平台部署方法进行详细介绍。
参见图1，图1为本申请一种实施例的云平台部署方法的流程图，包括以下步骤：
S101，获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件。
其中，每一云平台组件可以包含至少一个服务。
本申请实施例中，云平台组件指的是部署云平台所需要的组件，云平台组件可以包括：keystone、neutron、nova、glance、cinder、heat和ironic等，每一个云平台组件都有对应的安装包。其中，云平台的核心功能包括：计算、存储和网络，分别对应nova、cinder和neutron。其中，nova还提供对多种Hypervisor的支持，如KVM(Kernel-based Virtual Machine，基于内核的虚拟机)和Xen等，其中，Xen是一个开放源代码虚拟机监视器。cinder提供了存储资源的管理，可以管理各个厂商提供的专业存储设备。neutron提供了网络资 源的管理。
其中，配置文件可以实现对安装包的自动化安装，该配置文件中可以记录有：记录典型的安装过程中所需人工干预填写的各种参数；本申请实施例中，该配置文件中可以记录多个云平台组件的安装包，在安装过程中所需的各种参数。为了实现云平台组件的安装包的自动化安装，在获取多个云平台组件的安装包之后，可以确定用于对多个安装包进行自动化安装的配置文件。该配置文件可以为Kickstart文件，Kickstart文件是一个定义了Linux安装过程的配置文件，该Kickstart文件不仅可以记录有多个云平台组件的安装包在安装过程中所需的各种参数，还可以记录有Linux安装过程中所需的各种参数，比如要在Linux系统中使用的时区、如何对驱动器进行分区、或者应该安装哪些软件包等。有了该Kickstart文件可以让Linux安装过程按照预先定义的要求进行自动化安装，并且可以自动进行多个云平台组件的自动化安装。在部署云平台中大量节点时通过自动化安装的方式可以使部署过程更加简单、快捷。
例如，Kickstart文件中可以包括：
#version＝DEVEL
#System authorization information
auth--enableshadow--passalgo＝sha512
#Use CDROM installation media
cdrom
#Use graphical install
graphical
#Run the Setup Agent on first boot
firstboot--enable
#ignoredisk--only-use＝sda
#Keyboard layouts
keyboard--vckeymap＝us--xlayouts＝'us'
#System language
lang en_US.UTF-8--addsupport＝zh_CN.UTF-8
#Root password
rootpw KS123！
#System timezone
timezone Asia/beijing--isUtc
ignoredisk--only-use＝sda
#Partition clearing information
clearpart--all--initlabel--drives＝sda
可以看出，上述Kickstart文件中定义了Linux系统鉴权信息(System authorization information)、Linux系统语言(system language)、在Linux系统中使用的时区(System language)、Linux系统的Root密码(Root password)等信息。那么，Kickstart文件在指导安装包安装的过程中，可以同时设置Linux系统中的上述信息。
S102，在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件。
本申请实施例中，为了使在安装各云平台组件的安装包时不相互影响，首先需要确定各云平台组件的安装包之间无依赖，具体可以通过命令：
rpm--initdb--dbpath/tmp/testdbrpm--test--dbpath/tmp/testdb*.rpm
确认各云平台组件的安装包之间是否依赖，其中，*.rpm为云平台组件的安装包，*为安装包的名称。
在确定各云平台组件的安装包之间无依赖后，为了减轻云平台维护的复杂性，可以将各云平台组件的安装包及配置文件创建为镜像文件，例如，通过mkisofs工具将安装包及配置文件创建为镜像文件，mkisofs可将指定的目录与文件制作为ISO 9660格式的镜像文件，以供刻录光盘。这样，镜像文件中包含了部署所有云平台组件所需要的安装包以及指导各安装包进行自动化安装的配置文件，通过该方式可以使云平台的部署过程更加快捷。
S103，分别在云平台的各节点中安装镜像文件，以使得各节点安装云平台组件。即，将云平台组件安装在云平台的各节点中。
其中，云平台的各节点指的是云平台中的各服务器，也就是说，每一个节点即为一个服务器。如果在一个服务器中部署计算服务，那么，该服务器即为计算节点，如果在一个服务器中部署存储服务，那么，该服务器即为存储节点。对于不同的节点，安装的镜像文件是相同的。而且，不同节点中安装的操作系统是本申请实施例定制的操作系统，该定制的操作系统基于centos7的基础上增加了各云平台组件的安装包以及它们的依赖包，其中，centos7(Community Enterprise Operating System 7，第七代社区企业操作系统) 是Linux发行版之一，安装包为rpm格式的安装包，依赖包主要是Python标准库，例如requests、six、sqlalchemy等。其中，Python是一种面向对象的解释型计算机程序设计语言，Python语言具有简洁性、易读性以及可扩展性，并且Python标准库为Openstack中已使用的标准库，本申请实施例通过python语言编写云平台的部署框架，任何熟悉Openstack的工作人员，均可以快速的熟悉该云平台的部署框架，可以减少调试和学习成本，从而可以对云平台进行快速部署。
本申请实施例中，由于配置文件可以实现对安装包进行自动化安装，在一种实现方式中，分别在云平台的各节点中安装镜像文件，可以包括：根据镜像文件中的配置文件，分别在各节点中安装镜像文件中的安装包。
在一种实现方式中，云平台的各节点中安装的云平台组件的安装包可以是相同的；在本实现方式中，云平台的各节点中均安装有各云平台组件的安装包，以可以便于后续对云平台中各节点的角色的配置。在另一种实现方式中，可以预先确定出云平台中各节点的角色，并且，该配置文件中可以预存有各角色所需安装的云平台组件；本实现方式中，可以是基于该配置文件，在云平台的各节点中，仅安装该节点所需配置的角色对应的云平台组件，此时，可以在一定程度上节省各节点的存储空间。
S104，通过标准库配置并启动各节点对应的云平台组件中的服务。
本申请实施例中，标准库可以是Python标准库，Python标准库的主要功能包括：1.文本处理，包括：文本格式化、正则表达式匹配、文本差异计算与合并、Unicode支持，二进制数据处理等功能；2.文件处理，包括：文件操作、创建临时文件、文件压缩与归档、操作配置文件等功能；3.操作系统功能，包括：线程与进程支持、IO复用、日期与时间处理、调用系统函数、日志等功能；4.网络通信，包括：网络套接字，SSL加密通信、异步网络通信等功能；5.网络协议，支持HTTP(HyperText Transfer Protocol，超文本传输协议)、FTP(File Transfer Protocol,文件传输协议)、SMTP(Simple Mail Transfer Protocol，简单邮件传输协议)、IMAP(Internet Mail Access Protocol，Internet邮件访问协议)、NNTP(Network News Transfer Protocol，网络新闻传输协议)等多种网络协议，并提供了编写网络服务器的框架；6.W3C格式支持，包括：HTML(HyperText Markup Language，超文本标记语言)、SGML(Standard Generalized Markup language，标准通用标记语言)、XML的处理；7.其它功能，包括：国际化支持、数学运算、Hash等。
由以上可见，Python标准库提供了系统管理、网络通信、文本处理、数据库接口、图形系统、XML(可扩展标记语言)处理等额外的功能。由于Python标准库简单易懂，减少了部署人员的调试和学习成本，而且便于扩展和维护，从而可以使部署人员快速对云平台进行部署。
本申请实施例中，Python标准库为Openstack中已使用的标准库，基于Python标准库部署云平台，使得任何熟悉Openstack的人能快速熟悉该云平台部署流程。
在一种实现方式中，云平台中各节点可以安装有各云平台组件的安装包，即各节点安装有相同的安装包。本实现方式中，虽然各节点中安装的安装包是相同的，但是，各节点对应的需配置的云平台组件可以是不同的，也就是说，各节点可以配置不同的服务。其中，每个云平台组件中的服务是固定的，并且，每个云平台组件可以有多个服务，但是，在不同节点中可以部署同一个云平台组件中不同的服务，即不同节点启用的同一云平台组件中的服务可以是不同的。云平台组件中的服务可以以配置文件的方式进行设置，每个云平台组件中的一个服务可以有多个配置文件，而配置服务的过程可以理解为修改配置文件的过程。
例如，agent服务的配置文件中可以包括以下内容：
auth_version＝v2.0
admin_tenant_name＝service
admin_user＝kos
admin_password＝cloudos
signing_dir＝/var/cache/nova/api
hash_algorithms＝md5
insecure＝false
本申请实施例中，可以设置上述配置文件中的auth_version(鉴权版本)、hash_algorithms(hash算法)、signing_dir(签名路径)等信息，当然也可以对配置文件中的上述信息进行修改。例如，上述鉴权版本是v2.0，本申请实施例中可以将鉴权版本修改为v2.1。另外，对于节点中一些特殊的配置信息来说，如节点的IP(Internet Protocol，互联网协议)地址等，还可以将该特殊的配置信息添加至配置文件中。
本申请实施例中，启动服务就是将服务开启，可以通过Python标准库中的 subprocess库执行启动服务命令。如果服务需要通过pacemaker进行管理，可以执行pacemaker创建资源的命令；如果服务不需要通过pacemaker管理，可以执行用systemd的命令，例如，可以调用启动命令：systemctl start mysql，将服务开启。其中，Pacemaker是一个集群资源管理器，它利用集群基础构件(OpenAIS、heartbeat或corosync)提供的消息和成员管理能力来探测并从节点或资源级别的故障中恢复，即避免云平台受到故障的节点的影响，以实现集群服务的最大可用性。
本申请实施例的云平台部署方法，通过获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中安装镜像文件，以使得各节点安装云平台组件；配置并启动各节点对应的云平台组件中的服务。本申请实施例通过自定义镜像文件，并在各节点中自动化安装镜像文件中的云平台组件的安装包，使得云平台的部署过程更加快捷。另外，云平台的部署过程通过标准库实现，标准库代码结构简单易懂，便于扩展和维护，从而可以快速部署云平台。
本申请的一种实施例中，所述通过标准库配置并启动各节点对应的云平台组件中的服务，可以包括：通过标准库配置当前待配置服务，在当前待配置服务配置成功之后，通过标准库配置当前待配置服务之后的待配置服务；若当前待配置服务配置失败，保留已经配置成功的服务，其中，当前待配置服务之前的服务均通过标准库配置成功。
本申请实施例中，可以保留每一次配置过程中配置成功的服务，以在一定程度上可以节省云平台的配置成本。即通过标准库配置当前待配置服务，在当前待配置服务配置成功之后，通过标准库配置当前待配置服务之后的待配置服务；若当前待配置服务配置失败，保留已经配置成功的服务，其中，当前待配置服务之前的服务均通过标准库配置成功。
参见图2，图2为本申请另一种实施例的云平台部署方法的流程图，包括以下步骤：
S201，获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件。
S202，在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件。
S203，分别在云平台的各节点中安装镜像文件，以使各节点安装云平台组件。
S204，根据各节点及各节点对应的云平台组件，通过标准库设置各节点的部署顺序及各节点对应的云平台组件的部署顺序。
具体的，云平台中包含很多个节点，通常，不同节点提供的服务是不同的，因此，不同节点部署的服务也是不同的。在对云平台的节点进行部署时，首先，可以根据需要部署的节点，通过Python标准库中的oslo_config库设置节点的部署顺序；然后分别设置每个节点对应的云平台组件的部署顺序。具体可以通过定义步数文件进行设置。
例如，云平台中的节点包括：管理节点、计算节点、网络节点和存储节点，各节点的部署顺序及各节点对应的云平台组件的部署顺序如下：各节点的部署顺序可以为：首先部署管理节点、再部署计算节点、进而部署网络节点、最后部署存储节点；各节点对应的云平台组件的部署顺序，为：
1、管理节点部署的步骤可以为：1)配置并启动pacemaker服务，通过pacemaker启动虚拟IP地址，可以将该IP地址作为访问云平台的IP地址；2)配置并启动消息中间件服务(rabbitmq)，该消息中间件用于Openstack组件中各服务之间通信；3)配置并启动数据库服务(mysql+galera)，该数据库用于Openstack各组件的数据存储；4)配置并启动缓存服务(memcache)，该缓存服务可以对用户Openstack中认证信息进行缓存；5)配置并启动Openstack各组件服务包括：keystone、neutron、nova、glance、cinder、heat、ironic等；6)配置并启动监控服务(zabbix)；7)配置并启动UI(User Interface，用户界面)服务。
2、计算节点部署的步骤可以为：1)配置并启动网络agent服务；2)配置并启动计算服务(nova-compute)；3)配置并启动监控agent服务。
3、网络节点部署的步骤可以为：1)配置并启动网络dhcp(Dynamic Host Configuration Protocol，动态主机配置协议)服务；2)配置并启动网络二层服务；3)配置并启动网络三层服务；4)配置并启动网络vpn(Virtual Private Network，虚拟专用网络)服务；5)配置并启动网络负载均衡服务；6)配置并启动监控agent服务。
4、存储节点部署的步骤可以为：1)发现节点所有数据磁盘；2)格式化节点所有数据磁盘并挂载；3)启动存储服务。
其中，各节点对应的云平台组件的部署顺序指的是：各节点对应的云平台组件中的服务的部署顺序，在确定各节点的部署顺序及各节点对应的云平台组件的部署顺序之后，可以定义步数文件，步数文件中记录各节点对应的云平台组件的部署顺序，这样，在进行部署时，可以按照步数文件执行部署过程。
例如，步数文件可以包括：
master_steps＝{
1:role_utils.init,
2:zookeeper.start_zookeeper.main,
#kdfs
3:kdfs.start_kdfs.config,
4:ntp.start_ntp.main,
5:start_pacemaker.main,
6:haproxy.start_haproxy.main,
7:mysql.start_mysql.main,
8:rabbitmq.start_rabbitmq.main,
9:memcache.start_memcached.main,
#openstack services
10:keystone.start_keystone.main,
11:glance.start_glance_api.main,
12:glance.start_glance_registry.main,
13:neutron.start_neutron_server.main,
14:neutron.start_neutron_ovs_agent.main,
15:neutron.start_neutron_metadata_agent.main,
#we only need to config l3_agent here
16:neutron.start_neutron_l3_agent.config,
17:neutron.start_neutron_dhcp_agent.main,
18:neutron.start_neutron_lbaas_agent.main,
19:neutron.start_neutron_vpn_agent.main,
20:nova.start_nova_api.main,
21:nova.start_nova_metadata_api.main,
}
可以看出，上述步数文件中设置了节点中各服务的执行步数。通过步数文件可以确定节点中需要部署的服务，以及部署各服务的过程。在部署过程中，每完成一个服务的部署，该步数文件中的步数计数加一。以通过步数文件中步数计数可以确定出当前的部署进度。
S205，按照各节点的部署顺序及各节点对应的云平台组件的部署顺序，通过标准库配置并启动各节点对应的云平台组件中的服务。
本步骤中，在对节点进行部署时，可以按照S204中的执行步骤进行部署即可。通过步数文件中的执行步数以及步数计数对节点的部署进行记录，可以清晰地确定部署时的进度，以步数文件的形式记录服务之间的启动顺序可以保证有关联性的服务正常启动。
由于S201、S202、S203分别与图1实施例中的S101、S102、S103相同，S101、S102、S103的所有实现方式均适用于图2所示实施例，且均能达到相同或相似的有益效果，在此不再赘述。
本申请实施例的云平台部署方法，通过获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中自动化安装镜像文件中云平台组件的安装包；根据各节点及各节点对应的组件，设置各节点的部署顺序及各节点对应的组件的部署顺序，按照各节点的部署顺序及各节点对应的云平台组件的部署顺序，通过标准库配置并启动各节点对应的云平台组件中的服务。本申请实施例通过自定义镜像文件，并在各节点中自动化安装镜像文件；在对各节点进行部署时，按照预先设置的部署顺序对各节点进行部署，可以保证有关联性的服务正常启动。另外，云平台的部署过程通过标准库实现，标准库代码结构简单易懂，便于扩展和维护，从而可以快速部署云平台。
参见图3，图3为本申请又一种实施例的云平台部署方法的流程图，包括以下步骤：
S301，获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件。
其中，每一云平台组件可以包含至少一个服务。
S302，在确定多个安装包之间无依赖后，将多个安装包及配置文件创建 为镜像文件。
S303，分别在云平台的各节点中安装镜像文件，以使得各节点安装所述云平台组件。
S304，配置并启动各节点对应的云平台组件中的服务。
S305，若接收到删除云平台中节点的操作指令，将待删除的节点对应的组件中的服务停止，并将待删除的节点的信息删除。
其中，待删除的节点的信息可以包括：该待删除的节点在云平台中的标识，该待删除的节点所安装的安装包，以及该待删除的节点在云平台中所执行的操作日志信息等等。
本申请实施例中的云平台具有较强的可扩展性，在部署完云平台之后，若接收到删除云平台中节点的操作指令时，可以将待删除的节点对应的云平台组件中的服务停止，例如，若需要删除云平台中的计算节点，那么，可以将计算节点中的所有服务停止，在将计算节点中的服务停止之后，云平台中将不再包含计算节点。另外，还可以将计算节点的信息删除，这样，可以减少对存储空间的占用。
S306，若接收到增加节点的操作指令，在增加的节点中安装镜像文件，通过标准库配置并启动增加的节点对应的云平台组件中的服务。
本申请实施例中，除了可以删除云平台中的节点，还可以在云平台中增加节点。对于增加的节点，部署服务的方法与云平台中已存在的节点的部署服务的方法是相同的，具体的，执行步骤S303中镜像文件的安装，即安装云平台组件的安装包，之后通过标准库配置并启动增加的节点对应的云平台组件中的服务，通过标准库配置及启动服务的方法可以与图1实施例中步骤S104或者与图2实施例中步骤S205类似，在此不再赘述，当然，不同节点中需要配置和启动的服务可以是不同的，因此，增加的节点中配置和启动的服务可以与云平台中已经存在的节点中配置和启动的服务均不同。
由于S301、S302、S303、S304分别与图1实施例中的S101、S102、S103、S104相同，S101、S102、S103、S104的所有实现方式均适用于图3所示实施例，且均能达到相同或相似的有益效果，在此不再赘述。其中，上述步骤S305和步骤S306在步骤S304之后，但步骤S305和步骤S306之间没有顺序限制。本申请实施例中，步骤S305和步骤S306的具体实现方式可以基于REST(Representational State Transfer，表述性状态转移)API(Application  Programming Interface，应用程序编程接口)，REST指的是一组架构约束条件和原则。
本申请实施例的云平台部署方法，通过获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中自动化安装镜像文件中云平台组件的安装包；根据各节点及各节点对应的组件，设置各节点的部署顺序及各节点对应的组件的部署顺序，按照各节点的部署顺序及各节点对应的云平台组件的部署顺序，通过标准库配置并启动各节点对应的云平台组件中的服务。本申请实施例通过自定义镜像文件，并在各节点中自动化安装镜像文件；在对各节点进行部署时，按照预先设置的部署顺序对各节点进行部署，使得云平台的部署过程更加快捷。另外，云平台的部署过程通过标准库实现，标准库代码结构简单易懂，可以对云平台进行快速部署。本申请实施例的云平台部署方法具有较强的扩展性，在对云平台进行部署完成之后，还可以在云平台中增加节点，或者删除云平台中已经部署的节点，从而可以对云平台中的节点进行灵活部署。
图2实施中的步骤S205，按照各节点的部署顺序及各节点对应的云平台组件的部署顺序，通过标准库配置并启动各节点对应的云平台组件中的服务，具体部署过程可参见图4，图4为本申请一种实施例的节点部署流程图，包括以下步骤：
S401，读取当前步数。
其中，当前步数指的是步数文件中的步数计数。在一种情况中，在开始部署节点时，当前步数可以从步数1开始计数。
S402，判断是否存在未执行的步数，如果是，执行S403；如果否，进入S406，即部署结束。
本申请实施例中，步数文件中可以包括执行步数，即完成云平台的部署所需执行的步数，以及步数计数，步数文件是为了方便确定云平台的部署进度，每部署完成云平台中的节点中的一服务，该步数计数递增1，该递增1后的步数计数即可以认为上述当前步数，上述判断是否存在未执行的步数，可以是判断当前步数是否不大于执行步数，当判断当前步数不大于执行步数，表征判断存在未执行的步数，即当前未部署完成云平台，继续执行S403；当判断当前步数大于执行步数，表征判断不存在未执行的步数，即当前部署完 成云平台。
S403，执行当前步数，即部署该当前步数对应的服务。
S404，判断当前步数是否执行成功，即该当前步数对应的服务是否部署完成，如果是，执行S405，即增加步数，并返回至步骤S401直至S402的判断结果为否；如果否，进入S406，即部署结束。
本步骤中，可以记录每一个执行成功的步数，然后执行下一个步数。若当前步数执行失败，即S404的执行结果为否时，部署结束。
本步骤中，每部署完成一个服务，及执行完成一个步数，该当前步数加一，当当前步数对应的服务部署失败，即S404的判断结果为否时，本轮部署可以暂停，记录当前步数，即记录当前的部署的进度；并且，可以记录当前步数，并可以通知工作人员步数出现问题，当工作人员将所出现问题解决后，可以基于记录的当前的部署的进度，继续进行该云平台的部署，即从该当前步数对应的服务开始重新部署。保留已经执行成功的步数，在当前步数执行成功之后，执行当前步数之后的步数。
本申请实施例中，可以通过Python标准库中的模版库jinja2配置(及部署)云平台组件中的每一个服务，通过Python标准库中的subprocess库执行启动服务命令。
由上述可见，本申请实施例的云平台部署方法中，在当前步数执行失败、但当前步数之前的步数均配置成功时，仍然保留当前步数之前执行成功的所有步数，并记录当前失败的步数。这样，在下次部署时，可以从当前失败的步数开始继续执行，而不需要重新执行成功的步数，避免了云平台部署过程中相同操作的反复执行，从而可以加快云平台的部署过程。
本申请的一种实现方式中，获取多个云平台组件的安装包，包括：当本地服务器和官方服务器中同时包含第一组件的安装包时，从本地服务器中获取第一组件的安装包；当本地服务器中不包含第二组件的安装包、官方服务器中包含第二组件时，从官方服务器中获取第二组件的安装包；其中，第一组件和第二组件为云平台组件中的组件。
本申请实施例中，云平台组件可以有多个，云平台组件的安装包是在服务器中存储的，并且，本地服务器中和官方服务器中可能都存储有相同名称的云平台组件的安装包，第一组件的安装包指的是本地服务器中和官方服务器中名称相同的组件的安装包。此时，优先从本地服务器中获取第一组件的 安装包。第二组件的安装包指的是本地服务器中不存在、而官方服务器中存在的组件的安装包，此时，如果获取第二组件的安装包，需要从官方服务器中获取第二组件的安装包。其中，本地服务器指的是云平台中的服务器，例如，对于某网站的云平台，云平台组件存储在该网站所对应的服务器中；官方服务器指的是发布云平台组件的官方服务器。
其中，本地服务器中和官方服务器中存储的云平台组件的安装包可以是周期性更新的，因此，在对云平台进行部署时，通常从本地服务器或者从官网服务器中获取的云平台组件的安装包是最新的。本申请的一种实现方式中，可以通过Yum从本地服务器或者官方服务器中获取云平台组件的安装包。Yum(Yellow dog UpdaterModified)是一个Shell前端软件包管理器，能够从指定的服务器自动下载安装包并且安装，可以自动处理安装包之间的依赖性关系，并且一次安装所有依赖的软件包，无须繁琐地一次次下载、安装。
本申请实施例的云平台部署方法，将本地服务器中的第一组件的安装包设置为更高的优先级，可以优先获取本地服务器中的安装包。与官方服务器中存储的安装包相比，本地服务器中存储的安装包更符合部署云平台所具有的功能，从而可以更快速地部署云平台，因此，本申请实施例的云平台部署方法更简单、快捷。
本申请的一种实现方式中，云平台组件中包括第一组件；所述获取多个云平台组件的安装包，可以包括：当本地服务器和官方服务器中同时包含第一组件的安装包时，从本地服务器中获取第一组件的安装包；当本地服务器中不包含所述第一组件的安装包、且官方服务器中包含第一组件的安装包时，从官方服务器中获取第一组件的安装包。
本申请实施例的云平台部署方法，可以设置为当至少地方服务器中含有第一组件的安装包时，优先从地方服务器中获取第一组件的安装包；当地方服务器中不含有第一组件的安装包、且官方服务器中包含第一组件的安装包时，从官方服务器中获取第一组件的安装包。
相应于上述方法实施例，本申请实施例还提供了一种云平台部署装置，参见图5，图5为本申请一种实施例的云平台部署装置的结构图，包括：安装包获取模块501，设置为获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；镜像文件创建模块502，设置为在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；镜像文件安 装模块503，设置为分别在云平台的各节点中安装镜像文件，以使得所述各节点安装所述云平台组件；云平台组件部署模块504，设置为通过标准库配置并启动各节点对应的云平台组件中的服务。
本申请实施例的云平台部署装置，通过获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中安装镜像文件，以使得各节点安装云平台组件；配置并启动各节点对应的云平台组件中的服务。本申请实施例通过自定义镜像文件，并在各节点中自动化安装镜像文件中云平台组件的安装包，使得云平台的部署过程更加快捷。另外，云平台的部署过程通过标准库实现，标准库代码结构简单易懂，便于扩展和维护，从而可以快速部署云平台。
需要说明的是，本申请实施例的装置是应用上述云平台部署方法的装置，则上述云平台部署方法的所有实施例均适用于该装置，且均能达到相同或相似的有益效果。
参见图6，图6为本申请另一种实施例的云平台部署装置的结构图，包括：
安装包获取模块601，设置为获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件。镜像文件创建模块602，设置为在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件。镜像文件安装模块603，设置为分别在云平台的各节点中安装镜像文件，以使得所述各节点安装所述云平台组件。云平台组件部署模块604，设置为通过标准库配置并启动各节点对应的云平台组件中的服务。节点删除模块605，设置为若接收到删除云平台中节点的操作指令，将待删除的节点对应的云平台组件中的服务停止，并将待删除的节点的信息删除。节点增加模块606，设置为若接收到增加节点的操作指令，在增加的节点中安装镜像文件，通过标准库配置并启动增加的节点对应的云平台组件中的服务。
本申请实施例的云平台部署装置，通过获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中自动化安装镜像文件中云平台组件的安装包；根据各节点及各节点对应的组件，设置各节点的部署顺序及各节点对应的组件的部署顺序，按照各节点的部署顺序及各节点对应的云平台组件的部署顺序，通过标准库配置并启 动各节点对应的云平台组件中的服务。本申请实施例通过自定义镜像文件，并在各节点中自动化安装镜像文件；并且，云平台的部署过程通过标准库实现，标准库代码结构简单易懂，便于扩展和维护，从而可以快速部署云平台。在对各节点进行部署时，按照预先设置的部署顺序对各节点进行部署，可以保证有关联性的服务正常启动。另外，本申请实施例的云平台部署装置具有较强的扩展性，在对云平台进行部署完成之后，还可以在云平台中增加节点，或者删除云平台中已经部署的节点，从而可以对云平台中的节点进行灵活部署。
本申请的一种实现方式中，云平台组件部署模块设置为，通过标准库配置当前待配置服务，在所述当前待配置服务配置成功之后，通过标准库配置所述当前待配置服务之后的待配置服务；若所述当前待配置服务配置失败，保留已经配置成功的服务，其中，所述当前待配置服务之前的服务均通过标准库配置成功。
本申请的一种实现方式中，云平台部署装置还包括：部署顺序设置模块，设置为在所述通过标准库配置并启动所述各节点对应的云平台组件中的服务之前，根据各节点及各节点对应的云平台组件，通过标准库设置各节点的部署顺序及各节点对应的云平台组件的部署顺序；云平台组件部署模块设置为，按照各节点的部署顺序及各节点对应的云平台组件的部署顺序，通过标准库配置并启动各节点对应的云平台组件中的服务。
本申请的一种实现方式中，镜像文件安装模块设置为，根据镜像文件中的配置文件，分别在各节点中安装镜像文件中的安装包。
本申请的一种实现方式中，安装包获取模块，包括：第一获取子模块，设置为当本地服务器和官方服务器中同时包含所述第一组件的安装包时，从所述本地服务器中获取第一组件的安装包；第二获取子模块，设置为当所述本地服务器中不包含所述第一组件的安装包、且所述官方服务器中包含所述第一组件的安装包时，从所述官方服务器中获取所述第一组件的安装包。
本申请的一种实现方式中，所述标准库为Python标准库。
本申请实施例还提供了一种电子设备，参见图7，图7为本申请一种实施例的电子设备的结构图，包括：处理器701、通信接口702、存储器703和通信总线704，其中，处理器701、通信接口702、存储器703通过通信总线704完成相互间的通信；存储器703，设置为存放计算机程序；处理器701，设置为执 行存储器703上所存放的程序时，实现上述任一云平台部署方法的步骤。
需要说明的是，上述电子设备提到的通信总线704可以是PCI(Peripheral Component Interconnect，外设部件互连标准)总线或EISA(Extended Industry Standard Architecture，扩展工业标准结构)总线等。该通信总线704可以分为地址总线、数据总线、控制总线等。为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
通信接口702用于上述电子设备与其他设备之间的通信。
存储器703可以包括RAM(Random Access Memory，随机存取存储器)，也可以包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。在一种实施方式中，存储器还可以是至少一个位于远离前述处理器的存储装置。
上述的处理器701可以是通用处理器，包括：CPU(Central Processing Unit，中央处理器)、NP(Network Processor，网络处理器)等；还可以是DSP(Digital Signal Processing，数字信号处理器)、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field-Programmable Gate Array，现场可编程门阵列)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
本申请实施例的电子设备中，处理器通过执行存储器上所存放的程序，从而通过获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中自动化安装镜像文件中云平台组件的安装包；根据各节点及各节点对应的组件，设置各节点的部署顺序及各节点对应的组件的部署顺序，按照各节点的部署顺序及各节点对应的云平台组件的部署顺序，配置并启动各节点对应的云平台组件中的服务。本申请实施例通过自定义镜像文件，并在各节点中自动化安装镜像文件；在对各节点进行部署时，按照预先设置的部署顺序对各节点进行部署，可以保证有关联性的服务正常启动。另外，本申请实施例的云平台部署装置具有较强的扩展性，在对云平台进行部署完成之后，还可以在云平台中增加节点，或者删除云平台中已经部署的节点，从而可以对云平台中的节点进行灵活部署。
本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质内存储有计算机程序，计算机程序被处理器执行时，实现上述任一云平台部 署方法的步骤。
本申请实施例的计算机可读存储介质中存储的指令在计算机上运行时，从而通过获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中自动化安装镜像文件中云平台组件的安装包；根据各节点及各节点对应的云平台组件，设置各节点的部署顺序及各节点对应的组件的部署顺序，按照各节点的部署顺序及各节点对应的云平台组件的部署顺序，配置并启动各节点对应的云平台组件中的服务。本申请实施例通过自定义镜像文件，并在各节点中自动化安装镜像文件；在对各节点进行部署时，按照预先设置的部署顺序对各节点进行部署，可以保证有关联性的服务正常启动。另外，本申请实施例的云平台部署装置具有较强的扩展性，在对云平台进行部署完成之后，还可以在云平台中增加节点，或者删除云平台中已经部署的节点，从而可以对云平台中的节点进行灵活部署。
在本申请提供的再一实施例中，还提供了一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一云平台部署方法的步骤。
本申请实施例的计算机可读存储介质中存储的指令在计算机上运行时，从而通过获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；在确定多个安装包之间无依赖后，将多个安装包及配置文件创建为镜像文件；分别在云平台的各节点中自动化安装镜像文件中云平台组件的安装包；根据各节点及各节点对应的云平台组件，设置各节点的部署顺序及各节点对应的组件的部署顺序，按照各节点的部署顺序及各节点对应的云平台组件的部署顺序，配置并启动各节点对应的云平台组件中的服务。本申请实施例通过自定义镜像文件，并在各节点中自动化安装镜像文件；在对各节点进行部署时，按照预先设置的部署顺序对各节点进行部署，可以保证有关联性的服务正常启动。另外，本申请实施例的云平台部署装置具有较强的扩展性，在对云平台进行部署完成之后，还可以在云平台中增加节点，或者删除云平台中已经部署的节点，从而可以对云平台中的节点进行灵活部署。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示 这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本说明书中的各个实施例均采用相关的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于云平台部署装置、电子设备及可读存储介质实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内所作的任何修改、等同替换、改进等，均包含在本申请的保护范围内。
工业实用性
基于本申请实施例提供的上述云平台部署方法、装置、电子设备、计算机可读存储介质以及计算机程序产品，通过自定义镜像文件，并在各节点中自动化安装镜像文件，使得云平台的部署过程更加快捷。并且，云平台的部署过程通过标准库实现，标准库代码结构简单易懂，便于扩展和维护，从而可以快速部署云平台。在对云平台进行部署完成之后，还可以在云平台中增加节点，或者删除云平台中已经部署的节点，从而可以对云平台中的节点进行灵活部署。

Claims (17)

  1. 一种云平台部署方法，所述方法包括：
    获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；
    在确定所述多个安装包之间无依赖后，将所述多个安装包及所述配置文件创建为镜像文件；
    分别在云平台的各节点中安装所述镜像文件，以使所述各节点安装所述云平台组件；
    通过标准库配置并启动所述各节点对应的云平台组件中的服务。
  2. 根据权利要求1所述的云平台部署方法，其中，所述方法还包括：
    若接收到删除所述云平台中节点的操作指令，将待删除的节点对应的组件中的服务停止，并将所述待删除的节点的信息删除；
    若接收到增加节点的操作指令，在增加的节点中安装所述镜像文件，通过所述标准库配置并启动所述增加的节点对应的云平台组件中的服务。
  3. 根据权利要求1所述的云平台部署方法，其中，
    所述通过标准库配置并启动所述各节点对应的云平台组件中的服务，包括：
    通过标准库配置当前待配置服务，在所述当前待配置服务配置成功之后，通过标准库配置所述当前待配置服务之后的待配置服务；
    若所述当前待配置服务配置失败，保留已经配置成功的服务，其中，所述当前待配置服务之前的服务均通过标准库配置成功。
  4. 根据权利要求1所述的云平台部署方法，其中，在所述通过标准库配置并启动所述各节点对应的云平台组件中的服务之前，所述方法还包括：
    根据所述各节点及所述各节点对应的云平台组件，通过标准库设置所述各节点的部署顺序及所述各节点对应的云平台组件的部署顺序；
    所述通过标准库配置并启动所述各节点对应的云平台组件中的服务，包括：
    按照所述各节点的部署顺序及所述各节点对应的云平台组件的部署顺序，通过标准库配置并启动所述各节点对应的云平台组件中的服务。
  5. 根据权利要求1所述的云平台部署方法，其中，所述分别在云平台的各节点中安装所述镜像文件，包括：
    根据所述镜像文件中的配置文件，分别在所述各节点中安装所述镜像文 件中的安装包。
  6. 根据权利要求1所述的云平台部署方法，其中，
    所述云平台组件中包括第一组件；
    所述获取多个云平台组件的安装包，包括：
    当本地服务器和官方服务器中同时包含所述第一组件的安装包时，从所述本地服务器中获取第一组件的安装包；
    当所述本地服务器中不包含所述第一组件的安装包、且所述官方服务器中包含所述第一组件的安装包时，从所述官方服务器中获取所述第一组件的安装包。
  7. 根据权利要求1所述的云平台部署方法，其中，所述标准库为Python标准库。
  8. 一种云平台部署装置，所述装置包括：
    安装包获取模块，设置为获取多个云平台组件的安装包，确定用于对多个安装包进行自动化安装的配置文件；
    镜像文件创建模块，设置为在确定所述多个安装包之间无依赖后，将所述多个安装包及所述配置文件创建为镜像文件；
    镜像文件安装模块，设置为分别在云平台的各节点中安装所述镜像文件，以使得所述各节点安装所述云平台组件；
    云平台组件部署模块，设置为通过标准库配置并启动所述各节点对应的云平台组件中的服务。
  9. 根据权利要求8所述的云平台部署装置，其中，所述装置还包括：
    节点删除模块，设置为若接收到删除所述云平台中节点的操作指令，将待删除的节点对应的组件中的服务停止，并将所述待删除的节点的信息删除；
    节点增加模块，设置为若接收到增加节点的操作指令，在增加的节点中安装所述镜像文件，通过标准库配置并启动所述增加的节点对应的云平台组件中的服务。
  10. 根据权利要求8所述的云平台部署装置，其中，所述云平台组件部署模块设置为，通过标准库配置当前待配置服务，在所述当前待配置服务配置成功之后，通过标准库配置所述当前待配置服务之后的待配置服务；
    若所述当前待配置服务配置失败，保留已经配置成功的服务，其中，所述当前待配置服务之前的服务均通过标准库配置成功。
  11. 根据权利要求8所述的云平台部署装置，其中，所述装置还包括：
    部署顺序设置模块，设置为在所述通过标准库配置并启动所述各节点对应的云平台组件中的服务之前，根据所述各节点及所述各节点对应的云平台组件，通过标准库设置所述各节点的部署顺序及所述各节点对应的云平台组件的部署顺序；
    所述云平台组件部署模块设置为，按照所述各节点的部署顺序及所述各节点对应的云平台组件的部署顺序，通过标准库配置并启动所述各节点对应的云平台组件中的服务。
  12. 根据权利要求8所述的云平台部署装置，其中，所述镜像文件安装模块设置为，根据所述镜像文件中的配置文件，分别在所述各节点中安装所述镜像文件中的安装包。
  13. 根据权利要求8所述的云平台部署装置，其中，所述云平台组件中包括第一组件；
    所述安装包获取模块，包括：
    第一获取子模块，设置为当本地服务器和官方服务器中同时包含所述第一组件的安装包时，从所述本地服务器中获取第一组件的安装包；
    第二获取子模块，设置为当所述本地服务器中不包含所述第一组件的安装包、且所述官方服务器中包含所述第一组件的安装包时，从所述官方服务器中获取所述第一组件的安装包。
  14. 根据权利要求8所述的云平台部署装置，其中，所述标准库为Python标准库。
  15. 一种电子设备，包括：处理器、通信接口、存储器和通信总线，其中，所述处理器、所述通信接口、所述存储器通过所述通信总线完成相互间的通信；
    所述存储器，设置为存放计算机程序；
    所述处理器，设置为执行所述存储器上所存放的程序时，实现权利要求1-7任一所述的云平台部署方法步骤。
  16. 一种计算机可读存储介质，所述计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-7任一所述的云平台部署方法步骤。
  17. 一种计算机程序产品，当其在计算机上运行时，使得计算机执行权利要求1-7任一所述的方法步骤。
PCT/CN2018/111007 2017-10-19 2018-10-19 一种云平台部署方法、装置、电子设备及可读存储介质 WO2019076369A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710976922.X 2017-10-19
CN201710976922.XA CN109687987A (zh) 2017-10-19 2017-10-19 一种云平台部署方法、装置、电子设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2019076369A1 true WO2019076369A1 (zh) 2019-04-25

Family

ID=66173542

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/111007 WO2019076369A1 (zh) 2017-10-19 2018-10-19 一种云平台部署方法、装置、电子设备及可读存储介质

Country Status (2)

Country Link
CN (1) CN109687987A (zh)
WO (1) WO2019076369A1 (zh)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110187890A (zh) * 2019-05-29 2019-08-30 掌阅科技股份有限公司 项目部署的方法、电子设备、存储介质
CN110688130A (zh) * 2019-10-14 2020-01-14 天津卓朗科技发展有限公司 物理机部署方法、装置、可读存储介质及电子设备
CN111596927A (zh) * 2020-05-15 2020-08-28 北京金山云网络技术有限公司 服务部署方法、装置及电子设备
CN111897538A (zh) * 2020-07-13 2020-11-06 浪潮电子信息产业股份有限公司 一种基于cpu和操作系统的容器平台部署方法及系统
CN111934907A (zh) * 2020-07-06 2020-11-13 苏州浪潮智能科技有限公司 一种基于容器云平台的应用上云方法、系统及装置
CN111984366A (zh) * 2020-07-24 2020-11-24 苏州浪潮智能科技有限公司 一种容器化部署灾备机制的方法和系统
CN112019385A (zh) * 2020-08-28 2020-12-01 北京浪潮数据技术有限公司 一种云平台组件删除方法、装置、设备及存储介质
CN112463299A (zh) * 2020-11-27 2021-03-09 北京浪潮数据技术有限公司 一种界面显示服务部署方法、装置、设备及介质
CN112463168A (zh) * 2020-12-01 2021-03-09 苏州浪潮智能科技有限公司 一种vpp服务容器化部署方法、装置、终端及存储介质
CN112685503A (zh) * 2021-01-04 2021-04-20 上海圣剑网络科技股份有限公司 基于自动化运维工具的数据处理方法、装置及系统
CN113014406A (zh) * 2019-12-19 2021-06-22 阿里巴巴集团控股有限公司 设备部署方法、装置、服务器及存储介质
CN113127016A (zh) * 2021-04-30 2021-07-16 平安国际智慧城市科技股份有限公司 Hdp大数据平台的自动化部署方法、装置、设备及介质
CN113268252A (zh) * 2021-04-06 2021-08-17 国网河北省电力有限公司 基于虚拟化工控设备的镜像制作方法、系统及存储介质
CN113805804A (zh) * 2021-08-27 2021-12-17 济南浪潮数据技术有限公司 一种数据离线迁移的方法、装置、设备和介质
CN114115954A (zh) * 2022-01-25 2022-03-01 北京金堤科技有限公司 自动化集成部署服务的方法和装置、以及电子设备和存储介质
CN115242598A (zh) * 2022-07-15 2022-10-25 天翼云科技有限公司 一种云操作系统部署方法及装置
CN117519733A (zh) * 2023-11-16 2024-02-06 之江实验室 一种项目部署方法、装置、存储介质及电子设备

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112379934B (zh) * 2019-07-29 2022-12-13 中移(苏州)软件技术有限公司 一种云计算平台的部署方法及装置、存储介质
CN110995768B (zh) * 2019-12-31 2022-04-15 奇安信科技集团股份有限公司 一种构建及生成防火墙的方法、装置和介质
CN111443876A (zh) * 2020-06-17 2020-07-24 南京信易达计算技术有限公司 一种融合型存储专用操作系统、方法和存储介质
CN112003908B (zh) * 2020-08-07 2022-06-21 苏州浪潮智能科技有限公司 一种配置bmc的方法、系统、设备以及介质
CN111984623B (zh) * 2020-08-14 2024-02-09 北京人大金仓信息技术股份有限公司 数据库集群自动化部署方法、装置、介质和电子设备
CN112131263B (zh) * 2020-09-14 2024-02-27 微医云(杭州)控股有限公司 软件包获取方法、系统、装置、电子设备和存储介质
CN112130962B (zh) * 2020-09-29 2023-09-19 中国银行股份有限公司 持续交付平台及利用持续交付平台部署应用系统的方法
CN112910956B (zh) * 2021-01-15 2023-05-02 北京金山云网络技术有限公司 一种资源创建方法、装置及电子设备
CN113434370A (zh) * 2021-08-24 2021-09-24 统信软件技术有限公司 一种服务器集群部署方法、装置、计算设备及存储介质
CN115604101B (zh) * 2022-09-29 2024-02-02 北京亚控科技发展有限公司 系统管理方法及相关设备
CN115562813B (zh) * 2022-10-27 2023-04-18 北京同创永益科技发展有限公司 一种云原生环境动态构建工作负载的方法及系统
CN117112037A (zh) * 2023-08-10 2023-11-24 中国人民银行数字货币研究所 一种云平台启动方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104967664A (zh) * 2015-05-13 2015-10-07 西安三星电子研究有限公司 云的自动化部署系统和方法
US20160124823A1 (en) * 2014-10-31 2016-05-05 International Business Machines Corporation Log analytics for problem diagnosis
CN106506636A (zh) * 2016-11-04 2017-03-15 武汉噢易云计算股份有限公司 一种基于OpenStack的云平台集群方法及系统
CN106850621A (zh) * 2017-02-07 2017-06-13 南京云创大数据科技股份有限公司 一种基于容器云技术快速搭建Hadoop集群的方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104580519B (zh) * 2015-01-29 2017-11-28 福建师范大学福清分校 一种快速部署openstack云计算平台的方法
CN105426208A (zh) * 2015-11-16 2016-03-23 山东超越数控电子有限公司 一种云计算系统OpenStack离线自动安装方法
CN106789381A (zh) * 2017-03-31 2017-05-31 山东超越数控电子有限公司 一种针对云计算管理平台简单部署和快速配置的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160124823A1 (en) * 2014-10-31 2016-05-05 International Business Machines Corporation Log analytics for problem diagnosis
CN104967664A (zh) * 2015-05-13 2015-10-07 西安三星电子研究有限公司 云的自动化部署系统和方法
CN106506636A (zh) * 2016-11-04 2017-03-15 武汉噢易云计算股份有限公司 一种基于OpenStack的云平台集群方法及系统
CN106850621A (zh) * 2017-02-07 2017-06-13 南京云创大数据科技股份有限公司 一种基于容器云技术快速搭建Hadoop集群的方法

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110187890A (zh) * 2019-05-29 2019-08-30 掌阅科技股份有限公司 项目部署的方法、电子设备、存储介质
CN110187890B (zh) * 2019-05-29 2023-04-28 掌阅科技股份有限公司 项目部署的方法、电子设备、存储介质
CN110688130A (zh) * 2019-10-14 2020-01-14 天津卓朗科技发展有限公司 物理机部署方法、装置、可读存储介质及电子设备
CN113014406B (zh) * 2019-12-19 2023-10-24 阿里巴巴集团控股有限公司 设备部署方法、装置、服务器及存储介质
CN113014406A (zh) * 2019-12-19 2021-06-22 阿里巴巴集团控股有限公司 设备部署方法、装置、服务器及存储介质
CN111596927A (zh) * 2020-05-15 2020-08-28 北京金山云网络技术有限公司 服务部署方法、装置及电子设备
CN111596927B (zh) * 2020-05-15 2023-08-18 北京金山云网络技术有限公司 服务部署方法、装置及电子设备
CN111934907B (zh) * 2020-07-06 2022-12-27 苏州浪潮智能科技有限公司 一种基于容器云平台的应用上云方法、系统及装置
CN111934907A (zh) * 2020-07-06 2020-11-13 苏州浪潮智能科技有限公司 一种基于容器云平台的应用上云方法、系统及装置
CN111897538A (zh) * 2020-07-13 2020-11-06 浪潮电子信息产业股份有限公司 一种基于cpu和操作系统的容器平台部署方法及系统
CN111984366A (zh) * 2020-07-24 2020-11-24 苏州浪潮智能科技有限公司 一种容器化部署灾备机制的方法和系统
CN111984366B (zh) * 2020-07-24 2023-01-06 苏州浪潮智能科技有限公司 一种容器化部署灾备机制的方法和系统
CN112019385A (zh) * 2020-08-28 2020-12-01 北京浪潮数据技术有限公司 一种云平台组件删除方法、装置、设备及存储介质
CN112019385B (zh) * 2020-08-28 2022-11-25 北京浪潮数据技术有限公司 一种云平台组件删除方法、装置、设备及存储介质
CN112463299A (zh) * 2020-11-27 2021-03-09 北京浪潮数据技术有限公司 一种界面显示服务部署方法、装置、设备及介质
CN112463168B (zh) * 2020-12-01 2023-01-10 苏州浪潮智能科技有限公司 一种vpp服务容器化部署方法、装置、终端及存储介质
CN112463168A (zh) * 2020-12-01 2021-03-09 苏州浪潮智能科技有限公司 一种vpp服务容器化部署方法、装置、终端及存储介质
CN112685503A (zh) * 2021-01-04 2021-04-20 上海圣剑网络科技股份有限公司 基于自动化运维工具的数据处理方法、装置及系统
CN113268252A (zh) * 2021-04-06 2021-08-17 国网河北省电力有限公司 基于虚拟化工控设备的镜像制作方法、系统及存储介质
CN113127016A (zh) * 2021-04-30 2021-07-16 平安国际智慧城市科技股份有限公司 Hdp大数据平台的自动化部署方法、装置、设备及介质
CN113805804A (zh) * 2021-08-27 2021-12-17 济南浪潮数据技术有限公司 一种数据离线迁移的方法、装置、设备和介质
CN113805804B (zh) * 2021-08-27 2024-02-13 济南浪潮数据技术有限公司 一种数据离线迁移的方法、装置、设备和介质
CN114115954A (zh) * 2022-01-25 2022-03-01 北京金堤科技有限公司 自动化集成部署服务的方法和装置、以及电子设备和存储介质
CN115242598A (zh) * 2022-07-15 2022-10-25 天翼云科技有限公司 一种云操作系统部署方法及装置
CN117519733A (zh) * 2023-11-16 2024-02-06 之江实验室 一种项目部署方法、装置、存储介质及电子设备
CN117519733B (zh) * 2023-11-16 2024-05-28 之江实验室 一种项目部署方法、装置、存储介质及电子设备

Also Published As

Publication number Publication date
CN109687987A (zh) 2019-04-26

Similar Documents

Publication Publication Date Title
WO2019076369A1 (zh) 一种云平台部署方法、装置、电子设备及可读存储介质
US10095496B2 (en) Single, logical, multi-tier application blueprint used for deployment and management of multiple physical applications in a cloud infrastructure
US9710259B2 (en) System and method for customizing a deployment plan for a multi-tier application in a cloud infrastructure
US11941452B2 (en) System to generate a deployment plan for a cloud infrastructure according to logical, multi-tier application blueprint
US20210349706A1 (en) Release lifecycle management system for multi-node application
US10031783B2 (en) Execution of a distributed deployment plan for a multi-tier application in a cloud infrastructure
US9386079B2 (en) Method and system of virtual desktop infrastructure deployment studio
US9652211B2 (en) Policy management of deployment plans
US9665358B2 (en) Installation of a software agent via an existing template agent
US11431586B1 (en) Resolving configuration drift for computing resource stacks
US8645672B2 (en) Configuring a computer system for a software package installation
US11762644B2 (en) Agentless installation for building deployments
US11327824B2 (en) Using a web server to obtain service data for a failed software application
CN113886027B (zh) 虚拟机模板创建及虚拟机的进入方法、装置及存储介质
de Sousa Barros Remote Boot Manager: Operating System Installer

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: 18867596

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18867596

Country of ref document: EP

Kind code of ref document: A1