Autorep process to create repository according to seed data and at least one new schema

• US 7,689,587 B1
• Filed: 06/28/2007
• Issued: 03/30/2010
• Est. Priority Date: 06/28/2007
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Carson, Keith Alan Jr., Tiruveedi, Venkata R., Krishnamoorthy, Padma
• Primary Examiner(s): CHANNAVAJJALA, SRIRAMA T
• Application Number:
  US11/770,216
• Time in Patent Office: 1,006 Days
• Field of Search: 707 1- 5, 707/10, 707/100, 707/102, 707103 R-103 Z, 707/104.1, 707/200, 707/203, 707205-206, 707/103.X, 717/108, 717/112, 717121-122, 717168-177, 706 45- 50, 709/203, 709/217, 709/220
• US Class Current: 707/803
• CPC Class Codes: G06F 16/211 Schema design and management

Abstract

Generating a repository template of a repository of data for a storage area network (SAN) management tool is disclosed. The repository will hold data describing SAN elements and configurations, and will be stored on a host. A configuration file is updated to include current configuration data for the repository, and includes specifications for a set of new schemas that define structures within the repository. A set of new schemas is created from those specifications. Seed data that defines initial information for the repository is copied to the host. New schemas are initialized with the seed data. A repository template is generated from the created set of new schemas and the seed data, from which one or more repositories may be created to hold SAN data.

Claims

1. A method of generating a repository template of a repository of data for a storage area network management tool, the repository defined to hold data describing storage area network elements and configurations, the method comprising:

updating a configuration file to include current configuration data for a first repository, wherein the configuration file includes specifications for a set of schemas defining at least one repository structure;

using configuration data from the configuration file to access the first repository currently stored on a host;

removing any schemas and data currently stored by the first repository;

creating a set of new schemas for the first repository according to the specifications from the configuration file;

copying seed data to the host, wherein the seed data defines initial repository information;

initializing the set of new schemas with the seed data;

upon initializing the set of new schemas, generating a repository template from the set of new schemas and the seed data, the repository template defined for creating one or more repositories to hold storage area network data;

creating a second repository from the repository template, wherein the second repository includes the seed data and the set of new schemas;

establishing a test environment based on the repository template;

wherein establishing the test environment includes;

(i) exporting each schema in the set of new schemas into the test environment;

(ii) replacing the seed data in each exported schema with data from at least one live storage area network (SAN);

(iii) upon determining that each exported new schema properly handles data from the live SAN, indicating, in the test environment, that the second repository is acceptable;

loading a prior version of the repository onto the host;

comparing the schemas of the prior version of the repository with the schemas of the second repository to determine any differences; and

creating at least one script that, when executed on a repository based on the prior version of the repository, will upgrade schemas according to the set of new schemas in the second repository;

via the test environment, receiving a correction of at least one schema in the set of new schemas, wherein receiving the correction includes;

upon determining that at least one exported schema does not properly handle the data from the live SAN;

resolving at least one incompatibility between at least one portion of data from the live SAN and an exported new schema.

2. The method of claim 1 wherein creating a set of new schemas comprises:

placing a set of scripts in a single script file, wherein the set of scripts comprises scripts defined for generating the repository template; and

wherein generating the repository template comprises;

executing the single script file.

3. The method of claim 1 comprising:

exporting a copy of the second repository; and

using the exported copy of the second repository to troubleshoot errors in the second repository.

4. The method of claim 1 comprising:

copying the repository template to a location, wherein copying signals an install kit generator that the repository template is available; and

generating an install kit from the repository template, wherein the install kit allow for a clean install of a repository on a respective host.

5. The method of claim 1 comprising:

testing a configuration of the host that will store the first repository prior to beginning creation of the second repository.

6. The method of claim 1 comprising:

creating a repository of data from the repository template, wherein the repository includes the seed data and the set of new schemas.

7. The method of claim 1 comprising:

determining a result of the generation of the repository template, wherein the result may be success or failure; and

communicating the result of the generation of the repository template.

8. The method as in claim 1, wherein updating the configuration file to include current configuration data for the repository includes:

creating the specifications for the configuration file, the specifications for at least one first new schema, wherein the first new schema is designed to hold data that has not been previously collected for storage in the first repository.

9. The method as in claim 1, wherein updating the configuration file to include current configuration data for the repository includes:

creating the specifications for the configuration file, the specifications for at least one first new schema, wherein the first new schema differs from any schemas found in the first repository.

10. The method as in claim 1, wherein updating the configuration file to include current configuration data for the repository includes:

creating the specifications for the configuration file, the specifications for at least one first new schema, the first new schema describing a reorganization of data currently in the first repository, wherein the data currently in the first repository relates to respective storage area network components, wherein the first new schema further includes at least one definition of a storage space not included in the first repository.

11. A computer system comprising:

a memory;

a processor;

a display;

a communications interface;

an interconnection mechanism coupling the memory, the processor, the display, and the communications interface, allowing communication there between;

wherein the memory is encoded with an automatic repository generation application, that when executed in the processor, provides an automatic repository generation process that generates a repository template of a repository of data for a storage area network management tool by causing the computer system to perform the operations of;

updating a configuration file to include current configuration data for a first repository, wherein the configuration file includes specifications for a set of schemas defining at least one repository structure, wherein the repository is defined for holding data describing storage area network elements;

using configuration data from the configuration file to access the first repository currently stored on a host;

removing any schemas and data currently stored by the first repository;

creating a set of new schemas for the first repository according to the specifications from the configuration file;

copying seed data to the host, wherein the seed data defines initial repository information;

initializing the set of new schemas with the seed data;

upon initializing the set of new schemas, generating a repository template from the set of new schemas and the seed data, the repository template defined for creating one or more repositories to hold storage area network data;

creating a second repository from the repository template, wherein the second repository includes the seed data and the set of new schemas;

establishing a test environment based on the repository template;

wherein establishing the test environment includes;

(i) exporting each schema in the set of new schemas into the test environment;

(ii) replacing the seed data in each exported schema with data from at least one live storage area network (SAN);

(iii) upon determining that each exported new schema properly handles data from the live SAN, indicating, in the test environment, that the second repository is acceptable;

loading a prior version of the repository onto the host;

comparing the schemas of the prior version of the repository with the schemas of the second repository to determine any differences; and

creating at least one script that, when executed on a repository based on the prior version of the repository, will upgrade schemas according to the set of new schemas in the second repository;

via the test environment, receiving a correction of at least one schema in the set of new schemas, wherein receiving the correction includes;

upon determining that at least one exported schema does not properly handle the data from the live SAN;

resolving at least one incompatibility between at least one portion of data from the live SAN and an exported new schema.

12. The computer system of claim 11 wherein creating a set of new schemas comprises:

placing a set of scripts in a single script file, wherein the set of scripts comprises scripts defined for generating the repository template;

and wherein generating the repository template comprises;

executing the single script file.

13. A computer program product, stored on computer readable medium, to generate a repository template of a repository of data for a storage area network management tool, the computer program product comprising:

computer program code for updating a configuration file to include current configuration data for a first repository, wherein the configuration file includes specifications for a set of schemas defining at least one repository structure, wherein the repository is defined for holding data describing storage area network elements;

computer program code for using configuration data from the configuration file to access the first repository currently stored on a host;

computer program code for removing any schemas and data currently stored by the first repository;

computer program code for creating a set of new schemas for the first repository according to the specifications from the configuration file;

computer program code for copying seed data to the host, wherein the seed data defines initial repository information;

computer program code for initializing the set of new schemas with the seed data;

computer program code for generating a repository template from the set of new schemas and the seed data upon initializing the set of new schemas, the repository template defined for creating one or more repositories to hold storage area network data;

computer program code for creating a second repository from the repository template, wherein the second repository includes the seed data and the set of new schemas;

computer program code for establishing a test environment based on the repository template;

wherein establishing the test environment includes;

(i) computer program code for exporting each schema in the set of new schemas into the test environment;

(ii) computer program code for replacing the seed data in each exported schema with data from at least one live storage area network (SAN);

(iii) computer program code for indicating, in the test environment, that the second repository is acceptable upon determining that each exported new schema properly handles data from the live SAN;

computer program code for loading a prior version of the repository onto the host;

computer program code for comparing the schemas of the prior version of the repository with the schemas of the second repository to determine any differences; and

computer program code for creating at least one script that, when executed on a repository based on the prior version of the repository, will upgrade schemas according to the set of new schemas in the second repository;

computer program code for receiving a correction, via the test environment, of at least one schema in the set of new schemas, wherein receiving the correction includes;

computer program code for determining that at least one exported schema does not properly handle the data from the live SAN;

computer program code for resolving at least one incompatibility between at least one portion of data from the live SAN and an exported new schema upon determining that at least one exported schema does not properly handle the data from the live SAN.

14. The computer program product of claim 13 wherein computer program code for creating a set of new schemas comprises:

computer program code for placing a set of scripts in a single script file, wherein the set of scripts comprises scripts defined for generating the repository template;

and wherein generating the repository template comprises;

computer code for executing the single script file.