WO2020135228A1 - 云平台部署方法、装置、服务器及存储介质 - Google Patents

云平台部署方法、装置、服务器及存储介质 Download PDF

Info

Publication number
WO2020135228A1
WO2020135228A1 PCT/CN2019/126679 CN2019126679W WO2020135228A1 WO 2020135228 A1 WO2020135228 A1 WO 2020135228A1 CN 2019126679 W CN2019126679 W CN 2019126679W WO 2020135228 A1 WO2020135228 A1 WO 2020135228A1
Authority
WO
WIPO (PCT)
Prior art keywords
role
control node
deployment
migrated
attribute
Prior art date
Application number
PCT/CN2019/126679
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 中兴通讯股份有限公司
Priority to EP19902781.4A priority Critical patent/EP3905588A4/en
Publication of WO2020135228A1 publication Critical patent/WO2020135228A1/zh

Links

Images

Classifications

    • 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/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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
    • 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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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/12—Discovery or management of network topologies
    • H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
    • 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/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5048—Automatic or semi-automatic definitions, e.g. definition templates
    • 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
    • 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/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • 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/0893—Assignment of logical groups to network 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components

Definitions

  • the invention relates to cloud computing cluster technology, in particular to a cloud platform deployment method, device, server and storage medium.
  • Cloud computing cluster environment also known as cloud platform deployment, usually refers to the process of installing and activating the related services and components of the cloud computing management system on the server.
  • the above installation process is usually for the entire cloud computing management system, that is, the management service of the entire cloud computing management system is completed as a whole to complete the deployment and installation.
  • the deployment complexity is relatively high, and the deployment and expansion after the deployment is complete
  • the difficulty is large, so the flexibility is poor, and it is difficult to meet the performance expansion requirements of the cloud computing management system.
  • the embodiments of the present disclosure provide a cloud platform deployment method, device, server, and storage medium.
  • an embodiment of the present disclosure provides a cloud platform deployment method, including: obtaining a deployment instruction; according to the deployment instruction, and setting a node type attribute and/or a role aggregation attribute in the role attribute of the role, the role to be deployed Correspondingly deployed to the target control node.
  • an embodiment of the present disclosure provides a cloud platform deployment apparatus, including: an acquisition module for acquiring a deployment instruction; a deployment module for setting a node type attribute and a role attribute in a role attribute according to the deployment instruction /Or the role aggregation attribute, correspondingly deploy the role to be deployed to the target control node.
  • an embodiment of the present disclosure provides a server, including a processor and a memory for storing a computer program that can run on the processor; wherein, when the processor is used to run the computer program, the implementation of the present disclosure is performed Examples of cloud platform deployment methods.
  • an embodiment of the present disclosure provides a storage medium in which executable instructions are stored.
  • the executable instructions are executed by a processor, the cloud platform deployment method described in the embodiments of the present disclosure is implemented.
  • FIG. 1 is a schematic diagram of a physical networking environment of a cloud platform in an embodiment of the present disclosure.
  • FIG. 2 is a schematic flowchart of a cloud platform deployment method in an embodiment disclosed in the present disclosure.
  • FIG. 3 is a schematic diagram of a predefined role in an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of deploying a role to a control node in a cloud platform deployment method according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of role migration in a cloud platform deployment method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart of a cloud platform deployment method in another embodiment disclosed in the present disclosure.
  • FIG. 7 is a schematic flowchart of a cloud platform deployment method in yet another embodiment disclosed in the present disclosure.
  • FIG. 8 is a schematic structural diagram of a cloud platform deployment device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a server in an embodiment of the present disclosure.
  • Cloud platform also known as cloud computing management system, refers to the realization of a full service cycle by building infrastructure as a service (Iaas), platform as a service (Paas) and software as a service (SaaS) Station-type services form a multi-level and comprehensive cloud computing management system.
  • infrastructure as a service means that users can obtain services from a complete computer infrastructure through the network; platform as a service means to use the software development platform as a service and submit it to users in a SaaS mode; software as a service means to pass The network provides software mode. Users do not need to purchase software, but can rent Web-based software from the provider to manage the business activities of cloud-based enterprises.
  • Role refers to the grouping definition based on the related services and components included in the cloud computing management system. For example, a specific service combination can be defined as a specific role, and each role can be used to represent an abstraction of a group of services.
  • High availability cluster (High Availability, HA) service operation mode refers to that there are generally two or more nodes, which are divided into an active node and a standby node. Usually, the one that is performing the business is called the active node, and the backup as the active node is called the standby node. When there is a problem with the active node, causing the running business (task) to fail to run normally, the standby node will detect it at this time and immediately connect the active node to execute the business, thereby achieving business continuity.
  • load balancing cluster (Load Balance, LB) service operation mode refers to the cluster architecture based on the distribution server (Director Server) to achieve shared storage, when the user's request comes, it will be sent directly to the Director Server, through the Director Server According to the preset algorithm, the user's request is distributed to the real server in the backend intelligently and balancedly, and the shared storage resources are used to ensure that all the data requested by the user is the same.
  • Distribution server Distribution server
  • the installation process of related services and components on the server is usually oriented to the entire cloud computing management system.
  • the general installation process includes the following steps S1 to S7.
  • S1 basic hardware configuration, including server BIOS (Basic Input/Output System, server boot and configuration tool) configuration, network and storage device basic configuration.
  • server BIOS Basic Input/Output System, server boot and configuration tool
  • S6 Install computing-related services on the computing node host.
  • the computing node and the control node can be deployed in one, that is, the computing-related services can be deployed on the control node.
  • the above deployment process is to complete the deployment and installation of the entire cloud computing management system's management services as a whole.
  • the consequence of this method is that it is difficult to expand and reconfigure after installation and cannot support large-scale deployment scenarios.
  • the public inventor found in the research that it is possible to divide the control node and the service running on the computing node when deploying the cloud computing management system, such as OpenStack as an example, the service that will run on the control node Defined as a control role, some public services such as image management, authentication management, database, message server, etc. are defined as corresponding service roles, so you can flexibly control the landing and operation of cloud computing management services on the server, and at the same time, expand the capacity of the control node In the scenario, it also supports limited expansion capabilities, such as distributing different roles on different servers to increase the processing capacity of the cloud management system.
  • the deployment solution will still have the following problems.
  • the main service of the control node is defined as a control role.
  • the service deployment cannot be flexibly adjusted; the current common solution in the industry is to isolate such services in The deployment tool is pre-defined as a separate role. This method will result in too many roles and complicated deployment schemes.
  • the number of control nodes generally reaches or exceeds 6, and the current common operation method in the industry is to drag characters to the control node host or select the corresponding control node host under the role, regardless of Which method is used, there are many repetitive actions of the operation, resulting in increased deployment complexity.
  • the present disclosure adds the node type attribute and/or the role aggregation attribute to the role-based role attribute, deploys the role to be deployed to the target control node according to the role attribute, and deploys according to the node type attribute in the role attribute, which is convenient for direct
  • the node types supported by the role complete the automatic deployment of the role to the target control node, and the deployment is based on the role aggregation attribute in the role attribute, which facilitates the migration and aggregation of the role according to the role aggregation attribute of the role, which can simplify the deployment difficulty of the cloud platform and Complexity, increase deployment flexibility.
  • a control node group containing multiple control nodes can be defined in advance, and the role deployment operates according to the control node group, which can ensure the consistency of the service configuration on the running node, can simplify the deployment difficulty and complexity of the cloud platform, and support Scenarios with different numbers of control node hosts in different control node groups improve deployment flexibility.
  • FIG. 1 is a schematic structural diagram of a physical networking environment of a cloud platform provided by an embodiment of the present disclosure, including a deployment node (Deployment Node), a control node (Control Node), a computing node (Compute Node), and storage resources ( Storage).
  • the deployment node may include one or more physical servers (Deployment Node1), which are used to implement the cloud platform deployment method provided by the embodiments of the present disclosure.
  • the control node may include one or more control node groups, such as Control Group1, Control Group2, ... Control Group N, and each control node group includes one or more control node hosts for running a specific service combination.
  • the deployment node and the control node may be merged, that is, the cloud platform deployment method provided by the embodiment of the present disclosure used by the deployment node for implementation may be performed by the control node as a service.
  • the computing nodes are used to provide virtual resources, and the virtual resources can be grouped and correspondingly include multiple computing nodes, such as Computer Node 1, Computer Node 2, Computer Node M.
  • Storage resources include one or more physical storage devices (Storage), which are used to provide corresponding storage resources for the operation of control nodes and computing nodes.
  • FIG. 2 is a schematic flowchart of a cloud platform deployment method provided by an embodiment of the present disclosure, which can be applied to a deployment node or a control node in the cloud platform shown in FIG. 1.
  • the method includes the following steps: step 101 and step 102.
  • Step 101 Obtain deployment instructions.
  • the deployment instructions refer to the relevant instructions that trigger the deployment of the cloud platform.
  • the cloud platform deployment may include one or more deployment stages such as role deployment, service activation, and capacity expansion deployment.
  • the corresponding deployment instructions may include relevant instructions that trigger the execution of the role deployment , Related instructions for triggering the execution of service activation, and related instructions for triggering the execution of expansion and deployment.
  • the deployment instruction may be obtained based on one or more human-computer interaction operations received by the software application interface, and the form of the human-computer interaction operation for obtaining the deployment instruction is not limited.
  • the deployment instruction as an example of the relevant instruction that triggers the execution of the role deployment, for example, it can be a role deployment virtual button provided through the software application interface, and the deployment instruction is obtained by receiving a touch operation for the role deployment virtual button; the deployment instruction is used as the trigger
  • the relevant instructions for performing service activation can be input through the parameter configuration window provided by the software application interface to receive the input operation of the parameters that meet the set requirements, and the virtual button can be activated through the service activation provided by the software application interface to receive the corresponding touch operation.
  • the deployment instruction or, take the deployment instruction as the relevant instruction that triggers the expansion deployment, for example, it can be the role migration virtual button provided through the software application interface to receive the corresponding touch operation, and the role list provided through the software application interface Obtain deployment instructions to the selected operation of the role to be migrated.
  • Step 102 According to the deployment instruction and the node type attribute and/or role aggregation attribute in the role attribute of the set role, the role to be deployed is correspondingly deployed to the target control node.
  • role refers to the grouping definition based on related services and components included in the cloud computing management system.
  • a specific service combination can be defined as a specific role, and each role can be used to represent an abstraction of a group of services.
  • Attribute refers to the description of an abstract aspect of an object, and is a general term for the nature of an object and the relationship between objects.
  • the character attribute refers to the description of the abstract aspect of the character, which is used to characterize the relationship between the character's nature and the character.
  • the node type attribute is used to characterize the node type supported by the role, such as a control node and/or a computing node.
  • the role aggregation attribute is used to characterize a role as an aggregated role or a non-aggregated role, where the same aggregated role can include multiple specified sub-roles.
  • the configuration of the role list can be simplified to simplify deployment complexity.
  • the role to be deployed is correspondingly deployed to the target control node according to the node type attribute and/or role aggregation attribute in the role attribute of the set role, wherein the role type attribute and/or role are included by setting the role attribute Aggregation attribute, based on the node type attribute, you can determine the node type supported by the corresponding role, and/or, based on the role aggregation attribute, you can determine the sub-roles associated with the corresponding role, so that it is convenient to complete the role-to-target control directly according to the node type supported by the role Automatic deployment of nodes, or migration and aggregation of roles according to the role aggregation attributes of roles, simplify the difficulty and complexity of cloud platform deployment, and increase deployment flexibility.
  • the role to be deployed when the role to be deployed is deployed to the control node, the role to be deployed may be correspondingly deployed to the target control node according to the operation of the control node group, including: corresponding deployment of the role to be deployed to the target control node group; wherein, The target control node group includes multiple control nodes.
  • control node group means that the control nodes are defined in groups, and each control node group includes a specified number of control node hosts.
  • the role operation can be based on the control node group instead of a single control node, to ensure that the service configuration of all control nodes in the same control node group is the same, reducing the probability of configuration errors and reducing Configure the number of operations.
  • the deployment of roles is based on the control node group operation, which can ensure the consistency of the service configuration on the running node, thereby simplifying the deployment difficulty and complexity of the cloud platform, and supporting control in different control node groups Scenarios with different numbers of node hosts improve deployment flexibility.
  • FIG. 3 is a schematic diagram of roles provided by an embodiment of the present disclosure.
  • a role is defined based on a specific service combination, and may include the following roles.
  • Controller control node service, where the role is an aggregate role, including the following sub-roles.
  • Controller_nova used to manage the entire life cycle of a virtual machine instance for a single user or use a group, and provide virtual services according to user needs. It can be used to create, power on, shut down, suspend, pause, adjust, migrate, restart, and destroy virtual machines, and configure information specifications such as CPU and memory.
  • Controller_cinder which provides stable data block storage services for running instances. Its plug-in driver architecture is conducive to the creation and management of block devices, such as creating and deleting volumes, and mounting and unmounting volumes on instances.
  • Controller_neutron provides cloud computing network virtualization technology, and provides network connection services for other OpenStack services. Provide interface for users, you can define Network, Subnet, Router, configure Dynamic Host Setting Protocol (DHCP), Domain Name System (DNS), load balancing, Ethernet (L3) service, network support General routing encapsulation protocol (GRE), virtual local area network (VLAN).
  • DHCP Dynamic Host Setting Protocol
  • DNS Domain Name System
  • L3 Layer 3
  • GRE General routing encapsulation protocol
  • VLAN virtual local area network
  • Controller_ironic, deploying physical machines and deploying virtual machines are triggered by nova by creating virtual machines, but the drivers of the underlying scheduler (nova-scheduler) and daemon (nova-compute) are different.
  • the underlying driver of the virtual machine uses the virtualization technology of the virtualization management platform application program interface (libvirt), and the physical machine uses the Ironic technology.
  • Ironic can be regarded as a collection of a set of middle software layer application program interfaces (Hypervisor API), Its function is similar to libvirt.
  • Controller_heat provides a collaborative deployment method defined by templates to realize the automatic deployment of cloud infrastructure software operating environment (computing, storage and network resources).
  • Controller_backup providing data backup service.
  • Controller_telemetry a technology for remotely collecting data at high speed from physical devices or virtual devices.
  • the device actively sends device data information to the collector through Push Mode to provide more real-time and higher-speed data collection functions.
  • FIG. 4 is a schematic diagram of deploying a role to a control node according to an embodiment of the present disclosure.
  • the role Service Rolls is defined based on a specific service combination.
  • the role Service Rolls includes Identity, Image, network_L2, network_L3 , RabbitMQ, MariaDB, MangoDB, Controller, Other Commons and Services, define the control node group Controller Group 1 includes multiple control nodes, such as Controller Node 1, Controller Node 2, Controller Node 3, and deploy the role Service Rolles to this one at a time
  • the service configuration of all control nodes Controller 1, Node 1, Controller 2 and Controller 3 in the target control node group Controller 1 is guaranteed to reduce the probability of configuration errors and the number of configuration operations.
  • deploying the role to be deployed to the target control node correspondingly includes: in the case where the role attribute includes the node type attribute, according to When the node type attribute determines that the node type supported by the role to be deployed is a control node, the role to be deployed is correspondingly deployed to the target control node.
  • the node type attribute refers to the node type supported by the role, such as a control node and/or a computing node.
  • the identification information of the control node refers to relevant information used to uniquely characterize the identity of the control node, such as the number, address, name and address of the control node.
  • the deployment instruction may refer to a role configuration parameter that carries the identification information of the target control node. The user can input the identification information of the control node and determine the type of node supported by the role as the control node according to the node type attribute.
  • the role is deployed to the target control node. Among them, when deploying the role to be deployed to the target control node corresponding to the type of node supported by the role, you can also operate according to the control node group.
  • Obtaining the deployment instruction is to obtain the identification information of the target control node group.
  • the user can define and identify a control node group containing multiple control nodes in advance, and enter the identification information of the control node group to be deployed as the target control node group to uniformly deploy the designated role into the target control node group at a time .
  • the specified role can be determined according to the node type attribute in the role attribute.
  • the node type supported by the role is determined as the control node according to the node type attribute, the corresponding role can be automatically deployed to the target control node group.
  • users can pre-define the control node group Controller, Group 1, and pre-define the node type attribute in the role attributes of all roles in the role Service Roles.
  • the supported node types are control nodes.
  • the user can obtain the deployment instruction by entering the identification information corresponding to the control node group Controller Group 1; or when the target control node group is uniquely determined, the deployment instruction can be obtained by triggering the deployment button to trigger the role All roles in ServiceRoles are automatically deployed to the control node group, which does not require complicated configuration by users, thereby improving deployment efficiency and ease of use.
  • the following steps are included.
  • the dependent roles and resources corresponding to the corresponding roles are determined according to the dependent attributes in the role attributes, and role dependency relationship data is generated.
  • the role dependency data obtain the role configuration parameters that carry the identification information of the dependent role and resources.
  • Dependency attributes refer to the dependent roles and resources corresponding to the roles.
  • the deployment of a role may need to depend on other roles such as components, services, or other resources such as a database.
  • the other roles or other resources that need to be dependent are characterized by dependency attributes and used to generate role dependency data at the deployment node to form Complete deployment timing.
  • the role dependency data may be in the form of a list, corresponding to being formed as a list of role dependency relationships; or may be in the form of a tree diagram, correspondingly being formed as a role dependency relationship tree.
  • the identification information that depends on roles and resources refers to information that uniquely characterizes the corresponding roles and resource identities.
  • the identity information that characterizes a role can be a server address
  • the information that characterizes the resource identity can be a database identification.
  • the role and resources corresponding to the role are determined according to the definition of the role's dependency attributes.
  • the human-computer interaction mode correspondingly obtains the role configuration parameters that meet the definition of the dependent role and resources, for example, the role configuration parameters that obtain the identification information of the database and the message server are defined according to the corresponding dependency attributes.
  • the role configuration parameters can be obtained through human-computer interaction, for example, the parameter configuration window provided by the software application interface can be used to receive the role configuration parameters that meet the definition of the dependent role and resources; or, the software application interface can also be used
  • the provided parameter selection list page receives the selected role configuration parameters for the dependent roles and resources displayed on the page.
  • the role dependency data is used to characterize the dependencies of the roles and resources that the roles need to rely on when deployed. Determine the deployment timing according to the role dependency data, and activate the role according to the role configuration parameters according to the deployment timing, which may include: determining the deployment timing of each role according to the role and resource dependencies required by each role in the role dependency data And form a role dependency tree, by traversing the role dependency tree, the role activation interface is activated in turn to activate the role.
  • the dependent attribute of role A defines the dependent role corresponding to role A as role B, that is, the deployment of role A needs to rely on role B to complete the deployment first, so that the role dependency relationship data formed by the dependency attributes of role A can determine the role
  • the deployment sequence of B should precede role A, and so on, to form a complete deployment sequence of all roles.
  • the role configuration parameters corresponding to the identification information of the dependent role and resources that meet the definition of the dependency attribute are obtained correspondingly according to the definition of the dependency attribute in the role attribute, which is convenient for dragging the role to be deployed to the target control node or the target control node
  • the activation application of the role is called according to the deployment timing and according to the corresponding role configuration parameters
  • the program interface API performs role activation to complete the corresponding deployment of the role to be deployed to the target control node.
  • the method before deploying the role to be deployed to the target control node, the method further includes: acquiring address information carrying a floating internet protocol address IP as the role configuration parameter of the role to be deployed.
  • the identification information that depends on roles and resources refers to an open IP address that can be routed to and is not automatically assigned to a physical device.
  • the physical device can have an automatically assigned static IP for communication between the internal network devices.
  • This internal network uses private addresses. These private addresses cannot be routed to.
  • floating IP the services of the internal network physical device can be recognized by the external network. And visit. Through the setting of floating IP, it is possible to realize the replacement without delay between the physical devices of the internal network and provide external services.
  • the role configuration parameters for obtaining the floating IP address can be obtained through human-computer interaction.
  • the role configuration parameters for the input floating IP address can be received through the parameter configuration window provided by the software application interface; or, it can also be obtained through the software.
  • the parameter selection list page provided by the application interface receives the selected role configuration parameters of the floating IP address and so on.
  • the configuration parameters are acquired in a machine-interactive manner to adapt to different personalized roles and form a parameter list that meets the role requirements.
  • the configuration parameters include the identification information of the corresponding dependent roles and resources configured for the role to be deployed, and the corresponding IP address information configured for the role to be deployed, so that the role can be satisfied after the role is activated based on the configuration parameters The different performance requirements of the role.
  • obtaining the corresponding configuration parameters through human-computer interaction can be regarded as obtaining the deployment instruction to execute the service activation, so as to traverse the role dependency data after dragging the role to be deployed to the target control node or target control node group, Call the activation application program interface (API) corresponding to the role and activate the role based on the above parameter list to complete the corresponding deployment of the role to be deployed to the target control node or target control node group.
  • API application program interface
  • activating the role according to the role configuration parameters according to the deployment timing includes: according to the deployment timing, calling the corresponding role activation interface according to the role configuration parameters and the role operation attributes in the role properties to activate the role.
  • the role operation attribute refers to a set of role operation methods corresponding to the role, including API interfaces such as activation, migration, and deactivation and their corresponding data parameter definitions.
  • the configuration parameters that meet the role requirements are obtained through human-computer interaction, and the role dependency data is generated according to the role attributes to determine the deployment timing , And traverse the role dependency data to call the activation API corresponding to the role according to the deployment timing and pass the parameters based on the corresponding parameter list to activate the role, and complete the corresponding deployment of the role to be deployed to the target control node or target control node group.
  • the operation is performed according to the control node group, and before the role to be deployed is correspondingly deployed to the target control node group, the following steps are included.
  • the corresponding control node host is formed into a control node group.
  • each control node group may include a specified number of control node hosts accordingly.
  • Obtain the selection instruction of the control node host which can be the control node host identification received through the parameter input window provided by the software application interface, and correspondingly obtain the selection instruction of the control node host; or, it can also be the control provided by the software application interface
  • the node host list page receives the selection command of the control node host corresponding to the selection operation of the control node host displayed on the page. According to the selection command of the control node host, the control node group is defined accordingly.
  • FIG. 5 is a schematic diagram of role migration in a control node expansion scenario provided by an embodiment of the present disclosure, where the control node group includes a control node group Controller 1 and a control node group Controller 2 that respectively include different control node hosts.
  • the control node group Controller Group 1 includes control nodes Controller Node 1, Controller Node 2 and Controller Node 3, and the control node group Controller Group 2 includes control nodes Controller Node 4, Controller Node 5 and Controller Node 6.
  • control node group When deploying on a cloud platform, you can define a control node group by selecting the control nodes Controller, Node 1, Controller 2 and Controller Node 3, and forming a control node by selecting control nodes Controller 4, Node 4, Node 5 and Controller 6 Group Controller 2, which can be deployed in groups based on control node groups, supports scenarios where different control node groups contain different numbers of hosts, and simplifies deployment complexity when serving distributed deployments.
  • obtaining the deployment instruction includes: obtaining a role migration instruction carrying identification information of the role to be migrated.
  • deploying the role to be deployed to the target control node correspondingly includes the following steps.
  • the role attribute includes the role aggregation attribute
  • the role to be migrated is an aggregation role and the role to be migrated is a partial migration according to the set role aggregation attribute
  • the role aggregation attribute refers to characterizing a role as an aggregated role including multiple sub-roles or as a non-aggregated role. By adding the role aggregation attribute, multiple roles with specific associations can be associated and defined to form an aggregate role, where the multiple roles included in the aggregate role are correspondingly called sub-roles.
  • the identification information of the role to be migrated refers to relevant information that can uniquely characterize the identity of the role to be migrated.
  • the deployment instruction refers to a role migration instruction that carries identification information of the role to be migrated.
  • the role migration instruction that carries the identification information of the role to be migrated may include but is not limited to the following ways: First, through the role list page provided by the software application interface, receive the selection of the role to be migrated displayed on the role list page And drag the operation to obtain the role migration instruction that carries the identification information of the role to be migrated; second, through the role information window provided by the software application interface, receive the identification information of the input role to be migrated and confirm the operation to obtain the carried The role migration instruction with the identification information of the role to be migrated; third, the role migration virtual button corresponding to each role provided through the software application interface, receiving the touch operation on the role migration virtual button, and the obtained carrying the corresponding pending Role migration instructions for migrating role identification information; fourth, through the role migration virtual button provided by the software application interface, receiving the role migration trigger instruction, and receiving the selected operation of the role to be migrated based on the role list page or based on the role information window Enter the identification information of the role to be migrated, and thus obtain the role migration instruction that carries
  • the role aggregation attribute is added to the role attribute to support multi-role aggregation to form an aggregated role, and the migration and deployment operations for the aggregated role with multiple roles are supported correspondingly.
  • the aggregated role can be targeted Overall deployment, so as to realize the overall deployment of the sub-roles included in the aggregate role at one time, or to expand the sub-roles associated with the aggregate role according to different actual needs, and select and deploy some sub-roles. In this way, by supporting role aggregation and adopting aggregated roles to achieve overall or partial migration, it can not only meet the deployment purposes of different needs, but also reduce deployment operations, achieve flexible service migration and expansion, simplify deployment complexity, and improve deployment efficiency.
  • the role to be migrated when the role to be migrated is migrated to the target control node according to the role aggregation attribute, it can also be operated according to the control node group, and the sub-role to be migrated to the target control node according to the selected instruction can be moved to the target control node according to the selected instruction
  • the migration subrole is migrated to the target control node group.
  • the Cloud platform when the cloud platform is deployed, it can support partial migration of the aggregation role Controller in the control node expansion scenario.
  • the control node group Controller 1 is formed.
  • the control nodes in the control node group Controller Group 1 Controller 1 Node 1, Controller 2 and Controller 3 are deployed with the same role
  • Service Roles Service Roles include the following sub-roles: Identity, Image, network_L2, network_L3, RabbitMQ, MariaDB, MangoDB, Controller, Other Common Roles and Services.
  • new control nodes Controller Node 4, Controller 5 and Controller 6 are added and new control node group Controller 2 is defined and formed.
  • the role migration instruction carrying the aggregated role controller expand the sub-list information associated with the aggregated role controller, based on the sub-list information, obtain the selected instructions of the sub-role Controller_nova, Controller_cinder, Controller_neutron, Controller_ironic to be migrated, and according Migrate the sub-roles Controller_nova, Controller_cinder, Controller_neutron, Controller_ironic to the target control node group Controller Group 2, to achieve partial migration for the aggregated role Controller.
  • the following steps are included.
  • Deactivation refers to the operation to terminate the activated state.
  • the scheme for the migration of roles after dragging the corresponding sub-role to be migrated to the corresponding target control node, it also includes re-aggregating the migrated role according to the role aggregation attribute, and Update. After dragging the corresponding sub-role to be migrated to the corresponding target control node, it also includes deactivation at the original control node where the role to be migrated is located, and activation at the target control node after the role to be migrated is migrated.
  • the migration operation of the selected sub-role to be migrated to the target control node will generate and carry the corresponding migration parameters
  • the migration parameters include the identification information of the original control node where the sub-role to be migrated is located and the identification information of the target control node to which it is migrated .
  • the corresponding role deactivation interface Application, Programming, Interface, API
  • the sub-role to be migrated when it is migrated to the target control node according to the role aggregation attribute, it may also be operated according to the control node group.
  • the deactivation and activation operations of the sub-role to be migrated are also operated according to the control node group, which specifically includes: The node group is deactivated, and the target control node group after the migration of the sub-role to be migrated is activated.
  • the migration parameters corresponding to the corresponding migration operation include the identification information of the original control node group where the sub-role to be migrated is located and the identification information of the target control node group to which it is migrated.
  • corresponding deployment of the role to be deployed to the target control node further includes the following steps.
  • the role to be migrated is determined to be a non-aggregated role according to the role aggregation attribute; or, the role to be migrated is determined to be the aggregated role and the role to be migrated is the overall migration according to the role aggregation attribute.
  • the role aggregation attribute refers to characterizing a role as an aggregated role including multiple sub-roles or as a non-aggregated role. By adding the role aggregation attribute, multiple roles with specific associations can be associated and defined to form an aggregate role, where the multiple roles included in the aggregate role are correspondingly called sub-roles.
  • the role to be migrated is correspondingly migrated to the target control node.
  • the role to be migrated is correspondingly migrated to the target control node.
  • the role to be migrated when the role to be migrated is migrated to the target control node according to the role aggregation attribute, it may also be operated according to the control node group. That is, the corresponding migration of the role to be migrated to the target control node may be the corresponding migration of the role to be migrated to the target control node group.
  • the Cloud platform when the cloud platform is deployed, it can support migration by control node group for non-aggregated roles network_L2 and network_L3 in the control node expansion scenario.
  • the control node group Controller 1 is first formed according to the definitions of the control nodes Controller 1, Node 2 and Controller 3.
  • Service Roles includes the following sub-roles: Identity, Image, network_L2, network_L3, RabbitMQ, MariaDB, MangoDB, Controller, Other Common Roles and Services.
  • Service Roles includes the following sub-roles: Identity, Image, network_L2, network_L3, RabbitMQ, MariaDB, MangoDB, Controller, Other Common Roles and Services.
  • the non-aggregated roles network_L2 and network_L3 are migrated to the target control node group Controller Group 2 to realize the direct migration of the non-aggregated roles network_L2 and network_L3.
  • the overall migration of aggregated roles is the same as the migration of non-aggregated roles.
  • the aggregated role controller is migrated to the target control node group Controller 2. Direct overall migration for the aggregation role Controller.
  • the role to be migrated when the cloud platform is deployed, the role to be migrated is determined to be the role to be migrated according to the role migration instruction, and when the role to be migrated is determined to be a non-aggregated role, the role to be migrated is migrated to the corresponding target control node or Target control node group; when determining that the role to be migrated is an aggregated role, it is further determined whether the role to be migrated is an overall migration or a partial migration, and when the role to be migrated is an overall migration, the migrated role is migrated to the corresponding target control node or target control Node group; when the role to be migrated is a partial migration, expand the sub-role list information contained in the aggregate role, obtain the selected instruction for the sub-role based on the sub-role list information, and migrate the sub-role to the corresponding one according to the selected instruction Target control node or target control node group.
  • role aggregation attributes to the role attributes to support the definition and operation of roles during cloud platform deployment, it supports the deployment of aggregate roles in large-scale scenarios to achieve flexible role deployment. In other scenarios, the overall deployment of aggregate roles is also supported. Simplify the complexity of role definition and improve deployment efficiency.
  • the following steps are included.
  • Deactivation refers to the operation to terminate the activated state.
  • the scheme for migrating roles after dragging the corresponding role to be migrated to the corresponding target control node, it also includes re-aggregating the migrated role.
  • the corresponding role to be migrated may refer to the aggregated role as a whole, the non-aggregated role or the sub-role.
  • After dragging the corresponding role to be migrated to the corresponding target control node it also includes performing a deactivation operation at the original control node where the role to be migrated is located, and performing an activation operation at the target control node after the role to be migrated is migrated.
  • the role to be migrated corresponding to the migration operation will carry the corresponding migration parameters, including the identification information of the original control node where the role to be migrated is located and the target control to which it is migrated According to the identification information of the node, after the corresponding role to be migrated is migrated to the target control node, the corresponding role can be called to activate the interface to activate the role to be migrated according to the migration parameters; Call the corresponding role activation interface to activate the role to be migrated to complete the role migration.
  • the role to be migrated when the role to be migrated is migrated to the target control node according to the role aggregation attribute, it may also be operated according to the control node group.
  • the deactivation and activation operations of the role to be migrated are also operated according to the control node group, which specifically includes: the original control node group where the role to be migrated is located Deactivate and activate the target control node group after the role to be migrated is migrated.
  • the migration parameters corresponding to the corresponding migration operation include: the identification information of the original control node group where the role to be migrated is located and the identification information of the target control node group to which it is migrated.
  • the method further includes: pre-defining the role in the cloud platform and the role attribute corresponding to the role.
  • the role attribute includes at least one of the following: a node type attribute and a role aggregation attribute.
  • role attributes include identity attributes, dependent attributes, service attributes, node type attributes, role aggregation attributes, and role operation attributes.
  • Role refers to the grouping definition based on related services and components included in the cloud computing management system. For example, a specific service combination can be defined as a specific role, and each role can be used to represent an abstraction of a group of services.
  • the character attribute refers to the description of the abstract aspect of the character, which is used to characterize the relationship between the character's nature and the character.
  • the node type attribute refers to the node type supported by the role, such as a control node and/or a computing node.
  • the role aggregation attribute refers to characterizing the role as an aggregated role or a non-aggregated role, where the same aggregated role may include multiple specified associated sub-roles.
  • Identity attribute refers to the relevant information used to characterize the identity of the role, such as the role name and description information.
  • Dependency attributes refer to the dependent roles and resources used to characterize the roles, such as the identification information of other roles or identification information of other resources that the corresponding role deployment needs to depend on.
  • the service attribute refers to the service list and service operation mode included in the role.
  • the service operation mode mainly includes a high availability cluster (High Availability, HA) service operation mode or a load balancing cluster (Load Balance, LB) service operation mode.
  • the role operation attribute refers to a set of role operation methods used to characterize the role, including API interfaces such as activation, migration, and deactivation, and their corresponding data parameter definitions.
  • the role attributes include node type attributes, and the node types supported by the corresponding roles can be determined based on the node type attributes, so that it is convenient to directly complete the role to the target control node according to the node types supported by the role Or the automatic deployment of the target control node group; role attributes include role aggregation attributes. Based on the role aggregation attributes, the sub-roles associated with the corresponding role can be determined, which facilitates the complete or partial migration of aggregated roles according to the role aggregation attributes of the role, and the post-migration Re-aggregation; role attributes include role operation attributes.
  • a set of operation methods corresponding to the role can be determined, such as activation, migration, and deactivation operation methods, and API interfaces and corresponding parameter definitions required to perform the corresponding operation methods can be determined.
  • you can expand the control node determine the role type based on the role attributes and migrate roles according to the corresponding method, and for non-aggregated roles, you can directly migrate from the original control node group to the target Control node group; for the aggregation role, if it is a whole migration, you can directly migrate from the original control node group to the target control node group; if it is a partial migration, expand the aggregation role and migrate the role that needs to be migrated to the target control node group, After the migration, the original control node group and the target control node group are re-aggregated according to the role aggregation attributes of the role.
  • the cloud platform deployment method includes the following steps S61 to step S66.
  • Step S61 a predefined control node group; wherein, a control node host can be selected, for example, 1 to 3 servers are defined as a cloud platform control node group Controller 1 according to the actual situation of the environment.
  • Step S62 predefined roles and role attributes; among them, grouping and definition can be performed according to components and services in the cloud platform, and specific service combinations can be defined as roles respectively.
  • the defined roles Service can include: Identity, Image, network_L2, network_L3, RabbitMQ, MariaDB, MangoDB, Controller, Other Commons and Services.
  • Controller is an aggregation role, and the corresponding sub-role includes: Controller_nova, Controller_cinder, Controller_neutron, Controller_ironic, Controller_heat, Controller_backup, Controller_telemetry, Other Controllers and Services.
  • Step S63 the corresponding character is automatically dragged to the target control node group according to the node type attribute of the character; wherein, the operation of automatically dragging the corresponding character to the target control node group according to the node type attribute of the role can be performed based on the deployment instruction.
  • the deployment instruction may refer to the deployment virtual key provided based on the software application interface, and the deployment instruction obtained through the touch operation for deploying the virtual key received through human-computer interaction; or may also refer to the input provided based on the software application interface
  • the window receives the input identification information of the target control node group and confirms the deployment instruction obtained. Taking the OpenStack cloud platform as an example, please refer to FIG. 4 again.
  • the node type attributes of all roles in the role Service Rolls include support for the control node, and all roles in the role Service Rolls are automatically deployed to the control Node group Controller Group 1.
  • Step S64 a role dependency list is generated according to the dependency attributes in the role attributes, and the dependent resources of all roles are scanned to generate a dependency relationship tree; wherein, the dependency relationship tree refers to nodes and roles, etc., and characterizes the node through the connection line before the node Tree diagram formed by interdependence.
  • the dependency relationship tree refers to nodes and roles, etc., and characterizes the node through the connection line before the node Tree diagram formed by interdependence.
  • Step S65 Obtain the role configuration parameters.
  • the role configuration parameters include but are not limited to: identification information of the target control node group, corresponding identification information of dependent roles and resources, and floating IP address information; wherein, the identification information of the target control node group may be Refers to the host group and host list corresponding to the landing of the role to be deployed.
  • the identification information of the corresponding dependent roles and resources may refer to the dependent roles and dependent resources required in the definition of the dependent attributes of the roles to be deployed, such as configuration information corresponding to databases and message servers.
  • the role configuration parameters are obtained through human-computer interaction, and the corresponding role configuration parameters can be obtained as deployment instructions for performing role activation operations during the cloud platform deployment process.
  • step S66 the role activation interface is called to activate the role; wherein, according to the role attributes corresponding to the role to be deployed, the corresponding role activation interface is called, and the above role configuration parameters are passed, and the role activation is completed by traversing the dependency tree.
  • the cloud platform deployment method provided in the above embodiment is mainly applicable to the cloud platform service deployment process in a typical scenario.
  • the corresponding role is directly dragged to the control node group according to the node type attribute, based on Uniform deployment of role node type attributes can improve deployment efficiency and ease of use; and all role operations are based on the control node group, which can ensure that all hosts in the control node group have the same role configuration, simplifying deployment complexity.
  • the cloud platform deployment method in the control node capacity expansion scenario mainly includes the role migration solution in the control node capacity expansion scenario, which may be based on the cloud platform architecture that has been initially deployed, such as the cloud platform that is initially deployed using the cloud platform deployment method shown in FIG. 6
  • the architecture is executed based on the control node expansion requirements, please refer to FIG. 7, the cloud platform deployment method is as follows steps S71-step 710.
  • Step S71 define a new control node group Controller Group 2; where, the newly added node can be selected to define a new control node group, because all role operations are based on the control node group, select the newly added node to complete the definition of the control node group, To prepare for the subsequent role operation.
  • step S72 it is determined whether the role to be migrated is an aggregation role. If yes, step S73 is executed; if not, step S76 is executed; here, the role to be migrated can be understood as a role to be deployed in the role migration scheme. Among them, the determination of the role to be migrated can be triggered according to different role migration instructions. For example, the role to be migrated can be directly selected and dragged based on the role list page.
  • a role migration instruction for migrating character identification information may be a touch operation based on the touch operation of the character migration button, and based on the migration instruction, a selected operation of the character to be migrated or input identification information of the character to be migrated may be received, thereby Correspondingly obtain the role migration instruction carrying the identification information of the role to be migrated; it may be based on the role list page to receive the selected operation of the role to be migrated and the touch operation of the role migration button to obtain the role carrying the identification information of the role to be migrated Migration instructions.
  • Step S73 Drag the role to be migrated to the target control node group, and generate migration parameters accordingly; wherein, the migration parameter includes the original control node group and host list where the role to be migrated is located, and the role to be migrated is migrated to the target control node group and host list.
  • Step S74 the corresponding deactivation interface is called on the original control node group of the role to be migrated, and the deactivation operation is performed on the role to be migrated.
  • step S75 the corresponding activation interface is called in the target control node group of the role to be migrated, and the activation operation of the role to be migrated is performed.
  • step S76 when it is determined that the role to be migrated is an aggregated role, it is determined whether the role to be migrated is an overall migration or a partial migration. If it is an overall migration, step S73 is returned to, if it is a partial migration, step S77 is executed.
  • Step S77 Expand the sub-role list information associated with the aggregate role.
  • Step S78 Drag the sub-role to be migrated to the target control node group, and generate migration parameters accordingly; wherein, the migration parameters include the original control node group and host list where the sub-role to be migrated is located, and the sub-role to be migrated to the target control node group and List of hosts.
  • Step S79 Call the corresponding deactivation interface on the original control node group of the sub-role to be migrated, and perform the deactivation operation on the role to be migrated.
  • Step S710 the corresponding activation interface is called in the target control node group of the sub-role to be migrated, and an activation operation is performed on the role to be migrated.
  • the cloud platform deployment method provided in the above embodiment is mainly applicable to the role migration solution in the cloud platform service deployment process under the control node expansion scenario.
  • By adding the role aggregation attribute to the role attribute it supports the aggregation of role deployment in a large-scale scenario to achieve Flexible role deployment, adopting aggregated role deployment in typical scenarios to reduce the complexity of role configuration; at the same time, control nodes are grouped and managed, and all role operations are based on the control node group to ensure the role of all hosts in the same control node group
  • the configuration is the same, simplifying the complexity of environment deployment and improving ease of use. Referring to FIG.
  • a cloud platform deployment apparatus including an acquisition module 11 for acquiring deployment instructions; a deployment module 13 for setting nodes according to deployment instructions and role attributes of roles Type attribute and/or role aggregation attribute, correspondingly deploy the role to be deployed to the target control node.
  • the deployment module 13 is specifically configured to deploy the role to be deployed to the target control node when it is determined that the node type supported by the role to be deployed is a control node according to the node type attribute when the role attribute includes the node type attribute.
  • the deployment module 13 is also used to determine the dependent roles and resources corresponding to the corresponding roles according to the dependency attributes in the role attributes, and to generate role dependency data;
  • the acquisition module 11 is also used to obtain dependent roles based on the role dependency data The role configuration parameters of the identification information of the resource;
  • the device further includes an activation module 15, which is used to determine the deployment timing according to the role dependency data, and activate the role according to the role configuration parameters according to the deployment timing.
  • the obtaining module 11 is specifically used to obtain the role migration instruction carrying the identification information of the role to be migrated; the deployment module 13 is specifically used to determine the role aggregation instruction based on the role aggregation attribute based on the role migration instruction when the role attribute includes the role aggregation attribute
  • the role to be migrated is an aggregation role and the role to be migrated is a partial migration; expand the subrole list information associated with the role to be migrated, and select the subrole to be migrated to the target control node based on the subrole list information.
  • the device also includes a deactivation module 16 and an activation module 15, the deactivation module 16 is used to call the corresponding role deactivation interface at the original control node where the sub-role to be migrated is located, to deactivate the sub-role to be migrated; the activation module 15 is used to To call the corresponding role activation interface at the target control node to activate the sub-role to be migrated.
  • the deployment module 13 is also used to determine that the role to be migrated is a non-aggregated role according to the role aggregation attribute when the role attribute includes the role aggregation attribute; or, to determine the role to be migrated to be the aggregated role and the role to be migrated according to the role aggregation attribute For overall migration; correspondingly migrate the role to be migrated to the target control node.
  • the device further includes a deactivation module 16 and an activation module 15.
  • the deactivation module 16 is used to call the corresponding role deactivation interface at the original control node where the role to be migrated is located to deactivate the sub-role to be migrated; the activation module 15 uses To call the corresponding role activation interface at the target control node to activate the role to be migrated.
  • the deployment module 13 is specifically configured to correspondingly deploy the role to be deployed to the target control node group; wherein, the target control node group includes multiple control nodes.
  • the device further includes a node definition module 10, which is used to obtain a selection instruction of the control node host; according to the selection instruction, the corresponding control node host is formed into a control node group.
  • a node definition module 10 which is used to obtain a selection instruction of the control node host; according to the selection instruction, the corresponding control node host is formed into a control node group.
  • the device further includes a role definition module 12 for pre-defining the roles in the cloud platform and the role attributes corresponding to the roles.
  • the role attributes include at least one of the following: node type attributes and role aggregation attributes.
  • the cloud platform deployment apparatus provided in the above embodiments is only exemplified by the division of the above program modules during cloud platform deployment. In practical applications, the above steps can be allocated to different program modules according to needs, that is, Divide the internal structure of the device into different program modules to complete all or part of the processing described above.
  • the cloud platform deployment apparatus and the cloud platform deployment method embodiments provided in the above embodiments belong to the same concept. For the specific implementation process, see the method embodiments, and details are not described here.
  • the server includes a processor 201 and is used to store and run on the processor 201
  • the processor 201 executes the steps of the cloud platform deployment method provided by any embodiment of the present disclosure.
  • the processor 201 and the storage medium 202 do not refer to the corresponding number as one, but may be one or more.
  • the server also includes a memory 203, a network interface 204, and a system bus 205 connecting the processor 201, the memory 203, the network interface 204, and the storage medium 202.
  • the storage medium 202 stores an operating system and a cloud platform deployment device for implementing the cloud platform deployment method provided by the embodiments of the present invention.
  • the processor 201 is used to improve computing and control capabilities and support the operation of the entire server.
  • the memory 203 is used to provide an environment for the operation of the memory cache management method in the storage medium 202, and the network interface 204 is used by other nodes to perform network communication.
  • An embodiment of the present invention further provides a computer storage medium, for example, including a memory storing a computer program, which can be executed by a processor to complete the steps of the cloud platform deployment method provided by any embodiment of the present invention.
  • the computer storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM; it may also be various devices including one or any combination of the above memories.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Human Computer Interaction (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本公开提供了一种云平台部署方法、装置、服务器及存储介质，该方法包括：获取部署指令；根据所述部署指令，以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点。其中角色属性包括节点类型属性和/或角色聚合属性，便于直接根据角色所支持的节点类型完成角色到目标控制节点组的自动部署，或根据角色的角色聚合属性完成角色的迁移和聚合，可以简化云平台的部署难度和复杂度，提高云平台的部署灵活性。

Description

云平台部署方法、装置、服务器及存储介质 技术领域
本发明涉及对云计算集群技术，尤其涉及一种云平台部署方法、装置、服务器及存储介质。
背景技术
云计算集群环境，也称云平台的部署，通常是指将云计算管理系统的相关服务、组件在服务器上完成安装、激活的过程。
相关技术中，上述安装过程通常是面向云计算管理系统整体，也即将整个云计算管理系统的管理服务作为一个整体来完成部署安装，如此，部署复杂度较高，且部署完成后扩展和改配难度大，从而灵活性较差，难以满足云计算管理系统的性能扩展需求。
发明内容
为解决现有存在的技术问题，本公开实施例提供一种云平台部署方法，装置、服务器及存储介质。
第一方面，本公开实施例提供一种云平台部署方法，包括：获取部署指令；根据所述部署指令，以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点。
第二方面，本公开实施例提供一种云平台部署装置，包括：获取模块，用于获取部署指令；部署模块，用于根据所述部署指令，以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点。
第三方面，本公开实施例提供一种服务器，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器；其中，所述处理器用于运行所述计算机程序时，执行本公开实施例所述的云平台部署方法。
第四方面，本公开实施例提供一种存储介质，所述存储介质中存储有可执行指令，所述可执行指令被处理器执行时实现本公开实施例所述的云平台部署方法。
。
附图说明
图1为本公开一实施例中云平台的物理组网环境的示意图。
图2为本公开公开一实施例中云平台部署方法的流程示意图。
图3为本公开公开一实施例中预定义角色的示意图。
图4为本公开公开一实施例中云平台部署方法中将角色部署至控制节点的示意图。
图5为本公开公开一实施例中云平台部署方法中角色迁移的示意图。
图6为本公开公开另一实施例中云平台部署方法的流程示意图。
图7为本公开公开又一实施例中云平台部署方法的流程示意图。
图8为本公开公开一实施例中云平台部署装置的结构示意图。
图9为本公开公开一实施例中服务器的结构示意图。
具体实施方式
以下结合说明书附图及具体实施例对本发明技术方案做进一步的详细阐述。除非另有定义，本文所使用的所有的技术和科学术语与属于本发明的技术领域的技术人员通常理解的含义相同。本文中在本发明的说明书中所使用的术语只是为了描述具体的实施例的目的，不是旨在于限制本发明。本文所使用的术语“和/或”包括一个或多个相关的所列项目的任意的和所有的组合。
在以下的描述中，涉及到“一些实施例”的表述，其描述了所有可能实施例的子集，但是应当理解，“一些实施例”可以是所有可能实施例的相同子集或不同子集，并且可以在不冲突的情况下相互结合。
对本公开进行进一步详细说明之前，对本公开实施例中涉及的名词和术语进行说明，本发明实施例中涉及的名词和术语适用于如下的解释。
1)、云平台(Cloud platform)，也称为云计算管理系统，是指通过构建基础设施即服务(Iaas)、平台即服务(Paas)和软件即服务(SaaS)来实现全服务周期的一站式服务，形成多层级、全方位的云计算管理系统。其中，基础设施即服务是指用户通过网络可以从完善的计算机基础设施获得服务；平台即服务是指将软件研发的平台作为一种服务，以SaaS的模式提交给用户；软件即服务是指通过网络提供软件的模式，用户无需购买软件，而可以向提供商租用基于Web的软件来管理上云企业的经营活动。
2)、角色，是指基于云计算管理系统包含的相关服务、组件进行的分组定义，如可以将一个特定的服务组合定义为特定的角色，每一角色可以用于表征一组服务的抽象。
3)、高可用性集群(High Availability，HA)服务运行模式，是指一般有两个或两个以上的节点，且分为主用节点及备用节点。通常把正在执行业务的称为主用节点，而作为主用节点的一个备份的则称为备用节点。当主用节点出现问题，导致正在运行的业务(任务)不能正常运行时，备用节点此时就会侦测到，并立即接续主用节点来执行业务，从而实现业务的连续性。
4)、负载均衡集群(Load Balance，LB)服务运行模式，是指基于分发服务器(Director Server)实现共享存储的集群架构，当用户的请求过来时，会直接发送到Director Server上，通过Director Server把用户的请求根据预先设置好的算法，智能均衡地分发到后端的真正服务器(real server)上，通过共享存储资源，以保证所有用户请求的数据是一样的。
相关技术中，云平台部署过程中，相关服务、组件在服务器上安装过程通常是面向云计算管理系统整体，以OpenStack云计算管理系统部署为例，通常的安装过程包括如下步骤S1至S7。
S1，基础硬件配置，包括服务器BIOS(Basic Input/Output System，服务器的引导及配置工具)配置、网络及存储设备基础配置。
S2，安装服务器的操作系统(OS)，并完成OS基础配置。
S3，在控制节点主机上安装控制节点相关的软件及服务。
S4，如果是双控或三控环境，逐一完成各服务器的软件安装。
S5，完成相关服务的HA(High Availability，高可用)、LB(Load Balance，负载均衡)配置及OpenStack云计算管理系统业务相关配置。
S6，在计算节点主机上安装计算相关服务，计算节点和控制节点可以合一部署，即计算相关服务可以在控制节点部署。
S7，随着控制节点管理的计算节点规模逐步增加，需要在原有双控或三控环境上增加控制节点，将部分服务迁移到新的控制节点上，通过增加控制节点数量的方式扩展云计算管理系统的服务规模。
上述部署过程是将整个云计算管理系统的管理服务作为一个整体来完成部署安装，这种方式导致的后果是安装后的扩展和改配难度大，无法支持大规模部署场景。
为了解决上述问题，公开发明人在研究中发现，可以在部署云计算管理系统时对控制节点、计算节点上运行的服务做一定的划分，比如以OpenStack为例，将在控制节点上运行的服务定义为控制角色，将一些公共服务比如镜像管理、认证管理、数据库、消息服务器等分别定义为相应服务角色，如此可以灵活控制云计算管理服务在服务器上的落地和运行，同时，在控制节点扩容的场景下，也支持有限的扩展能力，比如将不同角色分布在不同的服务器上，以增加云管理系统的处理能力。然而，在大规模云计算管理系统部署时，由于涉及的控制节点数量比较多，该部署方案仍然会存在以下几点问题。
第一、将控制节点的主要服务定义为一个控制角色，在大规模场景下控制角色中出现有瓶颈的服务时无法灵活的调整服务部署；目前业界通常的解决方案是将这类服务独立出来在部署工具中预定义为单独角色，这种方式会导致角色过多，部署方案复杂。
第二、在大规模云环境场景下，控制节点数量普遍达到或超过6台，目前业界通常的操作方式是将角色拖动到控制节点主机上或在角色下选择对应落地的控制节点主机，无论是哪种方式，操作的重复动作都比较多，导致部署复杂度增加。
基于此，本公开通过基于角色的角色属性中增加节点类型属性和/或角色聚合属性，根据角色属性将待部署角色对应部署到目标控制节点，根据角色属性中节点类型属性进行部署，便于直接根据角色所支持的节点类型完成角色到目标控制节点的自动部署，而根据角色属性中角色聚合属性进行部署，便于根据角色的角色聚合属性完成角色的迁移和聚合，均可以简化云平台的部署难度和复杂度，提高部署灵活性。其次，可以预先定义包含多个控制节点的控制节点组，角色的部署按照控制节点组操作，可以确保服务在所运行节点上配置的一致性，可以简化云平台的部署难度和复杂度，且支持不同控制节点组中控制节点主机数量不同的场景，提高部署灵活性。
请参阅图1，为本公开一实施例所提供的云平台的物理组网环境的结构示意图，包括部署节点(Deployment Node)、控制节点(Control Node)、计算节点(Compute Node)以及存储资源(Storage Resource)。其中，部署节点可以包括一个或者多个物理服务器(Deployment Node1)，用于实现本公开实施例所提供的云平台部署方法。控制节点可以包括一个或者多个控制节点组，如Control Group1、Control Group2、...Control Group N，每一控制节点组包括一个或者多个控制节点主机，用于运行特定的服务组合。部署节点和控制节点可以合并，也即，部署节点用于实现的本公开实施例所提供的云平台部署方法可以作为一种服务由控制节点执行。计算节点用于提供虚拟资源，可以将虚拟资源进行分组并对应包括多个计算节点，如Computer Node 1、Computer Node 2、...Computer Node M。存储资源包括一个或多个物理存储设备(Storage)，用于为控制节点、计算节点的运行提供对应的存储资源。
请参阅图2，为本公开公开一实施例提供的云平台部署方法的流程示意图，可应用于如图1所示云平台中的部署节点或控制节点，该方法包括如下步骤：步骤101和步骤102。
步骤101，获取部署指令。
这里，部署指令是指触发云平台部署的相关指令，云平台部署可以包括角色部署、服务激活、扩容部署等一个或者多个部署阶段，相应的部署指令可以包括用于触发执行角色部署的相关指令、用于触发执行服务激活的相关指令、用于触发执行扩容部署的相关指令。
部署指令可以是基于软件应用界面接收到的一个或者多个人机交互操作而获取到的，其中对于获取部署指令的人机交互操作的形式并不限制。以部署指令为触发执行角色部署的相关指令为例，可以是通过软件应用界面提供的角色部署虚拟按键，通过接收到针对角色部署虚拟按键的触控操作而获取到部署指令；以部署指令为触发执行服务激活的相关指令为例，可以是通过软件应用界面提供的参数配置窗口接收符合设定要求的参数的输入操作、并通过软件应用界面提供的服务激活虚拟按键接收到对应的触控操作而获取到部署指令；或者，以部署指令为触发执行扩容部署的相关指令为例，可以是通过软件应用界面提供的角色迁移虚拟按键接收对应的触控操作、并通过软件应用界面提供的角色列表接收到对待迁移角色的选定操作而获取到部署指令。
步骤102，根据部署指令，以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点。
这里，角色是指基于云计算管理系统包含的相关服务、组件进行的分组定义，如可以将一个特定的服务组合定义为特定的角色，每一角色可以用于表征一组服务的抽象。属性是指对一个对象的抽象方面的描述，是对象的性质与对象之间关系的统称。角色属性是指对角色的抽象方面的描述，用于表征角色的性质与角色之间的关系。其中，节点类型属性用于表征角色对应所支持的节点类型，如控制节点和/或计算节点。角色聚合属性用于表征角色为聚合角色或者非聚合角色，其中同一聚合角色可以包括多个指定的子角色，通过定义聚合角色可以简化角色列表的配置，以简化部署复杂度。
本公开上述实施例中，根据设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点，其中，通过设置角色属性包括节点类型属性和/或角色聚合属性，基于节点类型属性可以确定相应角色所支持的节点类型，和/或，基于角色聚合属性可以确定相应角色关联的子角色，如此，便于直接根据角色所支持的节点类型完成角色到目标控制节点的自动部署，或者根据角色的角色聚合属性完成角色的迁移和聚合，简化云平台的部署难度和复杂度，提高部署灵活性。
在一些实施例中，将待部署角色部署到控制节点时可以是按照控制节点组操作，将待部署角色对应部署到目标控制节点，包括：将待部署角色对应部署到目标控制节点组；其中，目标控制节点组包括多个控制节点。
这里，控制节点组是指将控制节点按组定义，每一控制节点组包括指定数量的控制节点主机。通过将待部署角色对应部署到目标控制节点组，使得角色的操作均可以基于控制节点组而不是单个控制节点，以保证同一控制节点组内所有控制节点的服务配置相同，降低配置错误概率，减少配置操作次数。
本公开上述实施例中，角色的部署是按照控制节点组操作，可以确保服务在所运行节点上配置的一致性，从而可以简化云平台的部署难度和复杂度，且支持不同控制节点组中控制节点主机数量不同的场景，提高部署灵活性。
请参阅图3，为本公开一实施例提供的角色的示意图，以OpenStack云平台为例，基于特定的服务组合定义角色，可以包括如下角色。
1)Identity，鉴权认证服务。
2)Image，镜像管理服务。
3)network_L2，以太网L2服务。
4)network_L3，以太网L3服务。
5)RabbitMQ，消息服务。
6)MariaDB，数据库管理系统服务。
7)MangoDB，NoSQL的数据库服务。
8)Controller，控制节点服务，其中该角色为聚合角色，包括如下子角色。
8.1)Controller_nova，用于为单个用户或使用群组管理虚拟机实例的整个生命周期，根据用户需求来提供虚拟服务。可以用于负责虚拟机创建、开机、关机、挂起、暂停、调整、迁移、重启、销毁等操作，配置CPU、内存等信息规格。
8.2)Controller_cinder，为运行实例提供稳定的数据块存储服务，它的插件驱动架构有利于块设备的创建和管理，如创建卷、删除卷，在实例上挂载和卸载卷。
8.3)Controller_neutron，提供云计算的网络虚拟化技术，为OpenStack其他服务提供网络连接服务。为用户提供接口，可以定义网络(Network)、子网络(Subnet)、路由器(Router)，配置动态主机设置协议(DHCP)、域名系统(DNS)、负载均衡、以太网(L3)服务，网络支持通用路由封装协议(GRE)、虚拟局域网(VLAN)。
8.4)Controller_ironic，部署物理机跟部署虚拟机都是nova通过创建虚拟机的方式来触发，只是底层调度器(nova-scheduler)和守护进程(nova-compute)的驱动不一样。其中，虚拟机的底层驱动采用的虚拟化管理平台应用程序接口(libvirt)的虚拟化技术，而物理机是采用Ironic技术，Ironic可以看成一组中间软件层应用程序接口(Hypervisor API)的集合，其功能与libvirt类似。
8.5)Controller_heat，提供了一种通过模板定义的协同部署方式，实现云基础设施软件运行环境(计算、存储和网络资源)的自动化部署。
8.6)Controller_backup，提供数据备份服务。
8.7)Controller_telemetry，远程的从物理设备或虚拟设备上高速采集数据的技术。设备通过推模式(Push Mode)主动向采集器上送设备数据信息，提供更实时更高速的数据采集功能。
8.8)Other Controller Roles and Services，其它控制角色集服务，为示例，其它服务不一一列举。
9)Other Common Roles and Services，其它公共服务，为示例，其它服务不一一列举。
请参阅图4，为本公开一实施例提供的角色部署至控制节点的示意图，仍以OpenStack云平台为例，基于特定的服务组合定义角色Service Roles，角色Service Roles包括Identity、Image、network_L2、network_L3、RabbitMQ、MariaDB、MangoDB、Controller、Other Common Roles and Services，定义控 制节点组Controller Group 1包括多个控制节点，如Controller Node 1、Controller Node 2、Controller Node 3，将角色Service Roles统一一次部署到该目标控制节点组Controller Group 1内，保证该目标控制节点组Controller Group 1内所有控制节点Controller Node 1、Controller Node 2和Controller Node 3的服务配置相同，降低配置错误概率和减少配置操作次数。
在一些实施例中，根据部署指令，以及角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点，包括：在角色属性包括节点类型属性的情况下，根据节点类型属性确定待部署角色所支持的节点类型为控制节点时，将待部署角色对应部署到目标控制节点。
节点类型属性是指角色支持的节点类型，如控制节点和/或计算节点。控制节点的标识信息是指用于唯一表征控制节点身份的相关信息，如控制节点的编号、地址、名称地址等。这里，部署指令可以是指携带有目标控制节点的标识信息的角色配置参数，用户可以通过输入控制节点的标识信息，根据节点类型属性确定角色所支持的节点类型为控制节点时，可以自动将相应角色部署到目标控制节点。其中，根据角色所支持的节点类型将待部署角色对应部署到目标控制节点时，也可以是按控制节点组进行操作，获取部署指令为获取目标控制节点组的标识信息，在云平台部署时，用户可以预先定义包含多个控制节点的控制节点组并予以标识，通过输入待进行部署的控制节点组的标识信息作为目标控制节点组，以将指定的角色统一一次部署到该目标控制节点组内。其中，指定的角色可以根据角色属性中的节点类型属性确定，根据节点类型属性确定角色所支持的节点类型为控制节点时，可以自动将相应角色部署到目标控制节点组。
请再次参阅图4，仍以OpenStack云平台为例，用户可以预先定义控制节点组Controller Group 1，并预先定义角色Service Roles中所有角色的角色属性中的节点类型属性支持的节点类型为控制节点，在云平台部署时，用户可以通过输入控制节点组Controller Group 1对应的标识信息而获取到部署指令；或者当目标控制节点组唯一确定的前提下通过触发部署按键而获取到部署指令，触发将角色Service Roles中所有角色自动部署到该控制节点组，不 需要用户的复杂配置，从而提升部署效率和易用性。
在一些实施例中，将待部署角色对应部署到目标控制节点之前，包括如下步骤。
根据角色属性中的依赖属性确定相应角色对应的依赖角色及资源，生成角色依赖关系数据。
根据角色依赖关系数据，获取携带有依赖角色及资源的标识信息的角色配置参数。
将待部署角色对应部署到目标控制节点之后，包括：根据角色依赖关系数据确定部署时序，按照部署时序根据角色配置参数对角色进行激活。
依赖属性是指角色对应的依赖角色及资源。某一角色的部署可能需要依赖其它角色如组件、服务，或者依赖其它资源如数据库，将所需要依赖的其它角色或其它资源通过依赖属性表征，用于在部署节点生成角色依赖关系数据，以形成完整的部署时序。其中，角色依赖关系数据可以是列表形式，对应形成为角色依赖关系列表；或者也可以是树图形式，对应形成为角色依赖关系树。依赖角色及资源的标识信息是指用于唯一表征对应的角色及资源身份的信息，如表征角色的身份信息可以是服务器地址、表征资源身份的信息可以是数据库标识等。通过根据角色属性中的依赖属性生成角色依赖关系数据，在云平台部署时，根据角色的依赖属性定义确定该角色对应的依赖角色及资源，在将待部署角色部署到目标控制节点之前，可以基于人机交互方式相应获取符合该依赖角色及资源定义的角色配置参数，如，根据相应依赖属性定义获取数据库、消息服务器的标识信息的角色配置参数。其中，获取角色配置参数可以通过人机交互的方式获取，如，可以是通过软件应用界面提供的参数配置窗口接收符合该依赖角色及资源定义的角色配置参数；或者，也可以是通过软件应用界面提供的参数选择列表页面接收对页面中显示的依赖角色及资源的选定的角色配置参数等。
角色依赖关系数据用于表征角色部署时所需依赖的角色及资源的依赖关系。根据角色依赖关系数据确定部署时序，按照部署时序根据角色配置参数对角色进行激活，可以包括：根据角色依赖关系数据中每一角色所需依赖的角色及资源的依赖关系，确定各角色的部署时序并形成角色依赖树，通过 遍历角色依赖树，依次对角色调用角色激活接口进行激活。如，角色A的依赖属性定义该角色A对应的依赖角色为角色B，也即角色A的部署需要依赖角色B先完成部署，从而根据角色A的依赖属性所形成的角色依赖关系数据可以确定角色B的部署时序应先于角色A，依次类推，可以形成所有角色的完整的部署时序。
本公开实施例中，通过根据角色属性中的依赖属性定义，相应获取符合依赖属性定义的依赖角色及资源的标识信息的角色配置参数，便于将待部署角色拖动到目标控制节点或者目标控制节点组后，如，根据角色的节点类型属性将相应角色自动拖动到目标控制节点组后，根据角色依赖关系数据所确定的部署时序，按照部署时序并根据对应的角色配置参数调用角色的激活应用程序接口(API)进行角色激活，完成将待部署角色对应部署到目标控制节点。
在一些实施例中，将待部署角色对应部署到目标控制节点之前，还包括：获取携带有浮动互联网协议地址IP的地址信息作为待部署角色的角色配置参数。
依赖角色及资源的标识信息，即浮动IP，是指公开的、可以路由到的IP地址，并且不会自动分配给实体设备。通常，实体设备可以有自动分配的静态IP用于内部网间设备的通讯，这个内部网使用私有地址，这些私有地址不能被路由到，通过浮动IP使得内部网实体设备的服务才能被外网识别和访问。通过浮动IP的设置，可以实现内部网的实体设备之间无延迟替换并对外提供服务。其中，获取浮动IP地址的角色配置参数可以通过人机交互的方式获取，如，可以是通过软件应用界面提供的参数配置窗口接收输入的浮动IP地址的角色配置参数；或者，也可以是通过软件应用界面提供的参数选择列表页面接收对浮动IP地址的选定的角色配置参数等。
需要说明的是，在云平台部署时，可以首先包括角色部署阶段，也即基于角色的节点类型属性将角色拖动到目标控制节点或控制节点组，再进一步包括服务激活阶段，也即通过人机交互的方式获取配置参数，以适应于不同的个性化角色而形成符合角色要求的参数列表。本实施例中，配置参数包括为待部署角色配置的对应的依赖角色及资源的标识信息、以及为待部署角色 配置的对应的IP的地址信息，以便于基于配置参数对角色进行激活后满足各角色的不同性能需求。其中，通过人机交互的方式获取到相应的配置参数可以视为获取到执行服务激活的部署指令，从而实现将待部署角色拖动到目标控制节点或者目标控制节点组后遍历角色依赖关系数据，调用角色对应的激活应用程序接口(Application Programming Interface，API)并基于上述参数列表进行角色激活，完成将待部署角色对应部署到目标控制节点或者目标控制节点组。
在一些实施例中，按照部署时序根据角色配置参数对角色进行激活，包括：按照部署时序，根据角色配置参数以及角色属性中的角色操作属性调用对应的角色激活接口，对角色进行激活。
角色操作属性是指角色对应的一组角色操作方法，包括激活、迁移、去激活等API接口及其相应数据参数定义。通过定义角色操作属性，便于根据角色属性相应执行角色的指定操作，实现快速部署。在云平台部署时，通过将待部署角色拖动到目标控制节点或者目标控制节点组后，通过人机交互的方式获取符合角色要求的配置参数，根据角色属性生成角色依赖关系数据以确定部署时序，并遍历该角色依赖关系数据以根据部署时序调用角色对应的激活API并基于相应的参数列表传递参数进行角色激活，完成将待部署角色对应部署到目标控制节点或者目标控制节点组。
在一些实施例中，将待部署角色对应部署到控制节点时是按照控制节点组操作，将待部署角色对应部署到目标控制节点组之前，包括如下步骤。
获取控制节点主机的选取指令。
根据选取指令将对应的控制节点主机形成控制节点组。
这里，每一控制节点组可以相应包括指定数量的控制节点主机。获取控制节点主机的选取指令，可以是通过软件应用界面提供的参数输入窗口接收输入的控制节点主机标识，而相应获取到控制节点主机的选取指令；或者，也可以是通过软件应用界面提供的控制节点主机列表页面，接收对页面中显示的控制节点主机的选取操作而相应获取到的控制节点主机的选取指令。根据控制节点主机的选取指令而相应定义控制节点组。
请参阅图5，为本公开一实施例提供的控制节点扩容场景下角色迁移的 示意图，其中控制节点组包括分别包含不同控制节点主机的控制节点组Controller Group 1和控制节点组Controller Group 2。控制节点组Controller Group 1包括控制节点Controller Node 1、Controller Node 2和Controller Node 3，控制节点组Controller Group 2包括控制节点Controller Node 4、Controller Node 5和Controller Node 6。在云平台部署时，可以通过选取控制节点Controller Node 1、Controller Node 2和Controller Node 3定义形成控制节点组Controller Group 1，通过选取控制节点Controller Node 4、Controller Node 5和Controller Node 6定义形成控制节点组Controller Group 2，可以基于控制节点组按组进行部署操作，支持不同控制节点组中包含不同主机数量不同的场景，在服务分布式部署时简化部署复杂度。
在一些实施例中，获取部署指令包括：获取携带有待迁移角色的标识信息的角色迁移指令。
根据部署指令、以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点，包括如下步骤。
在角色属性包括角色聚合属性的情况下，基于角色迁移指令，根据设角色聚合属性确定待迁移角色为聚合角色且待迁移角色为部分迁移；
展开待迁移角色关联的子角色列表信息，基于子角色列表信息选定待迁移子角色迁移到目标控制节点。
角色聚合属性是指表征角色为包括多个子角色的聚合角色或者为非聚合角色。通过增加角色聚合属性，可以将具有特定关联的多个角色进行关联定义形成聚合角色，其中，聚合角色内包括的多个角色相应称为子角色。待迁移角色的标识信息是指能够唯一表征待迁移角色身份的相关信息。这里，部署指令是指携带有待迁移角色的标识信息的角色迁移指令。通过根据角色迁移指令，确定对应的待迁移角色为聚合角色时，展开待迁移角色关联的子角色列表信息，通过获取对子角色列表信息的选定指令而将相应的待迁移子角色迁移到目标控制节点，相应实现针对聚合角色的部分迁移。
获取携带有待迁移角色的标识信息的角色迁移指令，可以包括但不限于如下几种方式：第一，通过软件应用界面提供的角色列表页面，接收对角色列表页面中显示的待迁移角色的选定并拖动操作而获取到的携带有待迁移 角色的标识信息的角色迁移指令；第二、通过软件应用界面提供的角色信息窗口，接收输入的待迁移角色的标识信息并确认操作而获取到的携带有待迁移角色的标识信息的角色迁移指令；第三、通过软件应用界面提供的与各角色对应的角色迁移虚拟按键，接收对角色迁移虚拟按键的触控操作，而获取到的携带有对应的待迁移角色的标识信息的角色迁移指令；第四，通过软件应用界面提供的角色迁移虚拟按键，接收角色迁移的触发指令，并基于角色列表页面接收待迁移角色的选定操作或基于角色信息窗口接收输入的待迁移角色的标识信息，从而获取到的携带有对应的待迁移角色的标识信息的角色迁移指令。
本公开实施例中，角色属性中增加角色聚合属性，以支持多角色聚合形成聚合角色，而相应支持针对聚合有多个角色的聚合角色执行迁移部署操作，在云平台部署时，可以针对聚合角色整体部署，从而实现对聚合角色包含的子角色整体一次部署，也可以根据不同实际需求展开聚合角色所关联的子角色，针对部分子角色进行选定和部署。如此，通过支持角色聚合并采用聚合角色实现整体或者部分迁移，不仅能够满足不同需求的部署目的，而且可以减少部署操作，实现灵活的服务迁移和扩展，简化部署复杂度和提升部署效率。
其中，根据角色聚合属性将待迁移角色迁移到目标控制节点时，也可以是按控制节点组进行操作，根据选定指令将待迁移子角色迁移到目标控制节点，可以是根据选定指令将待迁移子角色迁移到目标控制节点组。
请再次参阅图5，仍以OpenStack云平台为例，在云平台部署时，可以支持在控制节点扩展场景下针对聚合角色Controller进行部分迁移。首先，根据控制节点Controller Node 1、Controller Node 2和Controller Node 3定义形成控制节点组Controller Group 1。初次部署完成后，比如基于各角色的角色属性中的节点类型属性进行自动部署完成后，控制节点组Controller Group 1中各控制节点Controller Node 1、Controller Node 2和Controller Node 3分别部署有相同的角色Service Roles，角色Service Roles包括如下子角色：Identity、Image、network_L2、network_L3、RabbitMQ、MariaDB、MangoDB、Controller、Other Common Roles and Services。出于扩容的需求，新加入控制 节点Controller Node 4、Controller Node 5和Controller Node 6并定义形成新的控制节点组Controller Group 2。通过获取携带有聚合角色Controller的角色迁移指令，展开聚合角色Controller关联的子列表信息，基于子列表信息获取对待迁移子角色Controller_nova、Controller_cinder、Controller_neutron、Controller_ironic的选定指令，并根据选定指令将待迁移子角色Controller_nova、Controller_cinder、Controller_neutron、Controller_ironic迁移到目标控制节点组Controller Group 2，实现针对聚合角色Controller的部分迁移。
在一些实施例中，根据子角色列表信息选定待迁移子角色迁移到目标控制节点之后，包括如下步骤。
在待迁移子角色所在原控制节点调用对应的角色去激活接口，对待迁移子角色进行去激活。
在目标控制节点调用对应的角色激活接口，对待迁移子角色进行激活。
去激活是指终止激活状态的操作。在云平台部署时，针对角色进行迁移的方案中，将对应的待迁移子角色拖动到对应的目标控制节点后，还包括对迁移后的角色根据角色聚合属性进行重新聚合，对聚合角色进行更新。将对应的待迁移子角色拖动到对应的目标控制节点后，还包括在待迁移角色所在原控制节点进行去激活、以及在待迁移角色迁移后的目标控制节点进行激活。其中选定待迁移子角色迁移到目标控制节点的迁移操作，迁移操作将生成并携带相应迁移参数，迁移参数包括待迁移子角色所在原控制节点的标识信息和迁移至的目标控制节点的标识信息，可以根据迁移参数，相应在待迁移子角色所在原控制节点调用对应的角色去激活接口(Application Programming Interface，API)，对待迁移子角色进行去激活；然后在目标控制节点调用对应的角色激活接口，对待迁移子角色进行激活，从而完成角色迁移。
其中，根据角色聚合属性将待迁移子角色迁移到目标控制节点时，也可以是按控制节点组进行操作。相应的，将对应的待迁移子角色拖动到对应的目标控制节点组后，对待迁移子角色的去激活和激活操作也是按控制节点组进行操作，具体包括：在待迁移子角色所在原控制节点组进行去激活、以及 在待迁移子角色迁移后的目标控制节点组进行激活。相应迁移操作对应的迁移参数包括待迁移子角色所在原控制节点组的标识信息和迁移至的目标控制节点组的标识信息。
在一些实施例中，根据部署指令、以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点，还包括如下步骤。
在角色属性包括角色聚合属性的情况下，根据角色聚合属性确定待迁移角色为非聚合角色；或者，根据角色聚合属性确定待迁移角色为聚合角色且待迁移角色为整体迁移。
将待迁移角色对应迁移到目标控制节点。
角色聚合属性是指表征角色为包括多个子角色的聚合角色或者为非聚合角色。通过增加角色聚合属性，可以将具有特定关联的多个角色进行关联定义形成聚合角色，其中，聚合角色内包括的多个角色相应称为子角色。通过根据角色迁移指令，确定对应的待迁移角色为非聚合角色时，则将待迁移角色对应迁移到目标控制节点。或者，通过根据角色迁移指令，确定对应的待迁移角色为聚合角色且待迁移角色为整体迁移时，则将待迁移角色对应迁移到目标控制节点。
其中，根据角色聚合属性将待迁移角色迁移到目标控制节点时，也可以是按控制节点组进行操作。也即，将待迁移角色对应迁移到目标控制节点可以是将待迁移角色对应迁移到目标控制节点组。
请再次参阅图5，仍以OpenStack云平台为例，在云平台部署时，可以支持在控制节点扩展场景下针对非聚合角色network_L2、network_L3进行按控制节点组迁移。云平台初次部署时，首先根据控制节点Controller Node 1、Controller Node 2和Controller Node 3定义形成控制节点组Controller Group 1。初次部署完成后，比如基于各角色的角色属性中的节点类型属性进行自动部署完成后，控制节点组Controller Group 1中各控制节点Controller Node 1、Controller Node 2和Controller Node 3分别部署有相同的角色Service Roles，角色Service Roles包括如下子角色：Identity、Image、network_L2、network_L3、RabbitMQ、MariaDB、MangoDB、Controller、Other Common Roles  and Services。出于扩容的需求，新加入控制节点Controller Node 4、Controller Node 5和Controller Node 6并定义形成新的控制节点组Controller Group 2。通过获取携带有非聚合角色network_L2、network_L3的角色迁移指令，将非聚合角色network_L2、network_L3迁移到目标控制节点组Controller Group 2，实现针对非聚合角色network_L2、network_L3的直接迁移。需要说明的是，针对聚合角色的整体迁移与非聚合角色的迁移方式相同，通过获取携带有聚合角色Controller的整体迁移的角色迁移指令，将聚合角色Controller迁移到目标控制节点组Controller Group 2，实现针对聚合角色Controller的直接整体迁移。
本公开实施例中，在云平台部署时，根据角色迁移指令确定当前待进行迁移的角色为待迁移角色，判断待迁移角色为非聚合角色时，将待迁移角色迁移到对应的目标控制节点或目标控制节点组；判断待迁移角色为聚合角色时，则进一步判断待迁移角色为整体迁移或者部分迁移，当待迁移角色为整体迁移时，则将迁移角色迁移到对应的目标控制节点或目标控制节点组；当待迁移角色为部分迁移时，则展开聚合角色中包含的子角色列表信息，基于子角色列表信息获取对子角色的选定指令，并根据选定指令将子角色迁移到对应的目标控制节点或目标控制节点组。如此，通过在角色属性中增加角色聚合属性支持云平台部署时角色的定义和操作，在大规模场景下支持聚合角色展开从而实现灵活的角色部署，在其它场景应用也支持采用聚合角色整体部署，简化角色定义的复杂度，提升部署效率。
在一些实施例中，将待迁移角色对应迁移到目标控制节点之后，包括如下步骤。
在待迁移角色所在原控制节点调用对应的角色去激活接口，对待迁移角色进行去激活。
在目标控制节点调用对应的角色激活接口，对待迁移角色进行激活。
去激活是指终止激活状态的操作。在云平台部署时，针对角色进行迁移的方案中，将对应的待迁移角色拖动到对应的目标控制节点后，还包括对迁移后的角色进行重新聚合。其中，对应的待迁移角色可以是指聚合角色整体、非聚合角色或子角色。将对应的待迁移角色拖动到对应的目标控制节点后， 还包括在待迁移角色所在的原控制节点进行去激活操作、以及在待迁移角色迁移后的目标控制节点进行激活操作。其中，将待迁移角色对应迁移到目标控制节点的迁移操作完成后，迁移操作对应的待迁移角色将携带相应迁移参数，迁移参数包括待迁移角色所在原控制节点的标识信息和迁移至的目标控制节点的标识信息，将待迁移角色对应迁移到目标控制节点后，可以根据迁移参数相应在待迁移角色所在原控制节点调用对应的角色去激活接口，对待迁移角色进行去激活；并在目标控制节点调用对应的角色激活接口，对待迁移角色进行激活，从而完成角色迁移。
其中，根据角色聚合属性将待迁移角色迁移到目标控制节点时，也可以是按控制节点组进行操作。相应的，将对应的待迁移角色拖动到对应的目标控制节点组后，对待迁移角色的去激活和激活操作也是按控制节点组进行操作，具体包括：在待迁移角色所在原控制节点组进行去激活、以及在待迁移角色迁移后的目标控制节点组进行激活。相应迁移操作对应的迁移参数包括：待迁移角色所在原控制节点组的标识信息和迁移至的目标控制节点组的标识信息。
在一些实施例中，方法还包括：预先定义云平台中的角色及角色对应的角色属性，角色属性包括如下至少其中一种：节点类型属性、角色聚合属性。其中，角色属性包括身份属性、依赖属性、服务属性、节点类型属性、角色聚合属性和角色操作属性。
角色是指基于云计算管理系统包含的相关服务、组件进行的分组定义，如可以将一个特定的服务组合定义为特定的角色，每一角色可以用于表征一组服务的抽象。角色属性是指对角色的抽象方面的描述，用于表征角色的性质与角色之间的关系。节点类型属性是指角色支持的节点类型，如控制节点和/或计算节点。角色聚合属性是指用于表征角色为聚合角色或者非聚合角色，其中同一聚合角色可以包括多个指定的关联子角色。身份属性是指用于表征角色身份的相关信息，如角色名称及描述信息。依赖属性是指用于表征角色对应的依赖角色及资源，如表征相应角色部署所需要依赖的其它角色的标识信息或其它资源的标识信息。服务属性是指角色所包含的服务列表及服务运行模式，其中服务运行模式主要包括高可用性集群(High Availability， HA)服务运行模式或负载均衡集群(Load Balance，LB)服务运行模式。角色操作属性是指用于表征角色对应的一组角色操作方法，包括激活、迁移、去激活等API接口及其相应数据参数定义。
本公开实施例中，通过定义角色及角色属性，其中角色属性包括节点类型属性，基于节点类型属性可以确定相应角色所支持的节点类型，便于直接根据角色所支持的节点类型完成角色到目标控制节点或者目标控制节点组的自动部署；角色属性包括角色聚合属性，基于角色聚合属性可以确定相应角色关联的子角色，便于根据角色的角色聚合属性完成聚合角色的整体迁移或部分迁移、以及迁移后的重新聚合；角色属性包括角色操作属性，基于角色操作属性可以确定角色对应的一组操作方法，如激活、迁移、去激活操作方法，确定相应执行操作方法所需API接口及相应参数定义。在云平台部署时，针对不同场景下部分角色存在瓶颈时，可以扩容控制节点，并基于角色属性确定角色类型并按相应方法迁移角色，针对非聚合角色，可以直接从原控制节点组迁移至目标控制节点组；针对聚合角色，如果是整体迁移，则可以直接从原控制节点组迁移至目标控制节点组；如果是部分迁移，则展开聚合角色，将需要迁移的角色迁移至目标控制节点组，迁移后再原控制节点组和目标控制节点组根据角色的角色聚合属性重新聚合。
为了能够对本公开实施例所提供的云平台部署方法的实现流程能够进一步具体的了解，下面分别结合典型场景下的云平台部署方法以及控制节点扩容场景下云平台部署方法进行举例性说明，请参阅图6，云平台部署方法包括如下步骤S61至步骤S66.
步骤S61，预定义控制节点组；其中，可以选择控制节点主机，如根据环境实际情况选择1～3台服务器定义为云平台控制节点组Controller Group 1。
步骤S62，预定义角色和角色属性；其中，可以根据云平台中组件、服务进行分组定义，将特定的服务组合分别相应定义为角色。以OpenStack云平台为例，请再次参阅图3，定义角色Service Roles可以包括：Identity、Image、network_L2、network_L3、RabbitMQ、MariaDB、MangoDB、Controller、Other Common Roles and Services。其中，Controller为聚合角色，对应关联的子角 色包括：Controller_nova、Controller_cinder、Controller_neutron、Controller_ironic、Controller_heat、Controller_backup、Controller_telemetry、Other Controller Roles and Services。
步骤S63，根据角色的节点类型属性将对应角色自动拖动到目标控制节点组；其中，可以基于部署指令执行根据角色的节点类型属性将对应角色自动拖动到目标控制节点组的操作。部署指令可以是指基于软件应用界面提供的部署虚拟按键，通过人机交互接收到的针对部署虚拟按键的触控操作而获取到的部署指令；或者，也可以是指基于软件应用界面提供的输入窗口接收输入的目标控制节点组的标识信息并确认而获取到的部署指令。以OpenStack云平台为例，请再次参阅图4，根据控制节点组的定义以及角色定义，角色Service Roles中所有角色的节点类型属性均包括支持控制节点，将角色Service Roles中所有角色自动部署到控制节点组Controller Group 1。
步骤S64，根据角色属性中依赖属性生成角色依赖关系列表，扫描全部角色的依赖资源生成依赖关系树；其中，依赖关系树是指以角色、资源等为节点并通过节点之前的连线表征节点之间依赖关系所形成的树图。通过形成依赖关系树，便于后续根据依赖关系树遍历执行角色激活操作，形成完整部署时序关系。
步骤S65，获取角色配置参数，角色配置参数包括但不限于：目标控制节点组的标识信息、对应的依赖角色及资源的标识信息以及浮动IP的地址信息；其中，目标控制节点组的标识信息可以是指对应待部署角色落地的主机组及主机列表。对应的依赖角色及资源的标识信息可以是指对应待部署角色的依赖属性定义中所需要的依赖角色和依赖资源，如数据库、消息服务器对应的配置信息。这里，通过人机交互方式获取角色配置参数，可以将获取到对应的角色配置参数作为在云平台部署过程中执行角色激活操作的部署指令。
步骤S66，调用角色激活接口激活角色；其中，根据待部署角色对应的角色属性，调用对应的角色激活接口，并传递上述角色配置参数，遍历依赖关系树完成角色激活。
上述实施例所提供的云平台部署方法，主要适用于典型场景下的云平台 的服务部署过程，通过角色属性中增加节点类型属性，根据节点类型属性直接将对应角色拖动到控制节点组，基于角色节点类型属性实现统一部署，可以提升部署效率和易用性；且所有角色的操作均基于控制节点组进行，可以保证控制节点组内所有的主机的角色配置相同，简化部署复杂度。
控制节点扩容场景下云平台部署方法主要包括在控制节点扩容场景下角色迁移方案，可以是基于已初始部署完成的云平台架构，如采用图6所示的云平台部署方法初始部署完成的云平台架构上基于控制节点扩容需求下执行，请参阅图7，云平台部署方法如下步骤S71-步骤710.
步骤S71，定义新的控制节点组Controller Group 2；其中，可以是选择新加入的节点定义新的控制节点组，因所有角色的操作均基于控制节点组，选择新加入节点完成控制节点组定义，以为后续角色操作做好准备。
步骤S72，判断待迁移角色是否为聚合角色，若是，则执行步骤S73，若否，则执行步骤S76；这里，待迁移角色可以理解为是角色迁移方案中的待部署角色。其中，待迁移角色的确定可以根据不同的角色迁移指令而触发，如，可以是基于角色列表页面直接选定待迁移角色并拖动操作，基于选定和拖动操作而获取到携带有该待迁移角色的标识信息的角色迁移指令；可以是基于角色迁移按键的触控操作获取到迁移指令，并基于该迁移指令接收待迁移角色的选定操作或者接收输入的待迁移角色的标识信息，从而相应获取到携带有待迁移角色的标识信息的角色迁移指令；可以是基于角色列表页面接收待迁移角色的选定操作以及角色迁移按键的触控操作，从而获取到携带有待迁移角色的标识信息的角色迁移指令。
步骤S73，拖动待迁移角色到目标控制节点组，相应生成迁移参数；其中，迁移参数包括待迁移角色所在原控制节点组及主机列表、以及待迁移角色迁移至目标控制节点组及主机列表。
步骤S74，在待迁移角色的原控制节点组调用对应的去激活接口，对待迁移角色执行去激活操作。
步骤S75，在待迁移角色的目标控制节点组内调用对应的激活接口，对待迁移角色执行激活操作。
步骤S76，确定待迁移角色为聚合角色时，判断待迁移角色为整体迁移或者部分迁移，如果是整体迁移，则返回执行步骤S73，如果是部分迁移，则执行步骤S77。
步骤S77，展开聚合角色关联的子角色列表信息。
步骤S78，拖动待迁移子角色至目标控制节点组，相应生成迁移参数；其中，迁移参数包括待迁移子角色所在原控制节点组及主机列表、以及待迁移子角色迁移至目标控制节点组及主机列表。
步骤S79，在待迁移子角色的原控制节点组调用对应的去激活接口，对待迁移角色执行去激活操作。
步骤S710，在待迁移子角色的目标控制节点组内调用对应的激活接口，对待迁移角色执行激活操作。
上述实施例所提供的云平台部署方法，主要适用于控制节点扩容场景下云平台的服务部署过程中角色迁移方案，通过角色属性中增加角色聚合属性，在大规模场景下支持聚合角色展开从而实现灵活的角色部署，在典型场景应用时采用聚合角色部署而降低角色配置复杂度；同时，将控制节点分组管理，所有角色的操作均基于控制节点组进行，保证同一控制节点组内所有主机的角色配置相同，简化环境部署复杂度，提升易用性。请参阅图8，本公开实施例另一方面提供一种云平台部署装置，包括获取模块11，用于获取部署指令；部署模块13，用于根据部署指令，以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点。
其中，部署模块13，具体用于在角色属性包括节点类型属性的情况下，根据节点类型属性确定待部署角色所支持的节点类型为控制节点时，将待部署角色对应部署到目标控制节点。
其中，部署模块13，还用于根据角色属性中的依赖属性确定相应角色对应的依赖角色及资源，生成角色依赖关系数据；获取模块11，还用于根据角色依赖关系数据，获取携带有依赖角色及资源的标识信息的角色配置参数；装置还包括激活模块15，激活模块15用于根据角色依赖关系数据确定部署时序，按照部署时序根据角色配置参数对角色进行激活。
其中，获取模块11，具体用于获取携带有待迁移角色的标识信息的角色迁移指令；部署模块13，具体用于在角色属性包括角色聚合属性的情况下，基于角色迁移指令，根据角色聚合属性确定待迁移角色为聚合角色且待迁移角色为部分迁移；展开待迁移角色关联的子角色列表信息，基于子角色列表信息选定待迁移子角色迁移到目标控制节点。
其中，装置还包括去激活模块16和激活模块15，去激活模块16用于在待迁移子角色所在原控制节点调用对应的角色去激活接口，对待迁移子角色进行去激活；激活模块15，用于在目标控制节点调用对应的角色激活接口，对待迁移子角色进行激活。
其中，部署模块13，还用于在角色属性包括角色聚合属性的情况下，根据角色聚合属性确定待迁移角色为非聚合角色；或者，根据角色聚合属性确定待迁移角色为聚合角色且待迁移角色为整体迁移；将待迁移角色对应迁移到目标控制节点。
其中，装置还包括去激活模块16和激活模块15，去激活模块16，用于在待迁移角色所在原控制节点调用对应的角色去激活接口，对待迁移子角色进行去激活；激活模块15，用于在目标控制节点调用对应的角色激活接口，对待迁移角色进行激活。
其中，部署模块13，具体用于将待部署角色对应部署到目标控制节点组；其中，目标控制节点组包括多个控制节点。
其中，装置还包括节点定义模块10，用于获取控制节点主机的选取指令；根据选取指令将对应的控制节点主机形成控制节点组。
其中，装置还包括角色定义模块12，用于预先定义云平台中的角色及角色对应的角色属性，角色属性包括如下至少其中一种：节点类型属性、角色聚合属性。
上述实施例提供的云平台部署装置在进行云平台部署时，仅以上述各程序模块的划分进行举例说明，在实际应用中，可以根据需要而将上述步骤分配由不同的程序模块完成，即可以将装置的内部结构划分成不同的程序模块，以完成以上描述的全部或者部分处理。另外，上述实施例提供的云平台部署装置与云平台部署方法实施例属于同一构思，其具体实现过程详见方法 实施例，这里不再赘述。
本发明实施例另一方面还提供一种服务器，该服务器可以归属于云平台中的部署节点或控制节点，请参阅图9，该服务器包括处理器201以及用于存储能够在处理器201上运行的计算机程序的存储介质202，其中，处理器201用于运行计算机程序时，执行本公开任一实施例所提供的云平台部署方法的步骤。这里，处理器201和存储介质202并非指代对应的数量为一个，而是可以为一个或者多个。其中，该服务器还包括内存203、网络接口204以及将处理器201、内存203、网络接口204及存储介质202连接的系统总线205。存储介质202中存储有操作系统和用于实现本发明实施例所提供的云平台部署方法的云平台部署装置，该处理器201用于提高计算和控制能力，支撑整个服务器的运行。该内存203用于为存储介质202中的内存缓存管理方法的运行提供环境，网络接口204用于其它节点进行网络通信。
本发明实施例还提供了一种计算机存储介质，例如包括存储有计算机程序的存储器，该计算机程序可以由处理器执行，以完成本发明任一实施例所提供的云平台部署方法的步骤。该计算机存储介质可以是FRAM、ROM、PROM、EPROM、EEPROM、Flash Memory、磁表面存储器、光盘、或CD-ROM等存储器；也可以是包括上述存储器之一或任意组合的各种设备。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。本发明的保护范围应以所述权利要求的保护范围以准。

Claims (13)

  1. 一种云平台部署方法，其包括：
    获取部署指令；
    根据所述部署指令，以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点。
  2. 如权利要求1所述的方法，其中，所述根据所述部署指令，以及所述角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点，包括：
    在所述角色属性包括节点类型属性的情况下，根据所述节点类型属性确定待部署角色所支持的节点类型为控制节点时，将所述待部署角色对应部署到所述目标控制节点。
  3. 如权利要求2所述的方法，其中，所述将所述待部署角色对应部署到所述目标控制节点之前，包括：
    根据所述角色属性中的依赖属性确定相应角色对应的依赖角色及资源，生成角色依赖关系数据；
    根据所述角色依赖关系数据，获取携带有依赖角色及资源的标识信息的角色配置参数；
    所述将所述待部署角色对应部署到所述目标控制节点之后，包括：
    根据所述角色依赖关系数据确定部署时序，按照所述部署时序根据所述角色配置参数对所述角色进行激活。
  4. 如权利要求1所述的方法，其中，所述获取部署指令包括：
    获取携带有待迁移角色的标识信息的角色迁移指令；
    所述根据所述部署指令、以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点，包括：
    在所述角色属性包括角色聚合属性的情况下，基于所述角色迁移指令，根据所述角色聚合属性确定所述待迁移角色为聚合角色且所述待迁移角色为部分迁移；
    展开所述待迁移角色关联的子角色列表信息，基于所述子角色列表信息选定待迁移子角色迁移到目标控制节点。
  5. 如权利要求4所述的方法，其中，所述根据所述子角色列表信息选定待迁移子角色迁移到目标控制节点之后，包括：
    在所述待迁移子角色所在原控制节点调用对应的角色去激活接口，对所述待迁移子角色进行去激活；
    在所述目标控制节点调用对应的角色激活接口，对所述待迁移子角色进行激活。
  6. 如权利要求4所述的方法，其中，所述根据所述部署指令、以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点，还包括：
    在所述角色属性包括角色聚合属性的情况下，根据所述角色聚合属性确定所述待迁移角色为非聚合角色；或者，根据所述角色聚合属性确定所述待迁移角色为聚合角色且所述待迁移角色为整体迁移；
    将所述待迁移角色对应迁移到目标控制节点。
  7. 如权利要求6所述的方法，其中，所述将所述待迁移角色对应迁移到目标控制节点之后，包括：
    在所述待迁移角色所在原控制节点调用对应的角色去激活接口，对所述待迁移角色进行去激活；
    在所述目标控制节点调用对应的角色激活接口，对所述待迁移角色进行激活。
  8. 如权利要求1至7中任一项所述的方法，其中，所述将待部署角色对应部署到目标控制节点，包括：
    将待部署角色对应部署到目标控制节点组；其中，所述目标控制节点组包括多个控制节点。
  9. 如权利要求8所述的方法，其中，所述将待部署角色对应部署到目标控制节点组之前，包括：
    获取控制节点主机的选取指令；
    根据所述选取指令将对应的所述控制节点主机形成控制节点组。
  10. 如权利要求1至7中任一项所述的方法，其中，还包括：
    预先定义云平台中的角色及所述角色对应的角色属性，所述角色属性包括如下至少其中一种：节点类型属性、角色聚合属性。
  11. 一种云平台部署装置，其包括：
    获取模块，用于获取部署指令；
    部署模块，用于根据所述部署指令，以及设置角色的角色属性中的节点类型属性和/或角色聚合属性，将待部署角色对应部署到目标控制节点。
  12. 一种服务器，其包括处理器和用于存储能够在处理器上运行的计算机程序的存储器；其中，
    所述处理器用于运行所述计算机程序时，执行权利要求1至10中任一项所述云平台部署方法。
  13. 一种存储介质，其所述存储介质中存储有可执行指令，所述可执行指令被处理器执行时实现权利要求1至10中任一项所述云平台部署方法。
PCT/CN2019/126679 2018-12-26 2019-12-19 云平台部署方法、装置、服务器及存储介质 WO2020135228A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP19902781.4A EP3905588A4 (en) 2018-12-26 2019-12-19 METHOD AND DEVICE FOR DEPLOYING A CLOUD PLATFORM, SERVER AND STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811599579.2 2018-12-26
CN201811599579.2A CN111371579B (zh) 2018-12-26 2018-12-26 云平台部署方法、装置、服务器及存储介质

Publications (1)

Publication Number Publication Date
WO2020135228A1 true WO2020135228A1 (zh) 2020-07-02

Family

ID=71129142

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/126679 WO2020135228A1 (zh) 2018-12-26 2019-12-19 云平台部署方法、装置、服务器及存储介质

Country Status (3)

Country Link
EP (1) EP3905588A4 (zh)
CN (1) CN111371579B (zh)
WO (1) WO2020135228A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112783668A (zh) * 2020-12-30 2021-05-11 宁波智能成型技术创新中心有限公司 基于RabbitMQ的海量智能制造设备的数据采集处理方法
CN114006815A (zh) * 2020-07-13 2022-02-01 中移(苏州)软件技术有限公司 云平台节点的自动化部署方法、装置、节点及存储介质
CN114116066A (zh) * 2021-11-30 2022-03-01 湖南麒麟信安科技股份有限公司 一种云平台集群控制方法、系统及存储介质
CN115225635A (zh) * 2022-06-30 2022-10-21 浪潮云信息技术股份公司 一种多云纳管方法及装置
CN115314381A (zh) * 2022-10-11 2022-11-08 统信软件技术有限公司 一种自动部署方法、装置与计算设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113407197B (zh) * 2021-05-21 2024-05-07 北京达佳互联信息技术有限公司 服务部署方法、装置、电子设备以及存储介质
CN113900809A (zh) * 2021-10-09 2022-01-07 江苏安超云软件有限公司 云计算管理平台实施复杂度评估的方法及应用
CN114089721A (zh) * 2021-11-17 2022-02-25 东方红卫星移动通信有限公司 基于云平台的控制系统构建方法及控制系统
CN114244836B (zh) * 2021-12-17 2023-12-05 杭州视洞科技有限公司 一种混合云场景中服务器批量管理方法
CN117270888B (zh) * 2023-11-24 2024-04-16 之江实验室 一种云端应用部署方法、系统、装置及计算机设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104679608A (zh) * 2015-02-09 2015-06-03 广州杰赛科技股份有限公司 一种基础设施虚拟化平台构建方法及其镜像管理结构
CN106506636A (zh) * 2016-11-04 2017-03-15 武汉噢易云计算股份有限公司 一种基于OpenStack的云平台集群方法及系统
US20180234351A1 (en) * 2017-02-14 2018-08-16 At&T Intellectual Property I, L.P. Systems and Methods For Allocating and Managing Resources in an Internet of Things Environment Using Location Based Focus of Attention
CN109067877A (zh) * 2018-08-03 2018-12-21 平安科技（深圳）有限公司 一种云计算平台部署的控制方法、服务器及存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103346974B (zh) * 2013-06-03 2015-04-08 华为技术有限公司 一种业务流程的控制方法及网络设备
US9954949B2 (en) * 2015-04-30 2018-04-24 Hewlett Packard Enterprise Development Lp Cloud images
CN106878334A (zh) * 2015-05-13 2017-06-20 西安三星电子研究有限公司 云的自动化部署系统和方法
CN105100267B (zh) * 2015-08-24 2018-12-14 用友网络科技股份有限公司 大企业私有云的部署装置和方法
US10338981B2 (en) * 2016-12-06 2019-07-02 Vmware, Inc Systems and methods to facilitate infrastructure installation checks and corrections in a distributed environment
CN108134690B (zh) * 2017-12-13 2021-07-27 中盈优创资讯科技有限公司 网络业务部署流程控制方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104679608A (zh) * 2015-02-09 2015-06-03 广州杰赛科技股份有限公司 一种基础设施虚拟化平台构建方法及其镜像管理结构
CN106506636A (zh) * 2016-11-04 2017-03-15 武汉噢易云计算股份有限公司 一种基于OpenStack的云平台集群方法及系统
US20180234351A1 (en) * 2017-02-14 2018-08-16 At&T Intellectual Property I, L.P. Systems and Methods For Allocating and Managing Resources in an Internet of Things Environment Using Location Based Focus of Attention
CN109067877A (zh) * 2018-08-03 2018-12-21 平安科技（深圳）有限公司 一种云计算平台部署的控制方法、服务器及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3905588A4 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006815A (zh) * 2020-07-13 2022-02-01 中移(苏州)软件技术有限公司 云平台节点的自动化部署方法、装置、节点及存储介质
CN114006815B (zh) * 2020-07-13 2024-01-26 中移(苏州)软件技术有限公司 云平台节点的自动化部署方法、装置、节点及存储介质
CN112783668A (zh) * 2020-12-30 2021-05-11 宁波智能成型技术创新中心有限公司 基于RabbitMQ的海量智能制造设备的数据采集处理方法
CN112783668B (zh) * 2020-12-30 2023-09-01 宁波智能成型技术创新中心有限公司 基于RabbitMQ的海量智能制造设备的数据采集处理方法
CN114116066A (zh) * 2021-11-30 2022-03-01 湖南麒麟信安科技股份有限公司 一种云平台集群控制方法、系统及存储介质
CN114116066B (zh) * 2021-11-30 2024-05-07 湖南麒麟信安科技股份有限公司 一种云平台集群控制方法、系统及存储介质
CN115225635A (zh) * 2022-06-30 2022-10-21 浪潮云信息技术股份公司 一种多云纳管方法及装置
CN115314381A (zh) * 2022-10-11 2022-11-08 统信软件技术有限公司 一种自动部署方法、装置与计算设备

Also Published As

Publication number Publication date
EP3905588A1 (en) 2021-11-03
CN111371579A (zh) 2020-07-03
EP3905588A4 (en) 2022-01-19
CN111371579B (zh) 2023-04-07

Similar Documents

Publication Publication Date Title
WO2020135228A1 (zh) 云平台部署方法、装置、服务器及存储介质
US10701139B2 (en) Life cycle management method and apparatus
CN111385114B (zh) Vnf服务实例化方法及装置
US10198281B2 (en) Hybrid infrastructure provisioning framework tethering remote datacenters
CN108737468B (zh) 云平台服务集群、构建方法及装置
US10061619B2 (en) Thread pool management
US9058198B2 (en) System resource sharing in a multi-tenant platform-as-a-service environment in a cloud computing system
WO2019007353A1 (zh) 一种虚拟资源的分配方法及装置
JP2021518018A (ja) 関数チェックポイントを使用したサービスハブのための関数移植性
WO2017157156A1 (zh) 一种用户请求的处理方法和装置
US8832775B2 (en) Techniques for workload spawning
US11496414B2 (en) Interoperable cloud based media processing using dynamic network interface
AU2014226355A1 (en) Method and system for providing a roaming remote desktop
US11221866B2 (en) Accelerator loading method, system, and apparatus
US11740936B2 (en) Method and system for managing cloud resources
US9378039B2 (en) Virtual machine storage replication schemes
CN113196237A (zh) 计算系统中的容器迁移
US11210132B2 (en) Virtual machine migration in virtualization environment having different virtualization systems
WO2018191849A1 (zh) 云管理平台、虚拟机管理方法及其系统
US11416267B2 (en) Dynamic hardware accelerator selection and loading based on acceleration requirements
US11099829B2 (en) Method and apparatus for dynamically deploying or updating a serverless function in a cloud architecture
WO2019195177A1 (en) On-demand code execution with limited memory footprint
CN115604120A (zh) 一种多云集群资源共享方法、装置、设备及存储介质
Wei et al. A VDI system based on cloud stack and active directory
US11050794B2 (en) Generating security policies for end-user devices using group rankings and partial policy determinations

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019902781

Country of ref document: EP

Effective date: 20210726