Technical field
[0001]
　(Related description of the application)
　The present invention, Japanese Patent Application: is based on the priority claim of Japanese Patent Application No. 2015-014614 (January 28, 2015 application), all the description of the same application with the quotation It is assumed to be built in this document.
　The present invention is a virtual network function management device, system, a healing method, and a program, particularly to healing function of the virtual network functions that operate on that virtual infrastructure.
Background technique
[0002]
　Server computing, as a technology for virtualizing storage and network functions such as on the server, a virtual machine implemented on virtualization layer such as a hypervisor (Hypervisor): implemented as software by (VM Virtual Machine) NFV (Network Functions Virtualization) and the like are known. For example MANO is realized on the basis of (Management & Orchestration) architecture. Figure 1 is a view taken from Figure 5.1 of page 23 Non-patent Document 1 (The NFV-MANO architectural framework with reference points).
[0003]
　Referring to FIG. 1, VNF (Virtual Network Function) corresponds to the application that operates in a virtual machine on the server (VM), to implement the network functions by software. As VNF, for example LTE (Long Term Evolution) MME in EPC, a core network of a network (Evolved Packet Core) (Mobility Management Entity) or S-GW (Serving Gateway), software P-GW (PDN Gateway) etc. (Virtual it may be realized on the machine). In the example of FIG. 1, EM for example, every VNF: management feature called (Element Manager element management) are provided.
[0004]
　NFVI forming the execution base of VNF (Network Function Virtualization Infrastructure) comprises computing, storage, network functions like a physical machine virtualized computing a virtualization of hardware resources (server) in virtualization layer such as a hypervisor, the virtual storage, a foundation that can be handled flexibly as virtualized hardware resources such as virtual network.
[0005]
　NFV MANO（Management & Orchestration）は、NFV-Orchestrator（NFVO）、VNF-Manager（VNFM）、Virtualized Infrastructure Manager（VIM）を備えている。
[0006]
　NFV-Orchestrator (NFVO) performs NFVI resource orchestration, and NS (Network Service) Lifecycle Management (of NS instance Instantiation, Scaling, Termination, Update, etc.). In addition, NFVO is, NS catalog (NSD / VLD / VNFFGD), and VNF performed a catalog (VNFD / VM image / manifest file, etc.) management of, with the NFV instance repository, NFVI resources of the repository.
[0007]
　VNF-Manager (VNFM) performs life cycle management of VNF (instantiation, update, search, scaling, termination, (Assisted / Auto) healing, etc.) and event notification.
[0008]
　Virtualized Infrastructure Manager (VIM) via the virtualization layer controls NFVI (computing, storage, network resource management, NFVI fault monitoring is performed foundation of NFV, such as monitoring the resource information).
[0009]
　OSS (Operation Service Systems) is, for example, network operators (carriers) to build a service, the system needed to continue to operate (equipment and software, how it works, etc.) is obtained by collectively. BSS (Business Service Systems) is, for example, charging network operators (carriers) such as user fees, billing, is a generic name of information system used for, such as customer support (equipment and software, mechanisms, etc.).
[0010]
　NS catalog (NS catalog) represents the repository of network service (NS). NS catalog (NS catalog), the network service (NS) deployment templates provide support of the generation and management of (Network Service Descriptor (NSD), Virtual Link Descriptor (VLD), VNF Forwarding Graph Descriptor (VNFFGD)). Deployment means to deploy the actual use environment customized according to the requirements and specifications.
[0011]
　VNF catalog (VNF catalog) represents the VNF package repository. VNF catalog, VNF Descriptor (VNFD), software image, and generates and support of the management of VNF packages, such as manifest file.
[0012]
　NFV instance repository (NFV instance Repository) the total VNF, holds the instance information for all network service (NS). VNF instance, NS instance each of VNF, is described in the NS record. These records lifecycle of each instance, VNF lifecycle management operations is updated to reflect the execution result of NS lifecycle management operations.
[0013]
　NFVI resource repository (NFVI Resources Repository) holds extracted by VIM beyond the infrastructure domain of the operator, is available (available) / Book (reserved) / allocated (allocated The) information resources.
[0014]
　In Figure 1, the reference point Os-Nfvo is, OSS (Operation Service Systems) / BSS is a reference point between (Business Service Systems) and NFVO, network service lifecycle management requests, VNF lifecycle management requests, related NFV transfer of status information, used for exchange of the policy management information.
[0015]
　See point VNFM-Vi, the resource allocation request from VNFM, used to exchange configuration and status information of the virtualized resources.
[0016]
　Reference point Ve-Vnfm-em is, EM and, VNF instantiation between VNFM, VNF instance retrieval, update, end, scale-out / in, scale up / down, the configuration from the EM to VNFM, transfer of events, from VNFM the configuration of the VNF to VNF, used in the event of notification, or the like.
[0017]
　Reference point Ve-Vnfm-Vnf is, and VNF, VNF instantiation between VNFM, VNF instance retrieval, update, end, scale-out / in, scale up / down, the configuration from the VNF to VNFM, transfer of events, from VNFM the configuration of the VNF to VNF, used in the event of notification, or the like.
[0018]
　See point Nf-Vi is computing, storage, VM allocation with an indication of the network resource management, VM resource allocation update, VM migration, VM Exit, generation and deletion of the connection between the VM, the virtual to the resource allocation request allocation of resources, the transfer of state information of virtualized resources, used for exchange of information in the configuration and status of the hardware resources.
[0019]
　See point Vn-Nf represents the execution environment provided in VNF by NFVI.
[0020]
　See point Nfvo-Vnfm is, VNF-Manager (VNFM) resource related requests by the (authentication, reservation, allocation, etc.), the transfer configuration information to VNFM, used to collect the state information of VNF.
[0021]
　See point Nfvo-Vi resource reservation from the NVO, used to exchange configuration and status information of the assignment request and virtualized resources. (See Non-Patent Document 1 for details).
CITATION
Non-Patent Document
[0022]
非 特許 文献 1: ETSI GS NFV-Man 001 V1.1.1 (2014-12) Network Functions Virtualisation (NFV); Management and Orchestration
Summary of the Invention
Problems that the Invention is to Solve
[0023]
　The following analysis is given by the present invention. Non-Patent Document 1 of VNF-Manager (VNFM; virtual network function management device), healing as life-cycle management of VNF, generating virtual machine failure (hereinafter, "VM") stops, to create a new VM processing (hereinafter simply referred to as "healing") to implement. Specifically, VNFM uses the VNF catalog (VNF catalog) VDU (Virtual Deployment Unit) element which is held in the VM deployment template called VNFD (VNF Descriptor) in the same configuration as VM failed ( It performs a process to create a VM of the VM name / IP address / MAC address) (see "6.3 Virtualised Network Function information elements" of non-Patent Document 1). It should be noted, may be created as management on a different VM, may be created as the same VM.
[0024]
　However, as shown in FIG. 2, since the overwriting old VM image file during the healing, there is a problem that can not parse the failure content of VM failed. This is a non-patent document 1 Annex I I. Also occur in the specification of the 1 "Open Stack".
[0025]
　The present invention is a virtual network function management apparatus that can contribute to facilitate the analysis of failure content of VM, system, providing healing method, and a program of interest.
Means for Solving the Problems
[0026]
　According to a first aspect, the virtual network function management device including a virtual machine monitor for detecting a failure of the virtual machines running on the virtualization platform management unit for managing the virtual infrastructure is provided. The virtual network function management device, the so failure is feasible backup image file of the virtual machine occurs, the image file of the virtual machine in which the failure occurs after updating logically, the virtualization infrastructure the control unit, and a control unit for instructing the re-creation of virtual machines the problem has occurred.
[0027]
　According to a second aspect, the virtual network function providing system comprising a virtual network function management devices described above are provided.
[0028]
　According to a third aspect, the step of detecting a failure of the virtual machines running on the virtualization platform management unit for managing the virtual infrastructure, when detecting a failure in the virtual machine, the virtual that the problem has occurred backup to allow implementation of machine image file, the image file of the virtual machine in which the failure occurs after updating logically, to the virtualization infrastructure controller, re virtual machines the problem has occurred Healing method comprising the steps of instructing to create, it is provided. The method of virtual network function management apparatus that performs Hirungu virtual machines are tied to a particular machine.
[0029]
　According to a fourth aspect, a program to be executed by a computer functioning as a virtual network function management devices described above are provided. Incidentally, this program may be computer recorded the possible (non-transient of) storage medium read. That is, the present invention can also be embodied as a computer program product.
　Each element of the virtual network function management device, system, virtual machine healing methods and programs, respectively contribute to the resolution of the problems described above.
Effect of the Invention
[0030]
　According to the present invention, it is possible to contribute to facilitation of the analysis of the failure contents of the VM operating on a virtual network function infrastructure (NFVI). Further, the present invention is a virtual network function management apparatus shown in background art, and is also assumed to be converted into virtual network function management system analysis function disorders contents of VM is improved.
BRIEF DESCRIPTION OF THE DRAWINGS
[0031]
FIG. 1 is a diagram illustrating the NFV-MANO of NFV architecture (citing Fig.5.1 Non-Patent Document 1).
Is a diagram for explaining the healing process in FIG. 2] NFV architecture.
3 is a diagram showing a configuration of a virtual network function providing system of the first embodiment of the present invention.
4 is a diagram showing a configuration of a virtual network function management apparatus of the first embodiment of the present invention.
5 is a diagram for explaining the outline of the VM image file managed in the first NFVO NFV instance repository embodiments of the present invention.
6 is a sequence diagram showing the flow of the VM healing process of the first embodiment of the present invention.
7 is a sequence diagram showing the flow (with backup) of VM healing process of the first embodiment of the present invention.
8 is a diagram for explaining a change in the VM image file in the first embodiment of the present invention.
9 is a diagram for explaining a change in the VM image file in the first embodiment of the present invention.
FIG. 10 is a sequence diagram showing the flow of the VM healing process of the second embodiment of the present invention.
11 is a diagram for explaining a change in the VM image file in the second embodiment of the present invention.
12 is a diagram for explaining a change in VM image file in the second embodiment of the present invention.
13 is a sequence diagram showing the VM healing operation of the third embodiment of the present invention.
14 is a diagram showing the flow (with backup) of VM healing process of the third embodiment of the present invention.
DESCRIPTION OF THE INVENTION
[0032]
[First Embodiment]
　Next, a first embodiment of the present invention with reference to the accompanying drawings. Figure 3 is a diagram showing the configuration of a virtual network function providing system of the first embodiment of the present invention.
[0033]
　Referring to FIG. 3, and NFVO100 connected to the maintenance terminal 110, n-number of VNFM for managing VNF to provide a virtualized network functions to the user (the virtual network function management device) and 102a ~ 102n, and execution platform of VNF arrangement of NFVI VIM104 controlling the (network function virtualization infrastructure) 114 is connected are shown.
[0034]
　NFVO100, based on the user instruction received through the maintenance terminal 110, and VNFM102a ~ 102n, controls the VIM104. In addition, NFVO100 is, with respect to the maintenance terminal 110, operations support and billing management of network services, to provide the necessary information to the customer management and the like. Further, NFVO100 (orchestration apparatus) of this embodiment, when receiving the VM stop notification failed from VNFM102a ~ 102n, NFV instance repository held by itself (NFV instance Repository; in FIG. 1 "NFV the Instances" reference ) to update the VM name that is held in.
[0035]
　VNFM102a ~ 102n (hereinafter, when not particularly distinguished VNFM, simply referred to as "VNFM102"), based on an instruction from NFVO100, to manage the lifecycle of VNF112a ~ 112n that runs on the virtualization platform (hereinafter, VNFM and when not particularly distinguished VNF, referred to as "VNFM102", "VNF112"). The details, with reference to FIG. 4 described later.
[0036]
　VIM104 based on an instruction from NFVO100, manages the virtualization infrastructure underlying the VNF112 operates. The VIM, can be used as the non-patent document 1 VIM and equivalent.
[0037]
　Figure 4 is a diagram showing a configuration of VNFM102 the first embodiment of the present invention. Referring to FIG. 4, VNFM102 includes a VM fault detection unit 1021, a control unit 1022, the.
[0038]
　VM fault detection unit 1021, when receiving the failure occurrence notification from VNF112, in order to start a VM healing process, the control unit 1022 requests the issuance of a specific VM in VM stop request for VIM104. As the mechanism of detection of VNF failure in VM failure detection unit 1021 in addition to the method described in Non-Patent Document 1, it is possible to use a health check or the like well known methods.
[0039]
　Control unit 1022, in addition to the issuance of the VM stop request for VIM104, perform VM port deletion / deletion request and for VIM104, the issue of VM creation request.
[0040]
　The control unit 1022, in VIM104, wherein the disorder as is feasible to re-create a virtual machine that has occurred requests the image file of VM that the problem has occurred, to NFVO100 to logically updated. In the present embodiment, the control unit 1022, to NFVO100, requests the rename VM name failed. Instead of the renaming of VM name, or by requiring a process to make a predetermined flag in the management information of the corresponding VM. These are merely examples, while allowing implement backup image file VM that the failure has occurred is not limited as long as it allows the re-creation of the relevant VM. For example, instead of the aforementioned renaming process transitions the appropriate VM to the inactive state (standby state), then re-create the appropriate VM with a different name, finally, also possible to employ processing for replacing the VM name it is.
[0041]
　Figure 5 is a diagram for explaining the outline of the VM image file managed in NFVO100 NFV instance repository of the first embodiment of the present invention. (Referred to as "VM table") left table of FIG. 5 is an image diagram of an information element to store configuration and status of the VM. In the example of FIG. 5, VM of VM name = vm001 includes a virtual NIC (network interface card), the connection information of the virtual port is set. Further, in the example of FIG. 5, VM state of VM name = vm001 indicates that "Start" (middle).
[0042]
　(Referred to as "virtual port table") right table in FIG. 5 is an image diagram of port information stored in NFVI114 side. In the example of FIG. 5, two of the set to the virtual port IP address and MAC address of the virtual NIC of VM name = vm001 is held. In NFVI114 side, the destination and the source of the VM packet is determined at these addresses.
[0043]
　In the following description, with respect to VM name "vm001", "- bk" by adding, to change the VM name using a predetermined rule, such as "vm001-bk". As the predetermined rule may be any existing VM name conflicts that do occur, it is not particularly limited. For example, the update date in the file name, or add the updated date and time (for example, "VM001-20150101"), replace the part of the character of the VM name on a predetermined reserved characters (for example, change the "VM001" to "BK001" ) may be the one.
[0044]
　Next, the operation of this embodiment will be described in detail with reference to the accompanying drawings. Figure 6 is a sequence diagram showing the flow of the VM healing process of the first embodiment of the present invention. Referring to FIG 6, first, when receiving the failure occurrence notification from VNF112, VNFM102, compared VIM104, it requests the stop of the VM corresponding to the VNF failed (in FIG. 6, "VM stop request").
[0045]
　VIM104 receives the VM stop request from VNFM102, for NFVI114, to instruct the stop of the VM ( "Shutdown virtual machine" in FIG. 6).
[0046]
　NFVI114 receives the VM of the stop instruction from VIM104, to stop the appropriate VM (VNF) ( "VM Stop" in FIG. 6). When the VM has stopped completely, NFVI114 inform you that the VM is suspended has been completed for VNFM through VIM104.
[0047]
　Through the VIM104, and to make sure that the VM of the stop has been completed, VNFM102 is, against NFVO100, to request the renaming of the appropriate VM name. NFVO100 refers to the NFV instance repository, to perform the renaming of VM name requested from VNFM102. Incidentally, as described in FIG. 6, rename VM name in NFVO100 will only modify the logical information. As it will be readily appreciated, as compared to performing a full backup of the image file, renaming process ends at high speed.
[0048]
　Upon receiving the notification that the renaming of the VM name has been completed from NFVO100, VNFM102 is, against VIM104, to request the deletion of the virtual port information ( "virtual port deletion request" in FIG. 6).
[0049]
　The VIM104 having received the deletion request of the virtual port information, compared NFVI114, instructing deletion of the specified virtual port information (see right table in FIG. 5) ( "Delete virtual network device" in FIG. 6). NFVI114 Upon deletion of virtual port information is completed, through the VIM104, it notifies that the deletion of virtual port information has been completed for VNFM102.
[0050]
　When the deletion of renaming and the virtual port information of the VM name is completed, recognized as the VM of the same name in NFVO100 absent, the corresponding VM is not present because the virtual port information is not present in NFVI114 (VIM104) side It is. Thereafter, VNFM102, relative VIM104, the creation of virtual port information, and instructs the creation of the VM failed (VM + virtual port creation request of FIG. 6).
[0051]
　VIM104 is the creation of virtual port information from VNFM102, receives the VM creation request failed, to NFVI114, instructs the creation of the creation and VM virtual port information ( "the Create virtual machine of FIG. 6, the Create NW Device ").
[0052]
　Thus, the creation of VM is completed. 7, in FIG. 6 is a sequence diagram in which the additional flow of backup processing VM image file to be executed in parallel with the creation of the VM. Referring to FIG. 7, VNFM102, to the VIM104, requests acquisition of the snapshot image file VM was renamed described above (backup) (Snapshot acquisition request of FIG. 7).
[0053]
　VIM104, upon receiving a snapshot of the acquisition (backup) request of the VM image file from the VNFM102, against NFVI114, to instruct the acquisition of the snapshot (backup image file) by specifying the VM that you rename the above-mentioned ( Create of Figure 7 Snapshot). NFVI114 that received the instruction performs an acquisition of the snapshot of the corresponding VNF112 (backup) (Snapshot generator of FIG. 7). NFVI114 acquires the snapshot is completed through the VIM104, notifying that the acquisition of the snapshot is completed for VNFM102.
[0054]
　Wherein the acquisition of the snapshot is completed, VNFM102, to the VIM104, instructing deletion of the VM that the rename (VM deletion request of FIG. 7).
[0055]
　VIM104 receives the VM deletion request the rename from VNFM102, to NFVI114, instructing deletion of the VM that the rename (7 "Delete virtual machine").
[0056]
　NFVI114 is, the deletion of the VM is completed, to the VNFM102, to notify that the deletion of the VM has been completed.
[0057]
　8, FIG. 9 is a diagram for explaining a change in the VM image file in the sequence described above. As shown in FIG. 8, for example, when the VM to failure of VM name = vm001 occurs, VNFM102, after instructing to stop the VM relative VIM104, relative NFVO100, VM of VM with VM name = vm001 to request to rename the name to "VM001-bk". Furthermore, VNFM102 requests the VIM104, the deletion of the virtual port information corresponding to the virtual port is set to the virtual NIC of VM name = vm001 (see the two tables in the lower part of FIG. 8). With the above processing, as shown on the right side of FIG. 8, an instance of a VM name = vm001 is instead placed vm001-bk, virtual port information is deleted.
[0058]
　And rename to the VM001-bk of VM name = VM001, after the completion of the deletion of the virtual port information, VNFM102, as shown on the left side of FIG. 9, newly created and the image data of the VM name = VM001, a virtual port information to. Thus, as shown in the left lower portion of FIG. 9, a state in which the instances of VM name = vm001, instances of VM name = vm001-bk have coexist. As mentioned above, VM = VM001-bk backup of the image file (snapshot acquisition) can be carried out in parallel with the creation of the image data of the VM name = VM001.
[0059]
　After the completion of the VM = VM001-bk backup of the image file (snapshot acquisition), and VNFM102 to remove an image file of VM = VM001-bk, as the right hand side of FIG. 9, before the VM = VM001 fails it is possible to return to the state.
[0060]
　As described above, according to this embodiment, while realizing high-speed healing, it is possible to also take backup VM image file. In particular, the present embodiment is capable of starting the healing faster as compared to the third embodiment described later. In the present exemplary different embodiment, in synchronization with the healing process, although conducted backup VM image file (snapshot acquisition), the backup of the VM image file (snapshot acquisition) itself, and Healing asynchronously, it is also possible to carry out at any time.
[0061]
Second Embodiment
　Next will be described in detail with reference to the drawings, a second embodiment in which the optional process of deleting the virtual port information in the first embodiment described above. This embodiment is the feasible in the same configuration as the first embodiment, the following, the difference will be mainly described.
[0062]
　Figure 10 is a sequence diagram showing the flow of the VM healing process of the second embodiment of the present invention. Portion shown within a dashed line circle in FIG. 10 is a difference from the first embodiment. As shown in FIG. 10, a failure occurs in the VM, relative VNFM102 is NVFO100, flow until requesting rename VM name is the same as in the first embodiment.
[0063]
　When the rename from NVFO100 of VM name is notified of to be complete, VNFM102, compared VIM104, remove the virtual port information that has been set in the virtual NIC information of the VM image file after rename, virtual port of VM requested by the detach (disconnect) ( "virtual port detach request" in FIG. 10).
[0064]
　Detaching the virtual port VIM104 that received the (disconnection) request, to the NFVI114, instructs the detach of virtual ports of the corresponding VM (disconnection) (in FIG. 10, "Detach virtual port").
[0065]
　11, FIG. 12 is a diagram for explaining a change in the VM image file in the sequence described above. As shown in FIG. 11, for example, when the VM to failure of VM name = vm001 occurs, VNFM102, after instructing to stop the VM relative VIM104, relative NFVO100, VM of VM with VM name = vm001 to request to rename the name to "VM001-bk". Up to this point is the same as in the first embodiment. In the present embodiment, VNFM102 requests the VIM104, the deletion of virtual ports is set to a virtual NIC of VM name = VM001-bk. With the above processing, as shown on the right side of FIG. 11, the instance of the VM name = vm001 is instead placed vm001-bk, virtual connection virtual port information NIC to have been set therein is deleted.
[0066]
　And renamed to vm001-bk of VM name = vm001, after completion of the deletion of the connection virtual port information set to a virtual NIC, VNFM102, as shown on the left side of FIG. 12, a new image of the VM name = vm001 to create the data, the virtual port information. Thus, as shown in the left lower part of FIG. 12, a state in which the instances of VM name = vm001, instances of VM name = vm001-bk have coexist. As described above, in the present embodiment, VM = vm001-bk backup image file (snapshot acquisition) may be performed in parallel with the creation of the image data of the VM name = vm001.
[0067]
　After VM = VM001-bk backup image file (snapshot acquisition) is completed, deleting the image file of VM = VM001-bk, as in the right of FIG. 9, to the state before the VM = vm001 fails it is possible to return.
[0068]
　As described above, also in this embodiment, while realizing high-speed healing, it is possible to also take backup VM image file. In particular, the present embodiment differs from the first embodiment, it can advantageously be omitted deletion and re-creation of virtual port information.
[0069]
[Third Embodiment]
　Subsequently, also the third embodiment is positioned with reference to the drawings in detail, as a comparative example of the first and second embodiments described above. This embodiment also, the first, can be realized by the same configuration as the second embodiment, the following, the difference will be mainly described.
[0070]
　Figure 13 is a sequence diagram showing the flow of the healing process of the third embodiment of the present invention. First, difference from the second embodiment in that the implement after cessation VM failed acquisition of the snapshot of the VM image file that has stopped before the (backup).
[0071]
　Then, when the acquisition of VM snapshots that the stop (backup) is completed, VNFM102, once, delete the VM get that (backup) has been completed of the snapshot, to implement the creation of the VM.
[0072]
　Figure 14 is a diagram showing the flow (with backup) of VM healing process of the third embodiment of the present invention. In the third embodiment, when the failure of the VM is generated (step 001), prior to the acquisition of the snapshot of the VM image file (backup) is performed (step 002).
[0073]
　Then, at the stage of acquisition (backup) has been completed of the snapshot, to delete the VM image file of the VNFM102 has failed (Step003). Then, after the completion of the deletion of the VM image files, VM creation is performed in the VDU image taken from the VDU (Step004).
[0074]
　As described above, also in this embodiment, it is possible to take a backup of the VM image file.
[0075]
　1, 3, component devices and the internal processing means thereof NFV providing system shown in FIG. 4, the computer to configure these devices, by using the hardware, the computer to execute the processes described above It can also be realized by the program.
[0076]
　Having described the embodiments of the present invention, the present invention is not limited to the embodiments described above, without departing from the basic technical concept of the present invention, further modifications, substitutions, and adjustments it can be added. For example, the network configuration shown in the drawings, configurations of components, expressed form of a message is an example to aid in understanding the present invention, it is not limited to the configuration shown in the drawings.
[0077]
　Finally, to summarize the preferred embodiment of the present invention.
First Embodiment
　(see virtual network function management apparatus according to the first aspect)
Second Embodiment
　In a virtual network function management apparatus of the first embodiment,
　for a given orchestration device (NFVO), wherein by failure to request rename the virtual machine name generated, virtual network function management system for updating an image file of the virtual machine in which the failure occurs logically.
[Third Embodiment]
　In the virtual network function management apparatus of the first or second embodiment,
　further, the virtual network function management device carries out a process of disconnecting a virtual port of the virtual machine in which the fault has occurred.
[Fourth Embodiment]
　In the virtual network function management apparatus of the third any one form from the first,
　further, of the virtual port information of the virtualization infrastructure management unit side, an image file of the virtual machine that the failure has occurred virtual network function management device to delete the virtual port information corresponding to the virtual ports included in the.
[Fifth Embodiment]
　In the virtual network function management device of the fourth any one form from the first,
　independently of the rebuild process for the virtual machine, carrying out the backup image file of the virtual machine that the failure has occurred virtual network function management device that.
Sixth Embodiment
　(see virtual network function providing system according to the second aspect)
Seventh Embodiment
　(see healing method according to the third aspect)
Eighth Embodiment
　according (the fourth viewpoint programming reference)
　it should be noted that the form of the sixth to eighth, like the first embodiment, it is possible to develop the second to fifth embodiment.
[0078]
　Incidentally, the disclosures of Non-Patent Document described above, are incorporated by reference herein. Within the bounds of the full disclosure of the present invention (including the claims), and based on the basic technical concept, it is possible to modify and adjustments of embodiments and examples. Also, various combinations of various disclosed elements within the framework of the disclosure of the present invention (each element of each claim, including the elements of the embodiments or examples, each element of each figure), or can be selected it is. That is, the present invention naturally including the entire disclosure, various modifications will be made by those skilled in the art according to the technical concept, modification and in the appended claims. In particular, for the numerical ranges described herein, any numerical or small range comprised within the range should be construed as specifically described, even if otherwise stated.
DESCRIPTION OF SYMBOLS
[0079]
　NFVO 100
　102a ~ 102n VNFM (virtual network function management
　device) 104
　VIM 110 maintenance terminal
　112a ~ 112n VNF (Virtual Network
　Function) 114 NFVI (network function virtualization
　infrastructure) 1021 VM fault detection unit
　1022 control unit
The scope of the claims
[Claim 1]
　A virtual machine monitor for detecting a failure of the virtual machines running on the virtualization platform management unit for managing the virtual infrastructure,
　to allow implementation of the backup image file of the virtual machine that the failure occurs, the fault is the image file generated virtual machine after updating logically, the virtualized with respect to the base control unit, the disorder is a control section for instructing the re-creation of virtual machines that have occurred
　virtual network function management device provided with .
[Claim 2]
　Wherein, for a given orchestration system, by requiring rename the virtual machine name that the problem has occurred, according to claim 1 for updating the image file of the virtual machine that the failure has occurred logically virtual network function management device.
[Claim 3]
　Further, according to claim 1 or 2 virtual network function management device carries out a process of disconnecting a virtual port of the virtual machine in which the fault has occurred.
[Claim 4]
　Further, the one of the virtual port information of virtual infrastructure management side, virtual claims 1 to 3 any one of deleting a virtual port information corresponding to the virtual ports included in the image file of the virtual machine that the failure has occurred network function management device.
[Claim 5]
　Wherein independently of the re-create the virtual machine, the virtual network function management device backup image file claims 1 to implementation of 4 any one of the virtual machines that the problem has occurred.
[Claim 6]
　Virtual network function providing system comprising a virtual network function management device 5 any one of claims 1.
[Claim 7]
　Detecting a failure of the virtual machines running on the virtualization platform management unit for managing the virtual infrastructure,
　implemented when a failure is detected in the virtual machine, the backup image file of the virtual machine in which the failure has occurred as possible, the image file of the virtual machine in which the failure occurs after updating logically, to the virtualization based control unit, a step of instructing the re-creation of the virtual machine in which the failure occurs,
　the healing methods, including.