CN113157339B

CN113157339B - Application service extension method, system, storage medium and device based on OSB

Info

Publication number: CN113157339B
Application number: CN202110438778.0A
Authority: CN
Inventors: 黄林; 林健; 谢冬鸣
Original assignee: Dongyun Ruilian Wuhan Computing Technology Co ltd
Current assignee: Dongyun Ruilian Wuhan Computing Technology Co ltd
Priority date: 2021-04-23
Filing date: 2021-04-23
Publication date: 2023-07-18
Anticipated expiration: 2041-04-23
Also published as: CN113157339A

Abstract

The invention relates to the technical field of cloud computing, and discloses an application service extension method, an application service extension system, a storage medium and an application service extension device based on OSB. In the invention, firstly, the service configuration parameters of the target application service are acquired, the catalog packet corresponding to the target application service is determined, and the service configuration parameters and the catalog packet are sent to the container cluster, so that the container cluster generates the containerized target application service. Obviously, the invention provides a mode for quickly creating the containerized application service, simplifies the creation flow of the application service, thereby achieving the multi-type easy expansibility of the application service and solving the technical problem of poor expansibility of different application services at present.

Description

Application service extension method, system, storage medium and device based on OSB

Technical Field

The present invention relates to the field of cloud computing technologies, and in particular, to an OSB-based application service extension method, system, storage medium, and apparatus.

Background

With the continuous development of cloud computing technology, enterprise applications gradually trend toward transformation of micro-service architecture. Meanwhile, the containerized application service is designed by understanding the business architecture, so performance, availability, expandability, security and the like are more concerned when designing the containerized service.

Among them, OSB (Open Service Broker, open service agent) is a common protocol in the micro-service domain, and can provide standardized portals for the servicing of infrastructure software or application software. However, OSB is only one interface, and its specific technical implementation is diverse. The types of micro services are increasing, along with the endless layering of various clouding services. At present, no good technical scheme is available for achieving the easy expansibility of the application service, and the current application service has poor expansibility.

The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present invention and is not intended to represent an admission that the foregoing is prior art.

Disclosure of Invention

The invention mainly aims to provide an application service expansion method, an application service expansion system, a storage medium and an application service expansion device based on OSB, and aims to solve the technical problem that the expandability of the current application service is poor.

In order to achieve the above object, the present invention provides an OSB-based application service extension method, which includes the steps of:

acquiring service configuration parameters of a target application service;

determining a catalog packet corresponding to the target application service;

and sending the service configuration parameters and the directory package to a container cluster so that the container cluster generates the containerized target application service.

Preferably, after the service configuration parameter of the target application service is obtained, the OSB-based application service extension method further includes:

analyzing the service configuration parameters to obtain a package identifier;

correspondingly, the determining the directory package corresponding to the target application service specifically includes:

and determining a catalog package corresponding to the target application service in a package manager according to the package identifier.

Preferably, before the obtaining the service configuration parameter of the target application service, the OSB-based application service extension method further includes:

when a registration request is received, acquiring registration parameters;

reading a service access address from the registration parameter;

and acquiring service configuration parameters of the target application service according to the service access address in the packet manager.

Preferably, after the sending the service configuration parameter and the directory package to a container cluster, so that the container cluster generates the containerized target application service, the OSB-based application service extension method further includes:

when a service binding request is received, a binding identification is acquired;

transmitting the binding identification to the container cluster, so that the container cluster determines access credentials of the corresponding target application service according to the binding identification, and returns the access credentials to a client;

Wherein the access credential is for the client to connect to the target application service.

receiving a catalog packet corresponding to a target application service;

storing the catalog package in a package manager and updating a service list;

correspondingly, the obtaining the service configuration parameters of the target application service specifically includes:

reading service configuration parameters of the target application service from the updated service list;

wherein the catalog package is a package conforming to the format of the package manager of the container cluster;

wherein the target application service is any type of application service;

the target application service is MySQL service or Redis service.

when a resource expansion request is received, service positioning information and expansion parameters corresponding to the application service to be expanded are acquired;

Stopping running the application service to be expanded according to the service positioning information, performing resource expansion operation on the application service to be expanded according to the expansion parameters, and starting the containerized application service based on the resource specification corresponding to the resource expansion operation.

In addition, to achieve the above object, the present invention also proposes a network device comprising a memory, a processor and an OSB-based application service extension program stored on the memory and executable on the processor, the OSB-based application service extension program being configured to implement the steps of the OSB-based application service extension method as described above.

In addition, in order to achieve the above object, the present invention also proposes an application service system, which includes a client, a container cluster, and a network device as described above;

the client communicates with the network device via OSB protocol, and the network device communicates with the container cluster.

In addition, to achieve the above object, the present invention also proposes a storage medium having stored thereon an OSB-based application service extension program, which when executed by a processor, implements the steps of the OSB-based application service extension method as described above.

In addition, in order to achieve the above object, the present invention also proposes an OSB-based application service extension apparatus, which includes:

the parameter acquisition module is used for acquiring service configuration parameters of the target application service;

the catalog packet determining module is used for determining a catalog packet corresponding to the target application service;

and the service generation module is used for sending the service configuration parameters and the directory package to a container cluster so as to enable the container cluster to generate the containerized target application service.

In the invention, firstly, the service configuration parameters of the target application service are acquired, the catalog packet corresponding to the target application service is determined, and the service configuration parameters and the catalog packet are sent to the container cluster, so that the container cluster generates the containerized target application service. Obviously, the invention provides a mode for quickly creating the containerized application service, and simplifies the creation flow of the application service, thereby achieving the easy expansibility of the application service and solving the technical problem of poor expansibility of the current application service.

Drawings

FIG. 1 is a schematic diagram of a network device architecture of a hardware operating environment according to an embodiment of the present invention;

FIG. 2 is a flow chart of a first embodiment of an OSB-based application service extension method of the present invention;

FIG. 3 is a flow chart of a second embodiment of an OSB-based application service extension method of the present invention;

FIG. 4 is a flowchart of a third embodiment of an OSB-based application service extension method of the present invention;

FIG. 5 is a flowchart of a fourth embodiment of an OSB-based application service extension method of the present invention;

FIG. 6 is a flowchart of a fifth embodiment of an OSB-based application service extension method of the present invention;

fig. 7 is a block diagram illustrating a first embodiment of an OSB-based application service extension apparatus according to the present invention.

The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

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 invention.

Referring to fig. 1, fig. 1 is a schematic diagram of a network device structure of a hardware running environment according to an embodiment of the present invention.

As shown in fig. 1, the network device may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display (Display), the optional user interface 1003 may also include a standard wired interface as well as a wireless interface, and the wired interface of the user interface 1003 may be a universal serial bus (Universal Serial Bus, USB) interface in the present invention. The network interface 1004 may optionally include a standard wired interface as well as a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high speed random access memory (Random Access Memory, RAM); the Memory may be a stable Memory, such as a Non-volatile Memory (Non-volatile Memory), and specifically, a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.

Those skilled in the art will appreciate that the architecture shown in fig. 1 is not limiting of the network device and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

As shown in fig. 1, an operating system, a network communication module, a user interface module, and an OSB-based application service extension program may be included in a memory 1005, which is a type of computer storage medium.

In the network device shown in fig. 1, the network interface 1004 is mainly used for connecting to a background server, and performing data communication with the background server; the user interface 1003 is mainly used for connecting peripherals; the network device invokes the OSB-based application service extension program stored in the memory 1005 via the processor 1001 and performs the following operations:

acquiring service configuration parameters of a target application service;

determining a catalog packet corresponding to the target application service;

Further, the processor 1001 may call the OSB-based application service extension program stored in the memory 1005, and further perform the following operations:

Analyzing the service configuration parameters to obtain a package identifier;

accordingly, the following operations are also performed:

when a registration request is received, acquiring registration parameters;

reading a service access address from the registration parameter;

Receiving a catalog packet corresponding to a target application service;

storing the catalog package in a package manager and updating a service list;

accordingly, the following operations are also performed:

wherein the target application service is any type of application service;

the target application service is MySQL service or Redis service.

In this embodiment, firstly, a service configuration parameter of a target application service is obtained, a directory packet corresponding to the target application service is determined, and the service configuration parameter and the directory packet are sent to a container cluster, so that the container cluster generates a containerized target application service. Obviously, the embodiment provides a quick creation mode of the containerized application service, simplifies the creation flow of the application service, thereby achieving the easy expansibility of the application service and solving the technical problem of poor expansibility of the current application service.

Based on the above hardware structure, an embodiment of the OSB-based application service extension method of the present invention is presented.

Referring to fig. 2, fig. 2 is a flowchart of a first embodiment of an OSB-based application service extension method according to the present invention.

In a first embodiment, the OSB-based application service extension method includes the steps of:

step S10: and acquiring the service configuration parameters of the target application service.

It can be understood that the execution body of the embodiment is a network device, and an application service management platform may be carried on the network device, which may be simply referred to as a platform.

Of course, the platform may also be carried by multiple network devices, without limitation.

Further, the application service management platform may be built based on OSB, i.e. an OSB-based application service management platform.

In particular, OSB defines an HTTP (S) interface between the platform and the service proxy, noting that the role of the platform as expressed herein is carried on OSB-based clients, rather than OSB-based application service management platforms. The service agent is responsible for publishing a catalog of service products and service plans to the client and performing provisioning, binding, unbinding, and deconfiguration according to requests from OSB-based clients.

It should be understood that, in order to achieve the extensibility of the application service, this embodiment provides a kind of way to quickly create the containerized application service, so as to simplify the creation flow of the application service.

Specifically, the platform may first obtain the service configuration parameters of the target application service.

The target application service is the application service to be created, and can be recorded as application service a.

Step S20: and determining a directory package corresponding to the target application service.

The directory package for application service a may then be determined by querying.

Wherein the catalog package may be embodied as a Chart package.

Where Chart is a collection of files describing a set of related Kubernetes resources. Chart deploys files by creating them as a specific directory tree, packing them into versioned compression packages.

Among them, kubernetes is an open-source container orchestration engine that supports automated deployment, large-scale scalability, and application containerization management. When an application is deployed in a production environment, multiple instances of the application are typically deployed in order to load balance application requests. In Kubernetes, multiple containers may be created, one application instance running within each container, and then management, discovery, and access to the set of application instances is achieved through a built-in load balancing policy, without requiring complex manual configuration and handling by operation and maintenance personnel.

Step S30: and sending the service configuration parameters and the directory package to a container cluster so that the container cluster generates the containerized target application service.

It should be appreciated that the platform may send the service configuration parameters, catalog package, of application service a to the container cluster side, which may generate the containerized application service a so that the containerized application service may be quickly created.

Referring to fig. 3, fig. 3 is a schematic flow chart of a second embodiment of the OSB-based application service extension method according to the present invention, and the second embodiment of the OSB-based application service extension method according to the present invention is proposed based on the first embodiment shown in fig. 2.

In a second embodiment, after the step S10, the OSB-based application service extension method further includes:

step S101: and analyzing the service configuration parameters to obtain the package identification.

It can be understood that the first embodiment of the OSB-based application service extension method of the present invention mainly relates to a creation link of an application service, and this embodiment will further refine this creation link.

Specifically, the application service to be created here takes MySQL service as an example, and service configuration parameters may be parsed first to obtain a package identifier of a directory package corresponding to the MySQL service.

Wherein MySQL is a relational database management system.

Wherein the packet identification may be embodied as a packet number.

Correspondingly, the step S20 specifically includes:

step S201: and determining a catalog package corresponding to the target application service in a package manager according to the package identifier.

It will be appreciated that after the number of MySQL application service packages in the package manager of the container cluster is obtained, the catalog package may be queried and obtained by the package number.

Wherein the platform comprises a packet manager.

The embodiment further provides a specific creation mode of the containerized application service.

Further, the service configuration parameters are exemplified as follows,

the service configuration parameters include a service_instance ID (instance ID, instance identifier) and a plane_id (package ID, package identifier) of the MySQL database service.

Wherein the services_instances are randomly assigned to identify the created application service. The service_id and the plan_id are service IDs and package IDs in a corresponding service list, the service_id is a service number of MySQL, and the plan_id is an ID corresponding to various modes, such as MySQL single-machine mode, mySQL master-slave mode and MySQL double-master mode. In this embodiment, mySQL single mode is used.

The service configuration parameters further include resource parameters required by the service containerization of the MySQL database and access passwords of the containerized MySQL database, and in this embodiment, the parameters include resource parameters cpu, memory and capability required by the container, and further include passwords of root users of the MySQL database.

In addition, if the MySQL master-slave mode is adopted, the number of slave nodes needs to be set.

Further, by analyzing the service configuration parameters created for the MySQL database service, a Chart package of MySQL is pulled from the Helm server.

The Helm is a package manager of the Kubernetes, and consists of a client component Helm and a server component Tiller, and can package and uniformly manage a group of Kubernetes resources.

Further, the Chart package may be rendered through the service configuration parameters, then the rendering result is submitted to the Kubernetes cluster, and finally the Kubernetes cluster creates the containerized MySQL database service.

Wherein the rendering result may be a YAML file.

The service configuration parameters may include a service_id and a plan_id, which are used to identify a database schema of a specific MySQL. After downloading the Chart package of the corresponding MySQL mode from the Helm server, the Chart package can be decompressed first, and YAML identifiable by the Kubernetes cluster is rendered and generated according to the cpu, memory and capability in the parameters, at the moment, the service_instance ID can be randomly filled in, and then submitted to the Kubernetes cluster.

Wherein the container cluster may be a Kubernetes cluster.

Further, to generate a containerized target application service, a corresponding containerized application service may be created by a Docker.

Specifically, after receiving the rendered YAML packet, the Kubernetes cluster distributes tasks to nodes of the cluster, pulls a corresponding containerized mirror image of MySQL by using a Docker tool, runs a MySQL container according to the YAML, and creates a containerized MySQL database application service.

Wherein MySQL is the target application service, and the specific type of the target application service is not limited herein.

In this embodiment, the creation operation of the containerized MySQL database service may be completed, and of course, the application service is not limited to be just MySQL. It can be seen that this embodiment simplifies the process of creating MySQL database services, greatly simplifying the process of creating application services. At the same time, the orchestration of containerized application services is also simplified.

Referring to fig. 4, fig. 4 is a schematic flow chart of a third embodiment of the OSB-based application service extension method according to the present invention, and the third embodiment of the OSB-based application service extension method according to the present invention is proposed based on the first embodiment shown in fig. 2.

In a third embodiment, before the step S10, the OSB-based application service extension method further includes:

step S01: when a registration request is received, registration parameters are acquired.

It can be understood that the third embodiment of the OSB-based application service extension method of the present invention mainly relates to the registration procedure of the application service, which occurs before the creation procedure.

Specifically, a registration request initiated by a user using an OSB protocol-based client may be received first, and the platform may obtain registration parameters.

Further, the registration parameters may be obtained by parsing the registration request.

Step S02: and reading a service access address from the registration parameter.

In a specific implementation, the relevant information of all application services can be obtained in the container cluster packet manager through one address information.

The service access address is a service address of an OSB-based application service management platform.

Further, the registration parameters include the service access address, and may also include whether the access mode is asynchronous or synchronous, and if not, may default to asynchronous.

Step S03: and acquiring service configuration parameters of the target application service according to the service access address in the packet manager.

For example, the service configuration parameters of MySQL database service may be acquired, but of course, not limited thereto, and the service configuration parameters of all application services may be acquired at once.

The target application service may be any application service.

Wherein, the service configuration parameters of all application services can be obtained in the packet manager according to the service access address.

In this embodiment, all application service lists can be obtained only by providing the access address of the OSB-based application service management platform, that is, the service access address, so that the usability of the multi-type application service is greatly improved, and a unified management platform is provided for the multi-type application service.

Therefore, the unified standard interface is used for interfacing the multi-type containerized application service, the expandability and the operability of different types of containerized application services are simplified, and meanwhile, the efficient manageability of the multi-type application service is improved.

Further, the REST API corresponding to the registration request is exemplified as follows,

GET http://192.168.1.2:30021/v2/catalog

further, the fourth embodiment of the OSB-based application service extension method of the present invention mainly relates to a registration procedure of an application service, and this embodiment will further refine the registration procedure.

In particular, the packet manager of the container cluster may be a Helm tool. In order to acquire application service information, i.e., service configuration parameters, an index file in a server is mainly read from a server of Helm, examples of which are as follows,

the service configuration parameter, i.e. index file, contains information such as service ID, package ID, etc.

Further, after the service access address is read, service configuration parameters of all application services can be obtained according to the service access address, and an application service list and all the configurable parameter information can be returned to the client operated by the user.

Wherein, the configurable parameter information can be recorded as parameters.

In this embodiment, the user can identify the information of all application services that can be currently applied, and the process can acquire the information of all application services only by providing the access address of the OSB management platform, so that the management efficiency of the application services is greatly improved, and meanwhile, the usability of the application services is also greatly improved.

Referring to fig. 5, fig. 5 is a schematic flow chart of a fourth embodiment of an OSB-based application service extension method according to the present invention, and the fourth embodiment of the OSB-based application service extension method according to the present invention is proposed based on the first embodiment shown in fig. 2.

In a fourth embodiment, after the step S30, the OSB-based application service extension method further includes:

step S40: when a service binding request is received, a binding identification is obtained.

It can be understood that the fourth embodiment of the OSB-based application service extension method of the present invention mainly relates to an access procedure of an application service, which occurs after the creation procedure.

It will be appreciated that, upon receipt of a service binding request issued by a client, binding parameters may be received simultaneously, examples being as follows,

the binding parameters include a service_instance ID, a service_binding ID, a service_id, a plan_id and other parameters.

The service_bindings ID is a binding ID, which may be referred to as a binding identifier, so that an access credential in a binding may be directly obtained when information is queried. Other parameters may or may not be filled in, here specific application parameters that are not used as a containerized MySQL database service are filled in, only as save parameters.

Step S50: and sending the binding identification to the container cluster, so that the container cluster determines the corresponding access credential of the target application service according to the binding identification, and returns the access credential to the client.

It should be appreciated that the present embodiment will parse the parameters in the binding and obtain the access credentials from the containerized MySQL database service.

In the access link, the embodiment can acquire the access certificate of the containerized MySQL database service by using a binding mechanism, thereby greatly improving the access effectiveness of the containerized application service and simplifying the flow of acquiring the access certificate.

Further, a specific implementation procedure may be adopted, for example, after the OSB-based application service management platform receives the binding request, the service_instance ID, the service_links ID, the service_id, and the plane_id in the parameters may be resolved first. Then, the corresponding secret of MySQL database service can be found in the Kubernetes container cluster according to the binding identification service_instance ID, and the access IP address (Internet Protocol Address ), port number, access password of root user, used resource cpu, memory and capability information of the containerized MySQL can be obtained therefrom, which return information is exemplified as follows,

The return information listed here is the access credential when the subsequent client accesses the target application service.

It can be seen that the access credentials may include an access IP address, and may also include a port number, an access password of the root user, a used resource cpu, a memory, and capability information.

Further, after the registration link of the MySQL service and the creation of the MySQL database and the access mechanism of the MySQL, the access information of the database of the containerized MySQL is finally obtained. The user may connect to MySQL service using the return address and port number in the return information as exemplified above.

And, the password of the root user can also be used to operate in MySQL service.

Further, another way may be to parse the binding parameters to obtain an index created by the application service. Then, a corresponding containerized application service can be found according to the application service index, and access credentials for the application service can be obtained from the application service. Finally, the access credentials are returned, through which the user can access the application service.

More specifically, in the process of acquiring MySQL access credentials from a containerized MySQL database service in a Kubernetes cluster, a service binding request sent on a WEB interface is received first, configuration parameters are analyzed, then a corresponding containerized MySQL database service is found from the Kubernetes cluster, and information such as an access IP address, a port number, a root user password, etc. of the MySQL database service is acquired from a secret of the MySQL database service, and is returned to the WEB interface, so that a user can view the access credentials on the WEB interface.

Referring to fig. 6, fig. 6 is a schematic flow chart of a fifth embodiment of an OSB-based application service extension method according to the present invention, and the fifth embodiment of the OSB-based application service extension method according to the present invention is proposed based on the first embodiment shown in fig. 2.

In a fifth embodiment, before the step S10, the OSB-based application service extension method further includes:

step S04: and receiving a catalog packet corresponding to the target application service.

It can be understood that the fifth embodiment of the OSB-based application service extension method of the present invention mainly relates to an extension mechanism of an application service, which occurs before the creation link.

Specifically, taking the Redis service as an example, in order to create the Redis service more flexibly and more in accordance with the requirements later, the type of the Redis service can be extended first. For example, a Chart packet of a Redis service, which is input externally, may be received first.

Wherein Redis is a high performance key-value storage system. It supports relatively more value types stored, including string, list, set, zset, and hash (hash type).

Wherein the directory package corresponding to the target application service conforms to the format of the package manager, examples of the format are as follows,

Step S05: and storing the catalog package in a package manager and updating a service list.

Correspondingly, the step S10 specifically includes:

step S102: and reading the service configuration parameters of the target application service from the updated service list.

It will be appreciated that the corresponding information of the Redis service in the service list will be automatically updated after the target package is stored. For example, the corresponding information updated and added is configurable parameters cpu, memory, capability, persistence mode and password.

Meanwhile, the updated service list is updated and added with service_id and play_id.

Obviously, the subsequent creation link of the application service will use the corresponding information updated and added as described above, for example, service_id and plan_id.

Therefore, in the creation step, the service configuration parameters of the target application service will contain the information in the updated service list.

In this embodiment, by completing the extension of the Redis application service, the subsequent user can more simply create the Redis service, and the embodiment of the present invention is not limited to the specific type of the application service. Obviously, this process greatly simplifies the extended functionality of multiple types of application services, as well as enhancing their performance.

It can be seen that the directory package is a package conforming to the format of the package manager of the container cluster.

Wherein the target application service is any type of application service.

The target application service is MySQL service or Redis service.

Further, the catalog package corresponding to the target application service conforms to the format of the package manager, and as can be seen, all application services are managed by using the container cluster package manager, the application service package is only manufactured according to the format of the identifiable package of the container cluster package manager and stored in the container cluster package manager, and the related information of the application service can be obtained.

Further, more specifically, the catalog package may be stored in a package manager of the container cluster.

It can be seen that catalog packages for different types of application services can be stored in the package manager of the container cluster.

In addition, regarding the logging operation of the logging directory package, the platform may store the Chart package of the Redis application service to be extended in the Helm server, and update the Helm server.

More specifically, the directory package corresponding to the target application service and the number corresponding to the directory package may be stored in the container cluster package manager, i.e., in the Helm server.

In addition, after adding the Redis application service package to the Helm server, the platform may update the Helm server, at which time the Redis service list entry is added to the service list.

Therefore, the embodiment can manage all application services through the container cluster package manager, and only needs to make an application service package according to the format of the identifiable package of the container cluster package manager, and store the application service package into the container cluster package manager to obtain the relevant information of the application service.

In addition, after the platform updates the Helm server, the information of the extended Redis application service, including service_id and plan_id, can be added in the index file of the Helm server.

At this time, an entry for the Redis application service has been newly added to the index file index in the Helm server.

Further, when the platform acquires the extended application service list from the Helm server, the platform adds configurable parameters cpu, memory, capability, persistence mode and password to the extended Redis application service. After packaging, a complete containerized application service list is generated.

It can be seen that after the above steps, the service list already has basic information of the extended Redis application service, including information such as service_id, plan_id, and detailed configurable parameters. The user may then proceed to the creation link, the access link, and create the application services of the containerized Redis.

Further, after the sending the service configuration parameters and the directory package to a container cluster to enable the container cluster to generate the containerized target application service, the OSB-based application service extension method further includes:

It should be appreciated that the resource expansion request occurs after the creation link and the expansion mechanism occurs before the creation link.

Specifically, in terms of the resource expansion operation, if the resource of the MySQL database service is not used enough, the resource of the MySQL database service may be expanded.

Specifically, the cpu, memory and capability parameters used by the containerized MySQL database service are mainly extended. After the containerized MySQL database is successfully created, the resource expansion request can be submitted again, and corresponding parameters are configured.

An example of this is as follows,

then, when the OSB-based application service management platform receives the resource expansion request, all parameters in the configuration parameters are analyzed. The service_instance ID is obtained, and service_id and plan_id, namely service positioning information, are used for positioning the position of the containerized MySQL database service, then the position is found, and the operation is stopped. The cpu, memory, capability of the parameters is an expansion parameter for replacing the original parameters when restarting the MySQL database service, thereby realizing the resource expansion of MySQL.

After the resources are expanded, the containerized application service is started according to the new expanded resource specification, namely the expanded application service to be expanded.

In addition, the catalog packages of the application service may also be numbered and stored in the container cluster package manager. The index of the container cluster package manager is updated so that new application services are added to the index list of the container cluster package manager.

In addition, the application service list can be read from the container cluster package manager, and configurable parameter information can be configured for the extended application service.

In addition, the OSB-based application service management platform may also re-read the application service list in the container cluster package manager and list the configuration parameters of the corresponding application service.

Optionally, the OSB-based application service management platform further provides an application service resource expansion function, after receiving the resource expansion request, the OSB-based application service management platform analyzes the corresponding configuration parameters, finds the corresponding application service in the container cluster, submits the corresponding application service to the container cluster according to the new parameters, and the container cluster stops the application service before resource expansion first and starts the application service according to the new resource parameters.

Therefore, according to the first to fifth embodiments of the OSB-based application service extension method, aiming at the technical problems of poor expansibility and complex design of the current containerized application service, an extensible application service management platform is built by combining the OSB specification with a container cluster package manager, so that all types of application services can be docked by using the unified OSB specification, all types of application services are managed by using the container cluster package manager, the extension function of different types of application services is simplified, and the extension function of the application service can be realized by only adding different types of application service packages into the container cluster package manager. Meanwhile, the expansion function of the application service resource can be simplified.

Meanwhile, in order to meet the increase of application service types and resource expansion of application services under the use scene of diversified application programs, the current technical scheme mostly adopts a mode of adding a single application service and a single agent for arrangement, and a service agent needs to be designed at the same time when the application service is added. As can be seen, the current approach is cumbersome to operate in terms of the orchestration of multiple types of application services.

Aiming at the operation mode with higher operation complexity, the embodiment simplifies the whole operation flow by building an extensible application service management platform.

In addition, the embodiment of the invention also provides an application service system, which comprises a client, a container cluster and the network equipment;

Other embodiments or specific implementation manners of the application service system according to the present invention may refer to the above method embodiments, and are not described herein again.

Further, the client is an OSB protocol-based client.

Further, an OSB-based application services management platform may be carried on the network device.

Specifically, the client based on OSB protocol is mainly an interface for providing OSB docking, and can communicate with the OSB-based application service management platform and issue various application service requests. The management platform mainly comprises a registration request, an application service creation request, a service binding request and a resource expansion request, and returns corresponding information.

Wherein the OSB-based application services management platform may comprise a package manager of the container cluster.

Further, the container cluster uses in this example a Kubernetes cluster, with two parts, one being an application service and one being a mirror image based on application service containerization.

For example, kubernetes clusters are mainly MySQL database services that orchestrate the containerization.

More specifically, upon receiving YAML submitted by an OSB-based application service management platform, the application service is distributed to the executing nodes of the Kubernetes cluster. At the node, the base image and the application service based containerized image are pulled from the image repository, creating a containerized MySQL database service by the docker. The pulled mirror image is a mirror image based on application service containerization, and the mirror image based on application service containerization is designed and developed according to a MySQL running process, for example, in this embodiment, the mirror image of MySQL in a stand-alone mode can be provided by an official authority, while the mirror image of MySQL in a dual-master mode needs to be redesigned and developed, mainly to configure the roles of the nodes of the MySQL in the dual-master mode, and simultaneously to configure the connection parameters between the nodes.

Further, application services may be included in the container cluster, and mirroring based on application service containerization may also be included.

Further, the application service system may also include a mirror repository.

The mirror image warehouse is mainly used for storing mirrors based on application service containerization, for example, storing MySQL application service mirrors.

In this embodiment may be implemented with a Harbor warehouse for creating MySQL containerized services.

Among them, harbor is an open source solution for building a private Docker mirror warehouse at enterprise level, which is a higher level package for Docker Registry, which can provide friendly UI (User Interface Design, interface design) interface, role and user rights management, which is a widely used Docker mirror warehouse at present.

Therefore, the system integrates the client based on the OSB protocol, the application service management platform based on the OSB and the container cluster, simplifies the arrangement of the application service aiming at the containerized application service, and provides a supporting platform for the expansion of the application service, thereby improving the management efficiency of the containerized application service and improving the usability of the application service.

Further, as for the client, an OSB protocol-based client is used for communicating with an OSB-based application management platform.

Specifically, an OSB-based WEB interface will be described as an example.

The user can send a corresponding request to the application service management platform of the OSB on the WEB interface based on the OSB.

For example, when the application service management platform of the OSB registers, the IP address and access request mode of the application service management platform of the OSB need to be input on the WEB interface.

For example, when MySQL service is created, a corresponding MySQL application service mode, such as a stand-alone mode or a dual-master mode, needs to be selected on the WEB interface, and then the passwords of cpu, memory, capability and root users of MySQL are configured and then sent to the management platform of the application service of the OSB.

For example, when MySQL service is bound, parameters are filled in the WEB interface, then a binding request is sent to the application service management platform of the OSB, the application service management platform of the OSB returns the connection address and the password of MySQL, and finally the access ID address, the port number and the password of the created containerized MySQL database application service are displayed on the WEB interface. The user may use this IP address and password for access.

Further, in the case of a container cluster, specifically, the container cluster pulls the mirror image of the application service from the mirror image repository, and then manages and orchestrates all application services.

In addition, the container cluster may receive a request for creation and access of an application service by the OSB-based application service management platform.

Further, with respect to the image repository, specifically, the base images required for all application services and the containerized images based on the application services are stored.

More specifically, a more specific class of system embodiments may be provided herein as follows.

The platform comprises a service list, wherein the service list lists the numbers of all application services and mainly comprises service numbers and package numbers, and in addition, the platform also comprises configurable parameter information and service detailed description information of all application services.

When the platform receives the application service creation application, the application service instance number and the resource parameter information are acquired from the configuration parameters, the corresponding application service package is pulled from the container cluster package manager, and the application service package is submitted to the container cluster.

When the platform receives the application service binding application, the platform acquires the application service instance number from the configuration parameters, and acquires the corresponding access credential from the application service in the container cluster.

The container cluster package manager is configured to access packages of application services, submit packages to the container clusters, and create corresponding application service containers from the container clusters.

The container cluster mainly pulls the mirror image of the application service from the mirror image warehouse and lays out the containerized application service. The system comprises two parts, namely mirror images based on application service containerization and application services.

For application service based containerized mirroring, after understanding the running and development processes of an application program, it is necessary to develop a containerized mirror of an application service based on the running process of this application service, which is used to create a containerized application service.

For application services, particularly containerized application services, an application program may be placed into a container for execution and application service credentials provided.

The mirror image warehouse is used for storing the containerized mirror images based on the application services, and when the container cluster creates the containerized application services, the corresponding mirror images need to be pulled from the mirror image warehouse.

Further, the platform also includes a service list.

In addition, as for the service list, mainly, a service_id and a plan_id are acquired from the hell server, and which types of application services and which packages for each application service are determined according to the service_id and the plan_id. The configurable parameters of the MySQL database application service and the service_id and plan_id of the service may then be provided to an OSB protocol based WEB interface where the user may view the parameter information and package type of MySQL.

In addition, the container cluster package manager mainly uses a Helm tool to build a Helm server and stores a Chart package of MySQL database service.

The address of the Helm server is mainly used for obtaining a service list and downloading in the process of creation.

In addition, the embodiment of the invention also provides a storage medium, wherein the storage medium stores an application service extension program based on the OSB, and the application service extension program based on the OSB realizes the following operations when being executed by a processor:

acquiring service configuration parameters of a target application service;

determining a catalog packet corresponding to the target application service;

Further, the OSB-based application service extension program, when executed by the processor, further performs the following operations:

analyzing the service configuration parameters to obtain a package identifier;

accordingly, the following operations are also implemented:

When a registration request is received, acquiring registration parameters;

reading a service access address from the registration parameter;

receiving a catalog packet corresponding to a target application service;

storing the catalog package in a package manager and updating a service list;

accordingly, the following operations are also implemented:

Wherein the target application service is any type of application service;

the target application service is MySQL service or Redis service.

In addition, referring to fig. 7, an embodiment of the present invention further provides an OSB-based application service extension apparatus, where the OSB-based application service extension apparatus includes: a parameter acquisition module 10, a catalog packet determination module 20, and a service generation module 30;

the parameter obtaining module 10 is configured to obtain a service configuration parameter of a target application service;

the catalog packet determination module 20 is configured to determine a catalog packet corresponding to the target application service;

the service generating module 30 is configured to send the service configuration parameter and the directory packet to a container cluster, so that the container cluster generates the containerized target application service.

Other embodiments or specific implementation manners of the OSB-based application service extension apparatus of the present invention may refer to the above method embodiments, and are not described herein.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.

The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the terms first, second, third, etc. do not denote any order, but rather the terms first, second, third, etc. are used to interpret the terms as names.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. read-only memory, RAM, magnetic disk, optical disk), comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a communication device, etc.) to perform the method according to the embodiments of the present invention.

The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

1. An OSB-based application service extension method is characterized by comprising the following steps:

Acquiring service configuration parameters of a target application service;

determining a catalog packet corresponding to the target application service;

sending the service configuration parameters and the directory package to a container cluster so that the container cluster generates the containerized target application service;

after the service configuration parameters and the directory package are sent to a container cluster, so that the container cluster generates the containerized target application service, the OSB-based application service extension method further includes:

stopping running the application service to be expanded according to the service positioning information, performing resource expansion operation on the application service to be expanded according to the expansion parameters, and starting the containerized application service based on the resource specification corresponding to the resource expansion operation;

the resource expansion operation is to expand expansion parameters used by the containerized MySQL database service, wherein the expansion parameters comprise CPU, memory and capability parameters, and the expansion parameters are used for replacing original parameters when restarting the MySQL database service, so that the MySQL resource expansion is realized;

When the OSB-based application service management platform receives the resource expansion request, all parameters in the configuration parameters are analyzed;

the service_instance ID is obtained, service_id and plan_id are service positioning information used for positioning the position of the containerized MySQL database service, then the position is found, and the operation is stopped;

after the resources are expanded, starting the containerized application service according to the new expanded resource specification;

before the service configuration parameters of the target application service are obtained, the OSB-based application service extension method further includes:

when a registration request is received, acquiring registration parameters;

reading a service access address from the registration parameter;

acquiring service configuration parameters of the target application service in the packet manager according to the service access address;

The access certificate is used for the client to connect with the target application service;

wherein the OSB-based application service management platform receives the service binding request.

2. The OSB-based application service extension method as claimed in claim 1, wherein after the service configuration parameters of the target application service are obtained, the OSB-based application service extension method further comprises:

analyzing the service configuration parameters to obtain a package identifier;

3. The OSB-based application service extension method according to claim 1 or 2, wherein before the obtaining the service configuration parameters of the target application service, the OSB-based application service extension method further comprises:

receiving a catalog packet corresponding to a target application service;

storing the catalog package in a package manager and updating a service list;

wherein the target application service is any type of application service;

the target application service is MySQL service or Redis service.

4. A network device, the network device comprising: memory, a processor and an OSB-based application service extension program stored on the memory and executable on the processor, which OSB-based application service extension program when executed by the processor implements the steps of the OSB-based application service extension method according to any of claims 1 to 3.

5. An application service system comprising a client, a container cluster, and the network device of claim 4;

6. A storage medium, wherein an OSB-based application service extension program is stored on the storage medium, which when executed by a processor implements the steps of the OSB-based application service extension method according to any of claims 1 to 3.

7. An OSB-based application service extension apparatus, characterized in that the OSB-based application service extension apparatus comprises:

the service generation module is used for sending the service configuration parameters and the directory package to a container cluster so as to enable the container cluster to generate the containerized target application service;

the OSB-based application service extension device is further configured to, after the service configuration parameter and the directory package are sent to a container cluster, enable the container cluster to generate the containerized target application service, obtain service positioning information and extension parameters corresponding to the application service to be extended when a resource extension request is received; stopping running the application service to be expanded according to the service positioning information, performing resource expansion operation on the application service to be expanded according to the expansion parameters, and starting the containerized application service based on the resource specification corresponding to the resource expansion operation;

the application service extension device based on OSB is further configured to obtain a registration parameter when receiving a registration request before the service configuration parameter of the target application service is obtained; reading a service access address from the registration parameter; acquiring service configuration parameters of the target application service in the packet manager according to the service access address;

the OSB-based application service extension device is further configured to send the service configuration parameter and the directory package to a container cluster, so that after the container cluster generates the containerized target application service, when a service binding request is received, obtain a binding identifier; transmitting the binding identification to the container cluster, so that the container cluster determines access credentials of the corresponding target application service according to the binding identification, and returns the access credentials to a client;