CN114064213B - Quick arranging service method and system based on Kubernets container environment - Google Patents
Quick arranging service method and system based on Kubernets container environment Download PDFInfo
- Publication number
- CN114064213B CN114064213B CN202111355254.1A CN202111355254A CN114064213B CN 114064213 B CN114064213 B CN 114064213B CN 202111355254 A CN202111355254 A CN 202111355254A CN 114064213 B CN114064213 B CN 114064213B
- Authority
- CN
- China
- Prior art keywords
- service
- configuration
- task
- information
- orchestration
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000003860 storage Methods 0.000 claims abstract description 30
- 230000007246 mechanism Effects 0.000 claims abstract description 7
- 230000008569 process Effects 0.000 claims abstract description 7
- 238000012827 research and development Methods 0.000 claims abstract description 7
- 230000004048 modification Effects 0.000 claims description 7
- 238000012986 modification Methods 0.000 claims description 7
- 238000013475 authorization Methods 0.000 claims description 4
- 238000004458 analytical method Methods 0.000 claims description 3
- 230000010354 integration Effects 0.000 claims description 3
- 230000003993 interaction Effects 0.000 claims description 3
- 238000002360 preparation method Methods 0.000 abstract description 3
- 230000000977 initiatory effect Effects 0.000 abstract 1
- 230000007613 environmental effect Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000000889 atomisation Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000004083 survival effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a rapid arrangement service method based on Kubernets container environment, which comprises the following steps: defining a service orchestration task template, analyzing a template application scene, analyzing a system and a tool related to a research and development process, and extracting specific configuration of a task in different projects as a parameter of the task; project service orchestration, nginx configuration, parameter configuration, environment configuration and initialization; the analytics service is Deployment stateless load or StatefulSet stateful load or task Job or timing task CronJob; analyzing whether storage is needed or not; configuring a service arrangement template dependency relationship, wherein the service arrangement template relates to a plurality of services, analyzes whether the plurality of services have the dependency relationship, further analyzes the strong and weak ordering of the dependency relationship with the dependency relationship, and analyzes the establishment mechanism of the dependency relationship; triggering arrangement is invoked. The method can solve the problems of high stability of code dependence initiation, low preparation and deployment efficiency of an application software running environment, and manual updating and rollback efficiency.
Description
Technical Field
The invention relates to the technical field of containerized deployment environments, in particular to a quick arranging service method and system based on Kubernets container environments.
Background
With the popularization of the containerization technology, continuous delivery of cloud primordia is promoted, various companies begin to research and use continuous delivery products, the Kubernetes container platform based on the Docker is increasingly applied to production environments, when Deployment application in the Kubernetes container platform is updated, new codes are required to be pulled from a code library, new version application is compiled and built, mirror images are manufactured and uploaded to a mirror image warehouse, and Deployment application in the Kubernetes is updated.
However, almost all service systems currently store various types of operation information in the service side. Severely depending on the stability of the server. With the increase of the code quantity and the application quantity, most of systems only record the latest data parameters, the efficiency of manual updating and rollback is lower, the possibility of misoperation is higher, and the labor cost is higher. Therefore, in order to solve the problems, it is of great importance to provide a rapid orchestration service method based on Kubernets container environments.
Disclosure of Invention
The invention aims to provide a quick arranging service method and system based on Kubernets container environments. In order to solve the technical problems existing in the background art.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
A rapid orchestration service method based on Kubernets container environments, comprising: defining a service orchestration template; defining a service orchestration task template, analyzing a template application scene, analyzing a system and a tool related to a research and development process, and extracting specific configuration of a task in different projects as a parameter of the task; project service orchestration, nginx configuration, parameter configuration, environment configuration and initialization; the analytics service is Deployment stateless load or StatefulSet stateful load or task Job or timing task CronJob; analyzing whether storage is needed or not, and adopting a storage mode when storage is needed; configuring a service arrangement template dependency relationship, wherein the service arrangement template relates to a plurality of services, analyzes whether the plurality of services have the dependency relationship, further analyzes the strong and weak ordering of the dependency relationship with the dependency relationship, and analyzes the establishment mechanism of the dependency relationship; triggering arrangement is invoked.
In some embodiments, the method further comprises:
deploying environment, creating clusters and nodes; defining a region;
creating tenant information;
Performing authorization association on the tenant and the cluster;
Adding an administrator under the tenant;
Adding items to an administrator, and configuring item information, item personnel information and rights;
opening service rights for the project and acquiring service information;
Newly adding an application, and isolating service arrangement according to application classification;
Newly adding common config information, secret information and stored PVC information;
Newly creating service arrangement under the created cluster, tenant, area and project, and filling in global configuration of the service arrangement;
performing task configuration on a service arrangement stage of service arrangement, wherein the task configuration comprises log configuration;
Service orchestration information for the item is saved.
In some embodiments, the method opens service rights to the project, and further includes after obtaining the service information:
after entering the opened service, the administrator adds a new space and configures space information: mirror image, white list, resource and other information, different contents are separated according to space to distinguish the resources.
In some embodiments, the method further comprises:
Initializing service arrangement;
Storing the stored project service arrangement configuration information in a service arrangement configuration table of a database server, and converting each task into a yml-format task script by a script code generator based on the configuration information by a background service program module.
In some embodiments, the initialization includes the following operations:
Judging the current state, triggering the service scheduling execution when the user calls the task Job with no state load Deployment or no state load StatefulSet, and triggering the service scheduling execution when the timing rule is met after the user calls the task CronJob.
In some embodiments, the method further comprises selecting and editing the saved service orchestration configuration, the editing comprising at least one of: modifying task sequence, task configuration information, and adding and deleting tasks;
Wherein each modification of the service orchestration configuration is stored in version in a service orchestration configuration table established by the database server.
In some embodiments, the Kubernets container environment comprises:
the front end module is used for providing a man-machine interaction interface;
the database server is used for storing data information;
The pipeline server is used for creating and executing continuous integration and continuous deployment service arrangement and pushing the products to the product library;
the product library is used for storing War packages and a Docker mirror image;
gitlab, open source code hosting software, code hosting;
The code warehouse is used for storing project source codes;
the back-end management platform is used for integrating the core center of the resource and is responsible for connecting the front-end, the server of the pipeline, the server of the product library and the database.
Meanwhile, the invention also discloses a rapid arrangement service system based on Kubernets container environment, which comprises:
The definition module is used for defining a service arrangement template; defining a service orchestration task template, analyzing a template application scene, analyzing a system and a tool related to a research and development process, and extracting specific configuration of a task in different projects as a parameter of the task;
The first configuration module is used for project service arrangement, nginx configuration, parameter configuration, environment configuration and initialization; the analytics service is Deployment stateless load or StatefulSet stateful load or task Job or timing task CronJob;
the analysis module is used for analyzing whether storage is needed or not and the storage mode adopted when the storage is needed;
The second configuration module is used for configuring the dependence relationship of a service arrangement template, the service arrangement template relates to a plurality of services, analyzing whether the plurality of services have the dependence relationship, further analyzing the strong and weak ordering of the dependence relationship, and analyzing the establishment mechanism of the dependence relationship;
And the triggering module is used for calling the triggering arrangement.
Meanwhile, the invention also discloses a quick arranging service device based on Kubernets container environment, which comprises a processor and a memory; the memory is configured to store instructions that, when executed by the processor, cause the apparatus to implement the quick orchestration service method according to any one of the preceding claims based on Kubernets container environments.
Meanwhile, the invention also discloses a computer readable storage medium, wherein the storage medium stores computer instructions, and when the computer reads the computer instructions in the storage medium, the computer runs the rapid orchestration service method based on Kubernets container environments.
Advantageous effects
Compared with the prior art, the invention has the remarkable advantages that:
the invention makes service arrangement task atomization and parameterization configuration, so that the task can be highly multiplexed; the service arrangement template, the service arrangement task, the service arrangement dependency relationship and the service arrangement stage are designed, so that the common service arrangement can be defined more quickly; the service arrangement configuration function realizes visual modularized configuration, changes the traditional script configuration mode, reduces the configuration difficulty of service arrangement, and solves the problems of high stability of code dependence on an originating terminal, low preparation and deployment efficiency of an application software running environment, and manual update and rollback efficiency.
Drawings
FIG. 1 is a schematic diagram of a rapid orchestration service system based on Kubernets container environments according to one embodiment;
FIG. 2 is a flow chart of a rapid orchestration service method based on Kubernets container environments according to the present embodiment;
Fig. 3 is a flowchart of a rapid orchestration service method based on Kubernets container environments according to this embodiment.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
On the contrary, the application is intended to cover any alternatives, modifications, equivalents, and variations as may be included within the spirit and scope of the application as defined by the appended claims. Further, in the following detailed description of the present application, certain specific details are set forth in order to provide a better understanding of the present application. The present application will be fully understood by those skilled in the art without the details described herein.
A method and system for rapid orchestration service based on Kubernets container environments according to embodiments of the present application will be described in detail below with reference to fig. 1-3. It is noted that the following examples are only for explaining the present application and are not to be construed as limiting the present application.
Example 1
As shown in fig. 1, a rapid orchestration service system 100 based on Kubernets container environments, comprising:
The definition module is used for defining a service arrangement template; defining a service orchestration task template, analyzing a template application scene, analyzing a system and a tool related to a research and development process, and extracting specific configuration of a task in different projects as a parameter of the task;
The first configuration module is used for project service arrangement, nginx configuration, parameter configuration, environment configuration and initialization; the analytics service is Deployment stateless load or StatefulSet stateful load or task Job or timing task CronJob;
the analysis module is used for analyzing whether storage is needed or not and the storage mode adopted when the storage is needed;
The second configuration module is used for configuring the dependence relationship of a service arrangement template, the service arrangement template relates to a plurality of services, analyzing whether the plurality of services have the dependence relationship, further analyzing the strong and weak ordering of the dependence relationship, and analyzing the establishment mechanism of the dependence relationship;
And the triggering module is used for calling the triggering arrangement.
Example 2
As shown in fig. 2, a rapid orchestration service method based on Kubernets container environments includes the following specific flow 200:
at step 210, a service orchestration template is defined.
Defining a service orchestration task template, analyzing a template application scene, analyzing a system and a tool related to a research and development process, and extracting specific configuration of a task in different projects as a parameter of the task;
step 220, project service orchestration, nginx configuration, parameter configuration, environment configuration and initialization; the analytics service is Deployment stateless load or StatefulSet stateful load or task Job or timing task CronJob;
step 230, analyzing whether storage is needed or not, and adopting a storage mode when storage is needed;
Step 240, configuring a service arrangement template dependency relationship, wherein the service arrangement template relates to a plurality of services, analyzes whether the plurality of services have the dependency relationship, further analyzes the strong and weak ordering of the dependency relationship with the dependency relationship, and analyzes the establishment mechanism of the dependency relationship;
Step 250, call trigger orchestration.
Specifically, the implementation of the above steps is based on the following environmental configuration:
The front end module is used for providing a man-machine interaction interface; the database server is used for storing data information; the pipeline server is used for creating and executing continuous integration and continuous deployment service arrangement and pushing the products to the product library; the product library is used for storing War packages and a Docker mirror image; gitlab, open source code hosting software, code hosting; the code warehouse is used for storing project source codes; the back-end management platform is used for integrating the core center of the resource and is responsible for connecting the front-end, the server of the pipeline, the server of the product library and the database.
In some embodiments, as shown in fig. 3, the implementation of the method for rapid orchestration service based on Kubernets container environments is based specifically on the following operational flow:
1. Deploying an environment, creating a cluster and nodes; defining a region;
cluster resources, which provide resource guarantee for service arrangement; after the service scheduling template is called, the service scheduling template can be scheduled to node nodes, the node of the label can be designated, the resource use of all services under the cluster is ensured, and the service scheduling template can be scheduled to other nodes when the current resource is insufficient.
2. Creating tenant information;
Different tenants use so that they can work at different levels for their own authorized resources.
3. Performing authorization association on the tenant and the cluster;
different service orchestrations may be used with different resources.
4. Adding an administrator under the tenant;
5. The administrator adds the project newly, and dispose the project information, project personnel information, permission;
6. opening service rights for the project and acquiring service information;
7. after entering the opened service, the administrator adds a new space and configures space information: mirror image, white list, resource and other information, and different contents are separated according to space to distinguish the resources;
The information of domain name, user name, password, etc. of the mirror image is configured, and the mirror image can be used in service arrangement. Whether an intranet image or a third party image is used is distinguished.
8. Newly adding an application, and isolating service arrangement according to application classification;
9. Newly adding config information shared by service arrangement;
Service orchestration typically requires some underlying environmental configuration, which may be done in the form of a nginx/yml file to configure config information, or at orchestration time to configure environmental variables; when there is a dependency on service orchestration, multiple services may be associated here.
10. Newly adding secret information shared by service arrangement;
Also, there are some confidential configuration information that needs to be configured; the information of crt and key is required to be configured, and the information can be of the Opaque type or of the kubinetes type.
11. Newly adding the stored PVC information shared by service arrangement;
According to whether the service orchestration is deploment, stateful, whether the storage information is self-built or configured by using storageclass configured by the management background and the storage which is automatically built when stateful is established is determined, the driving type of the storage, the file system type, the address of the node, the account number of an administrator, the password and the like are determined, and the access modes are exclusive sharing, read-write sharing, read-only sharing and capacity size.
12. Newly creating service arrangement under the created cluster, tenant, area and project, and filling in global configuration of the service arrangement;
selecting a cluster, a tenant, an area and a project, creating service arrangement, configuring global information such as names of services and the like;
13. Performing task configuration on a service arrangement stage of service arrangement to realize free arrangement of tasks, including log configuration and the like;
The configuration service schedules specific information including whether to collect logs, whether to store volumes, and to mount, mount paths, whether to run with root identities, user IDs and user group IDs at run-time, mount group IDs, whether images are taken from an intranet or third party images, user names and passwords required by the images, policies for pulling the images, resources including requests and limit settings for CPU and memory, privilege mode, whether to run with root identities, user IDs and user group IDs at run-time, mount group IDs, working catalogues, running parameters, running commands, health checks including survival checks and ready checks, container lifecycle operations, copy conditions, whether to automatically adjust, scheduling policies, whether to be nodes with specified labels or not, system automatic scheduling, affinity and anti-affinity configuration, domain name configuration, port mapping, and the like.
14. After filling each stage of service arrangement, service arrangement information of the project can be saved;
after the information is stored, the information is stored in a database.
15. Other service information depending on configuration, namely initializing service arrangement;
The service arrangement may be a single service or a plurality of services, and a dependency relationship may exist between the plurality of services. After the service orchestration is invoked, the services are deployed in turn according to the dependencies.
16. Storing the stored project service arrangement configuration information in a service arrangement configuration table of a database server, and converting each task into a yml-format task script by a script code generator based on the configuration information by a background service program module;
17. After initialization, the background service program is ready, if the task Job is a Deployment stateless load or StatefulSet stateful load task, the user triggers the service programming to execute when calling, and if the task Job is a timing task CronJob, the user triggers the service programming to execute when the timing rule is met after calling;
18. The saved service arrangement configuration can be edited after being selected, the task sequence and the task configuration information are modified, and the tasks are added and deleted; each modification of the service orchestration configuration is stored in a service orchestration configuration table established by the database server according to versions, and the historical versions can be selected to check specific configuration information so as to support version rollback.
When a user needs to deploy a certain service, the user can quickly call the service arrangement, start the service, and when the currently operated service version is abnormal, find the historical normal operation version in the service details and roll back.
Meanwhile, the invention also discloses a quick arranging service device based on Kubernets container environment, which comprises a processor and a memory; the memory is configured to store instructions that, when executed by the processor, cause the apparatus to implement the quick orchestration service method according to any one of the preceding claims based on Kubernets container environments.
Meanwhile, the invention also discloses a computer readable storage medium, wherein the storage medium stores computer instructions, and when the computer reads the computer instructions in the storage medium, the computer runs the rapid orchestration service method based on Kubernets container environments.
In conclusion, the rapid arrangement service method based on Kubernets container environment can effectively solve the problems of high stability of code dependence on an originating end, low preparation and deployment efficiency of an application software running environment, and manual update and rollback efficiency.
The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather is intended to cover all modifications, equivalents, and alternatives falling within the spirit and principles of the invention.
Claims (9)
1. A fast orchestration service method based on a Kubernetes container environment, comprising:
Defining a service orchestration template; defining a service orchestration task template, analyzing a template application scene, analyzing a system and a tool related to a research and development process, and extracting specific configuration of a task in different projects as a parameter of the task;
Project service orchestration, nginx configuration, parameter configuration, environment configuration and initialization; the analytics service is Deployment stateless load or StatefulSet stateful load or task Job or timing task CronJob;
analyzing whether storage is needed or not, and adopting a storage mode when storage is needed;
Configuring a service arrangement template dependency relationship, wherein the service arrangement template relates to a plurality of services, analyzes whether the plurality of services have the dependency relationship, further analyzes the strong and weak ordering of the dependency relationship with the dependency relationship, and analyzes the establishment mechanism of the dependency relationship;
calling trigger arrangement; further comprises:
deploying environment, creating clusters and nodes; defining a region;
creating tenant information;
Performing authorization association on the tenant and the cluster;
Adding an administrator under the tenant;
Adding items to an administrator, and configuring item information, item personnel information and rights;
opening service rights for the project and acquiring service information;
Newly adding an application, and isolating service arrangement according to application classification;
Newly adding common config information, secret information and stored PVC information;
Newly creating service arrangement under the created cluster, tenant, area and project, and filling in global configuration of the service arrangement;
performing task configuration on a service arrangement stage of service arrangement, wherein the task configuration comprises log configuration;
Saving service arrangement information of the project;
Editing the saved service arrangement configuration after being selected, modifying task sequence, task configuration information and adding and deleting tasks; each modification of the service orchestration configuration is stored in a service orchestration configuration table established by the database server according to versions, and the historical versions are selected to check specific configuration information so as to support version rollback.
2. The method for rapidly arranging services based on the Kubernetes container environment according to claim 1, wherein the method for opening service rights to items, and obtaining service information further comprises:
after entering the opened service, the administrator adds a new space and configures space information: mirror image, white list and resource information, different contents are separated according to space to distinguish resources.
3. The quick orchestration service method based on the Kubernetes container environment according to claim 2, further comprising:
Initializing service arrangement;
Storing the stored project service arrangement configuration information in a service arrangement configuration table of a database server, and converting each task into a yml-format task script by a script code generator based on the configuration information by a background service program module.
4. A method of fast orchestration service based on a Kubernetes container environment according to claim 3, wherein the initialization comprises the following operations:
Judging the current state, triggering the service scheduling execution when the user calls the task Job with no state load Deployment or no state load StatefulSet, and triggering the service scheduling execution when the timing rule is met after the user calls the task CronJob.
5. The rapid orchestration service method according to claim 4, wherein the method comprises the steps of,
Selecting and editing the saved service arrangement configuration, wherein the editing comprises at least one of the following steps: modifying task sequence, task configuration information, and adding and deleting tasks;
Wherein each modification of the service orchestration configuration is stored in version in a service orchestration configuration table established by the database server.
6. The rapid orchestration service method according to any one of claims 1-5, wherein the Kubernetes container environment comprises:
the front end module is used for providing a man-machine interaction interface;
the database server is used for storing data information;
The pipeline server is used for creating and executing continuous integration and continuous deployment service arrangement and pushing the products to the product library;
the product library is used for storing War packages and a Docker mirror image;
gitlab, open source code hosting software, code hosting;
The code warehouse is used for storing project source codes;
the back-end management platform is used for integrating the core center of the resource and is responsible for connecting the front-end, the server of the pipeline, the server of the product library and the database.
7. A fast orchestration service system based on a Kubernetes container environment, comprising:
The definition module is used for defining a service arrangement template; defining a service orchestration task template, analyzing a template application scene, analyzing a system and a tool related to a research and development process, and extracting specific configuration of a task in different projects as a parameter of the task;
The first configuration module is used for project service arrangement, nginx configuration, parameter configuration, environment configuration and initialization; the analytics service is Deployment stateless load or StatefulSet stateful load or task Job or timing task CronJob;
the analysis module is used for analyzing whether storage is needed or not and the storage mode adopted when the storage is needed;
the second configuration module is used for configuring the dependence relationship of a service arrangement template, the service arrangement template relates to a plurality of services, analyzing whether the plurality of services have the dependence relationship, further analyzing the ordering of the dependence relationship, and analyzing the establishment mechanism of the dependence relationship;
the triggering module is used for calling triggering arrangement;
Further comprises:
deploying environment, creating clusters and nodes; defining a region;
creating tenant information;
Performing authorization association on the tenant and the cluster;
Adding an administrator under the tenant;
Adding items to an administrator, and configuring item information, item personnel information and rights;
opening service rights for the project and acquiring service information;
Newly adding an application, and isolating service arrangement according to application classification;
Newly adding common config information, secret information and stored PVC information;
Newly creating service arrangement under the created cluster, tenant, area and project, and filling in global configuration of the service arrangement;
performing task configuration on a service arrangement stage of service arrangement, wherein the task configuration comprises log configuration;
Saving service arrangement information of the project;
Editing the saved service arrangement configuration after being selected, modifying task sequence, task configuration information and adding and deleting tasks; each modification of the service orchestration configuration is stored in a service orchestration configuration table established by the database server according to versions, and the historical versions are selected to check specific configuration information so as to support version rollback.
8. A fast orchestration service device based on a Kubernetes container environment, the device comprising a processor and a memory; the memory is configured to store instructions that, when executed by the processor, cause the apparatus to implement a fast orchestration service method based on a Kubernetes container environment according to any one of claims 1 to 6.
9. A computer readable storage medium storing computer instructions which, when read by a computer in the storage medium, the computer runs a fast orchestration service method according to any one of claims 1-6, based on a Kubernetes container environment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111355254.1A CN114064213B (en) | 2021-11-16 | 2021-11-16 | Quick arranging service method and system based on Kubernets container environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111355254.1A CN114064213B (en) | 2021-11-16 | 2021-11-16 | Quick arranging service method and system based on Kubernets container environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114064213A CN114064213A (en) | 2022-02-18 |
| CN114064213B true CN114064213B (en) | 2024-05-31 |
Family
ID=80272696
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111355254.1A Active CN114064213B (en) | 2021-11-16 | 2021-11-16 | Quick arranging service method and system based on Kubernets container environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114064213B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114924833B (en) * | 2022-05-06 | 2024-05-17 | 华东师范大学 | User-noninductive micro-service container deployment method and deployment device thereof |
| CN116074063B (en) * | 2022-12-29 | 2024-06-07 | 中国联合网络通信集团有限公司 | Method, device, equipment and storage medium for realizing service deployment and private network isolation |
| CN116150116B (en) * | 2023-04-12 | 2023-07-04 | 阿里云计算有限公司 | File system sharing method and device, electronic equipment and storage medium |
| CN118158120A (en) * | 2024-01-08 | 2024-06-07 | 广州市玄武无线科技股份有限公司 | Centralized management cloud service arrangement method and system and electronic equipment |
| CN117707609B (en) * | 2024-02-06 | 2024-04-30 | 云账户技术(天津)有限公司 | Method and device for managing script tasks based on container arrangement management tool |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108681451A (en) * | 2018-05-14 | 2018-10-19 | 浪潮软件集团有限公司 | Visual kubernets micro-service arrangement implementation method |
| CN110245003A (en) * | 2019-06-06 | 2019-09-17 | 中信银行股份有限公司 | A kind of machine learning uniprocessor algorithm arranging system and method |
| CN110262806A (en) * | 2019-06-20 | 2019-09-20 | 杭州泰然鲸数云计算有限公司 | A kind of DevOps system for supporting automation services layout |
| CN110704164A (en) * | 2019-09-30 | 2020-01-17 | 珠海市新德汇信息技术有限公司 | Cloud native application platform construction method based on Kubernetes technology |
| CN111930388A (en) * | 2020-07-13 | 2020-11-13 | 银盛支付服务股份有限公司 | Continuous integration method and system based on k8s and docker container |
| CN112286628A (en) * | 2020-10-19 | 2021-01-29 | 烽火通信科技股份有限公司 | System for unifying nanotube Kubernetes heterogeneous applications and operation method |
| CN112527349A (en) * | 2020-12-02 | 2021-03-19 | 航天科工网络信息发展有限公司 | Dynamic deployment strategy optimization and continuous deployment service guarantee system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8607225B2 (en) * | 2010-12-28 | 2013-12-10 | Oracle International Corporation | Managed upgrades of components in an integrated software and hardware system |
| US10241778B2 (en) * | 2016-09-27 | 2019-03-26 | Ca, Inc. | Microservices version state visualization |
-
2021
- 2021-11-16 CN CN202111355254.1A patent/CN114064213B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108681451A (en) * | 2018-05-14 | 2018-10-19 | 浪潮软件集团有限公司 | Visual kubernets micro-service arrangement implementation method |
| CN110245003A (en) * | 2019-06-06 | 2019-09-17 | 中信银行股份有限公司 | A kind of machine learning uniprocessor algorithm arranging system and method |
| CN110262806A (en) * | 2019-06-20 | 2019-09-20 | 杭州泰然鲸数云计算有限公司 | A kind of DevOps system for supporting automation services layout |
| CN110704164A (en) * | 2019-09-30 | 2020-01-17 | 珠海市新德汇信息技术有限公司 | Cloud native application platform construction method based on Kubernetes technology |
| CN111930388A (en) * | 2020-07-13 | 2020-11-13 | 银盛支付服务股份有限公司 | Continuous integration method and system based on k8s and docker container |
| CN112286628A (en) * | 2020-10-19 | 2021-01-29 | 烽火通信科技股份有限公司 | System for unifying nanotube Kubernetes heterogeneous applications and operation method |
| CN112527349A (en) * | 2020-12-02 | 2021-03-19 | 航天科工网络信息发展有限公司 | Dynamic deployment strategy optimization and continuous deployment service guarantee system |
Non-Patent Citations (2)
| Title |
|---|
| "SGX-Aware Container Orchestration for Heterogeneous Clusters";Sebastien Vaucher;《2018 IEEE 38th International Conference on Distributed Computing Systems(ICDCS)》;20180723;第730-741页 * |
| "基于Kubernetes的容器云平台的设计与实现";兰智博;《中国优秀硕士学位论文全文数据库 信息科技辑》;20210415(2021年第04期);第I139-23页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114064213A (en) | 2022-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114064213B (en) | Quick arranging service method and system based on Kubernets container environment | |
| CN110912724B (en) | Parameter-driven automatic service arrangement method and device | |
| CN104317610B (en) | Method and device for automatic installation and deployment of hadoop platform | |
| US7496890B2 (en) | Generation of configuration instructions using an abstraction technique | |
| US8904341B2 (en) | Deriving grounded model of business process suitable for automatic deployment | |
| US20110004564A1 (en) | Model Based Deployment Of Computer Based Business Process On Dedicated Hardware | |
| WO2018036342A1 (en) | Csar-based template design visualization method and device | |
| US20020144256A1 (en) | Method of deployment for concurrent execution of multiple versions of an integration model on an integration server | |
| US20100280863A1 (en) | Automated Model Generation For Computer Based Business Process | |
| WO2009082381A1 (en) | Incorporating development tools in system for deploying computer based process on shared infrastructure | |
| CN111580926A (en) | Model publishing method, model deploying method, model publishing device, model deploying device, model publishing equipment and storage medium | |
| CN113986449A (en) | Container-oriented Linux kernel virtualization system and method | |
| US20110258620A1 (en) | Method and Apparatus for Making a BPM Application Available to Multiple Tenants | |
| CN109684028A (en) | A kind of method, device and equipment that operating system is separated with user data | |
| CN104699503A (en) | Method and device for replacing function execution logic in Android system | |
| CN111506314A (en) | Project development method, device, server and medium | |
| CN112363718A (en) | Industrial application integration system based on micro-service architecture | |
| CN117111960A (en) | Industrial field device monitoring system | |
| CN113568758B (en) | GPU resource pooling method, system, device and computer readable storage medium | |
| CN112564979B (en) | Execution method and device of construction task, computer equipment and storage medium | |
| CN114546563A (en) | Multi-tenant page access control method and system | |
| CN112199200B (en) | Resource scheduling method and device, computer equipment and storage medium | |
| US8914512B2 (en) | Method and system for defining additional resources in a user management system of a manufacturing execution system | |
| CN115390862A (en) | Application deployment method and device | |
| CN113835827A (en) | Application deployment method and device based on container Docker and electronic 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |