CN108964968B - Service access management method and system in container cloud environment - Google Patents
Service access management method and system in container cloud environment Download PDFInfo
- Publication number
- CN108964968B CN108964968B CN201810258545.0A CN201810258545A CN108964968B CN 108964968 B CN108964968 B CN 108964968B CN 201810258545 A CN201810258545 A CN 201810258545A CN 108964968 B CN108964968 B CN 108964968B
- Authority
- CN
- China
- Prior art keywords
- service
- service instance
- container
- kubernets
- instance
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5045—Making service definitions prior to deployment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a service access management method and system in a container cloud environment. The method comprises the following steps: obtaining a service mirror image required by service instance operation, compiling and uploading a yaml file containing required container resources, and converting the uploaded yaml file into container resources which can be managed by a kubernets container cloud platform by using a freemarker template engine. The invention provides a convenient access method for accessing the service of the cloud management platform by utilizing the kubernets container arrangement technology, can meet the increasing service access requirements of the cloud management platform, does not need to be redeveloped when accessing a new service, and only needs to make a service mirror image and define a kubernets yaml resource file. The cloud management platform supports the user-defined resource specification and the user-defined service access mode, can effectively improve the service access efficiency, and has the capability of rapidly releasing new services.
Description
Technical Field
The invention relates to the technical field of cloud services, in particular to a service access management method and system in a container cloud environment.
Background
In recent years, with the gradual popularization of cloud computing technology, more and more enterprises begin to choose to deploy cloud computing solutions, and public cloud manufacturers, private cloud manufacturers and mixed cloud manufacturers emerge like bamboo shoots in spring after rain. Due to uncertainty and dispute of public cloud security reliability and data ownership, enterprises with development capability can build own private cloud management platforms by combining the characteristics of the enterprises.
The cloud management platform can conveniently provide computing, network, storage resources and service components (such as redis, zookeeper and the like) for users, the management of the computing, network and storage resources is generally realized by using open-source openstack and kvm, the provision of the service components is not referred to by specific open-source technologies at present, and all public cloud manufacturers and private cloud manufacturers have service components (such as a cloud database redis in Ali, a cloud database mongodb and the like) which are commonly used, but are completely closed and opaque to the outside, and the types, functions and performances of the provided components are limited. When an enterprise builds a private cloud management platform, if a new service assembly is needed or the existing assembly cannot meet the requirement, the enterprise needs to be customized and developed again, and waste of human resources is caused.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present invention provide a service access management method and system in a container cloud environment. The technical scheme is as follows:
in one aspect, an embodiment of the present invention provides a service access management method in a container cloud environment, where the method includes:
acquiring a service mirror image required by service instance operation;
defining corresponding specification and service configuration information for the service instance;
compiling and uploading a yaml file containing required container resources, wherein the container resources are used for constructing a service instance of a kubernets platform;
converting the uploaded yaml file into a container resource which can be managed by a kubernetes container cloud platform by using a freemarker template engine;
constructing a required service instance by using the converted container resources, and defining a user access entrance for the constructed service instance;
and detecting the constructed service instance, and issuing a corresponding service instance on a kubernets container cloud platform after the detection is passed.
In the above service access management method according to the embodiment of the present invention, the obtaining a service image required by service instance operation includes:
the required service image is downloaded from the official website,
alternatively, the desired service image is re-prepared based on the existing base image.
In the above service access management method according to the embodiment of the present invention, the writing of the yaml file including the required container resource includes:
the yaml file is directly written according to the yaml file format,
or filling the information of the container resource in a preset yaml file editing interface to form a corresponding yaml file.
In the foregoing service access management method according to the embodiment of the present invention, when defining a user access entry for a constructed service instance, the method further includes:
and associating other services on which the constructed service instance runs for the constructed service instance.
In the foregoing service access management method according to the embodiment of the present invention, before the kubernets container cloud platform issues the corresponding service instance, the method further includes:
defining corresponding service basic information for a service instance, wherein the service basic information comprises: at least one of name, version, icon, description information of the service.
In another aspect, an embodiment of the present invention provides a service access management system in a container cloud environment, including:
the acquisition module is used for acquiring a service mirror image required by service instance operation;
the definition module is used for defining corresponding specification and service configuration information for the service instance;
the processing module is used for compiling and uploading a yaml file containing required container resources, and the container resources are used for constructing a service instance of the kubernets platform;
the processing module is also used for converting the uploaded yaml file into a container resource which can be managed by a kubernets container cloud platform by using a freemarker template engine;
the building module is used for building a required service instance by utilizing the converted container resources and defining a user access entrance for the built service instance;
the processing module is further used for detecting the constructed service instance and issuing the corresponding service instance on the kubernets container cloud platform after the detection is passed.
In the service access management system according to the above-mentioned embodiment of the present invention, the obtaining module is further configured to download a required service image from an official website,
alternatively, the desired service image is re-prepared based on the existing base image.
In the service access management system according to the above embodiment of the present invention, the processing module is further configured to write a yaml file directly according to a yaml file format,
or filling the information of the container resource in a preset yaml file editing interface to form a corresponding yaml file.
In the service access management system according to the embodiment of the present invention, when defining the user access entry for the constructed service instance, the processing module is further configured to associate, for the constructed service instance, another service on which the operation depends.
In the service access management system according to the embodiment of the present invention, before the cloud platform of the kubernets container issues the corresponding service instance, the definition module is further configured to define corresponding service basic information for the service instance, where the service basic information includes: at least one of name, version, icon, description information of the service.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
the embodiment of the invention provides a convenient access method for accessing the service of the cloud management platform by utilizing the kubernets container arrangement technology, can meet the increasing service access requirements of the cloud management platform, does not need to be redeveloped when accessing a new service, and only needs to make a service mirror image and define a kubernets yaml resource file. The cloud management platform supports the user-defined resource specification and the user-defined service access mode, can effectively improve the service access efficiency, and has the capability of rapidly releasing new services.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a service access management method in a container cloud environment according to an embodiment of the present invention;
fig. 2 is a diagram illustrating an example of obtaining a service image according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a specification of a service instance and exemplary service configuration information according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an example of writing a xml file according to an embodiment of the present invention;
FIG. 5 is a diagram illustrating a writing example of another xml file according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a example of uploading a yaml file according to an embodiment of the present invention;
FIG. 7 is a diagram illustrating an example of a service instance user access portal definition provided in accordance with an embodiment of the present invention;
FIG. 8 is a diagram illustrating an example of basic service information of a service instance according to an embodiment of the present invention;
FIG. 9 is a diagram illustrating an example of a service instance publishing process provided by an embodiment of the present invention;
fig. 10 is a diagram illustrating an example of a user applying for a service according to an embodiment of the present invention;
FIG. 11 is a diagram illustrating an example of access after activation of a service instance according to an embodiment of the present invention;
fig. 12 is a schematic structural diagram of a service access management system in a container cloud environment according to a second embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
Example one
The embodiment of the invention provides a service access management method in a container cloud environment, which is suitable for a Kubernets container cloud platform, and referring to fig. 1, the method can comprise the following steps:
step S11, obtain the service image required by the service instance running.
In this embodiment, one service instance is a set of a plurality of resource objects, and adding a service instance in the container cloud platform enables new services to be accessed for the container cloud platform. Service instances are operated in a kubernets container cluster, and the operation of the container needs to depend on images, so that corresponding service images need to be constructed firstly. Among them, Kubernetes is an open source platform for automated container operations including deployment, scheduling, and inter-node cluster extension.
Specifically, the step S11 can be implemented as follows:
the required service image is downloaded from an official website or is prepared anew based on an existing base image.
In this embodiment, the image may be downloaded from an official party, or may be completely reproduced based on the basic image, and the container runtime may receive environment variables transmitted by kubernets, so that it is necessary to consider which environment variables need to be transferred when the image is generated, and the container replaces configuration items of the service through shell scripts before starting. After the mirror image is manufactured, the mirror image needs to be pushed to a mirror image warehouse associated with the kubernetes cluster, so that the mirror image can be normally pulled when the service instance is started. Fig. 2 is an illustration of a redis service instance as an example, and a redis mirror is created and pushed to a mirror repository in fig. 2.
Step S12, defining corresponding specification and service configuration information for the service instance;
in this embodiment, each service uses different CPUs, memories and storages, and multiple resource specifications can be flexibly formulated according to service and service usage scenarios, so that different selection spaces are provided for users. The specifications of the service instance such as CPU, memory, storage specification and the like and the service configuration information (such as the example of FIG. 3) can be flexibly customized to meet the requirements of users to the maximum extent. The fields to be displayed during user application and activation, the regular expressions, default values and verification specifications of the fields can be configured in service instance configuration, and the field configuration information can be transmitted to a freemarker template engine during service application or starting, and then the freemarker template engine analyzes and transmits the information to a container.
Step S13, compiling and uploading a yaml file containing the required container resources, wherein the container resources are used for constructing the service instance of the kubernets platform.
In this embodiment, yaml is a language that is used exclusively for writing configuration files, and is very compact and powerful, far more convenient than the json format. All resources managed by kubernets can be called resource objects, kubernets support the creation of resource objects (pod, deployment, replicationController, etc.) using yaml files, and a service instance is a collection of resource objects. The creation of a service instance is to convert the yaml file into a kubernets manageable resource object. In practical application, one yaml can be written for each kubernets resource type, and all resource types can also be written in one yaml file. The changed content in the Yaml file is replaced by a placeholder, and when the service is created, the freemarker template engine automatically replaces the placeholder with real data of an instance.
Specifically, the step S13 can be implemented as follows:
the yaml file is written directly in the yaml file format (see the example of figure 4),
or filling in the information of the container resource in a preset yaml file editing interface to form a corresponding yaml file (see the example of fig. 5).
In this embodiment, the tenant may implement access to the service through the system access interface, and for the operation administrator, may write a kubernets yaml resource file to implement fast access to the service. Because the display modes and the capabilities of different access means are different, support for different access modes is provided, and good use effect of various access modes can be ensured.
And step S14, converting the uploaded yaml file into a container resource which can be managed by a kubernets container cloud platform by using a freemarker template engine.
In the embodiment, a yaml file editing service component is used, and a freemarker template engine is combined to dynamically modify the yaml resource file, so that service instances meeting different requirements are created. Fig. 6 is an example of uploading a yaml file.
And step S15, constructing the required service instance by using the converted container resource, and defining a user access entry for the constructed service instance.
In this embodiment, the access portal, that is, the portal ultimately provided for the user to access, supports different protocols (http, tcp, udp), and fig. 7 is a defined example of the service instance user access portal.
Step S16, associate the constructed service instance with other services on which it operates.
In this embodiment, other services dependent on the services may be defined when the services are accessed, the dependencies between the services are decoupled, that is, the service dependencies may associate the services dependent on each other, for example, when a kafka cluster is accessed, a zookeeper cluster needs to be accessed at the same time, and at this time, the zookeeper cluster may be accessed first, and only the zookeeper cluster needs to be selected when the kafka cluster is accessed. It should be noted that not every service instance needs to depend on other services, and therefore, step S16 may be selected for use according to a specific service instance, which is not limited herein (for example, the redis service instance does not depend on other services, so it is not filled).
Step S17, defining corresponding service basic information for the service instance, where the service basic information includes: at least one of name, version, icon, description information of the service.
In this embodiment, the service basic information may include information such as name, version, icon, and description of the service, which is displayed on the service list interface, so that the user can roughly know about the service (for example, the example shown in fig. 8). When the service is created, the corresponding access service is selected, the product name, the product catalog, the icon and the remark information of the service are defined, and the icon which is accessed by the service is selected by default and can be modified.
And step S18, detecting the constructed service instance, and issuing a corresponding service instance on the kubernets container cloud platform after the detection is passed.
In this embodiment, the service can be created after the information filled in the above steps is stored, and the service access personnel and the tester can perform the function test first to verify whether the mirror image, configuration and yaml files have problems, and the current service can be issued after the verification is passed. It should be noted that when the component has a new characteristic, the service component can be upgraded without affecting the operation of the original service instance, the new service instance has a new characteristic, and the two version instances can operate simultaneously.
FIG. 9 shows that the service instance (redis service) is tested and then released on the platform for the user to apply. FIG. 10 is a user applying for a redis service, including filling in instance names, selecting a deployment mode, selecting an instance specification, and selecting a storage size. In fig. 11, the system provides an access address after the service instance (redis service) is activated, and the application program can access the service instance through the access address, namely, the user can use the service instance.
The embodiment of the invention provides a convenient access method for accessing the service of the cloud management platform by utilizing the kubernets container arrangement technology, can meet the increasing service access requirements of the cloud management platform, does not need to be redeveloped when accessing a new service, and only needs to make a service mirror image and define a kubernets yaml resource file. The cloud management platform supports the user-defined resource specification and the user-defined service access mode, can effectively improve the service access efficiency, and has the capability of rapidly releasing new services.
Example two
The embodiment of the invention provides a device. The service access management system in the container cloud environment performs the method described in the first embodiment, referring to fig. 12, and the system may include: an acquisition module 100, a definition module 200, a processing module 300, and a construction module 400.
The obtaining module 100 is configured to obtain a service image required by service instance operation.
In this embodiment, one service instance is a set of a plurality of resource objects, and adding a service instance in the container cloud platform enables new services to be accessed for the container cloud platform. Service instances are operated in a kubernets container cluster, and the operation of the container needs to depend on images, so that corresponding service images need to be constructed firstly. Among them, Kubernetes is an open source platform for automated container operations including deployment, scheduling, and inter-node cluster extension.
The definition module 200 is configured to define corresponding specification and service configuration information for the service instance.
In this embodiment, each service uses different CPUs, memories and storages, and multiple resource specifications can be flexibly formulated according to service and service usage scenarios, so that different selection spaces are provided for users. The specifications of the service instance such as CPU, memory, storage specification and the like and the service configuration information (such as the example of FIG. 3) can be flexibly customized to meet the requirements of users to the maximum extent. The fields to be displayed during user application and activation, the regular expressions, default values and verification specifications of the fields can be configured in service instance configuration, and the field configuration information can be transmitted to a freemarker template engine during service application or starting, and then the freemarker template engine analyzes and transmits the information to a container.
And the processing module 300 is used for compiling and uploading a yaml file containing the required container resources, and the container resources are used for constructing the service instance of the kubernets platform.
In this embodiment, yaml is a language that is used exclusively for writing configuration files, and is very compact and powerful, far more convenient than the json format. All resources managed by kubernets can be called resource objects, kubernets support the creation of resource objects (pod, deployment, replicationController, etc.) using yaml files, and a service instance is a collection of resource objects. The creation of a service instance is to convert the yaml file into a kubernets manageable resource object. In practical application, one yaml can be written for each kubernets resource type, and all resource types can also be written in one yaml file. The changed content in the Yaml file is replaced by a placeholder, and when the service is created, the freemarker template engine automatically replaces the placeholder with real data of an instance.
The processing module 300 is further configured to convert the uploaded yaml file into a container resource manageable by a kubernets container cloud platform by using a freemarker template engine.
In the embodiment, a yaml file editing service component is used, and a freemarker template engine is combined to dynamically modify the yaml resource file, so that service instances meeting different requirements are created.
And the building module 400 is used for building the required service instance by using the converted container resource and defining a user access entrance for the built service instance.
In this embodiment, the access portal, i.e. the portal ultimately provided for user access, supports different protocols (http, tcp, udp).
The processing module 300 is further configured to detect the constructed service instance, and publish the corresponding service instance on the kubernets container cloud platform after the detection is passed.
In this embodiment, the service can be created after the information filled in the above steps is stored, and the service access personnel and the tester can perform the function test first to verify whether the mirror image, configuration and yaml files have problems, and the current service can be issued after the verification is passed. It should be noted that when the component has a new characteristic, the service component can be upgraded without affecting the operation of the original service instance, the new service instance has a new characteristic, and the two version instances can operate simultaneously.
In particular, the acquisition module 100, is also used to download the required service image from the official website,
alternatively, the desired service image is re-prepared based on the existing base image.
In this embodiment, the image may be downloaded from an official party, or may be completely reproduced based on the basic image, and the container runtime may receive environment variables transmitted by kubernets, so that it is necessary to consider which environment variables need to be transferred when the image is generated, and the container replaces configuration items of the service through shell scripts before starting. After the mirror image is manufactured, the mirror image needs to be pushed to a mirror image warehouse associated with the kubernetes cluster, so that the mirror image can be normally pulled when the service instance is started.
In particular, the processing module 300, is further configured to write the yaml file directly in the yaml file format,
or filling the information of the container resource in a preset yaml file editing interface to form a corresponding yaml file.
In this embodiment, the tenant may implement access to the service through the system access interface, and for the operation administrator, may write a kubernets yaml resource file to implement fast access to the service. Because the display modes and the capabilities of different access means are different, support for different access modes is provided, and good use effect of various access modes can be ensured.
Optionally, when defining a user access entry for the constructed service instance, the processing module 300 is further configured to associate, for the constructed service instance, other services on which the constructed service instance depends.
In this embodiment, other services dependent on the services may be defined when the services are accessed, the dependencies between the services are decoupled, that is, the service dependencies may associate the services dependent on each other, for example, when a kafka cluster is accessed, a zookeeper cluster needs to be accessed at the same time, and at this time, the zookeeper cluster may be accessed first, and only the zookeeper cluster needs to be selected when the kafka cluster is accessed.
Optionally, before the cloud platform of the kubernets container publishes the corresponding service instance, the defining module 200 is further configured to define corresponding service basic information for the service instance, where the service basic information includes: at least one of name, version, icon, description information of the service.
In this embodiment, the service basic information may include information such as name, version, icon, and description of the service, which is displayed on the service list interface, so that the user can roughly know about the service. When the service is created, the corresponding access service is selected, the product name, the product catalog, the icon and the remark information of the service are defined, and the icon which is accessed by the service is selected by default and can be modified.
The embodiment of the invention provides a convenient access method for accessing the service of the cloud management platform by utilizing the kubernets container arrangement technology, can meet the increasing service access requirements of the cloud management platform, does not need to be redeveloped when accessing a new service, and only needs to make a service mirror image and define a kubernets yaml resource file. The cloud management platform supports the user-defined resource specification and the user-defined service access mode, can effectively improve the service access efficiency, and has the capability of rapidly releasing new services.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
It should be noted that: in the service access management system in the container cloud environment provided in the foregoing embodiment, when the service access management method in the container cloud environment is implemented, only the division of the functional modules is illustrated, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the service access management system in the container cloud environment and the service access management method in the container cloud environment provided by the above embodiments belong to the same concept, and specific implementation processes thereof are detailed in the method embodiments and are not described herein again.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (10)
1. A service access management method in a container cloud environment is characterized by comprising the following steps:
acquiring a service mirror image required by service instance operation;
defining corresponding specification and service configuration information for the service instance;
compiling and uploading a yaml file containing required container resources, wherein the container resources are used for constructing a service instance of a kubernets platform;
converting the uploaded yaml file into a container resource which can be managed by a kubernetes container cloud platform by using a freemarker template engine;
constructing a required service instance by using the converted container resources, and defining a user access entrance for the constructed service instance;
and detecting the constructed service instance, and issuing a corresponding service instance on a kubernets container cloud platform after the detection is passed.
2. The method of claim 1, wherein obtaining the service image required by the service instance to run comprises:
the required service image is downloaded from the official website,
alternatively, the desired service image is re-prepared based on the existing base image.
3. The method of claim 1, wherein said authoring a yaml file containing the required container resources comprises:
the yaml file is directly written according to the yaml file format,
or filling the information of the container resource in a preset yaml file editing interface to form a corresponding yaml file.
4. The method of claim 1, wherein when defining a user access portal for a built service instance, the method further comprises:
and associating other services on which the constructed service instance runs for the constructed service instance.
5. The method of claim 1, further comprising, prior to the kubernets container cloud platform publishing the corresponding service instance:
defining corresponding service basic information for a service instance, wherein the service basic information comprises: at least one of name, version, icon, description information of the service.
6. A service access management system in a container cloud environment, comprising:
the acquisition module is used for acquiring a service mirror image required by service instance operation;
the definition module is used for defining corresponding specification and service configuration information for the service instance;
the processing module is used for compiling and uploading a yaml file containing required container resources, and the container resources are used for constructing a service instance of the kubernets platform;
the processing module is also used for converting the uploaded yaml file into a container resource which can be managed by a kubernets container cloud platform by using a freemarker template engine;
the building module is used for building a required service instance by utilizing the converted container resources and defining a user access entrance for the built service instance;
the processing module is further used for detecting the constructed service instance and issuing the corresponding service instance on the kubernets container cloud platform after the detection is passed.
7. The system of claim 6, wherein the acquisition module is further configured to download a desired service image from an official website,
alternatively, the desired service image is re-prepared based on the existing base image.
8. The system of claim 6, wherein the processing module is further configured to write yaml files directly in a yaml file format,
or filling the information of the container resource in a preset yaml file editing interface to form a corresponding yaml file.
9. The system of claim 6, wherein the processing module, when defining a user access portal for the built service instance, is further configured to associate other services on which the built service instance depends for its operation.
10. The system of claim 6, wherein before the kubernets container cloud platform publishes the corresponding service instance, the definition module is further configured to define corresponding service basic information for the service instance, and the service basic information includes: at least one of name, version, icon, description information of the service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810258545.0A CN108964968B (en) | 2018-03-27 | 2018-03-27 | Service access management method and system in container cloud environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810258545.0A CN108964968B (en) | 2018-03-27 | 2018-03-27 | Service access management method and system in container cloud environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108964968A CN108964968A (en) | 2018-12-07 |
| CN108964968B true CN108964968B (en) | 2022-01-11 |
Family
ID=64495657
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810258545.0A Active CN108964968B (en) | 2018-03-27 | 2018-03-27 | Service access management method and system in container cloud environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108964968B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11115278B2 (en) * | 2019-02-25 | 2021-09-07 | Cisco Technology, Inc. | Learning by inference from brownfield deployments |
| CN110333932A (en) * | 2019-06-13 | 2019-10-15 | 上海金融期货信息技术有限公司 | Service orchestration and relationship managing method and system based on container cloud |
| CN110795068B (en) * | 2019-08-08 | 2023-04-07 | 内蒙古大学 | Method and system for automatically generating executable scheme from user requirement in industry cloud environment |
| CN110806880A (en) * | 2019-11-04 | 2020-02-18 | 紫光云技术有限公司 | High-reliability, high-performance and high-efficiency container cluster deployment method |
| CN110888736A (en) * | 2019-11-15 | 2020-03-17 | 北京浪潮数据技术有限公司 | Application management method and system based on container cloud platform and related components |
| US11153279B2 (en) | 2020-01-30 | 2021-10-19 | Hewlett Packard Enterprise Development Lp | Locally representing a remote application programming interface (API) endpoint within an application platform |
| CN113301068A (en) * | 2020-04-07 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Method, system, device, cluster and medium for managing cluster resources |
| CN112328390B (en) * | 2020-10-13 | 2024-02-09 | 北京华胜天成科技股份有限公司 | Method, device and storage medium for automatically implementing cloud management platform |
| CN112395048B (en) * | 2020-11-27 | 2022-04-29 | 恒生电子股份有限公司 | Component management method and device and electronic equipment |
| CN112804097B (en) * | 2021-01-04 | 2023-06-27 | 北京金山云网络技术有限公司 | Private cloud deployment method, device and server |
| CN113377620A (en) * | 2021-06-24 | 2021-09-10 | 上海天壤智能科技有限公司 | Automatic system self-checking method and system based on Kubernetes |
| CN113434251B (en) * | 2021-06-25 | 2023-05-02 | 竹间智能科技（上海）有限公司 | Cross-platform deployment method, device and equipment for service modules |
| CN114039974A (en) * | 2021-10-20 | 2022-02-11 | 支付宝(杭州)信息技术有限公司 | Cloud container generation method and device, storage medium and electronic equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546571A (en) * | 2013-10-29 | 2014-01-29 | 北京华胜天成科技股份有限公司 | Platform-as-a-service (PaaS) realizing method and device |
| CN103685568A (en) * | 2013-12-31 | 2014-03-26 | 曙光云计算技术有限公司 | Platform service application deployment method and system of PAAS (Platform As A Service) platform under cloud computing environment |
| CN105245373A (en) * | 2015-10-12 | 2016-01-13 | 天津市普迅电力信息技术有限公司 | Construction and operation method of container cloud platform system |
| CN105574135A (en) * | 2015-12-14 | 2016-05-11 | 中电科华云信息技术有限公司 | Universal access method and universal access system for supporting heterogeneous services |
| CN107483225A (en) * | 2017-07-04 | 2017-12-15 | 北京奥鹏远程教育中心有限公司 | Docker application process and device in education cloud platform |
| CN107579931A (en) * | 2017-09-08 | 2018-01-12 | 杭州云象网络技术有限公司 | A kind of block chain based on Kubernetes is Service Source adaptation method |
| CN107766049A (en) * | 2017-10-19 | 2018-03-06 | 方欣科技有限公司 | One kind is based on docker cloud computing technology smart office system construction platforms |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180013636A1 (en) * | 2016-07-07 | 2018-01-11 | Cisco Technology, Inc. | System and method for scaling application containers in cloud environments |
-
2018
- 2018-03-27 CN CN201810258545.0A patent/CN108964968B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546571A (en) * | 2013-10-29 | 2014-01-29 | 北京华胜天成科技股份有限公司 | Platform-as-a-service (PaaS) realizing method and device |
| CN103685568A (en) * | 2013-12-31 | 2014-03-26 | 曙光云计算技术有限公司 | Platform service application deployment method and system of PAAS (Platform As A Service) platform under cloud computing environment |
| CN105245373A (en) * | 2015-10-12 | 2016-01-13 | 天津市普迅电力信息技术有限公司 | Construction and operation method of container cloud platform system |
| CN105574135A (en) * | 2015-12-14 | 2016-05-11 | 中电科华云信息技术有限公司 | Universal access method and universal access system for supporting heterogeneous services |
| CN107483225A (en) * | 2017-07-04 | 2017-12-15 | 北京奥鹏远程教育中心有限公司 | Docker application process and device in education cloud platform |
| CN107579931A (en) * | 2017-09-08 | 2018-01-12 | 杭州云象网络技术有限公司 | A kind of block chain based on Kubernetes is Service Source adaptation method |
| CN107766049A (en) * | 2017-10-19 | 2018-03-06 | 方欣科技有限公司 | One kind is based on docker cloud computing technology smart office system construction platforms |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108964968A (en) | 2018-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108964968B (en) | Service access management method and system in container cloud environment | |
| CN107766126B (en) | Container mirror image construction method, system and device and storage medium | |
| CN108279932B (en) | Method and device for dynamically configuring user interface of mobile terminal | |
| CN107615239B (en) | Infrastructure for hosting and publishing software packages | |
| US9582268B2 (en) | Automatic communications graphing for a source application | |
| US9367305B1 (en) | Automatic container definition | |
| US20190272227A1 (en) | Software testing and verification | |
| US10366112B2 (en) | Compiling extract, transform, and load job test data cases | |
| US11667033B2 (en) | Systems and methods for robotic process automation | |
| CN110912724A (en) | Parameter-driven automatic service arrangement method and device | |
| CN111399840B (en) | Module development method and device | |
| US20170048331A1 (en) | Platform runtime abstraction | |
| CN113885849A (en) | Application development method and device based on industrial internet platform and terminal equipment | |
| US20230401058A1 (en) | Semantic functional wrappers of services | |
| US10459698B2 (en) | Framework for generating adapters in an integrated development environment | |
| CN113094028A (en) | Windows desktop program development framework, method and related components | |
| CN110083366B (en) | Application running environment generation method and device, computing equipment and storage medium | |
| US9934019B1 (en) | Application function conversion to a service | |
| US10802810B2 (en) | Consuming persistent library bundles | |
| US20220365758A1 (en) | Tool for Introspection in Object-Oriented Source Code | |
| CN114115982A (en) | Code issuing method, device, equipment and storage medium | |
| CN115525396A (en) | Application management method and device based on cloud protogenesis | |
| CN114201174A (en) | Construction method and device of hybrid mobile application, electronic equipment and storage medium | |
| CN114077437A (en) | Integrated management method, device and system for artificial intelligence application | |
| CN113342633B (en) | Performance test method and device |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 518000 building 501, 502, 601, 602, building D, wisdom Plaza, Qiaoxiang Road, Gaofa community, Shahe street, Nanshan District, Shenzhen City, Guangdong Province Applicant after: China Southern Power Grid Shenzhen Digital Power Grid Research Institute Co.,Ltd. Address before: 518000, two floor, fragrant building, 2075 Lianhua Road, Futian District, Shenzhen, Guangdong. Applicant before: SHENZHEN COMTOP INFORMATION TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 518000 building 501, 502, 601, 602, building D, wisdom Plaza, Qiaoxiang Road, Gaofa community, Shahe street, Nanshan District, Shenzhen City, Guangdong Province Patentee after: China Southern Power Grid Digital Platform Technology (Guangdong) Co.,Ltd. Address before: 518000 building 501, 502, 601, 602, building D, wisdom Plaza, Qiaoxiang Road, Gaofa community, Shahe street, Nanshan District, Shenzhen City, Guangdong Province Patentee before: China Southern Power Grid Shenzhen Digital Power Grid Research Institute Co.,Ltd. |