WO2017181876A1 - 一种设备状态及资源信息监测方法、相关设备及系统 - Google Patents
一种设备状态及资源信息监测方法、相关设备及系统 Download PDFInfo
- Publication number
- WO2017181876A1 WO2017181876A1 PCT/CN2017/080111 CN2017080111W WO2017181876A1 WO 2017181876 A1 WO2017181876 A1 WO 2017181876A1 CN 2017080111 W CN2017080111 W CN 2017080111W WO 2017181876 A1 WO2017181876 A1 WO 2017181876A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- container
- virtual machine
- vnf
- resource
- nfvi
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
-
- 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
-
- 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/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
-
- 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
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/70—Virtual switches
Definitions
- the present invention relates to the field of computer technologies, and in particular, to a device status and resource information monitoring method, related device and system.
- the traditional telecommunication system is composed of various dedicated hardware devices, and different applications use different hardware devices.
- the system becomes more and more complex, which brings many challenges, including the development of new services, the operation and maintenance of the system, and resource utilization.
- the world's 13 major telecom operators jointly released the NFV white paper. It also announced the establishment of NFV ISG at ETSI to develop NFV requirements and technical framework to promote the development of NFV.
- NFV Network Function Virtualization
- COTS Commercial-off-the- Shelf
- each network element used in the telecommunication network can be transformed into a stand-alone application, which can be flexibly deployed on a unified infrastructure platform built by standards-based servers, storage, and switches, and through virtualization technology to the infrastructure.
- the hardware device resources are pooled and virtualized, and the virtual resources are provided to the upper layer application.
- the virtual network function (VNF) is deployed to the virtual machine or the container to implement decoupling between the application and the hardware, so that the virtual resource is enabled.
- each virtual machine or container has its own device status and resource monitoring module. If thousands of virtual machines or containers are deployed on a server, there will be thousands of resource monitoring modules, resulting in resource overhead. Big.
- the embodiment of the invention discloses a device status and resource information monitoring method, a related device and a system, which can remove repeated monitoring and reduce resource monitoring overhead.
- the embodiment of the invention discloses a device status and resource information monitoring method.
- the method includes: the network function virtualization infrastructure NFVI receives a subscription message sent by the virtual network function VNF; wherein the subscription message is used to obtain a deployment VNF of the NFVI monitoring.
- NFVI reports the virtual machine created by the VNF to the VNF through the network function virtualization infrastructure interface according to the subscription message or Device status and resource monitoring information for the container.
- the NFVI can be used to monitor the device status and resource monitoring information of the virtual machine or the container for multiple virtual machines or containers created by deploying the VNF, so that each virtual machine or container has its own device status. And the repeated monitoring caused by the resource monitoring mechanism, thereby reducing the resource monitoring overhead of the network function virtualization system.
- FIG. 1 is a system architecture diagram of a network function virtualization NFV according to an embodiment of the present invention
- FIG. 2 is a schematic flowchart of a device status and resource information monitoring method according to an embodiment of the present invention
- FIG. 3 is a schematic structural diagram of a network function virtualization infrastructure disclosed in an embodiment of the present invention.
- FIG. 4 is a schematic structural diagram of a device status and resource information monitoring system according to an embodiment of the present invention.
- FIG. 5 is another schematic structural diagram of a network function virtualization infrastructure disclosed in an embodiment of the present invention.
- FIG. 1 is an architectural diagram of an NFV system 100 that can be implemented in various network environments, such as a data center network, a carrier network, or a local area network.
- the NFV system 100 includes a network function virtualization management and orchestration system (NFV-MANO) 101, a network function virtualization infrastructure (NFVI) 130, and multiple element management (EM).
- NFV-MANO network function virtualization management and orchestration system
- NFVI network function virtualization infrastructure
- EM multiple element management
- the network function virtualization orchestration and management system 101 includes a network function virtualization orchestrator (NFVO) 102, one or more virtual network function managers (VNF Managers, VNFM) 104, and a virtualization infrastructure manager ( Virtualized Infrastructure Manager, VIM) 106.
- the network function virtualization infrastructure 130 includes a hardware resource layer, a virtualization layer, and a virtual resource layer.
- the hardware resource layer includes computing hardware 112, storage hardware 114, and network hardware 116.
- the virtual resource layer includes virtual computing 110, virtual storage 118, and virtual network. 120.
- Network services, VNF and infrastructure descriptions 126 and operational support system/business support system 124 are further discussed in the ETSI GS NFV 002 V1.1.1 standard.
- the NFV management and orchestration system 101 is used to perform monitoring and management of the virtual network function 108 and the network function virtualization infrastructure 130.
- Network function virtualization orchestrator 102 can implement a network on network function virtualization infrastructure 130 Services (such as L2 and L3VPN services) may also perform resource related requests from one or more virtual network function managers 104, send configuration information to virtual network function manager 104, and collect status information for virtual network functions 108. Additionally, network function virtualization orchestrator 102 can communicate with virtual infrastructure manager 106 to enable resource allocation and/or reservation and to exchange configuration and status information for virtualized hardware resources.
- the virtual network function manager 104 can manage one or more virtual network functions 108.
- the virtual network function manager 104 can perform various management functions such as instantiating, updating, querying, scaling, and/or terminating the virtual network function 108 and the like.
- the virtual infrastructure manager 106 can perform resource management functions such as managing the allocation of infrastructure resources (eg, adding resources to containers) and operational functions (eg, collecting network function virtualization infrastructure failure information).
- the virtual network function manager 104 and the virtual infrastructure manager 106 can communicate with one another for resource allocation and exchange of configuration and status information for virtualized hardware resources.
- the network function virtualization infrastructure 130 includes hardware resources, software resources, or a combination of both to complete the deployment of the virtualized environment.
- the hardware resources and virtualization layers are used to provide virtualized resources, such as virtual machines and other forms of containers, for installing virtual network functions 108.
- Hardware resources include computing hardware 112, storage hardware 114, and network hardware 116.
- Computing hardware 112 may be off-the-shelf hardware and/or user-customized hardware used to provide processing and computing resources.
- Storage hardware 114 may be storage capacity provided within the network or storage capacity resident in storage hardware 114 itself (local storage located within the server). In one possible implementation, computing hardware 112 and storage hardware 114 can be grouped together.
- Network hardware 116 can be a switch, a router, and/or any other network device configured to have switching functionality.
- Network hardware 116 can span multiple domains and can include multiple networks interconnected by one or more transport networks.
- the virtualization layer of network function virtualization infrastructure 130 may abstract hardware resources and decouple virtual network functions 108 from the physical layer to provide virtualized resources to virtual network functions 108.
- the virtual resource layer includes virtual computing 110, virtual storage 118, and virtual network 120.
- Virtual computing 110 and virtual storage 118 may be provided to virtual network functionality 108 in the form of virtual machines and/or other containers.
- one or more virtual network functions 108 can be deployed on a virtual machine.
- the virtualization layer abstract network hardware 116 forms a virtual network 120.
- the virtual network 120 can include a virtual switch (Virtual Switch) for providing connections between virtual machines.
- the transport network in network hardware 116 can be virtualized using a centralized control plane and a separate forwarding plane (eg, software defined network, SDN).
- virtual network function manager 104 can interact with virtual network function 108 and network element management 122 to manage the lifecycle of virtual network function 108 and exchange configuration and status information.
- the virtual network function 108 can be configured to virtualize at least one network function performed by one physical network device.
- the virtual network function 108 can be configured to provide functions of different network elements in an IMS (IP Multimedia Subsystem, IP Multimedia Subsystem, IMS for short) network, such as a P-CSCF (Proxy-Call Session).
- IMS IP Multimedia Subsystem
- IMS IP Multimedia Subsystem
- IMS IP Multimedia Subsystem
- P-CSCF Proxy-Call Session
- the element management 122 is configured to manage one or more virtual network functions 108.
- the virtual network function 108 can be deployed in a container or a virtual machine.
- each virtual machine or container has its own independent device status.
- the resource monitoring module if thousands of virtual machines or containers are deployed on one server, there will be thousands of device status and resource monitoring modules, resulting in excessive resource overhead and waste of resources.
- FIG. 2 is a schematic flowchart of a method for monitoring device status and resource information according to an embodiment of the present invention.
- the method includes the following steps:
- the network function virtualization infrastructure NFVI receives the subscription message sent by the virtual network function VNF.
- the VNF is deployed in a virtual machine or a container.
- the VNF needs to obtain the device status and resource monitoring information of the virtual machine or the container
- the VNF sends a subscription message to the NFVI
- the NFVI receives the subscription message sent by the VNF
- the device status indicates that the device is assigned to the virtual machine or
- the hardware resource of the container is a normal state or a fault state
- the resource monitoring information indicates an operating parameter of a hardware resource allocated to the virtual machine or the container, such as a utilization rate, an idle rate, a packet loss rate, a running time, or a failure time.
- the NFVI reports, according to the subscription message, the device status and resource monitoring information of the virtual machine or the container that deploys the VNF to the VNF through the network function virtualization infrastructure interface.
- the NFVI monitors the device status and resource monitoring information of the virtual machine or container in which the VNF is deployed.
- the NFVI adds a device status and resource monitoring module, device status, and resource monitoring on the Host OS where the physical server allocated on the virtualization layer is located.
- the module is used to monitor the device status and resource monitoring information of the virtual machine or container in which the VNF is deployed.
- multiple VNFs are deployed, multiple VNF virtual machines or containers share a device status and resource monitoring module, and the NFVI monitors the device status. And the resource monitoring information is reported to the VNF through the network function virtualization infrastructure interface.
- the method further includes:
- the NFVI receives a deployment request message sent by the VIM for creating a virtual machine or a container;
- the NFVI creates a virtual machine or a container that deploys the VNF according to the deployment request message;
- the monitoring function of the monitoring module is started in the host operating system Host OS, and the monitoring module is presented in a virtual device manner to the VNF. Virtual machine or container.
- the NFVI adds a device status and a resource monitoring module to the Host OS where the physical server allocated on the virtualization layer is located, and the device status and resource monitoring module is used to detect the device status and resource monitoring information of the virtual machine or the container in which the VNF is deployed.
- the VIM sends a deployment request message to the NFVI, and the deployment request message is used to create a virtual machine or a container for installing the VNF.
- the deployment request message carries a resource monitoring field, and the resource monitoring field is a piece.
- the data of the device indicates the device status and running parameters of the hardware resources allocated to the virtual machine or the container.
- the NFVI creates a virtual machine or container of the VNF according to the deployment request message, and parses the value of the monitoring flag of the resource monitoring field to determine the resource in the NFVI.
- the value of the monitoring flag in the monitoring field is true, for example, when the value of the monitoring flag is 1, it indicates that the device status and the monitoring function of the resource monitoring module are turned on.
- the value of the monitoring flag is 0, it indicates that the device status is turned off.
- the monitoring function of the resource monitoring module, NFVI determines the need to open the device status and resources
- the monitoring function of the device state and the resource monitoring module is enabled in the Host OS where the physical server is located on the virtualization layer, and the device status and resource monitoring module are presented to the virtual machine deploying the VNF as a virtual device.
- a container where the device status and resource monitoring module is a virtual device for the virtual machine or the container, and after the device status and the resource monitoring module are monitored, the device status and resource monitoring module monitors the virtual machine used to deploy the VNF or Device status and resource monitoring information for the container.
- the method further includes:
- the NFVI When the NFVI detects that a virtual machine or a container that deploys the VNF has a preset fault, the NFVI sends the fault information of the preset fault to the virtual network infrastructure manager VIM, according to the VIM. Fault information processing office Preset failure.
- the preset fault may be a fault that cannot be networked, a disk read/write error, or a software failure.
- the fault code corresponding to the preset fault and the fault description information may be Each type of fault corresponds to a fault code.
- the fault description information indicates the faulty application, the operating parameters of the device (CPU usage, disk free space, memory usage, etc.), which will include fault codes and fault description information.
- the information is reported to the VIM.
- the VIM locates the faulty hardware device based on the fault information reported by the NFVI.
- the subscription message is used to obtain device status and resource information of the virtual machine or container that is configured by the NFVI to deploy the VNF; and the device status of the virtual machine or the container includes the virtual machine or the container.
- the device status of the virtual machine or the container includes the virtual machine or the container.
- resource monitoring information of the virtual machine or container includes utilization of a physical processor, physical memory, network card, and disk allocated to the virtual machine or container At least one of the rates.
- the device status indicates that the hardware resource allocated to the virtual machine or the container is a normal state or a fault state
- the hardware resource includes at least one of a physical processor, a physical memory, and a network card machine disk
- the resource monitoring information indicates that the resource is allocated to the virtual machine or the container.
- the operating parameters of the hardware resource for example, the resource monitoring information includes at least one of a physical processor, a physical memory, a network card, and a utilization rate of the disk.
- the resource monitoring field includes a field of a virtual machine or a container device state of an enumerated type, and a field of virtual machine or container resource information of an enumerated type;
- a field of the enumerated type of virtual machine or container device state for monitoring the state of the physical processor, physical memory, network card, and disk allocated to the virtual machine or container; the virtual machine or container resource information of the enumerated type A field that monitors the utilization of physical processors, physical memory, network cards, and disks of a virtual machine or container.
- the NFVI can be used to monitor the device status and resource monitoring information of the virtual machine or the container for multiple virtual machines or containers created by deploying the VNF, so that each virtual machine or container has its own device status. And repeated monitoring caused by the resource monitoring mechanism, thereby reducing the resource monitoring overhead of the network function virtualization system.
- FIG. 3 is a schematic structural diagram of a network function virtualization infrastructure according to an embodiment of the present invention.
- the network function virtualization infrastructure includes a receiving module 301 and a reporting module 302.
- the receiving module 301 is configured to receive a subscription message sent by the virtual network function VNF.
- the VNF is deployed in the virtual machine or the container.
- the VNF needs to obtain the device status and resource monitoring information of the virtual machine or the container
- the VNF sends a subscription message to the NFVI
- the receiving module 301 of the NFVI receives the subscription message sent by the VNF.
- the device status indicates that the hardware resources allocated to the virtual machine or the container are in a normal state or a fault state
- the resource monitoring information indicates the running parameters of the hardware resources allocated to the virtual machine or the container, for example, the running parameters include the utilization rate, the idle rate, and the packet loss rate. , running time or downtime, etc.
- the reporting module 302 is configured to report, according to the subscription message, the device status and resource monitoring information of the virtual machine or the container that deploys the VNF to the VNF through the network function virtualization infrastructure interface.
- the reporting module 302 obtains the device status and resource monitoring information of the virtual machine or the container in which the VNF is deployed. For example, the device status and the resource monitoring module, the device status, and the resource are added to the Host OS where the physical server allocated on the virtualization layer is located.
- the monitoring module monitors the device status and resource monitoring information of the virtual machine or container in which the VNF is deployed, and the reporting module 302 obtains the device status and the resource monitoring information monitored by the resource monitoring module, and reports the information to the VNF.
- the VMs or containers of the multiple VNFs share a device status and resource monitoring module, and the reporting module 302 reports the acquired device status and resource monitoring information to the network function virtualization infrastructure interface. VNF.
- the receiving module is further configured to: before receiving the subscription message sent by the virtual network function VNF, receive a deployment request message sent by the VIM to create a virtual machine or a container;
- the NFVI also includes:
- a creating module configured to create a virtual machine or a container that deploys the VNF according to the deployment request message
- a startup module configured to: when the monitoring flag of the resource monitoring field in the deployment request message is true, start a device state and a monitoring function of the resource monitoring module in the host operating system Host OS;
- the device status and resource monitoring module is configured to monitor device status and resource monitoring information of a virtual machine or a container that deploys the VNF, where the device status and resource monitoring module is presented in a virtual device manner to the VNF. Virtual machine or container.
- the NFVI adds a device status and a resource monitoring module to the Host OS where the physical server allocated on the virtualization layer is located, and the device status and resource monitoring module is used to detect the device status and resource monitoring information of the virtual machine or the container in which the VNF is deployed.
- the VIM sends a deployment request message to the NFVI, and the deployment request message is used to create a virtual machine or a container for installing the VNF.
- the deployment request message carries a resource monitoring field, and the resource monitoring field is a piece.
- the data of the device indicates the device status and running parameters of the hardware resources allocated to the virtual machine or the container.
- the NFVI creation module creates a virtual machine or container of the VNF according to the deployment request message, and starts the module to parse the value of the monitoring flag of the resource monitoring field.
- the value of the monitoring flag in the determined resource monitoring field is true, for example, when the value of the monitoring flag is 1, it indicates that the device status and the monitoring function of the resource monitoring module are turned on, and when the value of the monitoring flag is 0, it indicates Turn off the monitoring function of the device status and resource monitoring module, and the startup module determines the need.
- the monitoring function of the device status and resource monitoring module is enabled in the Host OS where the physical server is located on the virtualization layer, and the device status and resource monitoring module are presented as virtual devices.
- the device status and resource monitoring module is a virtual device for the virtual machine or the container. After the device status and the monitoring function of the resource monitoring module are enabled, the device status and resource monitoring module are used for monitoring. Device status and resource monitoring information of the virtual machine or container where the VNF is deployed.
- the NFVI further includes:
- a sending module configured to: when the NFVI detects that a virtual machine or a container that deploys the VNF has a preset fault, send the fault information of the preset fault to the virtual network infrastructure manager VIM, according to the VIM The fault information processes the preset fault.
- the preset fault may be a fault that cannot be networked, a disk read/write error, or a software failure.
- the fault code corresponding to the preset fault and the fault description information may be Each type of fault corresponds to a fault code.
- the fault description information indicates the faulty application and the running parameters of the device (for example: CPU usage, disk free space, memory usage, etc.), and the sending module will include the fault code and fault.
- the fault information of the description information is reported to the VIM.
- the VIM locates the faulty hardware device according to the fault information reported by the NFVI.
- the subscription message is used to obtain device status and resource information of the virtual machine or container that is deployed by the NFVI to deploy the VNF; device status of the virtual machine or the container At least one of a state of a physical processor, a physical memory, a network card, and a disk allocated to the virtual machine or container; the resource monitoring information of the virtual machine or container includes a physical processor assigned to the virtual machine or container At least one of physical memory, network card, and disk utilization.
- the device status indicates that the hardware resources allocated to the virtual machine or the container are in a normal state or a fault state, and the hardware
- the resource includes at least one of a physical processor, a physical memory, and a network card machine disk;
- the resource monitoring information indicates an operating parameter of a hardware resource allocated to the virtual machine or the container, for example, the resource monitoring information includes a physical processor, a physical memory, a network card, and a disk. At least one of the utilization rates.
- the resource monitoring field includes a field of a virtual machine or a container device state of an enumerated type and a field of virtual machine or container resource information of an enumerated type;
- FIG. 4 is a schematic structural diagram of a device status and resource information monitoring system according to an embodiment of the present invention.
- the device status and resource information monitoring system includes a network function virtualization infrastructure NFVI130, a virtual network function VNF108, and a virtual basis.
- the device state and resource monitoring module 121 is deployed in the virtualization layer 131 in the network function virtualization infrastructure 130, and the device state of the virtual machine or container for deploying the virtual network function 108 needs to be monitored.
- the virtual network function manager adds a resource monitoring field and a configuration resource monitoring field in the service description file, and the resource monitoring field includes a field of the device state of the virtual machine or the container of the enumerated type, and the virtual machine of the enumerated type.
- the field of the container resource information indicates that the device is in a normal state or a fault state
- the resource information indicates an operating parameter of the device, such as an operating parameter such as a CPU, a memory, a hard disk, or a network utilization
- the resource monitoring field further includes a monitoring flag bit. The monitoring flag indicates that the device status and the monitoring function of the resource monitoring module are turned on or off.
- the monitoring flag when the value of the monitoring flag is 1, it indicates that the device status and the monitoring function of the resource monitoring module are turned on. When the value of the monitoring flag is 0, it means to be turned off.
- the manager 104 sends a deployment request message carrying the resource monitoring field to the virtual infrastructure manager 106, and the virtual infrastructure manager 106 receives the deployment request message, and instructs to apply for the resource for creating the virtual machine or the container according to the deployment request message, and determines the specific Deploying a node, creating a virtual machine or container for deploying virtual network function 108, after successful creation, virtual infrastructure manager 106 sends a deployment request message carrying resource monitoring field to network function virtualization infrastructure 130; network function virtualization infrastructure
- the monitoring flag of the resource monitoring field in the deployment request message is determined to be true, the monitoring function of the device state and the resource monitoring module is started in the host operating system Host OS, and the device status and resource monitoring module 121 is presented as a virtual device.
- the virtual machine or the container of the virtual network function 108 is deployed.
- the device status and resource monitoring module 121 can simultaneously monitor virtual machines or containers of multiple virtual network functions.
- the device status and the resource monitoring module are simultaneously Monitor virtual network functions1
- the network function virtualization infrastructure 130 receives the subscription message sent by the virtual network function 108 (for example, the virtual network function 1), the device status and The monitoring module monitors the device status or resource monitoring information of the virtual machine or container in which the virtual network function 108 is deployed, and the network function virtualization infrastructure acquires the device status and the resource monitoring information monitored by the resource monitoring module 121, and virtualizes the network function.
- the infrastructure interface reports the device status and resource monitoring information of the virtual machine or container deploying the virtual network function 108 to the virtual network function 108.
- the device status and resource monitoring module 121 in the virtualization layer 131 is presented to the virtual network function 108 in a virtual device manner.
- the device status and resource monitoring module 121 is a virtual device for the virtual network function 108.
- the device status and resource occupancy of the virtual device can be sent.
- the virtual infrastructure manager 106 is sent to the virtual infrastructure manager 106 to subscribe to the virtual device's device state and resource occupancy status.
- the resource occupancy status indicates the virtual device's CPU, memory, disk, and network card. At least one operating parameter to achieve fault location for the virtual device.
- FIG. 5 is another schematic structural diagram of a network function virtualization infrastructure according to an embodiment of the present invention.
- the NFVI 5 includes a processor 501, a memory 502, and a transceiver 503.
- the transceiver 503 is configured to transmit and receive data with and from an external device.
- the number of processors 501 in NFVI 5 may be one or more.
- processor 501, memory 502, and transceiver 503 may be coupled by a bus system or other means.
- NFVI5 can be used to perform the method shown in Figure 2. For the meaning and examples of the terms involved in the embodiment, reference may be made to the corresponding embodiment of FIG. 2. I will not repeat them here.
- the program code is stored in the memory 502.
- the processor 501 is configured to call the program code stored in the memory 502 for performing the following operations:
- the device status and resource monitoring information of the virtual machine or container deploying the VNF are reported to the VNF by using the network function virtualization infrastructure interface according to the subscription message.
- the method before the processor 501 performs the receiving the subscription message sent by the virtual network function VNF, the method further includes:
- the monitoring function of the device state and the resource monitoring module is started in the host operating system Host OS, and the device state and the resource monitoring module are in a virtual device manner. Presented to the virtual machine or container that deployed the VNF.
- the processor 501 is further configured to:
- the subscription message is used to obtain device status and resource information of the virtual machine or container that is deployed by the NFVI to deploy the VNF;
- the device status of the virtual machine or the container includes an allocation to the At least one of a physical processor, a physical memory, a network card, and a state of a disk of the virtual machine or the container;
- the resource monitoring information of the virtual machine or the container includes a physical processor, physical memory, or At least one of the utilization of the network card and the disk.
- the resource monitoring field includes a field of a virtual machine or a container device state of an enumerated type and a field of virtual machine or container resource information of an enumerated type;
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)
- Environmental & Geological Engineering (AREA)
- Debugging And Monitoring (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
本发明实施例公开了一种设备状态及资源信息监测方法,该方法包括:网络功能虚拟化基础设施NFVI接收虚拟网络功能VNF发送的订阅消息;NFVI根据订阅消息通过网络功能虚拟化基础设施接口向VNF上报部署VNF的虚拟机或容器的设备状态及资源监测信息。采用本发明实施例,能够针对部署VNF的多个虚拟器或容器,统一利用NFVI来监测虚拟机或容器的设备状态及资源信息,避免每个虚拟机或容器都有自己的设备状态及资源监测机制引起的重复监控,从而降低了网络功能虚拟化系统的资源监控开销。
Description
本申请要求于2016年4月19日提交中国专利局、申请号为201610243244.1、发明名称为“一种设备状态及资源信息监测方法、相关设备及系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本发明涉及计算机技术领域,尤其涉及一种设备状态及资源信息监测方法、相关设备及系统。
传统的电信系统通过各种专用的硬件设备组成,不同的应用采用不同的硬件设备。随着网络规模的增长,系统越来越复杂,带来了诸多的挑战,包括新增业务的开发上线、系统的运维、资源利用率等。为了应对这些挑战及利用IT业界的虚拟化技术及云计算技术,在2012年10月22日召开的“SDN and OpenFlow World Congress”会议上,全球主要的13个电信运营商联合发布了NFV白皮书,并宣布在ETSI成立NFV ISG,制定NFV的需求及技术框架,推动NFV的发展。
网络功能虚拟化(Network Function Virtualization,NFV)技术可以简单地理解为将电信网络中使用的各个网元的功能从目前的专用硬件平台迁移至通用的商用货架产品(COTS,Commercial-off-the-shelf)服务器上。通过NFV技术将电信网络中使用的各个网元转变成为独立的应用,可以灵活部署在基于标准的服务器、存储以及交换机等其他设备构建的统一基础设施平台上,并通过虚拟化技术,对基础设施硬件设备资源池化及虚拟化,对上层应用提供虚拟资源,例如,将虚拟网络功能(Virtual Network Function,VNF)部署到虚拟机或容器中,实现应用与硬件之间的解耦,使得虚拟资源供给速度大大增加实现应用、硬件解耦,使得每一个应用能够快速增加虚拟资源以实现快速扩展系统容量的目的。然而,实践中发现,每个虚拟机或容器都有自己的设备状态及资源监测模块,若一个服务器上部署上千个虚拟机或容器,将会有上千个资源监测模块,导致资源开销过大。
发明内容
本发明实施例公开了一种设备状态及资源信息监测方法、相关设备及系统,能够去除重复监控,降低资源监控开销。
本发明实施例公开了一种设备状态及资源信息监测方法,该方法包括:网络功能虚拟化基础设施NFVI接收虚拟网络功能VNF发送的订阅消息;其中,该订阅消息用于获取NFVI监测的部署VNF创建的虚拟机或容器的设备状态及资源监测信息;虚拟机或容器的设备状态包括分配给虚拟机或容器的物理处理器、物理内存、网卡及磁盘的状态;虚拟机或容器的资源监测信息包括分配给虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率;NFVI根据订阅消息通过网络功能虚拟化基础设施接口向VNF上报部署VNF创建的虚拟机或
容器的设备状态及资源监测信息。采用本发明实施例,能够针对部署VNF而创建的多个虚拟器或容器,统一利用NFVI来监测虚拟机或容器的设备状态及资源监测信息,避免每个虚拟机或容器都有自己的设备状态及资源监测机制引起的重复监控,从而,降低了网络功能虚拟化系统的资源监控开销。
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1是本发明实施例公开的一种网络功能虚拟化NFV的系统架构图;
图2是本发明实施例公开的一种设备状态及资源信息监测方法的流程示意图;
图3是本发明实施例公开的一种网络功能虚拟化基础设施的结构示意图;
图4是本发明实施例公开的一种设备状态及资源信息监测系统的架构示意图;
图5是本发明实施例公开的网络功能虚拟化基础设施的另一结构示意图。
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
为了更好的理解本发明实施例,下面先对本发明实施例的网络功能虚拟化NFV(Network Function Virtualization,网络功能虚拟化,简称NFV)的系统架构图进行描述。如图1所示,图1是NFV系统的架构图,NFV系统100可以在各种不同的网络环境中使用,例如:一个数据中心网络、运营商网络或局域网来实现。NFV系统100包括一个网络功能虚拟化管理和编排系统(NFV-Management and Orchestration,NFV-MANO)101、网络功能虚拟化基础设施(NFV Infrastructure,NFVI)130、多个网元管理(Element Management,EM)122、多个虚拟网络功能(Virtual Network Function,VNF)108、网络服务、VNF和基础设施描述126(Network Service,VNF and Infrastructure Description)以及运营支撑系统/业务支撑系统(Operation-Support System/Business Support System,OSS/BSS)124。其中,网络功能虚拟化编排和管理系统101包括网络功能虚拟化编排器(NFV Orchestrator,NFVO)102、一个或多个虚拟网络功能管理器(VNF Manager,VNFM)104和虚拟化基础设施管理器(Virtualized Infrastructure Manager,VIM)106。网络功能虚拟化基础设施130包括硬件资源层、虚拟化层和虚拟资源层,硬件资源层包括计算硬件112、存储硬件114和网络硬件116,虚拟资源层包括虚拟计算110、虚拟存储118和虚拟网络120。网络服务、VNF和基础设施描述126和运营支撑系统/业务支撑系统124在ETSI GS NFV 002 V1.1.1标准中有进一步的讨论。
NFV管理和编排系统101用于执行对虚拟网络功能108和网络功能虚拟化基础设施130的监视和管理。网络功能虚拟化编排器102可以实现在网络功能虚拟化基础设施130上的网络
服务(如L2和L3VPN服务),也可以执行来自一个或多个虚拟网络功能管理器104的资源相关请求,发送配置信息到虚拟网络功能管理器104,并收集虚拟网络功能108的状态信息。另外,网络功能虚拟化编排器102可以与虚拟基础设施管理器106通信,以实现资源的分配和/或预留以及交换虚拟化硬件资源的配置和状态信息。虚拟网络功能管理器104可以管理一个或多个虚拟网络功能108。虚拟网络功能管理器104可以执行各种管理功能,例如实例化、更新、查询、缩放和/或终止虚拟网络功能108等。虚拟基础设施管理器106可以执行资源管理的功能,例如管理基础设施资源的分配(例如增加资源到容器)和操作功能(如收集网络功能虚拟化基础设施故障信息)。虚拟网络功能管理器104和虚拟基础设施管理器106可以相互通信进行资源分配和交换虚拟化硬件资源的配置和状态信息。
网络功能虚拟化基础设施130包括硬件资源、软件资源或两者的组合来完成虚拟化环境的部署。换句话说,硬件资源和虚拟化层用于提供虚拟化的资源,例如作为虚拟机和其他形式的容器,用于安装虚拟网络功能108。硬件资源包括计算硬件112、存储硬件114和网络硬件116。计算硬件112可以是市场上现成的硬件和/或用户定制的硬件,用来提供处理和计算资源。存储硬件114可以是网络内提供的存储容量或驻留在存储硬件114本身的存储容量(位于服务器内的本地存储器)。在一种可能的实现方式中,计算硬件112和存储硬件114可以被集中在一起。网络硬件116可以是交换机、路由器和/或配置成具有交换功能的任何其他网络设备。网络硬件116可以横跨多个域,并且可以包括多个由一个或一个以上传输网络互连的网络。
网络功能虚拟化基础设施130的虚拟化层可以从物理层抽象硬件资源和解耦虚拟网络功能108,以便向虚拟网络功能108提供虚拟化资源。虚拟资源层包括虚拟计算110、虚拟存储118和虚拟网络120。虚拟计算110和虚拟存储118可以以虚拟机和/或其他容器的形式提供给虚拟网络功能108。例如:一个或一个以上的虚拟网络功能108可以部署在一个虚拟机(Virtual Machine)上。虚拟化层抽象网络硬件116形成虚拟网络120,虚拟网络120可以包括虚拟交换机(Virtual Switch),虚拟交换机用来提供虚拟机之间的连接。此外,网络硬件116中的传输网络,可以采用集中式控制平面和一个单独的转发平面(如软件定义网络,SDN)虚拟化。
如图1所示,虚拟网络功能管理器104可与虚拟网络功能108和网元管理122交互来对虚拟网络功能108的生命周期进行管理以及交换配置和状态信息。虚拟网络功能108可以被配置为通过一个物理网络设备执行的至少一个网络功能的虚拟化。例如,在一个实现方案中,虚拟网络功能108可以经过配置以提供IMS(IP Multimedia Subsystem,IP多媒体子系统,简称IMS)网络中的不同网元具备的功能,如P-CSCF(Proxy-Call Session Control Funtion,代理呼叫会话控制功能,简称P-CSCF)、S-CSCF(Serving-Call Session Control Funtion,服务呼叫会话控制功能,简称PSCSCF))或HSS(Home Subscriber Server,归属签约用户服务器,简称HSS)的网络功能等。网元管理122经过配置以对一个或一个以上的虚拟网络功能108进行管理。
在现有的NFV系统中,虚拟网络功能108可以部署在容器或虚拟机中,为实现对虚拟机或容器的设备状态和资源信息的监控,每个虚拟机或容器都有自己独立的设备状态和资源监测模块,若一个服务器上部署上千个虚拟机或容器,将会有上千个设备状态和资源监测模块,导致资源开销过大,造成资源浪费。
请参阅图2,图2是本发明实施例公开的一种设备状态及资源信息监测方法的流程示意图,在本发明实施例中,所述方法包括以下步骤:
S201、网络功能虚拟化基础设施NFVI接收虚拟网络功能VNF发送的订阅消息。
具体的,VNF部署在虚拟机或容器中,VNF需要获取虚拟机或容器的设备状态及资源监测信息时,向NFVI发送订阅消息,NFVI接收VNF发送的订阅消息,设备状态表示分配给虚拟机或容器的硬件资源为正常状态或故障状态,资源监测信息表示分配给虚拟机或容器的硬件资源的运行参数,例如:利用率、空闲率、丢包率、运行时间或故障时间等。
S202、所述NFVI根据所述订阅消息通过网络功能虚拟化基础设施接口向所述VNF上报部署所述VNF的虚拟机或容器的设备状态及资源监测信息。
具体的,NFVI监测部署VNF的虚拟机或容器的设备状态及资源监测信息,例如,NFVI在虚拟化层上分配的物理服务器所在的Host OS上增加设备状态及资源监测模块,设备状态及资源监测模块用于监测部署VNF的虚拟机或容器的设备状态及资源监测信息,当部署多个VNF时,多个VNF的虚拟机或容器共用一个设备状态及资源监测模块,NFVI将监测到的设备状态及资源监测信息通过网络功能虚拟化基础设施接口向上报给VNF。
可选的,所述网络功能虚拟化基础设施NFVI接收虚拟网络功能VNF发送的订阅消息之前,所述方法还包括:
所述NFVI接收所述VIM发送的用于创建虚拟机或容器的部署请求消息;
所述NFVI根据所述部署请求消息创建部署所述VNF的虚拟机或容器;
所述NFVI确定所述部署请求消息中资源监测字段的值为真时,在主机操作系统Host OS中启动监测模块的监测功能,并将所述监测模块以虚拟设备方式呈现给部署所述VNF的虚拟机或容器。
具体的,NFVI在虚拟化层上分配的物理服务器所在的Host OS中增加设备状态及资源监测模块,设备状态及资源监测模块用于检测部署VNF的虚拟机或容器的设备状态及资源监测信息,当需要启动设备状态及资源监测模块的监测功能时,VIM向NFVI发送部署请求消息,部署请求消息用于创建安装VNF的虚拟机或容器,部署请求消息中携带资源监测字段,资源监测字段为枚举型数据,表示分配给虚拟机或容器的硬件资源的设备状态及运行参数,NFVI根据部署请求消息创建VNF的虚拟机或容器,以及解析资源监测字段的监测标志位的值,在NFVI确定资源监测字段中的监测标志位的值为真时,例如:监测标志位的值为1时,表示开启设备状态及资源监测模块的监测功能,监测标志位的值为0时,表示关闭设备状态及资源监测模块的监测功能,NFVI确定需要开启设备状态及资源监测模块的监测功能时,在虚拟化层上分配物理服务器所在的Host OS中开启设备状态及资源监测模块的监测功能,并将设备状态及资源监测模块以虚拟设备方式呈现给部署VNF的虚拟机或容器,此时设备状态及资源监测模块对于虚拟机或容器而言为一个虚拟设备,开启设备状态及资源监测模块的监测功能后,设备状态及资源监测模块监测用于部署VNF的虚拟机或容器的设备状态及资源监测信息。
可选的,所述方法还包括:
当所述NFVI监测到部署所述VNF的虚拟机或容器出现预设故障时,所述NFVI将所述预设故障的故障信息发送给虚拟网络基础设施管理器VIM,由所述VIM根据所述故障信息处理所
述预设故障。
具体的,预设故障可以是无法联网、磁盘读写出错、软件无法失败等故障,NFVI监测到虚拟机或容器发生预设故障时,可以将预设故障对应的故障代码和故障描述信息,其中,每种类型的故障对应一个故障代码,故障描述信息表示发生故障的应用程序、设备的运行参数(CPU占用率、磁盘剩余空间、内存占用率等),将包括故障代码和故障描述信息的故障信息上报给VIM,VIM根据NFVI上报的故障信息进行定位发生故障的硬件设备。
可选的,所述订阅消息用于获取所述NFVI监测的部署所述VNF的虚拟机或容器的设备状态及资源信息;所述虚拟机或容器的设备状态包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的状态中的至少一个;所述虚拟机或容器的资源监测信息包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率中的至少一个。
具体的,设备状态表示分配给虚拟机或容器的硬件资源为正常状态或故障状态,硬件资源包括物理处理器、物理内存、网卡机磁盘中的至少一个;资源监测信息表示分配给虚拟机或容器的硬件资源的运行参数,例如:资源监测信息包括物理处理器、物理内存、网卡及磁盘的利用率中的至少一个。
可选的,所述资源监测字段包括枚举类型的虚拟机或容器设备状态的字段以及枚举类型的虚拟机或容器资源信息的字段;
所述枚举类型的虚拟机或容器设备状态的字段,用于监控分配给虚拟机或容器的物理处理器、物理内存、网卡及磁盘的状态;所述枚举类型的虚拟机或容器资源信息的字段,用于监控虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率。
采用本发明实施例,能够针对部署VNF而创建的多个虚拟器或容器,统一利用NFVI来监测虚拟机或容器的设备状态及资源监测信息,避免每个虚拟机或容器都有自己的设备状态及资源监测机制引起的重复监控,从而降低了网络功能虚拟化系统的资源监控开销。
请参阅图3,图3是本发明实施例公开的一种网络功能虚拟化基础设施的结构示意图,在本发明实施例中,网络功能虚拟化基础设施包括接收模块301和上报模块302。
接收模块301,用于接收虚拟网络功能VNF发送的订阅消息。
具体的,VNF部署在虚拟机或容器中,VNF需要获取虚拟机或容器的设备状态及资源监测信息时,向NFVI发送订阅消息,NFVI的接收模块301接收VNF发送的订阅消息。设备状态表示分配给虚拟机或容器的硬件资源为正常状态或故障状态,资源监测信息表示分配给虚拟机或容器的硬件资源的运行参数,例如:运行参数包括利用率、空闲率、丢包率、运行时间或故障时间等。
上报模块302,用于根据所述订阅消息通过网络功能虚拟化基础设施接口向所述VNF上报部署所述VNF的虚拟机或容器的设备状态及资源监测信息。
具体的,上报模块302获取部署VNF的虚拟机或容器的设备状态及资源监测信息,例如,在虚拟化层上分配的物理服务器所在的Host OS上增加设备状态及资源监测模块,设备状态及资源监测模块监测部署VNF的虚拟机或容器的设备状态及资源监测信息,上报模块302获取设备状态及资源监测模块监测到的设备状态及资源监测信息,上报给VNF。其中,当部署多个VNF时,多个VNF的虚拟机或容器共用一个设备状态及资源监测模块,上报模块302将获取到的设备状态及资源监测信息通过网络功能虚拟化基础设施接口向上报给VNF。
可选的,在本发明的一些实施例中,所述接收模块还用于在接收虚拟网络功能VNF发送的订阅消息之前,接收所述VIM发送的用于创建虚拟机或容器的部署请求消息;
所述NFVI还包括:
创建模块,用于根据所述部署请求消息创建部署所述VNF的虚拟机或容器;
启动模块,用于确定所述部署请求消息中资源监测字段的监测标志位为真时,在主机操作系统Host OS中启动设备状态及资源监测模块的监测功能;
所述设备状态及资源监测模块,用于监测部署所述VNF的虚拟机或容器的设备状态及资源监测信息;其中,所述设备状态及资源监测模块以虚拟设备方式呈现给部署所述VNF的虚拟机或容器。
具体的,NFVI在虚拟化层上分配的物理服务器所在的Host OS中增加设备状态及资源监测模块,设备状态及资源监测模块用于检测部署VNF的虚拟机或容器的设备状态及资源监测信息,当需要启动设备状态及资源监测模块的监测功能时,VIM向NFVI发送部署请求消息,部署请求消息用于创建安装VNF的虚拟机或容器,部署请求消息中携带资源监测字段,资源监测字段为枚举型数据,表示分配给虚拟机或容器的硬件资源的设备状态及运行参数,NFVI的创建模块根据部署请求消息创建VNF的虚拟机或容器,启动模块解析资源监测字段的监测标志位的值,启动在确定资源监测字段中的监测标志位的值为真时,例如:监测标志位的值为1时,表示开启设备状态及资源监测模块的监测功能,监测标志位的值为0时,表示关闭设备状态及资源监测模块的监测功能,启动模块确定需要开启设备状态及资源监测模块的监测功能时,在虚拟化层上分配物理服务器所在的Host OS中开启设备状态及资源监测模块的监测功能,并将设备状态及资源监测模块以虚拟设备方式呈现给部署VNF的虚拟机或容器,此时设备状态及资源监测模块对于虚拟机或容器而言为一个虚拟设备,开启设备状态及资源监测模块的监测功能后,设备状态及资源监测模块监测用于部署VNF的虚拟机或容器的设备状态及资源监测信息。
可选的,在本发明的一些实施例中,所述NFVI还包括:
发送模块,用于在所述NFVI监测到部署所述VNF的虚拟机或容器出现预设故障时,将所述预设故障的故障信息发送给虚拟网络基础设施管理器VIM,由所述VIM根据所述故障信息处理所述预设故障。
具体的,预设故障可以是无法联网、磁盘读写出错、软件无法失败等故障,NFVI监测到虚拟机或容器发生预设故障时,可以将预设故障对应的故障代码和故障描述信息,其中,每种类型的故障对应一个故障代码,故障描述信息表示发生故障的应用程序、设备的运行参数(例如:CPU占用率、磁盘剩余空间、内存占用率等),发送模块将包括故障代码和故障描述信息的故障信息上报给VIM,VIM根据NFVI上报的故障信息进行定位发生故障的硬件设备。
可选的,在本发明的一些实施例中,所述订阅消息用于获取所述NFVI监测的部署所述VNF的虚拟机或容器的设备状态及资源信息;所述虚拟机或容器的设备状态包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的状态中的至少一个;所述虚拟机或容器的资源监测信息包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率中的至少一个。
具体的,设备状态表示分配给虚拟机或容器的硬件资源为正常状态或故障状态,硬件
资源包括物理处理器、物理内存、网卡机磁盘中的至少一个;资源监测信息表示分配给虚拟机或容器的硬件资源的运行参数,例如:资源监测信息包括物理处理器、物理内存、网卡及磁盘的利用率中的至少一个。
可选的,在本发明的一些实施例中,所述资源监测字段包括枚举类型的虚拟机或容器设备状态的字段以及枚举类型的虚拟机或容器资源信息的字段;
所述枚举类型的虚拟机或容器设备状态的字段,用于监控分配给虚拟机或容器设备的物理处理器、物理内存、网卡及磁盘的状态;所述枚举类型的虚拟机或容器资源信息的字段,用于监控虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率。
本发明实施例和方法实施例一基于同一构思,其带来的技术效果也相同,具体过程可参照方法实施例的描述。
请参阅图4,图4是本发明实施例公开的一种设备状态及资源信息监测系统的架构示意图,设备状态及资源信息监测系统包括网络功能虚拟化基础设施NFVI130、虚拟网络功能VNF108、虚拟基础设施管理器VIM106以及虚拟化网络功能管理器VNFM104。该实施例与图1相比,在网络功能虚拟化基础设备130中的虚拟化层131部署设备状态及资源监测模块121,需要监控用于部署虚拟网络功能108的虚拟机或容器的设备状态和资源监测信息时,虚拟网络功能管理器在业务描述文件中增加资源监测字段和配置资源监测字段,资源监测字段包括枚举类型的虚拟机或容器的设备状态的字段,以及枚举类型的虚拟机或容器资源信息的字段,设备状态表示设备为正常状态或故障状态,资源信息表示设备的运行参数,例如CPU、内存、硬盘或网络的利用率等运行参数,资源监测字段中还包括监测标志位,监测标志位表示开启或关闭设备状态及资源监测模块的监测功能,例如,监测标志位的值为1时表示开启设备状态及资源监测模块的监测功能,监测标志位的值为0时表示关闭设备状态及资源监测模块的监测功能;虚拟网络功能管理器104向虚拟基础设施管理器106发送携带资源监测字段的部署请求消息,虚拟基础设施管理器106接收部署请求消息,根据部署请求消息指示申请用于创建虚拟机或容器的资源,确定具体的部署节点,创建用于部署虚拟网络功能108的虚拟机或容器,创建成功后虚拟基础设施管理器106向网络功能虚拟化基础设施130发送携带资源监测字段的部署请求消息;网络功能虚拟化基础设施130确定部署请求消息中资源监测字段的监测标志位为真时,在主机操作系统Host OS中启动设备状态及资源监测模块的监测功能,并将设备状态及资源监测模块121以虚拟设备方式呈现给部署虚拟网络功能108的虚拟机或容器,需要说明的是,设备状态及资源监测模块121可同时监控多个虚拟网络功能的虚拟机或容器,以图中为例子,设备状态及资源监控模块同时监控虚拟网络功能1、虚拟网络功能2和虚拟网络功能3各自的虚拟机或容器的设备状态及资源监测信息;网络功能虚拟化基础设施130接收虚拟网络功能108(例如虚拟网络功能1)发送的订阅消息,设备状态及监测模块监测部署虚拟网络功能108的虚拟机或容器的设备状态或资源监测信息,网络功能虚拟化基础设施获取设备状态及资源监测模块121监测到的设备状态及资源监测信息,通过网络功能虚拟化基础设施接口向虚拟网络功能108上报部署虚拟网络功能108的虚拟机或容器的设备状态及资源监测信息。其中,虚拟化层131中的设备状态及资源监测模块121以虚拟设备方式呈现给虚拟网络功能108,此时设备状态及资源监测模块121对于虚拟网络功能108而言为一个虚拟设备,Host OS也可以将该虚拟设备的设备状态和资源占用情况发
送给虚拟基础设施管理器106,其他虚拟网络功能可以向虚拟基础设施管理器106订阅该虚拟设备的设备状态和资源占用情况,资源占用情况表示该虚拟设备的CPU、内存、磁盘和网卡中的至少一个的运行参数,以实现对虚拟设备的故障定位。
请参阅图5,图5是本发明实施例公开的网络功能虚拟化基础设施的另一结构示意图,在本发明实施例中,NFVI5包括处理器501、存储器502和收发器503。收发器503用于与外部设备之间收发数据。NFVI5中的处理器501的数量可以是一个或多个。本发明的一些实施例中,处理器501、存储器502和收发器503可通过总线系统或其他方式连接。NFVI5可以用于执行图2所示的方法。关于本实施例涉及的术语的含义以及举例,可以参考图2对应的实施例。此处不再赘述。
其中,存储器502中存储程序代码。处理器501用于调用存储器502中存储的程序代码,用于执行以下操作:
接收虚拟网络功能VNF发送的订阅消息;
根据所述订阅消息通过网络功能虚拟化基础设施接口向所述VNF上报部署所述VNF的虚拟机或容器的设备状态及资源监测信息。
在本发明的一些实施例中,处理器501执行所述接收虚拟网络功能VNF发送的订阅消息之前,所述方法还包括:
接收所述VIM发送的用于创建虚拟机或容器的部署请求消息;
根据所述部署请求消息创建部署所述VNF的虚拟机或容器;
确定所述部署请求消息中资源监测字段的监测标志位为真时,在主机操作系统Host OS中启动设备状态及资源监测模块的监测功能,并将所述设备状态及资源监测模块以虚拟设备方式呈现给部署所述VNF的虚拟机或容器。
在本发明的一些实施例中,处理器501还用于执行:
当监测到部署所述VNF的虚拟机或容器出现预设故障时,将所述预设故障的故障信息发送给虚拟网络基础设施管理器VIM,由所述VIM根据所述故障信息处理所述预设故障。
在本发明的一些实施例中,所述订阅消息用于获取所述NFVI监测的部署所述VNF的虚拟机或容器的设备状态及资源信息;所述虚拟机或容器的设备状态包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的状态中的至少一个;所述虚拟机或容器的资源监测信息包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率中的至少一个。
在本发明的一些实施例中,所述资源监测字段包括枚举类型的虚拟机或容器设备状态的字段以及枚举类型的虚拟机或容器资源信息的字段;
所述枚举类型的虚拟机或容器设备状态的字段,用于监控分配给虚拟机或容器设备的物理处理器、物理内存、网卡及磁盘的状态;所述枚举类型的虚拟机或容器资源信息的字段,用于监控虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率。
以上对本发明实施例公开的一种设备状态及资源信息监测方法、相关设备及系统进行了详细介绍,本文中应用了具体个例对本发明的原理及实施方式进行了阐述,以上实施例的说明只是用于帮助理解本发明的方法及其核心思想;同时,对于本领域的一般技术人员,依据本发明的思想,在具体实施方式及应用范围上均会有改变之处,综上所述,本说明书内容不应理解为对本发明的限制。
Claims (11)
- 一种设备状态及资源信息监测方法,其特征在于,包括:网络功能虚拟化基础设施NFVI接收虚拟网络功能VNF发送的订阅消息;所述NFVI根据所述订阅消息通过网络功能虚拟化基础设施接口向所述VNF上报部署所述VNF的虚拟机或容器的设备状态及资源监测信息。
- 根据权利要求1所述的方法,其特征在于,所述网络功能虚拟化基础设施NFVI接收虚拟网络功能VNF发送的订阅消息之前,所述方法还包括:所述NFVI接收所述VIM发送的用于创建虚拟机或容器的部署请求消息;所述NFVI根据所述部署请求消息创建部署所述VNF的虚拟机或容器;所述NFVI确定所述部署请求消息中资源监测字段的监测标志位为真时,在主机操作系统Host OS中启动设备状态及资源监测模块的监测功能,并将所述设备状态及资源监测模块以虚拟设备方式呈现给部署所述VNF的虚拟机或容器。
- 根据权利要求2所述的方法,其特征在于,所述方法还包括:当所述NFVI监测到部署所述VNF的虚拟机或容器出现预设故障时,所述NFVI将所述预设故障的故障信息发送给虚拟网络基础设施管理器VIM,由所述VIM根据所述故障信息处理所述预设故障。
- 根据权利要求1至3任一项所述的方法,其特征在于,所述订阅消息用于获取所述NFVI监测的部署所述VNF的虚拟机或容器的设备状态及资源信息;所述虚拟机或容器的设备状态包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的状态中的至少一个;所述虚拟机或容器的资源监测信息包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率中的至少一个。
- 根据权利要求4所述的方法,其特征在于,所述资源监测字段包括枚举类型的虚拟机或容器设备状态的字段以及枚举类型的虚拟机或容器资源信息的字段;所述枚举类型的虚拟机或容器设备状态的字段,用于监控分配给虚拟机或容器设备的物理处理器、物理内存、网卡及磁盘的状态;所述枚举类型的虚拟机或容器资源信息的字段,用于监控虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率。
- 一种网络功能虚拟化基础设施NFVI,其特征在于,包括:接收模块,用于接收虚拟网络功能VNF发送的订阅消息;上报模块,用于根据所述订阅消息通过网络功能虚拟化基础设施接口向所述VNF上报部署所述VNF的虚拟机或容器的设备状态及资源监测信息。
- 根据权利要求6所述的NFVI,其特征在于,所述接收模块还用于在接收虚拟网络功能VNF发送的订阅消息之前,接收所述VIM发送的用于创建虚拟机或容器的部署请求消息;所述NFVI还包括:创建模块,用于根据所述部署请求消息创建部署所述VNF的虚拟机或容器;启动模块,用于确定所述部署请求消息中资源监测字段的监测标志位为真时,在主机操作系统Host OS中启动设备状态及资源监测模块的监测功能;所述设备状态及资源监测模块,用于监测部署所述VNF的虚拟机或容器的设备状态及资源监测信息;其中,所述设备状态及资源监测模块以虚拟设备方式呈现给部署所述VNF的虚拟机或容器。
- 根据权利要求7所述的NFVI,其特征在于,所述NFVI还包括:发送模块,用于在所述NFVI监测到部署所述VNF的虚拟机或容器出现预设故障时,将所述预设故障的故障信息发送给虚拟网络基础设施管理器VIM,由所述VIM根据所述故障信息处理所述预设故障。
- 根据权利要求6至8任一项所述的NFVI,其特征在于,所述订阅消息用于获取所述NFVI监测的部署所述VNF的虚拟机或容器的设备状态及资源信息;所述虚拟机或容器的设备状态包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的状态中的至少一个;所述虚拟机或容器的资源监测信息包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率中的至少一个。
- 根据权利要求9所述的NFVI,其特征在于,所述资源监测字段包括枚举类型的虚拟机或容器设备状态的字段以及枚举类型的虚拟机或容器资源信息的字段;所述枚举类型的虚拟机或容器设备状态的字段,用于监控分配给虚拟机或容器的物理处理器、物理内存、网卡及磁盘的状态;所述枚举类型的虚拟机或容器资源信息的字段,用于监控虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率。
- 一种设备状态及资源信息监测系统,其特征在于,包括:网络功能虚拟化基础设施NFVI、虚拟网络功能VNF、虚拟网络基础设施管理器VIM以及虚拟化网络功能管理器VNFM,其中,所述VNFM在所述VNF的每个实例中增加资源监测字段,并根据所述每个实例的要求设置所述资源监测字段,向所述VIM发送用于创建虚拟机或容器的部署请求消息;所述部署请求消息中携带所述资源监测字段;所述VIM将所述部署请求消息发送给所述NFVI;所述NFVI接收所述部署请求消息,根据所述部署请求消息创建部署所述VNF的虚拟机或容器,确定所述部署请求消息中资源监测字段的监测标志位为真时,在主机操作系统Host OS中启动设备状态及资源监测模块的监测功能,并将所述设备状态及资源监测模块以虚拟设备方式呈现给部署所述VNF的虚拟机或容器;所述VNF向所述NFVI发送订阅消息,所述订阅消息用于获取所述NFVI监测的部署所述VNF的虚拟机或容器的设备状态及资源信息;所述虚拟机或容器的设备状态包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的状态中的至少一个;所述虚拟机或容器的资源监测信息包括分配给所述虚拟机或容器的物理处理器、物理内存、网卡及磁盘的利用率中的至少一个;所述NFVI根据所述订阅消息通过网络功能虚拟化基础设施接口向所述VNF上报部署所述VNF的虚拟机或容器的设备状态及资源监测信息。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610243244.1A CN105760214B (zh) | 2016-04-19 | 2016-04-19 | 一种设备状态及资源信息监测方法、相关设备及系统 |
CN201610243244.1 | 2016-04-19 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017181876A1 true WO2017181876A1 (zh) | 2017-10-26 |
Family
ID=56335322
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/080111 WO2017181876A1 (zh) | 2016-04-19 | 2017-04-11 | 一种设备状态及资源信息监测方法、相关设备及系统 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN105760214B (zh) |
WO (1) | WO2017181876A1 (zh) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110166503A (zh) * | 2018-02-11 | 2019-08-23 | 中国移动通信有限公司研究院 | 信息交互方法、设备及计算机可读存储介质 |
CN111130925A (zh) * | 2019-11-29 | 2020-05-08 | 广州文远知行科技有限公司 | 资源监控方法、装置、计算机设备和存储介质 |
CN111443984A (zh) * | 2019-01-17 | 2020-07-24 | 中国移动通信有限公司研究院 | 网络功能虚拟化nvf系统的容器部署方法及装置 |
CN111597032A (zh) * | 2020-05-26 | 2020-08-28 | 北京学之途网络科技有限公司 | 任务调度管理方法、装置及电子设备 |
CN111835685A (zh) * | 2019-04-19 | 2020-10-27 | 厦门网宿有限公司 | 一种监控Nginx网络隔离空间的运行状态的方法和服务器 |
CN111835684A (zh) * | 2019-04-19 | 2020-10-27 | 厦门网宿有限公司 | 一种haproxy设备的网络隔离监控方法及系统 |
CN111953503A (zh) * | 2019-05-14 | 2020-11-17 | 中国电信股份有限公司 | Nfv资源部署编排方法和网络功能虚拟化编排器 |
US10880370B2 (en) | 2018-11-27 | 2020-12-29 | At&T Intellectual Property I, L.P. | Virtual network manager system |
WO2020263874A1 (en) * | 2019-06-25 | 2020-12-30 | Vmware, Inc. | Systems and methods for selectively implementing services on virtual machines and containers |
CN114157585A (zh) * | 2021-12-09 | 2022-03-08 | 京东科技信息技术有限公司 | 一种业务资源监测的方法和装置 |
US11296975B2 (en) | 2019-06-25 | 2022-04-05 | Vmware, Inc. | Systems and methods for implementing multi-part virtual network functions |
CN114374609A (zh) * | 2021-12-06 | 2022-04-19 | 东云睿连(武汉)计算技术有限公司 | 基于rdma设备的深度学习作业运行方法及系统 |
Families Citing this family (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105760214B (zh) * | 2016-04-19 | 2019-02-26 | 华为技术有限公司 | 一种设备状态及资源信息监测方法、相关设备及系统 |
CN106487633B (zh) * | 2016-10-11 | 2019-12-06 | 中国银联股份有限公司 | 一种虚拟机异常的监测方法和装置 |
CN106452925B (zh) * | 2016-12-02 | 2021-01-05 | 华为技术有限公司 | 在nfv系统中检测故障的方法、装置和系统 |
CN110178342B (zh) * | 2017-01-14 | 2022-07-12 | 瑞典爱立信有限公司 | Sdn网络的可扩缩应用级别监视 |
US10523550B2 (en) * | 2017-04-27 | 2019-12-31 | Huawei Technologies Co., Ltd. | Scout functions |
CN107689953B (zh) * | 2017-08-18 | 2020-10-27 | 中国科学院信息工程研究所 | 一种面向多租户云计算的容器安全监控方法及系统 |
CN107678836B (zh) * | 2017-10-12 | 2021-09-03 | 新华三大数据技术有限公司 | 集群的测试数据获取方法及装置 |
CN110275756B (zh) * | 2018-03-13 | 2023-04-18 | 华为技术有限公司 | 虚拟化网元的部署方法以及装置 |
CN110311798B (zh) * | 2018-03-20 | 2021-02-12 | 华为技术有限公司 | 一种管理虚拟资源的方法及装置 |
CN114880078A (zh) | 2018-06-05 | 2022-08-09 | 华为技术有限公司 | 管理容器服务的方法和装置 |
CN110618884A (zh) * | 2018-06-19 | 2019-12-27 | 中国电信股份有限公司 | 故障监控方法、虚拟化的网络功能模块管理器和存储介质 |
CN110673981B (zh) * | 2018-07-03 | 2022-06-17 | 中国电信股份有限公司 | 故障恢复方法、装置和系统 |
CN109218071B (zh) * | 2018-07-17 | 2020-09-29 | 华为技术有限公司 | 一种nfv环境下的拨测方法及装置 |
CN111221620B (zh) * | 2018-11-27 | 2024-02-09 | 华为技术有限公司 | 存储方法、装置及存储介质 |
CN111698112B (zh) * | 2019-03-15 | 2021-09-14 | 华为技术有限公司 | 一种容器化虚拟网络功能vnf的资源管理方法及装置 |
CN110134519A (zh) * | 2019-05-21 | 2019-08-16 | 中国太平洋保险(集团)股份有限公司 | 一种基于容器平台实现网站管理的控制方法及装置 |
CN112395152B (zh) * | 2019-08-19 | 2022-04-12 | 阿里巴巴集团控股有限公司 | 服务器资源获取方法及获取系统 |
CN110740121B (zh) * | 2019-09-09 | 2023-04-07 | 西安万像电子科技有限公司 | 资源订阅系统及方法 |
CN111130953B (zh) * | 2019-12-31 | 2022-04-15 | 奇安信科技集团股份有限公司 | Vnf可用性监测方法、设备及介质 |
CN113342456A (zh) * | 2020-03-02 | 2021-09-03 | 中兴通讯股份有限公司 | 一种连接方法、装置、设备和存储介质 |
CN112214281A (zh) * | 2020-09-24 | 2021-01-12 | 明辰智航(北京)测试技术有限公司 | 一种监测虚拟数据的方法和系统 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103186450A (zh) * | 2011-12-28 | 2013-07-03 | 英业达集团(天津)电子技术有限公司 | 虚拟资源的使用消耗的监测方法及系统 |
CN105049293A (zh) * | 2015-08-21 | 2015-11-11 | 中国联合网络通信集团有限公司 | 监控的方法及装置 |
WO2016026129A1 (en) * | 2014-08-22 | 2016-02-25 | Nokia Technologies Oy | A security and trust framework for virtualized networks |
CN105490846A (zh) * | 2015-12-07 | 2016-04-13 | 中国电子科技集团公司第三十二研究所 | 服务器虚拟化管理系统及方法 |
CN105760214A (zh) * | 2016-04-19 | 2016-07-13 | 华为技术有限公司 | 一种设备状态及资源信息监测方法、相关设备及系统 |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2936754B1 (en) * | 2013-01-11 | 2020-12-02 | Huawei Technologies Co., Ltd. | Network function virtualization for a network device |
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 |
RU2640724C1 (ru) * | 2014-04-09 | 2018-01-11 | Хуавей Текнолоджиз Ко., Лтд. | Способ устранения неисправностей, устройство и система, основанные на виртуализации сетевых функций |
CN104050045B (zh) * | 2014-06-27 | 2017-06-27 | 华为技术有限公司 | 基于磁盘io的虚拟资源分配方法及装置 |
CN104869023B (zh) * | 2015-05-29 | 2019-02-26 | 华为技术有限公司 | 一种时间校正方法、装置及系统 |
CN105119736B (zh) * | 2015-07-15 | 2019-01-18 | 华为技术有限公司 | 网络功能虚拟化架构中数据检查的方法和装置 |
CN105187249B (zh) * | 2015-09-22 | 2018-12-07 | 华为技术有限公司 | 一种故障恢复方法及装置 |
-
2016
- 2016-04-19 CN CN201610243244.1A patent/CN105760214B/zh active Active
-
2017
- 2017-04-11 WO PCT/CN2017/080111 patent/WO2017181876A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103186450A (zh) * | 2011-12-28 | 2013-07-03 | 英业达集团(天津)电子技术有限公司 | 虚拟资源的使用消耗的监测方法及系统 |
WO2016026129A1 (en) * | 2014-08-22 | 2016-02-25 | Nokia Technologies Oy | A security and trust framework for virtualized networks |
CN105049293A (zh) * | 2015-08-21 | 2015-11-11 | 中国联合网络通信集团有限公司 | 监控的方法及装置 |
CN105490846A (zh) * | 2015-12-07 | 2016-04-13 | 中国电子科技集团公司第三十二研究所 | 服务器虚拟化管理系统及方法 |
CN105760214A (zh) * | 2016-04-19 | 2016-07-13 | 华为技术有限公司 | 一种设备状态及资源信息监测方法、相关设备及系统 |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110166503B (zh) * | 2018-02-11 | 2021-11-19 | 中国移动通信有限公司研究院 | 信息交互方法、设备及计算机可读存储介质 |
CN110166503A (zh) * | 2018-02-11 | 2019-08-23 | 中国移动通信有限公司研究院 | 信息交互方法、设备及计算机可读存储介质 |
US11451624B2 (en) | 2018-11-27 | 2022-09-20 | At&T Intellectual Property I, L.P. | Virtual network manager system |
US10880370B2 (en) | 2018-11-27 | 2020-12-29 | At&T Intellectual Property I, L.P. | Virtual network manager system |
CN111443984A (zh) * | 2019-01-17 | 2020-07-24 | 中国移动通信有限公司研究院 | 网络功能虚拟化nvf系统的容器部署方法及装置 |
CN111443984B (zh) * | 2019-01-17 | 2023-03-31 | 中国移动通信有限公司研究院 | 网络功能虚拟化nvf系统的容器部署方法及装置 |
CN111835685A (zh) * | 2019-04-19 | 2020-10-27 | 厦门网宿有限公司 | 一种监控Nginx网络隔离空间的运行状态的方法和服务器 |
CN111835684A (zh) * | 2019-04-19 | 2020-10-27 | 厦门网宿有限公司 | 一种haproxy设备的网络隔离监控方法及系统 |
CN111953503A (zh) * | 2019-05-14 | 2020-11-17 | 中国电信股份有限公司 | Nfv资源部署编排方法和网络功能虚拟化编排器 |
CN111953503B (zh) * | 2019-05-14 | 2023-04-07 | 中国电信股份有限公司 | Nfv资源部署编排方法和网络功能虚拟化编排器 |
US11588675B2 (en) | 2019-06-25 | 2023-02-21 | Vmware, Inc. | Systems and methods for selectively implementing services on virtual machines and containers |
WO2020263874A1 (en) * | 2019-06-25 | 2020-12-30 | Vmware, Inc. | Systems and methods for selectively implementing services on virtual machines and containers |
US10931507B2 (en) | 2019-06-25 | 2021-02-23 | Vmware, Inc. | Systems and methods for selectively implementing services on virtual machines and containers |
US12021735B2 (en) | 2019-06-25 | 2024-06-25 | Vmware, Inc. | Systems and methods for implementing multi-part virtual network functions |
US11296975B2 (en) | 2019-06-25 | 2022-04-05 | Vmware, Inc. | Systems and methods for implementing multi-part virtual network functions |
CN111130925A (zh) * | 2019-11-29 | 2020-05-08 | 广州文远知行科技有限公司 | 资源监控方法、装置、计算机设备和存储介质 |
CN111130925B (zh) * | 2019-11-29 | 2022-08-26 | 广州文远知行科技有限公司 | 资源监控方法、装置、计算机设备和存储介质 |
CN111597032A (zh) * | 2020-05-26 | 2020-08-28 | 北京学之途网络科技有限公司 | 任务调度管理方法、装置及电子设备 |
CN111597032B (zh) * | 2020-05-26 | 2024-03-26 | 北京明略昭辉科技有限公司 | 任务调度管理方法、装置及电子设备 |
CN114374609A (zh) * | 2021-12-06 | 2022-04-19 | 东云睿连(武汉)计算技术有限公司 | 基于rdma设备的深度学习作业运行方法及系统 |
CN114374609B (zh) * | 2021-12-06 | 2023-09-15 | 东云睿连(武汉)计算技术有限公司 | 基于rdma设备的深度学习作业运行方法及系统 |
CN114157585A (zh) * | 2021-12-09 | 2022-03-08 | 京东科技信息技术有限公司 | 一种业务资源监测的方法和装置 |
Also Published As
Publication number | Publication date |
---|---|
CN105760214B (zh) | 2019-02-26 |
CN105760214A (zh) | 2016-07-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017181876A1 (zh) | 一种设备状态及资源信息监测方法、相关设备及系统 | |
US11895016B2 (en) | Methods and apparatus to configure and manage network resources for use in network-based computing | |
EP3455728B1 (en) | Orchestrator for a virtual network platform as a service (vnpaas) | |
US10644952B2 (en) | VNF failover method and apparatus | |
US10140112B2 (en) | Update management system and update management method | |
US11307943B2 (en) | Disaster recovery deployment method, apparatus, and system | |
KR102059251B1 (ko) | 노드 시스템, 서버 장치, 스케일링 제어 방법 및 프로그램 | |
WO2018001049A1 (zh) | 一种网络边缘计算的虚拟网络功能部署方法、装置和系统 | |
WO2019238004A1 (zh) | 一种告警的方法及装置 | |
EP3447965B1 (en) | Network function instance management method and relevant device | |
WO2014169870A1 (zh) | 虚拟网元自动装载及虚拟机ip地址获取的方法与系统、存储介质 | |
WO2016206456A1 (zh) | 物理机升级方法、业务迁移方法及装置 | |
US10664303B2 (en) | Network management for elastic virtual network functions | |
US10083098B1 (en) | Network function virtualization (NFV) virtual network function (VNF) crash recovery | |
US20130201875A1 (en) | Distributed fabric management protocol | |
WO2020001409A1 (zh) | 一种虚拟网络功能vnf部署方法及装置 | |
WO2018039973A1 (zh) | 网络功能处理方法及相关设备 | |
CN104158707A (zh) | 一种检测并处理集群脑裂的方法和装置 | |
CN111835685B (zh) | 一种监控Nginx网络隔离空间的运行状态的方法和服务器 | |
JP2015191246A (ja) | 通信システムおよび管理方法 | |
JPWO2018174225A1 (ja) | ネットワーク機能仮想化管理オーケストレーション装置、通信システム、方法及びプログラム | |
EP3972196A1 (en) | Virtual network function (vnf) deployment method and apparatus | |
CN108833613B (zh) | 一种动态主机配置协议的实现方法及系统 | |
CN105591780B (zh) | 集群监测方法和设备 | |
CN110545193B (zh) | 一种虚拟资源的管理方法、虚拟资源管理设备及服务器 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17785361 Country of ref document: EP Kind code of ref document: A1 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 17785361 Country of ref document: EP Kind code of ref document: A1 |