WO2017107483A1 - 一种虚拟化网管文件下载负载均衡的方法及网管服务器 - Google Patents

一种虚拟化网管文件下载负载均衡的方法及网管服务器 Download PDF

Info

Publication number
WO2017107483A1
WO2017107483A1 PCT/CN2016/091752 CN2016091752W WO2017107483A1 WO 2017107483 A1 WO2017107483 A1 WO 2017107483A1 CN 2016091752 W CN2016091752 W CN 2016091752W WO 2017107483 A1 WO2017107483 A1 WO 2017107483A1
Authority
WO
WIPO (PCT)
Prior art keywords
network management
management server
file management
file
hardware resources
Prior art date
Application number
PCT/CN2016/091752
Other languages
English (en)
French (fr)
Inventor
李锐
廖俊锋
钟小武
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017107483A1 publication Critical patent/WO2017107483A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Definitions

  • the present application relates to, but is not limited to, the field of wireless base stations, and in particular, to a method for downloading load balancing of virtualized network management files and a network management server.
  • the traditional base station network management functions are generally large and complete, and the number of management base stations is also large.
  • the network management software generally runs on a high-performance server, when multiple base stations request services at the same time, especially long-term and resource-intensive, such as downloading a large number of files at the same time (such as version files), the network management server will be caused.
  • the CPU Central Processing Unit
  • Version management is a very important function of the network management. Version management mainly includes downloading, upgrading, activation, and rollback of the version. Version management is also a very important module in file management.
  • a medium-sized and large-scale city usually deploys thousands of base stations. When the whole network version is upgraded, the base station downloads the version from the version server of the network management system (usually FTP (File Transfer Protocol) protocol).
  • FTP File Transfer Protocol
  • the network management version server reads and writes the disk and forwards the data at an increased rate, causing the network management CPU to go up, generating an alarm and rejecting the normal requests of the remaining base stations.
  • the network management system is generally designed to limit the number of connections downloaded by the base station, and each connection is limited in speed. As a result, the upgrade time of the entire network element base station is very long and the user experience is poor. At the same time, the performance of different hardware servers is different, and the software has a fixed limit on the number of connections, which may cause some servers to be more stable when connected, and some servers have remaining resources.
  • This document provides a method for downloading load balancing of virtualized network management files and a network management server to solve Resolve the problem of low management performance of related technical network management files (including version files).
  • a method for downloading load balancing of a networked network management file comprising:
  • the network management server pre-configures a separate file management virtual machine
  • the network management server monitors the hardware resources of the entire network management server;
  • the network management server detects that the current hardware resources are sufficient, scheduling to create a new file management virtual machine, increasing the speed and number of file downloads;
  • the network management server If the network management server detects that the current hardware resources are scarce, stop starting a new service, migrate the existing connection to another file management virtual machine, and delete the idle file management virtual machine.
  • the independent file management virtual machine pre-configured by the network management server includes one or more virtual machines, and when multiple virtual machines are included, each virtual machine has a different IP address.
  • the network management server monitors hardware resources of the entire network management server, including:
  • the network management server monitors the utilization rate of current hardware resources
  • the monitored current hardware resource utilization meets or exceeds the maximum threshold, it determines that the current hardware resources are scarce.
  • the maximum threshold includes a preset central processing unit CPU operating rate maximum threshold, a maximum memory capacity threshold, a storage maximum threshold, and a current network bandwidth maximum threshold. Any one or several of them.
  • the foregoing method further includes:
  • the network management server After the network management server completes the file management service for the base station, the network management server restores the number of file management virtual machines to the initial number of file management virtual machines.
  • a network management server comprising:
  • File management module set to: run on a separate file management virtual machine
  • the dynamic monitoring module is configured to: monitor the hardware resources of the entire network management server during the process of providing the file management service for the base station by the network management server, and schedule a new file management virtual machine to increase the file download when the current hardware resources are sufficient. Speed and number of connections, and when monitoring current hardware resources is scarce, stop starting new services, migrate existing connections to other file management virtual machines, and delete idle file management virtual machines.
  • the file management module includes one or more virtual machines, and when multiple virtual machines are included, each virtual machine has a different IP address.
  • the dynamic monitoring module is configured to:
  • the monitored current hardware resource utilization meets or exceeds the maximum threshold, it determines that the current hardware resources are scarce.
  • the maximum threshold includes a preset central processing unit CPU operating rate maximum threshold, a memory maximum threshold, a storage maximum threshold, and a current network bandwidth maximum threshold. Any one or several of them.
  • the dynamic monitoring module is further configured to restore the number of file management virtual machines to an initial number of file management virtual machines after the network management server completes the file management service for the base station.
  • a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the above method.
  • the technical solution of the application improves the management performance of the network management file and improves the resource utilization of the network management server.
  • FIG. 1 is a flowchart of a method for downloading load balancing of a virtualized network management file according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a network management server in an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a network management server according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a network management server in an optional embodiment of the present invention.
  • FIG. 5 is a flowchart of implementing file management by a network management server according to an embodiment of the present invention.
  • NFV Network Function Virtualization
  • cloud management unified management of business management
  • Orchestrator business management
  • the next generation of base stations must also meet the virtualization standards, and general-purpose devices such as network management, which are stored in the core equipment room, are required to be virtualized earlier. Therefore, the inventor proposes that the network management itself can run directly on a high-performance general-purpose server, only need to add a layer of virtualization (such as installing virtualization or container technology such as Openstack or Docker), and manage files (including version management).
  • the functions are independently run on different virtual machines, thereby improving the file management capabilities of the network management system and making rational use of hardware resources.
  • This embodiment provides a method for downloading load balancing of a virtualized network management file, which mainly includes the following steps:
  • Step 100 The network management server pre-configures an independent file management virtual machine.
  • the independent file management virtual machine pre-configured by the network management server includes one or more virtual machines, and when multiple virtual machines are included, each virtual machine has a different IP address.
  • the file management involved in this embodiment includes version management.
  • step 200 the network management server monitors the hardware resources of the entire network management server in the process of providing the file management service for the base station. If the network management server monitors that the current hardware resources are sufficient, step 300 is performed, and if the network management server detects that the current hardware resources are insufficient, step 400 is performed. ;
  • the network management server monitors the utilization rate of current hardware resources
  • the monitored current hardware resource utilization meets or exceeds the maximum threshold, it determines that the current hardware resources are scarce.
  • the maximum threshold includes one or more of a preset central processing unit CPU operating rate maximum threshold, a maximum memory capacity threshold, a maximum storage capacity threshold, and a current network bandwidth maximum threshold. .
  • Step 300 scheduling to create a new file management virtual machine, increasing the speed of file downloading and the number of connections, and ending the process;
  • step 400 the startup of the new service is stopped, the existing connection is migrated to another file management virtual machine, and the idle file management virtual machine is deleted, and the process ends.
  • the number of file management virtual machines can be restored to the initial number of file management virtual machines.
  • This embodiment provides a network management server, which mainly splits the core functions of the network management system into multiple independent modules, and separates modules with common management and resource consumption. Modules with high resource consumption can be run independently and deployed in the cloud, and the rest of the modules run on the remaining virtual machines (VM: Virtual Machine). The principle is shown in Figure 2.
  • VM Virtual Machine
  • the network management server mainly includes the following modules:
  • the file management module 11 is configured to run on a separate file management virtual machine
  • the cloud adopts different virtualization technologies, and each file management module runs on a virtual machine.
  • the running environment of the virtual machine may be based on virtualization or container technology such as Openstack and Docker.
  • the NMS is powered on.
  • the default number of VMs is generated based on the previous configuration files or configuration parameters.
  • Each VM runs the default specifications, such as the maximum number of connections for file download.
  • the dynamic monitoring module 12 is configured to: monitor available hardware resources, and if the current hardware resources are sufficient, schedule to create more virtual machines to the module with more resource consumption (ie, the file management module 11), and accelerate the module with higher current load. Processing speed. If the hardware resource utilization has reached the threshold (that is, the hardware resources are scarce), stop starting a new service, or reject the new service request, migrate the existing connection to as few virtual machines as possible, and delete the idle virtual machine. . Wherein, when determining whether the hardware resources are scarce, the hardware resource utilization rate may be determined, wherein the hardware resource utilization may include a CPU. Maximum utilization, maximum memory capacity threshold, maximum network bandwidth threshold, maximum storage threshold, and so on.
  • the dynamic monitoring module 12 restores each virtual machine configuration to a default state.
  • the network management system can also add a load balancing module.
  • the entire system architecture is shown in Figure 4.
  • the dynamic monitoring module 12 monitors the running performance status of the network management system, and the load balancing module dynamically schedules the newly accessed user to access the appropriate virtual machine according to the current resource access situation.
  • the high resource consumption module in the present application includes but is not limited to file management, and the manner in which the remaining resources consume high modules is also within the protection scope of the present application.
  • the application scenario of the present application is not limited to the application of the base station, and the manner of placing the resource high-load request in the cloud is also within the protection scope of the present application.
  • the network management software separates the resource consumption high functions, such as the version management function.
  • the split file management function (such as the version management function) runs on a separate virtual machine, and other functions (such as the network management system) run on other virtual machines.
  • the split file management function can be run on one or more virtual machines, each having a different IP (Internet Protocol) address.
  • IP Internet Protocol
  • IP addresses are 192.168.1.2/24 and 192.168.1.3/24, and the virtual machine IP running by the rest of the network management module is 192.168.1.1/24.
  • File Management The maximum number of connections supported per virtual machine is 96.
  • the network management system sends a version download (such as version update) command to the base station.
  • the base station requests the delivery version from the network management system, and the network management load balancing module allocates an optimal URL to the base station according to the current running status of the file management module on different virtual machines, or creates more file management virtual machines to receive more connections;
  • the load balancing module allocates a lighter file management virtual machine IP, such as 192.168.1.2/24, to the base station according to the current base station operation. Alternatively, the base station can simultaneously return the progress of the file download.
  • a lighter file management virtual machine IP such as 192.168.1.2/24
  • the network management dynamically monitors the performance of the current virtual machine operation (ie, the hardware resource utilization of the entire network management system);
  • step 305 Determine whether the hardware resource utilization reaches the threshold. If yes, go to step 306. Otherwise, schedule to create more file management virtual machines, increase the speed of file download and the number of connections, and return to step 303.
  • the threshold includes the maximum CPU utilization, the maximum memory capacity threshold, and the current maximum network bandwidth threshold.
  • the maximum threshold of hardware resources is 80% of the CPU operating rate.
  • more versions are issued to the base station. If the CPU running rate is higher than 80%, the version is stopped and the connections on the remaining file management VMs are migrated to the 192.168.1.2/24 virtual machine. When the remaining file management VMs are not connected, delete the corresponding ones. Virtual machine.
  • the dynamic monitoring module restores each virtual machine configuration to the default state.
  • the dynamic monitoring module restores the file management virtual machine to the default two, each connection number is 96, and the corresponding IP addresses are 192.168.1.2/24 and 192.168.1.3/24, respectively.
  • the embodiment of the invention further provides a computer readable storage medium, which stores computer executable instructions, and the method for implementing load balancing of the virtualized network management file downloading when the computer executable instructions are executed by the processor.
  • the embodiment of the invention improves the management performance of the network management file and improves the resource utilization of the network management server.

Abstract

本文公布一种虚拟化网管文件下载负载均衡的方法及网管服务器，所述方法包括：网管服务器预先配置独立的文件管理虚拟机；在所述网管服务器为基站提供文件管理服务的过程中，网管服务器监测整个网管服务器的硬件资源；如果所述网管服务器监测到当前硬件资源充足，则调度创建新的文件管理虚拟机，增加文件下载的速度和连接数；如果所述网管服务器监测到当前硬件资源匮乏，则停止启动新的服务，将已存在的连接迁移到其他文件管理虚拟机上，并删除空闲的文件管理虚拟机。

Description

一种虚拟化网管文件下载负载均衡的方法及网管服务器 技术领域
本申请涉及但不限于无线基站领域，尤其是一种虚拟化网管文件下载负载均衡的方法及网管服务器。
背景技术
传统基站网管功能一般大而全，同时管理基站的数目也很多。虽然网管软件一般都运行在高性能的服务器上，但是多个基站同时请求服务时，尤其是持续时间比较长，资源消耗大的，如大量的文件同时下载(如版本文件)，会导致网管服务器CPU(Central Processing Unit：中央处理器)冲高，而拒绝其余基站等合理请求。
版本管理是网管的一个非常重要功能，版本管理主要包括版本的下载、升级、激活、回退等操作，版本管理又属于文件管理中很重要的一个模块。一个中大型城市一般都部署几千个基站，当全网版本升级时，基站会从网管的版本服务器上下载版本(一般采用FTP(File Transfer Protocol：文件传输协议)协议)。当多个基站同时升级版本时，网管版本服务器读写磁盘和转发数据速率加快，导致网管CPU冲高，从而产生告警并拒绝其余基站的正常请求。
为了保护网管功能的正常使用，网管一般设计为限制基站下载的连接数，并且每个连接都限速，这样导致了全网元基站升级时间会非常长，用户体验差。同时，不同硬件服务器的性能是有区别的，而软件对连接数的限制又是固定的，可能会导致一部分服务器在满连接时性能比较吃紧，另外一些服务器还有剩余资源。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供一种虚拟化网管文件下载负载均衡的方法及网管服务器，以解 决相关技术网管文件(包括版本文件)管理性能低的问题。
一种虚拟化网管文件下载负载均衡的方法，该方法包括：
网管服务器预先配置独立的文件管理虚拟机；
在所述网管服务器为基站提供文件管理服务的过程中，网管服务器监测整个网管服务器的硬件资源；
如果所述网管服务器监测到当前硬件资源充足，则调度创建新的文件管理虚拟机，增加文件下载的速度和连接数；
如果所述网管服务器监测到当前硬件资源匮乏，则停止启动新的服务，将已存在的连接迁移到其他文件管理虚拟机上，并删除空闲的文件管理虚拟机。
可选地，上述方法中，所述网管服务器预先配置的独立的文件管理虚拟机包括一个或多个虚拟机，其中，包括多个虚拟机时，每个虚拟机具有不同的IP地址。
可选地，上述方法中，所述网管服务器监测整个网管服务器的硬件资源包括：
所述网管服务器监测当前硬件资源的利用率；
若所监测的当前硬件资源的利用率小于最大门限值，则确定当前硬件资源充足；
若所监测的当前硬件资源的利用率达到或超过最大门限值，则确定当前硬件资源匮乏。
可选地，上述方法中，所述最大门限值包括预设的中央处理单元CPU运行率最大门限值、内存容量最大门限值、存储容量最大门限值和当前网络带宽最大门限值中的任一种或几种。
可选地，上述方法还包括：
所述网管服务器为基站完成文件管理服务后，将文件管理虚拟机的数目恢复至文件管理虚拟机的初始数目。
一种网管服务器，包括：
文件管理模块，设置为：运行在独立的文件管理虚拟机上；
动态监测模块，设置为：在本网管服务器为基站提供文件管理服务的过程中，监测整个网管服务器的硬件资源，在监测到当前硬件资源充足时，调度创建新的文件管理虚拟机，增加文件下载的速度和连接数，以及在监测到当前硬件资源匮乏时，停止启动新的服务，将已存在的连接迁移到其他文件管理虚拟机上，并删除空闲的文件管理虚拟机。
可选地，上述服务器中，所述文件管理模块包括一个或多个虚拟机，其中，包括多个虚拟机时，每个虚拟机具有不同的IP地址。
可选地，上述服务器中，所述动态监测模块设置为：
监测当前硬件资源的利用率；
若所监测的当前硬件资源的利用率小于最大门限值，则确定当前硬件资源充足；
若所监测的当前硬件资源的利用率达到或超过最大门限值，则确定当前硬件资源匮乏。
可选地，上述服务器中，所述最大门限值包括预设的中央处理单元CPU运行率最大门限值、内存容量最大门限值、存储容量最大门限值和当前网络带宽最大门限值中的任一种或几种。
可选地，上述服务器中，所述动态监测模块，还设置为：在本网管服务器为基站完成文件管理服务后，还将文件管理虚拟机的数目恢复至文件管理虚拟机的初始数目。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述方法。
采用本申请技术方案提高了网管文件管理性能，并提高了网管服务器资源利用率。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1是本发明实施例的虚拟化网管文件下载负载均衡的方法的流程图；
图2是本发明实施例中网管服务器的原理示意图；
图3是本发明实施例的网管服务器的组成示意图；
图4是本发明可选实施例中网管服务器的原理图；
图5是本发明实施例中网管服务器实现文件管理的流程图。
本发明的实施方式
下文将结合附图对本发明的实施方式进行说明。需要说明的是，在不冲突的情况下，本申请的实施例和实施例中的特征可以任意相互组合。
实施例1
本申请发明人发现NFV(Network Function Virtualization)架构中提到了硬件虚拟化管理，云管理，业务管理的统一编排(Orchestrator)。而下一代的基站也必须符合虚拟化的标准，类似于网管等存放于核心机房的通用设备更早要求被虚拟化。因此，发明人提出，网管本身可以直接运行在高性能的通用服务器上，只需要在增加一层虚拟化(如安装Openstack或Docker等虚拟化或容器技术)，并将文件管理(包括版本管理)的功能独立运行在不同虚机上，从而提高网管系统的文件管理能力，并合理利用硬件资源。本实施例提供一种虚拟化网管文件下载负载均衡的方法，主要包括如下步骤：
步骤100，网管服务器预先配置独立的文件管理虚拟机；
该步骤中，网管服务器预先配置的独立的文件管理虚拟机包括一个或多个虚拟机，其中，包括多个虚拟机时，每个虚拟机具有不同的IP地址。
另外，本实施例中所涉及的文件管理包括版本管理。
步骤200，网管服务器为基站提供文件管理服务的过程中，网管服务器监测整个网管服务器的硬件资源，如果网管服务器监测到当前硬件资源充足执行步骤300，如果网管服务器监测到当前硬件资源匮乏执行步骤400；
该步骤中，网管服务器监测整个网管服务器的硬件资源的过程如下：
所述网管服务器监测当前硬件资源的利用率；
若所监测的当前硬件资源的利用率小于最大门限值，则确定当前硬件资源充足；
若所监测的当前硬件资源的利用率达到或超过最大门限值，则确定当前硬件资源匮乏。
其中，最大门限值包括预设的中央处理单元CPU运行率最大门限值、内存容量最大门限值、存储容量最大门限值和当前网络带宽最大门限值中的任一种或几种。
步骤300，调度创建新的文件管理虚拟机，增加文件下载的速度和连接数，结束本流程；
步骤400，停止启动新的服务，将已存在的连接迁移到其他文件管理虚拟机上，并删除空闲的文件管理虚拟机，结束本流程。
当系统重新上电，或者网管服务器为基站完成文件管理服务后，可将文件管理虚拟机的数目恢复至文件管理虚拟机的初始数目。
实施例2
本实施例提供一种网管服务器，主要将网管系统的核心功能拆分为多个独立模块，将常用管理和资源消耗较多的模块分离。资源消耗多的模块可以独立运行，并部署在云，其余模块则运行其余虚机(VM：Virtual Machine)上，其原理如图2所示。
如图3所示，该网管服务器主要包括如下模块：
文件管理模块11，设置为：运行在独立的文件管理虚拟机上；
其中，云端采用不同的虚拟化技术，每个文件管理模块运行于虚机上，虚机的运行环境可以是基于Openstack、Docker等虚拟化或容器技术。
网管系统上电，根据之前的配置文件或配置参数生成缺省数目的虚拟机，每个虚拟机运行缺省的规格参数，如文件下载的最大连接数等。
动态监测模块12，设置为：监测可利用的硬件资源，如果当前硬件资源充足，则调度创建更多的虚机给资源消耗多的模块(即文件管理模块11)，加速当前负荷较高模块的处理速度。如果硬件资源利用率已达到门限值(即硬件资源匮乏)，则停止启动新的服务，或拒绝新的服务请求，把已经存在的连接迁移到尽量少的虚机上，并删除空闲的虚机。其中，判断硬件资源是否匮乏时可根据硬件资源利用率来判断，其中硬件资源利用率可以包括CPU 最大利用率、内存容量最大门限值、网络带宽最大门限值、存储容量最大门限值等等。
高资源消耗请求完毕后，动态监测模块12把每个虚机配置恢复为缺省状态。
另外，网管系统还可以新增负载均衡模块，此时整个系统架构如图4所示。动态监测模块12监测网管运行性能状态，负载均衡模块动态根据当前资源接入情况，调度新接入的用户接入合适的虚机。
本申请中高资源消耗模块包括但不仅限于文件管理，其余资源消耗高模块的方式也在本申请的保护范围内。
本申请的应用场景不仅限于基站的应用，其余对资源高负荷请求的方式放置于云端的方式也在本申请的保护范围内。
下面再结合附图说明上述网管服务器实现文件管理的过程，该过程如图5所示，包括如下步骤：
301、网管软件将资源消耗高功能，例如版本管理功能独立拆分出来。
302、拆分出的文件管理功能(例如版本管理功能)运行于独立的虚机上，其余功能(例如网管系统)运行于其它虚机上。
其中，拆分出的文件管理功能可运行于一个或多个虚拟机上，每个虚拟机具有不同的IP(Internet Protocol)地址。
例如，可以缺省配置2个文件管理虚机，IP地址分别为192.168.1.2/24和192.168.1.3/24，网管其余模块运行的虚机IP为192.168.1.1/24。文件管理每个虚机支持的最大连接数为96。
303、网管给基站下发版本下载(如版本更新)命令。基站向网管请求下发版本，网管负载均衡模块根据当前不同虚机上文件管理模块运行的状况分配最优的URL给基站，或创建更多的文件管理虚机接收更多连接；
假设。负载均衡模块根据当前基站运行情况，分配负荷较轻的文件管理虚机IP，如192.168.1.2/24返回给基站。可选地，基站可以同时返回文件下载的进度。
304、网管动态监测当前虚机运行的性能(即整个网管系统的硬件资源利用率)；
305、判断硬件资源利用率是否达到阈值，如果是，进入步骤306，否则调度创建更多的文件管理虚拟机，增加文件下载的速度和连接数，返回步骤303。
其中，阈值包括CPU最大利用率、内存容量最大门限值、当前网络带宽最大门限值等。
假设，硬件资源的最大门限值为CPU运行率80％，则CPU运行率低于60％时，可以创建2个文件管理虚拟机，对应IP为192.168.1.4/24和192.168.1.5/24，同时下发更多的版本给基站。如果监测到CPU运行率高于80％，则开始停止下发版本，并将其余文件管理虚机上的连接迁移到192.168.1.2/24的虚机上，当其余文件管理虚机没有连接后，删除对应的虚拟机。
306、停止启动新的服务，或拒绝新的基站文件下载请求，将已存在的连接迁移到尽量少的虚机上，并删除空闲的文件管理虚拟机。
307、文件更新下载完毕，动态监测模块把每个虚机配置恢复为缺省状态。
例如，动态监测模块将文件管理虚机恢复为缺省的2个，每个连接数为96，对应IP地址分别为192.168.1.2/24和192.168.1.3/24。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述虚拟化网管文件下载负载均衡的方法。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的模块/单元可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本申请不限制于任何特定形式的硬件和软件的结合。
以上所述，仅为本发明的可选实例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
工业实用性
本发明实施例提高了网管文件管理性能，并提高了网管服务器资源利用率。

Claims (10)

  1. 一种虚拟化网管文件下载负载均衡的方法，该方法包括：
    网管服务器预先配置独立的文件管理虚拟机；
    在所述网管服务器为基站提供文件管理服务的过程中，网管服务器监测整个网管服务器的硬件资源；
    如果所述网管服务器监测到当前硬件资源充足，则调度创建新的文件管理虚拟机，增加文件下载的速度和连接数；
    如果所述网管服务器监测到当前硬件资源匮乏，则停止启动新的服务，将已存在的连接迁移到其他文件管理虚拟机上，并删除空闲的文件管理虚拟机。
  2. 如权利要求1所述的方法，其中，
    所述网管服务器预先配置的独立的文件管理虚拟机包括一个或多个虚拟机，其中，包括多个虚拟机时，每个虚拟机具有不同的IP地址。
  3. 如权利要求1或2所述的方法，其中，所述网管服务器监测整个网管服务器的硬件资源包括：
    所述网管服务器监测当前硬件资源的利用率；
    若所监测的当前硬件资源的利用率小于最大门限值，则确定当前硬件资源充足；
    若所监测的当前硬件资源的利用率达到或超过最大门限值，则确定当前硬件资源匮乏。
  4. 如权利要求3所述的方法，其中，
    所述最大门限值包括预设的中央处理单元CPU运行率最大门限值、内存容量最大门限值、存储容量最大门限值和当前网络带宽最大门限值中的任一种或几种。
  5. 如权利要求3所述的方法，该方法还包括：
    所述网管服务器为基站完成文件管理服务后，将文件管理虚拟机的数目恢复至文件管理虚拟机的初始数目。
  6. 一种网管服务器，包括：
    文件管理模块，设置为：运行在独立的文件管理虚拟机上；
    动态监测模块，设置为：在本网管服务器为基站提供文件管理服务的过程中，监测整个网管服务器的硬件资源，在监测到当前硬件资源充足时，调度创建新的文件管理虚拟机，增加文件下载的速度和连接数，以及在监测到当前硬件资源匮乏时，停止启动新的服务，将已存在的连接迁移到其他文件管理虚拟机上，并删除空闲的文件管理虚拟机。
  7. 如权利要求6所述的服务器，其中，
    所述文件管理模块包括一个或多个虚拟机，其中，包括多个虚拟机时，每个虚拟机具有不同的IP地址。
  8. 如权利要求6或7所述的服务器，其中，所述动态监测模块设置为：
    监测当前硬件资源的利用率；
    若所监测的当前硬件资源的利用率小于最大门限值，则确定当前硬件资源充足；
    若所监测的当前硬件资源的利用率达到或超过最大门限值，则确定当前硬件资源匮乏。
  9. 如权利要求8所述的服务器，其中，
    所述最大门限值包括预设的中央处理单元CPU运行率最大门限值、内存容量最大门限值、存储容量最大门限值和当前网络带宽最大门限值中的任一种或几种。
  10. 如权利要求8所述的服务器，其中，
    所述动态监测模块，还设置为：在本网管服务器为基站完成文件管理服务后，还将文件管理虚拟机的数目恢复至文件管理虚拟机的初始数目。
PCT/CN2016/091752 2015-12-23 2016-07-26 一种虚拟化网管文件下载负载均衡的方法及网管服务器 WO2017107483A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510979327.2A CN106911741B (zh) 2015-12-23 2015-12-23 一种虚拟化网管文件下载负载均衡的方法及网管服务器
CN201510979327.2 2015-12-23

Publications (1)

Publication Number Publication Date
WO2017107483A1 true WO2017107483A1 (zh) 2017-06-29

Family

ID=59088953

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/091752 WO2017107483A1 (zh) 2015-12-23 2016-07-26 一种虚拟化网管文件下载负载均衡的方法及网管服务器

Country Status (2)

Country Link
CN (1) CN106911741B (zh)
WO (1) WO2017107483A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110008005A (zh) * 2019-04-11 2019-07-12 中国南方电网有限责任公司 基于云平台的电网通信资源虚拟机迁移系统及方法
CN112000441A (zh) * 2020-08-24 2020-11-27 浪潮云信息技术股份公司 一种基于kubernetes声明式编排管理虚机生命周期的方法

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112055036A (zh) * 2019-06-05 2020-12-08 阿里巴巴集团控股有限公司 数据下载方法、装置、设备、系统及可读存储介质
CN112565319A (zh) * 2019-09-25 2021-03-26 中兴通讯股份有限公司 传输控制方法、网管服务器、基站及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030005080A1 (en) * 2001-06-28 2003-01-02 Watkins James S. Systems and methods for accessing data
CN102571959A (zh) * 2012-01-11 2012-07-11 北京奇虎科技有限公司 一种数据下载系统及方法
CN102624558A (zh) * 2012-03-09 2012-08-01 浪潮通信信息系统有限公司 一种基于云计算技术解决通信行业网管系统性能瓶颈的方法
CN103002044A (zh) * 2012-12-18 2013-03-27 武汉大学 一种提高多平台智能终端处理能力的方法
CN104702702A (zh) * 2012-01-11 2015-06-10 北京奇虎科技有限公司 一种数据下载系统及方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101414277B (zh) * 2008-11-06 2010-06-09 清华大学 一种基于虚拟机的按需增量恢复容灾系统及方法
CN102270157A (zh) * 2011-07-25 2011-12-07 浪潮(北京)电子信息产业有限公司 一种实现服务器资源分配的系统及方法
CN104468407B (zh) * 2013-09-16 2018-04-06 中国电信股份有限公司 实现业务平台资源弹性分配的方法与装置
CN104657215A (zh) * 2013-11-19 2015-05-27 南京鼎盟科技有限公司 云计算中虚拟化节能系统
WO2015132753A1 (en) * 2014-03-07 2015-09-11 Eco4Cloud S.R.L. Method for memory management in virtual machines, and corresponding system and computer program product
CN104615480A (zh) * 2015-02-04 2015-05-13 上海交通大学 基于numa高性能网络处理器负载的虚拟处理器调度方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030005080A1 (en) * 2001-06-28 2003-01-02 Watkins James S. Systems and methods for accessing data
CN102571959A (zh) * 2012-01-11 2012-07-11 北京奇虎科技有限公司 一种数据下载系统及方法
CN104702702A (zh) * 2012-01-11 2015-06-10 北京奇虎科技有限公司 一种数据下载系统及方法
CN102624558A (zh) * 2012-03-09 2012-08-01 浪潮通信信息系统有限公司 一种基于云计算技术解决通信行业网管系统性能瓶颈的方法
CN103002044A (zh) * 2012-12-18 2013-03-27 武汉大学 一种提高多平台智能终端处理能力的方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110008005A (zh) * 2019-04-11 2019-07-12 中国南方电网有限责任公司 基于云平台的电网通信资源虚拟机迁移系统及方法
CN110008005B (zh) * 2019-04-11 2023-07-18 中国南方电网有限责任公司 基于云平台的电网通信资源虚拟机迁移系统及方法
CN112000441A (zh) * 2020-08-24 2020-11-27 浪潮云信息技术股份公司 一种基于kubernetes声明式编排管理虚机生命周期的方法

Also Published As

Publication number Publication date
CN106911741B (zh) 2020-10-16
CN106911741A (zh) 2017-06-30

Similar Documents

Publication Publication Date Title
US9819538B2 (en) Maintaining resource availability during maintenance operations
US10275270B2 (en) Method and apparatus to scale application deployments in cloud computing environments using virtual machine pools
EP3170071B1 (en) Self-extending cloud
EP3365780B1 (en) Multi-tenant multi-session catalogs with machine-level isolation
US10628273B2 (en) Node system, server apparatus, scaling control method, and program
CN106471791B (zh) 用于基于移动设备的集群计算架构的方法和装置
US9176786B2 (en) Dynamic and automatic colocation and combining of service providers and service clients in a grid of resources for performing a data backup function
US9268590B2 (en) Provisioning a cluster of distributed computing platform based on placement strategy
US8806015B2 (en) Workload-aware placement in private heterogeneous clouds
US9231892B2 (en) Distributed virtual switch configuration and state management
US10671377B2 (en) Method to deploy new version of executable in node based environments
CN106227582B (zh) 弹性伸缩方法及系统
US20160350157A1 (en) Dynamic thread pool management
RU2653292C2 (ru) Перенос служб через границы кластеров
JP6840099B2 (ja) サービス提供システム、資源割り当て方法、及び資源割り当てプログラム
CN111796908B (zh) 一种资源自动弹性伸缩的系统、方法及云平台
WO2017107483A1 (zh) 一种虚拟化网管文件下载负载均衡的方法及网管服务器
JP2013541113A (ja) ステートレスクラウドコンピューティング環境において動作するステートフルアプリケーション
KR20060051932A (ko) 소프트웨어를 실행 동안 업데이트하는 시스템, 방법 및컴퓨터-판독가능 매체
US20140344807A1 (en) Optimized virtual machine migration
US20210255885A1 (en) System and method for multi-cluster storage
CN109960579B (zh) 一种调整业务容器的方法及装置
WO2014029239A1 (zh) 虚拟机放置策略的配置方法及装置
CN113900774B (zh) 云操作系统的虚拟机控制方法、装置以及存储介质
WO2023066246A1 (zh) 云手机安装应用的方法、系统和客户端云手机

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16877295

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16877295

Country of ref document: EP

Kind code of ref document: A1