Deployment control method and device, equipment and storage medium

Abstract

The invention provides a deployment control method and device, equipment and a storage medium. The method comprises the following steps: acquiring deployment demand information; according to the deployment demand information, a first micro-service is determined, and the first micro-service has related first configuration information; acquiring second configuration information related to the second micro-service according to the first configuration information; according to the first configuration information and the second configuration information, an automatic deployment script is generated, and the automatic deployment script is used for deploying the first micro-service and the second micro-service. Through the method and the device, the configuration information of different micro-services involved in the deployment process can be supported to be associated and identified, so that the deployment efficiency and accuracy are effectively improved.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular, to a deployment control method, apparatus, device, and storage medium. Background Art

[0002] When deploying to a local system, the commonly used deployment method is that front-end personnel first sort out user deployment requirements, and then back-end personnel sort out the microservices of each subsystem according to the user deployment requirements, generate a deployment configuration form, and obtain relevant microservice sets from the application service platform according to the configuration information in the deployment configuration form, and deploy them on the user side manually or by generating an automated script. After successful deployment, the deployment configuration form will be stored in the local database and corresponding to the user deployment requirements.

[0003] In the related art, it does not support the associated identification of the configuration information of different microservices involved in the deployment process, resulting in low deployment efficiency and low accuracy. Summary of the Invention

[0004] The present disclosure aims to at least solve one of the technical problems in the related art to some extent.

[0005] To this end, the present disclosure provides a deployment control method, a deployment control apparatus, a communication device, a non-transitory computer-readable storage medium storing computer instructions, and a computer program product, which can support the associated identification of the configuration information of different microservices involved in the deployment process, thereby effectively improving the deployment efficiency and accuracy.

[0006] The deployment control method proposed in the first aspect embodiment of the present disclosure includes: obtaining deployment requirement information; determining a first microservice according to the deployment requirement information, where the first microservice has relevant first configuration information; obtaining second configuration information related to a second microservice according to the first configuration information; generating an automated deployment script according to the first configuration information and the second configuration information, where the automated deployment script is used to deploy the first microservice and the second microservice.

[0007] The deployment control apparatus proposed in the second aspect embodiment of the present disclosure includes: a first obtaining module, configured to obtain deployment requirement information; a determining module, configured to determine a first microservice according to the deployment requirement information, where the first microservice has relevant first configuration information; a second obtaining module, configured to obtain second configuration information related to a second microservice according to the first configuration information; and a control module, configured to generate an automated deployment script according to the first configuration information and the second configuration information, where the automated deployment script is used to deploy the first microservice and the second microservice.

[0008] The communication device provided by the third - aspect embodiment of the present disclosure includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the deployment control method proposed by the above - mentioned aspect embodiment of the present disclosure.

[0009] The fourth - aspect embodiment of the present disclosure proposes a non - transitory computer - readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the deployment control method proposed by the above - mentioned aspect embodiment of the present disclosure.

[0010] The fifth - aspect embodiment of the present disclosure proposes a computer program product. When the instructions in the computer program product are executed by a processor, it performs the steps of the deployment control method proposed by the above - mentioned aspect embodiment of the present disclosure.

[0011] The deployment control method, deployment control device, communication device, non - transitory computer - readable storage medium storing computer instructions, and computer program product proposed by the present disclosure obtain deployment requirement information, and determine a first microservice according to the deployment requirement information. The first microservice has relevant first configuration information. According to the first configuration information, it obtains second configuration information related to a second microservice, and generates an automated deployment script according to the first configuration information and the second configuration information. The automated deployment script is used to deploy the first microservice and the second microservice. It can support the associated recognition of the configuration information of different microservices involved in the deployment process, thereby effectively improving the deployment efficiency and accuracy.

[0012] The additional aspects and advantages of the present disclosure will be partially given in the following description, partially become obvious from the following description, or be understood through the practice of the present disclosure. Description of the Drawings

[0013] The above - mentioned and / or additional aspects and advantages of the present disclosure will become obvious and easy to understand from the following description of the embodiments in conjunction with the drawings, where:

[0014] Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0015] Figure 2 is a schematic flowchart of a deployment control method provided by an embodiment of the present disclosure;

[0016] Figure 3 is a schematic flowchart of another deployment control method provided by an embodiment of the present disclosure;

[0017] Figure 4 is a schematic diagram of a preset relationship network in an embodiment of the present disclosure;

[0018] Figure 5It is a schematic flowchart of another deployment control method provided by an embodiment of the present disclosure;

[0019] Figure 6 It is a schematic flowchart of storing the design state in an embodiment of the present disclosure;

[0020] Figure 7 It is a schematic flowchart of the deployment working state in an embodiment of the present disclosure;

[0021] Figure 8 It is a schematic structural diagram of a deployment control device provided by an embodiment of the present disclosure;

[0022] Figure 9 It shows a block diagram of an exemplary communication device suitable for implementing the embodiments of the present disclosure. Detailed Embodiments

[0023] The embodiments of the present disclosure will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described by referring to the accompanying drawings are exemplary and are only used to explain the present disclosure, and should not be construed as a limitation to the present disclosure. On the contrary, the embodiments of the present disclosure include all changes, modifications, and equivalents falling within the spirit and scope of the appended claims.

[0024] To better understand a deployment control method disclosed by an embodiment of the present disclosure, the communication system applicable to the embodiments of the present disclosure will be described first below.

[0025] Please refer to Figure 1 , Figure 1 which is a schematic architecture diagram of a communication system provided by an embodiment of the present disclosure. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of the devices shown are only for illustration and do not constitute a limitation to the embodiments of the present disclosure. In practical applications, there may include two or more network devices and two or more terminal devices. Figure 1 Taking the communication system including a network device 101 and a terminal device 102 as an example.

[0026] The network device 101 in the embodiments of the present disclosure is an entity for transmitting or receiving signals. The specific technologies and specific device forms adopted by the network device are not limited in the embodiments of the present disclosure.

[0027] The terminal device 102 in the embodiments of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device may also be referred to as a terminal device, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc. The terminal device may be an automobile with communication functions, a smart vehicle, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and so on. The embodiments of the present disclosure do not limit the specific technologies and specific device forms adopted by the terminal device.

[0028] It can be understood that the communication system described in the embodiments of the present disclosure is to more clearly illustrate the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Those of ordinary skill in the art know that with the evolution of the system architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present disclosure are equally applicable to similar technical problems. The deployment control method in the embodiments of the present disclosure can be applied to the above-mentioned network device or terminal device, or can also be applied to any other possible device, and this is not limited. By way of example, it can be applied to deploy and control the service system in the network device, or can also be applied to deploy and control the service system in the terminal device, and this is not limited.

[0029] The deployment control method and its device provided by the present disclosure will be described in detail below with reference to the accompanying drawings. Figure 2 It is a flowchart of a deployment control method provided by an embodiment of the present disclosure. As Figure 2 shown, the method may include but is not limited to the following steps:

[0030] S201: Obtain deployment requirement information.

[0031] Among them, the information used to describe the content of user requirement deployment can be called deployment requirement information. By way of example, the deployment requirement information can be the type of business system for user requirement deployment, the types of microservices involved in the business system, the business functions that the microservices can provide, and other information. In some embodiments, a requirement collection interface can be provided in the deployment control platform. The requirement collection interface can provide an interface for collecting deployment requirement information, and the deployment requirement information can be collected based on this interface; alternatively, a document describing the deployment requirements can also be received, and the deployment requirement information can be automatically parsed from this document; or the deployment requirement information can be obtained based on any other possible method, and no limitation is imposed thereon.

[0032] S202: Determine a first microservice according to the deployment requirement information, where the first microservice has relevant first configuration information.

[0033] Among them, the reference microservice corresponding to the deployment requirement information can be called the first microservice. The number of the first microservices can be one or more. The first configuration information is used to describe the configuration information of the first microservice. The configuration information can be, for example, a microservice execution file, a configuration file, the number of Central Processing Unit (CPU) cores, the memory size, the disk space size, the network specification, etc.

[0034] By way of example, in the deployment working state, the first microservice can be determined according to the deployment requirement information. Specifically, for example, in the deployment working state, when a deployment is initiated, according to the user requirements (an optional example of the deployment requirement information), the microservice nodes corresponding to the requirements (an optional example of the first microservice) are filtered out and used as the starting nodes of the minimized deployment subset. The deployment subset can refer to a set formed by several microservices to be deployed including the first microservice.

[0035] In some embodiments, the identifier of the microservice that meets the requirements can be identified from the deployment requirement information, and the microservice corresponding to the identifier of the microservice can be used as the first microservice. It can also be based on artificial intelligence to automatically parse the deployment requirement information to perform multi-level decomposition of the deployment requirements, and the microservice corresponding to the deployment requirements at the reference level can be used as the first microservice; it can also be based on the deployment requirement information to determine the business function to be realized by the requirements, and the most basic microservice that can realize this business function can be used as the first microservice, and no limitation is imposed thereon.

[0036] In the embodiments of the present disclosure, after determining the first microservice according to the deployment requirement information, the second microservice related to the first microservice and the configuration information of the second microservice can be automatically identified. The configuration information of the second microservice can be called the second configuration information.

[0037] S203: Obtain second configuration information related to the second microservice according to the first configuration information.

[0038] Among them, the number of second microservices can be one or more, and there is no limit to this. The second microservice can be a microservice associated with the first microservice during the deployment process. It can be directly associated or indirectly associated.

[0039] After determining the first configuration information as described above, microservices with an association rule with the first microservice can be determined as the second microservices, and the second configuration information can be obtained according to the identifiers of the second microservices. The second configuration information can be pre-analyzed and stored, and the pre-stored second configuration information can be obtained according to the identifiers of the second microservices; alternatively, the first configuration information can also be analyzed accordingly to determine the second microservices associated with the first microservice during the deployment process and the second configuration information of the second microservices; or it can also be combined with any other possible methods to implement obtaining the second configuration information related to the second microservice according to the first configuration information, such as the method of automated script analysis, software development method, artificial intelligence method, etc., and there is no limit to this.

[0040] S204: Generate an automated deployment script according to the first configuration information and the second configuration information, where the automated deployment script is used to deploy the first microservice and the second microservice.

[0041] After obtaining the first configuration information of the first microservice and the second configuration information related to the second microservice as described above, the first configuration information and the second configuration information can be processed to obtain an automated deployment script. By way of example, the first configuration information and the second configuration information can form a full-scale deployment configuration, and the full-scale deployment configuration can be processed to obtain a full-scale deployment configuration table. The deployment software performs resource allocation and file packaging to obtain an automated deployment script. Then, by executing the automated deployment script, each microservice can be deployed in sequence.

[0042] In this embodiment, by obtaining deployment requirement information and determining the first microservice according to the deployment requirement information, where the first microservice has relevant first configuration information, obtaining second configuration information related to the second microservice according to the first configuration information, and generating an automated deployment script according to the first configuration information and the second configuration information, where the automated deployment script is used to deploy the first microservice and the second microservice. It can support the associated recognition of the configuration information of different microservices involved in the deployment process, thereby effectively improving the deployment efficiency and accuracy.

[0043] Figure 3 It is a schematic flowchart of another deployment control method provided by an embodiment of the present disclosure. As Figure 3 shown, the method may include but is not limited to the following steps:

[0044] S301: Obtain deployment requirement information.

[0045] S302: Determine a first microservice according to the deployment requirement information, where the first microservice has relevant first configuration information.

[0046] For the descriptions of S301 - S302, specific reference may be made to the above - mentioned embodiments, which will not be elaborated here.

[0047] S303: Determine a first node corresponding to the first configuration information from a preset relationship network, where the preset relationship network includes multiple nodes, each node is used to represent corresponding candidate configuration information, and there are edges between at least some of the nodes.

[0048] Among them, the node corresponding to the first configuration information in the preset relationship network can be called the first node. The first node is used to store the first configuration information.

[0049] The preset relationship network in the embodiments of the present disclosure includes multiple nodes. Each node corresponds to a candidate microservice, and each node is used to represent the candidate configuration information of the candidate microservice it corresponds to. There is a microservice dependency relationship between different candidate microservices corresponding to different nodes with edges, and the edges are used to represent the candidate association rules between different candidate microservices with a microservice dependency relationship. Thus, it is possible to model the microservice dependency relationship between different microservices based on the preset relationship network, and pre - store the candidate configuration information of the corresponding microservices based on the microservice dependency relationship, so as to support quickly and accurately identifying the configuration information of different microservices based on the preset relationship network.

[0050] As Figure 4 shown, Figure 4It is a schematic diagram of a preset relationship network in an embodiment of the present disclosure. Among them, each circle represents a node, and there may be connections between different nodes. Each node corresponds to the configuration information of a microservice, and the connection represents the association rule between two microservices. The preset relationship network can be specifically stored based on a directed storage mode, and the specific storage process can be referred to the following embodiments. When storing the deployment configuration, the deployment configuration is disassembled and separately stored in each node of the directed graph. The next-hop node of each node is the configuration information associated with the deployment configuration of the microservice corresponding to this node. The node itself stores the configuration information of the corresponding microservice, and the connection between nodes represents the association rule. The association rule can be an interface call relationship or a service dependency relationship. When a new node or function changes, starting from a reference node, the next-hop nodes of each node can be traversed through the depth-first algorithm or the breadth-first algorithm, and the configuration information corresponding to the next-hop node can be modified according to the association rule on the connection line. After the traversal is completed, a deployment configuration change order can be automatically generated. This process can be completed independently by the automated deployment software without manual participation. It not only ensures efficiency but also ensures correctness.

[0051] S304: Determine a second node that has a connection with the first node from multiple nodes.

[0052] After determining the first node corresponding to the first configuration information from the preset relationship network, a second node that has a connection with the first node can also be determined from multiple nodes. If there is a connection between the first node and the second node, it can indicate that there is a microservice dependency relationship between the first microservice and the second microservice, and the connection represents the association rule between the first microservice and the second microservice.

[0053] In some embodiments, the nodes in the preset relationship network that have a connection with the first node can be used as the second node, and the number of second nodes can be one or more.

[0054] In some embodiments, at least one second node that has a direct connection with the first node can be determined from multiple nodes. Among them, there is a direct microservice dependency relationship between the first microservice of the first node with a direct connection and the second microservice of the second node; and / or, at least one second node that has an indirect connection with the first node can be determined from multiple nodes. Among them, there is an indirect microservice dependency relationship between the first microservice of the first node with an indirect connection and the second microservice of the second node. To support accurately identifying the second configuration information of the second microservice that has a microservice dependency relationship with the first microservice based on the preset relationship network.

[0055] For example, Figure 4As shown in the figure, there is a direct microservice dependency relationship between node "Configuration 1" and node "Configuration 2", and there are indirect microservice dependency relationships between node "Configuration 1" and node "Configuration 3", node "Configuration 4", node "Configuration 5", and node "Configuration 6" respectively. The indirect microservice dependency relationship means that there is no direct edge between two nodes, and there is one or more other nodes between these two nodes.

[0056] S305: Use the candidate configuration information represented by the second node as the second configuration information.

[0057] After identifying one or more second nodes from the preset relationship network as described above, the configuration information stored in each second node can be used as the second configuration information.

[0058] S306: Determine the edge between the first node and the second node from the preset relationship network, and obtain the target association rule between the first microservice and the second microservice represented by the edge.

[0059] In the embodiments of the present disclosure, it is also possible to support determining the target association rule between the first microservice and the second microservice. For example, the candidate association rule stored in the edge between the first node and the second node in the preset relationship network can be used as the target association rule.

[0060] S307: Generate an automated deployment script according to the first configuration information, the second configuration information, and the target association rule, where the automated deployment script is used to deploy the first microservice and the second microservice.

[0061] That is to say, in this embodiment, it is supported to combine the first configuration information, the second configuration information, and the target association rule to generate an automated deployment script, so that the automated deployment script can automatically model and analyze the target association rules between different microservices. Since the target association rule can reflect the microservice dependency relationship between different microservices, the generated automated deployment script can better support the linkage deployment and startup of multiple microservices, improving the system deployment efficiency while enhancing the system deployment effect.

[0062] Figure 5 It is a flowchart of another deployment control method provided by the embodiments of the present disclosure. As Figure 5 shown, the method may include but is not limited to the following steps:

[0063] S501: Determine the benchmark candidate microservices according to the basic business.

[0064] In this embodiment, the construction process of the preset relationship network is shown. It can be to construct the preset relationship network in the storage design state. During the construction of the preset relationship network, the candidate configuration information of each candidate microservice is stored in the corresponding node of the preset relationship network. The candidate microservice can be, for example, any possible microservice required by the business system, and the candidate association rules between different microservices with microservice dependencies are stored in the connecting edges between the corresponding nodes.

[0065] In some embodiments, there can be one or more basic services. The basic service can be the most fundamental service that constitutes any functional business system. The benchmark candidate microservice can be determined with reference to the basic service. The benchmark candidate microservice can be a basic candidate microservice used to form the preset relationship network.

[0066] S502: Determine other candidate microservices that have microservice dependencies with the benchmark candidate microservice.

[0067] After determining the benchmark candidate microservice as described above, taking the benchmark candidate microservice as the benchmark and the other candidate microservices that have microservice dependencies with the benchmark candidate microservice as the extension, the node corresponding to the benchmark candidate microservice can be extended. For example, other nodes can be generated based on the node corresponding to the benchmark candidate microservice, and the connecting edges between at least some of the nodes can be constructed to form the preset relationship network.

[0068] S503: Determine the candidate association rules between the benchmark candidate microservice and other candidate microservices according to the microservice dependencies.

[0069] After determining the benchmark candidate microservice according to the basic service as described above, the candidate association rules between the benchmark candidate microservice and other candidate microservices can also be determined according to the microservice dependencies. The candidate association rules are used to form the connecting edges between at least some of the candidate microservices.

[0070] S504: Map the multiple candidate configuration information corresponding to multiple candidate microservices to the corresponding multiple nodes in the initial relationship network, and generate the connecting edges between the corresponding nodes of the candidate microservices with microservice dependencies according to the candidate association rules to obtain the preset relationship network.

[0071] In the embodiments of the present disclosure, it is also possible to support modifying the preset relationship network. For example, it can be determined the candidate microservice to be added, and the preset relationship network can be updated according to the candidate microservice to be added to obtain the updated preset relationship network. For example, a node corresponding to the candidate microservice to be added can be added to the preset relationship network, and the connecting edges between the candidate microservice to be added and other candidate microservices can be configured.

[0072] In some embodiments, at least one candidate microservice having a microservice dependency relationship with the candidate microservice to be added can be determined from a preset relationship network, a node corresponding to the candidate configuration information of the candidate microservice to be added can be established in the preset relationship network, a candidate association rule between the candidate microservice to be added and the at least one candidate microservice can be determined according to the microservice dependency relationship, and according to the candidate association rule, an edge connecting the nodes corresponding to the candidate microservice to be added and the at least one candidate microservice can be generated to obtain an updated preset relationship network. Thereby, the flexibility of the application of the preset relationship network can be greatly improved to meet the deployment requirements of personalized business systems.

[0073] Exemplarily, referring to the above Figure 4 , the configuration information for deploying each microservice is used as the smallest node unit and stored in multiple nodes of a directed graph (an optional example of the preset relationship network). The arrow represents the association rule between each configuration information (such as interface call relationship, Software Development Kit (SDK) dependency relationship, etc.). There is an association rule between the configuration information connected by the arrow (for example, there is an edge), and there is no direct association rule for those not connected by an arrow (for example, there is no edge). The configuration information at the end of the arrow can change according to the change of the configuration information at the top of the arrow. In addition to indicating the association rule, each arrow also needs to define the association rule. When the configuration information at the top of the arrow changes, the configuration information at the end of the arrow changes accordingly according to the association rule. For nodes where the configuration information affects each other, such as configuration 2 and configuration 6, the association rules between them (rule 5 and rule 6) need to ensure no conflict. When traversing configuration changes, each hop node can also be recorded to ensure that there is no circular traversal. Exemplarily, in the storage design state: determine the microservices corresponding to the basic services and store these microservices (an optional example of the benchmark candidate microservices) as the head nodes. When adding new extended support microservices, while storing them in their own nodes, the association rule can be determined through the microservice dependency relationship between microservices, and this node can be bound to the upper-level node. When the microservice function changes, re-establish the association rule between nodes. If there is a new microservice, it can be inserted in the middle of the directed graph or added to the end of the relationship chain. After completing the design of the entire directed graph, store it in the automated deployment software database. This process can be as Figure 6 shown Figure 6 is the schematic flow diagram of the storage design state in the embodiments of the present disclosure.

[0074] S505: Obtain deployment requirement information.

[0075] S506: Determine a first microservice according to the deployment requirement information, where the first microservice has relevant first configuration information.

[0076] S507: Determine a first node corresponding to the first configuration information from a preset relationship network, where the preset relationship network includes multiple nodes, each node is used to represent a corresponding candidate configuration information, and there are edges between at least some of the nodes.

[0077] S508: Determine a second node that has an edge with the first node from the multiple nodes.

[0078] S509: Use the candidate configuration information represented by the second node as the second configuration information.

[0079] S510: Generate an automated deployment script according to the first configuration information and the second configuration information, where the automated deployment script is used to deploy the first microservice and the second microservice.

[0080] Exemplarily, in the deployment working state: when initiating a deployment, according to user requirements, filter out the microservice nodes corresponding to the requirements as the starting node of the minimized deployment subset. The deployment software starts from the starting point, traverses each associated node in the configuration storage graph according to the breadth-first or depth-first algorithm, and records each node according to the association rules. Generate a full-scale deployment configuration table. After the deployment software performs resource allocation and file packaging, execute the automated deployment script. After success, start each microservice in sequence according to the dependency relationship. When the user requirements change, if a new microservice needs to be added, the foregoing steps are re-executed. If adjustments need to be made to the microservice, modify or remove the relevant microservice according to the adjustment requirements. As Figure 7 shown, Figure 7 is a schematic diagram of the deployment working state process in an embodiment of the present disclosure.

[0081] In this embodiment, by obtaining deployment requirement information and determining a first microservice according to the deployment requirement information, where the first microservice has relevant first configuration information, obtaining second configuration information related to a second microservice according to the first configuration information, and generating an automated deployment script according to the first configuration information and the second configuration information, where the automated deployment script is used to deploy the first microservice and the second microservice. It can support the associated identification of the configuration information of different microservices involved in the deployment process, thereby effectively improving the deployment efficiency and accuracy. By determining a benchmark candidate microservice according to the basic business and determining other candidate microservices that have a microservice dependency relationship with the benchmark candidate microservice, determining a candidate association rule between the benchmark candidate microservice and the other candidate microservices according to the microservice dependency relationship, mapping multiple candidate configuration information corresponding to multiple candidate microservices to multiple corresponding nodes in the initial relationship network, and generating edges between the corresponding nodes of the candidate microservices with microservice dependency relationships according to the candidate association rule, a preset relationship network is obtained. Thus, it realizes modeling the microservice dependency relationship between different microservices based on the preset relationship network, and pre-storing the candidate configuration information of the corresponding microservices based on the microservice dependency relationship to support quickly and accurately identifying the configuration information of different microservices based on the preset relationship network. It can also greatly improve the flexibility of the application of the preset relationship network to meet the deployment requirements of personalized business systems.

[0082] In the embodiment of the present disclosure, a storage scheme for a directed graph (an optional example of the preset relationship network) is proposed. It not only stores deployment configuration information but also stores the association rules between the configuration information. Automatically change the associated configuration items without the need for deployment personnel to participate in the intermediate process, improving the deployment configuration and change efficiency and reducing the probability of deployment configuration errors. Change the integrated deployment configuration list from centralized storage to discrete storage. On this basis, not only store the configuration information but also store the association relationships and association rules between the configuration information, and at the same time support quickly traversing and searching for and modifying all associated configurations through mature software algorithms (depth-first / breadth-first). Enable the deployment software to balance improving the configuration change efficiency and reducing the configuration error rate under complex large-scale business configurations. No manual intervention is required, and the configuration modification closed-loop operation is truly realized.

[0083] Figure 8 It is a schematic structural diagram of a deployment control device provided by an embodiment of the present disclosure.

[0084] As Figure 8 shown, the deployment control device 80 includes:

[0085] A first acquisition module 801, configured to acquire deployment requirement information.

[0086] A determination module 802, configured to determine a first microservice according to deployment requirement information, where the first microservice has relevant first configuration information.

[0087] A second acquisition module 803, configured to acquire second configuration information related to a second microservice according to the first configuration information.

[0088] A control module 804, configured to generate an automated deployment script according to the first configuration information and the second configuration information, where the automated deployment script is used to deploy the first microservice and the second microservice.

[0089] It should be noted that the foregoing explanation of the deployment control method also applies to the deployment control device in this embodiment, and will not be elaborated here.

[0090] In this embodiment, by acquiring deployment requirement information, and determining a first microservice according to the deployment requirement information, where the first microservice has relevant first configuration information, acquiring second configuration information related to a second microservice according to the first configuration information, and generating an automated deployment script according to the first configuration information and the second configuration information, where the automated deployment script is used to deploy the first microservice and the second microservice. It can support the associated identification of the configuration information of different microservices involved in the deployment process, thereby effectively improving the deployment efficiency and accuracy.

[0091] Figure 9 The block diagram of an exemplary communication device suitable for implementing the embodiments of the present disclosure is shown. Figure 9 The shown communication device 12 is only an example, and should not impose any limitation on the functions and usage scope of the embodiments of the present disclosure. As Figure 9 shown, the communication device 12 is presented in the form of a general-purpose computing device. The components of the communication device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 connecting different system components (including the system memory 28 and the processing unit 16).

[0092] Bus 18 represents one or more of several types of bus architectures, including a memory bus or memory controller, a peripheral bus, an Accelerated Graphics Port, a processor bus, or a local bus using any of the various bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnection (PCI) bus.

[0093] Communication device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by communication device 12, including volatile and nonvolatile media, removable and non-removable media.

[0094] Memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and / or cache memory 32. Communication device 12 may further include other removable / non-removable, volatile / nonvolatile computer system storage media. By way of example only, storage system 34 can be used for reading and writing on non-removable, nonvolatile magnetic media ( Figure 9 not shown and typically called a "hard disk drive").

[0095] Although Figure 9 not shown in the figure, a disk drive for reading and writing on a removable nonvolatile disk (such as a "floppy disk") and an optical disk drive for reading and writing on a removable nonvolatile optical disk (such as Compact Disc Read Only Memory (CD-ROM), Digital Video Disc Read Only Memory (DVD-ROM), or other optical media) can be provided. In these cases, each drive can be connected to bus 18 through one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.

[0096] A program / utilities 40 having a set (at least one) of program modules 42 can be stored, for example, in a memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. The program modules 42 generally execute the functions and / or methods in the embodiments described in the present disclosure.

[0097] The communication device 12 can also communicate with one or more external devices 14 (such as a keyboard, a pointing device, a display 24, etc.), and can also communicate with one or more devices that enable a human body to interact with the communication device 12, and / or communicate with any device that enables the communication device 12 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication can be carried out through an input / output (I / O) interface 22. Moreover, the communication device 12 can also communicate with one or more networks (such as a Local Area Network (LAN), a Wide Area Network (WAN), and / or a public network, such as the Internet) through a network adapter 20. As shown in the figure, the network adapter 20 communicates with other modules of the communication device 12 through a bus 18. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination with the communication device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0098] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing the deployment control method mentioned in the foregoing embodiments.

[0099] To implement the above embodiments, the present disclosure also proposes a non-transitory computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the deployment control method proposed in the foregoing embodiments of the present disclosure.

[0100] To implement the above embodiments, the present disclosure also proposes a computer program product. When the instructions in the computer program product are executed by a processor, they execute the deployment control method proposed in the foregoing embodiments of the present disclosure.

[0101] It should be noted that in the description of the present disclosure, the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of the present disclosure, unless otherwise specified, the meaning of "a plurality" is two or more.

[0102] Any process or method description depicted in a flowchart or otherwise described herein can be understood to represent a module, segment, or portion of code that includes one or more executable instructions for implementing a specific logical function or process. The scope of the preferred embodiments of the present disclosure includes additional implementations where functions may be executed not in the order shown or discussed, including in a substantially simultaneous manner according to the involved functions or in a reverse order, which should be understood by those skilled in the art to which the embodiments of the present disclosure pertain.

[0103] It should be understood that various parts of the present disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one or a combination of the following techniques well-known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application-specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0104] Those of ordinary skill in the art of this technology can understand that all or part of the steps carried out in implementing the methods of the above embodiments can be completed by instructing relevant hardware through a program. The said program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0105] In addition, in each of the embodiments of the present disclosure, the functional units can be integrated into one processing module, or each unit can exist physically alone, or two or more units can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0106] The above-mentioned storage medium can be a read-only memory, a magnetic disk, an optical disc, etc.

[0107] In the description of this specification, the description with reference to terms such as "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or more embodiments or examples.

[0108] Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present disclosure.

Claims

1. A deployment control method, characterized in that, the method includes: Obtaining deployment requirement information; According to the deployment requirement information, determining a first microservice, wherein the first microservice has relevant first configuration information; According to the first configuration information, obtaining second configuration information related to a second microservice; According to the first configuration information and the second configuration information, generating an automated deployment script, wherein the automated deployment script is used to deploy the first microservice and the second microservice.

2. The method according to claim 1, characterized in that, the obtaining the second configuration information related to the second microservice according to the first configuration information includes: Determining a first node corresponding to the first configuration information from a preset relationship network, wherein the preset relationship network includes multiple nodes, each node is used to represent corresponding candidate configuration information, and there are edges between at least some of the nodes; Determining a second node having an edge with the first node from the multiple nodes; Taking the candidate configuration information represented by the second node as the second configuration information.

3. The method according to claim 2, characterized in that, Each node corresponds to a candidate microservice, each node is used to represent the candidate configuration information of the candidate microservice it corresponds to, there is a microservice dependency relationship between different candidate microservices corresponding to nodes having edges, and the edge is used to represent the candidate association rule between different candidate microservices having the microservice dependency relationship.

4. The method according to claim 3, characterized in that, the generating an automated deployment script according to the first configuration information and the second configuration information includes: Determining the edge between the first node and the second node from the preset relationship network, and obtaining the target association rule between the first microservice and the second microservice represented by the edge; Generating the automated deployment script according to the first configuration information, the second configuration information and the target association rule.

5. The method according to claim 2, characterized in that, the determining a second node having an edge with the first node from the multiple nodes includes: Determining at least one second node having a direct edge with the first node from the multiple nodes, wherein there is a direct microservice dependency relationship between the first microservice of the first node and the second microservice of the second node; and / or, Determining at least one second node having an indirect edge with the first node from the multiple nodes, wherein there is an indirect microservice dependency relationship between the first microservice of the first node and the second microservice of the second node.

6. The method according to claim 2, characterized in that, the preset relationship network is constructed based on the following method: According to the basic business, determining the benchmark candidate microservices; Determining other candidate microservices having a microservice dependency relationship with the benchmark candidate microservices; According to the microservice dependency relationship, determining the candidate association rule between the benchmark candidate microservices and the other candidate microservices; Map multiple pieces of candidate configuration information corresponding to multiple candidate microservices to corresponding multiple nodes in the initial relationship network, and generate edges between the corresponding nodes of the candidate microservices with microservice dependencies according to the candidate association rules to obtain the preset relationship network.

7. The method according to claim 6, wherein, the method further includes: determine the candidate microservices to be added; update the preset relationship network according to the candidate microservices to be added to obtain an updated preset relationship network.

8. The method according to claim 7, wherein, the updating the preset relationship network according to the candidate microservices to be added to obtain an updated preset relationship network includes: determine at least one candidate microservice having a microservice dependency on the candidate microservice to be added from the preset relationship network; establish a node corresponding to the candidate configuration information of the candidate microservice to be added in the preset relationship network; determine the candidate association rules between the candidate microservice to be added and the at least one candidate microservice according to the microservice dependency; generate edges of the nodes corresponding to the candidate microservice to be added and the at least one candidate microservice respectively according to the candidate association rules to obtain an updated preset relationship network.

9. A deployment control device, wherein, the device includes: a first acquisition module for acquiring deployment requirement information; a determination module for determining a first microservice according to the deployment requirement information, where the first microservice has relevant first configuration information; a second acquisition module for acquiring second configuration information related to a second microservice according to the first configuration information; a control module for generating an automated deployment script according to the first configuration information and the second configuration information, where the automated deployment script is used to deploy the first microservice and the second microservice.

10. A communication device, wherein, includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method according to any one of claims 1-8.

11. A non-transitory computer-readable storage medium storing computer instructions, wherein, wherein, the computer instructions are used to cause the computer to execute the method according to any one of claims 1-8.

12. A computer program product, wherein, includes a computer program, and the computer program realizes the steps of the method according to any one of claims 1-8 when executed by a processor.

Images