KR101660631B1 - Method and Device for managing Data Center Using Ontology - Google Patents

Abstract

A technique relating to a data center management method and apparatus using an ontology is disclosed. The disclosed data center management method includes: receiving a request for characteristic information on an entity of the data center, the method comprising: receiving characteristic information about an entity of the data center; Searching data in the database for data matched with the characteristic information by using a semantic annotation; And generating and outputting the characteristic information using the retrieved data, wherein the server management ontology includes a class for the entity and a class for the property information, and the entity includes a server for the data center, Server rack or server row.

Description

[0001] The present invention relates to a data center management method and apparatus using an ontology,

The present invention relates to a data center management method and apparatus, and more particularly, to a data center management method and apparatus using an ontology.

As IT services around the world evolve, the size and number of data centers are growing exponentially. Also, as the size of the data center grows, the importance of data center management becomes more important.

Among the devices in the data center, servers are the most affected by management. However, about 10% of the servers in the actual data center are not used, and the servers used are operating at about 5 ~ 20% efficiency. Since these servers cause unnecessary power consumption of the server itself and peripheral equipment, monitoring of the server is essential for efficient management.

However, server monitoring for data center management is focused on monitoring the factors such as CPU, memory usage, etc. and focusing on the efficiency of server device itself and establishment of management policy. In addition, since the data observed on the server is mainly monitored using the database, the administrator is responsible for observing and analyzing the data.

That is, since the existing server monitoring is mainly managed using only the database, there is a problem that management is difficult when the administrator does not know the structure of the data center and the database clearly. Also, in the existing data center management technique, since the database stores data on a per server basis, information about the server rack or server row needs to be directly calculated by the manager, and there is a problem that an error may occur.

Recently, a data center management method using an ontology has been researched to solve such a problem, and Korean Prior Art Publication No. 2013-0097366 is a related prior art document.

The present invention provides a method and apparatus for efficiently managing a data center using an ontology.

According to an aspect of the present invention, there is provided a data center management method using a server management ontology, the method comprising: receiving characteristic information about an entity of the data center; Searching data in the database for data matched with the characteristic information by using a semantic annotation; And generating and outputting the characteristic information using the retrieved data, wherein the server management ontology includes a class for the entity and a class for the property information, and the entity includes a server for the data center, Provides a data center management method that includes server racks or server rows.

According to another aspect of the present invention, there is provided a data center management apparatus using a server management ontology, the data center management apparatus comprising: an interface unit for receiving characteristic information about an entity of the data center, ; And a data retrieval unit retrieving, from the database, the data matching the characteristic information using the semantic annotation, and generating the characteristic information, wherein the server management ontology includes a class for the entity, Wherein the entity provides a data center management device comprising a server, a server rack or a server column of the data center.

According to the present invention, the administrator can easily monitor the entities of the data center without having to know the database structure, modify the server management ontology and the semantic annotation without changing the data center system, .

In addition, according to the present invention, characteristic information about a server rack or a server row is generated by using characteristic information about the server and is provided to the manager, so that the manager can easily grasp not only the server but also the characteristic information about the server rack or the server row .

1 is a diagram for explaining a data center management system using a server management ontology according to an embodiment of the present invention.
2 is a diagram showing an entity of a data center.
3 is a view for explaining a data center management apparatus using a server management ontology according to an embodiment of the present invention.
4 is a view for explaining a server management ontology according to an embodiment of the present invention.
5 is a diagram for explaining semantic annotation according to an embodiment of the present invention.
6 is a diagram for explaining relationship information according to an embodiment of the present invention.
7 is a view for explaining a data center management method using a server management ontology according to an embodiment of the present invention.
8 is a view for explaining a data center management system according to a specific embodiment of the present invention.
9 to 11 are views showing interface screens and output information of a data center management apparatus according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. Like reference numerals are used for like elements in describing each drawing.

Hereinafter, embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram for explaining a data center management system using a server management ontology according to an embodiment of the present invention.

As shown in FIG. 1, the data center management system according to the present invention includes a data center 110, a database 120, and a data center management device 130.

2, which illustrates entities of the data center 110, the data center 110 may include a plurality of servers, server racks, and server rows. A plurality of servers constitute a server rack, and a plurality of server racks constitute a server row.

The database 120 stores characteristic information for the data center 110 entity, which may include a permanent characteristic for the entity and a temporal characteristic for the entity. The unique characteristic information is characteristic information inherent to the entity, and may be, for example, hardware information of the server, network information, or model information. The sensing characteristic information is information of an entity that is observed over time through a sensor or the like, and may be, for example, power consumption of the server, resource usage information, or usage time information.

The data center management apparatus 130 is an apparatus that can efficiently manage the data center 110 by using an ontology and is provided with an entity of the data center 110 that needs to be monitored using a semantic annotation And searches the database 120 for the characteristic information. Hereinafter, the ontology used in the present invention will be referred to as a server management ontology, and the semantic annotation for mapping additional information on a specific entity and generating additional semantic information is used to provide mapping information between the class of the server management ontology and the database do. The data center entity may be a server in the data center or a server rack, which is a collection of servers. Or a server row that is a collection of server racks.

That is, when the manager requests the characteristic information about the entity requiring monitoring through the data center management device 130, the data center management device 130 searches the data for the requested entity, And provides it to the administrator.

The server management ontology includes classes for entity and class information, and the class and database are mapped through semantic annotation. Therefore, the administrator can easily monitor the entities in the data center without having to know the database structure. And can verify new property information for the data center entity by modifying the server management ontology and the semantic annotation without changing the data center system.

In addition, according to the present invention, characteristic information about a server rack or a server row is generated by using characteristic information about the server and is provided to the manager, so that the manager can easily grasp not only the server but also the characteristic information about the server rack or the server row .

3 is a diagram for explaining a data center management apparatus 130 using a server management ontology according to an embodiment of the present invention.

As shown in FIG. 3, the data center management apparatus according to the present invention includes an interface unit 310 and a data search unit 320. According to the embodiment, the entity management unit 330 and the ontology management unit 340 may be further included. The data center management device according to the present invention may be a computer including a processor or a separate device.

The interface unit 310 receives the characteristic information about the entity of the data center and outputs characteristic information. For example, the manager can request the characteristic information to the interface unit 310 using the type of the entity to be monitored, the identifier (ID), the type of characteristic information, and the date information. The interface unit 310 may receive characteristic information about an entity requested by the administrator from the data searching unit 320 and output the characteristic information.

The data searching unit 320 searches the database for data matched with the characteristic information using the semantic annotation, and generates characteristic information. Here, the semantic annotation includes a class of a server management ontology and mapping information of a database column. More specifically, the semantic annotation includes a semantic template including an identifier for a characteristic information class and type information of a class, And a semantic map including column information.

That is, the data retrieving unit 320 can confirm the position of the database in which the characteristic information about the requested entity is stored by using the semantic annotation, and return the retrieved data from the database. The retrieved data can be an instance value of the server management ontology class.

On the other hand, the entity management unit 330 can identify the server included in the entity for which the property information is requested by using the entity relationship information, and the entity relationship information includes information on the inclusion relation between the entities, . The database stores data on a server basis. When characteristic information about a server rack or a server column is requested, the entity management unit 330 can identify a server included in the server rack or the server column using the relationship information.

For example, when the manager requests characteristic information on the server rack 02 (rack 02), the entity management unit 330 can confirm the identifier of the server included in the server rack 02 using the relationship information. The data searching unit 320 can search the data base for data matching with the characteristic information about the identified server. Depending on the embodiment, the database may store data in server rack and server column units.

In addition, the ontology management unit 340 can generate status information of the entity based on the characteristic information by using a query for the status information of the entity, and the interface unit 310 can request and output the status information from the administrator .

The state information may include at least one of idle state information, overload state information, migration candidate state information, and reallocation candidate state information. The administrator can select one or more of the above state information and request the ontology. The ontology management unit 340 can provide the entity information included in the state together with the requested state information to the interface unit 310.

The ontology management unit 340 may generate status information according to a predetermined rule. In one embodiment, the ontology management unit 340 may generate status information by comparing the characteristic information with a threshold value at a preset time or for a preset time. For example, if the CPU usage is equal to or greater than the threshold value at a predetermined time, the ontology management unit 340 may determine that the server is in an overloaded state.

4 is a view for explaining a server management ontology according to an embodiment of the present invention.

As shown in FIG. 4, the server management ontology according to the present invention includes an entity class as a top-level class and a characteristic class as a class for characteristic information. Since the characteristic information is characteristic information for the entity, a hasCharacteristic relation exists between the entity class and the characteristic class.

The entity class is a subclass that includes a server column class, a server rack class, and a server class. As described above, since the server rack is a set of servers, and the server row is a set of server racks, the containedIn relationship holds between the server column class, the server rack class, and the server class.

On the other hand, the characteristic class includes a unique characteristic class and a sensing characteristic class as a subclass. The inherent property class may include an identifier (ID) class, a CPU number class, a memory size class, a disk size class, an IP address class, a manufacturer class, and a comments class as subclasses. The sensing characteristic class may include a CPU usage class, a disk usage class, a memory usage class, a power usage class, a usage time class, and the like as a subclass.

FIG. 5 is a diagram for explaining a semantic annotation according to an embodiment of the present invention, showing a semantic annotation expressed in XML.

As shown in FIG. 5, the semantic annotation according to the present invention includes a semantic template and a semantic map. In the semantic template, "c2a" is labeled as an identifier (ID) of the server which is one of the unique characteristic classes, and the type information of the identifier value of the server is an integer (int). "C2b" is labeled as an identifier for the CPU usage, which is one of the sensing characteristic classes, and the type information of the CPU usage value is a float.

In the semantic map, the column "col01" in the database is mapped to the label "c2a", and the column "col02" is mapped to the label "c2b".

Meanwhile, although one database is used in FIG. 5 as an embodiment, the semantic annotation according to the present invention can also be applied between databases having different schemas. That is, heterogeneous databases can be consolidated by mapping each column name to the same name, even if the column names of the databases are different.

FIG. 6 is a diagram for explaining relation information according to an embodiment of the present invention, showing relationship information expressed in XML.

Referring to FIG. 6, relationship information may include information on contained, cinnected, and grouped relationships between entities. The relationship information can be represented by an ID and an attribute value of an entity, and the attribute value indicates one of an inclusion relation, a connection relation, and a grouping relation.

In FIG. 6, the server column id = 01 includes two server racks, the first server rack id = 01 includes two servers, and the second server rack id = . ≪ / RTI >

As described above, when the manager requests characteristic information about the second server rack (id = 02), the server included in the second server rack can be identified through the relationship information, Can be obtained.

7 is a view for explaining a data center management method using a server management ontology according to an embodiment of the present invention. In Fig. 7, the data center management method of the data center management apparatus illustrated in Fig. 3 is described as an embodiment.

The data center management apparatus requests the characteristic information about the entity of the data center (S710). The type of the entity and the type of characteristic information to be monitored by the administrator are input to receive the characteristic information request. Depending on the embodiment, the identifier (ID) and the date information of the entity may be further input.

The data center management apparatus searches the database for data matched with the requested characteristic information using the semantic annotation (S720), generates characteristic information using the retrieved data, and outputs the characteristic information (S730). At this time, the semantic annotation includes mapping information for a class of a server management ontology and a column of a database, more specifically, a semantic template including an identifier for a characteristic information class and type information of a class, and a database And a semantic map including column information of the column information.

On the other hand, in step S720, the data center management apparatus identifies the server included in the entity for which the characteristic information is requested by using the relationship information between the entities, and searches the database for data matching with the characteristic information about the identified server have.

The data center management apparatus can further receive status information on the entity, and can generate and output status information using the retrieved characteristic information according to the status information request. The characteristic information and the status information can be output through the display.

8 is a view for explaining a data center management system according to a specific embodiment of the present invention.

As shown in FIG. 8, the data center management system according to the present invention includes a data center 810, a database 820, and a data center management device 830. The data center management apparatus 830 includes an interface unit 840, a knowledge controller 850, and a knowledge expression model 890. The ontology management unit 870 includes an ontology engine 871, an ontology query creator 873, an ontology query creator 873, and an ontology management unit 870. The ontology management unit 870 includes a relation engine 860, an ontology management unit 870, A query builder 875, and an ontology query execution unit 877. The data retrieval unit 880 includes a database engine 881, a semantic annotation mapper 883, a database query builder 885, and a database query execution unit 887. Finally, the knowledge representation model 890 includes a relationship model 891, an ontology model 893, a semantic annotation model 895, and a database metadata model 897.

Here, the relationship engine 860 corresponds to the entity manager 330 described above, and the relationship model 891 corresponds to the relationship information described above. The ontology model 893 corresponds to the server management ontology described above, and the semantic annotation model 895 corresponds to the semantic annotation described in FIG. Finally, the database metadata model provides information about the database 820.

When the characteristic information about the entity is requested through the interface unit 840, the interface unit 840 transmits the kind of the requested entity and the ID information to the relation engine 860. The relationship engine 860 loads the relationship model 891 and returns the requested server, server rack or server column list and ID information.

At this time, since the returned information becomes the instance value of the ontology model, the ontology management unit 870 allocates the ontology model 893 to the memory to create an instance. More specifically, the ontology engine 871 requests the ontology query creator 873 to create an instance, and the ontology query creator 873 loads the ontology model 893 to create an instance. The generated instance is initially assigned a null value and filled in with the necessary information if it is returned or created.

The semantic annotation mapper 883 receives the semantic annotation model 895 and the database metadata 883 from the semantic annotation mapper 883, And returns the column information of the database to the database engine 881 using the model 897. The database query builder 883 generates a query using the returned column information, and the database query execution unit 885 queries the database 820 using the query. The query result, i.e., the requested property information, is returned to the database engine 881.

The ontology engine 871 assigns the property information to the instance, and the ontology query builder 875 generates a query for the state information request. The ontology query execution unit 877 executes the query using the query for the status information, and the ontology management unit 870 generates the status information using the characteristic information and predetermined rules, and then transmits the status information to the interface unit 840 to provide.

9 to 11 are views showing interface screens and output information of a data center management apparatus according to an embodiment of the present invention.

As shown in Fig. 9, the administrator can select the type of entity (server, rack and column) and the ID of the entity through the interface screen. The manager can also select the type of unique characteristic information and the type of sensing characteristic information, and can also request characteristic information by setting a period.

The administrator selects the server rack having the ID 01 as the entity, and when the network speed at 20:00 on September 24, 2013 is selected as the characteristic information, the characteristic information is outputted as shown in FIG.

In addition, the administrator can request necessary state information, and at this time, the threshold value used in the preset rule can be directly set. The result when the administrator requests the idle state information and the replacement candidate state information is shown in Fig. As shown in FIG. 11, state information corresponding to the server corresponding to the state is output together.

The above-described technical features may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

As described above, the present invention has been described with reference to particular embodiments, such as specific elements, and specific embodiments and drawings. However, it should be understood that the present invention is not limited to the above- And various modifications and changes may be made thereto by those skilled in the art to which the present invention pertains. Accordingly, the spirit of the present invention should not be construed as being limited to the embodiments described, and all of the equivalents or equivalents of the claims, as well as the following claims, belong to the scope of the present invention .

Claims (15)

A data center management method using a server management ontology,
Receiving characteristic information about an entity of the data center;
Searching data in the database for data matched with the characteristic information by using a semantic annotation; And
And generating and outputting the characteristic information using the searched data,
The step of searching in the database
Identifying a server included in the entity in which the characteristic information is requested using the relationship information between the entities; And
And searching the database for data matched with the identified characteristic information of the server,
Wherein the server management ontology includes a class for the entity and a class for the property information,
The entity comprising a server, server rack or server row in the data center,
Wherein the relationship information includes information on an inclusion relationship, a connection relationship, and a grouping relationship between the entities
How to manage your data center.
The method according to claim 1,
The semantic annotation
And the mapping information for the class and the columns of the database
How to manage your data center.
3. The method of claim 2,
The semantic annotation
A semantic template including an identifier for the characteristic information class and type information of the class; And
A semantic map including column information of the database corresponding to the identifier
The data center management method comprising:
The method according to claim 1,
The characteristic information
Comprising characteristic information for the entity and sensing characteristic information for the entity
How to manage your data center.
5. The method of claim 4,
The unique characteristic information
Hardware information and network information for the entity,
The sensing characteristic information
And information on the usage amount of the entities, information on the amount of usage of the resources,
How to manage your data center.
delete delete The method according to claim 1,
The retrieved data
An instance value for the class
How to manage your data center.
The method according to claim 1,
Receiving status information on the entity;
Generating the status information using the characteristic information; And
Outputting the status information
Further comprising the steps of:
A data center management apparatus using a server management ontology,
An interface unit for receiving characteristic information about an entity of the data center and outputting the characteristic information; And
And a data retrieval unit for retrieving data matched with the characteristic information using a semantic annotation in a database and generating the characteristic information,
Wherein the server management ontology includes a class for the entity and a class for the property information,
The entity comprising a server, server rack or server row in the data center,
The characteristic information
Specific characteristic information for the entity and sensing characteristic information for the entity,
Wherein the unique characteristic information includes hardware information and network information for the entity,
Wherein the sensing characteristic information includes power usage information, resource usage information, and usage time information for the entity
Data center management device.
11. The method of claim 10,
The semantic annotation
And the mapping information of the class and the column of the database
Data center management device.
12. The method of claim 11,
The semantic annotation
A semantic template including an identifier for the characteristic information class and type information of the class; And
A semantic map including column information of the database corresponding to the identifier
The data center management apparatus comprising:
delete 11. The method of claim 10,
Further comprising an entity management unit for identifying a server included in the entity requested by the characteristic information, using relationship information between the entities,
Wherein the relationship information includes information on an inclusion relationship, a connection relationship, and a grouping relationship between the entities
Data center management device.
11. The method of claim 10,
And an ontology management unit for generating the state information based on the property information using a query for state information of the entity,
The interface unit
Receives the status information, and outputs the status information
Data center management device.

Images