Abstract:
A server storage system comprises a plurality of server resources and a plurality of storage resources. A management system stores allocation control information. The allocation control information represents correspondences among resource types and resource quantities of exclusively allocated server resources and storage resources, resource types and resource quantities of commonly allocated server resources and storage resources, and virtual server load characteristics which are characteristics of virtual server loads. The management system accepts a virtual server creation instruction which is associated with one or more types of load characteristic information which is inputted by a manager and which relates to virtual server load characteristics, and on the basis of the allocation control information and the one or more types of load characteristic information, selects the exclusively allocated server resources and storage resources. The management system allocates the selected resources to a target virtual server. The allocation control information may be modified.
Abstract:
A plurality of multi-purpose diagnostic procedures are associated with a plurality of rules and defined using component types. The rules indicate an association between one or more condition events and a conclusion event. A management system specifies cause candidates based target rules associated with condition events related to the occurrence events, and specifies a multi-purpose diagnostic procedure in association with a target rule that is a basis of a selected cause candidate. The management system creates an expanded diagnostic procedure that is a diagnostic procedure to be performed on one or more management target components for specifying a more specific cause of the selected cause candidate or updating the certainty of the selected cause candidate based on the specified multi-purpose diagnostic procedure and configuration management information that is information about the configuration of a plurality of the management target components.
Abstract:
A migration support system 10 includes a node of a first distributed ledger system built on a blockchain platform 4500, wherein the node 2000 includes: a storage device that holds information on organizations that are allowed to participate in a distributed ledger system on each of blockchain platforms; and a computing device configured to, when the first distributed ledger system is migrated to another blockchain platform to build a second distributed ledger system, record, in a distributed ledger 2500 of the first distributed ledger system, correspondence between organizations participating in the first distributed ledger system and organizations participating in the second distributed ledger system, based on information on organizations that are allowed to participate in each distributed ledger system on the blockchain platform and the other blockchain platform, the information being held in the storage device.
Abstract:
Operation management with consistent policies and timings between nodes even in a situation where there are a plurality of administrators in the distributed ledger system is realized. In an operation management system 10 for a distributed ledger system 6 comprising a plurality of nodes, each of at least two or more predetermined nodes in the plurality of nodes manages an operation smart contract 372 for operation management of the distributed ledger system with a distributed ledger 37, when at least one node in the two or more predetermined nodes receives a transaction, the node which has received the transaction judges whether or not a type of the transaction is the operation smart contract 372, and, based on the judgment result, executes the operation smart contract 372.
Abstract:
In an access authority management system constituting a business network by predetermined business entities, a predetermined node is configured to execute a predetermined smart contract in accordance with contents of a transaction issued along with execution of a predetermined process and stored in a distributed ledger; and execute a predetermined process related to authority management of data access in a distributed ledger by a predetermined node of a participant in the business network based on an execution result of the smart contract.
Abstract:
In a transaction management system which is a distributed ledger system in which a business network is formed of a plurality of nodes, the node calculates an upper limit of the number of transactions that can be issued by each of a plurality of organizations according to a calculation rule shared among the nodes, and refuses to accept the transaction from an organization of the organizations of which the number of transactions in past exceeds the upper limit of the number of transactions.
Abstract:
A distributed ledger system has a configuration in which each of the distributed ledger subsystems includes a sub-ledger that holds ledger data shared in the distributed ledger subsystems, and a smart contract that interlocks between the distributed ledger subsystems having a common sub-ledger to perform a transaction processing related to an input and output of the ledger data, transmits a transaction request targeted for ledger data of another sub-ledger managed by another distributed ledger subsystem to another distributed ledger subsystem having the common sub-ledger by receiving a predetermined transaction request from a predetermined device and executing the smart contract, and replies with a transaction reply obtained from the other distributed ledger subsystem to the predetermined device.
Abstract:
This management system for a computer system including a plurality of resources receives designation of an app usage and refers to management information, which includes information about the plurality of resources. The management system determines, for a target virtual server (a virtual server that executes the app for the designated app usage), at least one of the specification of resources to be allocated for exclusive use and the specification of resources to be allocated for shared use, in accordance with app requirements associated with the designated app usage. The plurality of resources includes a plurality of logical volumes and a plurality of computer resources including a plurality of kinds of computer resources. The computer system includes a server system including two or more computer resources included among the plurality of computer resources. The resource specifications include the kinds of resources, app usages associated with resources, and/or the number of resources.
Abstract:
An exemplary event analysis method generates a topology, indicating a correlation between management objects corresponding to a correlation between events defined in selected event propagation model, from configuration management information. It generates, from the selected event propagation model and the topology, a causality indicating a correlation between the causal event identifying an identifier of the management object and the type of the event, and the derivative event sequentially taking place from the causal event. It, in generating the causality, identifies the type of the management object where the derivative event takes place and the type of the event, without identifying the identifier of the management object where the derivative event takes place, when the topology for identifying the identifier of the derivative event is ungeneratable. It performs an event analysis by comparing the generated causality and the event actually taking place at the management target apparatuses.
Abstract:
A management system manages a plurality of management target devices. A storage device stores one or more rules, plan information, and plan history information. A control device specifies a first cause event that is a candidate of a cause of the event that has occurred in any one of the management target devices based on the one or more rules, specifies a plurality of first plans that can be executed in the case in which the first cause event is a cause based on the plan information, calculates an index value indicating a possibility of succeeding in a failure recovery in the case in which the plan is executed for each of the plurality of first plans based on the plan history information, and displays data indicating any one or more plans of the plurality of first plans according to a display mode decided based on the index value.