WO2009144821A1 - 装置構成情報最適配置方法及び装置構成情報最適配置システム - Google Patents
装置構成情報最適配置方法及び装置構成情報最適配置システム Download PDFInfo
- Publication number
- WO2009144821A1 WO2009144821A1 PCT/JP2008/060057 JP2008060057W WO2009144821A1 WO 2009144821 A1 WO2009144821 A1 WO 2009144821A1 JP 2008060057 W JP2008060057 W JP 2008060057W WO 2009144821 A1 WO2009144821 A1 WO 2009144821A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- configuration information
- device configuration
- management unit
- information management
- unit
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 99
- 238000012545 processing Methods 0.000 claims description 46
- 230000008707 rearrangement Effects 0.000 claims description 23
- 230000002776 aggregation Effects 0.000 claims description 15
- 238000004220 aggregation Methods 0.000 claims description 15
- 230000004044 response Effects 0.000 claims description 14
- 230000008859 change Effects 0.000 claims description 6
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 230000004931 aggregating effect Effects 0.000 claims 1
- 108010047230 Member 1 Subfamily B ATP Binding Cassette Transporter Proteins 0.000 abstract description 19
- 102000004233 multidrug resistance protein 3 Human genes 0.000 abstract description 8
- 108090000743 multidrug resistance protein 3 Proteins 0.000 abstract description 8
- 101100284507 Schizosaccharomyces pombe (strain 972 / ATCC 24843) hdd1 gene Proteins 0.000 abstract description 3
- 102100030306 TBC1 domain family member 9 Human genes 0.000 abstract 1
- 230000008569 process Effects 0.000 description 63
- 102100033350 ATP-dependent translocase ABCB1 Human genes 0.000 description 18
- 101100216234 Schizosaccharomyces pombe (strain 972 / ATCC 24843) cut20 gene Proteins 0.000 description 18
- 108010087367 P-glycoprotein 2 Proteins 0.000 description 14
- 102100039032 Phosphatidylcholine translocator ABCB4 Human genes 0.000 description 14
- 238000010586 diagram Methods 0.000 description 14
- 239000000284 extract Substances 0.000 description 2
- 238000011835 investigation Methods 0.000 description 2
- 101000644682 Homo sapiens Ubiquitin-conjugating enzyme E2 H Proteins 0.000 description 1
- 101100282746 Oryza sativa subsp. japonica GID1 gene Proteins 0.000 description 1
- 101100156295 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) VID30 gene Proteins 0.000 description 1
- 102100020698 Ubiquitin-conjugating enzyme E2 H Human genes 0.000 description 1
- 238000012508 change request Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007480 spreading Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Definitions
- the present invention acquires and integrates device configuration information from a plurality of device configuration information management units, and a device configuration information management unit that manages device configuration information including a component of a device to be managed and a relationship between components.
- the present invention relates to an apparatus configuration information optimal arrangement method and an apparatus configuration information optimal arrangement system in an apparatus configuration information integrated management system including an apparatus configuration information integrated management unit to be managed.
- ITIL registered trademark, Information Technology Infrastructure Library
- CMDB Configuration Management Database
- CI system configuration information
- Configuration Item a device configuration information database
- the system configuration information database is constructed as a database for managing the relationship between the system configuration information and the system configuration information.
- the device configuration of the system includes various elements such as software and various data, not to mention various hardware.
- the implementation of the device configuration information database is called MDR (Management Data Repository). Furthermore, MDR manages the relationship (relationship) between each apparatus configuration information with apparatus configuration information.
- FCMDB Federated CMDB
- FCMDB has a reconciliation function that is a function of mediating device configuration information.
- the reconciliation function integrates the same device configuration information managed with a different name for each MDR or the same device configuration information managed with a different local ID for each MDR.
- the issue is how to efficiently retrieve the target data by cross-searching a plurality of lower-layer databases from the upper-layer database. That is, since the target device configuration information is distributed in a plurality of databases in each lower layer, the search response speed is reduced.
- the database structure and data arrangement of a plurality of databases under a higher-level database are devised, or the database data arrangement is changed to improve search efficiency. It was.
- related device configuration information is summarized so as to be optimally arranged at the time of device configuration information data registration or dynamically (during FCMDB operation). In this way, related device configuration information can be acquired more quickly from each MDR in FCMDB.
- the present invention has been made to solve the above problems (problems), while avoiding the problem of optimal placement investigation, the problem of relationship, the problem of reconciliation, and the problem of the location of device configuration information. It is an object of the present invention to provide an apparatus configuration information optimal arrangement method and apparatus configuration information optimal arrangement system that allow related apparatus configuration information to be acquired more quickly.
- the device configuration information management unit includes a device configuration information management unit that manages the device configuration, and a device configuration information integrated management unit that acquires and manages the device configuration information from a plurality of device configuration information management units.
- the device configuration information optimal arrangement processing unit is a device configuration information managed by a plurality of device configuration information management units. It is a requirement to perform the optimum arrangement by aggregation into a single device configuration information management unit of the device configuration information management unit number.
- the disclosed device configuration information optimum arrangement method and device configuration information optimum arrangement system when the device arrangement information related to each other is aggregated into one MDR based on the mutual relation and the optimum arrangement is performed, one MDR It is possible to acquire all the target device configuration information related to each other only by searching for the device configuration, and it is possible to acquire the device configuration information search result more quickly.
- FIG. 1 is a diagram for explaining an outline and features of an example of an embodiment.
- FIG. 2 is a block diagram illustrating a configuration of an apparatus configuration information integrated management system according to an example of the embodiment.
- FIG. 3 is a diagram illustrating an example of a device configuration information management table.
- FIG. 4 is a diagram illustrating an example of a relationship information management table.
- FIG. 5 is a diagram illustrating an example of the origin information management table.
- FIG. 6 is a diagram illustrating an example of the device configuration information management table.
- FIG. 7 is a diagram illustrating an example of a relationship information management table.
- FIG. 8 is a diagram illustrating an example of the location information management table.
- FIG. 9 is a flowchart showing various processing request execution processing procedures in the apparatus configuration information integrated management system.
- FIG. 9 is a flowchart showing various processing request execution processing procedures in the apparatus configuration information integrated management system.
- FIG. 10 is a flowchart showing the configuration information optimum arrangement processing procedure.
- FIG. 11 is a flowchart illustrating a rearrangement determination processing procedure.
- FIG. 12 is a flowchart showing the rearrangement execution processing procedure.
- FIG. 13 is a flowchart showing the origin management processing procedure.
- FIG. 14 is a diagram for explaining the outline of the origin management process.
- FIG. 15 is a flowchart showing the location management processing procedure.
- FIG. 16 is a diagram for explaining the outline of the location management process.
- FIG. 17 is a flowchart showing a simple registration processing procedure.
- FIG. 18 is a diagram for explaining the outline of the simple registration process.
- FIG. 19 is a flowchart showing the remaining capacity acquisition processing procedure of the MDR information management unit.
- FIG. 20 is a flowchart showing an information acquisition processing procedure.
- FIG. 21 is a diagram for explaining an overview of the information acquisition process.
- Configuration Information Relocation Execution Management Device 101 Allocation Determination Unit 102 Allocation Execution Unit 200 FCMDB 201 Operation Execution Unit 202 FCMDB Information Management Unit 202a Device Configuration Information Management Table 202b Relationship Information Management Table 203 Origin Management Unit 204 Origin Information Management Unit 204a Origin Information Management Table 300a, ..., 300n MDR 301 Operation Execution Unit 302 MDR Information Management Unit 302a Device Configuration Information Management Table 302b Relationship Information Management Table 303a Location Management Unit 303b Simple Registration Unit 303c Remaining Capacity Management Unit 303d Information Acquisition Unit 304 Location Information Management Unit 304a Location Information Management Table
- the MDR manages the device configuration information of a device to be managed
- the FCMDB integrally manages the device configuration information of each MDR.
- FIG. 1 is a diagram for explaining an outline and features of an example of an embodiment.
- the MDRs that the FCMDB is subject to integrated management are MDR1, MDR2, and MDR1.
- the MDR 1 indicates that “server 1” and “server 2” are managed as device configuration information.
- the MDR 2 indicates that “HDD (Hard Disk Drive, hereinafter the same) 1”, “HDD 2”, and “HDD 3” are managed as device configuration information.
- the MDR 3 indicates that “network 1” and “network 2” are managed as device configuration information.
- optimal arrangement of device configuration information related to each other is performed. That is, by moving the device configuration information of “HDD1”, “HDD2”, and “Network1” associated with “Server1” in the relationships “Rel1”, “Rel2”, and “Rel3” to the MDR1 and consolidating them. Optimal placement.
- the apparatus configuration information of “server 2” and “HDD 3” associated with “network 2” in the relationships “Rel 4” and “Rel 5” is moved to the MDR 3 to be optimally arranged.
- the target device related to each other can be obtained only by searching for one MDR. All configuration information can be acquired. Therefore, the turnaround time of the search result can be shortened.
- FIG. 2 is a block diagram illustrating a configuration of an apparatus configuration information integrated management system according to an example of the embodiment.
- the device configuration information integrated management system S includes a configuration information relocation execution management device 100, an FCMDB 200, and MDRs 300a,.
- the configuration information relocation execution management apparatus 100 is connected to the FCMDB 200 and the MDRs 300a,..., 300n, performs apparatus configuration information relocation processing for each MDR, and performs apparatus configuration information relocation management. It is.
- the configuration information rearrangement execution management apparatus 100 includes an arrangement determination unit 101 and an arrangement execution unit 102.
- the arrangement determination unit 101 requests the FCMDB 200 to obtain origin information indicating which device configuration information is managed by which MDR.
- the arrangement execution unit 102 is requested to execute the arrangement of the apparatus configuration information. .
- the arrangement execution unit 102 requests a certain MDR to delete the corresponding device configuration information when moving the device configuration information managed by a certain MDR to another MDR. In addition, it requests other MDRs to simply register the corresponding device configuration information.
- the arrangement execution unit 102 selects, for example, an MDR having the largest remaining capacity of a DB (Data Base, database, the same shall apply hereinafter) in order to determine a destination MDR to which the device configuration information is to be moved. For this purpose, a request for acquiring the remaining capacity of the resource is sent to each MDR.
- DB Data Base, database
- the FCMDB 200 is a device that integrally manages device configuration information managed by each MDR 300a,..., 300n.
- the FCMDB 200 includes an operation execution unit 201 that executes various data operations managed by the FCMDB information management unit 202 described later.
- the FCMDB 200 includes an FCMDB information management unit 202 that virtually integrally manages device configuration information managed by each MDR 300a,..., 300n.
- the FCMDB information management unit 202 stores a device configuration information management table 202a and a relationship information management table 202b.
- the device configuration information management table 202a manages configuration item (CI) information included in the device configuration information for each MDR, as shown in FIG. Further, the relationship information management table 202b manages which configuration item is associated with which configuration item for each relationship, as shown in FIG.
- the FCMDB 200 includes a origin management unit 203 that performs data manipulation of origin information indicating which MDR is managed by each configuration item managed in the device configuration information management table 202a, and origin information that manages origin information. And a management unit 204.
- the origin management unit 203 performs a data operation on the origin information managed by the origin information management unit 204 in response to the origin management request from the operation execution unit 201.
- the origin information management unit 204 stores an origin information management table 204a.
- the origin information management table 204a includes, for example, each configuration item included in the configuration information identified by the “entity ID” that is a globally valid ID in the device configuration information integrated management system S as shown in FIG. Manages the association of which MDR is managed.
- the origin of the configuration item included in the device configuration information whose “entity ID” is “GID (Global ID) 1” is “MDR1% LID1” and “MDR3% LID1”.
- “LID (Local ID)” is an ID that is locally valid in each MDR.
- the origin is “MDR1% LID1” represents “a configuration item of LID1 of MDR1”, and “MDR3% LID1” represents “a configuration item of LID1 of MDR3”.
- the configuration of the MDR will be described on behalf of the MDR 300a.
- the MDR 300a includes an operation execution unit 301 that executes various data operations managed by an MDR information management unit 302 described later.
- the MDR 300a includes an MDR information management unit 302 that manages device configuration information.
- the MDR information management unit 302 stores a device configuration information management table 302a and a relationship information management table 302b.
- the device configuration information management table 302a manages configuration item information managed by the MDR, as shown in FIG. Moreover, the relationship information management table 302b manages the configuration item with the relationship for each configuration item together with the identification information of the MDR in which the configuration item is managed as shown in FIG.
- the MDR 300a includes a location management unit 303a and a simple registration unit 303b that perform data operations on the location information management table 304a in the location information management unit 304 described later in response to a location management request and a simple registration request from the operation execution unit 301. Have.
- the location management unit 303a performs registration, update, deletion, and search of location information. Further, the simple registration unit 303b registers the location information of the device configuration information that has been moved from the other MDR by the optimal arrangement in the location information management table 304a of the location information management unit 304, with the location information itself as the location.
- the location information management unit 304 stores a location information management table 304a for managing the location of the device configuration information.
- the location information management table 304a manages “location” corresponding to “entity ID” as shown in FIG. Specifically, the location of the device configuration information whose “entity ID” is “LID1” is “MDR2% LID1”. “MDR2% LID1” represents “MDR2 LID1 configuration item”.
- FIG. 8 is the location information management table of MDR1
- FIG. 8 shows that “the configuration item of LID1 of MDR1 has been moved to MDR2.”
- 8 shows the location information management table of MDR2
- FIG. 8 shows that “the configuration item of LID1 exists in MDR2 (is not moved anywhere)”.
- the MDR 300a includes a remaining capacity management unit 303c that acquires the remaining capacity of the resource of the MDR information management unit 302 in response to a remaining capacity acquisition request from the operation execution unit 301. Furthermore, the MDR 300a searches for the device configuration information with reference to the device configuration information management table 302a and the relationship information management table 302b of the MDR information management unit 302 in response to the device configuration information acquisition request from the operation execution unit 301. It has the information acquisition part 303d which returns a result.
- the information acquisition unit 303d refers to the location information management table 304a of the location information management unit 304 when the required device configuration information does not exist in the device configuration information management table 302a due to optimal arrangement. Device configuration information is acquired from the previous MDR.
- FIG. 9 is a flowchart showing various processing request execution processing procedures in the apparatus configuration information integrated management system. This process is executed by the FCMDB 200.
- the operation execution unit 201 of the FCMDB 200 receives a processing request from a user (step S1). Subsequently, the operation execution unit 201 determines whether or not the received processing request is a search process (step S2). When it is determined that the received processing request is a search process (Yes at Step S2), the operation execution unit 201 searches the apparatus configuration information for the MDRs 300a,..., 300n (Step S3).
- step S2 if it is not determined that the received processing request is a search process (No in step S2), the processing request is registration / update / deletion of device configuration information, so the operation execution unit 201 sets the MDR 300a,. ... Register / update / delete device configuration information for 300n (step S4).
- step S5 the operation execution unit 201 notifies the configuration information relocation execution management apparatus 100 of the difference before and after the registration / update / deletion of the apparatus configuration information (step S5). Then, the configuration information relocation execution management apparatus 100 that has received the notification of the difference before and after the registration / update / deletion of the device configuration information starts the configuration information optimal allocation process (step S6).
- step S5 ends, the various processing request execution processing ends.
- FIG. 10 is a flowchart showing the configuration information optimum arrangement processing procedure. This process is executed by the configuration information relocation execution management apparatus 100.
- the arrangement determining unit 101 receives a notification of device configuration information difference from the FCMDB 200 (step S101). Subsequently, the arrangement determining unit 101 determines whether or not there is actually a difference in device configuration information (step S102). When it is determined that there is actually a difference in device configuration information (Yes at Step S102), the process proceeds to Step S103, and when it is not determined that there is actually a difference in device configuration information (No at Step S102), the configuration information The optimal placement process ends.
- step S103 the arrangement determination unit 101 performs a rearrangement determination process. Details of the rearrangement determination process will be described later with reference to FIG. Subsequently, the placement determination unit 101 determines whether or not a rearrangement determination target exists (step S104). When it is determined that there is a rearrangement determination target (Yes at Step S104), the process proceeds to Step S105, and when it is not determined that there is a rearrangement determination target (No at Step S104), the configuration information optimal arrangement processing ends. .
- step S105 the placement execution unit 102 performs rearrangement execution processing. Details of the rearrangement execution process will be described later with reference to FIG. When step S105 ends, the configuration information optimal arrangement process ends.
- FIG. 11 is a flowchart illustrating a rearrangement determination processing procedure.
- a set of difference information of the device configuration information is represented by “D”
- an element of “D” is represented by “d”.
- the arrangement determining unit 101 determines whether or not D is empty (empty set) (step S111). When it is determined that D is empty (empty set) (Yes at step S111), the rearrangement determination process ends. On the other hand, when it is not determined that D is empty (empty set) (No at step S111), the process proceeds to step S112.
- the arrangement determining unit 101 determines whether d extracted in step S112 is a configuration item (step S114). When it is determined that d is a configuration item (Yes at Step S114), the process proceeds to Step S115. When d is not determined to be a configuration item (No at Step S114), the process proceeds to Step S116.
- step S115 the arrangement determining unit 101 searches the FCMDB 200 for a set C of configuration items that can be reached by tracing the relationship from d and a set R of the traced relationship.
- step S116 the arrangement determining unit 101 searches the FCMDB 200 for a set C of configuration items that can be reached by tracing the relationship and a set R of the traced relationships for the source and target configuration items of d.
- the arrangement determining unit 101 determines whether or not all the configuration items are derived from the same MDR in the origin information acquired from the FCMDB 200 (step S119). When it is determined that all the configuration items are derived from the same MDR (Yes at Step S119), the rearrangement determination process ends.
- step S119 when it is not determined that all the configuration items are derived from the same MDR (No in step S119), E is set as a relocation target by the arrangement execution unit 102 (step S120). When this process ends, the rearrangement determination process ends.
- FIG. 12 is a flowchart showing the rearrangement execution processing procedure.
- E is a set of related apparatus configuration information
- O is a set of origin information of each element “e” of “E”.
- the placement execution unit 102 issues a remaining capacity acquisition request to all MDRs included in O (step S131). Subsequently, the placement execution unit 102 acquires the remaining capacity of each MDR (step S132).
- the arrangement execution unit 102 determines the MDR having the largest remaining capacity (step S133). The determined MDR is expressed as “m”. Subsequently, the placement execution unit 102 determines whether E is empty (empty set) (step S134). When it is determined that E is empty (empty set) (Yes at step S134), the process returns to the configuration information optimal arrangement process of FIG. On the other hand, when it is not determined that E is empty (empty set) (No at step S134), the process proceeds to step S135.
- step S135 the arrangement execution unit 102 extracts the entity e from E. Subsequently, the arrangement execution unit 102 requests the FCMDB 200 to change origin from e to m (step S136).
- the placement execution unit 102 checks the MDR from which e is derived using O (step S137).
- the MDR from which e is derived is expressed as “r”.
- the arrangement execution unit 102 makes a location change request for changing the location of e to m with respect to r (step S138).
- the arrangement execution unit 102 makes a simple registration request for e to m (step S139).
- the process moves to step S134.
- FIG. 13 is a flowchart showing the origin management processing procedure.
- the operation is expressed as “o”
- the entity ID is expressed as “e”
- the origin information is expressed as “d”.
- the origin management unit 203 of the FCMDB 200 determines whether o is “registration” (step S141). When it is determined that o is “registration” (Yes at step S141), the process proceeds to step S142. When o is not determined to be “registration” (No at step S141), the process proceeds to step S143.
- step S142 the origin management unit 203 registers d in the origin information management table 204a as origin information whose entity ID is e.
- step S143 the origin management unit 203 determines whether o is “update”. When it is determined that o is “update” (Yes at step S143), the process proceeds to step S144. When o is not determined to be “update” (No at step S143), the process proceeds to step S145.
- step S144 the origin management unit 203 updates the origin information whose entity ID is e in the origin information management table 204a with d.
- step S145 the origin management unit 203 determines whether o is “delete”. When it is determined that “o” is “delete” (Yes at Step S145), the process proceeds to Step S146. When o is not determined to be “Delete” (No at Step S145), the process proceeds to Step S147.
- step S146 the origin management unit 203 deletes the origin information whose entity ID is e from the origin information management table 204a.
- step S147 since it can be determined that o is a search request, the origin information whose entity ID is e is searched.
- MDR 3% LID1 which is the origin information of the entity ID “GID1”
- MDR2% LID1 which is the origin information of the entity ID “GID3”
- MDR1% LID4 and “MDR1% LID3”. Note that the LID numbers in each MDR are assigned in the order of rearrangement.
- the apparatus configuration information search processing speed can be improved by collecting and arranging the apparatus configuration information having the relationship in the same MDR.
- FIG. 15 is a flowchart showing the location management processing procedure.
- the operation is expressed as “o”
- the entity ID is expressed as “e”
- the location information is expressed as “d”.
- the location management unit 303a of the MDR 300a determines whether o is “registration” (step S151). When it is determined that o is “registration” (Yes at step S151), the process proceeds to step S152. When o is not determined to be “registration” (No at step S151), the process proceeds to step S153.
- step S152 the location management unit 303a registers d in the location information management table 304a as location information having an entity ID of e.
- step S153 the location management unit 303a determines whether o is “update”. When it is determined that o is “update” (Yes at Step S153), the process proceeds to Step S154, and when o is not determined to be “Update” (No at Step S153), the process proceeds to Step S155.
- step S154 the location management unit 303a updates the location information whose entity ID is e in the location information management table 304a with d.
- step S155 the location management unit 303a determines whether o is “delete”. When it is determined that o is “delete” (Yes at step S155), the process proceeds to step S156. When o is not determined to be “delete” (No at step S155), the process proceeds to step S157.
- step S156 the location management unit 303a deletes the location information whose entity ID is e from the location information management table 304a.
- step S157 since it can be determined that o is a search request, the location information whose entity ID is e is searched.
- the configuration information whose entity ID managed by MDR2 is “LID1” has been moved to MDR1, so that the entity ID in the location management information of MDR2 is changed.
- the location information of “LID1” is updated from “MDR2% LID1” to “MDR1% LID3”. In this way, even when device configuration information having a relationship is moved to be aggregated and arranged in the same MDR, the movement destination is managed by referring to the location information management table 304a. It becomes possible to grasp.
- FIG. 17 is a flowchart showing a simple registration processing procedure.
- the device configuration information is represented as “d”.
- the simple registration unit 303b of the MDR 300a generates an entity ID of d (step S161).
- the simple registration unit 303b registers d in the MDR information management unit 302 (device configuration information management table 302a and relationship information management table 302b) (step S162). Subsequently, the simple registration unit 303b registers the location of d as the MDR 300a itself in the location information management table 304a (step S163).
- the device configuration information (configuration item) newly registered or moved from another MDR to MDR1 is unique to the entity ID in MDR1. Is granted. Then, for example, “MDR1% LID10” is newly registered in the location information management table 304a as the location information of the device configuration information to which the entity ID “LID10” is assigned.
- the apparatus configuration information moved to be collectively arranged in the same MDR can be managed by the location information management table 304a in the same manner as the apparatus configuration information previously entered. .
- FIG. 19 is a flowchart showing the remaining capacity acquisition processing procedure of the MDR information management unit.
- the operation execution unit 301 of the MDR 300a determines whether or not the remaining capacity acquisition request of the MDR information management unit 302 has been received from the arrangement execution unit 102 of the configuration information relocation execution management apparatus 100 (step S171).
- Step S171 When it is determined that the remaining capacity acquisition request of the MDR information management unit 302 has been received (Yes at Step S171), the process proceeds to Step S172, and when it is not determined that the remaining capacity acquisition request of the MDR information management unit 302 has been received (Step S171). (No at S171), step S171 is repeated.
- step S172 the operation execution unit 301 instructs the remaining capacity management unit 303c to acquire the remaining capacity of the MDR information management unit 302.
- the remaining capacity management unit 303c acquires the remaining capacity of the MDR information management unit 302 and notifies the operation execution unit 301 (step S172).
- the operation execution unit 301 notifies the requesting arrangement execution unit 102 of the remaining capacity of the MDR information management unit 302 notified from the remaining capacity management unit 303c (step S173).
- the remaining capacity acquisition process of the MDR information management unit ends.
- FIG. 20 is a flowchart showing an information acquisition processing procedure.
- the information acquisition process is a process executed by the information acquisition unit 303d instructed by the operation execution unit 301 of the MDR 300a in response to a device configuration information search request from the FCMDB 200.
- the entity ID is expressed as “e”.
- the information acquisition unit 303d refers to the location information management table 304a of the location information management unit 304 and acquires the location information p of the device configuration information whose entity ID is e (step S181). Subsequently, the information acquisition unit 303d determines whether or not p acquired in step S181 indicates its own MDR (step S182). When it is determined that p indicates its own MDR (Yes at Step S182), the process proceeds to Step S183, and when it is not determined that p indicates its own MDR (No at Step S182), the process proceeds to Step S184.
- step S183 the information acquisition unit 303d refers to the device configuration information management table 302a of the MDR information management unit 302 and acquires the device configuration information i having the entity ID e.
- step S184 the information acquisition unit 303d refers to the location information management table 304a and acquires the device configuration information i corresponding to p from the MDR registered as the location information of p.
- step S183 or step S184 the information acquisition unit 303d returns the device configuration information i acquired in step S183 or step S184 to the FCMDB 200 via the operation execution unit 301 (step S185).
- the entity ID of MDR1 is “LID1”. It can be seen that the device configuration information “” can be acquired from the MDR 1. In addition, the device configuration information whose entity ID of MDR1 is “LID10” has been moved to MDR2, but since the location information is clear, it can be obtained from MDR2.
- the movement destination MDR of the device configuration information before movement and the entity ID in the movement destination MDR are managed. Even if the MDR is searched, it is possible to refer to the moved apparatus configuration information and to avoid the occurrence of a search miss hit.
- the FCMDB 200 can investigate or change which MDR originates from the outside of the registered device configuration information. Further, the optimum arrangement of the device configuration information can be performed from the outside. Further, only the location of information can be changed for the registered device configuration information. Further, the apparatus configuration information can be moved efficiently (at high speed) between the MDRs.
- the MDR 300a can manage the destination of movement when the registered device configuration information is moved. Also, it can be seen where the registered device configuration information currently exists. Also, device configuration information can be registered without reconciling (inquiring).
- Device configuration information between MDRs is determined by determining the optimal arrangement, examining device configuration information related to the distributed device configuration information (having relationships), and determining the MDR to which the related information is gathered Can be moved efficiently (at high speed).
- the configuration information rearrangement execution management device 100 is an external device of the FCMDB 200, but is not limited thereto, and may be a configuration included in the FCMDB 200.
- the remaining capacity of the resource is adopted as a criterion for determining the MDR that aggregates the device configuration information based on the relationship.
- the present invention is not limited to this, and other criteria such as resource access performance are used. May be adopted.
- all or part of the processes described as being automatically performed can be manually performed, or have been described as being manually performed. All or a part of the processing can be automatically performed by a known method.
- the processing procedure, the control procedure, the specific name, and information including various data and parameters shown in the exemplary embodiment can be arbitrarily changed unless otherwise specified.
- each component of each illustrated apparatus is functionally conceptual and does not necessarily need to be physically configured as illustrated. That is, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured.
- each processing function performed in each device is a CPU (Central Processing Unit) (or a microcomputer such as an MPU (Micro Processing Unit) or MCU (Micro Controller Unit)) and It may be realized by a program that is analyzed and executed by a CPU (or a microcomputer such as an MPU or MCU), or may be realized as hardware by wired logic.
- CPU Central Processing Unit
- MPU Micro Processing Unit
- MCU Micro Controller Unit
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
101 配置判定部
102 配置実行部
200 FCMDB
201 操作実行部
202 FCMDB情報管理部
202a 装置構成情報管理テーブル
202b リレーションシップ情報管理テーブル
203 由来管理部
204 由来情報管理部
204a 由来情報管理テーブル
300a、・・・、300n MDR
301 操作実行部
302 MDR情報管理部
302a 装置構成情報管理テーブル
302b リレーションシップ情報管理テーブル
303a 所在管理部
303b 簡易登録部
303c 残容量管理部
303d 情報取得部
304 所在情報管理部
304a 所在情報管理テーブル
Claims (16)
- 管理対象である装置の構成要素及び構成要素間の関連を含む装置構成情報を管理する装置構成情報管理部と、複数の前記装置構成情報管理部から前記装置構成情報を取得して統合管理する装置構成情報統合管理部とを含む装置構成情報統合管理システムにおける装置構成情報最適配置方法であって、
前記装置構成情報管理部が、管理対象装置の構成要素及び前記構成要素間の関連を含む装置構成情報を管理する装置構成情報管理ステップと、
前記装置構成情報統合管理部が、複数の前記装置構成情報管理部によって管理される前記装置構成情報を統合管理する装置構成情報統合管理ステップと、
装置構成情報最適配置処理部が、複数の前記装置構成情報管理部における前記装置構成情報管理ステップによって管理される前記装置構成情報のうち、前記構成要素間の関連がある装置構成情報を、複数の前記装置構成情報管理部のうちの一つの装置構成情報管理部に集約して最適配置を行う装置構成情報最適配置処理ステップと
を含むことを特徴とする装置構成情報最適配置方法。 - 前記装置構成情報最適配置処理ステップは、
前記装置構成情報管理部において、前記構成要素が新規登録、更新又は削除されたことによって前記装置構成情報に差分が生じたことを契機として、該装置構成情報の最適配置の必要性の有無を判定する再配置判定ステップと、
前記再配置判定ステップによって、前記装置構成情報の最適配置の必要性有りと判定された場合に、複数の前記装置構成情報管理部のうちの一つの装置構成情報管理部に、前記装置構成情報を集約して最適配置を行う配置実行ステップと
をさらに含むことを特徴とする請求項1記載の装置構成情報最適配置方法。 - 前記装置構成情報統合管理ステップは、統合管理対象の前記装置構成情報が、いずれの前記装置構成情報管理部によって管理されているかを識別する由来情報を管理する由来情報管理ステップをさらに含み、
前記再配置判定ステップは、前記由来情報管理ステップによって管理される前記由来情報が異なる装置構成情報が存在する場合に、該装置構成情報の最適配置の必要性有りと判定することを特徴とする請求項2記載の装置構成情報最適配置方法。 - 前記配置実行ステップは、前記装置構成情報を集約して最適配置を行う場合に、前記由来情報管理ステップに対して、該由来情報管理ステップによって管理される前記装置構成情報の由来情報を集約先の装置構成情報管理部へと変更する様に要求し、
前記由来情報管理ステップは、前記配置実行ステップからの前記由来情報の前記要求に応じて、前記装置構成情報の由来情報を集約先の装置構成情報管理部へと変更することを特徴とする請求項3記載の装置構成情報最適配置方法。 - 前記装置構成情報管理ステップは、前記装置構成情報の管理資源の状況を管理する管理資源状況管理ステップをさらに含み、
前記配置実行ステップは、最適配置を行う対象の前記装置構成情報を管理する各前記装置構成情報管理部における前記管理資源状況管理ステップに対して前記管理資源の状況報告を要求し、各前記装置構成情報管理部における前記管理資源状況管理ステップからの前記管理資源の状況報告に応じて、前記装置構成情報を集約して最適配置を行う装置構成情報管理部を決定することを特徴とする請求項2記載の装置構成情報最適配置方法。 - 前記装置構成情報管理ステップは、管理対象の前記装置構成情報が、いずれの前記装置構成情報管理部によって管理されているかを識別する所在情報を管理する所在情報管理ステップをさらに含み、
前記配置実行ステップは、前記装置構成情報を集約して最適配置を行う場合に、該当する装置構成情報を管理する前記装置構成情報管理部における所在情報管理ステップに対して、所在情報管理部によって管理される装置構成情報の所在情報を集約先の装置構成情報管理部へと変更する様に要求し、
前記所在情報管理ステップは、前記配置実行ステップからの前記所在情報の前記要求に応じて、前記装置構成情報の所在情報を集約先の装置構成情報管理部へと変更することを特徴とする請求項2記載の装置構成情報最適配置方法。 - 前記装置構成情報管理ステップは、前記装置構成情報を集約して最適配置を行う場合に、集約によって最適配置される装置構成情報を簡易登録する簡易登録ステップをさらに含み、
前記配置実行ステップは、前記装置構成情報を集約して最適配置を行う場合に、集約先の装置構成情報管理部における装置構成情報管理ステップに対して、集約によって最適配置される装置構成情報の簡易登録を要求し、
前記簡易登録ステップは、前記配置実行ステップからの前記要求に応じて、該当する装置構成情報を前記集約先の装置構成情報管理部の所在情報管理部に簡易登録することを特徴とする請求項6記載の装置構成情報最適配置方法。 - 前記装置構成情報管理ステップは、ユーザからの前記装置構成情報の取得要求に応じて、前記所在情報管理ステップによって管理される前記所在情報に基づき、自装置又は他の装置の前記構成情報管理部から、該当する装置構成情報を取得する情報取得ステップをさらに含むことを特徴とする請求項6記載の装置構成情報最適配置方法。
- 管理対象装置の構成要素及び前記構成要素間の関連を含む装置構成情報を管理する装置構成情報管理部と、
複数の前記装置構成情報管理部によって管理される前記装置構成情報を統合管理する装置構成情報統合管理部と、
複数の前記装置構成情報管理部によって管理される前記装置構成情報のうち、前記構成要素間の関連がある装置構成情報を、複数の前記装置構成情報管理部のうちの一つの装置構成情報管理部に集約して最適配置を行う装置構成情報最適配置処理部と
を有することを特徴とする装置構成情報最適配置システム。 - 前記装置構成情報最適配置処理部は、
前記装置構成情報管理部において、前記構成要素が新規登録、更新又は削除されたことによって前記装置構成情報に差分が生じたことを契機として、該装置構成情報の最適配置の必要性の有無を判定する再配置判定部と、
前記再配置判定部によって、前記装置構成情報の最適配置の必要性有りと判定された場合に、複数の前記装置構成情報管理部のうちの一つの装置構成情報管理部に、前記装置構成情報を集約して最適配置を行う配置実行部と
をさらに有することを特徴とする請求項9記載の装置構成情報最適配置システム。 - 前記装置構成情報統合管理部は、統合管理対象の前記装置構成情報が、いずれの前記装置構成情報管理部によって管理されているかを識別する由来情報を管理する由来情報管理部をさらに有し、
前記再配置判定部は、前記由来情報管理部によって管理される前記由来情報が異なる装置構成情報が存在する場合に、該装置構成情報の最適配置の必要性有りと判定することを特徴とする請求項10記載の装置構成情報最適配置システム。 - 前記配置実行部は、前記装置構成情報を集約して最適配置を行う場合に、前記由来情報管理部に対して、該由来情報管理部によって管理される前記装置構成情報の由来情報を集約先の装置構成情報管理部へと変更する様に要求し、
前記由来情報管理部は、前記配置実行部からの前記由来情報の前記要求に応じて、前記装置構成情報の由来情報を集約先の装置構成情報管理部へと変更することを特徴とする請求項11記載の装置構成情報最適配置システム。 - 前記装置構成情報管理部は、前記装置構成情報の管理資源の状況を管理する管理資源状況管理部をさらに有し、
前記配置実行部は、最適配置を行う対象の前記装置構成情報を管理する各前記装置構成情報管理部の前記管理資源状況管理部に対して前記管理資源の状況報告を要求し、各前記装置構成情報管理部の前記管理資源状況管理部からの前記管理資源の状況報告に応じて、前記装置構成情報を集約して最適配置を行う装置構成情報管理部を決定することを特徴とする請求項10記載の装置構成情報最適配置システム。 - 前記装置構成情報管理部は、管理対象の前記装置構成情報が、いずれの前記装置構成情報管理部によって管理されているかを識別する所在情報を管理する所在情報管理部をさらに有し、
前記配置実行部は、前記装置構成情報を集約して最適配置を行う場合に、該当する装置構成情報を管理する前記装置構成情報管理部の所在情報管理部に対して、該所在情報管理部によって管理される装置構成情報の所在情報を集約先の装置構成情報管理部へと変更する様に要求し、
前記所在情報管理部は、前記配置実行部からの前記所在情報の前記要求に応じて、前記装置構成情報の所在情報を集約先の装置構成情報管理部へと変更することを特徴とする請求項10記載の装置構成情報最適配置システム。 - 前記装置構成情報管理部は、前記装置構成情報を集約して最適配置を行う場合に、集約によって最適配置される装置構成情報を簡易登録する簡易登録部をさらに有し、
前記配置実行部は、前記装置構成情報を集約して最適配置を行う場合に、集約先の装置構成情報管理部に対して、集約によって最適配置される装置構成情報の簡易登録を要求し、
前記簡易登録部は、前記配置実行部からの前記要求に応じて、該当する装置構成情報を前記集約先の装置構成情報管理部の所在情報管理部に簡易登録することを特徴とする請求項14記載の装置構成情報最適配置システム。 - 前記装置構成情報管理部は、ユーザからの装置構成情報の取得要求に応じて、前記所在情報管理部によって管理される前記所在情報に基づき、自装置又は他の装置の装置構成情報管理部から該当する装置構成情報を取得する情報取得部をさらに有することを特徴とする請求項14記載の装置構成情報最適配置システム。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2008/060057 WO2009144821A1 (ja) | 2008-05-30 | 2008-05-30 | 装置構成情報最適配置方法及び装置構成情報最適配置システム |
JP2010514313A JP5120451B2 (ja) | 2008-05-30 | 2008-05-30 | 配置方法及び配置システム |
GB1020167.1A GB2474145B (en) | 2008-05-30 | 2008-05-30 | Device-configuration-information optimum arrangement method and device-configuration-information optimum arrangement system |
US12/955,557 US8209440B2 (en) | 2008-05-30 | 2010-11-29 | Device-configuration-information optimum arrangement method and device-configuration-information optimum arrangement system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2008/060057 WO2009144821A1 (ja) | 2008-05-30 | 2008-05-30 | 装置構成情報最適配置方法及び装置構成情報最適配置システム |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/955,557 Continuation US8209440B2 (en) | 2008-05-30 | 2010-11-29 | Device-configuration-information optimum arrangement method and device-configuration-information optimum arrangement system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009144821A1 true WO2009144821A1 (ja) | 2009-12-03 |
Family
ID=41376720
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2008/060057 WO2009144821A1 (ja) | 2008-05-30 | 2008-05-30 | 装置構成情報最適配置方法及び装置構成情報最適配置システム |
Country Status (4)
Country | Link |
---|---|
US (1) | US8209440B2 (ja) |
JP (1) | JP5120451B2 (ja) |
GB (1) | GB2474145B (ja) |
WO (1) | WO2009144821A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011134005A (ja) * | 2009-12-22 | 2011-07-07 | Fujitsu Ltd | 構成情報管理装置、分散情報管理システム、分散情報管理方法および分散情報管理プログラム |
JP2011133985A (ja) * | 2009-12-22 | 2011-07-07 | Fujitsu Ltd | 構成情報管理システム、構成情報管理方法、分散情報管理装置及び分散情報管理プログラム |
JP2011150545A (ja) * | 2010-01-21 | 2011-08-04 | Fujitsu Ltd | 構成情報管理装置、分散情報管理システム、分散情報管理方法および分散情報管理プログラム |
JP2011197808A (ja) * | 2010-03-17 | 2011-10-06 | Fujitsu Ltd | 構成情報管理装置、構成情報管理プログラム及び構成情報管理方法 |
JP2012053534A (ja) * | 2010-08-31 | 2012-03-15 | Hitachi Information Systems Ltd | 分散構成管理データベースシステム及び分散構成データ管理方法 |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009122527A1 (ja) * | 2008-03-31 | 2009-10-08 | 富士通株式会社 | 装置構成情報管理装置へ情報の更新系処理を行なう仮想統合管理装置 |
GB2473572A (en) * | 2008-07-04 | 2011-03-16 | Fujitsu Ltd | Information processor, information processing program, information processing method |
CN109359013A (zh) * | 2018-10-24 | 2019-02-19 | 郑州云海信息技术有限公司 | 一种主机管理特性测试方法、装置、设备及存储介质 |
CN117579485B (zh) * | 2024-01-12 | 2024-04-09 | 腾讯科技(深圳)有限公司 | 配置变更方法、装置、设备和存储介质 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0512338A (ja) * | 1991-07-05 | 1993-01-22 | Nec Corp | 分散データベースのデータ配置方式 |
JP2004296045A (ja) * | 2003-03-28 | 2004-10-21 | Fuji Photo Film Co Ltd | データ記録制御方法及びデータ記録装置 |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2001390C (en) | 1988-12-19 | 1997-12-30 | Ming-Chien Shan | View composition in a data-base management system |
CA2124720C (en) * | 1993-06-25 | 2002-10-22 | Michael R. C. Seaman | Integration of systems management services with an underlying system object model |
JP2000148549A (ja) * | 1998-11-16 | 2000-05-30 | Fujitsu Ltd | データ格納管理装置 |
ATE343817T1 (de) * | 2003-04-23 | 2006-11-15 | Comptel Corp | Ereignisvermittlung |
US7233957B1 (en) * | 2003-09-30 | 2007-06-19 | Emc Corporation | Method and apparatus for identifying and processing changes to management information |
US9137115B2 (en) * | 2004-12-06 | 2015-09-15 | Bmc Software, Inc. | System and method for resource reconciliation in an enterprise management system |
US20080059943A1 (en) * | 2006-08-30 | 2008-03-06 | Vadym Krevs | Method and system for using a library cache in a distributed development environment |
WO2009096030A2 (ja) * | 2008-01-31 | 2009-08-06 | Fujitsu Limited | 装置構成統合情報管理プログラム、装置構成情報管理プログラム、装置構成統合情報管理装置および装置構成情報管理装置 |
US9098555B2 (en) * | 2008-11-25 | 2015-08-04 | Dell Products L.P. | Method and system for health scoring information systems, users, and updates |
US10831724B2 (en) * | 2008-12-19 | 2020-11-10 | Bmc Software, Inc. | Method of reconciling resources in the metadata hierarchy |
US8380749B2 (en) * | 2009-01-14 | 2013-02-19 | Bmc Software, Inc. | MDR federation facility for CMDBf |
-
2008
- 2008-05-30 JP JP2010514313A patent/JP5120451B2/ja not_active Expired - Fee Related
- 2008-05-30 WO PCT/JP2008/060057 patent/WO2009144821A1/ja active Application Filing
- 2008-05-30 GB GB1020167.1A patent/GB2474145B/en not_active Expired - Fee Related
-
2010
- 2010-11-29 US US12/955,557 patent/US8209440B2/en not_active Expired - Fee Related
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0512338A (ja) * | 1991-07-05 | 1993-01-22 | Nec Corp | 分散データベースのデータ配置方式 |
JP2004296045A (ja) * | 2003-03-28 | 2004-10-21 | Fuji Photo Film Co Ltd | データ記録制御方法及びデータ記録装置 |
Non-Patent Citations (2)
Title |
---|
"Bunsan Database toshite", 19 March 2002 (2002-03-19), Retrieved from the Internet <URL:http://www.icot.or.jp/ARCHIVE/Museum/SOFTWARE/KAPPA/dist.html> [retrieved on 20080730] * |
SHUICHI OWA: "Process Base no IT Zenpan Tosei o Jitsugen ITILv3 ni Motozuite Jissen suru IT Service Management", COMPUTERWORLD, 1 December 2007 (2007-12-01), pages 70 - 75 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2011134005A (ja) * | 2009-12-22 | 2011-07-07 | Fujitsu Ltd | 構成情報管理装置、分散情報管理システム、分散情報管理方法および分散情報管理プログラム |
JP2011133985A (ja) * | 2009-12-22 | 2011-07-07 | Fujitsu Ltd | 構成情報管理システム、構成情報管理方法、分散情報管理装置及び分散情報管理プログラム |
JP2011150545A (ja) * | 2010-01-21 | 2011-08-04 | Fujitsu Ltd | 構成情報管理装置、分散情報管理システム、分散情報管理方法および分散情報管理プログラム |
JP2011197808A (ja) * | 2010-03-17 | 2011-10-06 | Fujitsu Ltd | 構成情報管理装置、構成情報管理プログラム及び構成情報管理方法 |
JP2012053534A (ja) * | 2010-08-31 | 2012-03-15 | Hitachi Information Systems Ltd | 分散構成管理データベースシステム及び分散構成データ管理方法 |
Also Published As
Publication number | Publication date |
---|---|
GB2474145B (en) | 2013-02-20 |
US8209440B2 (en) | 2012-06-26 |
JP5120451B2 (ja) | 2013-01-16 |
JPWO2009144821A1 (ja) | 2011-09-29 |
GB201020167D0 (en) | 2011-01-12 |
GB2474145A (en) | 2011-04-06 |
US20110072165A1 (en) | 2011-03-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5120451B2 (ja) | 配置方法及び配置システム | |
US11500875B2 (en) | Multi-partitioning for combination operations | |
US11494380B2 (en) | Management of distributed computing framework components in a data fabric service system | |
US11615087B2 (en) | Search time estimate in a data intake and query system | |
US11966391B2 (en) | Using worker nodes to process results of a subquery | |
US11321321B2 (en) | Record expansion and reduction based on a processing task in a data intake and query system | |
US11341131B2 (en) | Query scheduling based on a query-resource allocation and resource availability | |
US11442935B2 (en) | Determining a record generation estimate of a processing task | |
US11580107B2 (en) | Bucket data distribution for exporting data to worker nodes | |
US11593377B2 (en) | Assigning processing tasks in a data intake and query system | |
US11586627B2 (en) | Partitioning and reducing records at ingest of a worker node | |
US11314753B2 (en) | Execution of a query received from a data intake and query system | |
US11023463B2 (en) | Converting and modifying a subquery for an external data system | |
US11243963B2 (en) | Distributing partial results to worker nodes from an external data system | |
US11126632B2 (en) | Subquery generation based on search configuration data from an external data system | |
US11663227B2 (en) | Generating a subquery for a distinct data intake and query system | |
US11151137B2 (en) | Multi-partition operation in combination operations | |
US20200050612A1 (en) | Supporting additional query languages through distributed execution of query engines | |
US20200065303A1 (en) | Addressing memory limits for partition tracking among worker nodes | |
US20200050586A1 (en) | Query execution at a remote heterogeneous data store of a data fabric service | |
US20190138638A1 (en) | Task distribution in an execution node of a distributed execution environment | |
US20190138641A1 (en) | Subquery generation based on a data ingest estimate of an external data system | |
WO2020027867A1 (en) | Generating a subquery for a distinct data intake and query system | |
JP2018124658A (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: 08764925 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010514313 Country of ref document: JP |
|
ENP | Entry into the national phase |
Ref document number: 1020167 Country of ref document: GB Kind code of ref document: A Free format text: PCT FILING DATE = 20080530 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020167.1 Country of ref document: GB |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 08764925 Country of ref document: EP Kind code of ref document: A1 |