CN113254143B - Virtualized network function network element arrangement scheduling method, device and system - Google Patents
Virtualized network function network element arrangement scheduling method, device and system Download PDFInfo
- Publication number
- CN113254143B CN113254143B CN202010086196.6A CN202010086196A CN113254143B CN 113254143 B CN113254143 B CN 113254143B CN 202010086196 A CN202010086196 A CN 202010086196A CN 113254143 B CN113254143 B CN 113254143B
- Authority
- CN
- China
- Prior art keywords
- vnf
- network element
- node
- network
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000006870 function Effects 0.000 claims description 56
- 238000004891 communication Methods 0.000 claims description 36
- 238000012544 monitoring process Methods 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims description 10
- 230000004044 response Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 16
- 238000012545 processing Methods 0.000 description 4
- 238000013459 approach 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
- 230000001419 dependent effect Effects 0.000 description 2
- 238000012423 maintenance Methods 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
- 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
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 method, a device and a system for arranging and scheduling network elements of a virtualized network function, 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. The method and the device have the advantages that on the premise of meeting the service response time requirement, the cost of container resources is minimized, the network quality can be guaranteed to the greatest extent, and the resource utilization rate of bottom equipment is improved.
Description
Technical Field
The disclosure relates to the technical field of containers in the field of cloud computing, and in particular relates to a method, a device and a system for scheduling network element arrangement of a virtualized network function.
Background
NFV (Network Functions Virtualization, network function virtualization), 5G network element micro-service design, and containerized deployment have been trends, but each VNF (Virtual Network Function, virtualized network function) in a container service supply chain has a certain dependency relationship between network elements, and in a service scenario with large concurrency and low latency, in order to ensure efficient network transmission performance, it is often required to schedule the container VNF affinity with the dependency relationship into the same cluster, the same node, and even the same Pod (container instance).
In the related art, one approach is VNF cluster level affinity scheduling. I.e. scheduling the interdependent VNFs to different nodes of the same cluster, results in unstable network functionality. For VNFs with high response speed requirements, the VNFs are deployed independently across nodes, and still cannot meet a low latency scenario, performance loss exists in inter-VNF cross-node communication through a network stack, and it is difficult for network services to guarantee basic user experience.
One approach is VNF node level affinity scheduling. That is, each VNF that is interdependent is scheduled to the same node of the same cluster, resulting 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. The inter-VNF communication between the container VNFs in the same node needs to go through the kernel loop, and there is still a certain performance loss.
Another approach is Tag (label) based VNF container group level affinity scheduling. I.e. the VNFs of strongly dependent containers are manually labeled with the same Pod and scheduled to run on the same Pod, resulting in great operational difficulties. When the service needs to upgrade and roll back, only the Pod level can be operated uniformly, and independent life cycle management can not be carried out on different container VNs in the same Pod.
Disclosure of Invention
The invention provides a method, a device and a system for arranging and scheduling network elements of a virtualized network function, which can ensure 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 network element arrangement of a virtualized network function 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 includes: judging whether one node can meet the requirement of a VNF network element with a dependency relationship according to the resource occupation condition of the node; judging whether the VNF network elements with the dependency relationship support direct communication of the user state memory interface according to the network stack type of each VNF network element; if one node can meet the requirement of the VNF network element with the dependency relationship and the VNF network element with the dependency relationship supports direct communication of the user mode memory interface, the VNF network element with the dependency relationship is scheduled to the same container instance of the same node.
In some embodiments, scheduling each VNF network element further includes: if one node can meet the requirement of the VNF network element with the dependency relationship, but the VNF network element with the dependency relationship includes the VNF network element which does not support the direct communication type of the user mode memory interface, the VNF network element which supports the direct communication of the user mode memory interface and the VNF network element which does not support 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, scheduling each VNF network element further includes: and if one node cannot meet the requirement of the VNF network element with the dependency relationship, scheduling the VNF network element with the dependency relationship to different nodes of the same cluster.
In some embodiments, scheduling each VNF network element further includes: 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 to different container instances of the same node.
In some embodiments, scheduling each VNF network element further includes: 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 to different nodes.
In some embodiments, VNF network elements in different container instances scheduled to the same node are orchestrated to communicate over a local loop.
According to another aspect of the present disclosure, there is also provided a virtualized network function network element orchestration scheduling device, including: the VNF information acquiring unit is configured to acquire a dependency relationship between the virtualized network function VNF network elements in the container service chain and a 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; 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, there is also provided a virtualized network function network element orchestration scheduling device, including: a memory; and a processor coupled to the memory, the processor configured to perform the virtualized network function network element orchestration scheduling method described above based on instructions stored in the memory.
According to another aspect of the present disclosure, there is also provided a virtualized network function network element orchestration scheduling system, including: the VNF information setting unit is configured to store the dependency relationship between the virtual network function VNF network elements 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 arrangement scheduling device; the virtualized network function network element arranging and scheduling device.
According to another aspect of the disclosure, a computer readable storage medium is also provided, on which computer program instructions are stored, which instructions, when executed by a processor, implement the above-mentioned virtualized network function network element orchestration scheduling method.
Compared with the related art, in the embodiment of the disclosure, each VNF network element is scheduled according to the dependency relationship among 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 meeting the service response time requirement, the network quality can be ensured to the greatest extent, and the resource utilization rate of the bottom layer device is improved.
Other features of the present disclosure and its advantages will become apparent from the following detailed description of exemplary embodiments of the disclosure, 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 disclosure may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings in which:
fig. 1 is a flow diagram of some embodiments of a virtualized network function network element orchestration scheduling method of the present disclosure.
Fig. 2 is a flow chart illustrating further embodiments of a virtualized network function network element orchestration scheduling method of the present disclosure.
Fig. 3 is a flow diagram of some embodiments of a virtualized network function network element orchestration scheduling scheme of the present disclosure.
Fig. 4 is a schematic structural diagram of some embodiments of a virtualized network function network element orchestration scheduler of the present disclosure.
Fig. 5 is a schematic structural diagram of other embodiments of a virtualized network function network element orchestration scheduling device of the present disclosure.
Fig. 6 is a schematic structural diagram of other embodiments of a virtualized network function network element orchestration scheduling device of the present disclosure.
Fig. 7 is a schematic structural diagram of some embodiments of a virtualized network function network element orchestration scheduling system of 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, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless it is specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective parts shown in the drawings are not drawn in actual scale for 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 one of ordinary skill in the relevant art may not be discussed in detail, but should be considered part of the specification where appropriate.
In all examples shown and discussed herein, any specific values should be construed as merely illustrative, and not a limitation. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further discussion thereof is necessary in subsequent figures.
For the purposes of promoting an understanding of the principles and advantages of the disclosure, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same.
Aiming at the problems of resource waste and performance loss of network functions after the scheduling of the container VNF, the present disclosure provides a method, a device and a system for scheduling the network elements of the virtualized network function.
Fig. 1 is a flow diagram of some embodiments of a virtualized network function network element orchestration scheduling method of the present disclosure.
In step 110, a dependency relationship between VNF network elements in a container service chain and a network stack type of each VNF network element are obtained.
If the network delay tolerance of the front and rear VNF network elements in one container service chain is smaller than the threshold value, it is indicated that the two VNF network elements have a dependency relationship.
In some embodiments, the network stack type of the VNF network element includes: and supporting the direct communication type and the local loop communication type of the user-state memory interface.
The VNF network element in this embodiment is a more fine-grained one-container micro-service VNF that can be containerized, compared to a traditional VNF network element, where one container carries one VNF.
In step 120, the resource occupancy of each node in each cluster is obtained.
In some embodiments, a monitoring client is set in each node, and the monitoring client is used for monitoring the resource occupation condition of each node, feeding back the resource occupation condition to the monitoring server in a timing manner, and the monitoring server collects the resource occupation condition of each node uploaded by the monitoring client.
In step 130, scheduling is performed on each VNF network element according to the dependency relationship between VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node.
In the above embodiment, according to the dependency relationship among VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node, each VNF network element is scheduled, and on the premise of meeting the service response time requirement, the container resource overhead is minimized, the network quality can be ensured to the greatest extent, and the resource utilization rate of the bottom layer device is improved.
Fig. 2 is a flow chart illustrating further embodiments of a virtualized network function network element orchestration scheduling method of the present disclosure.
In step 210, a dependency relationship between VNF network elements in a container service chain and a network stack type of each VNF network element are obtained.
In step 220, the resource occupancy 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 with the dependency relationship according to the resource occupation condition of the node, if so, step 240 is performed, otherwise, step 270 is performed.
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 overhead between VNF network elements in the container service chain.
In step 240, according to the network stack type of each VNF network element, it is determined whether the VNF network elements with the dependency relationship support direct communication of the user mode memory interface, if so, step 250 is performed, otherwise, step 260 is performed.
In step 250, VNF network element arrangements with dependencies are scheduled into the same container instance of the same node. I.e. multiple VNF network elements are orchestrated and scheduled into the same Pod of the same node, one Pod encapsulating one or more containers.
Compared with the node-level affinity scheduling scheme, the VNF network elements in the multiple Pods can reduce network paths and resource expenses among the VNF network elements through local loop communication, enhance performance and improve network service quality.
In some embodiments, multiple VNFs are scheduled into the same Pod, and since each Pod has its own independent namespace, multiple containers in one Pod may share the same isolated process's namespace IPC, which is equivalent to multiple containers may communicate with each other using standard inter-process communication methods, such as SystemV semaphores and POSIX shared memory, without the need for kernel-mode loop-back communication. In addition, the containers in the same Pod use a directory on the host as a shared volume (shared volume), and share data among multiple containers, i.e. multiple containers multiplex memory page resources, so as to reduce the cost of the container resources.
In some embodiments, VNF network elements with a dependency relationship may be scheduled to the same Pod in a labeled manner, so that an operation and maintenance person may perform lifecycle management on any container in the Pod, simplifying operation and maintenance, and enabling VNF affinity of a strongly dependent container to be scheduled to the same Pod while not changing an existing deployment habit.
In the related art, each VNF network element with a requirement needs to be manually labeled, and VNF network elements with the same label are scheduled to the same Pod, in an actual application scenario, one VNF is usually deployed in batches or reused in multiple service chains, in this embodiment, only VNFs with a dependency relationship are labeled and deployed in the same Pod.
In step 260, the VNF network elements supporting direct communication of the user state memory interface and the VNF network elements not supporting direct communication of the user state memory interface are respectively scheduled 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 loop.
In step 270, VNF network element arrangements with dependencies are scheduled into different nodes of the same cluster.
In some embodiments, VNF network elements scheduled to different nodes are orchestrated to communicate across hosts.
When a plurality of VNF network elements are scheduled to the same container instance, the VNF network elements directly communicate by using a user mode memory interface, the network performance of the communication between the VNF network elements is highest, and the resource cost to the node is also minimum; when a plurality of VNF network elements are respectively scheduled to container examples with different nodes, local loop communication is utilized among the VNF network elements, so that the performance is low; when multiple VNF network elements are respectively scheduled to different nodes, inter-host communication is required between the multiple VNF network elements, and network performance is the worst.
In the above embodiment, according to the dependency relationship between VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node, the arrangement mode in the container instance is preferentially selected, and on the premise of meeting the service response time requirement, the container resource overhead is minimized.
In other embodiments of the present disclosure, when the host resources are sufficient, if there is no dependency between two VNF network elements before and after the container service chain, and the communication network delay between two nodes cannot meet the maximum value of the network delay tolerance between 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 to 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 a dependency relationship exists between the VNF1 network element and the VNF2 network element. Node a includes Pod1 and Pod2, and node B includes Pod3, among 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. The scheduling decision module gathers the dependency relationship of the VNF network elements, monitors the node resource use condition analyzed by the server, and schedules the VNF network elements to appropriate nodes or Pods according to the need. For example, VNF1 and VNF2 network elements are scheduled into Pod1 of node a, VNF3 network element is scheduled into Pod2 of node a, and VNF4 network element is scheduled into Pod3 of node B. The VNF1 network element and the VNF2 network element are directly communicated through a user mode memory interface, and the VNF1 network element and the VNF3 network element are communicated through a local loop.
In the above embodiment, the network service quality can be ensured, the basic user experience is satisfied, the container resource overhead can be minimized, the resource utilization rate is improved, and the container service chain VNF rationalization scheduling is realized.
Fig. 4 is a schematic structural diagram of some embodiments of a virtualized network function network element orchestration scheduler of the present disclosure. The apparatus includes a VNF information acquisition unit 410, a resource acquisition unit 420, and an 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 a resource occupation situation of each node in each cluster.
The orchestration scheduling unit 430 is configured to orchestrate and schedule each VNF network element according to the dependency relationship between VNF network elements, the network stack type of each VNF network element, and the resource occupancy of each node.
In some embodiments, according to the resource occupation condition of the nodes, judging whether one node can meet the requirement of the VNF network element with the dependency relationship; judging whether the VNF network elements with the dependency relationship support direct communication of the user state memory interface according to the network stack type of each VNF network element; if one node can meet the requirement of the VNF network element with the dependency relationship and the VNF network element with the dependency relationship supports direct communication of the user mode memory interface, the VNF network element with the dependency relationship is scheduled to the same container instance of the same node.
In some embodiments, if a node can meet the requirement of a VNF network element with a dependency relationship, but the VNF network element with a dependency relationship includes a VNF network element that does not support a direct communication type of a user state memory interface, the VNF network element that supports direct communication of the user state memory interface and the VNF network element that does not support direct communication of the user state memory interface are respectively scheduled and scheduled to different container instances of the same node.
In some embodiments, if a node cannot meet the requirement of a VNF network element with a dependency, the VNF network element with the dependency is scheduled to 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 to different container instances of the same node. VNF network elements in different container instances scheduled to the same node are orchestrated to communicate via a local loop.
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 to different nodes.
In the above embodiment, according to the dependency relationship between VNF network elements, the network stack type of each VNF network element, and the resource occupation condition of each node, the arrangement mode in the container instance is preferentially selected, which not only can ensure the network service quality, satisfy the basic user experience, but also can minimize the container resource overhead and improve the resource utilization ratio, thereby realizing the rationalized arrangement and scheduling of the container service chain VNF.
Fig. 5 is a schematic structural diagram of other embodiments of a virtualized network function network element orchestration scheduling device of the present disclosure. The device comprises: memory 510 and processor 520, wherein: 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 corresponding embodiments of 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 the 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 BUS 630. The device 600 may also be coupled to external storage 650 via a storage interface 640 for invoking external data, and may also be coupled to a network or another computer system (not shown) via a network interface 660, not described in detail herein.
In the embodiment, the data instruction is stored by the memory, and then the instruction is processed by the processor, so that the network quality can be ensured to the greatest extent, and the resource utilization rate of the bottom equipment is improved.
Fig. 7 is a schematic structural diagram of some embodiments of a virtualized network function network element orchestration scheduling system of 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 scheduler 740. Wherein virtualized network function network element orchestration scheduler 740 is described in detail in the above embodiments and is not further described herein.
The VNF information setting unit 710 is configured to store a dependency relationship between the virtualized network function VNF network elements in the container service chain and a network stack type of each VNF network element.
If the network delay tolerance of the front and rear VNF network elements in one container service chain is smaller than the threshold value, it is indicated that the two VNF network elements have a dependency relationship.
In some embodiments, the network stack types of the VNF network elements include a direct communication type supporting a user mode memory interface and a local loop back communication type.
The monitoring client 720 is configured to monitor the resource occupancy of the node, and send the resource occupancy of the node to the monitoring server 730.
The monitoring server 730 is configured to send the obtained resource occupancy status of each node to the virtualized network function network element orchestration scheduler 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 of the corresponding embodiments of fig. 1-2. It will be apparent to those skilled in the art that 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, etc.) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Thus far, the present disclosure has been described in detail. In order to avoid obscuring the concepts of the present disclosure, some details known in the art are not described. How to implement the solutions disclosed herein will be fully apparent to those skilled in the art from the above description.
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 above examples are for 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 disclosure. The scope of the present disclosure is defined by the appended claims.
Claims (10)
1. A virtual network function network element arranging and 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;
scheduling 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, including:
judging whether one node can meet the requirement of a VNF network element with a dependency relationship according to the resource occupation condition of the node;
judging whether the VNF network elements with the dependency relationship support direct communication of the user state memory interface according to the network stack type of each VNF network element;
and if the node can meet the requirement of the VNF network element with the dependency relationship and the VNF network element with the dependency relationship supports direct communication of the user-mode memory interface, scheduling the VNF network element with the dependency relationship into the same container instance of the same node.
2. The virtualized network function network element orchestration scheduling method according to claim 1, wherein orchestrating scheduling 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 direct communication of the user mode memory interface, the VNF network element that supports direct communication of the user mode memory interface and the VNF network element that does not support direct communication of the user mode memory interface are respectively scheduled and scheduled to different container instances of the same node.
3. The virtualized network function network element orchestration scheduling method according to claim 1, wherein orchestrating scheduling each VNF network element further comprises:
and if the one node cannot meet the requirement of the VNF network element with the dependency relationship, scheduling the VNF network element with the dependency relationship to different nodes of the same cluster.
4. A virtualized network function network element orchestration scheduling method according to any of claims 1-3, wherein orchestrating scheduling 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 two nodes cannot meet the maximum value of the network delay tolerance between the two VNF network elements, and then the two VNF network elements are scheduled to different container instances of the same node.
5. The virtualized network function network element orchestration scheduling method of claim 4, wherein orchestrating scheduling 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 cannot meet the requirements of the two VNF network elements, scheduling the two VNF network elements into different nodes.
6. The virtualized network function network element orchestration scheduling method of claim 2, wherein,
VNF network elements in different container instances scheduled to the same node are orchestrated to communicate via a local loop.
7. A virtualized network function network element orchestration scheduling device, comprising:
the VNF information acquiring unit is configured to acquire a dependency relationship between the virtualized network function VNF network elements in the container service chain and a 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;
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, wherein the scheduling unit is configured to determine whether one node can satisfy the requirement of the VNF network element with the dependency relationship according to the resource occupation condition of the node, determine whether the VNF network element with the dependency relationship supports direct communication of a user-mode memory interface according to the network stack type of each VNF network element, and schedule the VNF network element with the dependency relationship to the same container instance of the same node if one node can satisfy the requirement of the VNF network element with the dependency relationship and the VNF network element with the dependency relationship supports direct communication of the user-mode memory interface.
8. A virtualized network function network element orchestration scheduling device, comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the virtualized network function network element orchestration scheduling method according to any one of claims 1-6 based on instructions stored in the memory.
9. A virtualized network function network element orchestration scheduling system, comprising:
the VNF information setting unit is configured to store the dependency relationship between the virtual network function VNF network elements 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 arrangement scheduling device; and
the virtualized network function network element orchestration scheduling device of claim 7 or 8.
10. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the virtualized network function network element orchestration scheduling method of any one of claims 1-6.
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 CN113254143A (en) | 2021-08-13 |
| CN113254143B true 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) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117348981A (en) * | 2022-06-28 | 2024-01-05 | 中兴通讯股份有限公司 | Service scheduling method, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9973375B2 (en) * | 2013-04-22 | 2018-05-15 | Cisco Technology, Inc. | App store portal providing point-and-click deployment of third-party virtualized network functions |
| US10846137B2 (en) * | 2018-01-12 | 2020-11-24 | Robin Systems, Inc. | Dynamic adjustment of application resources in a distributed computing system |
-
2020
- 2020-02-11 CN CN202010086196.6A patent/CN113254143B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
|---|
| 基于联合备份的服务功能链可靠性保障的部署方法;汤红波;邱航;游伟;季新生;;电子与信息学报(第12期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113254143A (en) | 2021-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110704186B (en) | Computing resource allocation method and device based on hybrid distribution architecture and storage medium | |
| US20190377604A1 (en) | Scalable function as a service platform | |
| CN107038069B (en) | Dynamic label matching DLMS scheduling method under Hadoop platform | |
| CN110888743B (en) | GPU resource using method, device and storage medium | |
| CN115328663B (en) | Method, device, equipment and storage medium for scheduling resources based on PaaS platform | |
| CN105045658B (en) | A method of realizing that dynamic task scheduling is distributed using multinuclear DSP embedded | |
| US20160072726A1 (en) | Systems and methods for resource sharing between two resource allocation systems | |
| CN110661842B (en) | Resource scheduling management method, electronic equipment and storage medium | |
| CN108509280B (en) | Distributed computing cluster locality scheduling method based on push model | |
| US20240111549A1 (en) | Method and apparatus for constructing android running environment | |
| CN101751288A (en) | Method, device and system applying process scheduler | |
| CN114138434B (en) | Big data task scheduling system | |
| CN112486642B (en) | Resource scheduling method, device, electronic equipment and computer readable storage medium | |
| CN108170417B (en) | Method and device for integrating high-performance job scheduling framework in MESOS cluster | |
| CN116627661B (en) | Method and system for scheduling computing power resources | |
| CN112162852A (en) | Multi-architecture CPU node management method, device and related components | |
| WO2020108337A1 (en) | Cpu resource scheduling method and electronic equipment | |
| CN115454629A (en) | AI algorithm and micro-service scheduling method and device based on cloud native technology | |
| CN113254143B (en) | Virtualized network function network element arrangement scheduling method, device and system | |
| CN111459622A (en) | Method and device for scheduling virtual CPU, computer equipment and storage medium | |
| CN108829516B (en) | Resource virtualization scheduling method for graphic processor | |
| CN117608760A (en) | Cloud application hybrid deployment method applied to Kubernetes | |
| CN110175078B (en) | Service processing method and device | |
| CN112395056A (en) | Embedded asymmetric real-time system and electric power secondary equipment | |
| CN111400021B (en) | Deep learning method, device and system |
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 |