CN113254143A - Virtual network function network element arranging and scheduling method, device and system - Google Patents
Virtual network function network element arranging and scheduling method, device and system Download PDFInfo
- Publication number
- CN113254143A CN113254143A CN202010086196.6A CN202010086196A CN113254143A CN 113254143 A CN113254143 A CN 113254143A CN 202010086196 A CN202010086196 A CN 202010086196A CN 113254143 A CN113254143 A CN 113254143A
- Authority
- CN
- China
- Prior art keywords
- vnf
- network
- network element
- node
- dependency relationship
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 230000006870 function Effects 0.000 claims description 52
- 238000004891 communication Methods 0.000 claims description 34
- 238000012544 monitoring process Methods 0.000 claims description 23
- 238000004590 computer program Methods 0.000 claims description 10
- 230000004044 response Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 15
- 230000001419 dependent effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 101100491335 Caenorhabditis elegans mat-2 gene Proteins 0.000 description 2
- 102100033121 Transcription factor 21 Human genes 0.000 description 2
- 101710119687 Transcription factor 21 Proteins 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 101150031442 sfc1 gene Proteins 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a virtualized network function network element arranging and scheduling method, device and system, and relates to the technical field of containers in the field of cloud computing. The method comprises the following steps: acquiring a dependency relationship between VNF network elements in a container service chain and a network stack type of each VNF network element; acquiring the resource occupation condition of each node in each cluster; and scheduling each VNF network element according to the dependency relationship among the VNF network elements, the network stack type of each VNF network element and the resource occupation condition of each node. On the premise of meeting the requirement of service response time, the method and the system minimize the cost of container resources, can guarantee the network quality to the greatest extent, and improve the utilization rate of bottom equipment resources.
Description
Technical Field
The present disclosure relates to the field of container technologies in the field of cloud computing, and in particular, to a method, an apparatus, and a system for scheduling virtualized network function network elements.
Background
Network Function Virtualization (NFV), 5G Network element micro-service design, and containerized deployment have been trends, and each VNF (Virtual Network Function) Network element in a container service supply chain has a certain dependency relationship, and in order to ensure efficient Network transmission performance in a service scene with large concurrency and low delay, it is often necessary to schedule the VNF affinity of the container having the dependency relationship to the same cluster, the same node, or even the same Pod (container instance).
In the related art, one approach is VNF cluster-level affinity scheduling. That is, each VNF that is interdependent is scheduled to a different node in the same cluster, resulting in unstable network function performance. For VNFs with high response speed requirements, cross-node independent deployment still cannot meet low-latency scenarios, performance loss exists in cross-node communication between VNFs through a network stack, and network services are difficult to guarantee basic user experience.
One approach is VNF node level affinity scheduling. The VNFs that are mutually dependent are scheduled to the same node of the same cluster, which results in resource waste, some cluster nodes are too idle, some cluster nodes are too tight, and even the VNF of the whole service chain container cannot be scheduled under the conditions of user traffic surge and resource shortage. Kernel loopback communication needs to be carried out between container VNFs in the same node, and certain performance loss still exists.
Another approach is Tag-based VNF container group-level affinity scheduling. That is, the same Pod label is manually marked on the strongly dependent container VNF, and the strongly dependent container VNF is scheduled to run on the same Pod, which causes great difficulty in operation and maintenance. When the service needs to be upgraded and rolled back, only the Pod level can be operated in a unified way, and independent life cycle management cannot be performed on different container VNFs in the same Pod.
Disclosure of Invention
The invention provides a method, a device and a system for arranging and scheduling functional network elements of a virtualized network, which can guarantee the network quality to the greatest extent and improve the resource utilization rate of bottom equipment.
According to an aspect of the present disclosure, a method for scheduling a virtualized network function network element is provided, including: acquiring a dependency relationship between Virtual Network Function (VNF) network elements in a container service chain and a network stack type of each VNF network element; acquiring the resource occupation condition of each node in each cluster; and scheduling each VNF network element according to the dependency relationship among the VNF network elements, the network stack type of each VNF network element and the resource occupation condition of each node.
In some embodiments, orchestrating scheduling of each VNF network element comprises: judging whether a node can meet the requirement of a VNF network element with a dependency relationship or not according to the resource occupation condition of the node; judging whether the VNF network elements with the dependency relationship support direct communication of a user mode memory interface or not according to the network stack type of each VNF network element; if one node can meet the requirement of the VNF network elements with the dependency relationship, and the VNF network elements with the dependency relationship all support direct communication of user mode memory interfaces, the VNF network elements with the dependency relationship are scheduled and dispatched to the same container instance of the same node.
In some embodiments, orchestrating scheduling of each VNF network element further comprises: if one node can meet the requirement of the VNF network elements with the dependency relationship, but the VNF network elements with the dependency relationship include VNF network elements that do not support the user-mode memory interface direct communication type, the VNF network elements that support the user-mode memory interface direct communication and the VNF network elements that do not support the user-mode memory interface direct communication are respectively scheduled to different container instances of the same node.
In some embodiments, orchestrating scheduling of each VNF network element further comprises: and if one node cannot meet the requirement of the VNF network elements with the dependency relationship, arranging and scheduling the VNF network elements with the dependency relationship into different nodes of the same cluster.
In some embodiments, orchestrating scheduling of each VNF network element further comprises: if there is no dependency relationship between two VNF network elements before and after the container service chain, and one node can meet the requirements of the two VNF network elements, and the communication network delay between the two nodes cannot meet the maximum value of the network delay tolerance between the two VNF network elements, the two VNF network elements are scheduled and dispatched to different container instances of the same node.
In some embodiments, orchestrating scheduling of each VNF network element further comprises: and if the two VNF network elements before and after the container service chain have no dependency relationship and one node cannot meet the requirements of the two VNF network elements, arranging and scheduling the two VNF network elements into different nodes.
In some embodiments, VNF network elements in different container instances scheduled to the same node are orchestrated to communicate over a local loopback.
According to another aspect of the present disclosure, a virtual network function network element scheduling apparatus is further provided, including: the VNF information acquisition unit is configured to acquire the dependency relationship among VNF network elements of the virtualized network function in the container service chain and the network stack type of each VNF network element; the resource acquisition unit is configured to acquire the resource occupation condition of each node in each cluster; and the scheduling unit is configured to schedule each VNF network element according to the dependency relationship among the VNF network elements, the network stack type of each VNF network element and the resource occupation condition of each node.
According to another aspect of the present disclosure, a virtual network function network element scheduling apparatus is further provided, including: a memory; and a processor coupled to the memory, the processor configured to execute the virtualized network function network element orchestration scheduling method as described above based on the instructions stored in the memory.
According to another aspect of the present disclosure, a virtualized network function network element scheduling system is further provided, including: the VNF information setting unit is configured to store the dependency relationship among the VNF network elements of the virtualized network function in the container service chain and the network stack type of each VNF network element; the monitoring client is configured to monitor the resource occupation condition of the node and send the resource occupation condition of the node to the monitoring server; the monitoring server is configured to send the obtained resource occupation condition of each node to the virtualized network function network element arranging and scheduling device; and the arranging and scheduling device for the network element with the virtualized network function.
According to another aspect of the present disclosure, a computer-readable storage medium is also provided, on which computer program instructions are stored, and the instructions, when executed by a processor, implement the above-mentioned virtualized network function network element orchestration scheduling method.
Compared with the prior art, in the embodiment of the disclosure, each VNF network element is scheduled according to the dependency relationship among the VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node, and on the premise that the service response time requirement is met, the container resource overhead is minimized, the network quality can be guaranteed to the greatest extent, and the resource utilization rate of the bottom layer device 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
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The present disclosure may be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:
fig. 1 is a flowchart illustrating some embodiments of a virtualized network function network element orchestration scheduling method according to the present disclosure.
Fig. 2 is a flowchart illustrating a virtualized network function network element scheduling method according to another embodiment of the present disclosure.
Fig. 3 is a flowchart illustrating some embodiments of a scheduling scheme for arranging network elements of a virtualized network function according to the present disclosure.
Fig. 4 is a schematic structural diagram of some embodiments of a virtualized network function network element orchestration scheduling device according to the present disclosure.
Fig. 5 is a schematic structural diagram of another embodiment of a virtual network function network element scheduling apparatus according to the present disclosure.
Fig. 6 is a schematic structural diagram of another embodiment of a virtual network function network element scheduling apparatus according to the present disclosure.
Fig. 7 is a schematic structural diagram of some embodiments of a virtualized network function network element orchestration scheduling system according to the present disclosure.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
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.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
For the purpose of promoting a better understanding of the objects, aspects and advantages of the present disclosure, reference is made to the following detailed description taken in conjunction with the accompanying drawings.
The invention provides a virtualized network function network element scheduling method, device and system, aiming at the problems of resource waste and network function performance loss after scheduling of a container VNF.
Fig. 1 is a flowchart illustrating some embodiments of a virtualized network function network element orchestration scheduling method according to the present disclosure.
In step 110, the dependency relationship between the VNF network elements in the container service chain and the network stack type of each VNF network element are obtained.
If the network delay tolerance of two previous and next VNF network elements in one container service chain is smaller than the threshold, it indicates that the two VNF network elements have a dependency relationship.
In some embodiments, the network stack type of the VNF network element includes: and a direct communication type and a local loop communication type of a user mode memory interface are supported.
Compared to a conventional VNF network element, the VNF network element in this embodiment is a finer-grained one-container microservice VNF that can be containerized, where one container carries one VNF.
In step 120, the resource occupation of each node in each cluster is obtained.
In some embodiments, a monitoring client is arranged in each node, the monitoring client is used for monitoring the resource occupation condition of each node and feeding back the resource occupation condition to the monitoring server at regular time, and the monitoring server collects the resource occupation condition of each node uploaded by the monitoring client.
In step 130, each VNF network element is scheduled according to the dependency relationship between the VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node.
In the above embodiment, each VNF network element is scheduled according to the dependency relationship among the VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node, and on the premise that the service response time requirement is met, the container resource overhead is minimized, the network quality can be guaranteed to the maximum extent, and the resource utilization rate of the bottom layer device is improved.
Fig. 2 is a flowchart illustrating a virtualized network function network element scheduling method according to another embodiment of the present disclosure.
In step 210, the dependency relationship between the VNF network elements in the container service chain and the network stack type of each VNF network element are obtained.
In step 220, the resource occupation of each node in each cluster is obtained.
In step 230, it is determined whether a node can meet the requirement of the VNF network element having the dependency relationship according to the resource occupation of the node, if so, step 240 is executed, otherwise, step 270 is executed.
In some embodiments, it is further determined whether a node can meet the requirements of multiple VNF networks by calculating network performance requirements and resource overheads between VNF network elements in a container service chain.
In step 240, it is determined whether each VNF network element having a dependency relationship supports direct communication of the user mode memory interface according to the network stack type of each VNF network element, if so, step 250 is executed, otherwise, step 260 is executed.
In step 250, VNF network element choreographies with dependencies are scheduled into the same container instance of the same node. I.e. multiple VNF network element choreographies are scheduled into the same Pod of the same node, one Pod encapsulating one or more containers.
The VNF network elements in the same Pod of the same node are scheduled and directly communicated through a user mode memory interface, and compared with a node level affinity scheduling scheme, the VNF network elements in multiple pods are communicated through local loops, network paths and resource expenses among the VNF network elements can be reduced, performance is enhanced, and network service quality is improved.
In some embodiments, multiple VNFs are scheduled in the same Pod, and each Pod has its own independent namespace, and multiple containers in one Pod share the same namespace IPC of the isolated process, which means that the multiple containers can communicate with each other using standard inter-process communication methods, such as SystemV semaphores and POSIX sharing memory, without kernel-mode loopback communication. In addition, containers in the same Pod use one directory on the host as a shared volume (shared volume), and share data among a plurality of containers, that is, the plurality of containers multiplex memory page resources, and the container resource overhead is reduced.
In some embodiments, VNF network elements with dependency relationships may be scheduled to the same Pod in a tagging manner, and an operation and maintenance person may perform lifecycle management on any container in the Pod, thereby simplifying operation and maintenance, and scheduling VNF affinity of strongly dependent containers to the same Pod without changing an existing deployment habit.
In the related art, each VNF network element with a requirement needs to be manually tagged, and the VNF network elements with the same tag are scheduled to the same Pod, and in an actual application scenario, one VNF is usually deployed in batch or reused in multiple service chains.
In step 260, the VNF network elements supporting the direct communication of the user mode memory interface and the VNF network elements not supporting the direct communication of the user mode memory interface are respectively scheduled and dispatched to different container instances of the same node.
In some embodiments, VNF network elements in different container instances scheduled to the same node are orchestrated to communicate over a local loopback.
In step 270, VNF network element orchestrations with dependencies are scheduled into different nodes of the same cluster.
In some embodiments, the orchestration is via cross-host communication between VNF network elements scheduled to different nodes.
When a plurality of VNF network elements are dispatched to the same container instance, the VNF network elements directly communicate by using a user mode memory interface, the network performance of communication between the VNF network elements is highest, and the resource overhead to the node is also minimum; when a plurality of VNF network elements are respectively dispatched to different container instances of the same node, the VNF network elements use local loop communication to achieve secondary high performance; when multiple VNF network elements are respectively scheduled to different nodes, cross-host communication is required among the multiple VNF network elements, and network performance is the worst.
In the above embodiment, the scheduling manner in the container instance is preferentially selected according to the dependency relationship between the VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node, so that the container resource overhead is minimized on the premise of satisfying the service response time requirement.
In other embodiments of the present disclosure, when the host resources are sufficient, if there is no dependency relationship between two VNF network elements before and after the container service chain and the communication network delay between two nodes cannot satisfy the maximum value of the network delay tolerance between the two VNF network elements, the two VNF network elements are scheduled to different container instances of the same node.
In some embodiments, if there is no dependency between two VNF network elements before and after the container service chain, and one node cannot meet the requirements of the two VNF network elements, the two VNF network elements are scheduled into different nodes.
In some embodiments, as shown in FIG. 3. The container service chain SFC1 includes a VNF1 network element, a VNF2 network element, a VNF3 network element, and a VNF4 network element, where the VNF1 network element and the VNF2 network element have a dependency relationship therebetween. Node A includes Pod1 and Pod2, and node B includes Pod3 and other pods. The monitoring client A monitors the resource occupation condition of the node A, and the monitoring client B monitors the resource occupation condition of the node B, wherein the monitoring client A and the monitoring client B respectively send the monitored resource occupation condition of the node to the monitoring server. And the scheduling decision module is used for collecting the dependency relationship of the VNF network elements and the node resource use condition analyzed by the monitoring server side, and scheduling the VNF network elements to appropriate nodes or pods according to the requirements. For example, VNF1 network elements and VNF2 network elements are orchestrated into Pod1 of node a, VNF3 network elements are orchestrated into Pod2 of node a, and VNF4 network elements are orchestrated into Pod3 of node B. The VNF1 network element and the VNF2 network element communicate directly through a user mode memory interface, and the VNF1 network element and the VNF3 network element communicate through a local loopback.
In the embodiment, the network service quality can be guaranteed, the basic user experience is met, the resource utilization rate can be improved by minimizing the container resource overhead, and the reasonable arrangement and scheduling of the VNF of the container service chain are realized.
Fig. 4 is a schematic structural diagram of some embodiments of a virtualized network function network element orchestration scheduling device according to the present disclosure. The apparatus includes a VNF information acquisition unit 410, a resource acquisition unit 420, and a orchestration scheduling unit 430.
The VNF information obtaining unit 410 is configured to obtain a dependency relationship between VNF network elements in the container service chain and a network stack type of each VNF network element.
The resource obtaining unit 420 is configured to obtain resource occupation of each node in each cluster.
The orchestration scheduling unit 430 is configured to perform orchestration scheduling on each VNF network element according to the dependency relationship between the VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node.
In some embodiments, whether a node can meet the requirement of a VNF network element having a dependency relationship is determined according to a resource occupation situation of the node; judging whether the VNF network elements with the dependency relationship support direct communication of a user mode memory interface or not according to the network stack type of each VNF network element; if one node can meet the requirement of the VNF network elements with the dependency relationship, and the VNF network elements with the dependency relationship all support direct communication of user mode memory interfaces, the VNF network elements with the dependency relationship are scheduled and dispatched to the same container instance of the same node.
In some embodiments, if one node can meet the requirement of a VNF network element having a dependency relationship, but the VNF network element having the dependency relationship includes a VNF network element that does not support a user-mode memory interface direct communication type, the VNF network element that supports the user-mode memory interface direct communication and the VNF network element that does not support the user-mode memory interface direct communication are respectively scheduled in different container instances of the same node.
In some embodiments, if one node cannot meet the requirement of the VNF network elements with dependencies, the VNF network elements with dependencies are orchestrated and scheduled into different nodes of the same cluster.
In some embodiments, if there is no dependency between two VNF network elements before and after the container service chain, and one node can meet the requirements of the two VNF network elements, and the communication network delay between the two nodes cannot meet the maximum value of the network delay tolerance between the two VNF network elements, the two VNF network elements are scheduled and dispatched to different container instances of the same node. VNF network elements in different container instances scheduled to the same node communicate through a local loopback.
In some embodiments, if there is no dependency between two VNF network elements before and after the container service chain, and one node cannot meet the requirements of the two VNF network elements, the two VNF network elements are scheduled into different nodes.
In the above embodiment, the scheduling manner in the container instance is preferentially selected according to the dependency relationship between the VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node, which can ensure the network service quality, meet the basic user experience, minimize the container resource overhead, improve the resource utilization rate, and realize the reasonable scheduling of the VNF in the container service chain.
Fig. 5 is a schematic structural diagram of another embodiment of a virtual network function network element scheduling apparatus according to the present disclosure. The device includes: a memory 510 and a processor 520, wherein: the memory 510 may be a magnetic disk, flash memory, or any other non-volatile storage medium. The memory is used to store instructions in the embodiments corresponding to fig. 1-2. Processor 520 is coupled to memory 510 and may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 520 is configured to execute instructions stored in memory.
In some embodiments, as also shown in fig. 6, the apparatus 600 includes a memory 610 and a processor 620. Processor 620 is coupled to memory 610 through a BUS 630. The apparatus 600 may also be coupled to an external storage device 650 via a storage interface 640 for external data retrieval, and may also be coupled to a network or another computer system (not shown) via a network interface 660, which will not be described in detail herein.
In the embodiment, the data instruction is stored in the memory, and the instruction is processed by the processor, so that the network quality can be guaranteed to the greatest extent, and the resource utilization rate of bottom-layer equipment is improved.
Fig. 7 is a schematic structural diagram of some embodiments of a virtualized network function network element orchestration scheduling system according to the present disclosure. The system comprises a VNF information setting unit 710, a monitoring client 720, a monitoring server 730, and a virtualized network function network element orchestration scheduling device 740. The virtualized network function network element orchestration scheduler 740 is described in detail in the above embodiments, and is not further described here.
The VNF information setting unit 710 is configured to store dependencies between virtualized network functions VNF network elements in the container service chain and a network stack type of each VNF network element.
If the network delay tolerance of two previous and next VNF network elements in one container service chain is smaller than the threshold, it indicates that the two VNF network elements have a dependency relationship.
In some embodiments, the network stack type of the VNF network element includes a direct communication type supporting a user mode memory interface and a local loopback communication type.
The monitoring client 720 is configured to monitor the resource occupation of the node, and send the resource occupation of the node to the monitoring server 730.
The monitoring server 730 is configured to send the obtained resource occupation status of each node to the virtualized network function network element orchestration scheduling device 740.
In other embodiments, a non-transitory computer-readable storage medium has stored thereon computer program instructions which, when executed by a processor, implement the steps of the method in the embodiments corresponding to fig. 1-2. As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, apparatus, 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.
Thus far, the present disclosure has been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.
Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the foregoing examples are for purposes of illustration only and are not intended to limit the scope of the present disclosure. It will be appreciated by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.
Claims (11)
1. A virtual network function network element scheduling method comprises the following steps:
acquiring a dependency relationship between Virtual Network Function (VNF) network elements in a container service chain and a network stack type of each VNF network element;
acquiring the resource occupation condition of each node in each cluster;
and scheduling each VNF network element according to the dependency relationship among the VNF network elements, the network stack type of each VNF network element and the resource occupation condition of each node.
2. The virtualized network function network element orchestration scheduling method of claim 1, wherein performing orchestration scheduling on each VNF network element comprises:
judging whether a node can meet the requirement of a VNF network element with a dependency relationship or not according to the resource occupation condition of the node;
judging whether the VNF network elements with the dependency relationship support direct communication of a user mode memory interface or not according to the network stack type of each VNF network element;
if the node can meet the requirement of the VNF network elements with the dependency relationship and the VNF network elements with the dependency relationship all support direct communication of a user mode memory interface, the VNF network elements with the dependency relationship are scheduled and dispatched to the same container instance of the same node.
3. The virtualized network function network element orchestration scheduling method of claim 2, wherein performing orchestration scheduling on each VNF network element further comprises:
if the node can meet the requirement of the VNF network element with the dependency relationship, but the VNF network element with the dependency relationship includes a VNF network element that does not support the user-mode memory interface direct communication type, the VNF network element that supports the user-mode memory interface direct communication and the VNF network element that does not support the user-mode memory interface direct communication are respectively scheduled in different container instances of the same node.
4. The virtualized network function network element orchestration scheduling method of claim 2, wherein performing orchestration scheduling on each VNF network element further comprises:
and if the node cannot meet the requirement of the VNF network elements with the dependency relationship, arranging and scheduling the VNF network elements with the dependency relationship to different nodes of the same cluster.
5. The method for orchestration scheduling of network elements of virtual network functions according to any one of claims 2 to 4, wherein performing orchestration scheduling on each VNF network element further comprises:
if there is no dependency relationship between two VNF network elements before and after the container service chain, one node can meet the requirements of the two VNF network elements, but the communication network delay between the two nodes cannot meet the maximum value of the network delay tolerance between the two VNF network elements, arranging and scheduling the two VNF network elements to different container instances of the same node.
6. The virtualized network function network element orchestration scheduling method of claim 5, wherein performing orchestration scheduling on each VNF network element further comprises:
and if there is no dependency relationship between two VNF network elements before and after the container service chain, and one node cannot meet the requirements of the two VNF network elements, arranging and scheduling the two VNF network elements into different nodes.
7. The virtualized network functional network element orchestration scheduling method of claim 3,
VNF network elements in different container instances scheduled to the same node communicate through a local loopback.
8. A virtualized network function network element orchestration scheduling device, comprising:
the VNF information acquisition unit is configured to acquire the dependency relationship among VNF network elements of the virtualized network function in the container service chain and the network stack type of each VNF network element;
the resource acquisition unit is configured to acquire the resource occupation condition of each node in each cluster;
and the scheduling unit is configured to schedule each VNF network element according to the dependency relationship among the VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node.
9. A virtualized network function network element orchestration scheduling device, comprising:
a memory; and
a processor coupled to the memory, the processor configured to execute the virtualized network functional network element orchestration scheduling method of any of claims 1-7 based on instructions stored in the memory.
10. A virtualized network function network element orchestration scheduling system, comprising:
the VNF information setting unit is configured to store the dependency relationship among the VNF network elements of the virtualized network function in the container service chain and the network stack type of each VNF network element;
the monitoring client is configured to monitor the resource occupation condition of the node and send the resource occupation condition of the node to the monitoring server;
the monitoring server is configured to send the obtained resource occupation condition of each node to the virtualized network function network element arranging and scheduling device; and
a virtualized network function network element orchestration scheduling device according to claim 8 or 9.
11. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the virtualized network functional network element orchestration scheduling method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010086196.6A CN113254143B (en) | 2020-02-11 | 2020-02-11 | Virtualized network function network element arrangement scheduling method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010086196.6A CN113254143B (en) | 2020-02-11 | 2020-02-11 | Virtualized network function network element arrangement scheduling method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113254143A true CN113254143A (en) | 2021-08-13 |
| CN113254143B CN113254143B (en) | 2023-11-21 |
Family
ID=77219488
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010086196.6A Active CN113254143B (en) | 2020-02-11 | 2020-02-11 | Virtualized network function network element arrangement scheduling method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113254143B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024001559A1 (en) * | 2022-06-28 | 2024-01-04 | 中兴通讯股份有限公司 | Service scheduling method, electronic device and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140317261A1 (en) * | 2013-04-22 | 2014-10-23 | Cisco Technology, Inc. | Defining interdependent virtualized network functions for service level orchestration |
| CN106506201A (en) * | 2016-10-31 | 2017-03-15 | 中国联合网络通信集团有限公司 | VNF moving methods, MANO and system |
| CN108958882A (en) * | 2018-06-06 | 2018-12-07 | 麒麟合盛网络技术股份有限公司 | A kind of container method of adjustment, device and system |
| US20190220315A1 (en) * | 2018-01-12 | 2019-07-18 | Robin Systems, Inc. | Dynamic Adjustment Of Application Resources In A Distributed Computing System |
| CN110311798A (en) * | 2018-03-20 | 2019-10-08 | 华为技术有限公司 | A kind of method and device managing virtual resource |
| CN110392882A (en) * | 2017-01-13 | 2019-10-29 | 瑞典爱立信有限公司 | It is created in batches in the network for including virtualization network function by pipe function |
| CN110457135A (en) * | 2019-08-09 | 2019-11-15 | 重庆紫光华山智安科技有限公司 | A kind of method of resource regulating method, device and shared GPU video memory |
-
2020
- 2020-02-11 CN CN202010086196.6A patent/CN113254143B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140317261A1 (en) * | 2013-04-22 | 2014-10-23 | Cisco Technology, Inc. | Defining interdependent virtualized network functions for service level orchestration |
| US20140317293A1 (en) * | 2013-04-22 | 2014-10-23 | Cisco Technology, Inc. | App store portal providing point-and-click deployment of third-party virtualized network functions |
| CN106506201A (en) * | 2016-10-31 | 2017-03-15 | 中国联合网络通信集团有限公司 | VNF moving methods, MANO and system |
| CN110392882A (en) * | 2017-01-13 | 2019-10-29 | 瑞典爱立信有限公司 | It is created in batches in the network for including virtualization network function by pipe function |
| US20190220315A1 (en) * | 2018-01-12 | 2019-07-18 | Robin Systems, Inc. | Dynamic Adjustment Of Application Resources In A Distributed Computing System |
| CN110311798A (en) * | 2018-03-20 | 2019-10-08 | 华为技术有限公司 | A kind of method and device managing virtual resource |
| CN108958882A (en) * | 2018-06-06 | 2018-12-07 | 麒麟合盛网络技术股份有限公司 | A kind of container method of adjustment, device and system |
| CN110457135A (en) * | 2019-08-09 | 2019-11-15 | 重庆紫光华山智安科技有限公司 | A kind of method of resource regulating method, device and shared GPU video memory |
Non-Patent Citations (1)
| Title |
|---|
| 汤红波;邱航;游伟;季新生;: "基于联合备份的服务功能链可靠性保障的部署方法", 电子与信息学报, no. 12 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024001559A1 (en) * | 2022-06-28 | 2024-01-04 | 中兴通讯股份有限公司 | Service scheduling method, electronic device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113254143B (en) | 2023-11-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106802826B (en) | Service processing method and device based on thread pool | |
| CN107038069B (en) | Dynamic label matching DLMS scheduling method under Hadoop platform | |
| CN110888743B (en) | GPU resource using method, device and storage medium | |
| US10733019B2 (en) | Apparatus and method for data processing | |
| CN115328663B (en) | Method, device, equipment and storage medium for scheduling resources based on PaaS platform | |
| US9319281B2 (en) | Resource management method, resource management device, and program product | |
| CN109564528B (en) | System and method for computing resource allocation in distributed computing | |
| CN107431696A (en) | Method and cloud management node for application automatically dispose | |
| CN114138486A (en) | Containerized micro-service arranging method, system and medium for cloud edge heterogeneous environment | |
| WO2016039963A2 (en) | Resource sharing between two resource allocation systems | |
| CN112114950A (en) | Task scheduling method and device and cluster management system | |
| US11347546B2 (en) | Task scheduling method and device, and computer storage medium | |
| CN107818012B (en) | Data processing method and device and electronic equipment | |
| CN108509280B (en) | Distributed computing cluster locality scheduling method based on push model | |
| US20180191861A1 (en) | Method and Apparatus for Scheduling Resources in a Cloud System | |
| CN112860387A (en) | Distributed task scheduling method and device, computer equipment and storage medium | |
| CN108170417B (en) | Method and device for integrating high-performance job scheduling framework in MESOS cluster | |
| CN111459622A (en) | Method and device for scheduling virtual CPU, computer equipment and storage medium | |
| CN108829516B (en) | Resource virtualization scheduling method for graphic processor | |
| CN113051049B (en) | Task scheduling system, method, electronic device and readable storage medium | |
| CN113254143B (en) | Virtualized network function network element arrangement scheduling method, device and system | |
| CN117608760A (en) | Cloud application hybrid deployment method applied to Kubernetes | |
| CN115964176B (en) | Cloud computing cluster scheduling method, electronic equipment and storage medium | |
| CN112486638A (en) | Method, apparatus, device and storage medium for executing processing task | |
| CN112015515A (en) | Virtual network function instantiation method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |