Delivery method, device and equipment of proprietary cloud product and storage medium

Abstract

The application discloses a delivery method and device of a special cloud product, equipment and a storage medium, and relates to the technical field of clouds. The method comprises the following steps: according to function information of the special cloud product, the special cloud product is divided into a plurality of product components which can be independently deployed; product information of the special cloud product and parameter information of the plurality of product components are acquired; a delivery scheme is determined according to the product information and the parameter information, and pre-stored configuration information and product component original declaration; and the plurality of product components are deployed according to the delivery scheme. According to the application, the special cloud product is divided into product components which are relatively independent in deployment, and the plurality of product components are deployed according to a delivery scheme determined based on the product information of the special cloud product and the parameter information of the plurality of product components. The delivery process utilizes a systematic method to realize the deployment of the cloud product, and is free from the dependence on R&D personnel, so that the delivery cycle is greatly shortened, and the problem that the labor cost and the time cost are too high in the delivery of the special cloud product is solved.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the cloud technology field, and particularly relate to a delivery method, device and storage medium of a proprietary cloud product. BACKGROUND

[0002] The proprietary cloud product is a large software and hardware system. From the beginning of implementation to the completion of delivery, the process not only lasts for a long time, but also requires a large number of R&D technical personnel to follow up the deployment of the related product in addition to the delivery technical personnel responsible for the implementation. Therefore, a large amount of human and time costs are consumed in each delivery process. SUMMARY

[0003] Embodiments of the present application provide a delivery method, device and storage medium of a proprietary cloud product, which can solve the problem of high human and time costs in the delivery process of the proprietary cloud product. The technical solution is as follows:

[0004] In one aspect, a delivery method of a proprietary cloud product is provided, and the method comprises:

[0005] According to the function information of the proprietary cloud product, the proprietary cloud product is divided into a plurality of product components that can be independently deployed;

[0006] Obtaining product information of the proprietary cloud product and parameter information of a plurality of product components;

[0007] According to the product information and the parameter information, and pre-stored configuration information and product component original declaration, a delivery scheme is determined;

[0008] According to the delivery scheme, a plurality of product components are deployed to realize the delivery of the proprietary cloud product.

[0009] In one possible implementation, the determination of the delivery scheme according to the product information and the parameter information, and the pre-stored configuration information and product component original declaration comprises:

[0010] According to the product information and the pre-stored configuration information, dependency information between a plurality of product components is determined;

[0011] According to the parameter information and the pre-stored product component original declaration, deployment information of each product component is determined;

[0012] According to the deployment information of each product component and the dependency information between a plurality of product components, the delivery scheme is constructed.

[0013] In another possible implementation, the deployment of a plurality of product components according to the delivery scheme comprises:

[0014] analyzing the delivery scheme to obtain deployment information of each product component and dependency information among the product components;

[0015] deploying the product components according to the deployment information of each product component and the dependency information among the product components.

[0016] In yet another possible implementation, the deploying the product components according to the deployment information of each product component and the dependency information among the product components comprises:

[0017] distributing a corresponding product component to a corresponding deployment node according to the deployment information of each product component;

[0018] determining a deployment sequence of the product components according to the dependency information among the product components;

[0019] when receiving an operation instruction input by a user, remotely controlling each deployment node to deploy a corresponding product component according to the deployment sequence of the product components.

[0020] In yet another possible implementation, the obtaining the parameter information of the product components comprises:

[0021] obtaining the parameter information of each product component according to each product component, a pre-stored product component list and a standardized product component library.

[0022] In yet another possible implementation, the delivery method further comprises:

[0023] receiving feedback information sent by each deployment node corresponding to each product component, the feedback information comprising a deployment result of each product component;

[0024] when the feedback information is a result of a deployment failure of a target product component, repairing the target product component and re-deploying the target product component according to the delivery scheme, wherein the target product component is one of the product components.

[0025] In yet another possible implementation, the parameter information of the product components comprises at least one of service information exposed by a current product component, a computing resource relied on by the current product component, a deployment form of the current product component and a service of another product component relied on by the current product component.

[0026] On the other hand, a delivery device of a proprietary cloud product is provided, and the device comprises:

[0027] The division module is configured to divide the special cloud product into a plurality of product components that can be independently deployed according to function information of the special cloud product.

[0028] The acquisition module is configured to acquire product information of the special cloud product and parameter information of the plurality of product components.

[0029] The processing module is configured to determine a delivery scheme according to the product information and the parameter information, and pre-stored configuration information and product component original declaration.

[0030] The deployment module is configured to deploy the plurality of product components according to the delivery scheme to realize delivery of the special cloud product.

[0031] In one possible implementation, the processing module is specifically configured to:

[0032] determine dependency information between the plurality of product components according to the product information and the pre-stored configuration information; determine deployment information of each product component according to the parameter information and the pre-stored product component original declaration; and construct the delivery scheme according to the deployment information of each product component and the dependency information between the plurality of product components.

[0033] In another possible implementation, the deployment module is specifically configured to:

[0034] parse the delivery scheme to obtain the deployment information of each product component and the dependency information between the plurality of product components; and deploy the plurality of product components according to the deployment information of each product component and the dependency information between the plurality of product components.

[0035] In yet another possible implementation, the deployment module is specifically configured to:

[0036] distribute the corresponding product component to the corresponding deployment node according to the deployment information of each product component; determine a deployment sequence of the plurality of product components according to the dependency information between the plurality of product components; and remotely control each deployment node to deploy the corresponding product component according to the deployment sequence of the plurality of product components when an operation instruction input by a user is received.

[0037] In yet another possible implementation, the acquisition module is specifically configured to acquire the parameter information of each product component according to each product component and a pre-stored standardized product component library.

[0038] In yet another possible implementation, the delivery apparatus further includes:

[0039] receive feedback information sent by each of the deployment nodes corresponding to each of the product components, the feedback information comprising a deployment result of each of the product components;

[0040] The processing module is further configured to repair a target product component when the feedback information indicates a failure of the target product component, the target product component being one of the product components.

[0041] The deployment module is further configured to deploy the target product component according to the delivery scheme again.

[0042] In yet another possible implementation, the parameter information of the product component comprises at least one of service information exposed by a current product component, a computing resource relied on by the current product component, a deployment form of the current product component, and a service of another product component relied on by the current product component.

[0043] In another aspect, an electronic device is provided, the device comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, a code set or instruction set, the at least one instruction, the at least one program, the code set or instruction set being loaded and executed by the processor to implement the method for delivering a private cloud product as described above.

[0044] In another aspect, a computer-readable storage medium is provided, the storage medium having stored therein at least one instruction, at least one program, a code set or instruction set, the at least one instruction, the at least one program, the code set or instruction set being loaded and executed by the processor to implement the method for delivering a private cloud product as described above.

[0045] In another aspect, a computer program product is provided, which, when running on a computer, causes the computer to perform the method for delivering a private cloud product as described above.

[0046] The technical scheme provided by the embodiments of the present application has at least the following beneficial effects:

[0047] By dividing a private cloud product into product components that are relatively independent in terms of functions and deployment, and deploying the product components based on product information of the private cloud product and parameter information of the product components, and a pre-stored delivery scheme determined according to original declarations of the product components, the deployment process of the cloud product is implemented using a systematic method in the entire delivery process, which eliminates the dependence on cloud product R&D personnel, greatly shortens the delivery cycle, and also supports multiple cloud product delivery projects to be implemented in parallel. The delivery scheme is formulated without relying on manpower and experience, thereby solving the problem of high labor cost and time cost in the process of delivering a private cloud product. BRIEF DESCRIPTION OF DRAWINGS

[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0049] Figure 1 It is a process diagram for the delivery and implementation of proprietary cloud products in related technologies;

[0050] Figure 2 A schematic flow chart showing a method for delivering a proprietary cloud product according to an exemplary embodiment of the present application is shown;

[0051] Figure 3 A process diagram illustrating the implementation of a proprietary cloud product delivery provided by an exemplary embodiment of the present application is shown;

[0052] Figure 4 A process diagram of formulating a delivery plan provided by an exemplary embodiment of the present application is shown;

[0053] Figure 5 A schematic flow chart of deploying product components provided by an exemplary embodiment of the present application is shown;

[0054] Figure 6 A schematic structural diagram of a delivery device for a proprietary cloud product provided by an exemplary embodiment is shown;

[0055] Figure 7 A schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION

[0056] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0057] In order to make the purpose, features, and advantages of the invention of this application more obvious and easy to understand, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of this application.

[0058] Embodiments of the present application are described below in detail with reference to the accompanying drawings, examples of which are shown in the drawings, wherein the same or similar notations used throughout the drawings represent the same or similar elements or elements having the same or similar functions. The embodiments described below through reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as a limitation on the present application.

[0059] Those skilled in the art can understand that, unless specifically stated, the singular forms "a", "an" and "the" used herein also include the plural forms. It should be further understood that the phrase "comprising" used in the specification of the present application means that the features, integers, steps, operations, elements and / or components exist, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. It should be understood that when we say that an element is "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, or there can be intermediate elements. In addition, "connected" or "coupled" used herein can include wireless connection or wireless coupling. The phrase "and / or" used herein includes all or any single unit and all combinations of the associated listed items.

[0060] In order to better understand and illustrate the scheme of the embodiments of the present application, some technical terms involved in the embodiments of the present application are simply explained as follows:

[0061] Private cloud: a cloud system deployed in a customer's room environment, with the characteristics of autonomous control, data privacy, and security compliance.

[0062] Cloud solution: a private cloud system that can meet customer's customized needs, including functional requirements, security requirements, performance requirements, and operation and maintenance requirements.

[0063] Product component: a module unit with moderate granularity and independent deployment obtained by dividing a software product.

[0064] Delivery scheme: dependency information and deployment information of each cloud product of the cloud solution. The dependency information and deployment information of each cloud product include: deployment information of each cloud product and dependency information between each cloud product, and dependency information between each product component of each cloud product and deployment information of each product component.

[0065] Delivery engine: a program for automatically deploying a software product.

[0066] Deployment machine: a machine for performing deployment tasks, usually a linux operating system, with large disk space and network intercommunication with each machine in the room.

[0067] Cloud technology: the general term of network technology, information technology, integration technology, management platform technology, application technology and other technologies based on cloud computing business model application, which can form a resource pool, use on demand, flexible and convenient. Cloud computing technology will become an important support. The background service of the technical network system needs a large amount of computing and storage resources, such as video websites, picture websites and more portals. With the high development and application of the Internet industry, every item may have its own identification mark in the future, and it needs to be transmitted to the background system for logical processing. Different levels of data will be processed separately, and various industry data will need strong system support, which can only be realized through cloud computing.

[0068] Cloud computing: refers to the delivery and use mode of IT infrastructure, which refers to obtaining the required resources in a scalable manner through the network; broad sense of cloud computing refers to the delivery and use mode of service, which refers to obtaining the required service in a scalable manner through the network. This service can be IT and software, Internet related, or other services. Cloud computing is the product of the development and integration of grid computing, distributed computing, parallel computing, utility computing, network storage technologies, virtualization, load balancing and other traditional computer and network technologies.

[0069] Regarding the delivery of cloud products, the prior art scheme as shown in Figure 1 , a dedicated delivery technical personnel and a development technical personnel are used to cooperate, according to the planning scheme of the architect, referring to the deployment manual of the cloud product, and gradually completing the software deployment. Therefore, from the beginning of the implementation to the completion of the delivery, it lasts for 6 weeks or even longer. Moreover, in addition to the delivery technical personnel responsible for the implementation, a large number of development technical personnel are needed to support, and the corresponding development technical personnel are needed to follow up according to the deployment product. A cloud product delivery needs hundreds of development technical personnel to participate, this mode is not sustainable, the cost is too high, and the development manpower is limited, and there is no way to support more cloud product delivery projects at the same time.

[0070] Therefore, in order to solve the above technical problems, the embodiment of the present application provides a delivery method of a special cloud product. The method divides the special cloud product into product components which are independent in function and deployment, and deploys the product components based on product information of the special cloud product and parameter information of the product components, as well as pre-stored configuration information and a delivery scheme determined by original declaration of the product components. The deployment process of the cloud product is realized by using a systematic method in the whole delivery process, which breaks the dependence on the cloud product R&D technical personnel, greatly shortens the delivery cycle, and can also support multiple cloud product delivery projects to be implemented in parallel. The delivery scheme is formulated without relying on manpower and experience, thereby solving the problem of high labor cost and time cost in the delivery process of the special cloud product.

[0071] The technical solutions of the present application and how the technical solutions solve the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes can not be described again in some embodiments. The embodiments of the present application will be described below with reference to the drawings.

[0072] Figure 2 is a schematic flow chart of a delivery method 100 of a special cloud product provided by an exemplary embodiment of the present application. As shown in the figure, the delivery method 100 comprises: Figure 2

[0073] 101. According to the function information of the special cloud product, the special cloud product is divided into multiple product components which can be independently deployed.

[0074] 102. Obtain product information of the special cloud product and parameter information of the multiple product components.

[0075] Specifically, in this embodiment, the parameter information of each product component can be obtained according to each product component and a pre-stored standardized product component library.

[0076] That is, the pre-stored standardized product component library includes parameter information of multiple product components, wherein the parameter information of the product component includes at least one of service information exposed by the current product component, computing resources relied on by the current product component, deployment form of the current product component and services of other product components relied on by the current product component. The parameter information corresponding to each product component is found from the pre-stored standardized product component library according to each product component, so as to realize the standardization of each product component, abstract the delivery process of each cloud product into a general standard, and thus reduce the technical threshold of delivery and deployment. The product components can be presented in the form of a list.

[0077] In addition, in this embodiment, the product information of the corresponding special cloud product can be obtained based on the project information provided by the user. For example, the number, type and the like of the special cloud product.​

[0078] 103. determining a delivery scheme according to the product information and the parameter information, and pre-stored configuration information and product component original declaration.

[0079] Specifically, in this embodiment, the configuration information includes configuration relationships between a plurality of product components corresponding to each proprietary cloud product. The product component original declaration refers to parameter information of each product component and original declaration of relationships between the product components.

[0080] 104. deploying the plurality of product components according to the delivery scheme to implement delivery of the proprietary cloud product.

[0081] In one embodiment, 103 can include:

[0082] 1031. determining dependency information between the plurality of product components according to product information of the proprietary cloud product and pre-stored configuration information.

[0083] 1032. determining deployment information of each product component according to parameter information of each product component and pre-stored product component original declaration.

[0084] 1033. constructing the delivery scheme according to the deployment information of each product component and the dependency information between the plurality of product components.

[0085] Specifically, in this embodiment, the deployment information of the product component includes but is not limited to a machine ip on which the current product component is deployed and deployment parameters. The dependency information between the product components includes but is not limited to a service api, an ip, a port number, and a protocol. The delivery scheme constructed in this application is structured data, which can be expressed using json, csv, or xml, so as to facilitate computer reading and recognition, implement systematic support, and make the deployment process not rely on a large number of R&D personnel.

[0086] In another embodiment, 104 can include:

[0087] 1041. parsing the delivery scheme to obtain the deployment information of each product component and the dependency information between the plurality of product components.

[0088] 1042. deploying the plurality of product components according to the deployment information of each product component and the dependency information between the plurality of product components.

[0089] In this embodiment, by deploying the plurality of product components according to the deployment information of each product component and the dependency information between the plurality of product components, the accuracy and reliability of the deployment can be ensured.

[0090] Specifically, in this embodiment, 1042 can include:

[0091] According to the deployment information of each product component, the corresponding product component is distributed to the corresponding deployment node.

[0092] According to the dependency information among the plurality of product components, a deployment sequence of the plurality of product components is determined.

[0093] When receiving the operation instruction input by the user, the deployment of the corresponding product component by each deployment node is remotely controlled according to the deployment sequence of the plurality of product components.

[0094] That is, in the embodiment of the present application, the delivery technician can download the delivery engine, the product component package and the delivery scheme on the deployment machine, input the terminal command on the deployment machine, and run the method process of the present application in the background by the payment engine, so as to deploy each cloud product, thereby maximizing the technical threshold of delivering the cloud product, reducing the possible misoperation in the manual deployment process, and improving the efficiency of delivering the cloud solution.

[0095] It should be understood that the product component package herein can be for a plurality of cloud products or one cloud product. If it is one cloud product, the product component package includes a plurality of product components obtained by dividing the cloud product; if it is a plurality of cloud products, the product component package is a collection of a plurality of product component packages, and each product component package in the collection includes a plurality of product components obtained by dividing the corresponding cloud product.

[0096] In another embodiment, the delivery method 100 can further include:

[0097] 105. Receiving feedback information sent by each deployment node corresponding to each product component, the feedback information including the deployment result of each product component.

[0098] 106. When the feedback information is the result of the deployment failure of the target product component, repairing the target product component and re-deploying the target product component according to the delivery scheme, wherein the target product component is one of the plurality of product components.

[0099] In this embodiment, by detecting the deployment result, the successful deployment of each product component can be effectively ensured to ensure the successful delivery of the cloud product.

[0100] In order to better understand the method provided by the embodiments of the present application, the following will be combined with Figures 3 to 5 The technical solutions of the embodiments of the present application are further described.

[0101] As Figure 3The delivery platform shown can carry out the complete delivery process of the private cloud product. The product deployment scheme is obtained based on product options and capacity planning according to customer needs, and the private cloud product is accessed according to the functional characteristics of the private product, the module units that can be independently deployed are divided to form multiple product components, and the product components are standardized, that is, the general standard design of each product component is carried out. The general design should include but is not limited to: clearly stating the service information (API, protocol, port number, etc.) exposed to the outside of the current component, declaring the computing resources (cpu, memory, disk) relied on by the component, declaring the deployment form (container deployment, virtual machine / physical machine deployment, and number) of the component, and declaring which services of which products should be relied on.

[0102] Based on the product deployment scheme and the general standard design of the product component, a delivery scheme is constructed, which saves the deployment information of each cloud product component and the dependency information between the product components. The delivery scheme formed can also be saved as a template. The delivery engine is a set of standardized delivery procedures that can deploy standardized product components according to the delivery scheme. The delivery engine exposes simple commands that are triggered by users (delivery technicians) to execute.

[0103] Therefore, when the delivery of the private cloud product is carried out now, the delivery technician can download the delivery engine, the product component package and the delivery scheme on the deployment machine. By inputting a terminal command on the deployment machine, the method process of the present application is run in the background by the payment engine, and each cloud product can be deployed, thereby maximizing the technical threshold of delivering cloud products, reducing possible misoperations in the manual deployment process, etc., and improving the efficiency of delivering cloud solutions.

[0104] It should be noted that the delivery process of each cloud product in the cloud solution can adopt the method in the above embodiment, so that the delivery of the cloud solution can be realized.

[0105] As Figure 4 The delivery scheme planning service shown has the function of constructing / developing a delivery scheme. The customer project information in the figure is actually the product information of the private cloud product in the present application, such as product type, product quantity, etc.

[0106] For each product component in the product component list, based on the standardized product component library, the parameter information of each product component can be determined, thereby realizing the standardized design of the product component. According to the standardized product component and the original declaration of the product component, the deployment information of each product component is determined, such as the number of machines required to deploy each product component, and then a default scheme is formed. The default scheme can also not be used, but a scheme template is selected based on the deployment information of each product component to generate a corresponding scheme, and the scheme can also be manually adjusted.

[0107] Based on the product information of the proprietary cloud product and the configuration information stored in the configuration service, dependency information between the plurality of product components is obtained, and then based on the adjusted scheme and the dependency information between the plurality of product components, a scheme configuration is constructed, and a final delivery scheme is generated. The delivery scheme can be further saved as a template scheme, which provides convenience for the delivery of subsequent projects with the same cloud product delivery project.

[0108] In the actual application process of the embodiments of the present application, the deployment information of the product components and the dependency information between the product components can also be managed and maintained by the configuration service.

[0109] The delivery engine in the present application has the functions of analyzing the structured delivery scheme, distributing software packages / product component packages, remotely executing, controlling the deployment sequence of components, and concurrently executing deployment tasks. Figure 5 The flowchart shown is the process of deploying standardized product components by the payment engine according to the delivery scheme.

[0110] The first case is the delivery process for a proprietary cloud product.

[0111] The proprietary product is divided into 10 independently deployable product components, and the delivery scheme is determined according to the information (deployment information and dependency information therebetween) of the 10 product components. The process of deploying the 10 product components is as follows: reading the delivery scheme and obtaining the 10 product components, analyzing the delivery scheme to obtain the deployment information of each product component and the dependency information between the 10 product components, distributing the 10 product components to corresponding deployment nodes, determining the deployment sequence of the 10 product components, and remotely controlling each deployment node to deploy the corresponding product component. When a product component is successfully deployed, the next product component is deployed; when a product component fails to be deployed, the deployment process is ended, and the product component is repaired and then deployed again according to the delivery scheme until the 10 product components are successfully deployed.

[0112] The second case is the delivery process for a plurality of proprietary cloud products.

[0113] Each proprietary product is divided into a plurality of independently deployable product components, and the corresponding delivery scheme is determined according to the information (deployment information and dependency information therebetween) of the plurality of product components corresponding to each proprietary cloud product, and a plurality of delivery schemes are obtained. The process of deploying the plurality of cloud products is as follows: for each cloud product, the operation described in the first case is performed until all product components corresponding to the plurality of proprietary cloud products are successfully deployed.

[0114] In summary, the delivery method provided by the embodiments of the present application has at least the following beneficial effects compared with the prior art:

[0115] 1. Greatly reduced human cost: to complete a product deployment of a comparable scale, the prior art method requires the joint participation of delivery technicians and 100+ product development personnel, while the method of the present application can be completed independently by 5-6 delivery technicians;

[0116] 2. Greatly reduced time cost: to complete a product deployment of a medium scale, the prior art method requires more than 6 weeks, while the method of the present application only requires 1-2 weeks;

[0117] 3. The formulation of the delivery scheme no longer depends on manpower and experience, and can achieve systematic support.

[0118] Based on the same inventive concept, the embodiments of the present application also provide a delivery device for a proprietary cloud product. As shown in the structural schematic diagram of the delivery device for the proprietary cloud product, Figure 6 The delivery device 200 for the proprietary cloud product comprises a division module 201, a processing module 202 and a deployment module 203.

[0119] The division module 201 is configured to divide the proprietary cloud product into a plurality of product components that can be independently deployed according to the functional information of the proprietary cloud product.

[0120] The acquisition module 202 is configured to acquire product information of the proprietary cloud product and parameter information of the plurality of product components.

[0121] The processing module 203 is configured to determine a delivery scheme according to the product information and the parameter information of the plurality of product components, and pre-stored configuration information and product component original declaration.

[0122] The deployment module 204 is configured to deploy the plurality of product components according to the delivery scheme to achieve delivery of the proprietary cloud product.

[0123] Specifically, in this embodiment, the acquisition module 202 acquires the parameter information of each product component according to each product component and a pre-stored standardized product component library.

[0124] Specifically, in this embodiment, the parameter information of the product component includes at least one of service information exposed by the current product component, computing resources relied on by the current product component, a deployment form of the current product component and services of other product components relied on by the current product component.

[0125] In one embodiment, the processing module 203 is specifically configured to:

[0126] According to the product information of the private cloud product and the pre-stored configuration information, dependency information between the plurality of product components is determined. According to the parameter information of each product component and the pre-stored product component original declaration, deployment information of each product component is determined. According to the deployment information of each product component and the dependency information between the plurality of product components, a delivery scheme is constructed.

[0127] In another embodiment, the deployment module 204 is specifically configured to:

[0128] The delivery scheme is parsed to obtain the deployment information of each product component and the dependency information between the plurality of product components. According to the deployment information of each product component and the dependency information between the plurality of product components, the plurality of product components are deployed.

[0129] Specifically, in this embodiment, the deployment module 204 is configured to distribute the corresponding product component to the corresponding deployment node according to the deployment information of each product component. According to the dependency information between the plurality of product components, a deployment sequence of the plurality of product components is determined. When receiving an operation instruction input by a user, the deployment of the corresponding product component by each deployment node is remotely controlled according to the deployment sequence of the plurality of product components.

[0130] In another embodiment, as shown in Figure 6 The delivery apparatus 200 can further include a receiving module 205. In this embodiment,

[0131] The receiving module 205 is configured to receive feedback information sent by the deployment node corresponding to each product component, the feedback information including a deployment result of each product component.

[0132] The processing module 203 is further configured to, when the feedback information is a result of a deployment failure of a target product component, repair the target product component, wherein the target product component is one of the plurality of product components.

[0133] The deployment module 204 is further configured to re-deploy the target product component according to the delivery scheme.

[0134] The delivery apparatus for the private cloud product provided by the embodiments of the present application does not include the contents not described in detail, which can refer to the delivery method for the private cloud product provided by the above-mentioned embodiments. The delivery apparatus for the private cloud product provided by the embodiments of the present application can achieve the same beneficial effects as the delivery method for the private cloud product provided by the above-mentioned embodiments, which will not be described here again.

[0135] The application has at least the following beneficial effects: the proprietary cloud product is divided into functional and deployment relatively independent product components, and the product components are deployed based on product information of the proprietary cloud product and parameter information of the product components, and pre-stored configuration information and a delivery scheme determined by original declaration of the product components. The deployment process of the cloud product is realized by using a systematic method in the entire delivery process, the dependence on cloud product R&D technical personnel is eliminated, the delivery cycle is greatly shortened, and multiple cloud product delivery projects can be supported to be landed in parallel. The delivery scheme does not need to rely on manpower and experience in the formulation process, thereby solving the problem of high labor cost and time cost in the delivery process of the proprietary cloud product.

[0136] Based on the same inventive concept, the embodiment of the application further provides an electronic device, a structural schematic diagram of which is shown in Figure 7 The electronic device 300 includes at least one processor 301, a memory 302 and a bus 303, the at least one processor 301 is electrically connected with the memory 302; the memory 302 is configured to store at least one computer executable instruction, and the processor 301 is configured to execute the at least one computer executable instruction, so as to execute the steps of the delivery method of the proprietary cloud product provided in any one of the embodiments or any one of the optional implementation manners of the embodiment one.

[0137] Further, the processor 301 can be an FPGA (Field-Programmable Gate Array, field programmable gate array) or other devices with logic processing capability, such as an MCU (Microcontroller Unit, microcontroller unit) or a CPU (Central Process Unit, central processing unit).

[0138] Based on the same inventive concept, the embodiment of the application further provides a computer readable storage medium, and the storage medium stores at least one instruction, at least one program, a code set or an instruction set. The at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement the proprietary cloud product delivery method provided in the above method embodiment.

[0139] The computer readable storage medium provided by the embodiments of the present application includes, but is not limited to, any type of disk (including floppy disks, hard disks, optical disks, CD-ROMs, and magneto-optical disks), ROM (Read-Only Memory), RAM (Random Access Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, magnetic cards or optical cards. That is, the readable storage medium includes any medium that stores or transmits information in a form that can be read by a device (for example, a computer).

[0140] The present application also provides a computer program product, which, when running on an electronic device, causes the electronic device to perform the exclusive cloud product delivery method of each method embodiment described above.

[0141] Those skilled in the art can understand that all or part of the steps of the above-mentioned embodiments can be completed by hardware, or by program to instruct related hardware to complete, and the program can be stored in a computer readable storage medium.

[0142] Those skilled in the art can understand that each block in the structural diagram and / or block diagram and / or flowchart and the combination of the blocks in the structural diagram and / or block diagram and / or flowchart can be implemented by computer program instructions. Those skilled in the art can understand that these computer program instructions can be provided to a general-purpose computer, a special-purpose computer, or a processor of other programmable data processing method to implement, so as to execute the scheme specified in the block or blocks of the structural diagram and / or block diagram and / or flowchart disclosed in the present application by the computer or the processor of other programmable data processing method.

[0143] Those skilled in the art can understand that the steps, measures, and schemes in the various operations, methods, and processes discussed in the present application can be alternated, changed, combined, or deleted. Further, other steps, measures, and schemes in the various operations, methods, and processes discussed in the present application can also be alternated, changed, rearranged, decomposed, combined, or deleted. Further, the steps, measures, and schemes in the various operations, methods, and processes in the prior art can also be alternated, changed, rearranged, decomposed, combined, or deleted.

[0144] The above are only preferred embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A method for delivering a proprietary cloud product, characterized in that: The method comprises: Divide the proprietary cloud product into multiple independently deployable product components based on its functional information; Obtain product information of the proprietary cloud product and parameter information of multiple product components; Determining dependency information between a plurality of the product components based on the product information and pre-stored configuration information; Determining deployment information of each of the product components based on the parameter information and pre-stored original declarations of the product components; Determining a delivery plan based on the deployment information of each of the product components and the dependency information between the plurality of the product components; According to the delivery plan, the corresponding product components are distributed to the corresponding deployment nodes, and each deployment node is controlled to deploy multiple product components in sequence to achieve the delivery of the proprietary cloud product.

2. The method for delivering a proprietary cloud product according to claim 1, wherein: Distributing corresponding product components to corresponding deployment nodes according to the delivery plan, and controlling each deployment node to sequentially deploy multiple product components, including: Parsing the delivery solution to obtain deployment information of each product component and dependency information between multiple product components; According to the deployment information of each product component and the dependency information between the multiple product components, the corresponding product components are distributed to the corresponding deployment nodes, and each deployment node is controlled to deploy the multiple product components in sequence.

3. The method for delivering a proprietary cloud product according to claim 2, wherein: The step of distributing the corresponding product components to corresponding deployment nodes based on the deployment information of each product component and the dependency information between the multiple product components, and controlling each deployment node to sequentially deploy the multiple product components, includes: Distributing the corresponding product components to corresponding deployment nodes according to the deployment information of each product component; Determining a deployment order of the plurality of product components based on dependency information between the plurality of product components; When an operation instruction input by the user is received, each deployment node is remotely controlled to deploy the corresponding product components according to the deployment order of the multiple product components.

4. The method for delivering a proprietary cloud product according to any one of claims 1 to 3, characterized in that: Obtain parameter information of multiple product components, including: According to each of the product components and a pre-stored standardized product component library, parameter information of each of the product components is obtained.

5. The method for delivering a proprietary cloud product according to any one of claims 1 to 3, characterized in that: Said delivery methods also include: receiving feedback information sent by a deployment node corresponding to each of the product components, the feedback information including a deployment result of each of the product components; When the feedback information is a result of a target product component deployment failure, the target product component is repaired and redeployed according to the delivery plan, wherein the target product component is one of the multiple product components.

6. The method for delivering a proprietary cloud product according to any one of claims 1 to 3, characterized in that: The parameter information of the product component includes: service information exposed by the current product component, computing resources that the current product component depends on, deployment form of the current product component and at least one of services of other product components on which it depends.

7. A delivery device for a proprietary cloud product, characterized in that: The device comprises: A partitioning module, configured to partition the proprietary cloud product into a plurality of independently deployable product components based on functional information of the proprietary cloud product; An acquisition module, configured to acquire product information of the proprietary cloud product and parameter information of a plurality of product components; a processing module configured to determine dependency information between the plurality of product components based on the product information and pre-stored configuration information; determine deployment information for each of the product components based on the parameter information and pre-stored original declarations of the product components; and determine a delivery plan based on the deployment information for each of the product components and the dependency information between the plurality of product components; The deployment module is used to distribute the corresponding product components to the corresponding deployment nodes according to the delivery plan, and control each deployment node to deploy multiple product components in sequence to achieve the delivery of the proprietary cloud product.

8. The delivery device for a proprietary cloud product according to claim 7, characterized in that: The deployment module is specifically used to: Parsing the delivery solution to obtain deployment information of each product component and dependency information between multiple product components; According to the deployment information of each product component and the dependency information between the multiple product components, the corresponding product components are distributed to the corresponding deployment nodes, and each deployment node is controlled to deploy the multiple product components in sequence.

9. The delivery device for a proprietary cloud product according to claim 8, characterized in that: The deployment module is specifically used to: Distributing the corresponding product components to corresponding deployment nodes according to the deployment information of each product component; Determining a deployment order of the plurality of product components based on dependency information between the plurality of product components; When an operation instruction input by the user is received, each deployment node is remotely controlled to deploy the corresponding product components according to the deployment order of the multiple product components.

10. The delivery device of a proprietary cloud product according to any one of claims 7 to 9, characterized in that: The acquisition module is specifically used to: According to each of the product components and a pre-stored standardized product component library, parameter information of each of the product components is obtained.

11. The delivery device for a proprietary cloud product according to any one of claims 7 to 9, characterized in that: The delivery device further comprises: A receiving module, configured to receive feedback information sent by a deployment node corresponding to each of the product components, wherein the feedback information includes a deployment result of each of the product components; The processing module is further configured to repair the target product component and redeploy the target product component according to the delivery plan when the feedback information is a result of a target product component deployment failure, wherein the target product component is one of the multiple product components.

12. The delivery device for a proprietary cloud product according to any one of claims 7 to 9, characterized in that: The parameter information of the product component includes: service information exposed by the current product component, computing resources that the current product component depends on, deployment form of the current product component and at least one of services of other product components on which it depends.

13. An electronic device, characterized in that: The electronic device includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set, or an instruction set, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the delivery method of the proprietary cloud product according to any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that The storage medium stores at least one instruction, at least one program, a code set, or an instruction set, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the delivery method of the proprietary cloud product according to any one of claims 1 to 6.

Images