CN115665231A - Service creation method, device and computer-readable storage medium - Google Patents
Service creation method, device and computer-readable storage medium Download PDFInfo
- Publication number
- CN115665231A CN115665231A CN202211309198.2A CN202211309198A CN115665231A CN 115665231 A CN115665231 A CN 115665231A CN 202211309198 A CN202211309198 A CN 202211309198A CN 115665231 A CN115665231 A CN 115665231A
- Authority
- CN
- China
- Prior art keywords
- network
- service
- container
- networks
- endpoint
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The disclosure relates to a service creation method, a service creation device and a computer-readable storage medium, and relates to the technical field of computers. The method of the present disclosure comprises: creating a plurality of networks for a workload, wherein the workload comprises: a plurality of containers or container groups Pod implementing the same network function; different services are created for the plurality of networks, respectively.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a service creation method and apparatus, and a computer-readable storage medium.
Background
In an existing container management platform implementation, taking kubernets (K8 s for short) as an example, a Service (Service) associates tags of a workload (e.g., a container group (Pod)) according to a tag selector. When creating services for a workload, for a workload with multiple Network interfaces, the service is associated with one of the IP addresses visible to the K8s Cluster Network (Cluster Network), i.e. only one service is created for the workload.
Disclosure of Invention
The inventor finds that: at present, only one service is created for a workload, an application access workload can only pass through one service, the service capability of the workload cannot be effectively utilized, and the service efficiency is improved.
One technical problem to be solved by the present disclosure is: how to effectively utilize the service capability of the workload and improve the service efficiency.
According to some embodiments of the present disclosure, there is provided a service creation method including: creating a plurality of networks for a workload, wherein the workload comprises: a plurality of containers or container groups Pod implementing the same network function; different services are created for the plurality of networks, respectively.
In some embodiments, creating different services for the plurality of networks, respectively, includes: configuring different network marks for a plurality of networks in each container or container group description file respectively; different services are respectively created for the plurality of networks according to the network label of each network.
In some embodiments, each container or group of containers operates on a network entity corresponding to multiple network interfaces, each corresponding to a different network.
In some embodiments, creating different services for the plurality of networks, respectively, based on the network label for each network comprises: determining the plurality of containers or container groups as associated containers or container groups according to the labels of the plurality of containers or container groups; creating a plurality of services for a plurality of containers or container groups; each service of the plurality of services is associated with a corresponding network according to the network label of each network.
In some embodiments, the method further comprises: and establishing a corresponding endpoint for each service according to the IP address of the network interface corresponding to each service.
In some embodiments, creating a corresponding endpoint for each service based on the IP address of the network interface corresponding to each service comprises: allocating different IP addresses to a plurality of network interfaces corresponding to each container or container group; creating a corresponding endpoint for each service; and determining the resources of the endpoint corresponding to each service according to the IP address of the network interface corresponding to each service.
In some embodiments, determining the resources of the endpoint corresponding to each service according to the IP address of the network interface corresponding to each service includes: for each endpoint, in response to monitoring that the creation of the endpoint is completed, acquiring service information corresponding to the endpoint, wherein the service information comprises: a network tag serving a corresponding network; determining the IP address of a network interface corresponding to the network according to the network mark of the network; and modifying the default IP address in the resource of the endpoint into the IP address of the network interface corresponding to the network.
In some embodiments, the method further comprises: receiving different types of requests of users through different services; the service assigns the request to a corresponding container or group of containers according to a preset policy.
According to still other embodiments of the present disclosure, there is provided a service creation apparatus including: a network creation module to create a plurality of networks for a workload, wherein the workload comprises: a plurality of containers or container groups that implement the same network function; and the service creation module is used for respectively creating different services for the plurality of networks.
According to still other embodiments of the present disclosure, there is provided a service creation apparatus including: a processor; and a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to perform the steps of the service creation method as in any of the preceding embodiments.
According to still further embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program, wherein the program, when executed by a processor, implements the steps of the service creation method of any of the preceding embodiments.
In the method, the networks are created for the workload, and different services are created for the networks respectively, so that a plurality of applications can access the workload through the services, the service capacity of the workload is effectively utilized, and the service efficiency is improved.
Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 illustrates a flow diagram of a service creation method of some embodiments of the present disclosure.
Fig. 2 shows a schematic diagram of a service creation method of some embodiments of the present disclosure.
Fig. 3 shows a schematic diagram of a network structure of some embodiments of the present disclosure.
Fig. 4 shows a schematic structural diagram of a service creation apparatus of some embodiments of the present disclosure.
Fig. 5 shows a schematic structural diagram of a service creation apparatus according to further embodiments of the present disclosure.
Fig. 6 shows a schematic structural diagram of a service creation apparatus according to further embodiments of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
The present disclosure provides a method of creating a service for a workload, described below in conjunction with fig. 1-3.
FIG. 1 is a flow chart of some embodiments of a service creation method of the present disclosure. As shown in fig. 1, the method of this embodiment includes: steps S102 to S104.
In step S102, a plurality of networks are created for the workload.
The workload includes, for example: one or more containers (containers) or one or more groups of containers (Pod) that implement the same network functionality. Multiple networks may be created for each container or group of containers.
As shown in fig. 2, taking K8s as an example, a network is created: when a Pod is created, the Kubelet will call the default CNI plug-in to create a network for the Pod, assigning an IP address. When multiple networks are created for each Pod, multus, for example, is an example of a CNI plug-in that needs to be declared invoked in the annotation, one CNI plug-in representing the creation of one network.
In some embodiments, one or more network interfaces are created for each container, with different network interfaces accessing the corresponding networks. For example, each container or container group operates on a network entity corresponding to multiple network interfaces, each of which corresponds to a different network.
As shown in fig. 3, the system includes 4 containers (containers), each of which runs a corresponding Network entity, and each of the containers corresponds to two Network interfaces (Network interfaces) and respectively corresponds to different networks.
In step S104, different services are created for the plurality of networks, respectively.
In some embodiments, different network tags are configured for the plurality of networks in each container or container group description file, respectively; different services are respectively created for the plurality of networks according to the network label of each network.
For example, different networks are assigned different network labels in the container profile for each container or group of containers. As shown in fig. 2, taking K8s as an example, the label network: when a plurality of networks of a pod are created, a network flag is set for each created network to distinguish between the created different networks. For example, a Pod declares (e.g., in a Pod. Yaml file) multiple networks by way of annotations, each network containing a CNI plug-in that created the network and a corresponding network label. For example, two networks are created for Pod, labeled "net1" and "net2", respectively.
The creation of a service is based on a network tag, which is associated with the same service. In some embodiments, the plurality of containers or groups of containers are determined to be associated containers or groups of containers based on the labels of the plurality of containers or groups of containers; creating a plurality of services for a plurality of containers or container groups; each service of the plurality of services is associated with a corresponding network based on the network label of each network.
As shown in fig. 2, taking K8s as an example, the Pod tag selector: when the service is created, selecting the label through a selection (selector) field to match the label of the Pod; service and network label binding: in creating Service, in addition to using the tag selector to match the Pod, the network of the network tag selector matching Pod needs to be declared. I.e., service (e.g., in a Service. Yaml file) declares in the annotation that the Service corresponds to a network tag. For example, the corresponding network is labeled "net1" for one Service declaration and "net2" for another Service declaration.
According to the method of the embodiment, the plurality of networks are created for the workload, and different services are respectively created for the plurality of networks, so that the plurality of applications can access the workload through the plurality of services, the service capacity of the workload is effectively utilized, and the service efficiency is improved.
In some embodiments, the method further comprises: endpoints (Endpoints) are created for each service according to the IP address of the network interface associated with each service. For example, if there is only a single network interface for a container, then the endpoint corresponding to the service is created based on the IP address of that network interface. Aiming at the container, a plurality of network interfaces are provided, aiming at each service, an endpoint corresponding to the service is directly established according to the IP address of the corresponding network interface, or an endpoint corresponding to the default IP address establishing service is selected, the establishment completion of the endpoint is monitored, the network mark associated with the service is obtained, the IP address of the corresponding network interface is determined, and the default IP address in the endpoint is modified to be the IP address of the corresponding network interface.
In some embodiments, different IP addresses are assigned to each container or a corresponding plurality of network interfaces of a container group; each service creates a corresponding endpoint; and determining the resources of the endpoint corresponding to each service according to the IP address of the network interface corresponding to each service.
Further, for each endpoint, in response to monitoring that the creation of the endpoint is completed, acquiring information of a service corresponding to the endpoint, wherein the information of the service includes: a network tag serving a corresponding network; determining the IP address of a network interface corresponding to the network according to the network mark of the network; and modifying the default IP address in the resources of the endpoint into the IP address of the network interface corresponding to the network. Of course, the endpoint corresponding to the service may be created directly for each service according to the IP address of the corresponding network interface.
As shown in fig. 2, taking K8s as an example, an Endpoints controller (endpoint controller) creates Endpoints resources (Service name, IP, port, etc.) from Service information (tag selector, type, port, etc.) and information of a matched Pod (IP, port, etc.), and performs Endpoints lifecycle management. And monitoring Service creation information by an Endpoints controller, acquiring Service information, acquiring information of Pod through a tag selector, and creating Endpoints, wherein the IP can be the default IP address of the Pod. For example, the IP address of Endpoints can be set as the default IP address in Endpoints1. Yaml. The created Endpoints information is returned to the api server (interface server).
endpoints extended controller (end point extension controller): and monitoring the api server, and modifying the IP address according to the network marker selector after the Endpoints are created. The module can be integrated into an endpoints controller or can be separately deployed, and modification of the endpoints controller is reduced. For example, the Endpoints extended controller monitors Endpoints creating information, acquires Service information, analyzes and annotates to find that a network corresponding to the Service is net1, acquires an IP address corresponding to net1 in the Pod information, and modifies Endpoints resources. For example, the default IP address is modified in endpoints2.Yaml to the IP address corresponding to net 1. And returning the updated Endpoints information to the api server.
In the method of the present disclosure, for each container or group of containers, multiple networks are created for the container or group of containers, and in the container profile, different network labels are assigned to different networks. And creating a plurality of network interfaces for the container, accessing different network interfaces to corresponding networks, and allocating different IP addresses for different network interfaces. Different services are created for multiple networks of containers (the services are based on network labels, with the same network label being associated with the same service). An endpoint is created for each service based on the IP address of the network interface associated with each service.
Further, in some embodiments, different types of requests by the user are received through different services; the service assigns the request to the corresponding container or group of containers according to a preset policy. For example, the predetermined policy is a load balancing policy, etc., and the service allocates the request to the container or the container group with the lightest load and normal operation. In a scenario where a control plane and a user plane are separated, the control plane may correspond to one service, the user plane may correspond to one service, a control plane request of a user is received through the service corresponding to the control plane, a user plane request of the user is received through the service corresponding to the user plane, and then different types of requests are processed through different services.
And a plurality of services are provided for the outside, the service distributes the request to a certain normally-operated container according to a strategy, the coupling relation between the request and a specific container is decoupled, and the load balance can be better realized. Through separation of network traffic of a control plane, a data plane and the like, different services are constructed for access, the performance is improved, the user experience is improved, and the method has high value and practicability.
The scheme of the method and the device can create a plurality of networks for the workload, distinguish the networks through different network marks, create a plurality of services for different networks, create different service access endpoints according to the networks with different workloads, and avoid conflict with the workflow of the existing container management platform through a dynamic monitoring method. The disclosed solution enables associating services with each specific network interface of a workload, thereby enabling the creation of multiple service capabilities for the workload. The method can enable the application with a plurality of network interface requirements to better utilize the advantages of elasticity, expandability, flexibility, easy migration and the like brought by containerization. Aiming at the K8s scene, the existing K8s workflow is not changed while the requirement of creating finer-grained service is met.
The present disclosure also provides a service creation apparatus, described below in conjunction with fig. 4.
Fig. 4 is a block diagram of some embodiments of the disclosed service creation apparatus. As shown in fig. 4, the apparatus 40 of this embodiment includes: a network creation module 410 and a service creation module 420.
The network creation module 410 is configured to create a plurality of networks for a workload, wherein the workload comprises: multiple containers or groups of containers implementing the same network function.
The service creation module 420 is configured to create different services for the plurality of networks, respectively.
In some embodiments, the service creation module 420 is configured to configure different network tags for the plurality of networks in each container or container group description file, respectively; different services are respectively created for the plurality of networks according to the network label of each network.
In some embodiments, each container or group of containers operates on a network entity corresponding to multiple network interfaces, each corresponding to a different network.
In some embodiments, the service creation module 420 is configured to determine a plurality of containers or groups of containers as associated containers or groups of containers based on the labels of the plurality of containers or groups of containers; creating a plurality of services for a plurality of containers or container groups; each service of the plurality of services is associated with a corresponding network according to the network label of each network.
In some embodiments, the apparatus 40 further comprises: and the endpoint control module 430 is configured to create a corresponding endpoint for each service according to the IP address of the network interface corresponding to each service.
In some embodiments, the endpoint control module 430 is configured to assign different IP addresses to the corresponding plurality of network interfaces of each container or container group; creating a corresponding endpoint for each service; and determining the resources of the endpoint corresponding to each service according to the IP address of the network interface corresponding to each service.
In some embodiments, for each endpoint, in response to monitoring that creation of the endpoint is completed, information of a service corresponding to the endpoint is obtained, where the information of the service includes: a network tag serving a corresponding network; determining the IP address of a network interface corresponding to the network according to the network mark of the network; and modifying the default IP address in the resource of the endpoint into the IP address of the network interface corresponding to the network.
In some embodiments, different types of requests by the user are received through different services; the service assigns the request to the corresponding container or group of containers according to a preset policy.
The service creation means in the embodiments of the present disclosure may each be implemented by various computing devices or computer systems, which are described below in conjunction with fig. 5 and 6.
Fig. 5 is a block diagram of some embodiments of the disclosed service creation apparatus. As shown in fig. 5, the apparatus 50 of this embodiment includes: a memory 510 and a processor 520 coupled to the memory 510, the processor 520 configured to perform a service creation method in any of the embodiments of the present disclosure based on instructions stored in the memory 510.
Fig. 6 is a block diagram of further embodiments of the disclosed service creation apparatus. As shown in fig. 6, the apparatus 60 of this embodiment includes: memory 610 and processor 620 are similar to memory 410 and processor 420, respectively. An input output interface 630, a network interface 640, a storage interface 650, and the like may also be included. These interfaces 630, 640, 650 and the connections between the memory 610 and the processor 620 may be, for example, via a bus 660. The input/output interface 630 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 640 provides a connection interface for various networking devices, such as a database server or a cloud storage server. The storage interface 650 provides a connection interface for external storage devices such as an SD card and a usb disk.
According to some embodiments of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program, wherein the program, when executed by a processor, implements the steps of the service creation method of any of the preceding embodiments.
As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only exemplary of the present disclosure and is not intended to limit the present disclosure, so that any modification, equivalent replacement, or improvement made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (11)
1. A service creation method, comprising:
creating a plurality of networks for a workload, wherein the workload comprises: a plurality of containers or container groups Pod implementing the same network function;
different services are created for the plurality of networks, respectively.
2. The service creation method according to claim 1, wherein the creating different services for the plurality of networks respectively comprises:
configuring different network marks for the plurality of networks in each container or container group description file respectively;
and respectively creating different services for the plurality of networks according to the network mark of each network.
3. The service creation method according to claim 2, wherein the network entity in which each container or container group operates corresponds to a plurality of network interfaces, the plurality of network interfaces corresponding to different networks, respectively.
4. The service creation method according to claim 2, wherein the creating different services for the plurality of networks, respectively, according to the network label of each network includes:
determining the plurality of containers or container groups as associated containers or container groups according to the labels of the plurality of containers or container groups;
creating a plurality of services for the plurality of containers or container groups;
associating each of the plurality of services with a corresponding network according to the network label for each network.
5. The service creation method of claim 3, further comprising:
and establishing a corresponding endpoint for each service according to the IP address of the network interface corresponding to each service.
6. The service creation method of claim 5, wherein the creating a corresponding endpoint for each service according to the IP address of the network interface corresponding to each service comprises:
allocating different IP addresses to a plurality of network interfaces corresponding to each container or container group;
creating a corresponding endpoint for each service;
and determining the resources of the endpoint corresponding to each service according to the IP address of the network interface corresponding to each service.
7. The service creation method of claim 6, wherein the determining the resources of the endpoint corresponding to each service according to the IP address of the network interface corresponding to each service comprises:
for each endpoint, in response to monitoring that the creation of the endpoint is completed, acquiring information of a service corresponding to the endpoint, wherein the information of the service comprises: a network tag of a network corresponding to the service;
determining the IP address of a network interface corresponding to the network according to the network mark of the network;
and modifying the default IP address in the resources of the endpoint into the IP address of the network interface corresponding to the network.
8. The service creation method of claim 1, further comprising:
receiving different types of requests of users through different services;
the service assigns the request to the corresponding container or group of containers according to a preset policy.
9. A service creation apparatus comprising:
a network creation module to create a plurality of networks for a workload, wherein the workload comprises: a plurality of containers or container groups that implement the same network function;
and the service creation module is used for respectively creating different services for the plurality of networks.
10. A service creation apparatus comprising:
a processor; and
a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to perform the service creation method of any of claims 1-8.
11. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211309198.2A CN115665231A (en) | 2022-10-25 | 2022-10-25 | Service creation method, device and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211309198.2A CN115665231A (en) | 2022-10-25 | 2022-10-25 | Service creation method, device and computer-readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115665231A true CN115665231A (en) | 2023-01-31 |
Family
ID=84991836
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211309198.2A Pending CN115665231A (en) | 2022-10-25 | 2022-10-25 | Service creation method, device and computer-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115665231A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116633775A (en) * | 2023-07-24 | 2023-08-22 | 安超云软件有限公司 | Container communication method and system of multi-container network interface |
-
2022
- 2022-10-25 CN CN202211309198.2A patent/CN115665231A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116633775A (en) * | 2023-07-24 | 2023-08-22 | 安超云软件有限公司 | Container communication method and system of multi-container network interface |
| CN116633775B (en) * | 2023-07-24 | 2023-12-19 | 安超云软件有限公司 | Container communication method and system of multi-container network interface |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107431651B (en) | Life cycle management method and equipment for network service | |
| CN107580083B (en) | Method and system for allocating IP addresses of containers | |
| CN109684065B (en) | Resource scheduling method, device and system | |
| US8656387B2 (en) | Method and system for workload distributing and processing across a network of replicated virtual machines | |
| US10917294B2 (en) | Network function instance management method and related device | |
| CN110098946B (en) | Method and device for deploying virtualized network element equipment | |
| CN114244717B (en) | Configuration method and device of virtual network card resources, computer equipment and medium | |
| US20080229031A1 (en) | Method of Automated Resource Management In A Partition Migration Capable Environment | |
| US11271895B1 (en) | Implementing advanced networking capabilities using helm charts | |
| CN113849312A (en) | Data processing task allocation method and device, electronic equipment and storage medium | |
| CN115665231A (en) | Service creation method, device and computer-readable storage medium | |
| CN115237589A (en) | SR-IOV-based virtualization method, device and equipment | |
| CN107045452B (en) | Virtual machine scheduling method and device | |
| CN114070889B (en) | Configuration method, traffic forwarding device, storage medium, and program product | |
| CN111352710B (en) | Process management method and device, computing equipment and storage medium | |
| CN113220432A (en) | Multi-cloud interconnection method, device, equipment, storage medium and product | |
| CN108958878B (en) | Container-based network equipment operation control method and device | |
| CN112804069B (en) | Method, apparatus and computer readable storage medium for instantiating virtual network function | |
| CN111741097B (en) | Method for tenant to monopolize node, computer equipment and storage medium | |
| CN113961321A (en) | Cross-cloud-platform resource scheduling method and device, terminal equipment and storage medium | |
| CN115048192A (en) | Workflow scheduling method and system and workflow engine | |
| CN117234751A (en) | Cross-partition process communication method and device, electronic equipment and storage medium | |
| CN113760798A (en) | RDMA device allocation method, computing device and storage medium | |
| CN116800808A (en) | GPU resource calling method and device, electronic equipment and storage medium | |
| CN117251289A (en) | Multi-system request processing method, device, equipment and storage medium |
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 |