Deployment of target cloud service platform

Abstract

The invention provides a method, a device and a non-transitory computer readable medium for deploying a target cloud service platform. Configuration information for a target cloud service platform can be obtained. A bootstrap infrastructure may be established in a public cloud service platform based on the configuration information, the bootstrap infrastructure providing a set of core services associated with the target cloud service platform. A target service set may be created in the target cloud service platform based on the core service set.

Description

Background Art

[0001] Currently, cloud computing technology is developing rapidly and has completely changed the way enterprises and organizations store, manage and process data. In cloud computing, computing, storage, networking and other computing services can be provided through the Internet. Cloud computing can distribute computing tasks on a resource pool composed of a large number of computing devices, so that various application systems can obtain computing power, storage space, network communication capabilities, etc. from the resource pool as needed. Summary of the invention

[0002] This summary is provided to introduce a set of concepts that will be further described in the following detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0003] Embodiments of the present disclosure provide a method, apparatus, and non-transitory computer-readable medium for deploying a target cloud service platform. Configuration information for the target cloud service platform can be obtained. A bootstrap infrastructure can be established in a public cloud service platform based on the configuration information, and the bootstrap infrastructure provides a core service set associated with the target cloud service platform. A target service set can be created in the target cloud service platform based on the core service set.

[0004] An embodiment of the present disclosure proposes a cloud service system. The cloud service system may include a public cloud service platform and a target cloud service platform. The public cloud service platform may include a configuration storage area, a workflow engine, and a boot and start infrastructure. The configuration storage area may be used to store configuration information for the target cloud service platform. The workflow engine may be used to obtain the configuration information from the configuration storage area, and to establish the boot and start infrastructure based on the configuration information. The boot and start infrastructure may be used to provide a core service set associated with the target cloud service platform. The workflow engine is also used to create a target service set in the target cloud service platform based on the core service set. The target cloud service platform may be used to provide the target service set.

[0005] It should be noted that one or more of the above aspects include the features specifically pointed out in the following detailed description and claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. These features are merely indicative of the various ways in which the principles of various aspects may be implemented, and the present disclosure is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided to illustrate rather than limit the disclosed aspects.

[0007] Figure 1A A schematic diagram of a cloud service system in a configuration information acquisition phase according to an embodiment is shown.

[0008] Figure 1B A schematic diagram of a cloud service system in a bootstrapping infrastructure establishment phase according to an embodiment is shown.

[0009] Figure 1C A schematic diagram of a cloud service system in the target service set creation phase according to an embodiment is shown.

[0010] Figure 1D A schematic diagram of a cloud service system according to an embodiment at a target cloud service platform activation stage is shown.

[0011] Figure 2 An exemplary process of obtaining configuration information according to an embodiment is shown.

[0012] Figure 3 An exemplary process of establishing a boot-start infrastructure according to an embodiment is shown.

[0013] Figure 4 An exemplary process of creating a target service set according to an embodiment is shown.

[0014] Figure 5 An exemplary process of enabling a target cloud service platform according to an embodiment is shown.

[0015] Figure 6 A flowchart of an exemplary method for deploying a target cloud service platform according to an embodiment is shown.

[0016] Figure 7 An exemplary apparatus for deploying a target cloud service platform according to an embodiment is shown.

[0017] Figure 8 An exemplary apparatus for deploying a target cloud service platform according to an embodiment is shown. DETAILED DESCRIPTION

[0018] The present disclosure will now be discussed with reference to various exemplary embodiments. It should be understood that the discussion of these embodiments is only for enabling those skilled in the art to better understand and thereby implement the embodiments of the present disclosure, and does not teach any limitation on the scope of the present disclosure.

[0019] A cloud service platform may refer to a platform that can provide users with a series of cloud-based services, which may also be referred to as a cloud, cloud instance, and other similar concepts. The services provided by the cloud service platform can utilize the computing, storage, networking, and other resources of the cloud service platform through virtualization technology to achieve various functions, such as email, databases, video conferencing, etc. A data center may provide infrastructure for a cloud service platform. A data center may include computing equipment, support facilities, and the like. The computing equipment of a data center refers to hardware equipment that provides computing power, storage capacity, and network communication capabilities, and may include, for example, servers, storage devices, switches, routers, and other types of equipment. Support facilities refer to various auxiliary systems that support the normal operation of a data center, and may include, for example, power systems, cooling systems, and the like.

[0020] In some scenarios, a cloud service provider needs to establish a new cloud service platform in a specific area. The new cloud service platform may also be referred to as a target cloud service platform, a new cloud instance, etc. In this disclosure, for simplicity, the new cloud service platform is uniformly referred to as a target cloud service platform. Deploying a target cloud service platform refers to the process of configuring the hardware and software of the target cloud service platform so that the target cloud service platform can provide the required services or functions.

[0021] In the conventional target cloud service platform deployment mechanism, the deployment process can only be started after the data center construction is completed. The data center construction process may include installing the data center's computing equipment and supporting facilities, and first configuring some underlying services on a few servers to implement device management of the computing equipment in the data center. The process of building a data center is very time-consuming and usually takes several years.

[0022] The embodiments of the present disclosure propose a mechanism for deploying a target cloud service platform. The target cloud service platform deployment mechanism of the present disclosure can use existing resources in a public cloud service platform to establish a bootstrap infrastructure in the public cloud service platform. The bootstrap infrastructure can have a preliminary configuration for the target cloud service platform. Using the bootstrap infrastructure, a target service set can be created in the target cloud service platform, so that the target cloud service platform can provide user-oriented services.

[0023] In one aspect, embodiments of the present disclosure may obtain configuration information for a target cloud service platform. Configuration information may refer to any information or data used to configure the target cloud service platform so that it can implement the required services or functions. Configuration information may be generated by developers at a development management platform, and may include buildout artifacts generated during the software development process and other information used to configure the target cloud service platform, such as certificates, keys, etc. associated with the target cloud service platform.

[0024] In one aspect, the present disclosure may establish a bootstrap infrastructure in a public cloud service platform based on the obtained configuration information. The established bootstrap infrastructure may provide a core service set associated with a target cloud service platform. The core service set includes core services for implementing the internal core functions of the target cloud service platform, and these core services may serve as the basis for forming the target cloud service platform.

[0025] In one aspect, the present disclosure can create a target service set in a target cloud service platform based on a core service set. The target service set is a superset of the core service set, which can include a large number of services provided to meet user needs. After creating the target service set, the target cloud service platform can operate in a mode close to delivering a product.

[0026] In one aspect, the target cloud service platform can be a cloud service platform isolated from a public cloud service platform. The isolated cloud service platform can provide enhanced data security and data compliance. Data security is used to protect digital information from unauthorized access, damage or theft throughout its life cycle. Data compliance is used to make digital information meet the requirements of regulations established by different organizations or jurisdictions (e.g., countries, cities, etc.) by defining a series of standards to avoid loss, theft, damage and misuse of sensitive data.

[0027] The target cloud service platform deployment mechanism disclosed in the present invention helps to achieve rapid deployment of the target cloud service platform. For example, by utilizing existing resources in the public cloud service platform, the deployment process for the target cloud service platform can be started in advance without waiting for the construction of the data center of the target cloud service platform to be completed.

[0028] The target cloud service platform deployment mechanism disclosed in the present invention helps to provide better service consistency. The target cloud service platform deployment mechanism disclosed in the present invention can establish a bootstrap infrastructure in the public cloud service platform to provide a core service set associated with the target cloud service platform. Thanks to the network connection between the public cloud service platform and the development management platform, the development management platform can update the core service set so that the services in the core service set are consistent with the versions of the corresponding services in the public cloud service platform. When multiple target cloud service platforms are established at the same time, the target cloud service platform deployment mechanism disclosed in the present invention also helps to ensure service consistency between multiple core service sets associated with multiple target cloud service platforms.

[0029] The target cloud service platform deployment mechanism disclosed in the present invention helps to solve the circular dependency problem. During the deployment process of the target cloud service platform, there may be a situation where there is a circular dependency relationship between the services that need to be created. The target cloud service platform deployment mechanism disclosed in the present invention can use the existing services in the public cloud service platform to break this closed-loop circular dependency.

[0030] The target cloud service platform deployment mechanism disclosed in the present invention helps to realize some services associated with non-core functions of the target cloud service platform in advance. Services associated with non-core functions are generally created in the later stage of the target cloud service platform deployment, which may lead to the loss of some data in the early stage of the target cloud service platform deployment. The target cloud service platform deployment mechanism disclosed in the present invention can use the existing resources in the public cloud service platform to realize these non-core functions in advance.

[0031] Exemplary embodiments of the present disclosure will be described below with reference to the accompanying drawings.

[0032] Figures 1A to 1D A schematic diagram of a cloud service system 100 according to an embodiment is shown. The target cloud service platform deployment mechanism according to an embodiment of the present disclosure can be implemented in the cloud service system 100 to achieve deployment of the target cloud service platform. Exemplarily, the cloud service system 100 may include a public cloud service platform 110, a development management platform 120, a target cloud service platform 130, and the like.

[0033] The public cloud service platform 110 is an existing cloud service platform that can provide open cloud services to users in the coverage area. In one example, the public cloud service platform 110 can provide a global coverage area using data centers built in different geographical locations. The public cloud service platform 110 can be established and managed by a cloud service provider.

[0034] In an embodiment of the present disclosure, existing resources of the public cloud service platform 110 may be utilized to facilitate early deployment of the target cloud service platform 130. These existing resources may include: hardware resources of the public cloud service platform 110, such as servers, etc.; and software resources of the public cloud service platform 110, such as services, etc. Figures 1A to 1D It is shown that the public cloud service platform 110 may include a workflow engine 112. The workflow engine 112 may also be referred to as a task orchestration engine, a task orchestration tool, etc., which is used to automatically perform resource provision and configuration within the public cloud service platform 110.

[0035] The development management platform 120 may refer to a computing platform used by a cloud service provider to develop and manage a public cloud service platform and a target service platform. A network connection may be provided between the public cloud service platform 110 and the development management platform 120. The development management platform 120 may manage the public cloud service platform 110, for example, publishing updated services to the public cloud service platform 110, etc.

[0036] Figures 1A to 1D It is shown that the development management platform 120 may include a development tool 122 for performing software development work for the public cloud service platform and the target cloud service platform. For example, the development tool 122 can be implemented using VisualStudio, Eclipse, IntelliJ IDEA, and other commonly used software development tools. The development management platform 120 may also include other tools not shown, such as a code library for implementing the storage and management of code, a continuous integration and continuous delivery (CID: Continuous Integration, Continuous Delivery) pipeline for implementing the integration and delivery of code for different software modules, a publishing engine for publishing code to the public cloud service platform and the target cloud service platform, and other tools associated with the development and management of the public cloud service platform and the target cloud service platform.

[0037] The target cloud service platform 130 refers to a new cloud service platform to be established in a specific region. After deployment is completed, the target cloud service platform 130 can operate independently of the public cloud service platform 110, and can provide the same or different services as the public cloud service platform 110. The target cloud service platform 130 and the public cloud service platform 110 can have different coverage. For example, the public cloud service platform 110 can cover the world, while the target cloud service platform can only cover a specific jurisdiction.

[0038] In one example, the target cloud service platform 130 may be a cloud service platform isolated from the public cloud service platform 110 to provide enhanced data security and data compliance. Depending on the level of data security and data compliance required, the isolated cloud service platform may further include a completely isolated cloud service platform, a partially isolated cloud service platform, and the like. There should be no network connection between the completely isolated cloud service platform and the public cloud service platform 110. For example, a completely isolated cloud service platform may include an air-gapped type cloud service platform, and the like. A partially isolated cloud service platform may have a restricted network connection with the public cloud service platform 110. For example, a partially isolated cloud service platform may include a sovereign type cloud service platform, and the like. In a sovereign type cloud service platform, data requiring secure access and privacy can only reside within the sovereign type cloud service platform. It should be understood that although the target cloud service platform 130 is exemplarily explained as a cloud service platform isolated from the public cloud service platform 110 in multiple parts of the present disclosure, the embodiments of the present disclosure are not limited to this, but may further cover any other scenarios where the target cloud service platform 130 is not a cloud service platform isolated from the public cloud service platform 110.

[0039] Figures 1A to 1D Schematic diagrams of the cloud service system 100 at different deployment stages are shown respectively.

[0040] Figure 1A FIG. 1 shows a schematic diagram of the cloud service system 100 in the configuration information acquisition phase. At this time, the data center of the target cloud service platform 130 may still be under construction, which will not affect the configuration information acquisition phase. Figure 1A As shown, there is a network connection between the public cloud service platform 110 and the development management platform 120. The network connection can be used to transmit the configuration information 115 for the target cloud service platform 130 from the development management platform 120 to the public cloud service platform 110.

[0041] The configuration information 115 may be generated at the development management platform 120 or obtained in any other manner. The configuration information 115 may refer to any information or data used to configure the target cloud service platform 130 so that it can implement the required services or functions.

[0042] In one implementation, the configuration information 115 may include build artifacts for the target service platform 130. Build artifacts refer to tangible products generated during the process of developers using the development tools 122 to develop software for the target service platform 130, and may include, for example, source code, development documents, compiled files, executable files, test cases, test documents, test results, etc.

[0043] In one example, the build artifact may be verified. Verification of the build artifact can ensure that different software modules of the build artifact are correct on the one hand, and that software modules developed by different development teams are consistent on the other hand. For example, the build artifact can be verified by performing integration testing on the build artifact.

[0044] In one implementation, the configuration information 115 for the target cloud service platform 130 may also include other information in addition to the build artifacts, such as certificates, keys, etc. associated with the target cloud service platform 130. The other information may be determined after a small number of computing devices in the target cloud service platform 130 have been configured to provide some internal underlying services. For example, a small number of computing devices in the target cloud service platform 130 may have been configured to provide a dial-tune service, which defines how data interaction is performed between computing devices and specifies the certificates and keys to be used for the target cloud service platform 130. In addition, a small number of computing devices in the target cloud service platform 130 may have been configured to provide a network service to exchange data with the development management platform 120 over a network. Accordingly, the development management platform 120 may extract information such as certificates and keys from the target cloud service platform 130 over a network, and provide the extracted information to the public cloud service platform 110 as part of the configuration information 115.

[0045] The public cloud service platform 110 may include a configuration storage area 114 for storing configuration information 115. The configuration storage area 114 may be an independent storage area divided by the workflow engine 112 from the storage space of the public cloud service platform 110.

[0046] Figure 1B FIG. 1 shows a schematic diagram of the cloud service system 100 in the bootstrap infrastructure establishment phase. At this time, the data center of the target cloud service platform 130 may still be under construction without affecting the bootstrap infrastructure establishment phase. Figure 1BAs shown, a bootstrap infrastructure 116 can be established in the public cloud service platform 110. The bootstrap infrastructure 116 can be established by the workflow engine 112 based on the configuration information 115. The bootstrap infrastructure 116 is an infrastructure that is implemented using resources in the public cloud service platform and has a preliminary configuration for the target cloud service platform, which can also be called a bootstrap environment. The bootstrap infrastructure 116 can provide a core service set 118. The core service set 118 defines a series of core services associated with the core or underlying functions used to support the operation of the target cloud service platform, which can also be called a minimum viable product (MVP: Minimum Viable Product) and the like. For example, the core services in the core service set 118 may include control plane services, which are used to automatically manage computing devices in the cloud service platform, including performing software installation, patch management, restart, service deployment and other operations on the computing devices. The core services may also include: an authentication service for verifying the identity of a user to ensure that only authenticated users can access data; an authorization service for determining the user's authority and allowing the user to perform corresponding data access operations according to the type of authority the user has; an asset inventory management service for managing the hardware asset list of a data center; etc. It should be understood that in an embodiment of the present disclosure, the core services in the core service set 118 may include any one or more of the exemplary services listed above, and may also include any other type of core or underlying functional services for supporting the operation of the target cloud service platform.

[0047] The boot and start infrastructure 116 can be regarded as a tenant in the public cloud service platform 110, which occupies virtual resources in the public cloud service platform to provide a core service set 118. The boot and start infrastructure 116 is isolated from other tenants in the public cloud service platform 110 to ensure that the boot and start infrastructure 116 is protected by security and data compliance in the public cloud service platform 110. The isolation between the boot and start infrastructure 116 and other tenants in the public cloud service platform 110 can be achieved by any tenant isolation technology known in the art, such as firewall technology, software defined network (SDN: Software Defined Network) technology, etc.

[0048] Figure 1C FIG. 1 is a schematic diagram of the cloud service system 100 in the target service set creation stage. At this point, the construction of the data center of the target cloud service platform 130 has been completed or substantially completed, so the computing equipment of the data center can be enabled to create a target service set 132 in the target cloud service platform 130 based on the core service set 118. Figure 1CAs shown, a target service set 132 can be created in the target cloud service platform 130. The target service set 132 can be created by the workflow engine 112 based on the core service set 118. The target service set 132 defines a series of target services for meeting user needs in the target cloud service platform, which can also be called a minimum marketable product (MMP: Minimum Marketable Product). For example, the target services in the target service set 132 may include: a mail service for transmitting emails; a file sharing service for sharing files between multiple users; a file collaboration service for enabling multiple users to collaboratively edit files; an instant messaging service for real-time data communication between users; and so on. It should be understood that in an embodiment of the present disclosure, the target services in the target service set 132 may include any one or more of the exemplary services listed above, and may also include any other type of service for meeting user needs in the target cloud service platform.

[0049] like Figure 1C As shown, there may be a network connection between the bootstrap infrastructure 116 and the target cloud service platform 130. Using the network connection, the core services in the core service set 118 may be migrated from the bootstrap infrastructure 116 to the target cloud service platform 130. For example, the migration may be performed by the workflow engine 112.

[0050] The target service set 132 may be a superset of the core service set 118. Therefore, the target service set 132 may include services added on the basis of the core service set 118. In one implementation, it may be determined which services need to be added based on the product service list. The product service list may define a list of services that the target cloud service platform 130 should provide after the deployment is completed, and may be provided based on the needs of the target cloud service platform 130. In one example, these added services may be extended in the target cloud service platform 130 based on the migrated core services. For example, the extension may be performed by the workflow engine 112. The workflow engine 112 may configure the core services in the core service set 118 so that the migrated core services extend the services to be added in the target cloud service platform. In one example, these added services may be published from the development management platform 120 to the target cloud service platform 130 through a network connection between the development management platform 120 and the target cloud service platform 130.

[0051] Figure 1D FIG. 1 shows a schematic diagram of the cloud service system 100 in the activation phase of the target cloud service platform. Figure 1DAs shown, after the target service set 132 has been created in the target cloud service platform 130, the target cloud service platform 130 can be enabled. After the target cloud service platform 130 is enabled, the network connection between the target cloud service platform 130 and the bootstrap infrastructure 116 can be disconnected, or access restrictions can be imposed on the network connection, for example, a firewall 125 can be imposed on the network connection. In one example, the network connection between the development management platform 120 and the target cloud service platform 130 can be maintained to enable the development management platform 120 to manage the target cloud service platform 130, for example, to update the version of the service in the target cloud service platform 130. In one example, after the target cloud service platform 130 is enabled, the network connection between the development management platform 120 and the target cloud service platform 130 can be disconnected or access restrictions can be imposed on the network connection, which makes the target cloud service platform 130 fully isolated from the outside world so as to meet further data security and compliance requirements.

[0052] Figure 2 FIG. 2 shows an exemplary process 200 for obtaining configuration information according to an embodiment. The operations in process 200 may be performed by Figures 1A to 1D The workflow engine 112 shown in FIG.

[0053] At 210, the workflow engine may establish a configuration storage area in the public cloud service platform. The workflow engine may divide an independent storage area in the storage space of the public cloud service platform as the configuration storage area. Dividing an independent configuration storage area is conducive to isolating the configuration information from the data of other tenants of the public cloud service platform, thereby improving the security of the configuration information. The configuration storage area can be used to store configuration information for the target cloud service platform, for example, in combination with Figures 1A to 1D Configuration information 115 discussed. The configuration information may be generated at the development management platform or obtained in any other manner. For example, via a network connection between the development management platform and the public cloud service platform, the configuration information may be transmitted to the public cloud service platform and then stored in a configuration storage area. In one example, establishing a configuration storage area may be a broad concept, which may include not only dividing independent storage areas in a storage space, but also building a configuration database in the divided storage areas. Thus, after receiving the configuration information from the development management platform, the storage of the configuration information may be achieved by filling the data into the configuration database.

[0054] At 220, the workflow engine may obtain configuration information from the configuration storage area. The workflow engine may perform a data read operation on the configuration storage area, for example, read a data entry in a configuration database, to obtain the configuration information.

[0055] According to an embodiment of the present disclosure, after the configuration information is obtained, a bootstrap infrastructure may be established in a public cloud service platform based on the configuration information to provide a core service set associated with a target cloud service platform.

[0056] Figure 3 An exemplary process 300 for establishing a boot-start infrastructure according to an embodiment is shown. The operations in process 300 may be performed by Figures 1A to 1D The workflow engine 112 shown in FIG.

[0057] In one example, in order to establish a bootstrap infrastructure that provides a set of core services, some core services may be copied from a public cloud service platform at 310. The copying of the core services from the public cloud service platform may be performed based on configuration information, wherein the configuration information determines which services should be included in the set of core services provided by the bootstrap infrastructure. The workflow engine may obtain a copy of the corresponding core service in the public cloud service platform and place the obtained copy on a server to form the bootstrap infrastructure.

[0058] In one example, in order to establish a bootstrap infrastructure that provides a set of core services, some core services can be generated using a seed server at 311. The seed server is the first or a few servers that are configured to be enabled in the bootstrap infrastructure, which can provide the lowest-level services for deploying the target cloud service platform. These lowest-level services are usually not user-oriented, but provide internal functions to promote the initial operation of the data center. For example, these lowest-level services may include services for managing servers so that more servers in the data center can be configured to provide core services in subsequent stages. The seed server and these lowest-level services it provides can call more servers in the bootstrap infrastructure based on configuration information to generate core services in more servers. Using a seed server to generate core services can minimize the association between the core services provided by the bootstrap infrastructure and the existing services in the public cloud platform, which helps to avoid the target cloud service platform that is ultimately deployed from being affected by the existing services in the public cloud platform.

[0059] At 320, a bootstrap infrastructure may be established using core services copied from a public cloud service platform and / or generated by a seed server, and the established bootstrap infrastructure may provide a core service set that implements the internal core functions of the target cloud service platform.

[0060] In one example, the core service set may also include other services that are not closely related to the internal core functions of the target cloud service platform, such as monitoring services, logging services, etc. The monitoring service can be used to monitor the operating data of the deployment process for the target cloud service platform. The logging service can be used to record log data of the deployment process for the target cloud service platform. These services are usually created in the later stages of the deployment of the target cloud service platform. However, in an embodiment of the present disclosure, these services can be created in advance during the stage of establishing the bootstrap infrastructure to avoid the loss of some data in the early stages of the deployment of the target cloud service platform.

[0061] In one example, some core services in the core service set of the bootstrap infrastructure may be the same services as the corresponding core services in the public cloud service platform. In this case, the core services in the core service set and the corresponding core services in the public cloud service platform should use the same version to ensure service consistency.

[0062] In one example, a core service circular dependency problem may be encountered in the process of generating a core service set. The core service circular dependency problem is caused by the possible dependency between core services. For example, the creation of a first core service may depend on a second core service, the creation of a second core service may depend on a third core service, and the creation of a third core service may depend on the first core service. As a result, the dependency relationship between the three core services forms a complete closed loop, resulting in the inability to start the core service set creation process from any one core service. In order to break this closed-loop core service circular dependency, at least one core service among multiple core services with a circular dependency relationship can be created using existing services in a public cloud service platform. For example, an existing service in a public cloud service platform that is the same as the first core service can be used to first create a third core service that depends on the first core service in a boot and start infrastructure, and then the created third core service can be used to create a second core service that depends on the third core service in the boot and start infrastructure, and finally the created second core service can be used to create a first core service that depends on the second core service in the boot and start infrastructure. In this way, the closed-loop core service circular dependency can be broken using existing services in a public cloud service platform.

[0063] In one example, the public cloud service platform may include multiple data centers. The bootstrap infrastructure may be established in a data center in the public cloud service platform that is geographically closest to the data center of the target cloud service platform. This facilitates efficient data transmission between the bootstrap infrastructure and the target cloud service platform in a later stage.

[0064] In one example, multiple target cloud service platforms 130 may be deployed simultaneously. In this case, a corresponding bootstrap infrastructure 116 may be established for each target cloud service platform 130 in the public cloud service platform 110 .

[0065] At 330, a separate identity manager can be created in the bootstrap infrastructure. An identity manager is a system for managing user access rights, which is used to control which users can access which resources using the corresponding access rights assigned to users by a system administrator. When a user attempts to access a resource, the identity manager can allow or prevent the user from performing access operations based on the user's access rights. The identity manager created in the bootstrap infrastructure is specifically for the target cloud service platform, and therefore can be separated from the existing identity manager in the public cloud service platform. The separation between the identity manager created in the bootstrap infrastructure and the existing identity manager in the public cloud service platform can be embodied as follows: the system administrator of the existing identity manager does not have the authority to log in to the identity manager created at 330 to perform permission allocation operations. On the contrary, the identity manager created at 330 can be managed by the platform operator responsible for operating the target cloud service platform. In the case where the target cloud service platform is an isolated cloud service platform, creating a separate identity manager can help meet the requirements of the isolated cloud service platform for data security and compliance.

[0066] According to an embodiment of the present disclosure, after the bootstrap infrastructure is established, the data center construction of the target cloud service platform can be waited for to be completed so as to enter the next stage to create a target service set in the target cloud service platform. During the waiting process, the core services in the core service set provided by the bootstrap infrastructure can be updated in the public cloud service platform to promote the service consistency between the core services provided by the bootstrap infrastructure and the corresponding services in the public cloud service platform. In one example, the update of the core service can be implemented using the control plane service of the bootstrap infrastructure. The development management platform can provide updated code to the control plane to update the version of the core service. This allows the core services in the core service set and the corresponding services in the public cloud service platform to be updated at the same rhythm. Thus, the core services in the core service set and the corresponding services in the public cloud service platform can meet the service consistency requirements. In one example, in a similar manner, when multiple target cloud service platforms are established at the same time, multiple core service sets respectively associated with multiple target cloud service platforms can also have service consistency.

[0067] According to an embodiment of the present disclosure, after the construction of the data center is completed, the next stage can be entered to create a target service set in the target cloud service platform.

[0068] Figure 4 An exemplary process 400 for creating a target service set according to an embodiment is shown. The operations in process 400 may be performed by Figures 1A to 1D The workflow engine 112 shown in FIG.

[0069] At 410, the core services in the core service set can be migrated from the boot-start infrastructure to the target cloud service platform. Exemplarily, the migration process can be divided into three stages. In the first stage, the core services in the core service set can be fully provided by N servers in the boot-start infrastructure; in the second stage, the core services can be jointly provided by N servers in the boot-start infrastructure and M servers in the target cloud service platform; in the third stage, the core services can be fully provided by M servers in the target cloud service platform. These three stages implement the process of gradually migrating the core service set from the boot-start infrastructure in the public cloud service platform to the target cloud service platform. In one example, entering the second stage from the first stage involves the process of transferring data from the boot-start infrastructure to the target cloud service platform. For example, copies and running data of core services can be transferred from the boot-start infrastructure to the target cloud service platform, so that the servers in the target cloud service platform and the servers in the boot-start infrastructure can provide the same core services synchronously. In one example, the process of transferring data from the bootstrap infrastructure to the target cloud service platform may not be involved in the process of moving data from the first stage to the second stage. For example, some services such as web-based services do not require the retention of state information during operation, and can therefore be expanded to any server so that these servers provide the same core services. In one example, the above two methods can be combined. For example, the migration process of some core services in the core service set may involve data transfer, while the migration process of some core services may not involve data transfer.

[0070] At 420, the migrated core services can be expanded to a target service set. Expanding the migrated core services to a target service set can be achieved by adding some services based on the migrated core services. In one implementation, the workflow engine can determine which services need to be added based on the product service list. In one example, the workflow engine can configure the core services in the core service set so that the migrated core services expand the services to be added in the target cloud service platform. For example, the migrated core services can call more servers in the target cloud service platform to generate the added services. In one example, through the network connection between the development management platform and the target cloud service platform, the development management platform can publish the added services to the target cloud service platform.

[0071] In one example, a target service circular dependency problem may be encountered in the process of creating a target service set in the target cloud service platform. In order to break this closed-loop target service circular dependency, existing services in the public cloud service platform, including core services in the bootstrap infrastructure or other services in the public cloud service platform outside the bootstrap infrastructure, can be used to create at least one target service among multiple target services with circular dependencies. In the same way as solving the core service circular dependency problem, the closed-loop target service circular dependency can be broken by using existing services in the public cloud service platform.

[0072] In one example, creating a target service set in a target cloud service platform may be an ongoing process. For example, when a dependency of a target service required by the target cloud service platform is satisfied, the target service may be created in the target cloud service platform based on the core service set. During the creation of the target cloud service platform, some overlapping functions between the core service set and the target service set may be controlled by the target service set.

[0073] According to an embodiment of the present disclosure, the completion of the creation of the target service set means the completion of the deployment process for the target cloud service platform, and accordingly, the target cloud service platform can now run in a mode close to the delivery product. In this case, the target cloud service platform can be enabled.

[0074] Figure 5 An exemplary process 500 of enabling a target cloud service platform according to an embodiment is shown. In one example, the operations in process 500 can be completed by a workflow engine within the target cloud service platform.

[0075] At 510, the target cloud service platform may be enabled. In one example, before enabling the target cloud service platform, it may be determined whether the target cloud service platform meets the enabling conditions. For example, risk assessment, security testing, data compliance review, etc. may be performed on the target cloud service platform. If it is determined that the target cloud service platform meets the enabling conditions, the target cloud service platform may be enabled.

[0076] At 520 , the network connection between the bootstrap infrastructure and the target cloud service platform may be disconnected, or access restrictions may be imposed on the network connection, for example, a firewall may be imposed on the network connection.

[0077] In one example, after the target cloud service platform is enabled, the established bootstrap infrastructure can be abandoned in the public cloud service platform. For example, virtual resources occupied by the bootstrap infrastructure can be released for use by other tenants in the public cloud service platform. In one example, the bootstrap infrastructure can be retained in the public cloud service platform for subsequent security, data compliance, and other aspects of the target cloud service platform.

[0078] In one example, after the target cloud service platform is enabled, certificates, keys, etc. may be updated in the target cloud service platform to avoid security issues.

[0079] In one example, after the target cloud service platform is enabled, the development management platform can manage the target cloud service platform in a manner similar to managing a public cloud service platform, for example, publishing new services to the target cloud service platform, updating services in the target cloud service platform, etc. In this case, the network connection between the development management platform and the target cloud service platform can be maintained. In one example, after the target cloud service platform is enabled, the network connection between the development management platform and the target cloud service platform can be disconnected or access restrictions can be imposed on the network connection, which fully isolates the target cloud service platform from the outside world to meet further data security and compliance requirements.

[0080] Figure 6 A flow chart of an exemplary method 600 for deploying a target cloud service platform according to an embodiment is shown.

[0081] At 610 , configuration information for a target cloud service platform may be obtained.

[0082] At 620 , a bootstrap infrastructure may be established in a public cloud service platform based on the configuration information, the bootstrap infrastructure providing a set of core services associated with the target cloud service platform.

[0083] At 630 , a target service set may be created in the target cloud service platform based on the core service set.

[0084] In one implementation, method 600 may further include establishing a configuration storage area in the public cloud service platform for storing the configuration information, wherein obtaining the configuration information includes obtaining the configuration information from the configuration storage area.

[0085] In one implementation, the configuration information may include build artifacts for the target cloud service platform.

[0086] In one implementation, the core services in the core service set may be generated by at least using a seed server in the bootstrap infrastructure. In one implementation, the core services in the core service set may be copied from the public cloud service platform based on the configuration information.

[0087] In an implementation, creating a target service set in the target cloud service platform based on the core service set may include: migrating core services in the core service set from the bootstrap infrastructure to the target cloud service platform.

[0088] The creating a target service set in the target cloud service platform based on the core service set may further include: expanding the migrated core services into the target service set in the target cloud service platform according to a product service list associated with the target cloud service platform.

[0089] In one implementation, creating a target service set in the target cloud service platform based on the core service set may include: based on dependencies between multiple target services in the target service set, using existing services in the public cloud service platform to create at least one target service among the multiple target services.

[0090] In one implementation, establishing the bootstrap infrastructure may include: based on dependencies between multiple core services in the core service set, using existing services in the public cloud service platform to create at least one core service among the multiple core services.

[0091] In one implementation, the target cloud service platform may include a cloud service platform isolated from the public cloud service platform, and method 600 may also include: after the target service set is created, disconnecting the network connection between the boot infrastructure and the target cloud service platform or imposing access restrictions on the network connection.

[0092] In one implementation, the method 600 may further include: updating the core services in the core service set provided by the boot infrastructure to meet the service consistency requirement.

[0093] In one implementation, the method 600 may further include: creating an identity manager associated with the target cloud service platform in the bootstrapping infrastructure, wherein the created identity manager is separate from an existing identity manager in the public cloud service platform.

[0094] In one implementation, the core service set may include at least one of a monitoring service and a logging service for deployment of the target cloud service platform.

[0095] It should be understood that method 600 may also include any steps / processes for deploying a target cloud service platform according to the above-mentioned embodiments of the present disclosure.

[0096] Figure 7 An exemplary apparatus 700 for deploying a target cloud service platform according to an embodiment is shown.

[0097] The device 700 may include: a configuration information acquisition module 710, used to obtain configuration information for a target cloud service platform; a boot and startup infrastructure establishment module 720, used to establish a boot and startup infrastructure in a public cloud service platform based on the configuration information, wherein the boot and startup infrastructure provides a core service set associated with the target cloud service platform; and a target service set creation module 730, used to create a target service set in the target cloud service platform based on the core service set.

[0098] In addition, the device 700 may also include any other modules configured to perform any operations of the method for deploying a target cloud service platform according to the above-mentioned embodiments of the present disclosure.

[0099] Figure 8 An exemplary apparatus 800 for deploying a target cloud service platform according to an embodiment is shown.

[0100] The device 800 may include at least one processor 810. The device 800 may also include a memory 820 connected to the at least one processor 810. The memory 820 may store computer executable instructions, which, when executed, enable the at least one processor 810 to: obtain configuration information for a target cloud service platform; establish a boot and start infrastructure in a public cloud service platform based on the configuration information, wherein the boot and start infrastructure provides a core service set associated with the target cloud service platform; and create a target service set in the target cloud service platform based on the core service set. In addition, the at least one processor 810 may also be configured to perform any other operations of the method for deploying a target cloud service platform according to the above-mentioned embodiment of the present disclosure.

[0101] Embodiments of the present disclosure may be implemented in a non-transitory computer-readable medium. The non-transitory computer-readable medium may include instructions, which, when executed, may cause at least one processor to: obtain configuration information for a target cloud service platform; establish a boot and start infrastructure in a public cloud service platform based on the configuration information, the boot and start infrastructure providing a core service set associated with the target cloud service platform; and create a target service set in the target cloud service platform based on the core service set. In addition, when the instructions are executed, at least one processor may also execute any step / process of the method for deploying a target cloud service platform according to the above-mentioned embodiment of the present disclosure.

[0102] An embodiment of the present disclosure proposes a cloud service system, including a public cloud service platform and a target cloud service platform. The public cloud service platform may include a configuration storage area, a workflow engine, and a boot and start infrastructure. The configuration storage area may be used to store configuration information for the target cloud service platform. The workflow engine may be used to obtain the configuration information from the configuration storage area, and may establish the boot and start infrastructure based on the configuration information. The boot and start infrastructure may be used to provide a core service set associated with the target cloud service platform. The workflow engine may also be used to create a target service set in the target cloud service platform based on the core service set. The target cloud service platform may be used to provide the target service set.

[0103] In one implementation, the configuration information may include build artifacts for the target cloud service platform.

[0104] In one implementation, the bootstrap infrastructure may include a seed server, and the core services in the core service set may be generated at least using the seed server; or the core services in the core service set may be copied from the public cloud service platform by the workflow engine based on the configuration information.

[0105] In one implementation, the workflow engine may also be used to create a target service set by performing the following operations: migrating core services in the core service set from the bootstrap infrastructure to the target cloud service platform.

[0106] The workflow engine may also be used to create a target service set by: expanding the core service set into the target service set in the target cloud service platform according to a product service list associated with the target cloud service platform.

[0107] In one implementation, the target cloud service platform may include a cloud service platform isolated from the public cloud service platform, and the workflow engine may also be used to: after the target service set is created, disconnect the network connection between the boot startup infrastructure and the target cloud service platform or impose access restrictions on the network connection.

[0108] In addition, the components included in the cloud service system may also be respectively configured to perform any other operations of the method for deploying a target cloud service platform according to the above-mentioned embodiment of the present disclosure.

[0109] The embodiment of the present disclosure proposes a computer program product, which includes a computer program, and the computer program can be executed by a processor to: obtain configuration information for a target cloud service platform; establish a boot and start infrastructure in a public cloud service platform based on the configuration information, and the boot and start infrastructure provides a core service set associated with the target cloud service platform; and create a target service set in the target cloud service platform based on the core service set. In addition, the computer program can also be executed by the processor to perform any step / process of the method for deploying a target cloud service platform according to the above-mentioned embodiment of the present disclosure.

[0110] It should be understood that all operations in the method described above are merely exemplary, and the present disclosure is not limited to any operations in the method or the order of these operations, but should cover all other equivalent transformations under the same or similar concept.

[0111] In addition, the articles "a" and "an" as used in this specification and the appended claims should generally be construed to mean "one" or "one or more" unless specified otherwise or clear from context to be directed to a singular form.

[0112] It should also be understood that all modules in the above described device can be implemented in various ways. These modules can be implemented as hardware, software, or a combination thereof. In addition, any module in these modules can be further divided into submodules or combined together functionally.

[0113] Processors have been described in conjunction with various devices and methods. These processors can be implemented using electronic hardware, computer software or any combination thereof. Whether these processors are implemented as hardware or software will depend on specific application and the overall design constraints imposed on the system. As an example, the processor provided in the present disclosure, any part of the processor or any combination of processors can be implemented as a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic, a discrete hardware circuit, and other suitable processing components configured to perform the various functions described in the present disclosure. The function of the processor provided in the present disclosure, any part of the processor or any combination of processors can be implemented as software executed by a microprocessor, a microcontroller, a DSP or other suitable platforms.

[0114] Software should be broadly considered to represent instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, running threads, processes, functions, etc. Software can reside in a computer-readable medium. A computer-readable medium can include, for example, a memory, which can be, for example, a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic stripe), an optical disk, a smart card, a flash memory device, a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, or a removable disk. Although the memory is shown as being separated from the processor in the various aspects provided in the present disclosure, the memory can also be located inside the processor (e.g., a cache or a register).

[0115] The above description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects are apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein. All structural and functional equivalents of the elements of the various aspects described in this disclosure that are known or to be known to those skilled in the art will be covered by the claims.

Claims

1. A method for deploying a target cloud service platform, including: obtaining configuration information for the target cloud service platform; establishing a bootstrapping infrastructure in a public cloud service platform based on the configuration information, the bootstrapping infrastructure providing a set of core services associated with the target cloud service platform; and creating a target service set in the target cloud service platform based on the set of core services.

2. The method according to claim 1, further including: establishing a configuration storage area in the public cloud service platform for storing the configuration information, wherein obtaining the configuration information includes obtaining the configuration information from the configuration storage area.

3. The method according to claim 1, wherein the configuration information includes build artifacts for the target cloud service platform.

4. The method according to claim 1, wherein the core services in the set of core services are generated at least by using seed servers in the bootstrapping infrastructure; or the core services in the set of core services are copied from the public cloud service platform based on the configuration information.

5. The method according to claim 1, wherein creating a target service set in the target cloud service platform based on the set of core services includes: migrating the core services in the set of core services from the bootstrapping infrastructure to the target cloud service platform.

6. The method according to claim 5, wherein creating a target service set in the target cloud service platform based on the set of core services further includes: expanding the migrated core services into the target service set in the target cloud service platform according to a product service list associated with the target cloud service platform.

7. The method according to claim 1, wherein creating a target service set in the target cloud service platform based on the set of core services includes: creating at least one target service among the multiple target services by using existing services in the public cloud service platform based on the dependency relationships among the multiple target services in the target service set.

8. The method according to claim 1, wherein establishing the bootstrapping infrastructure includes: creating at least one core service among the multiple core services by using existing services in the public cloud service platform based on the dependency relationships among the multiple core services in the set of core services.

9. The method according to claim 1, wherein the target cloud service platform includes a cloud service platform isolated from the public cloud service platform, and the method further includes: after the target service set is created, disconnecting the network connection between the bootstrapping infrastructure and the target cloud service platform or imposing access restrictions on the network connection.

10. The method according to claim 1, further including: updating the core services in the set of core services provided by the bootstrapping infrastructure to meet service consistency requirements.

11. The method according to claim 1, further including: Create an identity manager associated with the target cloud service platform in the bootstrapping infrastructure, where the created identity manager is separated from the existing identity manager in the public cloud service platform.

12. The method according to claim 1, wherein, the core service set includes at least one of a monitoring service and a recording service for the deployment of the target cloud service platform.

13. A cloud service system, comprising a public cloud service platform and a target cloud service platform, wherein, the public cloud service platform includes a configuration storage area, a workflow engine, and a bootstrapping infrastructure, where the configuration storage area is used to store configuration information for the target cloud service platform; the workflow engine is used to obtain the configuration information from the configuration storage area and establish the bootstrapping infrastructure based on the configuration information; the bootstrapping infrastructure is used to provide a core service set associated with the target cloud service platform; and the workflow engine is further used to create a target service set in the target cloud service platform based on the core service set, and the target cloud service platform is used to provide the target service set.

14. The cloud service system according to claim 13, wherein, the configuration information includes build artifacts for the target cloud service platform.

15. The cloud service system according to claim 13, wherein, the bootstrapping infrastructure includes a seed server, and the core services in the core service set are at least generated using the seed server; or the core services in the core service set are copied by the workflow engine from the public cloud service platform based on the configuration information.

16. The cloud service system according to claim 13, wherein, the workflow engine is further used to create a target service set by: migrating the core services in the core service set from the bootstrapping infrastructure to the target cloud service platform.

17. The cloud service system according to claim 16, wherein, the workflow engine is further used to create a target service set by: expanding the migrated core services into the target service set in the target cloud service platform according to a product service list associated with the target cloud service platform.

18. The cloud service system according to claim 13, wherein, the target cloud service platform includes a cloud service platform isolated from the public cloud service platform, and the workflow engine is further used to: after the target service set is created, disconnect the network connection between the bootstrapping infrastructure and the target cloud service platform or impose access restrictions on the network connection.

19. An apparatus for deploying a target cloud service platform, comprising: at least one processor; and a memory storing computer-executable instructions that, when executed, cause the at least one processor to: obtain configuration information for a target cloud service platform, Establish a bootstrapping infrastructure in a public cloud service platform based on the configuration information, where the bootstrapping infrastructure provides a core service set associated with the target cloud service platform, and Create a target service set in the target cloud service platform based on the core service set.

20. A non-transitory computer-readable medium comprising instructions that, when executed, cause at least one processor to:[[]] Obtain configuration information for a target cloud service platform; Establish a bootstrapping infrastructure in a public cloud service platform based on the configuration information, where the bootstrapping infrastructure provides a core service set associated with the target cloud service platform; and Create a target service set in the target cloud service platform based on the core service set.

Images