[go: up one dir, main page]

WO2013114829A1 - Système de traitement d'informations, centre de traitement d'information, procédé de migration de système et programme - Google Patents

Système de traitement d'informations, centre de traitement d'information, procédé de migration de système et programme Download PDF

Info

Publication number
WO2013114829A1
WO2013114829A1 PCT/JP2013/000344 JP2013000344W WO2013114829A1 WO 2013114829 A1 WO2013114829 A1 WO 2013114829A1 JP 2013000344 W JP2013000344 W JP 2013000344W WO 2013114829 A1 WO2013114829 A1 WO 2013114829A1
Authority
WO
WIPO (PCT)
Prior art keywords
data center
virtual
migration
virtual data
construction program
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.)
Ceased
Application number
PCT/JP2013/000344
Other languages
English (en)
Japanese (ja)
Inventor
栄 島村
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Publication of WO2013114829A1 publication Critical patent/WO2013114829A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources

Definitions

  • the present invention relates to an information processing system, a data center, a system migration method, and a program.
  • Patent Document 1 discloses a technology related to system migration using a virtual machine.
  • the management server acquires the resource usage by the virtual server on the physical server, and moves the virtual machine to the physical server that can secure the resource usage.
  • System migration between data centers can be realized by moving all virtual machines on a physical server in a data center to a physical server in another data center using a technique such as that disclosed in Patent Document 1.
  • each system constructed in the migration source data center may be configured by a plurality of virtual machines. is there. Therefore, in order for each system to operate normally, it is necessary to move all virtual machines in the migration source data center to the same migration destination data center.
  • a virtual machine since a virtual machine is moved to a physical server that can ensure actual resource usage, it can be migrated to a data center that is somewhat smaller than the migration source data center.
  • the resource usage rate in the migration source data center is high, a data center having the same scale as the migration source data center is still required as the migration destination of the data center.
  • An object of the present invention is to provide an information processing system, a data center, a system migration method, and a program capable of solving the above-described problems and capable of migrating to a smaller data center in system migration between data centers. Is to provide.
  • An information processing system includes a plurality of data centers in which one or more virtual data centers are constructed, and each of the plurality of data centers includes one or more constituting each of the one or more virtual data centers.
  • a construction program storage unit and a migration destination data center of a migration target virtual data center among the one or more virtual data centers are determined, and a construction program corresponding to the migration target virtual data center is stored in the migration destination data center.
  • transition control means is provided.
  • the data center is a data center in which one or more virtual data centers are constructed, and is one or more that executes processing of one or more virtual machines constituting each of the one or more virtual data centers.
  • a construction program storage means for storing a construction program for constructing the virtual data center on the one or more processing means, corresponding to each of the processing means and the one or more virtual data centers;
  • a migration control means for determining a migration destination data center of a migration target virtual data center in the virtual data center and transmitting a construction program corresponding to the migration target virtual data center to the migration destination data center; .
  • a system migration method is a system migration method between a plurality of data centers in which one or more virtual data centers are constructed, and the data center corresponds to each of the one or more virtual data centers.
  • the migration destination data center of the migration target virtual data center in the virtual data center is determined, and a construction program corresponding to the migration target virtual data center is transmitted to the migration destination data center.
  • a computer-readable recording medium is a recording medium that stores a program for system migration between a plurality of data centers in which one or more virtual data centers are constructed.
  • One or more processing means for executing processing of one or more virtual machines constituting each of the one or more virtual data centers included in the data center corresponding to each of the one or more virtual data centers in a computer included therein A construction program for constructing the virtual data center is stored above, a migration destination data center of the migration target virtual data center of the one or more virtual data centers is determined, and the migration target virtual data center is stored in the migration target virtual data center.
  • a program for executing processing for transmitting a corresponding construction program to the migration destination data center is stored.
  • the effect of the present invention is that the system can be transferred to a smaller data center in the system transfer between the data centers.
  • step S104 It is a flowchart which shows the detail of the data acquisition process (step S104) by the construction program 300 in the 1st Embodiment of this invention. It is a flowchart which shows the detail of the virtual data center construction process (step S202) by the construction program 300 in the 1st Embodiment of this invention. It is a figure which shows the example of the virtual DC resource information 410 in the 1st Embodiment of this invention. It is a figure which shows the example of the network configuration information 420 in the 1st Embodiment of this invention. It is a figure which shows the example of the module structure information 431 in the 1st Embodiment of this invention.
  • FIG. 2 is a block diagram showing the configuration of the information processing system in the first embodiment of the present invention.
  • the information processing system includes a plurality of data centers 100 including one or more computers (not shown) including a CPU (Central Processing Unit) and a storage medium (memory).
  • the reference numeral in parentheses following the reference number indicates an identifier.
  • the data center 100 (DC1) indicates the data center 100 with the identifier DC1.
  • the information processing system includes a data center 100 (DC1 to DC4).
  • the data center 100 includes a migration control unit 110, a construction program storage unit 120, a construction information storage unit 130, a resource management unit 140 (or a virtualization platform), a resource management information storage unit 141, a resource allocation information storage unit 143, one or more The processing device 150, one or more storage devices 160, and one or more network devices 170.
  • the processing device 150 is a part of the one or more computers described above, and includes a basic OS having a communication function, an installation program, and the like.
  • the storage device 160 is a storage device that can be used by the processing device 150, such as a disk array device.
  • the network device 170 is a communication device that can connect the processing devices 150 such as a network switch.
  • One or more virtual data centers 200 that operate independently of each other are constructed on the processing device 150, the storage device 160, and the network device 170 of each data center 100.
  • virtual data centers 200 VDCs 11 to 14 are constructed in the data center 100 (DC1).
  • FIG. 3 is a diagram showing an example of the configuration of the virtual data center 200 in the first embodiment of the present invention.
  • Each virtual data center 200 includes one or more systems 210.
  • Each system 210 includes one or more virtual machines 220.
  • the virtual data center 200 (VDC 11) includes a system 210 (S1 to S3).
  • the system 210 (S1) includes a virtual machine 220 (VM11, 12)
  • the system 210 (S2) includes a virtual machine 220 (VM21, 22)
  • the system 210 (S3) includes a virtual machine 220 (VM31, 32).
  • the system 210 (S1) includes a virtual machine 220 (VM11, 12)
  • the system 210 (S2) includes a virtual machine 220 (VM21, 22)
  • the system 210 (S3) includes a virtual machine 220 (VM31, 32).
  • the virtual machines 220 are connected to each other by a common network 230 in the virtual data center 200 such as a VLAN (Virtual LAN) configured by the network device 170 and a network 240 in the system 210.
  • a VLAN Virtual LAN
  • the virtual machine 220 (VM11, 12, 13) is connected by the network 230 (VL0).
  • the virtual machine 220 (VM11, 12), the virtual machine 220 (VM21, 22), and the virtual machine 220 (VM31, 32) are connected by a network 240 (VL1), a network 240 (VL2), and a network 240 (VL3), respectively.
  • VL1 network 240
  • VL2 network 240
  • VL3 network 240
  • the network 230 and the network 240 are connected to an external network such as the Internet by the gateway 250.
  • the gateway 250 may be, for example, a gateway server in accordance with NAT (Network Address Translation) technology defined by RFC1631.
  • FIG. 4 is a diagram illustrating an example of the configuration of the virtual machine 220 according to the first embodiment of this invention.
  • the virtual machine 220 executes an application module (AP module) that is an application program for providing a service to a user or the like, a related module that is another program used by the AP module, such as a library, and the AP module. It is composed of middleware modules (MW modules), OS modules, and virtual machine modules (VM modules or VM images) that are necessary platform programs.
  • AP module application module
  • MW modules middleware modules
  • OS modules virtual machine modules
  • VM modules or VM images virtual machine modules
  • the construction program storage unit 120 stores a construction program 300 for constructing the virtual data center 200.
  • the construction program 300 is executed on a computer included in the data center 100. Note that the format of the construction program 300 may be a virtual machine image executed on a computer.
  • the construction information storage unit 130 stores construction information 400 related to the virtual data center 200. The construction program 300 and the construction information 400 are stored in correspondence with each virtual data center 200 constructed in the data center 100.
  • the construction program storage unit 120 and the construction information storage unit 130 of the data center 100 are stored in each of the virtual data centers 200 (VDCs 11 to 14) constructed in the data center 100 (DC1).
  • the construction program 300 and the construction information 400 are stored.
  • FIG. 5 is a diagram showing the configuration of the construction program 300 and the construction information 400 in the first embodiment of the present invention.
  • the construction program 300 includes a deployment control unit 310 and a data acquisition unit 380. That is, the construction program 300 causes the computers included in the data center 100 to function as the deployment control unit 310 and the data acquisition unit 380.
  • the deployment control unit 310 constructs the virtual data center 200 based on the construction information 400.
  • the deployment control unit 310 includes an AP module deployment unit 320, a related module deployment unit 330, an MW / OS deployment unit 340, a data deployment unit 350, a VM deployment unit 360, and an NW deployment unit 370.
  • the AP module deploying unit 320, the related module deploying unit 330, the MW / OS deploying unit 340, the data deploying unit 350, and the VM deploying unit 360 are respectively configured as AP modules that configure the virtual machine 220 in the processing device 150. Installation (deployment) and setting of modules, MW / OS modules, and VM modules are performed.
  • the data deployment unit 350 restores the data area in the processing device 150 and the storage device 160 using the backup data.
  • the NW deployment unit 370 uses the network device 170 to construct the networks 230 and 240.
  • the data acquisition unit 380 generates backup data for the data areas in the processing device 150 and the storage device 160.
  • the deployment control unit 310 performs the deployment processing and setting specific to the system 210, the virtual machine 220, and the module. You may go.
  • the construction information 400 includes virtual DC (data center) resource information 410, network configuration information 420, system configuration information 430, data area information 440, and module information 450.
  • virtual DC data center
  • the virtual DC resource information 410 indicates the amount of resources required by the virtual data center 200.
  • the resource amount includes, for example, the number of CPUs on the processing device 150, the amount of memory, the amount of disk area on the storage device 160, the number of networks 230 and 240, and the like.
  • FIG. 9 is a diagram illustrating an example of the virtual DC resource information 410 according to the first embodiment of this invention.
  • the virtual DC resource information 410 includes a required resource amount for each resource type.
  • the network configuration information 420 indicates setting information of the common network 230 in the virtual data center 200.
  • FIG. 10 is a diagram illustrating an example of the network configuration information 420 according to the first embodiment of this invention.
  • the network configuration information 420 includes the network address of the network 230 for each identifier (NW identifier) of the network 230 as the setting information of the network 230.
  • the network configuration information 420 may include external network setting information and the virtual machine image identifier of the gateway 250.
  • the system configuration information 430 includes module configuration information 431 and network setting information 432.
  • the module configuration information 431 indicates a module configuring each virtual machine 220 of each system 210 in the virtual data center 200.
  • FIG. 11 is a diagram illustrating an example of the module configuration information 431 according to the first embodiment of this invention.
  • the module configuration information 431 includes, for each identifier of the virtual machine 220 of each system 210, the module type and module identifier of the module that configures the virtual machine 220.
  • the module configuration information 431 may further include setting information for each module.
  • the network setting information 432 indicates setting information of the network 240 in each system 210 of the virtual data center 200.
  • FIG. 12 is a diagram illustrating an example of the network setting information 432 according to the first embodiment of this invention.
  • the network setting information 432 includes a network address of the network 240 for each identifier (NW identifier) of the network 240 of each system 210.
  • the network setting information 432 includes, for each interface identifier (IF identifier) of the virtual machine 220 of each system 210, an identifier (NW identifier) of the network 240 to which the interface is connected.
  • the data area information 440 indicates backup data of the data area used by each system 210 in the virtual data center 200.
  • the data area is, for example, a data area that is secured on the memory of the processing apparatus 150 or the storage apparatus 160 by each system 210 or each virtual machine 220, and the backup data is backup data related to the data area. is there.
  • FIG. 13 is a diagram illustrating an example of the data area information 440 according to the first embodiment of this invention.
  • the data area information 440 includes, for each identifier of the data area of the system 210 and for each identifier of the data area of the virtual machine 220 of each system 210, an identifier (data identifier) of backup data of the data area. including.
  • the module information 450 includes modules constituting each system 210 and each virtual machine 220 in the virtual data center 200, and backup data.
  • FIG. 14 is a diagram illustrating an example of the module information 450 according to the first embodiment of this invention.
  • the module information 450 includes a module corresponding to each module identifier indicated by the module configuration information 431 in FIG. 11, backup data corresponding to each data identifier indicated by the data area information 440 in FIG.
  • the virtual machine image corresponding to the virtual machine image identifier of the gateway 250 indicated by the network configuration information 420 in FIG. 10 is included.
  • the module information 450 can include, as one common module, modules common to each system 210 and each virtual machine 220, such as an OS module and an MW module.
  • the virtual DC resource information 410, the network configuration information 420, the module configuration information 431, the network setting information 432, and the data area information 440 described above may be described in other formats such as XML (Extensible Markup Language). Good.
  • Each of the modules included in the virtual DC resource information 410, the network configuration information 420, the module configuration information 431, the network setting information 432, and the module information 450 described above, together with the construction program 300, is the designer of the virtual data center 200. It is assumed that the information is generated by the administrator or the like and set in advance in the construction information storage unit 130 and the construction program storage unit 120 by an administrator or the like.
  • the virtual DC resource information 410 described above may be updated according to the state of the virtual data center 200.
  • the migration control unit 110 determines the migration destination data center 100 of the migration target virtual data center 200 and transmits the construction program 300 of the migration target virtual data center 200 to the migration destination data center 100.
  • the resource management unit 140 allocates (dispenses) resources for constructing the virtual data center 200 to the virtual data center 200.
  • the resource management information storage unit 141 stores resource management information 142.
  • the resource management information 142 indicates the amount of resources that can be used in the data center 100.
  • FIG. 15 is a diagram illustrating an example of the resource management information 142 according to the first embodiment of this invention.
  • the resource management information 142 includes an available resource amount for each resource type.
  • Resource allocation information storage unit 143 stores resource allocation information 144.
  • the resource allocation information 144 indicates the amount of resources allocated to each virtual data center 200.
  • FIG. 16 is a diagram illustrating an example of the resource allocation information 144 according to the first embodiment of this invention.
  • the resource allocation information 144 includes the resource type and the allocated amount for each identifier of the virtual data center 200.
  • the resource management unit 140 (virtualization platform) is NISTNDefinition of Cloud Computing (Draft) (http://csrc.nist.gov/publications/drafts/800-145/Draft-SP-800-145_cloud-definition. (pdf) may include the functions of Service Models IaaS (Infrastructure as Service). Further, the resource management unit 140 may allocate resources in accordance with API (Application Programming Interface) defined by libvirt (http://libvirt.org/).
  • API Application Programming Interface
  • the migration control unit 110 and the resource management unit 140 may be a computer that includes a CPU and a storage medium that stores a program and that operates by control based on the program.
  • the construction program storage unit 120, the construction information storage unit 130, the resource management information storage unit 141, and the resource allocation information storage unit 143 may be configured as individual storage media or a single storage medium.
  • each data center 100 can access a part or all of the construction program storage unit 120, the construction information storage unit 130, the resource management information storage unit 141, and the resource allocation information storage unit 143. Etc. may be included.
  • a part of the module information 450 of the construction information 400 may be stored in a storage device that can be accessed by each data center 100.
  • modules commonly used by a plurality of virtual machines 220 such as MW modules and OS modules, may be stored in an external repository (not shown) accessible by each data center 100.
  • FIG. 6 is a flowchart showing the migration process in the first embodiment of the present invention.
  • the migration process will be described by taking as an example the case of migrating all the virtual data centers 200 in the data center 100 (DC1) to another data center 100 in FIG.
  • the migration control unit 110 of the migration source data center 100 receives an instruction to migrate the data center 100 from, for example, an administrator.
  • the migration control unit 110 may determine the necessity of migration of the data center 100 based on the monitoring information of the virtual machine 220 and the processing device 150 in each virtual data center 200, and may start migration processing. .
  • the migration control unit 110 selects one migration target virtual data center 200 from the non-migrated virtual data centers 200 constructed in the data center 100 (step S101).
  • the migration control unit 110 of the data center 100 selects the virtual data center 200 (VDC11).
  • the migration control unit 110 searches for another data center 100 (migration destination data center 100) to which the selected virtual data center 200 can be migrated (step S102).
  • the migration control unit 110 determines whether the necessary resource amount indicated by the virtual DC resource information 410 of the construction information 400 for the virtual data center 200 to be migrated can be secured, for example.
  • the migration destination data center 100 is searched by inquiring 140.
  • the resource management unit 140 of another data center 100 determines whether or not the necessary resource amount included in the inquiry can be secured based on the available resource amount of the resource management information 142 and responds with the result.
  • the migration control unit 110 of the data center 100 inquires of the data center 100 (DC2) whether the necessary resource amount indicated by the virtual DC resource information 410 in FIG. 9 can be secured.
  • the resource management unit 140 of the data center 100 (DC2) determines that the necessary resource amount can be secured based on the available resource amount indicated by the resource management information 142 in FIG.
  • the migration control unit 110 of the data center 100 (DC1) determines the data center 100 (DC2) as the migration destination data center 100.
  • step S102 When the migration destination data center 100 does not exist in step S102 (step S103 / No), the migration control unit 110 proceeds to the process of step S106.
  • step S102 When the migration destination data center 100 exists in step S102 (step S103 / Yes), the migration control unit 110 loads the construction program 300 corresponding to the migration target virtual data center 200 stored in the construction program storage unit 120. Start up and instruct the execution of the data acquisition process.
  • the construction program 300 executes data acquisition processing (step S104).
  • the migration control unit 110 of the data center 100 activates the construction program 300 of the virtual data center 200 (VDC11).
  • FIG. 7 is a flowchart showing details of the data acquisition process (step S104) by the construction program 300 in the first embodiment of the present invention.
  • the data acquisition unit 380 of the construction program 300 selects one system 210 included in the virtual data center 200 (step S301). For example, the data acquisition unit 380 of the construction program 300 of the virtual data center 200 (VDC 11) selects the system 210 (S1).
  • the data acquisition unit 380 acquires the contents of the data area of the system 210 in the processing device 150 and the storage device 160, and generates backup data (step S302).
  • the data acquisition unit 380 registers the backup data in the module information 450, and registers the identifier of the backup data in the data area information 440.
  • the data acquisition unit 380 generates backup data (Sys_DATA1, 2) of the data area (Sys_Area1, 2) of the system 210 (S1), registers it in the module information 450 as shown in FIG.
  • the identifier is registered in the data area information 440 as shown in FIG.
  • the data acquisition unit 380 selects one virtual machine 220 included in the system 210 (step S303).
  • the data acquisition unit 380 selects the virtual machine 220 (VM11) of the system 210 (S1).
  • the data acquisition unit 380 acquires the contents of the data area of the virtual machine 220 in the processing device 150 and the storage device 160, and generates backup data (step S304).
  • the data acquisition unit 380 registers the backup data in the module information 450, and registers the identifier of the backup data in the data area information 440.
  • the data acquisition unit 380 generates backup data (VM_DATA1, 2) of the data area (VM_Area1, 2) of the virtual machine 220 (VM11), registers it in the module information 450 as shown in FIG. Are registered in the data area information 440 as shown in FIG.
  • the data acquisition unit 380 repeats steps S303 to S304 for all virtual machines 220 included in the virtual data center 200 (step S305).
  • the data acquisition unit 380 repeats steps S301 to S305 for all the systems 210 included in the virtual data center 200 (step S306).
  • data area information 440 as shown in FIG. 13 and module information 450 as shown in FIG. 14 are set in the construction information 400 of the virtual data center 200 (VDC 11).
  • the migration control unit 110 transmits the construction program 300 and the construction information 400 corresponding to the virtual data center 200 to be migrated to the migration destination data center 100 (step S105).
  • the migration control unit 110 of the data center 100 transmits the construction program 300 and construction information 400 of the virtual data center 200 (VDC11) to the data center 100 (DC2).
  • the construction information 400 includes virtual DC resource information 410, network configuration information 420, module configuration information 431, network setting information 432, data area information 440, and module information 450 shown in FIGS.
  • the migration control unit 110 of the migration destination data center 100 receives the construction program 300 and the construction information 400 from the migration source data center 100 and stores them in the construction program storage unit 120 and the construction information storage unit 130, respectively. (Step S201).
  • the migration control unit 110 activates the construction program 300 corresponding to the migration target virtual data center 200 stored in the construction program storage unit 120 and instructs execution of the virtual data center construction process.
  • the construction program 300 executes a virtual data center construction process (step S202).
  • the migration control unit 110 of the data center 100 activates the construction program 300 of the virtual data center 200 (VDC11).
  • FIG. 8 is a flowchart showing details of the virtual data center construction process (step S202) by the construction program 300 in the first embodiment of the present invention.
  • the deployment control unit 310 of the construction program 300 acquires the resources required by the virtual data center 200 from the resource management unit 140 of the migration destination data center 100 (step S401).
  • the deployment control unit 310 sends the necessary resource amount (the number of CPUs, the amount of memory, the amount of disk space, the number of networks 230 and 240) of the virtual data center 200 indicated by the virtual DC resource information 410 to the resource management unit 140.
  • the resource management unit 140 allocates the resource amount requested by the deployment control unit 310 to the virtual data center 200, and assigns the identifiers of the processing device 150, the storage device 160, and the network device 170 to which the resource is allocated, to the deployment control unit. 310 is notified.
  • the deployment control unit 310 of the construction program 300 of the virtual data center 200 requests the required resource amount indicated by the virtual DC resource information 410 in FIG.
  • the resource management unit 140 allocates the requested resource to the virtual data center 200 (VDC 11) and updates the resource management information 142 in FIG. Further, the resource management unit 140 updates the resource allocation information 144 as shown in FIG.
  • the NW deployment unit 370 of the deployment control unit 310 constructs the network 230 in the virtual data center 200 (step S402).
  • the NW deployment unit 370 constructs the network 230 indicated by the network configuration information 420 in the network device 170 to which resources are allocated.
  • the NW deployment unit 370 constructs the network 230 (VL0) indicated by the network configuration information 420 in FIG.
  • the NW deployment unit 370 constructs the gateway 250 of the virtual data center 200 (step S403).
  • the NW deployment unit 370 acquires the virtual machine image of the gateway 250 indicated by the network configuration information 420 from the module information 450, and deploys the virtual machine image to the processing device 150 to which the resource is allocated.
  • the NW deployment unit 370 acquires the virtual machine image (VMI_GW) of the gateway 250 indicated by the network configuration information 420 in FIG. 10 from the module information 450 in FIG.
  • VMI_GW virtual machine image
  • the deployment control unit 310 selects one system 210 included in the virtual data center 200 (step S404).
  • the deployment control unit 310 selects the system 210 (S1).
  • the NW deployment unit 370 constructs the network 240 in the system 210 (step S405).
  • the NW deployment unit 370 constructs the network 240 indicated by the network setting information 432 in the network device 170 to which resources are allocated.
  • the NW deployment unit 370 constructs the network 240 (VL1) indicated by the network setting information 432 in FIG.
  • the deployment control unit 310 selects one virtual machine 220 constituting the system 210 (step S406).
  • the deployment control unit 310 selects the virtual machine 220 (VM11) of the system 210 (S1).
  • the VM deployment unit 360 deploys the virtual machine image of the virtual machine 220 to the processing device 150 to which the resource is allocated (Step S407).
  • the VM deployment unit 360 acquires the virtual machine module (virtual machine image) indicated by the module configuration information 431 from the module information 450 and deploys it to the processing apparatus 150.
  • setting information for a virtual machine module is described in the module configuration information 431, setting for the virtual machine module is performed according to the setting information.
  • the VM deployment unit 360 acquires the virtual machine image (VMI1) of the virtual machine 220 (VM11) indicated by the module configuration information 431 in FIG. 11 from the module information 450 in FIG.
  • the NW deployment unit 370 connects the virtual machine 220 to the network 230 and the network 240 (step S408).
  • the NW deployment unit 370 sets the network device 170 based on the network setting information 432 of the construction information 400.
  • the NW deployment unit 370 connects the interfaces IF1 and IF2 of the virtual machine 220 (VM11) to the network 230 (VL0) and the network 240 (VL1) based on the network setting information 432 in FIG.
  • the network device 170 is set.
  • the data deployment unit 350 restores the contents of the data area of the virtual machine 220 in the processing device 150 and the storage device 160 based on the backup data (step S409).
  • the data deployment unit 350 acquires the backup data of the virtual machine 220 indicated by the data area information 440 from the module information 450 and restores the contents of the data area.
  • the data deployment unit 350 obtains backup data (VM_DATA1, 2) of the data area (VM_Area1, 2) of the virtual machine 220 (VM11) indicated by the data area information 440 in FIG. 13 from the module information 450 in FIG. Acquired and restores the contents of the data area (VM_Area1, 2) in the processing device 150 and the storage device 160.
  • the MW / OS deployment unit 340 deploys the OS module and the MW module in the virtual machine 220 on the processing device 150 (step S410).
  • the related module deployment unit 330 deploys the related module to the virtual machine 220 on the processing device 150 (step S411).
  • the AP module deployment unit 320 deploys the AP module to the virtual machine 220 on the processing device 150 (step S412).
  • the MW / OS deploying unit 340, the related module deploying unit 330, and the AP module deploying unit 320 acquire each module indicated by the module configuration information 431 from the module information 450 and deploy it to the virtual machine 220.
  • the setting for each module is performed according to the setting information.
  • the MW / OS deploying unit 340, the related module deploying unit 330, and the AP module deploying unit 320 are configured such that the OS module (OS 1) and the MW module indicated by the module configuration information 431 in FIG. (MW1), the related module (Lib1), and the AP module (AP1) are acquired and deployed to the virtual machine 220 (VM11).
  • a virtual machine 220 having a module configuration as shown in FIG. 4 is constructed in the processing device 150 of the data center 100 (DC2).
  • the deployment control unit 310 repeats steps S406 to S412 for all virtual machines 220 included in the system 210 (step S413).
  • the data deployment unit 350 restores the contents of the data area of the system 210 in the processing device 150 and the storage device 160 based on the backup data (step S414).
  • the data deployment unit 350 acquires the backup data of the system 210 from the module information 450 based on the data area information 440, and restores the contents of the data area.
  • the data deployment unit 350 acquires backup data (Sys_DATA1, 2) of the data area (Sys_Area1, 2) of the system 210 (S1) from the module information 450 of FIG. 15 based on the data area information 440 of FIG. Then, the contents of the data area (Sys_Area1, 2) in the processing device 150 and the storage device 160 are restored.
  • the deployment control unit 310 repeats steps S404 to S414 for all the systems 210 included in the virtual data center 200 (step S415).
  • VDC 11 virtual data center 200 having the system configuration shown in FIG. 3 is constructed in the data center 100 (DC 2).
  • the migration control unit 110 of the migration source data center 100 repeats the processing of steps S101 to S105 for all the virtual data centers 200 of the migration source data center 100, and tries to migrate to another data center 100 (step S106). ).
  • each virtual data center 200 is constructed in another data center 100.
  • FIG. 17 is a diagram illustrating an example of migration of the virtual data center 200 between the data centers 100 according to the first embodiment of this invention.
  • the virtual data center 200 goes to the data center 100 (DC2)
  • the virtual data center 200 goes to the data center 100.
  • the virtual data center 200 (VDC 13, 14) is migrated to the data center 100 (DC4).
  • the migration control unit 110 outputs a list of virtual data centers 200 that could not be migrated to the administrator or the like as an error message (step S107).
  • the operation has been described by taking as an example the case of migrating all the virtual data centers 200 of the migration source data center 100 to another data center 100, but the specification specified by the administrator Only the virtual data center 200 may be migrated to another data center 100.
  • FIG. 1 is a block diagram showing a characteristic configuration of the first embodiment of the present invention.
  • the information processing system includes a plurality of data centers 100 in which one or more virtual data centers 200 are constructed.
  • Each of the plurality of data centers 100 includes one or more processing devices 150, a construction program storage unit 120, and a migration control unit 110.
  • the processing device 150 executes processing of one or more virtual machines 220 configuring each of the one or more virtual data centers.
  • the construction program storage unit 120 stores a construction program 300 for constructing the virtual data center 200 on one or more processing devices 150 for each of the one or more virtual data centers 200.
  • the migration control unit 110 determines the migration destination data center 100 of the migration target virtual data center 200 among the one or more virtual data centers 200, and executes the construction program 300 corresponding to the migration target virtual data center 200. The data is transmitted to the migration destination data center 100.
  • migration to a smaller data center 100 can be performed in the migration of the system between the data centers 100.
  • the reason is that the data center 100 is constructed by one or more virtual data centers 200, and the migration control unit 110 performs migration to another data center 100 in units of the virtual data center 200.
  • the migration control unit 110 performs migration to another data center 100 in units of the virtual data center 200.
  • the migration control unit 110 transmits the construction program 300 for constructing the migration target virtual data center 200 to the migration destination data center 100.
  • the construction of the virtual data center 200 there are cases where deployment processing and settings specific to the system 210, the virtual machine 220, and the modules (for example, settings specific to the OS module, MW module, and AP module) are required. Not all data centers 100 are provided with means for performing these unique deployment processes and settings.
  • the migration destination data center 100 is specific to the migration target system 210, the virtual machine 220, and the module.
  • the virtual data center 200 can be migrated even without a means for performing a simple deployment process and setting.
  • the amount of data transferred can be reduced in the system migration between the data centers 100.
  • the reason is that the construction program 300 deploys one or more modules constituting the virtual machine 220 based on the construction information 400 in the migration destination data center 100.
  • the construction information 400 may include such a module as one common module. it can. Therefore, in the migration of the virtual machine 220 between the data centers 100, the migration destination data center 100 is compared with a case where a virtual machine image including a higher-order module (for example, from the OS module to the AP module) of the virtual machine is transferred. The amount of data transferred to is reduced.
  • the second embodiment of the present invention is different from the first embodiment in that the migration control unit 110 selects the virtual data center 200 to be migrated based on the migration priority.
  • FIG. 18 is a block diagram showing a configuration of the information processing system in the second exemplary embodiment of the present invention.
  • the configuration of the data center 100 according to the second embodiment of the present invention includes a migration priority storage unit 111 in addition to the configuration of the data center 100 according to the first embodiment.
  • the migration priority storage unit 111 stores migration priority information 112.
  • the migration priority information 112 indicates the migration priority of each virtual data center 200 constructed in the data center.
  • FIG. 19 is a diagram illustrating an example of the migration priority information 112 according to the second embodiment of this invention.
  • the migration priority information 112 indicates the migration priority of the virtual data center 200 for each identifier (virtual DC identifier) of the virtual data center 200.
  • identifier virtual DC identifier
  • the migration priority is set in advance by an administrator or the like based on, for example, the importance of the system 210 included in each virtual data center 200 and the service level required for each virtual data center 200. For example, a migration priority higher than that of the other virtual data centers 200 is set as the migration priority of the virtual data center 200 that guarantees a high service level with a high usage fee.
  • FIG. 20 is a flowchart showing the migration process in the second embodiment of the present invention.
  • the migration control unit 110 of the migration source data center 100 selects one virtual data center 200 with the highest migration priority from the non-migrated virtual data centers 200 constructed in the data center 100 (step S111). .
  • the migration control unit 110 selects the virtual data center 200 based on the migration priority information 112.
  • the migration control unit 110 searches for another data center 100 to which the selected virtual data center 200 can be migrated (step S102).
  • step S102 When the migration destination data center 100 exists in step S102 (step S112 / Yes), the virtual data center construction process is executed by the construction program 300 transmitted to the migration destination data center 100 as in the first embodiment. (Steps S104 to S105, S201 to S202).
  • step S102 When the migration destination data center 100 does not exist in step S102 (step S112 / No), the migration control unit 110 expects the status of the other data center 100 to change, and again after a certain time, the migration destination data.
  • the center 100 is searched (step S113).
  • step S113 if the migration destination data center 100 exists (step S114 / Yes), virtual data center construction processing is executed (steps S104 to S105, S201 to S202).
  • step S113 when the migration destination data center 100 does not exist (step S114 / No), the migration control unit 110 determines whether or not a predetermined timeout time has elapsed (step S115). When it is not time-out (step S115 / No), the transfer control unit 110 repeats the processing from step S113. When it is time-out (step S115 / Yes), the migration control unit 110 interrupts the migration of the virtual data center 200 that has not been migrated at that time, and displays a list of virtual data centers 200 that could not be migrated as an error message. (Step S107).
  • the migration control unit 110 selects the migration target virtual data center 200 based on the migration priority.
  • the virtual data center 200 including the important system 210 is preferentially migrated. It is possible to prevent the entire system 210 in the data center 100 from being stopped due to a failure of the data center 100 or the like.
  • the construction program 300 itself is different from the first embodiment in that it automatically controls transition.
  • FIG. 21 is a diagram showing a configuration of the construction program 300 in the third embodiment of the present invention.
  • the configuration of the construction program 300 according to the third embodiment of the present invention is the virtual data center 200 corresponding to the construction program 300 in addition to the configuration of the construction program 300 according to the first embodiment.
  • a transition control unit (autonomous transition control unit) 390 that performs the same processing as the transition control unit 110 is included. That is, the construction program 300 further causes the computer included in the data center 100 to function as the migration control unit 390.
  • the migration control unit 390 of the construction program 300 in the migration source data center 100 based on the monitoring information of the virtual machines 220 and processing devices 150 in the virtual data center 200 corresponding to the construction program 300. Determine the need for migration.
  • the migration control unit 390 determines the migration destination data center 100 of the virtual data center 200 and instructs the data acquisition unit 380 to execute data acquisition processing. Then, the migration control unit 390 transmits the construction program 300 and the construction information 400 corresponding to the construction program 300 to the migration destination data center 100.
  • the migration control unit 390 of the transmitted construction program 300 instructs the deployment control unit 310 to execute the virtual data center construction process.
  • the virtual data center 200 corresponding to the construction program 300 is constructed in the migration destination data center 100.
  • the virtual data center 200 can be autonomously migrated to another data center 100.
  • the migration control unit 390 of the construction program 300 determines the migration destination data center 100 of the virtual data center 200 corresponding to the construction program 300 and transmits the construction program 300 to the migration destination data center 100. Because. Thereby, even when the migration destination data center 100 does not have the migration control unit 110, the virtual data center 200 can be re-migrated to another data center 100.
  • the virtual machine module may be a virtual machine template including an upper module (for example, OS module, MW module), various settings for the virtual machine 220, and various settings for the upper module.
  • an upper module for example, OS module, MW module
  • the virtual machine module may include an image of a data area used by the virtual machine 220.
  • the data acquisition unit 380 in the data acquisition process, the data acquisition unit 380 generates a virtual machine image including a data area for each virtual machine 220 of each system 210 and registers it in the module information 450. Then, in the virtual data center construction process, the VM deployment unit 360 or the data deployment unit 350 acquires a virtual machine image including a data area from the module information 450 and deploys it to the processing device 150.
  • Data Center 110 Migration Control Unit 111 Migration Priority Storage Unit 112 Migration Priority Information 120 Construction Program Storage Unit 130 Construction Information Storage Unit 140 Resource Management Unit 141 Resource Management Information Storage Unit 142 Resource Management Information 143 Resource Allocation Information Storage Unit 144 Resource Allocation information 150 Processing device 160 Storage device 170 Network device 200 Virtual data center 210 System 220 Virtual machine 230 Network 240 Network 250 Gateway 300 Construction program 310 Deployment control unit 320 AP module deployment unit 330 Related module deployment unit 340 MW / OS deployment unit 350 Data deployment unit 360 VM deployment unit 370 NW deployment unit 380 Data acquisition unit 390 Migration control unit 400 Built information 410 virtual DC resource information 420 the network configuration information 430 system configuration information 431 module configuration information 432 network setting information 440 data area information 450 module information

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Stored Programmes (AREA)
PCT/JP2013/000344 2012-02-01 2013-01-24 Système de traitement d'informations, centre de traitement d'information, procédé de migration de système et programme Ceased WO2013114829A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2012019889 2012-02-01
JP2012-019889 2012-02-01

Publications (1)

Publication Number Publication Date
WO2013114829A1 true WO2013114829A1 (fr) 2013-08-08

Family

ID=48904879

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/000344 Ceased WO2013114829A1 (fr) 2012-02-01 2013-01-24 Système de traitement d'informations, centre de traitement d'information, procédé de migration de système et programme

Country Status (1)

Country Link
WO (1) WO2013114829A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023500669A (ja) * 2019-10-31 2023-01-10 サービスナウ， インコーポレイテッド クロス・クラウド・オペレーションのためのクラウド・サービス

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011128967A (ja) * 2009-12-18 2011-06-30 Hitachi Ltd 仮想計算機の移動方法、仮想計算機システム及びプログラム
JP2011209811A (ja) * 2010-03-29 2011-10-20 Nec Corp 仮想マシンシステムおよび仮想マシン配置方法
JP2011210032A (ja) * 2010-03-30 2011-10-20 Hitachi Ltd 仮想マシンのマイグレーション方法およびシステム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011128967A (ja) * 2009-12-18 2011-06-30 Hitachi Ltd 仮想計算機の移動方法、仮想計算機システム及びプログラム
JP2011209811A (ja) * 2010-03-29 2011-10-20 Nec Corp 仮想マシンシステムおよび仮想マシン配置方法
JP2011210032A (ja) * 2010-03-30 2011-10-20 Hitachi Ltd 仮想マシンのマイグレーション方法およびシステム

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023500669A (ja) * 2019-10-31 2023-01-10 サービスナウ， インコーポレイテッド クロス・クラウド・オペレーションのためのクラウド・サービス
JP7461471B2 (ja) 2019-10-31 2024-04-03 サービスナウ， インコーポレイテッド クロス・クラウド・オペレーションのためのクラウド・サービス

Similar Documents

Publication Publication Date Title
CN111656320B (zh) 机器人应用管理装置、系统、方法及程序
CN107924383B (zh) 用于网络功能虚拟化资源管理的系统和方法
US10044795B2 (en) Methods and apparatus for rack deployments for virtual computing environments
CN107534579B (zh) 资源管理的系统和方法
CN113971095A (zh) 扩展进程中的kubernetes应用程序接口
US11093296B2 (en) System, virtualization control apparatus, method for controlling a virtualization control apparatus, and program
US20190327144A1 (en) Methods and apparatus for template driven infrastructure in virtualized server systems
US11461120B2 (en) Methods and apparatus for rack nesting in virtualized server systems
JP6102949B2 (ja) 仮想計算機管理プログラム，仮想計算機管理方法及び仮想計算機システム
JP6677294B2 (ja) ネットワークシステム、パッチファイル適用方法、及びプログラム
US11343141B2 (en) Methods and apparatus to migrate physical server hosts between virtual standard switches and virtual distributed switches in a network
JP6330923B2 (ja) オーケストレータ装置、システム、仮想マシンの作成方法及びプログラム
CN104410672A (zh) 网络功能虚拟化应用升级的方法、转发业务的方法及装置
CN107113193B (zh) 一种确定vnf的处理策略的方法、装置及系统
EP3442203A1 (fr) Procédé et dispositif de migration de machine virtuelle et système de virtualisation
KR101585160B1 (ko) 독립실행환경을 제공하는 분산 컴퓨팅 시스템 및 분산 컴퓨팅 시스템의 제어방법
KR20150109692A (ko) 가상 머신 이미지 파일을 제공하는 방법 및 그 장치
JPWO2017170309A1 (ja) ネットワークシステム、その管理方法および装置ならびにサーバ
CN113986539B (zh) 实现pod固定IP的方法、装置、电子设备和可读存储介质
CN119088409A (zh) 一种升级迁移方法、装置、设备及计算机可读存储介质
CN108345496B (zh) 一种运行应用程序的方法及装置
JP2024524398A (ja) コンテナクラスタのストレージリソースを管理するための方法および装置、ならびにシステム
JP6792125B1 (ja) エッジシステム、エッジシステムの制御方法、エッジシステムの制御に用いるコンピュータプログラム、及び、その記録媒体
WO2013114829A1 (fr) Système de traitement d'informations, centre de traitement d'information, procédé de migration de système et programme
JP2011221634A (ja) 計算機システム、論理区画管理方法及び論理分割処理プログラム

Legal Events

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

Ref document number: 13743644

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13743644

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP