# US 2012/0254861 A1 · Method and apparatus of data center file system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254861 A1
- Document ID: US20120254861A1
- Status: Published application
- Kind: A1
- Application number: 13/074,269
- Filed: 2011-03-29
- Published: 2012-10-04
- Earliest claimed: 2011-03-29
- Assignees: Hitachi, Ltd.
- Inventors: Robert Eugene DOWN, JR.; William ZIETZKE; Dan RITCHIE; Yoshiki KANO
- Web page: https://patentgrep.com/patent/US20120254861A1

## CPC

- G06F 8/63: {Image based installation; Cloning; Build to order}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 3/0607: {by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device}
- G06F 3/0647: {Migration mechanisms}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments of the invention provide a capability to validate volume status on the host and storage system stored virtual machine image in the datacenter management server. In one embodiment, a server system includes a storage system having a plurality of volumes, a plurality of host systems, and a management server coupled with the storage system and the host systems via a network. A method of managing the server system comprises: generating a golden image in the storage system corresponding to a virtual machine image file; copying virtual machine data from the golden image to some of the plurality of volumes in the storage system; and keeping track, by the management server, of status of the volumes which have copied virtual machine data by monitoring activity of the virtual machines.

## Claims

### Claim 1

A method of managing a server system which includes a storage system having a plurality of volumes, a plurality of host systems, and a management server coupled with the storage system and the host systems via a network, the method comprising:
generating a golden image in the storage system corresponding to a virtual machine image file;
copying virtual machine data from the golden image to some of the plurality of volumes in the storage system; and
keeping track, by the management server, of status of the volumes which have copied virtual machine data by monitoring activity of the virtual machines;
wherein if the activity of a monitored virtual machine is start of deployment of the virtual machine (VM), the keeping track comprises checking if the status of a volume storing the VM data to be used for deploying the virtual machine from the storage system is in a volume pool and not attached to a target LUN (logical unit number) via storage management API before execution of deployment of the virtual machine;
wherein if the activity of a monitored virtual machine is deployment of the virtual machine before starting the virtual machine, the keeping track comprises checking if the status of a volume storing the VM data to be used for deploying the virtual machine from the storage system is “attached” as a volume that has been attached for a host system to which the virtual machine is to be deployed; and
wherein if the activity of a monitored virtual machine is end of storing the virtual machine, the keeping track comprises checking if the status of a volume storing the VM data that was used for deploying the virtual machine from the storage system is detached from a target LUN (logical unit number) and is in a volume pool via storage management API.

### Claim 2 (depends on 1)

The method according to claim 1,
wherein the golden image is generated using storage capability of the storage system pursuant to input from a VM administrator without input from administrator of the storage system or administrator of the management server.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising, prior to copying VM data from the golden image to some of the plurality of volumes in the storage system:
creating each of the plurality of volumes for storing VM data; and
attaching each of the created volumes to a host group which is a group of host systems that have the host systems' WWNs (World Wide Names) that can be mapped to volumes.

### Claim 4 (depends on 3)

The method according to claim 3, further comprising, subsequent to copying VM data from the golden image to some of the plurality of volumes in the storage system:
detaching each of the volumes from the host group; and
reserving host for VM by selecting an unused or shared core from a host list showing for each host system (1) a core which resides on the host system's processor and has usage by VM, and (2) a status which stores a name of any virtual machine which uses the core or no entry if the core is not used by any virtual machine, so as to make dedicated VM deployment for a target core by inserting a reserved state for the VM in the selected core.

### Claim 5 (depends on 4)

The method according to claim 4, further comprising, subsequent to the detaching and reserving:
attaching each of the detached volumes to the host group;
updating VM filename for each of the attached volumes;
rescanning disk in the storage system to discover one or more new volumes for host, each of the one or more new volumes being “discovered” as a volume that has been discovered for a host system to which a virtual machine is to be deployed;
bringing the rescanned disk online based on the discovered volumes; and
mounting the online disk.

### Claim 6 (depends on 5)

The method according to claim 5, further comprising, subsequent to the rescanning, bringing, and mounting:
starting VM image based on the mounted disk;
setting host to used by inserting in the host list VM name in place of the reserved state for the started VM in the selected core; and
updating the VM filename for each of the volumes for the started VM.

### Claim 7 (depends on 5)

The method according to claim 5, further comprising:
before attaching a volume to a host group, checking connection status of the host group for the volume to be attached to determine if the volume is not already attached; and
before detaching a volume from a host group, checking connection status of the host group for the volume to be detached to determine if the volume is attached.

### Claim 8 (depends on 4)

The method according to claim 4, further comprising:
validating cluster configuration of the host group by checking WWNs of the host systems in the host group.

### Claim 9 (depends on 8)

The method according to claim 8, further comprising, if the activity of a monitored virtual machine is start of deployment of the virtual machine:
determining if a number of the WWNs of the host systems is at least two and determining whether a number of ports in the storage system is at least two; and
if there are not at least two WWNs and at least two ports in the determining, storing operated variables of the deployment of the virtual machine and performing recovery using the stored operated variables.

### Claim 10 (depends on 4)

The method according to claim 4, further comprising, if the activity of a monitored virtual machine is start of deployment of the virtual machine:
determining whether there is an available core to deploy VM and, if yes, selecting an available core by inserting a reserved state for the VM in the selected core and, if no, sending an alert on failure to find an available core.

### Claim 11

A management server which is coupled with a storage system and host systems via a network, the storage system having a plurality of volumes, the management server comprising a processor; a memory; and a plan executor to execute plans to:
generate a golden image in the storage system corresponding to a virtual machine image file;
copy virtual machine data from the golden image to some of the plurality of volumes in the storage system; and
keep track, by the management server, of status of the volumes which have copied virtual machine data by monitoring activity of the virtual machines;
wherein if the activity of a monitored virtual machine is start of deployment of the virtual machine (VM), the keeping track comprises checking if the status of a volume storing the VM data to be used for deploying the virtual machine from the storage system is in a volume pool and not attached to a target LUN (logical unit number) via storage management API before execution of deployment of the virtual machine;
wherein if the activity of a monitored virtual machine is deployment of the virtual machine before starting the virtual machine, the keeping track comprises checking if the status of a volume storing the VM data to be used for deploying the virtual machine from the storage system is “discovered” as a volume that has been discovered for a host system to which the virtual machine is to be deployed; and
wherein if the activity of a monitored virtual machine is end of storing the virtual machine, the keeping track comprises checking if the status of a volume storing the VM data that was used for deploying the virtual machine from the storage system is detached from a target LUN (logical unit number) and is in a volume pool via storage management API.

### Claim 12 (depends on 11)

The management server according to claim 11,
wherein the golden image is generated using storage capability of the storage system pursuant to input from a VM administrator without input from administrator of the storage system or administrator of the management server.

### Claim 13 (depends on 11)

The management server according to claim 11, wherein the plan executor is configured to execute plans, prior to copying VM data from the golden image to some of the plurality of volumes in the storage system, to:
create each of the plurality of volumes for storing VM data; and
attach each of the created volumes to a host group which is a group of host systems that have the host systems' WWNs (World Wide Names) that can be mapped to volumes.

### Claim 14 (depends on 13)

The management server according to claim 13, wherein the plan executor is configured to execute plans, subsequent to copying VM data from the golden image to some of the plurality of volumes in the storage system, to:
detach each of the volumes from the host group; and
reserve host for VM by selecting an unused or shared core from a host list showing for each host system (1) a core which resides on the host system's processor and has usage by VM, and (2) a status which stores a name of any virtual machine which uses the core or no entry if the core is not used by any virtual machine, so as to make dedicated VM deployment for a target core by inserting a reserved state for the VM in the selected core.

### Claim 15 (depends on 14)

The management server according to claim 14, wherein the plan executor is configured to execute plans, subsequent to the detaching and reserving, to:
attach each of the detached volumes to the host group;
update VM filename for each of the attached volumes;
rescan disk in the storage system to discover one or more new volumes for host, each of the one or more new volumes being “discovered” as a volume that has been discovered for a host system to which a virtual machine is to be deployed;
bring the rescanned disk online based on the discovered volumes; and
mount the online disk.

### Claim 16 (depends on 15)

The management server according to claim 15, wherein the plan executor is configured to execute plans, subsequent to the rescanning, bringing, and mounting, to:
start VM image based on the mounted disk;
set host to used by inserting in the host list VM name in place of the reserved state for the started VM in the selected core; and
update the VM filename for each of the volumes for the started VM.

### Claim 17 (depends on 15)

The management server according to claim 15, wherein the plan executor is configured to execute plans:
before attaching a volume to a host group, to check connection status of the host group for the volume to be attached to determine if the volume is not already attached; and
before detaching a volume from a host group, to check connection status of the host group for the volume to be detached to determine if the volume is attached.

### Claim 18 (depends on 14)

The management server according to claim 14, wherein the plan executor is configured to execute plans to:
validate cluster configuration of the host group by checking WWNs of the host systems in the host group.

### Claim 19 (depends on 18)

The management server according to claim 18, wherein the plan executor is configured to execute plans, if the activity of a monitored virtual machine is start of deployment of the virtual machine, to:
determine if a number of the WWNs of the host systems is at least two and determining whether a number of ports in the storage system is at least two; and
if there are not at least two WWNs and at least two ports in the determining, store operated variables of the deployment of the virtual machine and perform recovery using the stored operated variables.

### Claim 20 (depends on 14)

The management server according to claim 14, wherein the plan executor is configured to execute plans, if the activity of a monitored virtual machine is start of deployment of the virtual machine, to:
determine whether there is an available core to deploy VM and, if yes, select an available core by inserting a reserved state for the VM in the selected core and, if no, send an alert on failure to find an available core.
