CN110278101B - Resource management method and equipment - Google Patents
Resource management method and equipment Download PDFInfo
- Publication number
- CN110278101B CN110278101B CN201810210015.9A CN201810210015A CN110278101B CN 110278101 B CN110278101 B CN 110278101B CN 201810210015 A CN201810210015 A CN 201810210015A CN 110278101 B CN110278101 B CN 110278101B
- Authority
- CN
- China
- Prior art keywords
- information
- alarm
- identifier
- virtual machine
- hardware
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 20
- 238000000034 method Methods 0.000 claims abstract description 35
- 238000012545 processing Methods 0.000 claims description 24
- OOXMVRVXLWBJKF-DUXPYHPUSA-N n-[3-[(e)-2-(5-nitrofuran-2-yl)ethenyl]-1,2,4-oxadiazol-5-yl]acetamide Chemical compound O1C(NC(=O)C)=NC(\C=C\C=2OC(=CC=2)[N+]([O-])=O)=N1 OOXMVRVXLWBJKF-DUXPYHPUSA-N 0.000 claims 6
- 238000012423 maintenance Methods 0.000 abstract description 13
- 238000004891 communication Methods 0.000 abstract description 3
- 230000015654 memory Effects 0.000 description 18
- 230000006870 function Effects 0.000 description 14
- 238000005516 engineering process Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000010354 integration Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 235000019800 disodium phosphate Nutrition 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a resource management method and equipment, relates to the technical field of communication, and is used for solving the problem that physical resources and virtual resources of infrastructure cannot be uniformly managed in the conventional NFV architecture, so that inconvenience is caused to resource statistics and maintenance work of the infrastructure. The method comprises the following steps: the association relation manager RM acquires physical resource information of each hardware device, virtual resource information of each virtual machine VM and first association information in the NFV architecture, inquires target first association information according to an identification list of a physical host where the virtual machine is deployed, inquires target physical resource information according to a hardware identification in the target first association information, and generates second association information of the target physical resource information and the virtual resource information. The method may be applied to an NFV architecture.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a resource management method and device.
Background
Network Function Virtualization (NFV) Technology refers to a Technology for carrying various software-based Network Functions (NFs) by employing industrial standard servers, memories, and switches, by means of standard Internet Technology (IT) virtualization Technology and conventional proprietary hardware devices.
Currently, a commonly accepted NFV architecture is the NFV architecture defined by the European Telecommunications Standards Institute Network Function virtualization Industry Specification group (ETSI NFV ISG). As shown in fig. 1, the existing NFV architecture includes: a Management and orchestrator (MANO) for managing the traffic in the NFV. The MANO includes a Virtual Network Function Manager (VNFM), a Virtualization Infrastructure Manager (VIM), and a Network Function Virtualization Orchestrator (NFVO). The VNFM is used to manage a lifecycle of a Virtual Network Function (VNF). The VIM is used to manage the Virtual resources of a Network Function Virtualization Infrastructure (NFVI). NFVO is used to manage the lifecycle of web services.
The NFV architecture further includes a Physical Infrastructure Manager (PIM) configured to manage hardware physical resources of the NFVI. An Operation Support System (OSS) or a service Support System (BSS) is used to manage service information in a network. And the VNF is used for collecting the virtual resource information. And an Element Manager (EM) for managing the virtual resource information collected by the VNF, a lifecycle of the VNF, and processing interaction between the VNF and the OSS/BSS.
At present, in an NFV architecture, physical resources and virtual resources of an infrastructure cannot be managed in a unified manner, and further, much inconvenience is caused to resource statistics and maintenance work of the infrastructure.
Disclosure of Invention
The application provides a resource management method and equipment, which are used for solving the problem that physical resources and virtual resources of infrastructure cannot be uniformly managed in an NFV (network function virtualization) framework, and further inconvenience is caused to resource statistics and maintenance work of the infrastructure.
In order to achieve the purpose, the technical scheme is as follows:
in a first aspect, a resource management method is provided, where the method includes: and the association relation manager RM acquires the physical resource information of each hardware device, the virtual resource information of each virtual machine VM and the first association information in the NFV architecture. And the RM queries the target first associated information according to the identification list of the physical host where the virtual machine is deployed. And the RM queries the target physical resource information according to the hardware identifier in the target first correlation information. And the RM generates second associated information of the target physical resource information and the virtual resource information.
In a second aspect, an alarm method is provided, and the method includes that a network function virtualization orchestrator NFVO obtains service alarm information, where the service alarm information includes a service alarm virtual machine identifier and service alarm detailed information. And the NFVO receives third associated information sent by the RM. And the NFVO queries target third associated information according to the service alarm virtual machine identifier. And the alarm virtual machine identifier of the target third associated information is the same as the service alarm virtual machine identifier. And the NFVO positions the fault position according to the hardware detailed information in the physical resource alarm information comparison list in the target third associated information.
In a third aspect, an apparatus is provided, the apparatus comprising: an obtaining module, configured to obtain physical resource information of each hardware device in the NFV architecture, virtual resource information of each virtual machine VM, and first association information. Wherein the physical resource information includes: hardware identification, hardware type, and hardware details. The virtual resource information comprises a virtual machine identifier, an identifier list of a physical host where the virtual machine is deployed, and detailed information of the virtual machine. The first associated information comprises a hardware identifier and a host identifier. And the processing module is used for inquiring the target first associated information according to the identification list of the physical host where the virtual machine is deployed, which is acquired by the acquisition module. Wherein the host identifier included in the target first association information is located in an identifier list of a physical host where the virtual machine is deployed. The processing module is further configured to query the target physical resource information according to the hardware identifier in the target first correlation information. And the target physical resource information comprises a hardware identifier which is the same as the hardware identifier in the target first correlation information. The processing module is further configured to generate second association information of the target physical resource information and the virtual resource information. The second association information includes the virtual machine identifier, the virtual machine detailed information, an identifier list of a physical host where the virtual machine is deployed, and a hardware information list of the physical host where the virtual machine is deployed.
In a fourth aspect, the present application provides an apparatus comprising: a processor, a transceiver, and a memory. Wherein the memory is configured to store one or more programs, the one or more programs including instructions, and the processor is configured to execute the instructions stored in the memory, so as to cause the apparatus to perform the resource management method according to any one of the first aspect and the various optional implementations thereof, or to perform the alarm method according to any one of the second aspect and the various optional implementations thereof.
In a fifth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by an RM, the RM performs the resource management method described in any one of the first aspect and various optional implementations thereof.
The present application further provides another computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by an NFVO, the NFVO executes the data transmission method according to any one of the second aspect and various optional implementation manners of the NFVO.
In a sixth aspect, the present application provides an NFV architecture comprising NFVI, VIM, PIM, the RM described in any of the first aspect and its various alternative implementations, and the NFVO described in any of the second aspect and its various alternative implementations.
In summary, in the resource management method and device provided by the present application, the RM acquires the physical resource information of each hardware device, the virtual resource information of each VM, and the first association information in the NFV architecture, queries the target first association information according to the identifier list of the physical host where the virtual machine is deployed, queries the target physical resource information according to the hardware identifier in the target first association information, and generates the second association information of the target physical resource information and the virtual resource information. Therefore, compared with the prior art, the method and the device have the advantages that the physical resource information and the virtual resource information can be correspondingly combined together according to the identification list of the physical host where the virtual machine is deployed and the hardware identification, and convenience is further provided for statistics integration and operation maintenance of the physical resources and the virtual resources in the infrastructure in the NFV architecture.
Drawings
FIG. 1 is a schematic diagram of an NFV architecture in the prior art;
fig. 2 is a schematic structural diagram of an NFV architecture provided in an embodiment of the present application;
fig. 3 is a flowchart of a resource management method according to an embodiment of the present application;
FIG. 4 is a flowchart of another resource management method according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an apparatus provided in an embodiment of the present application;
fig. 6 is a schematic structural diagram of another apparatus provided in an embodiment of the present application.
Detailed Description
The embodiment of the present application is applicable to an NFV architecture, as shown in fig. 2, on the basis of the NFV architecture shown in fig. 1, an association Relationship Manager (RM) and a cloud resource manager are introduced into the NFV architecture of the present application. Therefore, the NFV architecture of the present application includes MANO, NFVI, OSS/BSS, EM, VNF, PIM, MANO, RM, cloud resource manager, where NFVO, VIM, VNFM are included in MANO. Unlike the prior art, in the embodiment of the present application, the VIM is further configured to send virtual resource information to the RM; PIM is also used to send physical resource information to RM; NFVO is also used to send the first association information to the RM. In the new device introduced by the application, the cloud resource manager is used for managing physical resource information and virtual resource information across resource pools. The RM is configured to generate statistical data of the virtual resource information and the physical resource information corresponding to the hardware identifier and the host identifier one to one according to the virtual resource information including the host identifier, the physical resource information including the hardware identifier, and the correspondence between the hardware identifier and the host identifier, so that the RM or another device performs unified management on the physical resources and the virtual resources in the NFV architecture.
The embodiment of the present application provides a resource management method, which can be applied to the NFV architecture shown in fig. 2. As shown in fig. 3, the method includes the following steps 101 to 104:
step 101, the RM acquires physical resource information of each hardware device, virtual resource information of each VM, and first association information in the NFV architecture.
Optionally, as shown in step 1011 in fig. 3, the RM acquires physical resource information of each hardware device in the NFV architecture from the PIM.
Wherein the physical resource information includes: hardware identification, hardware type, and hardware details.
Optionally, the hardware identifier may be a product serial number of the hardware, and the product serial number is globally unique. Optionally, the hardware detail information may be physical information of the hardware, for example, the hardware detail information may include data of a model, a CPU, a memory, a network, a disk, a location, and the like. Optionally, in this embodiment of the present application, the hardware type may be divided according to the hardware function, for example, the hardware may be divided into different types, such as a general server and a memory, according to the hardware function. Optionally, the physical resource information may be periodically acquired from the PIM by the RM, and a term for periodically acquiring the physical resource information may be set according to a user requirement or experience, where the term is not limited in this application.
Optionally, as shown in step 1012 in fig. 3, the RM acquires virtual resource information of each VM in the NFV architecture from the VIM.
The virtual resource information includes a virtual machine identifier, an identifier list of a physical host where the virtual machine is deployed, and detailed information of the virtual machine.
Optionally, the identifier list of the physical host where the virtual machine is deployed may be a host identifier list formed by unique host identifiers generated for each hardware in the resource pool when the VIM implements hardware installation and discovery operations. Optionally, the virtual machine identifier may be a unique virtual machine identifier generated by the VIM for the virtual machine when the virtual machine is created. Optionally, the detailed information of the virtual machine may include information such as specification of the virtual machine, CPU, memory, network, disk, affinity, and NUMA. Optionally, the virtual resource information may be periodically acquired by the RM from the VIM, and a term for periodically acquiring the virtual resource information may be set according to user needs or experience.
Optionally, as shown in step 1013 in fig. 3, the RM acquires the first association information from the NFVI.
The first associated information comprises a hardware identifier and a host identifier.
Optionally, the first related information may be periodically acquired by the RM from the NFVI, and a term for periodically acquiring the first related information may be set according to a user requirement or experience, and in the present application, the term is not limited.
Step 102, the RM queries the target first association information according to the identification list of the physical host where the virtual machine is deployed in the virtual resource information acquired in step 1012.
And the host identification contained in the target first association information is positioned in the identification list of the physical host where the virtual machine is deployed.
It should be noted that, after the RM acquires the first association information, the physical resource information, and the virtual resource information, whether the physical resource information and the virtual resource information are queried according to the first association information, or the first association information is queried according to the physical resource information, and then the virtual resource information is queried according to the first association information, the identifier list of the physical host where the virtual machine is deployed needs to be queried according to the host identifier in the first association information. In the process of querying, the first host identifier needs to be queried to the host identifier in the first association information, and therefore, a lot of time is wasted. Therefore, in the present application, usually, a plurality of target first association information are queried according to the identifier list of the physical host where the virtual machine is deployed in the virtual resource information obtained in step 1012, and then the target physical resource information is queried according to the hardware identifier in the plurality of target first association information.
Step 103, the RM queries the target physical resource information according to the hardware identifier in the target first correlation information.
And the hardware identifier contained in the target physical resource information is the same as the hardware identifier in the target first associated information.
And 104, generating second associated information of the target physical resource information and the virtual resource information by the RM.
The second associated information includes a virtual machine identifier, virtual machine detailed information, an identifier list of a physical host where the virtual machine is deployed, and a hardware information list of the physical host where the virtual machine is deployed.
For a more clear description of the method shown in fig. 3, the following description is given with reference to specific examples: assume that in the NFV architecture, there are two pieces of hardware a and C. Two virtual machines A1 and A2 run on the hardware A, the virtual machine A1 is deployed in a host B11-B15, and the virtual machine A2 is deployed in a host B21-B25. Two virtual machines C1 and C2 run on the hardware C, a virtual machine C1 is deployed in the hosts D11-D15, and a virtual machine C2 is deployed in the hosts D21-D25. The resource management method as shown in fig. 3 can be implemented as the following embodiments:
first, the RM acquires the physical resource information of the hardware A, C from the PIM, the virtual resource information of the virtual machines a1, a2, C1 and C2 from the VIM, and the corresponding relations (first association information) between the hardware A, C and the hosts B11-B15, B21-B25, D11-D15 and D21-D25.
Then, the RM queries the corresponding target first association information according to the identification lists B11-B15, B21-B25, D11-D15 and D21-D25 of the physical host where the virtual machine is deployed in the virtual resource information. For example, the RM finds the target first association information (A, B11) according to the identifier list B11-B15, finds the physical resource information corresponding to the hardware a according to the target first association information (A, B11), then reserves the virtual machine identifier, the virtual machine detailed information, and the identifier list of the physical host where the virtual machine is deployed (B11-B15) of the virtual machine B1, compresses the physical resource information corresponding to the hardware a into the hardware information list of the physical host where the virtual machine is deployed, and further generates the virtual resource information corresponding to the virtual machine B1 and the second association information of the physical resource information corresponding to the hardware a. The physical resource information in the hardware information list of the physical host where the virtual machine is deployed corresponds to the host identifier in the identifier list of the physical host where the virtual machine is deployed, for example, the physical host B11 may correspond to the physical resource information corresponding to the hardware a.
Optionally, after the RM generates second association information of the target physical resource information and the virtual resource information, the RM may further send the physical resource information, the virtual resource information, and the second association information to the cloud resource manager, so that the cloud resource manager may uniformly manage the physical resource information of each hardware in the cross-resource pool and the virtual resource information of the virtual machine running on each hardware, so that the cloud resource manager may perform classification statistics on the physical resource information and the virtual resource information in the cross-resource pool, and the physical resource information and the virtual resource information in the multiple resource pools may be presented on the same interface, which is beneficial for a technician to research on the physical resource information and the virtual resource information in the cross-resource pool.
In order to accurately position the fault position for later maintenance when a fault occurs in the network, the RM acquires the physical resource alarm information of each hardware device and the virtual resource alarm information of each VM in the NFV architecture after generating the second correlation information of the target physical resource information and the target virtual resource information, and generates the correlation information of the physical resource alarm information and the virtual resource alarm information. Specific implementations of this step can be found in the detailed description below.
In summary, in the resource management method and device provided by the present application, the RM acquires the physical resource information of each hardware device, the virtual resource information of each VM, and the first association information in the NFV architecture, queries the target first association information according to the identifier list of the physical host where the virtual machine is deployed, queries the target physical resource information according to the hardware identifier in the target first association information, and generates the second association information of the target physical resource information and the virtual resource information. Therefore, compared with the prior art, the method and the device have the advantages that the physical resource information and the virtual resource information can be correspondingly combined together according to the identification list of the physical host where the virtual machine is deployed and the hardware identification, and convenience is further provided for statistics integration and operation maintenance of the physical resources and the virtual resources in the infrastructure in the NFV architecture.
As shown in fig. 3, after the RM performs step 104 to generate the second association information of the target physical resource information and the virtual resource information, steps 201 to 206 may be further performed:
step 201, the RM acquires physical resource alarm information of each hardware device and virtual resource alarm information of each VM in the NFV architecture.
Optionally, as shown in step 2011 in fig. 4, the RM acquires, from the PIM, physical resource alarm information of each hardware device in the NFV architecture.
The physical resource alarm information comprises an alarm hardware identifier, physical alarm detailed information and an alarm hardware type.
Optionally, the physical alarm detailed information may include a physical resource alarm number, a physical resource alarm category, a physical resource alarm name, a physical resource alarm description, and the like. Optionally, the physical resource warning information may be obtained by the RM in real time from the PIM, so that the RM can quickly locate the fault location.
Optionally, as shown in step 2012 in fig. 4, the RM acquires virtual resource alarm information of each VM in the NFV architecture from the VIM.
The virtual resource alarm information comprises an alarm virtual machine identifier, virtual machine alarm detailed information and an identifier list of a physical host involved in alarm.
Optionally, the virtual resource alarm information may include a virtual resource alarm number, a virtual resource alarm category, a virtual resource alarm name, a virtual resource alarm description, and the like. Optionally, the virtual resource warning information may be acquired by the RM in real time from the VIM, so as to facilitate later maintenance of the virtual machine by the RM.
In step 202, the RM queries the target second association information according to the identifier list of the physical host related to the alarm in the virtual resource alarm information acquired in step 201.
And the identification list of the physical host where the virtual machine is deployed in the target second correlation information comprises the identification list of the physical host involved in the alarm.
Optionally, after the RM generates the second association information of the target physical resource information and the virtual resource information, the method for obtaining the third association information may further include:
the RM acquires physical resource alarm information of each hardware device and virtual resource alarm information of each VM in the NFV architecture, inquires target second associated information according to an identification list of a physical host related to the alarm, inquires a hardware identification of hardware corresponding to the identification list of the physical host related to the alarm according to a one-to-one correspondence relationship between the identification list of the physical host where the virtual machine is deployed in the target second associated information and a hardware information list of the physical host where the virtual machine is deployed, then inquires the target physical resource alarm information corresponding to the hardware identification according to the hardware identification, and generates third associated information of the target physical resource alarm information and the virtual resource alarm information.
When the RM queries the target physical resource alarm information through the target second association information, the identifier list of the physical host where the virtual machine is deployed may include a large number of identifiers of physical hosts that do not involve an alarm, but in this case, the RM may only query the physical host identifiers in sequence, and therefore the RM may need to traverse a plurality of physical host identifiers that do not involve an alarm to find the physical host identifiers that involve an alarm, which wastes a large amount of time. Therefore, in the present application, the RM generally adopts the implementation manner shown in step 201 and 204 when obtaining the third related information.
Step 203, the RM queries and specifies the first association information according to the identification list of the physical host involved in the alarm.
Wherein, the host identity contained in the first association information is appointed to be positioned in a physical host identity list related to the alarm.
Step 204, the RM queries the alarm information of the appointed physical resource according to the appointed first associated information.
And the alarm hardware identifier contained in the specified physical resource alarm information is the same as the hardware identifier in the specified first associated information.
Step 205, the RM generates third associated information that specifies the physical resource alarm information and the virtual resource alarm information.
The third associated information comprises an alarm virtual machine identifier, virtual machine alarm detailed information, an identifier list of a physical host involved in alarm and a physical resource alarm information comparison list. The physical resource alarm information comparison list comprises alarm hardware identification, physical alarm detailed information, alarm hardware type and hardware detailed information.
Optionally, the RM sends the third association information to the NFVO.
For a more clear description of the method shown in fig. 4, the following description is given with reference to specific examples as follows: assume that in the NFV architecture, there are two pieces of hardware a and C. Two virtual machines A1 and A2 run on the hardware A, the virtual machine A1 is deployed in a host B11-B15, and the virtual machine A2 is deployed in a host B21-B25. Two virtual machines C1 and C2 run on the hardware C, the virtual machine C1 is deployed in the hosts D11-D15, the virtual machine C2 is deployed in the hosts D21-D25, the virtual machines related to the alarm are C1 and C2, and the hosts related to the alarm are D11-D13 and D21-D23. The alarm method as shown in fig. 4 can be implemented as the following embodiments:
first, the RM obtains physical alarm resource information of hardware A, C from the PIM, obtains virtual resource alarm information of virtual machines a1, a2, C1, and C2 from the VIM, and obtains the corresponding relations (first association information) between hardware A, C and host computers B11-B15, B21-B25, D11-D15, and D21-D25.
Then, the RM queries target second associated information according to the identification lists D11-D13 and D21-D23 of the physical hosts involved in the alarm in the virtual resource alarm information, wherein the identification list of the physical host where the virtual machine is deployed in the target second associated information contains the identification list of the physical host involved in the alarm. Obviously, the target second correlation information found here is the second correlation information corresponding to D21-D25, D11-D15. The RM specifies first association information, e.g., first association information, according to the ID lists D11-D13, D21-D23 query of the physical hosts involved in the alarm (C, D21). Then, the RM queries the specified physical resource alarm information according to the specified first association information, where a hardware identifier of the specified physical resource alarm information is the same as a hardware identifier of the specified first association information, for example, the physical resource alarm information corresponding to the hardware C. Then, the RM reserves the virtual machine identifier, the virtual resource detailed information, the virtual machine list related to the alarm in the virtual resource alarm information, the hardware information list of the physical host where the virtual machine is deployed in the target second associated information, and the physical alarm detailed information in the physical resource alarm information, compresses the physical alarm detailed information and the hardware information list of the physical host where the virtual machine is deployed into a physical resource alarm information comparison list, and further generates third associated information. For example, if the physical resource alarm information corresponding to the hardware C and the virtual resource alarm information corresponding to the host identifiers D11-D15 generate the third association information, the generated third association information includes the virtual machine identifiers, the virtual resource detail information, the list of virtual machines related to the alarm, the physical alarm detail information corresponding to the hardware C, the hardware detail information of the hardware corresponding to the host identifiers D11-D15, the alarm hardware identifiers, and the alarm hardware types in the virtual resource alarm information corresponding to the host identifiers D11-D15.
It should be noted that, in the embodiment of the present application, the execution order of step 202 and step 203 is not limited. Wherein, step 203 may be executed first, and then step 202 may be executed; or step 202 is executed first, and then step 203 is executed; or step 202 and step 203 may be performed simultaneously.
Optionally, in order to facilitate a maintenance person to maintain the hardware fault on the network, after the RM sends the third relevant information to the NFVO, the NFVO may locate the fault location, and the fault locating method may include:
and the NFVO acquires service alarm information. The service alarm information comprises service alarm virtual machine identification and service alarm detailed information. Optionally, the detailed information of the service alarm includes a service alarm number, a service alarm category, a service alarm name, a service alarm description, and the like. Optionally, the NFVO acquires the service alarm information from an operation support system.
The NFVO receives the third association information sent by the RM.
And the NFVO queries the third association information of the target according to the service alarm virtual machine identifier. And the alarm virtual machine identifier of the target third associated information is the same as the service alarm virtual machine identifier.
And the NFVO positions the fault position according to the hardware detailed information in the physical resource alarm information comparison list in the target third associated information.
Optionally, when hardware in the NFV architecture fails, the NFVO may locate a fault location, and the fault locating method may further include:
NFVO obtains service alarm information, second correlation information, virtual resource alarm information and physical resource alarm information, inquires the second correlation information according to the service alarm virtual machine identifier of the service alarm information, inquires the physical resource alarm information according to the second correlation information, positions the fault hardware according to the hardware detail information in the second correlation information, and finally, maintenance personnel maintain the fault hardware according to the physical resource alarm detail information of the physical resource alarm information and the service alarm detail information of the service alarm information.
And the service alarm virtual machine identifier is the same as the virtual machine identifier of the second associated information. The hardware identifier of the hardware information list of the physical host where the virtual machine is deployed in the second associated information is the same as the hardware identifier of the physical resource alarm information.
In the NFV architecture, there are three types of failures that occur: physical layer faults, virtual layer faults, business layer faults. Therefore, there are three types of alarms covered in the service alarm information: physical layer alarm, virtual layer alarm and service layer alarm. Because the virtual machine runs on hardware, when the physical layer fails, the data of the virtual layer inevitably changes along with the failure, and therefore, as long as the physical layer gives an alarm, the virtual layer inevitably gives an alarm. If the physical layer and the virtual layer do not have alarms simultaneously and the NFVO can still receive the service alarm information, it indicates that the alarm described by the service alarm information is an alarm of the virtual layer or/and an alarm of the service layer, and if the virtual layer and the physical layer do not have alarms and the NFVO can still receive the service alarm information, it indicates that the alarm is an alarm of the service layer.
In order to ascertain the level of an alarm occurring in the NFV framework and respectively maintain faults occurring in different levels, optionally, the NFVO receives second association information and virtual resource alarm information sent by the RM, and a specific implementation manner of the alarm level ascertaining method is as follows:
and after the NFVO receives the third association information sent by the RM, the NFVO queries the target third association information according to the service alarm virtual machine identifier. If the third target association information can be inquired, the NFVO positions the fault position according to the hardware detailed information in the physical resource alarm information comparison list in the third target association information, and maintains the fault hardware according to the service alarm detailed information and the physical resource alarm detailed information in the physical resource alarm information comparison list.
And if the NFVO cannot inquire the target third associated information but can still receive the service alarm information, inquiring the virtual resource alarm information according to the service alarm virtual machine identifier, and if the NFVO can inquire the virtual resource alarm information, inquiring the second associated information according to the service alarm virtual machine identifier, finding a fault problem according to the detailed service alarm information, and restarting or debugging the virtual machine to maintain the fault. The virtual machine identifier of the virtual resource alarm information is the same as the service alarm virtual machine identifier, and the virtual machine identifier in the second associated information is the same as the service alarm virtual machine identifier.
If the NFVO cannot inquire the target third associated information and the virtual resource alarm information, but the NFVO can still receive the service alarm information, the NFVO presents the service alarm detailed information of the service alarm information to a human-computer interface so as to facilitate maintenance personnel to carry out maintenance work.
In summary, in the resource management method and device provided by the present application, the RM obtains the physical resource alarm information of each hardware device and the virtual resource alarm information of each VM in the NFV architecture. And then, the RM inquires the second associated information of the target according to the identification list of the physical host related to the alarm, inquires the appointed first associated information according to the identification list of the physical host related to the alarm, inquires the alarm information of the appointed physical resource according to the appointed first associated information, and generates third associated information of the alarm information of the appointed physical resource and the alarm information of the virtual resource. The third correlation information includes information of the physical resource included in the target second correlation information, and the information of the physical resource includes a hardware position. Finally, the RM sends the third association information to the NFVO. Therefore, when a hardware fault occurs in the network, the NFV framework can position the specific position of the fault hardware, so as to perform later maintenance on the fault hardware.
The present application provides an apparatus 30 that may be used to perform the method steps shown in any of the above-mentioned fig. 3 and 4, as shown in fig. 5, the apparatus 30 comprising:
the obtaining module 31 is configured to obtain physical resource information of each hardware device in the NFV architecture, virtual resource information of each virtual machine VM, and first association information. Wherein the physical resource information includes: hardware identification, hardware type, and hardware details. The virtual resource information includes a virtual machine identifier, an identifier list of a physical host where the virtual machine is deployed, and detailed information of the virtual machine. The first association information includes a hardware identification and a host identification.
The processing module 32 is configured to query the target first association information according to the identification list of the physical host deployed by the virtual machine, acquired by the acquisition module 31. And the host identification contained in the target first association information is positioned in the identification list of the physical host where the virtual machine is deployed.
The processing module 32 is further configured to query the target physical resource information according to the hardware identifier in the target first correlation information. And the hardware identifier contained in the target physical resource information is the same as the hardware identifier in the target first associated information.
The processing module 32 is further configured to generate second association information of the target physical resource information and the virtual resource information. The second associated information includes a virtual machine identifier, virtual machine detailed information, an identifier list of a physical host where the virtual machine is deployed, and a hardware information list of the physical host where the virtual machine is deployed.
In a possible design of the present application, the apparatus 30 further includes a sending module 33, where the sending module 33 is configured to send the physical resource information, the virtual resource information, and the second association information to a cloud resource manager.
In one possible design of the present application, the apparatus 30 includes:
the obtaining module 31 is further configured to obtain physical resource alarm information of each hardware device in the NFV architecture and virtual resource alarm information of each VM. The virtual resource alarm information comprises an alarm virtual machine identifier, virtual machine alarm detailed information and an identifier list of a physical host related to the alarm. The physical resource alarm information comprises alarm hardware identification, physical alarm detailed information and alarm hardware type.
The processing module 32 is further configured to query the target second association information according to the identification list of the physical host related to the alarm, acquired by the acquiring module 31. And the identification list of the physical host where the virtual machine is deployed in the target second correlation information comprises the identification list of the physical host involved in the alarm.
The processing module 32 is further configured to query and specify the first association information according to the identifier list of the physical host related to the alarm acquired by the acquiring module. Wherein, the host identity contained in the first association information is appointed to be positioned in a physical host identity list related to the alarm.
The processing module 32 is further configured to query the specified physical resource alarm information according to the specified first association information. And the alarm hardware identifier contained in the specified physical resource alarm information is the same as the hardware identifier in the specified first associated information.
The processing module 32 is further configured to generate third associated information that specifies the physical resource alarm information and the virtual resource alarm information. The third associated information comprises an alarm virtual machine identifier, virtual machine alarm detailed information, an identifier list of a physical host involved in alarm and a physical resource alarm information comparison list, wherein the physical resource alarm information comparison list comprises an alarm hardware identifier, physical alarm detailed information, an alarm hardware type and hardware detailed information.
In one possible design of the present application, the sending module 33 is further configured to:
and sending the third associated information to the NFVO.
In one possible design of the present application, the apparatus 30 includes:
the obtaining module 31 is further configured to obtain service alarm information. The service alarm information comprises service alarm virtual machine identification and service alarm detailed information.
The obtaining module 31 is further configured to receive third association information sent by the RM. The third associated information comprises an alarm virtual machine identifier, virtual machine alarm detailed information, an identifier list of a physical host involved in alarm and a physical resource alarm information comparison list.
The processing module 32 is further configured to query the target third association information according to the service alarm virtual machine identifier obtained by the obtaining module 31. And the alarm virtual machine identifier of the target third associated information is the same as the service alarm virtual machine identifier.
The processing module 32 is further configured to locate the fault location according to the hardware detailed information in the physical resource alarm information comparison list in the target third relevant information.
The device 30 may further comprise a storage module 34, the storage module 34 being adapted to store program codes and data of the device.
In summary, in the resource management method and device provided by the present application, the RM acquires the physical resource information of each hardware device, the virtual resource information of each VM, and the first association information in the NFV architecture, queries the target first association information according to the identifier list of the physical host where the virtual machine is deployed, queries the target physical resource information according to the hardware identifier in the target first association information, and generates the second association information of the target physical resource information and the virtual resource information. Therefore, compared with the prior art, the method and the device have the advantages that the physical resource information and the virtual resource information can be correspondingly combined together according to the identification list of the physical host where the virtual machine is deployed and the hardware identification, and convenience is further provided for statistics integration and operation maintenance of the physical resources and the virtual resources in the infrastructure in the NFV architecture.
As shown in fig. 6, the processing module 32 may be a processor 42 or controller in a device 40, which may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure. The processor or controller may be a central processing unit, general purpose processor, digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others.
The obtaining module 31 and the sending module 33 may be transceivers, transceiver circuits, or a communication interface 41 in the device 40.
The storage module 34 may be a memory 43 or the like in the device 40, which may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, a hard disk, or a solid state disk; the memory may also comprise a combination of memories of the kind described above.
The device 40 also includes a bus 44, which bus 44 may be an Extended Industry Standard Architecture (EISA) bus or the like. The bus 44 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.
Through the description of the above embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above functions may be distributed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the above-described system, device and unit, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.
The embodiment of the present application further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer executes the instructions, the computer executes the steps of the resource management method and the alarm method in the method flow shown in the foregoing method embodiment.
The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), an optical fiber, a portable Compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In embodiments of the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A resource management method is applied to a Network Function Virtualization (NFV) architecture, wherein the NFV architecture comprises an association Relation Manager (RM), and the method comprises the following steps:
the RM acquires physical resource information of each hardware device in the NFV architecture, virtual resource information of each virtual machine VM and first associated information; wherein the physical resource information includes: hardware identification, hardware type and hardware detailed information; the virtual resource information comprises a virtual machine identifier, an identifier list of a physical host where the virtual machine is deployed and detailed information of the virtual machine; the first associated information comprises a hardware identifier and a host identifier;
the RM queries target first associated information according to the identification list of the physical host where the virtual machine is deployed; the host identifier contained in the target first association information is located in an identifier list of a physical host where the virtual machine is deployed;
the RM queries target physical resource information according to the hardware identifier in the target first correlation information; the hardware identifier contained in the target physical resource information is the same as the hardware identifier in the target first association information;
the RM generates second associated information of the target physical resource information and the virtual resource information; the second association information includes the virtual machine identifier, the virtual machine detailed information, an identifier list of a physical host where the virtual machine is deployed, and a hardware information list of the physical host where the virtual machine is deployed.
2. The method of claim 1, wherein after the RM generates second association information for the target physical resource information and the virtual resource information, the method further comprises:
and the RM sends the physical resource information, the virtual resource information and the second correlation information to a cloud resource manager.
3. The method according to claim 1, wherein after the RM generates the second association information of the target physical resource information and the target virtual resource information, the method further comprises:
the RM acquires physical resource alarm information of each hardware device and virtual resource alarm information of each VM in the NFV architecture; the virtual resource alarm information comprises an alarm virtual machine identifier, virtual machine alarm detailed information and an identifier list of a physical host related to alarm; the physical resource alarm information comprises an alarm hardware identifier, physical alarm detailed information and an alarm hardware type;
the RM inquires second target associated information according to the identification list of the physical host related to the alarm; wherein, the identification list of the physical host where the virtual machine is deployed in the target second correlation information includes the identification list of the physical host related to the alarm;
the RM inquires and specifies first associated information according to the identification list of the physical host related to the alarm; wherein the host identifier included in the specified first association information is located in a physical host identifier list related to the alarm;
the RM inquires the alarm information of the appointed physical resource according to the appointed first association information; wherein, the alarm hardware identifier contained in the alarm information of the specified physical resource is the same as the hardware identifier in the specified first associated information;
the RM generates third associated information of the designated physical resource alarm information and the virtual resource alarm information; the third associated information includes the warning virtual machine identifier, virtual machine warning detailed information, an identifier list of a physical host related to the warning, and a physical resource warning information comparison list, where the physical resource warning information comparison list includes the warning hardware identifier, the physical warning detailed information, the warning hardware type, and the hardware detailed information.
4. The method according to claim 3, wherein after said RM generating third association information of said designated physical resource alarm information and said virtual resource alarm information, said method further comprises:
and the RM sends the third association information to the NFVO.
5. An alarm method is applied to a Network Function Virtualization (NFV) architecture, wherein the NFV architecture comprises an association manager (RM), and the method comprises the following steps:
a network function virtualization orchestrator NFVO acquires service alarm information, wherein the service alarm information comprises a service alarm virtual machine identifier and service alarm detailed information;
the NFVO receives third association information sent by the RM; the third associated information comprises an alarm virtual machine identifier, virtual machine alarm detailed information, an identifier list of a physical host involved in alarm and a physical resource alarm information comparison list;
the NFVO queries target third associated information according to the service alarm virtual machine identifier; wherein, the alarm virtual machine identifier of the target third associated information is the same as the service alarm virtual machine identifier;
and the NFVO positions the fault position according to the hardware detailed information in the physical resource alarm information comparison list in the target third associated information.
6. An apparatus, applied to a Network Function Virtualization (NFV) architecture including an association manager (RM), the apparatus comprising:
an obtaining module, configured to obtain physical resource information of each hardware device in the NFV architecture, virtual resource information of each virtual machine VM, and first association information; wherein the physical resource information includes: hardware identification, hardware type and hardware detailed information; the virtual resource information comprises a virtual machine identifier, an identifier list of a physical host where the virtual machine is deployed and detailed information of the virtual machine; the first associated information comprises a hardware identifier and a host identifier;
the processing module is used for inquiring target first associated information according to the identification list of the physical host where the virtual machine is deployed, which is acquired by the acquisition module; the host identifier contained in the target first association information is located in an identifier list of a physical host where the virtual machine is deployed;
the processing module is further configured to query target physical resource information according to the hardware identifier in the target first correlation information; the hardware identifier contained in the target physical resource information is the same as the hardware identifier in the target first association information;
the processing module is further configured to generate second association information of the target physical resource information and the virtual resource information; the second association information includes the virtual machine identifier, the virtual machine detailed information, an identifier list of a physical host where the virtual machine is deployed, and a hardware information list of the physical host where the virtual machine is deployed.
7. The apparatus of claim 6, wherein the apparatus further comprises:
a sending module, configured to send the physical resource information, the virtual resource information, and the second association information to a cloud resource manager.
8. The apparatus of claim 6, wherein the apparatus comprises:
the acquiring module is further configured to acquire physical resource alarm information of each hardware device and virtual resource alarm information of each VM in the NFV architecture; the virtual resource alarm information comprises an alarm virtual machine identifier, virtual machine alarm detailed information and an identifier list of a physical host involved in alarm; the physical resource alarm information comprises an alarm hardware identifier, physical alarm detailed information and an alarm hardware type;
the processing module is further configured to query second target association information according to the identifier list of the physical host related to the alarm, which is acquired by the acquisition module; wherein, the identification list of the physical host where the virtual machine is deployed in the target second correlation information includes the identification list of the physical host related to the alarm;
the processing module is further configured to query and specify first associated information according to the identifier list of the physical host related to the alarm, which is acquired by the acquisition module; wherein the host identifier included in the specified first association information is located in a physical host identifier list related to the alarm;
the processing module is further used for inquiring the alarm information of the specified physical resource according to the specified first associated information; wherein, the alarm hardware identifier contained in the alarm information of the specified physical resource is the same as the hardware identifier in the specified first associated information;
the processing module is further configured to generate third association information of the designated physical resource alarm information and the virtual resource alarm information; the third associated information includes the warning virtual machine identifier, virtual machine warning detailed information, an identifier list of a physical host related to the warning, and a physical resource warning information comparison list, where the physical resource warning information comparison list includes the warning hardware identifier, the physical warning detailed information, the warning hardware type, and the hardware detailed information.
9. The device of claim 6, wherein the sending module is further configured to:
and sending the third associated information to the NFVO.
10. An apparatus, applied to a Network Function Virtualization (NFV) architecture including an association manager (RM), the apparatus comprising:
the acquisition module is further used for acquiring service alarm information, wherein the service alarm information comprises a service alarm virtual machine identifier and service alarm detailed information;
the acquisition module is further configured to receive third association information sent by the RM; the third associated information comprises an alarm virtual machine identifier, virtual machine alarm detailed information, an identifier list of a physical host involved in alarm and a physical resource alarm information comparison list;
the processing module is further used for inquiring target third associated information according to the service alarm virtual machine identifier acquired by the acquisition module; wherein, the alarm virtual machine identifier of the target third associated information is the same as the service alarm virtual machine identifier;
and the processing module is further used for positioning the fault position according to the hardware detailed information in the physical resource alarm information comparison list in the target third associated information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810210015.9A CN110278101B (en) | 2018-03-14 | 2018-03-14 | Resource management method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810210015.9A CN110278101B (en) | 2018-03-14 | 2018-03-14 | Resource management method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110278101A CN110278101A (en) | 2019-09-24 |
| CN110278101B true CN110278101B (en) | 2022-02-18 |
Family
ID=67958405
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810210015.9A Active CN110278101B (en) | 2018-03-14 | 2018-03-14 | Resource management method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110278101B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11563677B1 (en) * | 2018-06-28 | 2023-01-24 | Cable Television Laboratories, Inc. | Systems and methods for secure network management of virtual network function |
| US11822946B2 (en) * | 2018-06-28 | 2023-11-21 | Cable Television Laboratories, Inc. | Systems and methods for secure network management of virtual network functions |
| CN113973047B (en) * | 2020-07-24 | 2024-04-09 | 中移(苏州)软件技术有限公司 | Information display method, device, equipment and storage medium |
| CN114189457A (en) * | 2021-11-11 | 2022-03-15 | 阿里云计算有限公司 | Cloud resource display and processing method, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103620558A (en) * | 2013-05-21 | 2014-03-05 | 华为技术有限公司 | A method for achieving correspondence of physical resource and virtual resource and a basic input output system |
| CN104754013A (en) * | 2013-12-31 | 2015-07-01 | 中国移动通信集团公司 | Cloud computing platform network resource control method, device and system |
| CN105634785A (en) * | 2014-11-07 | 2016-06-01 | 中国移动通信集团公司 | Fault reporting method, system and related device |
| CN106301828A (en) * | 2015-05-21 | 2017-01-04 | 中兴通讯股份有限公司 | A kind of processing method and processing device virtualizing network function traffic failure |
-
2018
- 2018-03-14 CN CN201810210015.9A patent/CN110278101B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103620558A (en) * | 2013-05-21 | 2014-03-05 | 华为技术有限公司 | A method for achieving correspondence of physical resource and virtual resource and a basic input output system |
| CN104754013A (en) * | 2013-12-31 | 2015-07-01 | 中国移动通信集团公司 | Cloud computing platform network resource control method, device and system |
| CN105634785A (en) * | 2014-11-07 | 2016-06-01 | 中国移动通信集团公司 | Fault reporting method, system and related device |
| CN106301828A (en) * | 2015-05-21 | 2017-01-04 | 中兴通讯股份有限公司 | A kind of processing method and processing device virtualizing network function traffic failure |
Non-Patent Citations (1)
| Title |
|---|
| NFV管理体系及其与OSS协同探讨;苗杰等;《邮电设计技术》;20161120(第11期);16-20页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110278101A (en) | 2019-09-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110278101B (en) | Resource management method and equipment | |
| US10700947B2 (en) | Life cycle management method and device for network service | |
| EP3149591B1 (en) | Tracking application deployment errors via cloud logs | |
| EP3281360B1 (en) | Virtualized network function monitoring | |
| US20220247640A1 (en) | Stateless resource management | |
| CN108039964B (en) | Fault processing method, device and system based on network function virtualization | |
| CN105429776B (en) | Method and system for managing functions of virtual network | |
| US10721146B2 (en) | Monitoring for managed services | |
| CN109150572B (en) | Method, device and computer readable storage medium for realizing alarm association | |
| KR102001898B1 (en) | Method of processing alarm information, related devices and systems | |
| CN105653398B (en) | A kind of smart allocation operating system mirror method | |
| EP2838228A1 (en) | Alarm correlation analysis method, apparatus, and system | |
| CN110661647A (en) | Life cycle management method and device | |
| CA2975242A1 (en) | System, virtualization control apparatus, method for controlling a virtualization control apparatus, and program | |
| CN103677858A (en) | Method, system and device for managing virtual machine software in cloud environment | |
| US10083051B1 (en) | System, method, and code for classifying resources of a virtual computing environment | |
| US9256828B2 (en) | Alarm correlation analysis method, apparatus and system | |
| CN104360878A (en) | Method and device for deploying application software | |
| US10735253B2 (en) | Alarm information reporting method and apparatus | |
| CN105119736A (en) | Data check method and device in network function virtualization architecture | |
| CN113037891B (en) | Access method and device for stateful application in edge computing system and electronic equipment | |
| CN111831392A (en) | Hardware acceleration method and related equipment | |
| CN108347465B (en) | Method and device for selecting network data center | |
| CN110868435A (en) | Bare metal server scheduling method and device and storage medium | |
| CN111651235A (en) | Virtual machine set task management method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |