WO2019109943A1 - Cloud platform management method and apparatus, electronic device and readable storage medium - Google Patents

Abstract

Provided are a cloud platform management method and apparatus, an electronic device and a readable storage medium, which are applied to the technical field of cloud computing. The method comprises: determining authorization information for a user, wherein the authorization information comprises: the number of nodes, a node configuration, a service life of a node and a component type; digitally signing the authorization information, and generating an authorization file according to obtained signature information and the authorization information; and when a cloud platform of the user is deployed, adding the authorization file to the cloud platform of the user, and deploying, according to the authorization information, a node in the cloud platform of the user to obtain the deployed cloud platform. Compared with the prior art, in the embodiments of the present application, by means of configuring one or more of the number of nodes, a node configuration and the type of a component in a node, a cloud platform is authorized in a combined manner, thus improving the flexibility of an authorization generation method.

Description

Cloud platform management method, device, electronic device and readable storage medium

This application claims the priority of the Chinese Patent Application entitled "A Cloud Platform Management Method, Apparatus, Electronic Device, and Readable Storage Medium" by the Chinese Patent Office on December 5, 2017, and the application number is 201711269676.0. The content is incorporated herein by reference.

Technical field

The present application relates to the field of cloud computing technologies, and in particular, to a cloud platform management method, apparatus, electronic device, and readable storage medium.

Background technique

Openstack is an open source cloud computing platform management project. It mainly cooperates with various components such as Nova, Neutron and cinder to complete the related operations of the cloud platform. OpenStack supports almost all types of cloud environments. The goal of OpenStack is to provide a cloud computing management platform that is simple to implement, scalable, rich, and standardized. OpenStack provides IaaS (Infrastructure as a Service) solutions through a variety of complementary services.

The cloud computing service provider can provide users with OpenStack-based cloud platform services, that is, deploy the OpenStack cloud platform for users and authorize users to use the OpenStack cloud platform. At present, the cloud computing service provider has a simple license management scheme for the user's OpenStack cloud platform, and usually only performs single-party license management for the OpenStack node. However, with the increasing number of Openstack cloud platform deployments and the increasing role and functionality of Openstack nodes, flexible and effective license management for users' Openstack cloud platforms is required. Especially when building an Openstack private cloud, a license management scheme is needed to control the number of clusters and the functionality of the cluster.

Summary of the invention

An object of the embodiments of the present application is to provide a cloud platform management method, apparatus, electronic device, and readable storage medium for performing flexible license management on a cloud platform. The specific technical solutions are as follows:

A first aspect of the embodiments of the present application provides a cloud platform management method, where the method includes: determining authorization permission information for the user, where the authorization permission information includes: a number of nodes, a node configuration, and a node. a period of use and a component type; digitally signing the license information, generating an authorization file according to the obtained signature information and the license information; and when the cloud platform of the user is deployed, the license file is Adding to the cloud platform of the user, deploying nodes in the cloud platform of the user according to the license information, and obtaining the deployed cloud platform.

With reference to the first aspect, in a possible implementation manner, the determining the license information for the user includes: determining the license information for the user according to the usage requirement of the user in the cloud platform.

With reference to the first aspect, in a possible implementation, before the deploying the node in the cloud platform of the user according to the license permission information, the method further includes: verifying, in the license file, Whether the signature information and the authorization permission information correspond; if the verification is passed, the signature information and the authorization permission information are stored in the cloud platform of the user.

With reference to the first aspect, in a possible implementation, the determining the license information for the user according to the usage requirement of the user in the cloud platform includes: determining whether the node is included according to the usage requirement Determining, in the request, determining whether the authorization for the number of nodes in the license information is on or off; determining whether to authorize the node configuration in the license information according to whether the requirement for the node configuration is included in the usage requirement For enabling or disabling; determining whether the license for the node usage period in the license information is turned on or off according to whether the usage requirement includes a requirement for a node usage period; whether the component type is included according to the usage requirement The requirement is to determine whether the license for the component type in the license information is turned on or off.

With reference to the first aspect, in a possible implementation manner, the deploying, by the user, the node in the cloud platform of the user according to the license information, including: when adding a node, acquiring the number of nodes to be added a node configuration, and determining whether the sum of the number of nodes in the cloud platform and the number of nodes in the node to be added is not greater than the number of nodes in the license information, and the cloud platform has Whether the node configuration of the adding node and the total configuration of the node configuration of the node to be added are not greater than the node configuration in the license information; when the determination result is yes, the node to be added is added.

With reference to the first aspect, in a possible implementation, after the deploying the cloud platform in the cloud platform of the user according to the license information, the method further includes: Receiving an operation instruction for expanding a node in the deployed cloud platform, adding node information to be extended to the authorization permission information, obtaining updated authorization permission information, and digitally signing the updated authorization permission information And generating an updated license file according to the obtained updated signature information and the updated license information; and installing the extended node on the deployed cloud platform according to the updated license file.

With reference to the first aspect, in a possible implementation, after the node in the cloud platform of the user is deployed according to the authorization permission information, and the deployed cloud platform is obtained, the method further includes: verifying The signature information and the expiration date in the license file in the deployed cloud platform; if the verification result is successful, periodically verify the license on the deployed cloud platform, and determine whether the deployed cloud platform is It runs within the scope of the license.

With reference to the first aspect, in a possible implementation manner, the performing the periodic authorization certificate verification on the deployed cloud platform, determining whether the deployed cloud platform is running within the scope of the license, includes: Verifying whether the number of nodes in the deployed cloud platform is not greater than the number of nodes in the license information; and verifying whether the configuration of the nodes in the deployed cloud platform is not greater than the nodes in the license information. Configuring whether the motherboard serial number of the node in the deployed cloud platform is in the license information; verifying whether the current time in the deployed cloud platform is within the validity period of the license information If the verification result is yes, it is determined that the deployed cloud platform runs within the scope of the license, otherwise, it is determined that the deployed cloud platform does not run within the scope of the license.

A second aspect of the embodiments of the present application provides a cloud platform management apparatus, including: an authorization permission information acquisition module, configured to determine authorization permission information for the user, where the authorization permission information includes: a number of nodes , a node configuration period, a node usage period, and a component type; a license file generating module, configured to digitally sign the license information, generate an authorization license file according to the obtained signature information and the license information; and a cloud platform deployment module, When the cloud platform of the user is deployed, the license file is added to the cloud platform of the user, and the node in the cloud platform of the user is deployed according to the license information, and deployed. After the cloud platform.

With reference to the second aspect, in a possible implementation, the authorization determining module is specifically configured to determine authorization information for the user according to a user's usage requirement for the cloud platform node.

With reference to the second aspect, in a possible implementation, the cloud platform management apparatus of the embodiment of the present application further includes: a signature information verification module, configured to verify the signature information and the authorization in the license file Whether the license information corresponds to the information storage module is configured to store the signature information and the license permission information in the cloud platform of the user if the signature information verification module passes the verification.

With reference to the second aspect, in a possible implementation manner, the license information obtaining module is specifically configured to determine, according to whether the requirement for the number of nodes is included in the usage requirement, determine a node in the license information. The number of licenses is turned on or off; determining whether the license configured for the node in the license information is turned on or off according to whether the requirement for the node is included in the usage requirement; whether the pair is included according to the usage requirement Determining the license period of the node in the license information to be turned on or off; determining whether the component type is in the license information according to whether the requirement for the component type is included in the use requirement The license is either on or off.

With reference to the second aspect, in a possible implementation, the cloud platform deployment module is specifically configured to: when adding a node, obtain the number of nodes and node configurations of the node to be added, and determine that the cloud platform has been added. Whether the sum of the number of nodes of the node and the number of nodes of the node to be added is not greater than the number of nodes in the license information, and the node configuration of the node in the cloud platform and the node to be added Whether the total configuration of the node configuration is not greater than the node configuration in the license information; when the determination result is yes, the node to be added is added.

With reference to the second aspect, in a possible implementation manner, the cloud platform management apparatus of the embodiment of the present application further includes: an authorization license information update module, configured to receive, if received, a node in the deployed cloud platform The extended operation instruction adds the node information to be extended to the license information to obtain updated license information; and the license file update module is configured to digitally sign the updated license information according to the obtained update The signature information and the updated license information generate an updated license file; the extended node installation module is configured to perform an installation of the extended node on the deployed cloud platform according to the updated license file.

With reference to the second aspect, in a possible implementation manner, the cloud platform management apparatus of the embodiment of the present application further includes: a first verification module, configured to verify signature information in the license file in the deployed cloud platform And the expiration date; the second verification module is configured to perform periodic authorization verification on the deployed cloud platform when the first verification module is successfully verified, and determine whether the deployed cloud platform runs on the license. In the range.

With reference to the second aspect, in a possible implementation, the second verification module is configured to verify whether the number of nodes in the deployed cloud platform is not greater than the number of nodes in the license information. Verifying whether the configuration of the node in the deployed cloud platform is not greater than the configuration of the node in the license information; verifying whether the serial number of the motherboard of the node in the deployed cloud platform is in the license information; Whether the current time in the deployed cloud platform is within the validity period of the license information; if the verification result is yes, it is determined that the deployed cloud platform runs within the scope of the license, otherwise Determining that the deployed cloud platform is not running within the scope of the license.

A third aspect of the embodiments of the present application provides an electronic device, including: a processor and a machine readable storage medium, the machine readable storage medium storing machine executable instructions executable by the processor, The steps of the cloud platform management method described in any of the above are implemented when the processor executes the machine executable instructions.

A fourth aspect of the embodiments of the present application provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by a processor, implementing the cloud of any of the foregoing The steps of the platform management method.

A fifth aspect of the embodiments of the present application provides a computer program product comprising instructions, when executed on a computer, causing a computer to perform the steps of any of the cloud platform management methods described above.

The cloud platform management method, the device, the electronic device, and the readable storage medium provided by the embodiment of the present application determine the license information for the user, where the license information includes: the number of nodes, the node configuration, the node usage period, and the component type; The license information is digitally signed, and the license file is generated according to the obtained signature information and the license information; when the user's cloud platform is deployed, the license file is added to the user's cloud platform, and the license information is deployed according to the license information. The nodes in the user's cloud platform get the deployed cloud platform. In the embodiment of the present application, the number of nodes in the cloud platform, the node configuration, the component type in the node, and the like may be combined and authorized to perform flexible authorization and license management on the cloud platform; and the license information is digitally signed to ensure the license information. Not easy to be tampered with. Of course, implementing any of the products or methods of the present application does not necessarily require that all of the advantages described above be achieved at the same time.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present application, and other drawings can be obtained according to the drawings without any creative work for those skilled in the art.

FIG. 1 is a flowchart of a cloud platform management method according to an embodiment of the present application;

2 is another flowchart of a cloud platform management method according to an embodiment of the present application;

3 is a flowchart of a method for deploying a cloud platform node according to an embodiment of the present application;

FIG. 4 is still another flowchart of a cloud platform management method according to an embodiment of the present application;

FIG. 5 is a structural diagram of a cloud platform management apparatus according to an embodiment of the present application;

FIG. 6 is another structural diagram of a cloud platform management apparatus according to an embodiment of the present application;

FIG. 7 is still another structural diagram of a cloud platform management apparatus according to an embodiment of the present application;

FIG. 8 is a structural diagram of an electronic device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

In the existing cloud platform management method, the deployment tool and the cloud platform of the cloud platform are separated, and the deployment tool may be a server or a virtual machine independent of the cloud platform, and an independent deployment tool acquires the number of nodes in the cloud platform. Information such as node configuration and component type requires authentication and other operations, which is complicated to implement and causes the deployment system to be too heavy. Moreover, the deployment tool can only obtain a single piece of information, such as the number of nodes. Therefore, the cloud platform license management function is single. In addition, the deployment tool can only deploy the cloud platform. After the cloud platform is deployed, the cloud platform cannot be verified. Legitimacy. In order to solve the problem, the embodiment of the present application provides a cloud platform management method, device, electronic device, and readable storage medium, which can perform copyright control, scale control, and use period control on a cloud platform, according to a user's use of the cloud platform. It is expected that a variety of licensing methods may be provided, and the licensing method may be a single one or a combination of multiple authorization methods. At the same time, the corresponding license information is generated, and the cloud platform is deployed according to the license information, and the basic functions and extended functions of the cloud platform are provided. Moreover, the cloud platform deployment tool of the embodiment of the present application is integrated in the cloud platform, and can communicate with components in the cloud platform, so that the component information can be conveniently obtained, because components in the cloud platform need to be activated through the license, and The deployment tool can be combined with the license to control the components, so that the cloud platform can be deployed more conveniently and efficiently. After the cloud platform is deployed, the legality of the cloud platform can be verified.

The execution body of the cloud platform management method provided by the embodiment of the present application may be a server in the cloud platform.

The cloud platform management method provided by the embodiment of the present application is first introduced in detail.

Referring to FIG. 1, FIG. 1 is a flowchart of a cloud platform management method according to an embodiment of the present application, including the following steps:

S101. Determine license information for the user, where the license information includes: a number of nodes, a node configuration, a node usage period, and a component type.

Exemplarily, in this step, the license information for the user is determined according to the user's use requirement of the node in the cloud platform.

The cloud platform management in the embodiment of the present application includes three phases: a license file preparation phase, a node deployment phase, and a cloud platform use phase. This step belongs to the license file preparation phase. The nodes in the cloud platform refer to servers. According to different roles of the nodes in the cloud platform, the nodes can be divided into: computing nodes, storage nodes, network nodes, and the like. The number of nodes is also the number of nodes. The node configuration may include: a number of CPUs (Central Processing Units), a memory capacity, and the like, which are not limited in this embodiment of the present application. For different users, the usage requirements of the cloud platform may be different. For example, the usage requirement of the cloud platform by the A user is mainly a storage function, the usage requirement of the cloud user by the B user is a computing function, and the use of the cloud platform by the C user is used. The requirements are storage functions and calculation functions. Therefore, in the embodiment of the present application, the license information for different users may be different, wherein the license information may be used to indicate resources that the user is authorized to use, and related information of the resources, exemplary, license The contents carried in the information can be seen in Table 1.

Table I

variable	Types of	name
License_name	String	Information name
Sale_type	Dict	Licensing method
Sale_info	Dict	Licensed content
Date	String	Validity period

The license_name is the name of the license, for example, the game; the sale_type is the license support method, including: the number of nodes (for example, the number of compute nodes, the number of network nodes, the number of storage nodes), The configuration of the node (for example, the number of CPUs of the node, the memory capacity, and the storage type supported by the cloud platform, and the like), and the types of components authorized in the nodes (Neutron, Nova, Cinder, etc.), etc. Provides basic Openstack functionality (computing, networking, storage, and authentication) components as well as extended Openstack features. The sale_info is the opening or closing status of the corresponding license mode, that is, whether to authorize the number of nodes, whether to configure the license for the node, etc.; date is the expiration date that each node and each component in the cloud platform can use.

The license information can be input by the relevant personnel. For example, the server that executes the main body is the cloud platform. For example, the background personnel can input the license information locally at the server, or the user can input the license information at the user terminal. The user terminal sends it to the server. The license information may also be determined according to the user's usage requirements of the nodes in the cloud platform. The user requirements may include functions (such as storage functions and computing functions) that the user needs to provide the cloud platform, and the amount of resources that need to be occupied (such as the need to occupy 3) Computing nodes, 1 storage node), etc. It can also include technical solutions that users need to implement with the cloud platform. The user can fill in the user requirements list and send it to the server. The server analyzes the user's needs and obtains the license information. For example, the user can fill in the demand list when registering.

Exemplarily, the user needs to implement some intelligent analysis algorithm by means of the cloud platform. After the background personnel analyzes the algorithm complexity of the intelligent analysis algorithm, it is determined that the implementation of the intelligent analysis algorithm requires five computing nodes and two storage nodes, and then it is determined. The obtained license information may indicate that the user is authorized to use 5 compute nodes and 2 storage nodes in the cloud platform.

S102. Digitally sign the license information, and generate an authorization file according to the obtained signature information and the license information.

In the embodiment of the present application, after obtaining the license information, the license information may be digitally signed to obtain signature information corresponding to the license information. Digital signature is an encryption method that guarantees the integrity of information transmission, enables the receiver to authenticate the sender, and prevents the repudiation in the transaction. The public key and the private key in the digital signature process may be pre-set asymmetric key pairs. In the embodiment of the present application, the message digest (Message-Digest) of the license information may be extracted by using a preset hash algorithm (such as the secure hash algorithm SHA), and the information digest is encrypted by using the private key to obtain the license information. The signature information is combined with the obtained signature information and the license information to obtain a license file. After receiving the license file, the receiver can decrypt the signature information in the license file by using the public key, and extract the information digest of the license information according to the same hash algorithm, and the decrypted information and the extracted information. For comparison, if the decrypted information is the same as the extracted information digest, it can be determined that the license information has not been tampered with; if the decrypted information is different from the extracted digest, it can be determined that the license information has been tampered with.

S103, when the user's cloud platform is deployed, the license file is added to the user's cloud platform, and the node in the user's cloud platform is deployed according to the license information, and the deployed cloud platform is obtained.

In this embodiment of the present application, the step belongs to the node deployment phase, and after the license file is generated, the cloud platform can be deployed. First, the license file is added to the user's cloud platform. Specifically, the license file is added to the database of the cloud platform. The license file includes: signature information and license information, so the cloud can be deployed according to the license information. The nodes in the platform. For example, the authorization for the number of nodes in the license information is: deploying 3 storage nodes and 2 compute nodes. The authorization for configuring the node in the license information is: the number of deployed CPUs is 10, then, in the right When the cloud platform is deployed, the cloud platform can be deployed according to the license information, and the deployed cloud platform can be obtained.

The cloud platform management method provided by the embodiment of the present application determines the license information for the user, where the license information includes: the number of nodes, the node configuration, the node usage period, and the component type; digitally signing the license information, according to the The signature information and the license information generate a license file; when the user's cloud platform is deployed, the license file is added to the user's cloud platform, and the nodes in the user's cloud platform are deployed according to the license information, and deployed. After the cloud platform. The embodiment of the present application can perform combined authorization on the number of nodes in the cloud platform, the node configuration, and the component types in the node, thereby performing flexible authorization and license management on the cloud platform, and digitally signing the license information to ensure the license information. Not easy to be tampered with.

Referring to FIG. 2, FIG. 2 is another flowchart of a cloud platform management method according to an embodiment of the present application, including the following steps:

S201. Determine, according to the usage requirement of the user in the cloud platform, the license information for the user, where the license information includes: a number of nodes, a node configuration, a node usage period, and a component type.

S202. Digitally sign the license information, and generate an authorization file according to the obtained signature information and the license information.

S203. When deploying the cloud platform of the user, adding the license file to the cloud platform of the user, verifying whether the signature information and the license information in the license file correspond to each other; if the verification is passed, the signature information and the license information are obtained. Stored in the user's cloud platform.

The digital signature technique encrypts the initial information with the sender's private key and transmits the obtained encrypted information together with the initial information to the recipient. The receiver can decrypt the encrypted initial information only by using the sender's public key, decrypt the encrypted initial information through the public key, and compare the obtained decrypted information with the initial information. If they are the same, the received initial information is received. It is complete and has not been modified during transmission. Otherwise, the initial information has been modified, so the digital signature can verify the integrity of the information. Digital signature is the process of encryption, and digital signature verification is the process of decryption.

In the embodiment of the present application, after the signature information in the license file is obtained by encrypting the license information by using the private key, after the license file is added to the cloud platform of the user, the license file may be obtained by using the public key. The signature information in the decryption is decrypted, and the obtained decryption information is compared with the license information. If the information is the same, it indicates that the license information has not been tampered with. Therefore, the integrity of the license information on the cloud platform is ensured by means of public and private keys, so that the license information is not easily falsified. Then, after the verification is passed, the signature information and the license information can be stored in the user's cloud platform.

S204. Deploy a node in the user's cloud platform according to the license information, and obtain the deployed cloud platform.

Since S201 and S202 are the same as S101 and S102 in the embodiment of FIG. 1, respectively, the steps in S204 and S103 are the same, and all implementations of S101, S102, and S103 are applicable to FIG. 2, and all of the same or similar beneficial effects can be achieved. , will not repeat them here.

The cloud platform management method provided by the embodiment of the present application determines the license information for the user according to the user's use requirement of the node in the cloud platform, where the license information includes: the number of nodes, the node configuration, the node use period, and the component type. Digitally signing the license information, and generating a license file according to the obtained signature information and license information; when deploying the user's cloud platform, adding the license file to the user's cloud platform, verifying the license file Whether the signature information and the license information correspond to each other; if the verification is passed, the signature information and the license information are stored in the user's cloud platform; according to the license information, the nodes in the user's cloud platform are deployed to obtain the deployed cloud platform. The embodiment of the present application can perform combined authorization for the number of nodes in the cloud platform, the node configuration, the component type in the node, and the like, thereby performing flexible authorization and license management on the cloud platform. By authorizing the license information digitally, the license information is not easily tampering.

The S203 and S204 in the foregoing embodiment of FIG. 2 are the node deployment stage. The flowchart of the node deployment method in the cloud platform in the embodiment of the present application can be seen in FIG. 3, including the following steps:

S301, adding a license file in the cloud platform.

In the embodiment of the present application, the license file may be generated according to the user's use requirements of the cloud platform. After the license file is obtained, the license file may be provided to the user, so that the user can use the license file according to the license file. The platform is deployed, and of course, the administrator can deploy the cloud platform. When deploying a cloud platform, you first need to add the license file to the cloud platform.

S302, verify signature information and expiration date.

It can be seen from the embodiment of FIG. 1 and the embodiment of FIG. 2 that the license file includes: signature information and license information. After obtaining the license file, the signature information can be verified, that is, the integrity of the license information is verified, and the license information is determined. The method of verifying the signature information may be: verifying whether the signature information and the license information in the license file correspond to each other. For details, refer to S203 in the embodiment of FIG. 2, and details are not described herein again. In addition, the license information also includes an expiration date, which is the expiration date of the cloud platform. When verifying the signature information, the expiration date in the license information may also be verified. If the current time is within the valid period, the verification is successful. The license information is usable; if the current time is not within the validity period, it indicates that the verification fails, and the license information is not available, and the process proceeds to S307, and the process ends.

S303. Store signature information and license information.

After the verification succeeds in S302, the signature information and the license information are stored in the cloud platform, that is, the database of the cloud platform, so that the cloud platform can be deployed according to the license information.

S304. Deploy the node according to the license information.

In the embodiment of the present application, the deployment of the nodes in the cloud platform will be described in detail below, and details are not described herein again.

S305, verify signature information and expiration date.

Specifically, after the nodes in the cloud platform are deployed, the signature information and the expiration date of each node may be verified. The verification method is the same as that of S302, and details are not described herein. Through the verification of this step, it can be guaranteed that the deployed cloud platform can be used.

S306, the cloud platform is deployed successfully.

In the cloud platform management method provided by the embodiment of the present application, when the node in the cloud platform is deployed, the license file is added to the cloud platform, and the signature information and the expiration date are verified. After the verification succeeds, the signature information is stored and The license information is used to deploy the node according to the license information. After the node is deployed, the signature information and the validity period of each node can be verified. After the verification succeeds, the cloud platform is successfully deployed. The embodiment of the present application verifies the signature information of the digitally signed license information, and ensures the integrity of the license information on the cloud platform, so that the license information is not easily falsified.

Referring to FIG. 4, FIG. 4 is still another flowchart of a cloud platform management method according to an embodiment of the present application, including the following steps:

S401. Determine, according to a user usage requirement of a node in the cloud platform, the license information for the user, where the license information includes: a number of nodes, a node configuration, a node usage period, and a component type.

S402. Digitally sign the license information, and generate an authorization file according to the obtained signature information and the license information.

S403. When the user's cloud platform is deployed, the license file is added to the user's cloud platform, and the nodes in the user's cloud platform are deployed according to the license information, and the deployed cloud platform is obtained.

S404. If an operation instruction for expanding a node in the deployed cloud platform is received, adding the node information to be extended to the license information to obtain updated license information.

In the embodiment of the present application, since the license information can be stored in the cloud platform, after the cloud platform is deployed, the license information can also be viewed and updated. If the user needs to extend the deployed cloud platform, the user sends an operation instruction for expanding the node in the deployed cloud platform, and after receiving the operation instruction, the cloud platform adds the node to be extended to the authorization information. Information, get updated license information. Certainly, the embodiment of the present application may further extend components in the node, and may also delete nodes in the cloud platform, delete components in the node, and the like, and expand the node as an example for description.

S405. Digitally sign the updated license information, and generate an updated license file according to the obtained updated signature information and the updated license information.

In this step, after the updated license information is obtained, the updated license information is digitally signed, and an updated license file is generated according to the obtained updated signature information and the updated license information. The method in this step is the same as the method in the embodiment S102 of FIG. 1, and details are not described herein again. This step differs from S102 in that the license information in this step is updated license information as compared with the license information in S102.

S406. Perform an installation of the extended node on the deployed cloud platform according to the updated license file.

In the embodiment of the present application, after the updated license file is obtained, the deployed node may be installed on the deployed cloud platform according to the updated license file. For example, if two storage nodes need to be added to the license information in the updated license file, this step adds two storage nodes based on the deployed cloud platform obtained in S403.

Since S401, S402, and S403 are the same as S101, S102, and S103 in the embodiment of FIG. 1, all implementations of S101, S102, and S103 are applicable to FIG. 4, and all of the same or similar beneficial effects can be achieved. Let me repeat.

The cloud platform management method provided by the embodiment of the present application, after obtaining the deployed cloud platform, if receiving an operation instruction for expanding a node in the deployed cloud platform, adding the information to be extended to the license information, Updated license information; digitally sign the updated license information, generate an updated license file according to the obtained updated signature information and updated license information; and perform the deployed cloud platform according to the updated license file Expansion node installation. The embodiment of the present application can also update the license information according to the user's need for the cloud platform extension, and then update the signature information and the license file corresponding to the license information, thereby flexibly expanding the cloud platform.

In an implementation manner of the application, determining the license information for the user according to the usage requirement of the node in the cloud platform by the user may include:

According to whether the requirement of the number of nodes is included in the usage requirement, it is determined whether the license for the number of nodes in the license information is turned on or off.

Determine whether the license configured for the node in the license information is turned on or off according to whether the requirement for the node configuration is included in the usage requirement.

According to whether the requirement of using the node includes the requirement of the term of use of the node, it is determined whether the license for the use term of the node in the license information is turned on or off.

Determine whether the license type for the component type in the license information is turned on or off according to whether the requirement for the component type is included in the usage requirement.

In the embodiment of the present application, the number of nodes, the node configuration, the node usage period, the component type, and the like may be combined and authorized, that is, the number of nodes, the node configuration, the node usage period, the component type, and the like may be applied to the application. Authorize one or more of the multiple items. When one of them is authorized, the license for the item can be opened. Otherwise, the license for the item is closed. Optionally, the boil type variable can be used to indicate the on or off status of the license. For example, if the number of nodes is authorized, the value of the Boolean variable corresponding to the number of nodes can be set to TRUE. Otherwise, You can set the value of a Boolean variable corresponding to the number of nodes to FALSE.

In the cloud platform management method of the embodiment of the present application, the number of nodes, the node configuration, the node usage period, the component type, and the like may be set to be turned on or off, and multiple authorization modes are obtained, and the cloud is obtained through multiple authorization modes. The platform is managed so that the cloud platform can be flexibly licensed and managed.

In an implementation manner of the present application, in the embodiment of FIG. 1 , the embodiment of FIG. 2 , and the embodiment of FIG. 4 , the nodes in the cloud platform of the user are deployed according to the license information, including:

When adding a node, the number of nodes to be added and the node configuration are obtained, and it is determined whether the sum of the number of nodes that have added nodes in the cloud platform and the number of nodes to be added is not greater than the number of nodes in the license information. And the total configuration of the node configuration of the added node in the cloud platform and the node configuration of the node to be added is not greater than the node configuration in the license information; when the judgment result is yes, the node to be added is added.

In the embodiment of the present application, the cloud platform may be deployed according to the license information. When the nodes in the cloud platform are deployed, the cluster information (information of all nodes) in the cloud platform needs to be checked according to the license information. . For example, when adding a node, you need to obtain information about the node to be added (number of nodes, node configuration, component type in the node, etc.), and the number of nodes to be added is equal to the number of nodes in the cloud platform. Adding, determining whether the total number of nodes in the obtained cloud platform is not greater than the number of nodes in the license information; adding the node configuration of the node to be added and the node configuration of the added node in the cloud platform, and determining the obtained cloud platform Whether the total node configuration in is not greater than the node configuration in the license information. If the above judgment result is yes, it is determined that the added node is successfully deployed. Otherwise, it is determined that the added node fails to be deployed. The node configuration includes: the number of CPUs and the size of the memory.

For example, when the node configuration is authorized, and the node configuration is authorized according to the number of CPUs, the signature information and the expiration date are first verified when the node is added. For the verification method, refer to S203 in the embodiment of FIG. This will not be repeated here. After the verification succeeds, the number of CPUs in the license information is read, and then the number of CPUs of the node to be added is obtained, and finally the number of CPUs is added to the number of CPUs in the cloud platform cluster, and the license is authorized. The number of CPUs in the information is compared. If the number of CPUs after the addition is less than or equal to the number of CPUs in the license information, that is, if the node to be added can be successfully deployed, the node to be added is added.

It can be seen that the cloud platform can be deployed through the license information, which can prevent the user from deploying the cloud platform beyond the scope of the license information license.

In an implementation manner of the application, after the cloud platform is deployed, that is, after the node in the cloud platform of the user is deployed according to the license information, and after the deployed cloud platform is obtained, the method further includes:

Verify the signature information and expiration date in the license file in the deployed cloud platform.

In the embodiment of the present application, for the deployed cloud platform, before the verification of the signature information and the expiration date, the service in the cloud platform may be authenticated. Specifically, the keystone is a component in the cloud platform. For identity authentication) Create a Token (temporary token in authentication). When the token is created, the signature information and the expiration date are read from the nova database, the signature information is verified, and the expiration date is valid. When the verification succeeds, a token is created for the keystone. After that, the signature information and the expiration date in the license file in the deployed cloud platform are verified. Specifically, after the signature information is decrypted, whether the decrypted information and the license information are verified are the same, and the license information is prevented from being tampered with. In addition, you can verify the expiration date in the license information to ensure that the current time is within the validity period of the cloud platform. If the verification result is successful, indicating that the deployed cloud platform can be used normally, then the deployed cloud platform is periodically authenticated and verified to determine whether the deployed cloud platform is running within the scope of the license.

In the process of using the cloud platform, in order to prevent the number of nodes and node configurations in the cloud platform from being tampered with, the distributed cloud platform can be periodically authenticated and authenticated to determine whether the deployed cloud platform is running under the license. Within the scope. Optionally, it is verified whether the number of nodes in the deployed cloud platform is not greater than the number of nodes in the license information; whether the configuration of the node in the deployed cloud platform is not greater than the configuration of the node in the license information; Whether the motherboard serial number of the node in the subsequent cloud platform is in the license information; verify whether the current time in the deployed cloud platform is within the validity period of the license information. If the above verification result is yes, it is determined that the deployed cloud platform runs within the scope of the license. Otherwise, it is determined that the deployed cloud platform does not run within the scope of the license.

For example, nova-compute (a service for computing in the nova component) collects the CPU and memory of the nodes in the cloud platform, and nova-conductor (the service for database interaction in the nova component) is responsible for integrating the CPU and memory of the entire cloud platform. Then, the license information in the cloud platform database is read, and after the signature information is verified, the node configuration is verified. The nova-conductor can also obtain the number of computing, network, and storage nodes of the cloud platform, and then read the license information in the cloud platform database, and verify the signature, and then verify the number of nodes. In the embodiment of the present application, the serial number of the physical node of the Openstack cloud platform may also be verified according to the license information. For example, for Openstack compute and storage converged nodes, the motherboard serial number of the node is obtained by nova-compute (the service used for computing in the nova component), and then obtained by nova-conductor (the service for database interaction in the nova component). And verify the license information; for a separate storage node, the storage daemon obtains the serial number of the node of the node, and then completes the verification; for a separate network node, the network daemon (such as neutron-openvswitch-agent) completes the verification of the serial number of the motherboard .

Corresponding to the foregoing method embodiments, the embodiment of the present application further provides a cloud platform management apparatus. Referring to FIG. 5, FIG. 5 is a structural diagram of a cloud platform management apparatus according to an embodiment of the present application, including:

The license information obtaining module 501 is configured to determine the license information for the user, where the license information includes: the number of nodes, the node configuration, the node usage period, and the component type; specifically, according to the user's use requirements for the nodes in the cloud platform. , determining license information for the user;

The license file generating module 502 is configured to digitally sign the license information, and generate an authorization file according to the obtained signature information and the license information;

The cloud platform deployment module 503 is configured to add the license file to the user's cloud platform when deploying the user's cloud platform, deploy the node in the user's cloud platform according to the license information, and obtain the deployed cloud platform. .

The cloud platform management device provided by the embodiment of the present application determines the license information for the user according to the user's use requirement of the node in the cloud platform, where the license information includes: the number of nodes, the node configuration, the node usage period, and the component type. Digitally signing the license information, and generating a license file according to the obtained signature information and the license information; when deploying the user's cloud platform, adding the license file to the user's cloud platform, according to the license information, Deploy the nodes in the user's cloud platform and get the deployed cloud platform. In the embodiment of the present application, the number of nodes in the cloud platform, the node configuration, the component type in the node, and the like may be combined and authorized to perform flexible authorization and license management on the cloud platform; and the license information is digitally signed to ensure the license information. Not easy to be tampered with.

It should be noted that, the device in the embodiment of the present application is a device that applies the foregoing cloud platform management method, and all embodiments of the cloud platform management method are applicable to the device, and all of the same or similar beneficial effects can be achieved.

Referring to FIG. 6, FIG. 6 is another structural diagram of a cloud platform management apparatus according to an embodiment of the present application, including:

The license information obtaining module 601 is configured to determine the license information for the user, where the license information includes: the number of nodes, the node configuration, the node usage period, and the component type; specifically, according to the user's use requirements for the nodes in the cloud platform. , determining license information for the user;

The license file generating module 602 is configured to digitally sign the license information, and generate an authorization file according to the obtained signature information and the license information;

The signature information verification module 603 is configured to verify whether the signature information and the license permission information in the license file correspond to each other;

The information storage module 604 is configured to: if the signature information verification module passes the verification, store the signature information and the license information in the cloud platform of the user;

The cloud platform deployment module 605 is configured to add the license file to the user's cloud platform when deploying the user's cloud platform, deploy the node in the user's cloud platform according to the license information, and obtain the deployed cloud platform. .

The cloud platform management device provided by the embodiment of the present application determines the license information for the user according to the user's use requirement of the node in the cloud platform, where the license information includes: the number of nodes, the node configuration, the node usage period, and the component type. Digitally signing the license information, and generating a license file according to the obtained signature information and license information; when deploying the user's cloud platform, adding the license file to the user's cloud platform, verifying the license file Whether the signature information and the license information correspond to each other; if the verification is passed, the signature information and the license information are stored in the user's cloud platform; according to the license information, the nodes in the user's cloud platform are deployed to obtain the deployed cloud platform. The embodiment of the present application can perform combined authorization for the number of nodes in the cloud platform, the node configuration, the component type in the node, and the like, thereby performing flexible authorization and license management on the cloud platform. By authorizing the license information digitally, the license information is not easily tampering.

Referring to FIG. 7, FIG. 7 is still another structural diagram of a cloud platform management apparatus according to an embodiment of the present application, including:

The license information obtaining module 701 is configured to determine the license information for the user, where the license information includes: a number of nodes, a node configuration, a node usage period, and a component type;

The license file generating module 702 is configured to digitally sign the license information, and generate an authorization license file according to the obtained signature information and the license information;

The cloud platform deployment module 703 is configured to add the license file to the user's cloud platform when deploying the user's cloud platform, deploy the node in the user's cloud platform according to the license information, and obtain the deployed cloud platform. ;

The license information update module 704 is configured to: if the operation instruction for expanding the node in the deployed cloud platform is received, add the node information to be extended to the license information to obtain the updated license information;

The license file update module 705 is configured to digitally sign the updated license information, and generate an updated license file according to the obtained updated signature information and the updated license information;

The extended node installation module 706 is configured to perform an installation of the extended node on the deployed cloud platform according to the updated license file.

The cloud platform management apparatus provided by the embodiment of the present application, after receiving the deployed cloud platform, adds an operation instruction for expanding a node in the deployed cloud platform, and adds information to be extended to the license information, and obtains Updated license information; digitally sign the updated license information, generate an updated license file according to the obtained updated signature information and updated license information; and perform the deployed cloud platform according to the updated license file Expansion node installation. The embodiment of the present application can also update the license information according to the user's use requirements for the cloud platform extension, thereby flexibly expanding the cloud platform.

In an implementation manner of the application, the license information obtaining module is specifically configured to determine the license information for the user according to the user's use requirements of the nodes in the cloud platform.

In an implementation manner of the present application, the license information obtaining module is specifically configured to determine whether the license for the number of nodes in the license information is turned on or off according to whether the requirement of the number of nodes is included in the use requirement; Whether the requirements of the node configuration are included in the requirement, determining whether the license for configuring the node in the license information is turned on or off; determining whether the license period is authorized in the license information according to whether the requirement of using the node includes the use term of the node. The license is turned on or off; depending on whether the requirements for the component type are included in the usage requirements, it is determined whether the license type for the component type in the license information is turned on or off.

In an implementation manner of the application, the cloud platform deployment module is specifically configured to: when adding a node, obtain the number of nodes and node configurations of the node to be added, and determine the number of nodes that have added nodes in the cloud platform and nodes to be added. Whether the sum of the number of nodes is not greater than the number of nodes in the license information, and whether the node configuration of the added node of the cloud platform and the total configuration of the node configuration of the node to be added are not greater than the node configuration in the license information; When the judgment result is yes, add the node to be added.

In an implementation manner of the application, the cloud platform management apparatus further includes:

The first verification module is configured to verify signature information and an expiration date in the license file in the deployed cloud platform;

The second verification module is configured to perform periodic authorization verification on the deployed cloud platform when the first verification module is successfully verified, and determine whether the deployed cloud platform runs within the scope of the license.

In an implementation manner of the application, the second verification module is specifically configured to verify whether the number of nodes in the deployed cloud platform is not greater than the number of nodes in the license information; and verify the configuration of the nodes in the deployed cloud platform. Whether it is not greater than the configuration of the node in the license information; verify whether the motherboard serial number of the node in the deployed cloud platform is in the license information; verify whether the current time in the deployed cloud platform is within the validity period of the license information. If the above verification result is yes, it is determined that the deployed cloud platform runs within the scope of the license. Otherwise, it is determined that the deployed cloud platform does not run within the scope of the license.

The embodiment of the present application further provides an electronic device. Referring to FIG. 8, FIG. 8 is a structural diagram of an electronic device according to an embodiment of the present application, including: a processor 801 and a machine readable storage medium 802. The machine readable storage medium 802 stores There are machine executable instructions executable by the processor 801 that, when executed by the processor 801, implement the steps of any of the cloud platform management methods described above.

The processor 801 may be a general-purpose processor, including: a CPU, an NP (Network Processor), or the like; or a DSP (Digital Signal Processing) or an ASIC (Application Specific Integrated Circuit). , FPGA (Field-Programmable Gate Array) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

The machine-readable storage medium 802 may include a RAM (Random Access Memory), and may also include a non-volatile memory, such as at least one disk storage. Alternatively, the machine readable storage medium 802 can also be at least one storage device located remotely from the processor 801.

It can be seen from the above that in the electronic device of the embodiment of the present application, the processor executes the machine executable instructions stored on the machine readable storage medium, so that the license for the user can be determined according to the user's use requirements of the nodes in the cloud platform. Information, wherein the license information includes: a number of nodes, a node configuration, a node usage period, and a component type; digitally signing the license information, generating an authorization license file according to the obtained signature information and the license information; When the platform is deployed, the license file is added to the user's cloud platform, and the nodes in the user's cloud platform are deployed according to the license information, and the deployed cloud platform is obtained. In the embodiment of the present application, the number of nodes in the cloud platform, the node configuration, the component type in the node, and the like may be combined and authorized to perform flexible authorization and license management on the cloud platform; and the license information is digitally signed to ensure the license information. Not easy to be tampered with.

The embodiment of the present application further provides a computer readable storage medium. The computer readable storage medium stores a computer program. When the computer program is executed by the processor, the steps of the cloud platform management method in the foregoing embodiment are implemented.

It can be seen from the above that when the computer program stored in the computer readable storage medium of the embodiment of the present application is executed by the processor, the license information for the user is determined according to the user's use requirement of the node in the cloud platform, wherein the license information includes : number of nodes, node configuration, node lifetime, and component type; digitally sign the license information, generate a license file based on the obtained signature information and license information; and license the user when deploying the cloud platform The file is added to the user's cloud platform, and the nodes in the user's cloud platform are deployed according to the license information, and the deployed cloud platform is obtained. In the embodiment of the present application, the number of nodes in the cloud platform, the node configuration, the component type in the node, and the like may be combined and authorized to perform flexible authorization and license management on the cloud platform; and the license information is digitally signed to ensure the license information. Not easy to be tampered with.

The embodiment of the present application further provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform the steps of any of the above cloud platform management methods.

The computer program product of the embodiment of the present application, when it is running on a computer, determines the license information for the user according to the user's use requirement of the node in the cloud platform, wherein the license information includes: the number of nodes, the node configuration, The term of use of the node and the type of the component; digitally sign the license information, generate a license file based on the obtained signature information and the license information; add the license file to the user's cloud platform when deploying the user's cloud platform According to the license information, deploy the nodes in the user's cloud platform to obtain the deployed cloud platform. In the embodiment of the present application, the number of nodes in the cloud platform, the node configuration, the component type in the node, and the like may be combined and authorized to perform flexible authorization and license management on the cloud platform; and the license information is digitally signed to ensure the license information. Not easy to be tampered with.

It should be noted that, in this context, relational terms such as first and second are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply such entities or operations. There is any such actual relationship or order between them. Furthermore, the term "comprises" or "comprises" or "comprises" or any other variations thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a plurality of elements includes not only those elements but also Other elements, or elements that are inherent to such a process, method, item, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

The various embodiments in the present specification are described in a related manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the cloud platform management device, the electronic device, the readable storage medium embodiment, and the computer program product, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant part of the method embodiment is referred to can.

The above description is only the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application are included in the scope of the present application.

Industrial applicability

Based on the foregoing technical solutions provided by the embodiments of the present application, the number of nodes in the cloud platform, the node configuration, the component types in the nodes, and the like may be combined and authorized, thereby performing flexible authorization and license management on the cloud platform; Digital signatures ensure that license information is not easily tampered with.

Claims (19)

1. A cloud platform management method, the method comprising:

   Determining license information for the user, wherein the license information includes: a number of nodes, a node configuration, a node usage period, and a component type;

   Digitally signing the license information, and generating an authorization license file according to the obtained signature information and the license information;

   When the cloud platform of the user is deployed, the license file is added to the cloud platform of the user, and the node in the cloud platform of the user is deployed according to the license information, and the deployed node is obtained. cloud platform.
2. The method of claim 1, wherein the determining the license information for the user comprises:

   The license information for the user is determined according to the user's usage requirements for the nodes in the cloud platform.
3. The cloud platform management method according to claim 1 or 2, wherein before the deploying the nodes in the cloud platform of the user according to the license permission information, the method further includes:

   Verifying whether the signature information and the license permission information in the license file correspond to each other;

   If the verification is passed, the signature information and the authorization permission information are stored in the cloud platform of the user.
4. The cloud platform management method according to claim 2, wherein the determining the license information for the user according to the usage requirement of the node in the cloud platform by the user includes:

   Determining whether the license for the number of nodes in the license information is turned on or off according to whether the requirement for the number of nodes is included in the use requirement;

   Determining, according to the requirement of the node configuration, whether the license for configuring the node in the license information is on or off;

   Determining, according to the requirement of the use requirement of the node, whether the license for the use term of the node in the license information is turned on or off;

   The authorization of the component type in the license information is determined to be on or off according to whether the requirement for the component type is included in the usage requirement.
5. The cloud platform management method according to claim 1 or 2, wherein the deploying the nodes in the cloud platform of the user according to the license permission information comprises:

   When the node is added, the number of nodes and the node configuration of the node to be added are obtained, and it is determined whether the sum of the number of nodes in the cloud platform and the number of nodes to be added is not greater than the license. The number of nodes in the information, and whether the node configuration of the added node in the cloud platform and the total configuration of the node configuration of the node to be added are not greater than the node configuration in the license information;

   When the judgment result is yes, the node to be added is added.
6. The cloud platform management method according to claim 1 or 2, wherein, after the node in the cloud platform of the user is deployed according to the authorization permission information, and the deployed cloud platform is obtained, the method further includes :

   And if the operation instruction for expanding the node in the deployed cloud platform is received, adding the node information to be extended to the authorization permission information to obtain updated authorization permission information;

   Digitally signing the updated license information, and generating an updated license file according to the obtained updated signature information and the updated license information;

   And installing the extended node on the deployed cloud platform according to the updated license file.
7. The cloud platform management method according to claim 1 or 2, wherein, after the node in the cloud platform of the user is deployed according to the authorization permission information, and the deployed cloud platform is obtained, the method further includes :

   Verifying the signature information and the expiration date in the license file in the deployed cloud platform;

   If the verification result is successful, perform periodic authorization verification on the deployed cloud platform to determine whether the deployed cloud platform is running within the scope of the license.
8. The cloud platform management method according to claim 6, wherein the performing the periodic authorization certificate verification on the deployed cloud platform, and determining whether the deployed cloud platform is running within the scope of the license, includes:

   Verifying that the number of nodes in the deployed cloud platform is not greater than the number of nodes in the license information;

   Verifying that the configuration of the node in the deployed cloud platform is not greater than the configuration of the node in the license information;

   Verifying whether the motherboard serial number of the node in the deployed cloud platform is in the license information;

   Verifying whether the current time in the deployed cloud platform is within the validity period of the license information;

   If the verification result is yes, it is determined that the deployed cloud platform runs within the scope of the license. Otherwise, it is determined that the deployed cloud platform does not run within the scope of the license.
9. A cloud platform management device, the device comprising:

   The license information obtaining module is configured to determine the license information for the user, where the license information includes: a number of nodes, a node configuration, a node usage period, and a component type;

   a license file generating module, configured to digitally sign the license information, and generate an authorization license file according to the obtained signature information and the license information;

   a cloud platform deployment module, configured to add the license file to the cloud platform of the user when deploying the cloud platform of the user, and deploy the cloud platform of the user according to the license information The node gets the cloud platform after deployment.
10. The device according to claim 9, wherein the authorization determination module is specifically configured to determine authorization permission information for the user according to a user's usage requirement for a node in the cloud platform.
11. The cloud platform management device according to claim 9 or 10, wherein the device further comprises:

    a signature information verification module, configured to verify whether the signature information in the license file and the license permission information correspond to;

    And an information storage module, configured to store the signature information and the license permission information into the cloud platform of the user if the signature information verification module passes the verification.
12. The cloud platform management device according to claim 10, wherein the authorization permission information acquisition module is specifically configured to determine, according to whether the usage requirement includes a number of nodes, determine a node in the authorization permission information. The number of licenses is on or off;

    Determining, according to the requirement of the node configuration, whether the license for configuring the node in the license information is on or off;

    Determining, according to the requirement of the use requirement of the node, whether the license for the use term of the node in the license information is turned on or off;

    The authorization of the component type in the license information is determined to be on or off according to whether the requirement for the component type is included in the usage requirement.
13. The cloud platform management device according to claim 9 or 10, wherein the cloud platform deployment module is configured to acquire a node number and a node configuration of a node to be added when the node is added, and determine the cloud platform Whether the sum of the number of nodes of the added node and the number of nodes of the node to be added is not greater than the number of nodes in the license information, and the node configuration of the added node in the cloud platform and the to-be-added Whether the total configuration of the node configuration of the node is not greater than the node configuration in the license information; when the determination result is yes, the node to be added is added.
14. The cloud platform management device according to claim 9 or 10, wherein the device further comprises:

    The license information update module is configured to: if an operation instruction for expanding the node in the deployed cloud platform is received, add the node information to be extended to the license information to obtain updated license information;

    a license file update module configured to digitally sign the updated license information, and generate an updated license file according to the obtained updated signature information and the updated license information;

    And an extended node installation module, configured to perform an installation of the extended node on the deployed cloud platform according to the updated license file.
15. The cloud platform management device according to claim 9 or 10, wherein the device further comprises:

    a first verification module, configured to verify signature information and an expiration date in the license file in the deployed cloud platform;

    The second verification module is configured to perform periodic authorization license verification on the deployed cloud platform when the first verification module is successfully verified, and determine whether the deployed cloud platform is running within the scope of the license.
16. The cloud platform management device according to claim 15, wherein the second verification module is configured to verify whether the number of nodes in the deployed cloud platform is not greater than a node in the license information. And verifying whether the configuration of the node in the deployed cloud platform is not greater than the configuration of the node in the license information; and verifying whether the serial number of the motherboard of the node in the deployed cloud platform is in the license information; Verifying whether the current time in the deployed cloud platform is within the validity period of the license information;

    If the verification result is yes, it is determined that the deployed cloud platform runs within the scope of the license. Otherwise, it is determined that the deployed cloud platform does not run within the scope of the license.
17. An electronic device comprising: a processor and a machine readable storage medium storing machine executable instructions executable by the processor, the processor executing the machine executable instructions The steps of implementing the cloud platform management method of any of claims 1-7.
18. A computer readable storage medium having stored therein a computer program, the computer program being executed by a processor, the step of implementing the cloud platform management method of any one of claims 1-7.
19. A computer program product comprising instructions, the computer program product comprising instructions, when executed on a computer, causing a computer to perform the cloud platform management method steps of any of claims 1-7.

Images