CN113608754A - Service instantiation method and device and electronic equipment - Google Patents
Service instantiation method and device and electronic equipment Download PDFInfo
- Publication number
- CN113608754A CN113608754A CN202110848323.6A CN202110848323A CN113608754A CN 113608754 A CN113608754 A CN 113608754A CN 202110848323 A CN202110848323 A CN 202110848323A CN 113608754 A CN113608754 A CN 113608754A
- Authority
- CN
- China
- Prior art keywords
- deployment
- blueprint
- service
- node
- instantiation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 238000004590 computer program Methods 0.000 claims description 11
- 230000001419 dependent effect Effects 0.000 claims description 8
- 230000001360 synchronised effect Effects 0.000 claims description 8
- 230000004044 response Effects 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000005034 decoration Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003362 replicative effect Effects 0.000 description 2
- 241000380131 Ammophila arenaria Species 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001502 supplementing effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a service instantiation method, a service instantiation device and electronic equipment, wherein the method comprises the following steps: responding to the node selection operation of a user, and acquiring each deployment node; arranging each deployment node according to the dependency relationship according to the editing operation of a user aiming at the dependency relationship of each deployment node to form an arrangement topological graph; and when an instantiation request is received, copying the arrangement topological graph to generate a copy blueprint, and writing the configuration resource in the instantiation request into the copy blueprint so as to generate a service instance according to the copy blueprint recorded with the configuration resource.
Description
Technical Field
The present application relates to the field of service instantiation technologies, and in particular, to a service instantiation method and apparatus, and an electronic device.
Background
In the related art, the method adopted for service instantiation is usually to write an orchestration file for constructing kubernets in advance for different instances before a service instantiation process is started, and perform service instantiation, or write YAML files for deploying nodes and write a dependency relationship corresponding to each deploying node by means of a hellm tool, and perform service instantiation.
However, in actual application, since YAML files used by the same deployment node may be different between different instances, before an instantiation request is initiated, the YAML files of each deployment node and the dependency relationships corresponding to each deployment node need to be respectively pre-written for different instances to form a plurality of deployment files corresponding to each instance one to one. With the increase of instantiation requests for the service, the pre-generated arrangement files are more and more, the management is more and more troublesome, the situations of arrangement disorder and arrangement error are easy to occur during the service instantiation, the inconvenience is brought to the configurator, and the convenience of the service instantiation is poor.
Disclosure of Invention
The present application aims to solve at least one of the technical problems in the prior art, and provides a service instantiation method, device and electronic device, which do not need to set corresponding arrangement files before an instantiation request is initiated for different instances, thereby improving the convenience of service instantiation.
In a first aspect, an embodiment of the present application provides a service instantiation method, including:
responding to the node selection operation of a user, and acquiring each deployment node;
arranging each deployment node according to the dependency relationship according to the editing operation of the user aiming at the dependency relationship of each deployment node to form an arrangement topological graph;
when an instantiation request is received, copying the arrangement topological graph to generate a copy blueprint, and writing the configuration resource in the instantiation request into the copy blueprint so as to generate a service instance according to the copy blueprint recorded with the configuration resource.
After an arrangement topological graph is formed through the dependency relationship of deployment nodes, when an instantiation request is received, the arrangement topological graph is copied to generate a copy blueprint, and then configuration resources in the instantiation request are written into the copy blueprint to be instantiated, so that the same arrangement topological graph can be instantiated into a plurality of different instances, dependency relationship arrangement of a deployment node cluster and yaml file pre-writing are not needed to be performed on each instantiation request in advance to generate an arrangement file, and convenience of service instantiation is improved.
Further, responding to the node selection operation of the user, selecting each deployment node, including:
responding to the node selection operation of a user, and acquiring a Docker mirror image and execution parameter information from a Docker mirror image warehouse;
and generating the deployment node according to the Docker mirror image version and the execution parameter information.
Further, the copying the layout topology map to generate a copy blueprint includes:
and according to a deployment node selection request in the instantiation request, selecting corresponding target deployment nodes from the deployment nodes in the layout topological graph, and copying the target deployment nodes and the dependency relationship of the target deployment nodes in the layout topological graph to generate the copied blueprint.
Further, the method also comprises the following steps:
and allocating corresponding instance identifiers for the service instances.
Further, the method also comprises the following steps:
and when the updating of the layout topological graph is detected, the updating information of the layout topological graph is synchronized to the copied blueprint so as to update the copied blueprint, and the service instance is updated according to the updated copied blueprint.
Further, the method also comprises the following steps:
storing the duplicate blueprints before updating.
Further, the dependency relationship is composed of the dependency items selected by the editing operation, and the dependency items include dependent deployment nodes, dependent types, and versions of the deployment nodes.
In a second aspect, in an embodiment of the present application, there is provided a service instantiation apparatus, including:
the node acquisition module is used for responding to the node selection operation of the user and acquiring each deployment node;
the node arranging module is used for arranging each deployment node according to the dependency relationship according to the editing operation of the user aiming at the dependency relationship of each deployment node to form an arranging topological graph;
and the instance generation module is used for copying the arrangement topological graph to generate a copy blueprint when an instantiation request is received, and writing the configuration resource in the instantiation request into the copy blueprint so as to generate the service instance according to the copy blueprint recorded with the configuration resource.
In a third aspect, an embodiment of the present application further provides an electronic device, including: the service instantiation method comprises the following steps of storing a service instantiation method, recording the service instantiation method in a storage, recording the service instantiation method in the storage, and running a computer program on a processor.
In a fourth aspect, embodiments of the present application provide a computer-readable recording medium, where computer-executable instructions are recorded, and the computer-executable instructions are configured to cause a computer to execute the service instantiation method according to the foregoing embodiments.
Drawings
The present application is further described with reference to the following figures and examples;
FIG. 1 is a diagram of an application environment of a service instantiation method in an embodiment of the present application;
FIG. 2 is a flow diagram that illustrates a method for instantiating a service in one embodiment;
FIG. 3 is a diagram of an exemplary structure for organizing a topology graph;
FIG. 4A is a schematic diagram of an exemplary structure for replicating blueprints;
FIG. 4B is a schematic diagram of yet another exemplary structure for replicating blueprints;
FIG. 5 is a flow diagram illustrating a method for instantiating a service in another embodiment;
FIG. 6 is a block diagram of an apparatus for instantiating a service in one embodiment;
fig. 7 is a block diagram of a server in one embodiment.
Detailed Description
Reference will now be made in detail to the present embodiments of the present application, preferred embodiments of which are illustrated in the accompanying drawings, which are for the purpose of visually supplementing the description with figures and detailed description, so as to enable a person skilled in the art to visually and visually understand each and every feature and technical solution of the present application, but not to limit the scope of the present application.
Distributed computing technology has become the mainstream of current information technology, such as mobile computing and cloud computing. Large application services in a cloud environment are often broken up into multiple services for scheduling and execution. In order to enable the service to be effectively scheduled, before the service scheduling process is started, the deployment node of each service is scheduled in an operation and maintenance environment, so that the service is instantiated according to the scheduled deployment node to generate a service instance, and then the service instance is deployed to perform subsequent service scheduling.
In the related art, the service instantiation usually adopts the following methods: 1. before the service instantiation process is started, the arrangement files for constructing Kubernets are pre-written according to different instances, and service instantiation is carried out. 2. And compiling YAML files of the deployment nodes and compiling the dependency corresponding to each deployment node by means of a Helm tool to instantiate the service. 3. Deployment nodes are arranged and instantiated after being used for docker-composition.
However, in actual application, since YAML files used by the same deployment node may be different between different instances, before an instantiation request is initiated, the YAML files of each deployment node and the dependency relationships corresponding to each deployment node need to be respectively pre-written for different instances to form a plurality of deployment files corresponding to each instance one to one. Before an instantiation request is initiated, the deployment node cluster 1 and the dependency relationship of each deployment node in the deployment node cluster 1 need to be pre-arranged for the instance 1, and the arrangement file 1 is formed after the YAML file of the deployment node cluster 1 is pre-written. Meanwhile, the deployment node cluster 2 and the dependency relationship of each deployment node in the deployment node cluster 2 need to be pre-arranged for the example 2, and the arrangement file 2 is formed after the YAML file of the deployment node cluster 2 is pre-written. And when a subsequent user initiates an instantiation request, generating a corresponding instance according to the corresponding layout file. With the increase of instantiation requests for services, pre-formed arrangement files are more and more, management is more and more troublesome, the situations of arrangement disorder and arrangement error are easy to occur during service instantiation, inconvenience is brought to configuration personnel, and the convenience of service instantiation is poor.
To solve the above problem, as shown in fig. 1, an application environment diagram of a service instantiation method in the embodiment of the present application is included, and includes a terminal 110 and a server 120. The terminal 110 may be specifically a desktop terminal or a mobile terminal, and the mobile terminal may be one of a mobile phone, a tablet computer, a notebook computer, a wearable device, and the like. The server 120 may be implemented by an independent server or a server cluster composed of a plurality of servers, and may also be a cloud server providing basic cloud computing services such as a cloud service, a cloud information base, cloud computing, a cloud function, cloud storage, a web service, cloud communication, middleware service, domain name service, security service, CDN, and a large information and artificial intelligence platform. When receiving a node selection operation sent by a user, the terminal 110 acquires each deployment node selected by the node selection operation from the server 120, and then performs deployment on each deployment node according to an editing operation of the user on a dependency relationship of each deployment node to form a deployment topological graph. When the terminal 110 receives the instantiation request, the arrangement topological graph is copied to generate a copy blueprint, and after the configuration resources in the instantiation request are written into the copy blueprint, the configuration resources are instantiated according to the copy blueprint recorded with the configuration resources to form a corresponding service instance.
According to the method and the device, after the arrangement topological graph is formed through the dependency relationship of the deployment nodes, when the instantiation request is received, the arrangement topological graph is copied to generate the copy blueprint, and the configuration resources in the instantiation request are written into the copy blueprint to be instantiated, so that the same arrangement topological graph can be instantiated into a plurality of different instances, dependency relationship arrangement of the deployment node cluster and yaml file pre-writing for generating the arrangement file are not needed for each instantiation request, and convenience of service instantiation is improved.
Hereinafter, the service instantiation method provided by the embodiments of the present application will be described and explained in detail through several specific embodiments.
As shown in FIG. 2, in one embodiment, a service instantiation method is provided. The embodiment is mainly illustrated by applying the method to computer equipment. The computer device may specifically be the terminal 110 in fig. 1 described above.
Referring to fig. 2, the service instantiation method specifically includes the following steps:
and S11, responding to the node selection operation of the user and acquiring each deployment node.
In an embodiment, the terminal is provided with tag information of a plurality of deployment nodes in advance for a user to select, each deployment node corresponds to one tag information, and the tag information can be displayed through a display screen of the terminal. The node selection operation may be a click operation, and when the click operation of the user on the tag information is received, the deployment node corresponding to the tag is acquired from the server according to the tag selected by the user click operation. The node selection operation can also be a dragging operation, and when the condition that the user drags the label to the designated area is detected, the deployment node corresponding to the label is obtained from the server.
In an embodiment, the deployment nodes include docker images and execution parameter information, respond to a node selection operation of a user, and select each deployment node, including: responding to the node selection operation of a user, and acquiring a Docker mirror image and execution parameter information from a Docker mirror image warehouse; and generating a deployment node according to the Docker mirror image version and the execution parameter information. The node selection operation is specifically a selection operation of a label of the Docker image and a label selection operation of the execution parameter information. And acquiring the corresponding Docker mirror image and the execution parameter information from a Docker mirror image warehouse in the server according to the Docker mirror image label and the execution parameter information label selected by the user. The execution parameter information comprises the number of CPU cores, memory information, port information, environment variables, middleware required by the node, a storage disk, the configuration of a load balancer and the like.
After the deployment nodes are obtained, the Docker mirror images and the execution parameter information of the deployment nodes can be displayed on a display interface of the terminal, so that a user can conveniently see the resource use condition of each node, and the user can conveniently manage the nodes.
And S12, arranging the deployment nodes according to the dependency relationship according to the editing operation of the user aiming at the dependency relationship of the deployment nodes to form an arrangement topological graph.
In an embodiment, after each deployment node is acquired, each deployment node is arranged according to the dependency relationship of each deployment node selected by a user. And if the deployment node A, the deployment node B and the deployment node C are obtained, displaying the deployment node A, the deployment node B and the deployment node C on a display interface. When the editing operation of the user is that the selected deployment node C depends on the deployment node B, and the deployment node B depends on the deployment node a, the deployment topology shown in fig. 3 may be generated according to the editing operation. The orchestration topological graph refers to planning information formed by a batch of deployment nodes, and the orchestration topological graph includes deployment nodes to be scheduled, dependencies among the deployment nodes, storage, configuration and the like, so that service instantiation can be performed according to the orchestration topological graph when service instantiation is performed.
In one embodiment, the editing operation may be the addition of a pointing arrow between the displayed deployment nodes. When the terminal detects that the directional arrow exists between the nodes, the dependency relationship between the two deployment nodes can be calculated according to the graph algorithm. If a directional arrow exists between the deployment node A and the deployment node B, the deployment node A points to the deployment node B, and the deployment node B can be calculated to be dependent on the deployment node A according to the graph algorithm.
And the dependency relationship consists of all dependency items selected by the editing operation, and the dependency items comprise dependent deployment nodes, dependent types and versions of the deployment nodes. Wherein a dependency type includes greater than, equal to, less than, greater than or equal to, less than or equal to. As an example of this embodiment, the dependency relationship may be expressed as deployment node a relying on deployment node B version greater than or equal to V1. As yet another example of this embodiment, deployment node a depends on a version greater than or equal to V1 of deployment node B and deployment node a depends on a version equal to V2 of deployment node C.
And S13, when the instantiation request is received, copying the arrangement topological graph to generate a copy blueprint, and writing the configuration resource in the instantiation request into the copy blueprint so as to generate the service instance according to the copy blueprint recorded with the configuration resource.
In one embodiment, the configuration resource includes environment information, middleware information, version information, configuration information, and the like, wherein the version information is used for indicating the version of the deployment node. When an instantiation request is received, the layout topological graph is copied, a copy blueprint corresponding to the instantiation request is generated, and then the environment information, the middleware information and the configuration information are written into the copy blueprint.
The choreography topological graph does not need to be bound with a fixed instantiation request, and the choreography topological graph is copied only when service instantiation is needed, so that a copy blueprint is obtained for service instantiation, and the service instantiation topological graph can be shared by a plurality of instance requests. When a plurality of service instantiation requests are received, such as instantiation request 1 and instantiation request 2, after the duplicate blueprint 1 and the duplicate blueprint 2 are respectively generated, the configuration resource of the instantiation request 1 is written into the duplicate blueprint 1 for instantiation, and the configuration resource of the instantiation request 2 is written into the duplicate blueprint 2 for instantiation, so that the arrangement topological graph can be instantiated into a plurality of different instances. The environment information, the middleware information and the configuration information in each instance can be different, and the deployment node does not need to be arranged again aiming at each instantiation request, so that the service instantiation efficiency is improved.
After an arrangement topological graph is formed through the dependency relationship of deployment nodes, when an instantiation request is received, the arrangement topological graph is copied to generate a copy blueprint, and then configuration resources in the instantiation request are written into the copy blueprint to be instantiated, so that the same arrangement topological graph can be instantiated into a plurality of different instances, dependency relationship arrangement of a deployment node cluster and yaml file pre-writing are not needed to be performed on each instantiation request in advance to generate an arrangement file, and convenience of service instantiation is improved.
In order to enable an orchestration topology graph to conveniently create multiple running instances, in an embodiment, copying the orchestration topology graph to generate a copy blueprint includes: and according to the deployment node selection request in the instantiation request, selecting corresponding target deployment nodes from the deployment nodes in the layout topological graph, and copying the target deployment nodes and the dependency relationship of the target deployment nodes in the layout topological graph to generate a copy blueprint.
Illustratively, if the deployment nodes in the orchestration topology include a deployment node a, a deployment node B, and a deployment node C, and the deployment node selection request in the instantiation request selects the deployment node a, the deployment node B, and the deployment node C, the orchestration topology is completely copied to generate the copy blueprint shown in fig. 4A. If the deployment node selection request selects the deployment node a and the deployment node B, the deployment node a and the deployment node B in the arrangement topological graph and the dependency relationship between the deployment node a and the deployment node B are copied to generate a copy blueprint shown in fig. 4B.
By the method, different copied blueprints can be conveniently formed for instantiation test and investigation, and configuration resources such as middleware can be reserved during test, so that the instantiation test is facilitated.
In order to facilitate monitoring of the service instance, in one embodiment, after the service instance is formed, a corresponding instance identifier is allocated to the service instance, and the instance identifier is a unique identifier, so that when an error occurs in the service instance, the service instance with the error can be quickly determined according to the instance identifier, and management is facilitated.
Considering that when a service is updated, the corresponding service instance also needs to be updated, in an embodiment, as shown in fig. 5, the method further includes:
s14, when detecting the updating of the layout topological graph, synchronizing the updating information of the layout topological graph to the copy blueprint to update the copy blueprint, and updating the service instance according to the updated copy blueprint.
In one embodiment, the update information includes newly added or deleted deployment nodes, or changes in dependencies of deployment nodes. When the topological graph is scheduled for updating, the updating information of the scheduled topological graph can be synchronized into each of the duplicate blueprints, so that after each of the duplicate blueprints is upgraded, the updated information is synchronized into the corresponding service instance for operation. If a deployment node D and the dependency relationships between the deployment node D and the deployment node A, the deployment node B and the deployment node C in the original layout topological graph are added to the layout topological graph, the dependency relationships between the deployment node D and the deployment node A, the deployment node B and the deployment node C in the original layout topological graph are synchronized to the copied blueprints.
The updated information of the updated arrangement topological graph is synchronized to each copy blueprint, so that each copy blueprint is updated and then synchronized to the corresponding instance to run.
In an embodiment, after updating the service instance according to the updated replicated blueprint, the method further includes: and storing the copied blueprints before updating. When the copied blueprints are updated, the old copied blueprints can be stored for subsequent tracing. When each copied blueprint is stored, the copied blueprints can be marked through the instance identifiers of the generated instances, so that the corresponding old copied blueprints can be conveniently found during backtracking.
In one embodiment, as shown in fig. 6, there is provided a service instantiation apparatus applied to a server, including:
the node obtaining module 101 is configured to respond to a node selection operation of a user to obtain each deployment node.
The node orchestration module 102 is configured to perform orchestration on each deployment node according to the dependency relationship according to an editing operation of a user on the dependency relationship of each deployment node, so as to form an orchestration topological graph.
The dependency relationship is composed of all dependency items selected by the editing operation, and the dependency items comprise dependent deployment nodes, dependent types and versions of the deployment nodes.
The instance generation module 103 is configured to, when an instantiation request is received, copy the orchestration topology map to generate a copy blueprint, and write the configuration resource in the instantiation request into the copy blueprint, so as to generate a service instance according to the copy blueprint recorded with the configuration resource.
The node obtaining module 101 is specifically configured to: responding to the node selection operation of a user, and acquiring a Docker mirror image and execution parameter information from a Docker mirror image warehouse; and generating the deployment node according to the Docker mirror image version and the execution parameter information.
In an embodiment, the instance generation module 103 is specifically configured to:
and according to a deployment node selection request in the instantiation request, selecting corresponding target deployment nodes from the deployment nodes in the layout topological graph, and copying the target deployment nodes and the dependency relationship of the target deployment nodes in the layout topological graph to generate the copied blueprint.
In an embodiment, the instance generation module 103 is further configured to: and allocating corresponding instance identifiers for the service instances.
In one embodiment, the instance generation module 103 is further configured to:
and when the updating of the layout topological graph is detected, the updating information of the layout topological graph is synchronized to the copied blueprint so as to update the copied blueprint, and the service instance is updated according to the updated copied blueprint.
In an embodiment, the instance generation module 103 is further configured to:
storing the duplicate blueprints before updating.
In one embodiment, there is provided an electronic device, as shown in fig. 7, including: the service instantiation method comprises the following steps of storing a service instantiation method, recording the service instantiation method in a storage, recording the service instantiation method in the storage, and running a computer program on a processor.
In one embodiment, the service instantiation apparatus provided in the present application can be implemented in the form of a computer program, and the computer program can be run on an electronic device as shown in fig. 7. The memory of the terminal device can record various program modules constituting the service instantiation device. The computer program of each program module causes the processor to execute the steps in the service instantiation method of each embodiment of the present application described in the present specification.
In one embodiment, there is provided an electronic device including: the service instantiation method comprises the following steps of a memory, a processor and a computer program recorded on the memory and capable of running on the processor, wherein the processor executes the program to execute the steps of the service instantiation method. Here, the steps of the service instantiation method may be the steps in the service instantiation method of the above embodiments.
In one embodiment, there is provided a computer-readable recording medium having recorded thereon computer-executable instructions for causing a computer to perform the steps of the service instantiation method described above. Here, the steps of the service instantiation method may be the steps in the service instantiation method of the above embodiments.
The foregoing is a preferred embodiment of the present application, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations are also regarded as the protection scope of the present application.
It will be understood by those skilled in the art that all or part of the processes of the methods of the above embodiments may be implemented by a computer program, which is recorded in a computer-readable recording medium, and the computer program may include the processes of the above embodiments of the methods when the computer program is executed. The recording medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
Claims (10)
1. A method of service instantiation, comprising:
responding to the node selection operation of a user, and acquiring each deployment node;
arranging each deployment node according to the dependency relationship according to the editing operation of the user aiming at the dependency relationship of each deployment node to form an arrangement topological graph;
when an instantiation request is received, copying the arrangement topological graph to generate a copy blueprint, and writing the configuration resource in the instantiation request into the copy blueprint so as to generate a service instance according to the copy blueprint recorded with the configuration resource.
2. The service instantiation method as claimed in claim 1, wherein selecting each deployment node in response to a node selection operation of a user comprises:
responding to the node selection operation of a user, and acquiring a Docker mirror image and execution parameter information from a Docker mirror image warehouse;
and generating the deployment node according to the Docker mirror image version and the execution parameter information.
3. The service instantiation method of claim 1, wherein said copying said orchestration topology graph to generate a copy blueprint comprises:
and according to a deployment node selection request in the instantiation request, selecting corresponding target deployment nodes from the deployment nodes in the layout topological graph, and copying the target deployment nodes and the dependency relationship of the target deployment nodes in the layout topological graph to generate the copied blueprint.
4. The service instantiation method according to any one of claims 1 to 3, further comprising:
and allocating corresponding instance identifiers for the service instances.
5. The service instantiation method according to claim 1 or 3, further comprising:
and when the updating of the layout topological graph is detected, the updating information of the layout topological graph is synchronized to the copied blueprint so as to update the copied blueprint, and the service instance is updated according to the updated copied blueprint.
6. The service instantiation method according to claim 5, further comprising:
storing the duplicate blueprints before updating.
7. The service instantiation method according to claim 1, wherein said dependency relationship is composed of each dependency selected by said editing operation, said dependency includes dependent deployment node, dependency type and version of deployment node.
8. A service instantiation apparatus, comprising:
the node acquisition module is used for responding to the node selection operation of the user and acquiring each deployment node;
the node arranging module is used for arranging each deployment node according to the dependency relationship according to the editing operation of the user aiming at the dependency relationship of each deployment node to form an arranging topological graph;
and the instance generation module is used for copying the arrangement topological graph to generate a copy blueprint when an instantiation request is received, and writing the configuration resource in the instantiation request into the copy blueprint so as to generate the service instance according to the copy blueprint recorded with the configuration resource.
9. An electronic device, comprising: memory, processor and computer program recorded on the memory and executable on the processor, characterized in that the processor implements the service instantiation method as claimed in any one of claims 1 to 7 when executing the program.
10. A computer-readable storage medium, in which a computer program is stored which is adapted to be loaded and executed by a processor to cause a computer device having said processor to carry out the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110848323.6A CN113608754A (en) | 2021-07-23 | 2021-07-23 | Service instantiation method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110848323.6A CN113608754A (en) | 2021-07-23 | 2021-07-23 | Service instantiation method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113608754A true CN113608754A (en) | 2021-11-05 |
Family
ID=78305500
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110848323.6A Pending CN113608754A (en) | 2021-07-23 | 2021-07-23 | Service instantiation method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113608754A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114398115A (en) * | 2021-12-03 | 2022-04-26 | 光控特斯联(重庆)信息技术有限公司 | Visual pipeline generation method and device, storage medium and electronic equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104813284A (en) * | 2012-12-03 | 2015-07-29 | 惠普发展公司，有限责任合伙企业 | Generic resource provider for cloud service |
| CN105518651A (en) * | 2013-09-04 | 2016-04-20 | 慧与发展有限责任合伙企业 | Policy based selection of resources for cloud service |
| CN107579851A (en) * | 2017-09-14 | 2018-01-12 | 郑州云海信息技术有限公司 | The method and apparatus for determining the execution sequence of resource layout template |
| US20190014015A1 (en) * | 2017-07-04 | 2019-01-10 | Vmware, Inc. | Smart service catalogs based deployment of applications |
| CN111552471A (en) * | 2020-04-07 | 2020-08-18 | 电科云(北京)科技有限公司 | Task arrangement method and system under hybrid cloud environment |
| CN111880904A (en) * | 2020-07-30 | 2020-11-03 | 北京浪潮数据技术有限公司 | Method, system and related device for arranging virtualization platform resources |
| CN112181602A (en) * | 2020-10-23 | 2021-01-05 | 济南浪潮数据技术有限公司 | Resource arranging method and device, electronic equipment and storage medium |
-
2021
- 2021-07-23 CN CN202110848323.6A patent/CN113608754A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104813284A (en) * | 2012-12-03 | 2015-07-29 | 惠普发展公司，有限责任合伙企业 | Generic resource provider for cloud service |
| CN105518651A (en) * | 2013-09-04 | 2016-04-20 | 慧与发展有限责任合伙企业 | Policy based selection of resources for cloud service |
| US20190014015A1 (en) * | 2017-07-04 | 2019-01-10 | Vmware, Inc. | Smart service catalogs based deployment of applications |
| CN107579851A (en) * | 2017-09-14 | 2018-01-12 | 郑州云海信息技术有限公司 | The method and apparatus for determining the execution sequence of resource layout template |
| CN111552471A (en) * | 2020-04-07 | 2020-08-18 | 电科云(北京)科技有限公司 | Task arrangement method and system under hybrid cloud environment |
| CN111880904A (en) * | 2020-07-30 | 2020-11-03 | 北京浪潮数据技术有限公司 | Method, system and related device for arranging virtualization platform resources |
| CN112181602A (en) * | 2020-10-23 | 2021-01-05 | 济南浪潮数据技术有限公司 | Resource arranging method and device, electronic equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114398115A (en) * | 2021-12-03 | 2022-04-26 | 光控特斯联(重庆)信息技术有限公司 | Visual pipeline generation method and device, storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112118565B (en) | Multi-tenant service gray level publishing method, device, computer equipment and storage medium | |
| CN109120678B (en) | Method and apparatus for service hosting of distributed storage system | |
| CN110768833B (en) | Application arrangement and deployment method and device based on kubernets | |
| US10776175B1 (en) | Solver for cluster management system | |
| US11882177B2 (en) | Orchestration of data services in multiple cloud infrastructures | |
| US8862933B2 (en) | Apparatus, systems and methods for deployment and management of distributed computing systems and applications | |
| US9851989B2 (en) | Methods and apparatus to manage virtual machines | |
| CN111782232A (en) | Cluster deployment method and device, terminal equipment and storage medium | |
| US8645837B2 (en) | Graphical user interface for managing services in a distributed computing system | |
| US8418181B1 (en) | Managing program execution based on data storage location | |
| US8918783B2 (en) | Managing virtual computers simultaneously with static and dynamic dependencies | |
| US11144292B2 (en) | Packaging support system and packaging support method | |
| CN113672352B (en) | Method and device for deploying federal learning task based on container | |
| CN112242920A (en) | Cloud platform deployment method, device and node | |
| US11108638B1 (en) | Health monitoring of automatically deployed and managed network pipelines | |
| CN115061717A (en) | Application management method, application subscription method and related equipment | |
| CN113434283B (en) | Service scheduling method and device, server and computer readable storage medium | |
| US20230126168A1 (en) | Scalable visualization of a containerized application in a multiple-cluster and multiple deployment application environment | |
| CN110784347A (en) | Node management method, system, equipment and storage medium for container cluster | |
| CN113608754A (en) | Service instantiation method and device and electronic equipment | |
| CN114675927A (en) | Service instance deployment method and device, electronic equipment and storage medium | |
| CN116881012A (en) | Container application vertical capacity expansion method, device, equipment and readable storage medium | |
| CN110958138A (en) | Container expansion method and device | |
| CN113326052A (en) | Method and device for upgrading service component, computer equipment and storage medium | |
| CN114003343A (en) | Cloud native application construction method and device and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |