Kubernetes storage resource binding method, system, device and medium based on location information

Abstract

The present disclosure provides a Kubernetes storage resource binding method, system, device and medium based on location information, so as to at least solve the problem that the current Kubernetes storage resource scheduling process cannot give full play to the maximum computing power of MEC. The method includes: judging whether a request for a persistent volume declaration PVC from a user terminal is received, the request carrying the access mode of the user terminal; if the request is received, obtaining the location information of the user terminal; judging whether the access mode of the user terminal is a static access mode; if it is a static access mode, selecting the first storage resource pool closest to the user terminal based on the location information of the user terminal; and binding the first persistent volume PV1 created in the first storage resource pool to the PVC. The present disclosure takes the location information of PV into consideration in the resource scheduling process, and implements the binding of storage resources to the storage resource pool closest to the user, so that MEC can give full play to its maximum computing power.

Description

Technical Field

[0001] The present disclosure relates to the field of edge computing technology, and in particular to a Kubernetes storage resource binding method based on location information, a Kubernetes storage resource binding system based on location information, a terminal device, and a computer-readable storage medium. Background Art

[0002] Kubernetes, or K8s for short, is an open source containerized application management platform for multiple hosts. The goal of Kubernetes is to make the deployment of containerized applications simple and efficient. Kubernetes provides a mechanism for application deployment, planning, updating, and maintenance. Kubernetes implements network storage through PV (PersistentVolume) and PVC (PersistentVolumeClaim) resources.

[0003] With the advancement of 5G commercialization and the vigorous development of big video, big data, Internet of Things and other businesses, more and more new applications have put forward higher requirements for network latency, bandwidth and security. The industry generally believes that MEC (Multi-Access Edge Computing) is a key technology to meet the development requirements of "massive data, ultra-low latency, and data security". At present, the analysis of Kubernetes network storage resource scheduling usually binds PVC and PV according to PVC's request for resources after the user defines PVC. However, in the application scenario of MEC, we hope that the storage resources are closest to the user. In this case, the greatest advantage of MEC can be brought into play. Obviously, the above binding strategy between PV and PVC cannot meet the requirement of binding storage resources to the storage resource pool closest to the user. Summary of the invention

[0004] The present disclosure provides a Kubernetes storage resource binding method, system, terminal device and computer-readable storage medium based on location information, so as to at least solve the technical problem that the current scheduling process of Kubernetes storage resources cannot give full play to the maximum computing power of MEC.

[0005] To achieve the above object, the present disclosure provides a Kubernetes storage resource binding method based on location information, which is applied to an edge computing controller. The method includes:

[0006] Determine whether a request for a persistent volume declaration PVC from a user terminal is received, wherein the request carries an access mode of the user terminal;

[0007] If the request is received, obtaining the location information of the user terminal;

[0008] Determining whether the access mode of the user terminal is a static access mode;

[0009] If it is a static access mode, a first storage resource pool closest to the user terminal is selected based on the location information of the user terminal; and a first persistent volume PV1 created in the first storage resource pool is bound to the PVC.

[0010] In one implementation, before determining whether a request for a persistent volume declaration PVC is received from a user terminal, the method further includes:

[0011] Sending a creation request for creating a persistent volume PVx to all storage resource pools in a preset area, so that each storage resource pool creates its own PVx based on the creation request, and each feeds back resource information of the PVx to the edge computing controller; and

[0012] Receive resource information of the PVx.

[0013] In one implementation, the request also carries resource request information of the user terminal;

[0014] After determining whether a request for a persistent volume declaration PVC is received from a user terminal, the method further includes:

[0015] If the request is received, the PVx that meets the resource supply condition is selected from the PVx based on the resource information of the PVx and the resource request information;

[0016] Selecting a first storage resource pool closest to the user terminal based on the location information of the user terminal includes:

[0017] Based on the location information of the user terminal, a first storage resource pool closest to the user terminal is selected from the storage resource pools corresponding to the PVx that meets the resource supply condition.

[0018] In one implementation, after determining whether a request for a persistent volume declaration PVC from a user terminal is received and before obtaining the location information of the user terminal, the method further includes:

[0019] Obtaining location information of a base station corresponding to the user terminal sending the request;

[0020] The acquiring the location information of the user terminal includes: determining the location information of the user terminal based on the location information of the base station.

[0021] In one implementation, after binding the PV1 created in the first storage resource pool to the PVC, the method further includes:

[0022] The binding information after the PV1 is bound to the PVC is sent to the user terminal, so that the user terminal stores data in the PV1 based on the binding information.

[0023] In one implementation, after determining whether the access mode of the user terminal is a static access mode, the method further includes:

[0024] If it is not a static access mode, determining whether the access mode of the user terminal is a dynamic access mode;

[0025] If it is a dynamic access mode, the storage resource pool corresponding to the SC that meets the preset conditions is selected from all storage resource pools of the created storage class SC;

[0026] Selecting a second storage resource pool closest to the user terminal from the storage resource pools corresponding to the SCs meeting the preset conditions based on the location information of the user terminal;

[0027] A second persistent volume PV2 is created in the second storage resource pool based on the created SC; and the PV2 is bound to the PVC.

[0028] In one implementation, before determining whether a request for a persistent volume declaration PVC is received from a user terminal, the method further includes:

[0029] Sending configuration requests for automatically configuring volume programs Px to all storage resource pools in a preset area respectively, so that each storage resource pool configures its own Px based on the configuration request and feeds back its own resource information to the edge controller respectively; and

[0030] Based on the resource information of each storage resource pool, an SC is created for each storage resource pool, and a mapping relationship between the SC and Px in each storage resource pool is established.

[0031] To achieve the above objectives, the present disclosure also provides a Kubernetes storage resource binding system based on location information, which is applied to an edge computing controller. The system includes:

[0032] A judgment module, configured to judge whether a request for a persistent volume declaration PVC from a user terminal is received, wherein the request carries an access mode of the user terminal;

[0033] an acquisition module, configured to acquire the location information of the user terminal when the determination module determines that the request is received;

[0034] The determination module is further configured to determine whether the access mode of the user terminal is a static access mode;

[0035] A selection module configured to select a first storage resource pool closest to the user terminal based on the location information of the user terminal when the judgment module determines that the access mode is static; and

[0036] A binding module is configured to bind the first persistent volume PV1 created in the first storage resource pool to the PVC.

[0037] To achieve the above-mentioned purpose, the present disclosure also provides a terminal device, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor runs the computer program stored in the memory, the processor executes the Kubernetes storage resource binding method based on location information.

[0038] To achieve the above objectives, the present disclosure also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the processor executes the Kubernetes storage resource binding method based on location information.

[0039] According to the Kubernetes storage resource binding method based on location information provided by the present disclosure, it is determined whether a request for a persistent volume declaration PVC from a user terminal is received, the request carries the access mode of the user terminal, and if so, the location information of the user terminal is obtained; then it is determined whether the access mode of the user terminal is a static access mode, and if it is a static access mode, the first storage resource pool closest to the user terminal is selected based on the location information of the user terminal, and finally the first persistent volume PV1 created in the first storage resource pool is bound to the PVC. The present disclosure takes the location information of PV into consideration during the resource scheduling process, and implements the binding of storage resources to the storage resource pool closest to the user, so that MEC can exert its maximum computing power.

[0040] Other features and advantages of the present disclosure will be described in the following description, and partly become apparent from the description, or be understood by practicing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings are used to provide further understanding of the technical solution of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present disclosure and do not constitute a limitation on the technical solution of the present disclosure.

[0042] Figure 1 This is an example diagram of the MEC edge cloud architecture;

[0043] Figure 2 This is an example diagram of the relationship between PV and PVC;

[0044] Figure 3a This is an example diagram of PV and PVC in static resource provisioning mode;

[0045] Figure 3b This is an example diagram of PV and PVC in dynamic resource provisioning mode;

[0046] Figure 4 A flowchart of a Kubernetes storage resource binding method based on location information provided in an embodiment of the present disclosure;

[0047] Figure 5 A flowchart of another method for binding Kubernetes storage resources based on location information provided by this association;

[0048] Figure 6 A flowchart of another method for binding Kubernetes storage resources based on location information provided in an embodiment of the present disclosure;

[0049] Figure 7a This is a schematic diagram of a process for static resource provisioning according to an embodiment of the present disclosure;

[0050] Figure 7b This is a flow chart of dynamic resource provisioning according to an embodiment of the present disclosure;

[0051] Figure 8 A schematic diagram of the structure of a Kubernetes storage resource binding system based on location information provided in an embodiment of the present disclosure;

[0052] Fig. 9 A schematic diagram of the structure of a terminal device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0053] To make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the specific implementation of the present disclosure is described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementation described here is only used to illustrate and explain the present disclosure, and is not used to limit the present disclosure.

[0054] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence; and, in the absence of conflict, the embodiments in the present disclosure and the features in the embodiments can be arbitrarily combined with each other.

[0055] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present disclosure, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.

[0056] With the advancement of 5G commercialization and the vigorous development of big video, big data, IoT and other services, more and more new applications have put forward higher requirements for network latency, bandwidth and security. The industry generally believes that MEC is a key technology to meet the development requirements of "massive data, ultra-low latency and data security".

[0057] The European Telecommunications Standards Institute (ETSI) defines MEC as: MEC provides cloud computing capabilities and an IT service environment at the edge of the network for application developers and content providers. This environment is characterized by ultra-low latency and high bandwidth as well as real-time access to wireless network information that applications can utilize. This definition draws a roadmap for telecom operators to provide cloud computing capabilities at the edge through the IaaS / PaaS model. Many ICT (Information Communications Technology) manufacturers at home and abroad have released a variety of edge cloud service platforms based on their own understanding of MEC. For example, AWS has released the edge service platform Wavelength, Microsoft has released the edge-oriented cloud platform Azure IoTEdge, Google has also launched the Anthos edge framework, Alibaba Cloud has launched the Link IoT Edge IoT edge computing solution, Baidu has launched the "end-to-end cloud" solution Baidu IntelliEdge for intelligent edge computing, and so on.

[0058] Let's take China Unicom's MEC as an example to make a simple explanation. China Unicom provides the overall architecture of the MEC edge cloud in the "5G MEC Edge Cloud Platform Architecture and Commercial Practice White Paper", such as Figure 1 As shown in the figure, in terms of deployment architecture, China Unicom's MEC edge cloud is mainly divided into three levels, namely, the whole network center node, the regional center / provincial capital node, and the local core / edge node.

[0059] 1) Central node of the entire network

[0060] Deploy a group-level edge business operation platform (including MEAO: Mobile Edge Application Operator) in Guangdong and Henan, connect to the group's OSS (The Office of Strategic Services, operation support system), BSS (Business support system, business support system), government and enterprise marketing portal, NFVO (NFV Orchestrator, network function virtualization management), and unified cloud management, and provide open interfaces for developers and customers to upload business capabilities and applications. Realize application synchronization between Guangdong and Henan, and jointly complete the orchestration and management of edge business applications across China Unicom's entire network.

[0061] 2) Regional Center / Provincial Capital Node

[0062] Regional center / provincial capital nodes have been deployed in Guangdong, Shanghai, Beijing, Zhejiang, Fujian, Jilin, Chongqing and other places. The regional center / provincial capital nodes are still being continuously supplemented and improved, and will be expanded to 31 provinces, municipalities and autonomous regions across the country in the future.

[0063] The regional center / provincial capital node is the core of China Unicom's MEC business incubation base, and will deploy systems or network elements such as MEPM (Mobile edge platform manager) and MEP (Mobile edge platform). MEPM is responsible for the ME_ICT-IaaS (ME_ICT-Infrastructure-as-a-Service, edge cloud basic service base) virtualization resource management, MEP access collaboration platform, node business management and other functions of all edge nodes in the node area / province. MEP can provide customers with centralized shared services.

[0064] 3) Local core nodes / edge nodes

[0065] The local core nodes / edge nodes correspond to the core / aggregation / on-site access room nodes in each city where MEC is deployed. ME_ICT-IaaS, MEP, and ME-VAS (ME-ValueAddedServic, edge value-added services) are deployed in the nodes to carry customers' specific business applications.

[0066] MEC technology sinks computing power to the edge of the network, that is, to the computer room close to the user. This leads to an inevitable contradiction: the closer the computer room is to the user, the better the network performance it provides, but the less guaranteed its hardware resources and operation and maintenance capabilities are. Container technology has the characteristics of lightweight, portability, and standardization. In the scenario of edge computing, it provides a good solution for various computing resource needs.

[0067] Kubernetes is a container cloud orchestration and scheduling technology. In Kubernetes, the smallest unit of computing resource scheduling is Pod, which is a combination of related containers. Node resources are the physical resources of Kubernetes' specific Pod nodes. Kubernetes resource scheduling refers to placing Pods on appropriate nodes to run. Pods themselves have a life cycle, so the containers and related data running inside the Pod cannot be persistently stored in the Pod. Kubernetes provides shared storage volume technology. Storage volumes are shared directories defined on Pod resources that can be mounted by all other containers. It is associated with storage space on external storage devices, thereby achieving persistent storage independent of the container's own file system. Kubernetes supports a very rich range of storage volume types, which can generally be divided into the following three types:

[0068] Local storage, such as emptyDir, HostPath;

[0069] Network storage, NFS, cinder, cephfs, AzureFile;

[0070] Special storage resources, such as Secret and ConfigMap.

[0071] The network storage system is a cluster-level resource. It is a storage resource independent of the Kubernetes cluster. The persistence of data storage is decoupled from the Kubernetes cluster. Network storage can well meet the data storage needs in MEC scenarios. Kubernetes implements the network storage function through PV and PVC resources.

[0072] PV stands for PersistentVolume, which is an abstraction of the underlying shared storage. PV is created and configured by the administrator. It is related to the implementation of the specific underlying shared storage technology. For example, Ceph distributed file system, GlusterFS (Gluster File System), NFS (Network File System), etc., all use the plug-in mechanism to connect to the shared storage. PVC stands for PersistenVolumeClaim, which is a statement of user storage. PVC is similar to Pod. Pod consumes nodes, while PVC consumes PV resources. Pod can request CPU memory, while PVC can request specific storage space and access mode. For real storage users, there is no need to care about the underlying storage implementation details, and they only need to use PVC directly.

[0073] PV can be regarded as available storage resources, and PVC is the demand for storage resources. The relationship between PV and PVC is as follows: Figure 2 As shown in Figure 1, an abstract layer, PersistentVolume, is added between Kubernetes and the network storage service, so that the use and management of the storage system can be decoupled from each other. Kubernetes' storage resources PV and PVC support both static resource provisioning and dynamic resource provisioning. Figure 3a and 3b As shown. In static mode, you need to create PV in advance. When a Pod applies for PVC, the PVC is bound to the created PV. In dynamic mode, dynamic binding of resources is completed through storage class (SC) and PVC, and the system automatically generates PV.

[0074] Among them, in the case of static resource scheduling, when the storage space requested by PVC is less than that of PV, the entire PV space can be used by PVC, which may cause resource waste. If the resource supply uses dynamic mode, the system will automatically create a PV and bind it to the PVC after finding a suitable StorageClass for the PVC. Dynamic scheduling solves the problem of storage resource waste. The size of the PV is created according to the PVC demand.

[0075] Through the analysis of Kubernetes network storage resource scheduling, after the user defines the PVC, the system will bind the PVC to the PV through static or dynamic resource provisioning mode according to the PVC's request for resources. The parameters related to the binding strategy between PVC and PV mainly include:

[0076] accessModes: access mode, which describes the access rights of user applications to storage resources;

[0077] storage: the storage size of the resource request;

[0078] matchLabels: PV selection conditions, which can be used to bind PVs by matching labels;

[0079] accessModes means that PVC can choose to bind to PVs of these modes (allowing a single node to mount for read and write, allowing multiple nodes to mount and read-only, or allowing multiple nodes to mount for read and write). Storage means that PVC chooses to bind to a PV with a certain storage space. matchLabels means that PV can choose to bind to PVs with certain labels.

[0080] In the application scenario of MEC, we hope that the storage resources are closest to the users. In this case, the greatest advantage of MEC can be brought into play. Obviously, the above binding strategy between PV and PVC cannot satisfy the requirement of binding storage resources to the storage resource pool closest to the users.

[0081] The following specific embodiments are used to describe in detail the technical solution of the present invention and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present invention will be described below in conjunction with the accompanying drawings.

[0082] Please refer to Figure 4 , Figure 4 A flow chart of a Kubernetes storage resource binding method based on location information provided in an embodiment of the present disclosure is applied to an edge computing controller. Specifically, the method includes steps S401-S405.

[0083] In step S401, it is determined whether a request for a persistent volume declaration PVC is received from a user terminal, wherein the request carries an access mode of the user terminal. If the request is received, step S402 is executed.

[0084] In this implementation, when a user terminal generates a Kubernetes storage resource scheduling requirement, it defines a PVC and sends a PVC request to the network. The edge computing controller obtains the PVC request of the user terminal from the network.

[0085] In one implementation, a user terminal sends a PVC request to a wireless access network to apply for an edge storage service PVC. A base station in the wireless access network forwards the user terminal's PVC request to a bearer network. The bearer network forwards the PVC request to a core network. The core network then forwards the PVC request to an edge computing controller.

[0086] It can be understood that the edge storage service PVC applied for by the user mainly carries storage space size, access mode, label information, etc., among which the storage space size is used to identify the requested resource information, the access mode is used to identify the requested resource supply mode, and the label information is used to identify the PVC request.

[0087] In step S402, the location information of the user terminal is obtained.

[0088] In this embodiment, in order to implement the binding strategy of PV and PVC so as to satisfy the requirement of binding storage resources to the storage resource pool closest to the user, the location information of the user terminal is obtained during resource binding, and resource binding is completed based on the location information of the user terminal.

[0089] In one embodiment, in order to facilitate obtaining the location information of the terminal, the base station in the wireless access network can report the base station number A while forwarding the PVC request of the user terminal to the bearer network, so that when the edge computing controller receives the base station number A and the PVC request, it can query the location information of the base station according to the base station number A, and then determine the location information of the terminal according to the location information of the base station.

[0090] In step S403, it is determined whether the access mode of the user terminal is a static access mode. If it is a static access mode, step S404 is executed, otherwise the process is terminated and resource binding is completed according to the prior art.

[0091] In one implementation, if the access mode is not a static mode, it is further determined whether the access mode is a dynamic mode, and the PVC is further bound according to the dynamic mode. This is described in detail in the following embodiments and will not be repeated here.

[0092] In step S404, a first storage resource pool closest to the user terminal is selected based on the location information of the user terminal.

[0093] In one implementation, by acquiring location information of all storage resource pools in the network, the storage resource pool closest to the user is calculated and selected based on the location information of the user terminal and the location information of all storage resource pools.

[0094] In step S405, the first persistent volume PV1 created in the first storage resource pool is bound to the PVC.

[0095] It can be understood that after the PVC and PV are bound, the storage resource pool can communicate with the user terminal to provide storage services and resource scheduling.

[0096] It should be noted that, in this embodiment, the PV suffix 1, 2, ..., x is used to distinguish the persistent volumes created by different storage resource pools and has no other special meaning. The persistent volume created by the first storage resource pool is the first persistent volume PV1, the persistent volume created by the second storage resource pool is the second persistent volume PV2, the persistent volume created by the xth storage resource pool is PVx, and so on.

[0097] Compared with related technologies, this embodiment creates PVC from the terminal, applies for storage services, and then the edge computing controller calculates the nearest resource pool based on location information, and finally binds PVC and PV. It takes into account the location information of PV in the resource scheduling process, and implements binding of storage resources to the storage resource pool closest to the user, so that MEC can exert its maximum computing power.

[0098] Please refer to Figure 5 , Figure 5 A flow chart of another method for binding Kubernetes storage resources based on location information is provided for an embodiment of the present disclosure. Compared with the above embodiment, this embodiment provides an example method for dynamic resource binding. Specifically, after determining whether the access mode of the user terminal is a static access mode (step S403), steps S501-S505 are also included.

[0099] In step S501, if the access mode is not a static access mode, it is determined whether the access mode of the user terminal is a dynamic access mode.

[0100] It can be understood that Kubernetes storage resource scheduling includes static resource provisioning mode and dynamic resource provisioning mode. This embodiment provides corresponding resource binding solutions based on different access modes of user terminals.

[0101] In step S502, if it is a dynamic access mode, a storage resource pool corresponding to the SC that meets the preset conditions is selected from all storage resource pools of the created storage class SC.

[0102] In one embodiment, for the static access mode, it is determined whether the resource information of the first storage resource pool that is closest to the user terminal finally selected satisfies the PVC request of the user terminal. If the resource information of the first storage resource pool cannot meet the PVC request, then the dynamic access mode is entered and the PVC is bound based on the dynamic access mode.

[0103] In step S503, a second storage resource pool closest to the user terminal is selected from the storage resource pools corresponding to the SCs meeting the preset conditions based on the location information of the user terminal.

[0104] It should be noted that the preset condition in this embodiment is that the resource information satisfies the resource size requested by the user terminal. In some implementations, those skilled in the art may adaptively set the preset condition in combination with actual applications.

[0105] In step S504, a second persistent volume PV2 is created in the second storage resource pool based on the created SC.

[0106] It can be understood that the SC is created in advance in the storage pool by the edge computing controller before the user terminal issues a PVC request.

[0107] In step S505, the PV2 is bound to the PVC.

[0108] Further, before determining whether a request for a persistent volume declaration PVC is received from a user terminal (step S401), the edge computing controller sends a Px configuration request to all storage resource pools in a preset area, creates SCs in each storage resource pool, and corresponds SCs to Px. After selecting a second storage resource pool for resource scheduling for the user terminal, a PV can be quickly and dynamically created based on the SC of the second storage resource pool. Specifically, the following steps are also included:

[0109] Sending configuration requests for automatically configuring volume programs Px to all storage resource pools in a preset area respectively, so that each storage resource pool configures its own Px based on the configuration request and feeds back its own resource information to the edge controller respectively; and

[0110] Based on the resource information of each storage resource pool, an SC is created for each storage resource pool, and a mapping relationship between the SC and Px in each storage resource pool is established.

[0111] The above steps mean that in the MEC environment, corresponding automatic configuration programs are created for all connected storage resource pools, that is, all connected storage resource pool information (including access mode, storage space size, label information, location information) is recorded in the database of the edge computing controller, waiting to be bound at any time.

[0112] It should be noted that, in this embodiment, the preset area and the area within the network coverage area can be adaptively set by those skilled in the art in combination with actual applications.

[0113] Please refer to Figure 6 , Figure 6A flow chart of another method for binding Kubernetes storage resources based on location information is provided for an embodiment of the present disclosure. In order to ensure that resource binding and resource binding can meet the resource storage requirements of the user terminal, based on the above embodiment, this embodiment further includes the following steps S601-S603 before determining whether a request for a persistent volume declaration PVC from the user terminal is received (step S401), and step S404 is further divided into step S604.

[0114] In step S601, a creation request for creating a persistent volume PVx is sent to all storage resource pools in a preset area, so that each storage resource pool creates its own PVx based on the creation request, and each feeds back resource information of the PVx to the edge computing controller.

[0115] Specifically, the edge computing controller sends a PVx creation request to the storage resource pool, and each storage resource pool creates PVx according to the request. For example, the first storage resource pool creates PV1, the second storage resource pool creates PV2, and so on. Then, their respective resource information is fed back to the edge computing controller, so that the information of all connected storage resource pools is recorded in the database of the edge computing controller, waiting to be bound at any time.

[0116] The request also carries resource request information of the user terminal, that is, storage space size. In some embodiments, in order to distinguish different PVC requests of user terminals, the PVC request also carries label information and the like.

[0117] In step S602, receiving resource information of the PVx;

[0118] In step S603, PVx that meets the resource supply condition is screened out from the PVx based on the resource information of the PVx and the resource request information.

[0119] It can be understood that the resource provision condition is met, that is, the resource information of PVx is at least greater than or equal to the resource request information requested by the user terminal PVC.

[0120] In step S604, based on the location information of the user terminal, a first storage resource pool closest to the user terminal is selected from the storage resource pools corresponding to the PVx that meets the resource supply condition.

[0121] Further, after determining whether a request for a persistent volume declaration PVC from a user terminal is received (S401), and before obtaining the location information of the user terminal (step S402), the following steps are also included:

[0122] Obtaining location information of a base station corresponding to the user terminal sending the request;

[0123] The step of obtaining the location information of the user terminal (step S402) is specifically the following steps: determining the location information of the user terminal based on the location information of the base station.

[0124] Specifically, in order to facilitate the acquisition of the terminal's location information, the base station in the wireless access network can report the base station number A while forwarding the user terminal's PVC request to the bearer network, so that when the edge computing controller receives the base station number A and the PVC request, it can query the base station's location information based on the base station number A, and then determine the terminal's location information based on the base station's location information.

[0125] It is understandable that the base station number information is quite different from the location information of the base station. Because in the operator's database, each base station has a unique number, and the geographical location information corresponding to the base station can be found through this number, and the location information of the terminal obtained based on this is also relatively accurate.

[0126] In one implementation, after binding the PV1 created in the first storage resource pool to the PVC (S405), the following steps are further included:

[0127] The binding information after the PV1 is bound to the PVC is sent to the user terminal, so that the user terminal stores data in the PV1 based on the binding information.

[0128] Specifically, after PVC is bound to PV1, the first storage resource pool can communicate with the user terminal, and the user terminal communicates with the corresponding storage resource pool by obtaining the binding information and stores data in the created PV. The same is true for the dynamic provisioning mode, which will not be described here.

[0129] For easier understanding, please refer to Figure 7a and Figure 7b ,in Figure 7a It is a Kubernetes storage resource binding method based on location information in the static resource provisioning mode. Figure 7b This is a Kubernetes storage resource binding method based on location information in a dynamic resource provisioning mode. This embodiment takes storage edge pool N1 and storage edge pool N2 as examples.

[0130] Among them, for the static resource supply mode, such as Figure 7a As shown:

[0131] S11, the edge computing controller initiates a request to create PV1 to the storage edge pool N1;

[0132] S12: The storage edge pool creates PV1 and feeds back the resource information of PV1 to the edge computing controller, along with the location information of N1.

[0133] S13, the edge computing controller initiates a request to create PV2 to the storage edge pool N2;

[0134] S14, the storage edge pool creates PV2 and feeds back the resource information of PV2 to the edge computing controller, and carries the location information of N2;

[0135] S15, the user terminal initiates a request to the wireless access network for edge storage service PVC;

[0136] S16, the base station in the wireless access network forwards the terminal application to the bearer network and reports the base station number A;

[0137] S17, the bearer network further forwards the PVC request of the user terminal and the base station number A to the core network;

[0138] S18. The core network further forwards the PVC request of the user terminal and the base station number A to the edge computing controller;

[0139] S19, the edge computing controller selects PVs that meet the conditions based on the request information of the PVC (including access mode, resource request size, and label); then, based on the base station number A, queries the database to obtain the base station location L3; in the list of all PVs that meet the resource supply conditions, selects PVx created by the resource pool Nx closest to L3, for example, PV1 created by N1, and finally binds the PVC to PV1;

[0140] S20. The edge computing controller sends the binding information of PVC and PV1 to the user terminal.

[0141] S21. The user terminal obtains the binding information between PVC and PV1, and stores the data in PV1.

[0142] Among them, for dynamic resource supply mode, such as Figure 7b As shown:

[0143] S31, the edge computing controller initiates a request to configure the automatic configuration volume program P1 to the storage edge pool N1, and N1 creates P1;

[0144] S32, N1 feedbacks resource information and location information L1;

[0145] S33, the edge computing controller initiates a request to configure the automatic configuration volume program P2 to the storage edge pool N2, and N2 creates P2;

[0146] S34, N2 feeds back resource information and location information L2;

[0147] S35. The edge computing controller creates StorageClass resources (SC1 and SC2). SC1 corresponds to P1 and SC2 corresponds to P2. The StorageClass resources contain resource information and location information of N1 and N2.

[0148] S36, the user terminal initiates a request to the wireless access network for edge storage service PVC;

[0149] S37, the base station in the wireless access network forwards the terminal application to the bearer network and reports the base station number A;

[0150] S38, the bearer network further forwards the PVC request of the user terminal and the base station number A to the core network;

[0151] S39. The core network further forwards the PVC request of the user terminal and the base station number A to the edge computing controller;

[0152] S40, the edge computing controller selects the StorageClass that meets the conditions based on the request information of the PVC (including the access mode, resource request size and label); then, based on the base station number A, the database is queried to obtain the base station location L3, and in the list of all StorageClasses that meet the resource supply conditions, the SCx created by the resource pool Nx closest to L3 is selected; based on the PVC request, the SCx creates PVx in the corresponding resource pool, for example, creates PV2 in N2, and finally binds PV2 to the PVC;

[0153] S41. The edge computing controller sends the binding information of PVC and PV2 to the user terminal.

[0154] S42. The user terminal obtains the binding information between PVC and PV2, and stores the data in PV2.

[0155] Based on the same technical concept, the embodiment of the present disclosure also provides a Kubernetes storage resource binding system based on location information, which is applied to the edge computing controller, such as Figure 8 As shown, the system comprises:

[0156] A judgment module 81 is configured to judge whether a request for a persistent volume declaration PVC from a user terminal is received, wherein the request carries an access mode of the user terminal;

[0157] An acquisition module 82, configured to acquire the location information of the user terminal when the determination module determines that the request is received;

[0158] The judging module 81 is further configured to judge whether the access mode of the user terminal is a static access mode;

[0159] A selection module 83 is configured to select a first storage resource pool closest to the user terminal based on the location information of the user terminal when the judgment module determines that the access mode is static; and

[0160] The binding module 84 is configured to bind the first persistent volume PV1 created in the first storage resource pool to the PVC.

[0161] In one embodiment, the system further comprises:

[0162] A first request module is configured to send a creation request for creating a persistent volume PVx to all storage resource pools in a preset area before the judgment module determines whether a request for a persistent volume declaration PVC from a user terminal is received, so that each storage resource pool creates its own PVx based on the creation request, and each feeds back resource information of the PVx to the edge computing controller; and

[0163] A receiving module is configured to receive resource information of the PVx.

[0164] In one implementation, the request also carries resource request information of the user terminal, and the system further includes:

[0165] A screening module, configured to screen out PVx that meets resource supply conditions from the PVx based on the resource information of the PVx and the resource request information;

[0166] The selection module 83 is specifically configured to select, based on the location information of the user terminal, a first storage resource pool that is closest to the user terminal from the storage resource pools corresponding to the PVx that meets the resource supply condition.

[0167] In one embodiment, the acquisition module 82 is further configured to, after the judgment module determines whether a request for a persistent volume declaration PVC of a user terminal is received, and before obtaining the location information of the user terminal, the location information of the corresponding base station to which the user terminal sends the request;

[0168] The acquisition module 82 includes: a determination unit, which is configured to determine the location information of the user terminal based on the location information of the base station.

[0169] In one embodiment, it further includes:

[0170] The sending module is configured to send binding information of the PV1 and the PVC to the user terminal after the binding module binds the PV1 created in the first storage resource pool to the PVC, so that the user terminal stores data in the PV1 based on the binding information.

[0171] In one embodiment, it further includes:

[0172] The judging module 81 is further configured to, when the judging module judges that the access mode of the user terminal is not a static access mode, continue to judge whether the access mode of the user terminal is a dynamic access mode;

[0173] The selection module 83 is further configured to select a storage resource pool corresponding to a SC that meets preset conditions from all storage resource pools of the created storage class SC when the judgment module judges that it is a dynamic access mode;

[0174] The selection module 83 is further configured to select, based on the location information of the user terminal, a second storage resource pool closest to the user terminal from the storage resource pools corresponding to the SCs meeting the preset conditions;

[0175] a first creation module, configured to create a second persistent volume PV2 in the second storage resource pool based on the created SC; and

[0176] The binding module 84 is further configured to bind the PV2 to the PVC.

[0177] In one embodiment, it further includes:

[0178] A second request module is configured to send a configuration request for automatically configuring a volume program Px to all storage resource pools in a preset area before the judgment module determines whether a request for a persistent volume declaration PVC is received from a user terminal, so that each storage resource pool configures its own Px based on the configuration request and feeds back its own resource information to the edge controller; and

[0179] The second creation module is configured to create SCs for each storage resource pool based on resource information of each storage resource pool, and establish a mapping relationship between SCs and Px in each storage resource pool.

[0180] Based on the same technical concept, the embodiment of the present disclosure also provides a terminal device, such as Fig. 9 As shown, the terminal device includes a memory 91 and a processor 92, wherein the memory 91 stores a computer program. When the processor 92 runs the computer program stored in the memory 91, the processor 92 executes the Kubernetes storage resource binding method based on location information.

[0181] Based on the same technical concept, an embodiment of the present disclosure also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the processor executes the Kubernetes storage resource binding method based on location information.

[0182] In the MEC application scenario, the binding of storage resources not only needs to consider resource information such as resource access mode and storage space size, but more importantly, the location information of storage resources. Only by storing data in the nearest storage resource pool can the edge computing capabilities be maximized. The disclosed embodiment makes up for the drawback of Kubernetes' storage resource binding that does not consider node location information.

[0183] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0184] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present disclosure, rather than to limit them. Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present disclosure.

Claims

1. A Kubernetes storage resource binding method based on location information, characterized in that: Applied to an edge computing controller, the method comprises: Determine whether a request for a persistent volume declaration PVC from a user terminal is received, wherein the request carries an access mode of the user terminal; If the request is received, obtaining the location information of the user terminal; Determining whether the access mode of the user terminal is a static access mode; If it is a static access mode, a first storage resource pool closest to the user terminal is selected based on the location information of the user terminal; and a first persistent volume PV1 created in the first storage resource pool is bound to the PVC; Before determining whether a request for declaring a persistent volume PVC from a user terminal is received, the method further includes: Sending a creation request for creating a persistent volume PVx to all storage resource pools in a preset area, so that each storage resource pool creates its own PVx based on the creation request, and each feeds back resource information of the PVx to the edge computing controller; and Receiving resource information of the PVx; The request also carries resource request information of the user terminal; After determining whether a request for a persistent volume declaration PVC is received from a user terminal, the method further includes: If the request is received, the PVx that meets the resource supply condition is selected from the PVx based on the resource information of the PVx and the resource request information; Selecting a first storage resource pool closest to the user terminal based on the location information of the user terminal includes: Based on the location information of the user terminal, a first storage resource pool closest to the user terminal is selected from the storage resource pools corresponding to the PVx that meets the resource supply condition.

2. The method according to claim 1, characterized in that After determining whether a request for a persistent volume declaration PVC from a user terminal is received and before obtaining the location information of the user terminal, the method further includes: Obtaining location information of a base station corresponding to the user terminal sending the request; The acquiring the location information of the user terminal includes: determining the location information of the user terminal based on the location information of the base station.

3. The method according to claim 1, characterized in that: After binding the PV1 created in the first storage resource pool to the PVC, the method further includes: The binding information after the PV1 is bound to the PVC is sent to the user terminal, so that the user terminal stores data in the PV1 based on the binding information.

4. The method according to claim 1, characterized in that: After determining whether the access mode of the user terminal is a static access mode, the method further includes: If it is not a static access mode, determining whether the access mode of the user terminal is a dynamic access mode; If it is a dynamic access mode, the storage resource pool corresponding to the SC that meets the preset conditions is selected from all storage resource pools of the created storage class SC; Selecting a second storage resource pool closest to the user terminal from the storage resource pools corresponding to the SCs meeting the preset conditions based on the location information of the user terminal; A second persistent volume PV2 is created in the second storage resource pool based on the created SC; and the PV2 is bound to the PVC.

5. The method according to claim 4, characterized in that Before determining whether a request for declaring a persistent volume PVC from a user terminal is received, the method further includes: Sending configuration requests for automatically configuring volume programs Px to all storage resource pools in a preset area respectively, so that each storage resource pool configures its own Px based on the configuration request and feeds back its own resource information to the edge controller respectively; and Based on the resource information of each storage resource pool, an SC is created for each storage resource pool, and a mapping relationship between the SC and Px in each storage resource pool is established.

6. A Kubernetes storage resource binding system based on location information, characterized in that: Applied to an edge computing controller, the system includes: A judgment module, configured to judge whether a request for a persistent volume declaration PVC from a user terminal is received, wherein the request carries an access mode of the user terminal; an acquisition module, configured to acquire the location information of the user terminal when the determination module determines that the request is received; The determination module is further configured to determine whether the access mode of the user terminal is a static access mode; A selection module configured to select a first storage resource pool closest to the user terminal based on the location information of the user terminal when the judgment module determines that the access mode is static; and A binding module, configured to bind the first persistent volume PV1 created in the first storage resource pool to the PVC; The system further comprises: A first request module is configured to send a creation request for creating a persistent volume PVx to all storage resource pools in a preset area before the judgment module determines whether a request for a persistent volume declaration PVC from a user terminal is received, so that each storage resource pool creates its own PVx based on the creation request, and each feeds back resource information of the PVx to the edge computing controller; and A receiving module, configured to receive resource information of the PVx; The request also carries resource request information of the user terminal, and the system further includes: a screening module configured to screen out PVx that meets the resource supply condition from the PVx based on the resource information of the PVx and the resource request information when the judging module determines that the request is received; The selection module is specifically configured to select, based on the location information of the user terminal, a first storage resource pool that is closest to the user terminal from the storage resource pools corresponding to the PVx that meets the resource supply condition.

7. A terminal device, characterized in that: The invention comprises a memory and a processor, wherein a computer program is stored in the memory, and when the processor runs the computer program stored in the memory, the processor executes the Kubernetes storage resource binding method based on location information according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that: A computer program is stored thereon. When the computer program is executed by a processor, the processor executes the Kubernetes storage resource binding method based on location information according to any one of claims 1 to 5.

Images