A method, system, device and storage medium for realizing fast capacity expansion and contraction of an NFV network element in a VI layer

Abstract

The application discloses a method, system, device and storage medium for realizing quick expansion and contraction of an NFV network element in a VI layer, and the method comprises the following steps: introducing a virtual machine vertical dynamic increase and decrease allocation technology to realize quick expansion and contraction of a network element virtual machine; multiplexing a virtual machine in a recycle bin to realize reuse of abandoned virtual machine resources; and introducing a virtual machine cloning technology to complete quick expansion of the network element virtual machine. Compared with an existing virtual machine creation mode, the application can realize quick expansion of the NFV network element in the VI layer through combination of multiple strategies. The scheme of the application can reduce the quantity of initialization configuration parameters of network element parameters, and the time required for expansion and contraction of the NFV network element can be optimized from a minute level to a second level by using the scheme of the application.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of cloud computing, and particularly relates to a method, system and device for realizing fast capacity expansion and contraction of NFV network elements in a VI layer and a storage medium. BACKGROUND

[0002] The NFV architecture of ETSI is a virtualized network architecture widely used in the field of telecommunications, and its goal is to decouple the functions of traditional network devices from dedicated hardware and transfer them to general computing, storage and network resources. The three-layer decoupling architecture of 5GC based on NFV technology completes the full decoupling of the general hardware layer, the virtualization infrastructure (VI) layer and the virtualized network element function (VNF) layer, so as to meet the requirements of different manufacturers and network unified architecture cloud deployment, realize the architecture unification and intensive sharing of cloud resource pool, effectively improve the self-controllable force of cloud network, improve the operation efficiency of cloud network, and reduce the construction and operation cost.

[0003] The 5G core network realized based on the three-layer decoupling framework of ETSI can very conveniently and efficiently dynamically adjust the capacity of network elements according to network requirements, and support dynamic capacity expansion and contraction of network elements. However, the existing network element capacity expansion and contraction scheme mainly relies on the VIM module in the MANO component to realize capacity expansion and contraction by adding / deleting network element virtual machines. Since the time required for creating / deleting network element virtual machines is relatively long, usually in minutes, the efficiency of capacity expansion and contraction of network elements is relatively low. Therefore, it is very necessary to develop a method for realizing fast capacity expansion and contraction of network elements. SUMMARY

[0004] The purpose of the present application is to provide a method, system, device and storage medium for realizing fast capacity expansion and contraction of NFV network elements in a VI layer, which realizes fast capacity expansion and contraction of NFV network elements in the VI layer by combining various technologies such as vertical capacity expansion and contraction virtual machines, recycle bin recovery virtual machines, cloning virtual machines and newly created virtual machines.

[0005] To achieve the above purpose, the technical solution provided by the present application is:

[0006] The first aspect of the present application provides a method for realizing fast capacity expansion and contraction of NFV network elements in a VI layer, comprising the following steps:

[0007] The virtual machine vertical dynamic increase / decrease technology is introduced to realize fast capacity expansion and contraction of network element virtual machines;

[0008] The virtual machines in the recycle bin are reused to realize the reuse of abandoned virtual machine resources;

[0009] The virtual machine cloning technology is introduced to complete the fast capacity expansion of network element virtual machines.

[0010] To optimize the above technical solution, the specific measures taken also include:

[0011] The vertical dynamic increase and decrease technology of the introduced virtual machine is used to realize the fast expansion and contraction of the network element virtual machine, including vertical expansion of the virtual machine configuration, specifically:

[0012] The POST / servers / {server_id} / action interface of the VIM is used, and the body is specified as {"live_resize":{"vcpus":"<CPU increase value>","rams":"<RAM increase value>"}}, the physical resources of the network element virtual machine are vertically increased according to the predetermined increase value, and the physical resources include CPU and memory.

[0013] Further, after the VIM component receives the network element virtual machine expansion message, the monitored CPU or memory physical resources of the physical machine where the network element virtual machine is located are compared with the horizontal expansion configuration requirements; if the physical resources are sufficient, the vertical dynamic increase and decrease technology of the introduced virtual machine is used to realize the fast expansion and contraction of the network element virtual machine; if the physical resources are not sufficient, the virtual machines in the recycle bin are reused to realize the reuse of the abandoned virtual machine resources.

[0014] The virtual machines in the recycle bin are reused to realize the reuse of the abandoned virtual machine resources, specifically:

[0015] The soft-delete method of the OpenStack community is used to delete the virtual machine, the recycle bin saves the deleted virtual machine, in the KVM / QEMU virtualization platform, the state corresponding to the deleted virtual machine is shutdown, and the virtual machine in the recycle bin only occupies storage resources, and the CPU and memory physical resources are released;

[0016] The VIM component matches the virtual machine in the recycle bin according to the network element type, version number and other information, uses the GET / servers / detail?recycled=True&app_type=<network element type>&app_version=<network element version> interface, if the available virtual machine is matched, the virtual machine in the recycle bin is reused; since the virtual machine in the recycle bin is in the shutdown state, it can only be restored to the physical machine where it is located to run, therefore, it is necessary to judge whether the corresponding CPU or memory physical resources of the physical machine are sufficient, if the physical resources are sufficient, the virtual machine recovery interface POST / servers / {server_id} / action of the VIM is used, and the body parameter is specified as {"restore":null} to restore the virtual machine in the recycle bin.

[0017] Further, if no virtual machine meeting the requirements is matched in the recycle bin, or the physical resources of the physical machine where the matched virtual machine is located are not sufficient, or after some virtual machines in the recycle bin are restored, the expansion and contraction configuration requirements cannot be met, the introduced virtual machine cloning technology is used to complete the fast expansion and contraction of the network element virtual machine.

[0018] The introduced virtual machine cloning technology completes the rapid expansion of the network element virtual machine, specifically:

[0019] The VIM component completes the expansion of the existing network element virtual machine through the virtual machine cloning interface POST / servers interface, and specifies the body as {"clone":{"name":"<vm_new>", "clone_type":"link_clone", "max_count":"<virtual machine quantity>", <other related cloning parameters specified according to the business>}}.

[0020] Further, if the cloning of part of the virtual machine fails, the expansion of the network element capacity is realized through the newly created virtual machine.

[0021] The introduced virtual machine vertical dynamic increase and decrease technology realizes the rapid expansion and contraction of the network element virtual machine, including vertical contraction virtual machine configuration and horizontal contraction virtual machine configuration, specifically:

[0022] After the VIM component receives the network element virtual machine contraction message, it will first determine whether the current virtual machine configuration is the minimum configuration. If it is not the minimum configuration, the CPU or memory configuration of the virtual machine is dynamically reduced through the virtual machine dynamic expansion and contraction interface of the VIM. The related interface is POST / servers / {server_id} / action interface, and the body is specified as {"live_resize":{"vcpus":"<CPU reduction value>", "rams":"<RAM reduction value>"}}, and the CPU or memory resources of the network element virtual machine are vertically reduced according to the predetermined reduction value, thereby completing the contraction of the network element capacity.

[0023] If it is the minimum configuration, the network element virtual machine is directly deleted to the recycle bin through the virtual machine deletion interface DELETE / servers / {server_id} of the VIM, and the body is specified as {"recycled":true}, thereby realizing the contraction of the network element virtual machine.

[0024] The second aspect of the present application provides a system for realizing the rapid expansion and contraction of the NFV network element in the VI layer, comprising:

[0025] A vertical expansion module is used to introduce virtual machine vertical dynamic increase and decrease technology to realize the rapid expansion and contraction of the network element virtual machine.

[0026] A recycle bin reuse module is used to reuse the virtual machine in the recycle bin, thereby realizing the reuse of the abandoned virtual machine resources.

[0027] A cloned virtual machine module is used to introduce virtual machine cloning technology to complete the rapid expansion of the network element virtual machine.

[0028] The third aspect of the present application provides an electronic device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, when the processor executes the computer program, the method for realizing fast expansion and contraction of NFV network element in VI layer according to the first aspect of the present application is realized.

[0029] The fourth aspect of the present application provides a computer readable storage medium, which stores a computer program, the computer program enables a computer to execute the method for realizing fast expansion and contraction of NFV network element in VI layer according to the first aspect of the present application.

[0030] Compared with the prior art, the present application has the following beneficial effects:

[0031] Compared with the prior art, the present application can realize the fast expansion of NFV network element in VI layer through the combination of multiple strategies.

[0032] The present application realizes the fast expansion and contraction of network element virtual machine through the introduction of vertical dynamic increase and decrease of virtual machine, reuses the virtual machine in the recycle bin to realize the reuse of abandoned virtual machine resources, and introduces the virtual machine cloning technology to realize the fast expansion of network element virtual machine, instead of virtual machine creation technology, thereby improving the expansion efficiency.

[0033] The scheme of the present application can reduce the initialization configuration parameter quantity of network element parameters, and using the scheme of the present application can optimize the time required for the expansion and contraction of NFV network element from minute level to second level. BRIEF DESCRIPTION OF DRAWINGS

[0034] Figure 1 is a system module diagram of an embodiment of the present application.

[0035] Figure 2 is an NFV reference architecture diagram of ETSI.

[0036] Figure 3 is a flowchart of expanding network element virtual machine in the present application.

[0037] Figure 4 is a flowchart of contracting network element virtual machine in the present application. DETAILED DESCRIPTION

[0038] The above content of the present application will be further described in detail through the form of examples, but this should not be understood as the scope of the above subject matter of the present application being limited to the following examples, and any technology realized based on the above content of the present application belongs to the scope of the present application.

[0039] Some nouns in the present application are explained as follows:

[0040] MANO: Management and Orchestration, management and orchestration system

[0041] NFV: Network Functions Virtualization, network function virtualization

[0042] NFVO: NFV Orchestrator, network function virtualization orchestrator

[0043] VNF: Virtualised Network Function, virtual network function

[0044] VNFM: VNF Manager, virtual network function management

[0045] VI: Virtualized Infrastructure, virtual infrastructure

[0046] VIM: Virtualized Infrastructure Manager, virtual infrastructure management

[0047] ETSI: European Telecommunications Standards Institute

[0048] The present application provides a method for realizing fast expansion and contraction of NFV network elements in VI layer, comprising the following steps:

[0049] The vertical dynamic increase and decrease of virtual machine allocation technology is introduced to realize the fast expansion and contraction of network element virtual machines;

[0050] The virtual machines in the recycle bin are multiplexed to realize the reuse of abandoned virtual machine resources;

[0051] The virtual machine cloning technology is introduced to complete the fast expansion of network element virtual machines.

[0052] The present application will be further described in detail in combination with specific embodiments, as shown in the following schemes: Figures 1-4

[0053] (I) Expansion scheme of NFV network element

[0054] ​The monitoring alarm module is interconnected with the VIM component through an Or-Vi interface. The Or-Vi interface supports RESTful, the message format adopts a JSON format, and the encoding adopts a UTF-8 format. The monitoring alarm module periodically acquires resource real-time usage rate information of a network element virtual machine through a POST / v2 / monitor / realtimePerf interface, including CPU usage rate (vm.cpu.usage) and memory usage rate (vm.memory.usage). At the same time, the monitoring alarm module receives a resource usage rate upper limit value index issued by the resource arrangement module. After periodically collecting the resource real-time usage rate information of the network element virtual machine each time, the monitoring alarm module compares the information with the resource usage rate upper limit value. Once the CPU or memory usage rate exceeds the upper limit value, an alarm is triggered, and the alarm information is sent to the resource arrangement module through a message queue mode.

[0055] The VIM component is mainly used for managing resources in a virtualized infrastructure (NFVI). The NFVI includes computing, storage, and network resources. The monitoring module acquires monitoring data, such as CPU and memory usage rate data, through an API interface provided by the VIM. The VIM also provides virtual machine management interfaces, such as virtual machine creation, deletion, recovery, expansion, contraction, and cloning, through a RESTful API.

[0056] The resource arrangement module is mainly used for overall arrangement management of NFV network element virtual machines. The arrangement module acquires alarm messages sent by the monitoring alarm module through a message queue mode and completes monitoring and management of the network element virtual machines through the monitoring alarm module and the resource management module. First, the arrangement module receives a resource usage rate upper limit value, i.e., CPU usage rate and memory usage rate upper limit values (threshold_upper_cpu and threshold_upper_ram), issued by an OSS / BSS system. Second, the arrangement module defines corresponding expansion configurations (including vertical expansion configurations and horizontal expansion configurations) according to different network element requirements. Finally, the arrangement module issues the resource usage rate upper limit value to the monitoring alarm module. After receiving the resource alarm notification, the arrangement module sends alarm information of an expanded network element virtual machine and corresponding expansion configurations of the network element to the resource management module through a message queue mode.

[0057] The resource management module, the monitoring alarm module, and the resource management module are designed and implemented in a MANO system. MANO (Management and Orchestration) is a management and arrangement system for network function virtualization, which is used for managing and arranging network function virtualization resources and services. The main function of the MANO system is to realize automatic, elastic, and flexible network service delivery, thereby improving the efficiency and service quality of network operators.

[0058] The capacity expansion configuration of the network element virtual machine includes vertical capacity expansion configuration and horizontal capacity expansion configuration. The vertical capacity expansion means that the number of virtual machines is not increased, and only the configuration of the virtual machine is increased, such as increasing the number of CPU cores or increasing the memory value of the virtual machine; the horizontal capacity expansion means that the configuration of the virtual machine is not modified, and only the number of virtual machines is increased.

[0059] Let R0 be the resource usage rate when the service is idle, R max be the upper limit value of resource usage (threshold_upper_cpu or threshold_upper_ram), r1 be the difference between the current resource usage rate and R max , r2 be the difference between the resource usage after capacity expansion and R max , N0 be the default configuration of the resource, N c be the current configuration of the resource (the number of CPU cores or the size of memory / G), n V+ be the expected vertical configuration value, n H+ be the expected horizontal configuration value (that is, the number of newly added virtual machines), and G be the service load. The configuration value calculation methods of the two capacity expansion modes are as follows:

[0060] (1) For the vertical capacity expansion virtual machine mode, the configuration value is calculated as follows:

[0061] ① G = N C × (R max -R0+r1);

[0062] ② G = (N C +n V+ ) × (R max -R0-r2)

[0063] The above ① and ② both use the configuration of the resource × the usage rate of the resource to represent the load of the service, (N C +n V+ ) represents the configuration of the resource after vertical configuration, and in combination with the above ① and ②, it can be obtained that: From the result, it can be known that the configuration value of the resource is proportional to the current configuration, the higher the excess usage rate of the resource is, and the lower the reduction degree of the resource is, the greater the configuration value of the resource is.

[0064] In actual operation, for the CPU resource, the minimum value of the configuration is 1 core, and for the memory resource, the minimum value of the configuration can be determined according to the service, and it is recommended to be 1 G, therefore, the actual virtual machine configuration value is

[0065] (2) For the horizontal capacity expansion virtual machine mode, the configuration value is calculated as follows:

[0066] ① G = N C × (Rmax - (R0+ r1);

[0067] G = (N C + n H+ × N0) × (R max - (R0+ r2)

[0068] Both of the above ① and ② use the configuration of resources x the usage rate of resources to represent the load of the service, (N C + n H + × N0) represents the configuration of resources after horizontal expansion, that is, the total configuration of multiple virtual machines, in combination with the above ① and ②, it can be obtained that: From the result, it can be known that the expansion value of resources is proportional to the current configuration and inversely proportional to the default configuration of resources, the higher the excess usage rate of resources and the lower the reduction degree of resources, the greater the expansion value of resources, that is, the more virtual machines need to be added.

[0069] In actual operation, for a virtual machine, the minimum value of expansion is 1 virtual machine, so the actual number of virtual machines to be added is

[0070] In some embodiments, the resource management module is interconnected with the VIM component through the Or-Vi interface, which is mainly used for the life cycle management of the virtual machine of the network element. After receiving the message of expanding the virtual machine of the network element and the corresponding expansion configuration of the network element, the resource management module will expand the virtual machine of the network element by using multiple strategies, so as to realize the rapid expansion of the virtual machine of the network element, and the related strategies are as follows:

[0071] 1. Vertical expansion of virtual machine configuration

[0072] After the VIM component receives the expansion message of the virtual machine of the network element, it will first compare the monitored CPU or memory resources of the physical machine where the virtual machine of the network element is located with the configuration requirements of horizontal expansion.

[0073] If the physical resources are sufficient, the POST / servers / {server_id} / action interface of the VIM is used, and the body is specified as {"live_resize":{"vcpus":"<CPU expansion value>","rams":"<RAM expansion value>"}}. According to the predetermined expansion value, the CPU or memory resources of the virtual machine of the network element are vertically expanded. This scheme does not need to close the original virtual machine, does not need to create a new virtual machine, has the fastest expansion speed of the virtual machine of the network element, does not preoccupy any resources before expansion, and can complete the expansion of the capacity of the network element without initializing the configuration of the parameters of the network element.

[0074] If the physical resources are not sufficient, subsequent operations are performed.

[0075] 2. Reuse of virtual machines in the recycle bin

[0076] The virtual machine recycle bin is not a function supported by the OpenStack community natively, and the VIM function in this patent enhances the native function. The recycle bin is used to save the virtual machines that have been deleted, and the soft-delete method of the OpenStack community is used to delete the virtual machines. In the platform using KVM / QEMU virtualization, the state of the deleted virtual machine is shutdown, so the virtual machine in the recycle bin only occupies storage resources, and the CPU and memory resources are released.

[0077] The VIM component matches the virtual machines in the recycle bin according to the information such as the type of network element and the version number, and uses the interface GET / servers / detail?recycled=True&app_type=<type of network element>&app_version=<version of network element> (&other filtering conditions). If a virtual machine is matched, the virtual machine in the recycle bin is reused. However, since the virtual machine in the recycle bin is in the shutdown state, it can only be restored to the physical machine where it is located, so it is necessary to determine whether the CPU or memory resources of the physical machine where it is located are sufficient. If the resources are sufficient, the virtual machine in the recycle bin can be restored through the virtual machine recovery interface POST / servers / {server_id} / action of the VIM and by specifying the body parameter {"restore": null}. This scheme does not need to create a new virtual machine, but only needs to start the existing virtual machine in the recycle bin, so the expansion of the virtual machine of the network element is faster. The virtual machine in the recycle bin before expansion only occupies the corresponding storage resources but does not occupy the CPU and memory resources, and only a small number of specified parameters of the network element need to be initialized to complete the expansion of the capacity of the network element.

[0078] If no virtual machine that meets the requirements is matched in the recycle bin, or the resources of the physical machine where the matched virtual machine is located are not sufficient, or after some virtual machines in the recycle bin are restored, the requirements of the expansion configuration cannot be met, subsequent operations are performed.

[0079] 3. Clone the virtual machine

[0080] Virtual machine cloning is not a function natively supported by the OpenStack community, and the VIM functions in this patent all enhance the native functions. Virtual machine cloning technology can quickly create a copy that is identical to an existing virtual machine, including the operating system, applications, and data. Virtual machine cloning can be divided into two main types: (1) Full clone: Full clone creates a complete copy independent of the original virtual machine, including the configuration, operating system, applications, and data of the virtual machine. This type of cloning occupies a larger storage space because it copies all the data, but allows the creation of independent virtual machine instances that do not affect the operation of the original virtual machine. (2) Linked clone: Linked clone is a more efficient cloning method that creates a snapshot of a virtual machine and shares the storage content of the original virtual machine. The cloned virtual machine shares the same base image as the original virtual machine and only contains the differences of the virtual machine, reducing storage requirements.

[0081] The VIM component completes the expansion of the existing network element virtual machine by using the virtual machine cloning interface POST / servers interface and specifying the body as {"clone":{"name":"<vm_new>", "clone_type":"link_clone","max_count":"<number of virtual machines>", <other related cloning parameters specified according to the business>}}. It is recommended to use the linked clone method to clone the virtual machine, which is more efficient and faster. This solution uses the cloned virtual machine method to add new virtual machines, which is faster to expand the network element virtual machine. No resources are preoccupied before expansion, and only a small number of network element parameters need to be initialized to complete the expansion of the network element capacity.

[0082] If the cloning of some virtual machines fails, subsequent operations are performed.

[0083] 4. New virtual machine

[0084] The VIM component completes the expansion of the existing network element virtual machine by using the virtual machine creation interface POST / servers / {server_id} / action interface and specifying the body as {"server":{"name":"<vm_new>", "imageRef":"<virtual machine image ID>", "flavorRef":"<virtual machine configuration>", "max_count":"<number of virtual machines>", <other related cloning parameters specified according to the business>}}. This solution uses the new virtual machine method to add new virtual machines, which is slower to expand the network element virtual machine. No resources are preoccupied before expansion, and the full amount of network element parameters need to be initialized to complete the expansion of the network element capacity.

[0085] The following is a comparison of the four ways to expand the network element virtual machine:

[0086] Serial number Mode Creation speed of virtual machine Pre-occupied resource condition Initialization amount of network element parameter 1 Vertical expansion of virtual machine Fastest Pre-occupy no resource No initialization 2 Restore virtual machine by recycle bin Faster Pre-occupy only storage resource Little parameter initialization 3 Clone virtual machine Faster Pre-occupy no resource Little parameter initialization 4 New virtual machine Slowest Pre-occupy no resource Full parameter initialization

[0087] (II) Scheme of scaling down NFV network element

[0088] The monitoring alarm module receives the resource usage lower limit value index issued by the resource arrangement module. After periodically collecting the real-time resource usage information of the network element virtual machine each time, the monitoring alarm module compares the information with the resource usage lower limit value. Once the CPU or memory usage is lower than the lower limit value, an alarm is triggered. The alarm information is sent to the resource arrangement module through the message queue mode.

[0089] The arrangement module receives the resource usage lower limit value, i.e., the CPU usage lower limit value and the memory usage lower limit value (threshold_lower_cpu and threshold_lower_ram), issued by the OSS / BSS system. Secondly, the arrangement module defines the corresponding scaling down configuration (including vertical scaling down configuration and horizontal scaling down configuration) according to different network element requirements. Finally, the arrangement module issues the resource usage lower limit value to the monitoring alarm module. After receiving the resource alarm notification, the arrangement module sends the alarm information of the scaling up network element virtual machine and the corresponding scaling up configuration of the network element to the resource management module through the message queue mode.

[0090] In order to calculate the scaling down configuration of the virtual machine, as above, let R0 be the resource usage when the service is idle, R min be the resource usage upper limit value (threshold_lower_cpu or threshold_lower_ram), r3 be the difference between the current resource usage and R min , r4 be the difference between the resource usage after scaling up and R min , N0 be the default configuration of the resource, N C be the current configuration of the resource (the number of CPU cores or the size of memory / G), n V- be the expected vertical reduction value, n H- be the expected horizontal reduction value, and G be the service load. The increment values of the two scaling up modes are calculated as follows:

[0091] (1) For the vertical scaling down virtual machine mode, the reduction value is calculated as follows:

[0092] ① G = N C × (R min -R0-r3);

[0093] ② G = (N C -n V- )×(R min -R0+r4)

[0094] In combination with the above ① and ②, the following can be obtained: In actual operation, the minimum value of the reduction for the CPU resource is 1 core, and the minimum value of the reduction for the memory resource can be determined according to the service, and is recommended to be 1G. In addition, in order not to affect the service of the virtual machine, the configuration of the virtual machine after reduction cannot be lower than N0, and therefore, the actual virtual machine reduction value is

[0095] (2) For the horizontal scaling of the virtual machine, since the loads of multiple virtual machines running the same service can be unbalanced, and the scaling has a greater impact on the service, the strategy of scaling 1 virtual machine at a time is adopted to complete the scaling.

[0096] In some embodiments, after the resource management module receives the message of scaling the virtual machine of the network element and the scaling configuration corresponding to the network element, the virtual machine of the network element is scaled by using multiple strategies, and the related strategies are as follows:

[0097] 1. Vertical scaling of the virtual machine configuration

[0098] After the VIM component receives the scaling message of the virtual machine of the network element, it will first determine whether the current configuration of the virtual machine is the minimum configuration. If it is not the minimum configuration, the configuration of the CPU or the memory of the virtual machine is dynamically reduced through the virtual machine dynamic expansion and scaling interface of the VIM. The related interface is the POST / servers / {server_id} / action interface, and the body is specified as {"live_resize":{"vcpus":"<CPU reduction value>","rams":"<RAM reduction value>"}}. The CPU or the memory resource of the virtual machine of the network element is vertically reduced according to the predetermined reduction value, so as to complete the scaling of the network element capability.

[0099] 2. Horizontal scaling of the virtual machine configuration

[0100] If it is the minimum configuration, the virtual machine of the network element is directly deleted to the recycle bin through the virtual machine deletion interface DELETE / servers / {server_id} of the VIM, and the body is specified as {"recycled":true}, so as to realize the scaling of the virtual machine of the network element.

[0101] The application also provides a system for realizing the rapid expansion and scaling of the NFV network element in the VI layer, which comprises:

[0102] A vertical scaling module is used to introduce the vertical dynamic increase and decrease of the virtual machine to realize the rapid expansion and scaling of the virtual machine of the network element.

[0103] A recycle bin reuse module is used to reuse the virtual machine in the recycle bin to realize the reuse of the abandoned virtual machine resource.

[0104] A cloned virtual machine module is used to introduce the virtual machine cloning technology to complete the rapid expansion of the virtual machine of the network element.

[0105] The application further provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method for realizing fast expansion and contraction of an NFV network element at a VI layer as described above when executing the computer program.

[0106] The application further provides a computer readable storage medium, which stores a computer program, wherein the computer program causes a computer to execute the method for realizing fast expansion and contraction of an NFV network element at a VI layer as described above.

[0107] In the embodiments disclosed in the application, the computer storage medium can be a tangible medium, which can contain or store programs for use by or in connection with an instruction execution system, apparatus or device. The computer storage medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any suitable combination of the above. More specific examples of the computer storage medium can include one or more wire-based electrical connections, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0108] The above description is only the preferred embodiments of the application, and does not limit the application in any form. Any modification, equivalent replacement, improvement, etc. of the above embodiments made by those skilled in the art without departing from the technical solution of the application shall still fall within the protection scope of the application.

Claims

1. A method for quickly scaling up and down NFV network elements at the VI layer, including the following steps: Introduce the technology of dynamically increasing and decreasing the vertical configuration of virtual machines to achieve the quick scaling up and down of network element virtual machines; Reuse the virtual machines in the recycling station to realize the reuse of discarded virtual machine resources; Introduce the virtual machine cloning technology to complete the quick expansion of network element virtual machines; Among them, after the VIM component receives the network element virtual machine expansion message, it compares the monitored CPU or memory physical resources of the physical machine where the network element virtual machine is located with the horizontal expansion configuration requirements; if the physical resources are sufficient, the technology of dynamically increasing and decreasing the vertical configuration of virtual machines is introduced to realize the quick scaling up and down of network element virtual machines; if the physical resources are insufficient, the virtual machines in the recycling station are reused to realize the reuse of discarded virtual machine resources; If no virtual machine that meets the requirements is found in the recycling station, or if a matching virtual machine is found but the physical resources of the physical machine where it is located are insufficient, or if the physical resources are still insufficient to meet the expansion configuration requirements after restoring some virtual machines in the recycling station, the virtual machine cloning technology is introduced to complete the quick expansion of network element virtual machines.

2. The method for rapidly expanding and shrinking NFV network elements at layer VI according to claim 1, characterized in that: The introduction of the technology of dynamically increasing and decreasing the vertical configuration of virtual machines to realize the quick scaling up and down of network element virtual machines includes vertical expansion of virtual machine configuration, specifically: Through the VIM's POST / servers / {server_id} / action interface, and specifying the body as {"live_resize":{"vcpus":"<CPU increment value>","rams":"<RAM increment value>"}}, vertically increment the physical resources of the network element virtual machine according to the predetermined increment value, and the physical resources include CPU and memory.

3. The method for rapidly expanding and shrinking NFV network elements at layer VI according to claim 1, characterized in that: The reuse of the virtual machines in the recycling station to realize the reuse of discarded virtual machine resources is specifically: Use the native soft-delete method of the OpenStack community to delete virtual machines. The recycling station saves the deleted virtual machines. In a platform using KVM / QEMU virtualization, the state of the virtual machine after deletion is shutdown. The virtual machines in the recycling station only occupy storage resources, and the CPU and memory physical resources are released; The VIM component matches the virtual machines in the recycling station according to the network element type and version number information. If available virtual machines are found, it attempts to reuse the virtual machines in the recycling station; since the virtual machines in the recycling station are in the shutdown state and can only be restored to run on the physical machine where they are located, it is necessary to first judge whether the corresponding CPU or memory physical resources of the physical machine where they are located are sufficient. If the physical resources are sufficient, the virtual machines in the recycling station are restored through the VIM's virtual machine restoration interface POST / servers / {server_id} / action, and the body parameter {"restore":null} is specified.

4. The method for rapidly expanding and shrinking NFV network elements at layer VI according to claim 1, characterized in that: The introduction of the virtual machine cloning technology to complete the quick expansion of network element virtual machines is specifically: The VIM component posts to the / servers interface through the virtual machine cloning interface, and specifies the body as {"clone": {"name": "<vm_new>", "clone_type": "link_clone", "max_count": "<number of virtual machines>", <other relevant cloning parameters specified according to the business>}}, to complete the expansion of the existing network element virtual machines.

5. The method for rapidly expanding and shrinking NFV network elements at layer VI according to claim 1, characterized in that: The introduction of the virtual machine vertical dynamic scaling technology realizes the rapid scaling of network element virtual machines, including vertical scaling down of virtual machine configurations and horizontal scaling down of virtual machine configurations, specifically as follows: After the VIM component receives the network element virtual machine scaling down message, it will first determine whether the current virtual machine configuration is the lowest configuration. If it is not the lowest configuration, it will dynamically reduce the CPU or memory configuration of the virtual machine through the VIM virtual machine dynamic scaling interface. The relevant interface is the POST / servers / {server_id} / action interface, and the body is specified as {"live_resize": {"vcpus": "<CPU scaling down value>", "rams": "<RAM scaling down value>"}}, and vertically scale down the CPU or memory resources of the network element virtual machine according to the predetermined scaling down value, so as to complete the scaling down of the network element capabilities; If it is already the lowest configuration, it will directly use the VIM virtual machine deletion interface DELETE / servers / {server_id}, and specify the body as {"recycled": true}, to delete the network element virtual machine into the recycle bin, thus realizing the scaling down of the network element virtual machine.

6. A system for rapidly expanding and shrinking NFV network elements at layer VI, characterized in that, Including: A vertical expansion module, used to introduce the virtual machine vertical dynamic scaling technology to realize the rapid scaling of network element virtual machines; A recycle bin reuse module, used to reuse the virtual machines in the recycle bin to realize the reuse of the abandoned virtual machine resources; A cloned virtual machine module, used to introduce the virtual machine cloning technology to complete the rapid expansion of network element virtual machines; Among them, after the VIM component receives the network element virtual machine expansion message, it will compare the monitored CPU or memory physical resources of the physical machine where the network element virtual machine is located with the horizontal expansion configuration requirements; If the physical resources are sufficient, the rapid scaling of network element virtual machines is realized by introducing the virtual machine vertical dynamic scaling technology; if the physical resources are insufficient, the virtual machines in the recycle bin are reused to realize the reuse of the abandoned virtual machine resources; If no virtual machine that meets the requirements is found in the recycle bin, or if a matching virtual machine is found but the physical resources of the physical machine where it is located are insufficient, or if the physical resources are still insufficient to meet the expansion configuration requirements after restoring some of the virtual machines in the recycle bin, the virtual machine cloning technology is introduced to complete the rapid expansion of network element virtual machines.

7. An electronic device, characterized in that, Including: A memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it realizes the method for realizing the rapid scaling of NFV network elements in the VI layer as described in any one of claims 1-5.

8. A computer-readable storage medium storing a computer program that causes a computer to perform the method for rapidly scaling up and down NFV network elements at layer VI as described in any one of claims 1-5.

Images