[Technical Field]
[0001]
The present invention relates to a cloud-configuration storage system, a cloudconfiguration
storage method and a cloud-configuration storage program suitable for
acquiring a configuration information of a cloud environment as of an arbitrary point of
time, and managing a history thereof.
[Background Art]
[0002]
Recently, in the field of computer technology, a service of constructing a cloud
environment using a combination of various virtualization techniques and providing the
constructed cloud environment to users is spreading rapidly. In the cloud environment,
it is necessary to allow the configuration to be apprehended, and since the
configuration changes dynamically, it is necessary to store the information before and
after the change to correspond to occurrence of failure or to improve performance.
[0003]
Techniques disclosed in Patent Literatures 1 and 2 are examples of documents
related to the above-described art. Patent Literature 1 discloses an art of generating a
logical topology information of a virtual network related to a virtual network composed of
virtualization techniques including a virtual LAN, a virtual interface, and a virtual router.
Therefore, according to the art disclosed in Patent Literature 1, (1) a setting pattern
related to the generation of multiple kinds of virtual resources and a setting pattern
related to connections between the multiple kinds of virtual resources are extracted
from setting information (configuration) on network apparatuses constituting the virtual
network; (2) identifiers necessary to generate the virtual resources, or to generate
connection relations between the virtual resources are extracted from the extracted
setting pattern; (3) configuration components of a logical topology corresponding to the
virtual resources or connections between the virtual resources are generated by using
information which includes the extracted identifiers; and (4) the generated configuration
components of individual logical topologies are integrated to generate logical topology
information expressed as one topology, the information of which is stored in a storage.
[0004]
The art disclosed in Patent Literature 2 provides a configuration information
acquisition method in a cloud environment which implements an efficient monitoring
operation while reducing the amount of data to be handled, by reducing a load to a
physical server to be monitored in a system of the cloud environment, and an
apparatus for implementing the method. The art of Patent Literature 2 includes the
steps of collecting a mirrored packet from packets flowing between a plurality of virtual
2
machines, analyzing traffic/route information from the collected packet; determining
whether a corresponding relationship between a physical server and the virtual
machines is changed, as a result of the analysis; instructing a monitoring device which
monitors an entire configuration, to acquire configuration information when it is
recognized that the corresponding relationship is changed; and acquiring and storing
the configuration information in the monitoring device after the change.
[Citation List]
[Patent Literature]
[0005]
[PTL 1] Japanese Unexamined Patent Application Publication No 2013-081053
[PTL 2] Japanese Unexamined Patent Application Publication No. 2012-004781
[Summary of Invention]
[Technical Problem]
[0006]
According to the aforementioned technique, in a state where an infrastructure
is constructed using a cloud environment of a plurality of cloud service providers, a
large number of configuration changes occur in a short time, since the change of
system configuration can be performed easily in a short time. Further, some cloud
services are provided with a function to change a number of virtual servers
automatically. Therefore, it is difficult to apprehend a configuration information as of a
specific point of time compared to an on-premise environment where configuration
change is not frequently performed.
[0007]
Therefore, much time was required to specify and take measures against
failure that has occurred immediately after the cloud environment has been changed.
Further, since a history of the cloud environment cannot be stored, there was a problem
in that a truly preferable cloud configuration capable of comparing a past cloud
environment and a cloud environment after the change could not be constructed. Thus,
the object of the present invention is to provide a system capable of apprehending a
configuration of the cloud environment and storing a configuration change history.
[Solution to Problem]
[0008]
In order to solve the problems described above, a cloud-configuration storage
system according to one typical aspect of the present invention is configured to connect
to one or more cloud service provision systems providing a cloud service, the system
including a client apparatus and a server apparatus, the client apparatus including a
cloud connection information reception part configured to receive a cloud connection
information constructing a cloud environment from a user, a configuration storage
processing part configured to receive designation of the cloud environment to be stored,
and a configuration history display processing part configured to perform display control
of a configuration history of the cloud environment being stored, the server apparatus
3
including a cloud connection information part configured to store and register the cloud
connection information received by the cloud connection information reception part of
the client apparatus in a cloud connection information DB, a configuration information
acquisition processing part configured to acquire the cloud configuration information
constructed in the cloud service provision system from the cloud service provision
system according to a cloud configuration information acquisition request from the
configuration display processing part of the client apparatus, a cloud configuration
history DB configured to store the configuration information being acquired as a
configuration history information, and a configuration history acquisition processing part
configured to acquire a configuration history information from the cloud configuration
history DB. The configuration storage processing part having received a cloud
configuration storage command from the user is configured to extract a cloud ID for
acquiring cloud configuration information from the cloud configuration display request
command, and transmit the configuration display command of the extracted cloud ID to
the configuration information acquisition processing part, wherein the configuration
information acquisition processing part is configured to acquire a cloud connection
information from the cloud connection information DB based on the cloud ID, specify a
cloud service provision system acquiring the cloud configuration information based on
the acquired cloud connection information, and acquire the cloud configuration
information from the specified cloud service provision system and store the information
in the cloud configuration history DB, and wherein the configuration history display
processing part is configured to acquire a configuration history from the configuration
information acquisition processing part based on a cloud information whose
configuration is to be displayed received from the user, generate a cloud configuration
diagram using a configuration component icon corresponding to each configuration
element and a connection information based on the configuration history being
acquired, and display the cloud configuration diagram being generated on the screen.
[Advantageous Effects of Invention]
[0009]
According to the present cloud-configuration storage system, configuration
information on the cloud service can be acquired from the cloud service provider either
periodically or when a change occurs, and stored in the configuration history DB.
Therefore, a configuration information as of a specific point of time can be referred to,
and replication of a cloud configuration of a current point of time or restoration of a past
cloud configuration is enabled, and specification of cause of failure or specification of a
performance bottleneck portion is enabled. The problems, configurations and effects
other than those described above will become apparent based on the following
description of embodiments.
[Brief Description of Drawings]
[0010]
4
[FIG. 1] FIG. 1 is a view illustrating an outline of invention in a cloud-configuration
storage system according to one embodiment of the present invention.
[FIG. 2] FIG. 2 is a view illustrating an entire configuration of a system using the cloudconfiguration
storage system according to one embodiment of the present invention.
[FIG. 3] FIG. 3 is a block diagram illustrating an internal configuration of a client PC
(client terminal).
[FIG. 4] FIG. 4 is a block diagram illustrating an internal configuration of a physical
server.
[FIG. 5] FIG. 5 is a view illustrating a configuration example of a cloud connection
information.
[FIG. 6] FIG. 6 is a view illustrating a configuration example of a cloud service
configuration information.
[FIG. 7] FIG. 7 is a view illustrating a configuration example of a cloud configuration
history table.
[FIG. 8] FIG. 8 is a view illustrating a configuration example of a cloud configuration
component history table.
[FIG. 9] FIG. 9 is a flowchart illustrating a main processing of update of cloud
configuration history.
[FIG. 10] FIG. 10 is a flowchart illustrating an acquisition processing of cloud
configuration information and display processing of update history.
[FIG. 11] FIG. 11 is a flowchart illustrating an acquisition processing of cloud
configuration information.
[FIG. 12] FIG. 12 is a flowchart illustrating a configuration history update processing of
cloud configuration information of a configuration information acquisition processing
part.
[FIG. 13] FIG. 13 is a flowchart illustrating a history display / restoration / replication
processing of cloud configuration.
[FIG. 14] FIG. 14 is an image view illustrating a restoration of a cloud configuration.
[FIG. 15] FIG. 15 is an image view illustrating a replication of a cloud configuration.
[Description of Embodiments]
[0011]
Embodiments of the present invention will now be described with reference to
the drawings. In the following description, various information are referred to as
"management tables", for example, but the various information can also be expressed
by data structures other than tables. Further, the "management table" can also be
referred to as "management information" to indicate that the information does not
depend on the data structure.
[0012]
The processes are sometimes described using the term “program” as the
subject. The program is executed by a processor such as an MP (Micro Processor) or
a CPU (Central Processing Unit) for performing determined processes. A processor
5
can also be the subject of the processes, since the processes are performed by a
processor using appropriate storage resources (such as memories) and communication
interface devices (such as communication ports). The processor can also use
dedicated hardware in addition to the CPU. The computer programs can be installed to
each computer from a program source. The program source can be provided via a
program assignment server or storage media, for example.
[0013]
Each element, such as each controller, can be identified by numbers, but other
types of identification information such as names can be used as long as they are
identifiable information. The equivalent elements are denoted with the same reference
numbers in the drawings and the description of the present invention, but the present
invention is not restricted to the present embodiments, and other modified examples in
conformity with the idea of the present invention are included in the technical scope of
the present invention. The number of each component can be one or more than one,
unless defined otherwise.
[0014]
FIG. 1
FIG. 1 is a view illustrating an outline of the invention in a cloud-configuration
storage system according to one embodiment of the present invention.
[0015]
In constructing an intra-company infrastructure environment using a public
cloud provided to an unspecified large number of general users through the Internet by
a cloud provider (cloud service provider), it is necessary to use a standard tool unique
to the cloud provider, and as a result of infrastructure environment of a cloud
constructed by the standard tool, the respective configuration components (resources:
such as server, network, and data center) are merely displayed in the form of a list.
[0016]
Therefore, it was difficult to apprehend the connection states of the respective
configuration components and the entire configuration. For example, a server list
stores information of a data center (hereinafter abbreviated as DC) ID to which a server
belongs and a network ID being connected, in addition to a server ID. Similarly, a
network list stores information of the server ID being connected, in addition to a network
ID. A DC list stores information of a server ID of the servers existing within the DC, in
addition to the DC ID. Therefore, overview of the infrastructure configuration
(relationship between resources) cannot be apprehended speedily from the lists.
[0017]
It was necessary to copy lists and check the relationship between the
respective IDs and the resources, in order to apprehend the overview of infrastructure
configuration (relationship between resources), according to which errors and leaks of
relationship between resources occurred, and the check required much time and
workload.
6
[0018]
The above-described problems can be solved by generating a visual
configuration diagram illustrated in FIG. 1 by gathering information acquired from the
cloud service providers, and using notation and icons that can be easily recognized and
understood by a system administrator. However, if an infrastructure is configured of a
cloud environment provided by a plurality of cloud service providers, a large amount of
configuration change occurs in a short period of time, since change of system
configuration can be performed easily in a short time. Some cloud services are
equipped with a function to change the number of virtual servers automatically.
Therefore, even through use of such a visual configuration diagram, it is difficult to
apprehend the configuration information of a specific time point compared to an onpremises
environment.
[0019]
Actually, a cloud configuration as of 2014/4/1 in FIG. 1 is stored in a
configuration information 11a and illustrated in a configuration diagram 1a. Further, the
cloud configuration as of 2014/12/1 is stored in a configuration information 11b and
illustrated in a configuration diagram 1b. The icons shown in the configuration diagram
1a and the configuration diagram 1b are a user connection 103, a VPN connection
(VPNC) 104, a VPN gateway (VPNG) 105, a virtual DC 106, an internet gateway 107, a
load balancer 108, a network segment (NWS) 109, a global IP 110, and a virtual server
111.
[0020]
By comparing the cloud configuration as of 2014/4/1 with the cloud
configuration as of 2014/12/1, a virtual server 12b is newly added, and a virtual server
12a is deleted in the cloud configuration as of 2014/12/1. However, the cloud
configuration information as of 2014/4/1 has been rewritten by the cloud configuration
information as of 2014/12/1, such that even if change of resource of cloud configuration
has been performed, there was no means to detect that change. Further, it was not
possible to restore a past cloud environment. Thus, there was a drawback that much
workload and time was required to specify a failure occurrence location (access failure
caused by frequent accesses to the deleted virtual server 12a), or analyzing causes.
[0021]
Therefore, the present embodiment solves the problems described above by
providing a cloud-configuration storage system that facilitates difference detection by
acquiring configuration information of cloud services and storing a configuration change
history.
[0022]
FIG. 2
FIG. 2 is a view illustrating an entire configuration of a system adopting the
cloud-configuration storage system according to an embodiment of the present
invention. The system is composed of a cloud-configuration storage system 28 and a
7
cloud service (IaaS: Infrastructure as a Service) 24. The cloud-configuration storage
system 28 and the cloud service (IaaS) 24 are connected via a network 25 such as a
LAN (Local Area Network).
[0023]
A cloud service API (Application Programming Interface) 241 in the drawing
refers to a software for operating the cloud service (IaaS) 24 provided by the cloud
service provider. Further, cloud connection information 50 refers to information such as
IDs and keys necessary for using the cloud service API 241. The configuration
information 60 refers to information on resources (such as a virtual DC, a virtual server,
and a virtual network) in the cloud service 24. The cloud service (IaaS) 24 includes
hardware resources such as a large number of server apparatuses, storage devices,
and network devices, and software resources such as various OSs (Operating
Systems) and APs (Application Programs), and the resources are provided virtually to
the users.
[0024]
The cloud-configuration storage system 28 is composed of a client PC
(hereinafter abbreviated as client) 21, and a physical server (hereinafter abbreviated as
server) 22. The client 21 has three function blocks called a cloud connection
information reception part 211, a configuration storage processing part 213, and a
configuration history display processing part 214.
[0025]
The cloud connection information reception part 211 is a function part for
receiving registration of a cloud connection information 50 (refer to FIG. 5) for a user 23
to construct the infrastructure environment.
[0026]
A configuration storage processing part 213 is a function part that receives
from the user 23 a cloud information (such as cloud ID) whose configuration information
60 of cloud environment should be saved, and generates a storage request of the
configuration information 60 to the server 22.
[0027]
A configuration history display processing part 214 is a function part that
receives a cloud information designated by the user 23 to have its configuration
displayed, and displays the configuration information 60 of the cloud environment as a
configuration viewer on a screen at an arbitrary time point. The configuration
information 60 is acquired by the configuration display processing part 212 requesting
execution of acquisition of configuration information 60 to a configuration information
acquisition processing part 222 of the server 22.
[0028]
The server 22 has five function blocks, a cloud connection information
registration part 221, a configuration information acquisition processing part 222, a
8
cloud connection information DB 223, a configuration history acquisition processing
part 224, and a configuration history DB 225.
[0029]
The cloud connection information registration part 221 is a function part for
storing and saving a cloud connection information 50 received by the cloud connection
information reception part 211 of the client 21 in the the cloud connection information
DB 223.
[0030]
The configuration information acquisition processing part 222 acquires the
cloud connection information 50 stored in the the cloud connection information DB 223,
and based on the acquired cloud connection information 50, requests acquisition of
configuration information 60 with respect to the cloud service (IaaS) 24, and acquires
the configuration information 60. It is further equipped with a function to receive a
change notice of configuration information 60 from a proxy server a 26 / proxy server b
27 or a cloud service (IaaS) 24, to acquire the configuration information 60 as of that
time point, and to store the acquired configuration information 60 in a configuration
history DB 225. The cause of occurrence of change notice of configuration information
60 from the cloud service (IaaS) 24 can be, for example, the automatic changing of
number of virtual servers 111, as described earlier.
[0031]
A configuration history acquisition processing part 224 has a function to acquire
a configuration history information of a configuration history 70 (FIG. 7: cloud
configuration history table) / configuration history 80 (FIG. 8: cloud configuration
component history table) from the configuration history DB 225 based on a request
from the configuration history display processing part 214 of the client 21, and transmit
the acquired configuration history information to the configuration history display
processing part 214.
[0032]
The configuration history DB 225 is a storage function part that stores the
configuration history information of the configuration history 70 (FIG. 7: cloud
configuration history table) / configuration history 80 (FIG. 8: cloud configuration
component history table) from the configuration information acquisition processing part
222, and the stored configuration history information is read as needed by the
configuration history acquisition processing part 224.
[0033]
The user 23 registers the cloud connection information 50, designates the
cloud whose configuration of cloud environment should be stored, and designates the
cloud whose configuration is to be displayed to the cloud-configuration storage system
28. The cloud-configuration storage system 28 acquires the configuration information
60 from the cloud service (IaaS) 24 based on the received registration information and
the designated information.
9
[0034]
The user 23 can register a plurality of cloud services (IaaS) 24 provided by
different providers to constitute the infrastructure environment of the cloud. Therefore,
the cloud-configuration storage system 20 can store configuration information 60 of
different cloud environments, the configuration history 70 (cloud configuration history
table), and the configuration history 80 (cloud configuration component history table).
Therefore, the cloud-configuration storage system 28 has an acquisition function of the
configuration information 60 of a plurality of cloud services (IaaS) 24 of different
providers, and a storage function and a display function of the configuration information
60. The detailed description will be described later.
[0035]
FIG. 3
FIG. 3 is a block diagram illustrating an internal configuration of a client PC
(client terminal).
[0036]
The client 21 includes a CPU 2101, a memory 2102, a storage part 2103, an
input part 2104, an output part 2105, a display part 2106, and a communication part
2107.
[0037]
The CPU 2101 is a processor that controls the entire client 21. The memory
2102 is a device that temporarily stores various programs and various data described
later. The storage part 2103 is a device that permanently stores various programs and
various data described later.
[0038]
The input part 2104 is a device that receives input, such as a keyboard or a
mouse. The output part 2105 is a device that outputs information and data, such as a
speaker or a printer.
[0039]
The display part 2106 is a device that displays information and data, such as a
liquid crystal display. The communication part 2107 is a device that connects the client
21 with other devices (such as the server 22 or the apparatus of the cloud service
(IaaS) 24) via a network. The above-described configuration components are mutually
connected via an internal bus.
[0040]
The memory 2102 stores various OSs provided by OS provision companies,
and various APs operating on the various OSs.
[0041]
FIG. 4
FIG. 4 is a block diagram illustrating an internal configuration of a server. The
server 22 includes a CPU 2201, a memory 2202, a storage part 2203, an input part
2204, an output part 2205, a display part 2206, and a communication part 2207.
10
[0042]
The CPU 2201 is a processor that controls the entire server 22. The memory
2202 is a device that temporarily stores various programs and various data described
later. The storage part 2203 is a device that permanently stores various programs and
various data described later.
[0043]
The input part 2204 is a device that receives input, such as a keyboard or a
mouse. The output part 2205 is a device that outputs information and data, such as a
speaker or a printer.
[0044]
The display part 2206 is a device that displays information and data, such as a
liquid crystal display. The communication part 2207 is a device that connects the
server 22 with other devices (such as the client 21 or the apparatus of the cloud service
(IaaS) 24) via a network. The above-described configuration components are mutually
connected via an internal bus.
[0045]
The server 22 is not necessarily equipped with the input part 2204, the output
part 2205 and the display part 2206 illustrated by the dotted lines, and in that case, the
server 22 should merely have an interface to which these configuration components
can be connected.
[0046]
FIG. 5
FIG. 5 is a view illustrating a configuration example of a cloud connection
information. The cloud connection information 50 is composed of a cloud management
table 51, a cloud service management table of company A 52, and a cloud service
management table of company M 53. The tables are provided to enable handling of
multiple types of cloud services. Therefore, a table for managing the connection
information 50 specific to each cloud service is provided for each cloud service, and
information is stored and managed in each table.
[0047]
The cloud management table 51 is composed of a cloud ID for uniquely
identifying the cloud type, a cloud provider ID for uniquely identifying the type of the
cloud provider (cloud service provider 24), a cloud name which is the name of the cloud
being used, and a cloud information expressed in the form of an IP address serving as
the connection information to the cloud. A predetermined information is stored in each
entry corresponding to the cloud ID. For example, "acs" is stored as the cloud provider
ID whose cloud ID is "1", "vdc-001" is stored in the cloud name, and "10.0.0.0/16" is
stored as the cloud information as connection IP address information, and managed.
[0048]
The cloud service management table of company A 52 is composed of a cloud
ID for uniquely identifying the cloud type, a region ID for uniquely identifying the range
11
of area managed by a cloud, an access ID for uniquely identifying the user 23, an
access key used for access by the user 23, and a virtual DC_ID for uniquely identifying
the virtual DC. A predetermined information is stored in each entry corresponding to
the cloud ID. For example, "ap-northeast-1" is stored as the region ID whose cloud ID
is "2", "HJSERHSDFGJS" is stored as the access ID, "JUTFGJJDDGHJFDS" is stored
as the access key, and "vdc-g48gwy4r" is stored as the virtual DC_ID, and managed.
[0049]
The cloud service management table of company M 53 is composed of a cloud
ID for uniquely identifying the cloud type, a subscription ID for identifying the contents of
the provided service, a region ID for uniquely identifying the range of area managed by
the cloud, a certification information for using the cloud service, and a virtual DC_ID for
uniquely identifying the virtual DC. Predetermined information is stored in each entry
corresponding to the cloud ID. For example, "74urjhjuy4uygulsdfhg" is stored as the
subscription ID where the cloud ID is "3", "East Asia" is stored as the region ID, "RTokyo-
7-2-2014-credentials" is stored as the certification, and "website001" is stored as
the virtual DC_ID, and managed.
[0050]
In the cloud management table 51, the cloud ID is set as an external key
(common key) to associate the cloud service management table of company A 52 and
the cloud service management table of company M 53 for management.
[0051]
As for the cloud connection information 50, the user 23 enters necessary
information to the cloud connection information reception part 211 of the client 21, and
the information is registered. Specifically, predetermined selection and input of
information using a menu or input area displayed on the display part 2106 of the client
21 in FIG. 3 is performed form the input part 2104. Then, the CPU 2101 temporarily
stores the cloud connection information 50 received through the input part 2104 in the
memory 2102 or the storage part 2103. The registration operation of the cloud
connection information is executed by the cloud connection information reception part
211 controlling the CPU 2101.
[0052]
FIG. 6
FIG. 6 is a view illustrating a configuration example of a cloud service
configuration information. A cloud service configuration information 60 is information
corresponding to the cloud ID in the configuration information acquisition request
transmitted to the cloud service 24 from the configuration information acquisition
processing part 222 of the cloud-configuration storage system 28.
[0053]
The cloud service configuration information 60 (configuration information 60) is
composed of an item number (#), a configuration apparatus, a configuration
component, and a configuration information setting content. For example, regarding
12
the virtual DC whose item number (#) is "1", based on the configuration information
setting content, it can be recognized that the virtual DC_ID is "vdc-001". Further,
according to this virtual DC, the setting content of the virtual network whose item
number (#) is "2" is "subnets" :[{"subnet_id" : "subnet-01", "netaddr" : "10.0.0.0/24", so
that it can be recognized that the subnet_id is "subnet-01" and that it is connected to a
network having a network address of "10.0.0.0/24".
[0054]
In item number (#) "3" where the configuration apparatus is a "virtual network
device", the configuration components are "load balancer", "Internet gateway", "ＶＰＮ
(Virtual Private Network) gateway", "VPN connection", and "user connection", and
although not illustrated, the setting contents of the configuration information are stored
in each configuration component. Although not illustrated, the aforementioned cloud ID
information is added to the configuration information 60.
[0055]
In the present embodiment, the configuration information 60 is stored in the
configuration history DB 225 either periodically or each time a change occurs, such that
restoration or replication the cloud environment is enabled.
[0056]
FIG. 7
FIG. 7 is a view illustrating a configuration example of a cloud configuration
history table. The cloud configuration history table 70 is a table that manages the
configuration history in cloud units.
[0057]
The cloud configuration history table 70 is composed of a configuration history
ID, a cloud ID, a history name, and a configuration information acquisition time, and
predetermined information for each new configuration or change of configuration is
stored in the respective entries by the configuration information acquisition processing
part 222. For example, "1" is stored as the cloud ID corresponding to the configuration
history ID "1", "before adding server" is stored as the history name, and "2014/1/1
15:12:35.725" is stored as the configuration information acquisition time. Similarly, "1"
is stored as the cloud ID corresponding to the configuration history ID "2",
"(configuration change notice)" is stored as the history name, and information "2014/2/4
13:20:21.544" is stored as the configuration information acquisition time. Further, "2" is
stored as the cloud ID corresponding to the configuration history ID "3", "newly
constructed" is stored as the history name, and "2014/6/3 20:21:43.265" is stored as
the configuration information acquisition time.
[0058]
The cloud configuration component history table 80 described below is
associated (linked) with the cloud configuration history table using the configuration
history ID as an external key (common key), and stored in the configuration history DB
225 as cloud configuration history information.
13
[0059]
FIG. 8
FIG. 8 is a diagram illustrating a configuration example of a cloud configuration
component history table. A configuration component key refers to a character string
indicating data (configuration component information) stored in a configuration
component information string. Further, a configuration component refers to data,
configuration information, configuration diagram files and the like constituting a
configuration history. The types of configuration components linked to one
configuration history differs according to a type of cloud service being stored.
[0060]
Configuration components "acs:vdc" and "image:png" have configuration
history ID "1". The configuration component information whose configuration history
ID is "1" and configuration component is "acs:vdc" is "{"id":"vdc-001", "subnets":
[{"subnet_id":"subnet-01", "netaddr": "10.0.0.0/24", ...", and this information is stored in
the configuration history DB 225.
[0061]
The configuration component information whose configuration history ID is "1"
and configuration component is "image:png" is
"iVBORw0KGgoAAAANSUhEUgAAA5gAAALkCAYAAABqX5qzAAAABHNCS ...", and
this information is stored in the configuration history DB 225.
[0062]
The configuration component whose history ID is "2" is similar to the
configuration components "acs:vdc" and "image:png" having configuration history ID "1".
The reason is because the cloud ID whose configuration history ID is "1" and the cloud
ID whose configuration history ID is "2" are the same, which is "1". The configuration
component information whose configuration history ID is "2" and configuration
component is "acs:vdc" is "{"id":"vdc-001", "subnets": [{"subnet_id":"subnet-02",
"netaddr": "10.0.0.0/25", ...".
[0063]
The configuration component information whose configuration history ID is "2"
and configuration component is "image:png" is
"AM5Q0apYu/+H3teudFVX+0XIHGOpmRiHwN9bLMSJeMwZWWIUuSZVIK...". As
described, the information of the state in which the configuration history ID has been
changed from "1" is stored in the configuration component information whose
configuration history ID is "2", and stored in the configuration history DB 225. Thereby,
even after the change of cloud environment, the cloud configuration can be returned to
the environment before the change.
[0064]

FIG. 9
14
FIG. 9 is a flowchart illustrating a main processing for updating a cloud
configuration history. The subject of the processing is the function part of the client 21
or the server 22, but it can also be a CPU 2101 of the client 21 or a CPU 2201 of the
server 22.
[0065]
In S901, the configuration information acquisition processing part 222 acquires
an event information from a proxy server 26/27. The event can be a configuration
change, construction of a new cloud, acquisition of configuration information, and so on.
In S902, the configuration information acquisition processing part 222
determines whether a configuration change command has been executed. The
configuration change command includes a command for constructing a new cloud
mentioned earlier. If it is determined that a configuration change command has been
executed (S902: Yes), the configuration information acquisition processing part 222
executes S905, and if it is determined that the command has not been executed (S902:
No), it executes S903.
[0066]
In S903, the configuration information acquisition processing part 222 acquires
a time information from a timer (not shown) of the server 22 or the like.
In S904, the configuration information acquisition processing part 222
determines whether a prescribed time (acquisition time of configuration information)
has been reached. If a prescribed time has been reached (S904: Yes), the
configuration information acquisition processing part 222 executes S905, and if the time
has not been reached (S904: No), the processes of S901 and thereafter are executed
again.
In S905, the configuration information acquisition processing part 222 executes
an acquisition processing of the configuration information 60 at the current point of time.
[0067]
According to the above-described processing, the history of the configuration
information 60 can be stored and saved in the configuration history DB 225.
[0068]
FIGs. 10 – 12
FIG. 10 is a flowchart illustrating an acquisition processing of cloud
configuration information and display processing of update history. FIG. 11 is a
flowchart illustrating and acquisition processing of cloud configuration information in the
configuration information acquisition processing part. FIG. 12 is a flowchart illustrating
a configuration history update processing of cloud configuration information in the
configuration information acquisition processing part. The subject of the processing is
the function part of the client 21 or the server 22, but it can also be the CPU 2101 of the
client 21 or the CPU 2201 of the server 22.
[0069]
15
In S1001 of FIG. 10, the configuration storage processing part 213 acquires the
cloud information storing the configuration information 60 selected by the user 23.
Specifically, a virtual DC_ID (cloud ID) is entered in the screen of a display portion 2106,
and an input part 2104 receives the information on the virtual DC_ID and transfers the
information to the configuration storage processing part 213.
In S1002, the configuration storage processing part 213 transmits the virtual
DC_ID (cloud ID) to the configuration information acquisition processing part 222 of the
server 22, and requests acquisition of the configuration information 60. The
configuration information acquisition processing part 222 executes the acquisition
processing of configuration information. The acquisition processing of the configuration
information 60 relates to executing a subroutine processing illustrated in FIG. 11.
[0070]
In S1003, the configuration storage processing part 213 stores the acquired
configuration information 60, the updated configuration history table 70 and
configuration component history table 80 in the configuration history DB 225. Then,
the configuration storage processing part 213 transmits the stored configuration
information 60, the configuration history table 70 and the configuration component
history table 80 to the configuration history acquisition processing part 224.
In S1004, the configuration history display processing part 214 acquires the
cloud ID displaying the configuration selected by the user 23. The configuration history
display processing part 214 transmits the acquired cloud ID to the configuration history
acquisition processing part 224, and acquires a history list information. The
configuration history display processing part 214 displays the acquired history list
information on the screen of the display portion 2106.
[0071]
In S1005, in the configuration history display processing part 214, the user 23
selects the cloud ID whose detailed configuration component information is to be
displayed from the history list displayed on the screen, and selects the cloud ID using a
keyboard or a mouse of the input part 2104. The configuration history display
processing part 214 acquires the selected cloud ID, and transmits the cloud ID to the
configuration history acquisition processing part 224. The configuration history
acquisition processing part 224 acquires a predetermined configuration information, the
configuration history table 70 and the configuration component history table 80 based
on the received cloud ID from the configuration history DB 225, and transmits the same
to the configuration history display processing part 214.
In 1006, the configuration history display processing part 214 generates a
configuration diagram based on the received configuration information, the
configuration history table 70 and the configuration component history table 80, and
displays the generated configuration diagram on the screen of the display portion 2106.
[0072]
16
The above-described processing enables to store the configuration information
60 and the information in the configuration history table 70 and the configuration
component history table 80 as of an arbitrary point of time.
[0073]
In S1101 of FIG. 11, the configuration information acquisition processing part
222 of the server 22 acquires a cloud connection information 50 from the cloud
connection information DB 223 based on the received virtual DC_ID (cloud ID).
In S1102, the configuration information acquisition processing part 222
determines whether the designated cloud is provided by company A, based on a cloud
provider ID corresponding to the designated cloud ID. If the designated cloud is
provided by company A (S1102: Yes), the configuration information acquisition
processing part 222 executes S1103, and if not (S1102: No), executes S1104.
In S1103, the configuration information acquisition processing part 222
transmits an acquisition request of the configuration information 60 to a cloud service
(ACS), and acquires the configuration information 60 in the cloud service (ACS).
[0074]
In S1104, the configuration information acquisition processing part 222
determines whether the designated cloud is provided by company M, based on the
cloud provider ID corresponding to the designated cloud ID. If the designated cloud is
provided by company M (S1104: Yes), the configuration information acquisition
processing part 222 executes S1105, and if not (S1104: No), executes S1105.
In S1105, the configuration information acquisition processing part 222
transmits an acquisition request of configuration information 60 to the cloud service
(MCS), and acquires the configuration information 60 according to the cloud service
(MCS).
[0075]
In S1106, the configuration information acquisition processing part 222
determines whether the designated cloud is provided by company H, based on the
cloud provider ID corresponding to the designated cloud ID. If the designated cloud is
provided by company M (S1106: Yes), the configuration information acquisition
processing part 222 executes S1107, and if not (S1106: No), determines whether the
cloud is provided by a cloud service provider other than companies A, M and H.
In S1107, the configuration information acquisition processing part 222
transmits an acquisition request of the configuration information 60 to the cloud service
provided by company H, and acquires the configuration information 60 according to the
cloud service of company H.
[0076]
In S1108, the configuration information acquisition processing part 222
determines whether the configuration information of all designated clouds have been
acquired. If the configuration information of al designated clouds has been acquired
17
(S1108: Yes), the configuration information acquisition processing part 222 executes
S1109, and if not (S1108: No), executes the processing of S1101 and thereafter.
[0077]
Next, the details of acquisition processing of configuration information in S1103,
S1105, and S1107 are described with reference to FIG. 12.
[0078]
In S1201 of FIG. 12, the configuration information acquisition processing part
222 acquires configuration apparatuses of the configuration information 60 and a
configuration information setting content of the configuration component corresponding
to a virtual DC (item number (#) "1").
In S1202, the configuration information acquisition processing part 222
acquires configuration apparatuses of the configuration information 60 and a
configuration information setting content of the configuration component corresponding
to a virtual network (item number (#) "2").
In S1203, the configuration information acquisition processing part 222
acquires a configuration information setting content corresponding to a virtual server
(item number "4").
In S1204, the configuration information acquisition processing part 222
acquires a configuration information setting content of a virtual network equipment (item
number (#) "3") and the configuration component corresponds to a load balancer.
[0079]
In S1205, the configuration information acquisition processing part 222
determines whether all configuration information has been acquired. If not all
configuration information has been acquired (S1205: No), the configuration information
acquisition processing part 222 executes S1206, and if all has been acquired (S1205:
Yes), the processing is returned to any one of the call destination processes S1103,
S1105 and S1107.
In S1206, the configuration information acquisition processing part 222
acquires the configuration information of other configuration apparatuses or
configuration components, and executes the processing of S1205 again.
[0080]
In S1207, the configuration information acquisition processing part 222 updates
the configuration component history table 80 by the acquired configuration information
60.
In S1208, the configuration information acquisition processing part 222 updates
the configuration history table 70 based on the acquired configuration information 60
and the updated configuration component history table 80. Then, the configuration
information acquisition processing part 222 returns the processing to a subroutine call
destination (any one of S1103, S1105 and S1107).
[0081]
18
Based on the processing of FIGs. 10 to 12, the configuration information 60
and the information of the configuration history table 70 and the configuration
component history table 80 as of an arbitrary point of time can be stored and saved in
the configuration history DB 225. Therefore, restoration to a past cloud environment
and replication of a cloud environment as of a current point of time is enabled. The
detailed processing will be described with reference to FIG. 13.
[0082]
FIG.
13
FIG. 13 is a flowchart illustrating a history display / restoration / replication
processing of a cloud configuration. The subject of the processing is the configuration
history display processing part 214, but it can also be the CPU 2101 of the client 21.
[0083]
In S1301, the configuration history display processing part 214 acquires the
input information that the user has entered through the input part 2104, that is, the
cloud ID to be displayed and the configuration history ID indicating the point of time of
the configuration.
In S1302, the configuration history display processing part 214 determines
based on the acquired configuration history ID whether to display the configuration as
of the current point of time. The configuration at the current point of time can be judged
based on whether the configuration history ID is the youngest of the cloud ID. If the
configuration as of the current point of time is to be displayed (S1302: Yes), the
configuration history display processing part 214 executes S1303, and if not (S1302:
No), executes S1304.
In S1303, the configuration history display processing part 214 acquires and
generates the configuration diagram at the current point of time by acquiring
configuration information 60 from the configuration history DB 225, displays the
generated configuration diagram on the screen of the display portion 2106, and ends
the processing.
[0084]
In S1304, if the past configuration is to be displayed (S1304: Yes), the
configuration history display processing part 214 executes S1305, and if not (S1304:
No), it executes S1308.
In S1305, the configuration history display processing part 214 acquires the
configuration information 60, the information of the configuration history table 70 and
the configuration component history table 80 from a history DB 225 to construct a
configuration diagram as of a requested past point of time. The configuration history
display processing part 214 generates a configuration diagram from the acquired
information, and displays the generated configuration diagram on the screen of the
display portion 2106.
19
Then, in S1306, the configuration history display processing part 214
determines whether a highlight display of difference with the current configuration is
requested. If requested (S1306: Yes), the configuration history display processing part
214 executes S1307, and if not (S1306: No), ends the processing.
In S1307, the configuration history display processing part 214 executes a
difference portion, highlights the extracted configuration component, and ends the
processing. According to the processing of steps S1301 through S1307, the user can
confirm the difference in configuration between the past cloud environment and the
current cloud environment described in FIG. 1 on the screen. The difference portion
can be apprehended precisely by highlighting (meshing) only the difference portions.
[0085]
In S1308, the configuration history display processing part 214 determines
whether restoration of the configuration information is requested. If restoration is
requested (S1308: Yes), the configuration history display processing part 214 executes
S1309, and if not (S1308: No), it ends the processing.
In S1309, the configuration history display processing part 214 constructs the
cloud environment based on past configuration information, and displays the
configuration diagram on the screen.
[0086]
In S1310, the configuration history display processing part 214 determines
whether replication of configuration information is requested. If replication is requested
(S1310: Yes), the configuration history display processing part 214 executes S1311,
and if not (S1310: No), it executes S1312.
In S1311, the configuration history display processing part 214 executes
replication of cloud environment based on the current configuration information,
displays the configuration diagram on the screen, and ends the processing.
In S1312, the configuration history display processing part 214 notifies an error
to the user 23, and ends the processing. The error notice is transmitted and displayed
on the display portion 2106, such as in a case where there is no corresponding cloud
environment for the entered cloud ID, and the error is notified to the user.
[0087]
FIG. 14
FIG. 14 is an image diagram illustrating a restoration of a cloud configuration.
The present image view illustrates a case where a configuration information 11b
(configuration diagram 1b) as of a current point of time 2014/12/1 is returned to a
configuration information 11a (configuration diagram 1a) as of a past point of time
2014/4/1. According to the configuration information 11b (configuration diagram 1b) as
of 2014/12/1, the virtual server 12a is deleted, and a virtual server 12b is newly added.
The configuration is returned to the configuration information (configuration diagram 1a)
as of 2014/4/1 where the deletion and addition of the virtual servers are not performed.
As described, the current cloud environment can be returned to the past cloud
20
environment by executing the processing of FIG. 13 described earlier. It is also
possible to simultaneously display the configuration information 11b (configuration
diagram 1b) and the configuration information 11a (configuration diagram 1a) on the
screen for comparison.
[0088]
According to the example of FIG. 14, the configuration information 11b
(configuration diagram 1b) as of current point of time 2014/12/1 is returned to the
configuration information 11a (configuration diagram 1a) as of a past point of time
2014/4/1, and the operation is illustrated. Although not illustrated, it is possible to return
the configuration to an older point of time, such as to a point of time of 2014/2/1, and it
is also possible to display the configuration information 11a (configuration diagram 1a)
as of 2014/4/1 and the configuration information as of 2014/2/1 at the same time.
[0089]
FIG. 15
FIG. 15 is an image view illustrating a replication of cloud configuration. The
present view illustrates a case in which a failure has occurred to the virtual server 12a
in the configuration information 11a (configuration diagram 1a) of a real operation
environment 10a as of 2014/4/1, and that an identical cloud environment is replicated
and a test environment 10c is constructed, in order to specify a cause of failure and to
perform countermeasures. The components other than the virtual server 12a are
operating normally, so the real operation environment 10a continues to operate. The
replicated test environment 10c adopts an identical configuration and executes identical
operations as the real operation environment 10a to specify the cause of failure and to
take countermeasures. Thereby, the cause of failure can be specified and
countermeasures can be taken by without stopping the operating environment. Thus,
replication of the current cloud environment is enabled by executing the processing of
FIG. 13 described earlier.
[0090]
As described above, according to the cloud-configuration storage system, the
difference between a past cloud environment and a current cloud environment can be
confirmed. The difference can be apprehended precisely by highlighting only the
difference portions. Moreover, since the current cloud environment can be returned to
the past cloud environment, and a cloud environment having an identical configuration
as the real operation environment 10a can be replicated, cause of failure can be
specified and countermeasures can be taken without stopping the operating
environment.
[0091]
The present invention is not restricted to the above-illustrated preferred
embodiments, and can include various modifications. The above-illustrated
embodiments are described in detail to help understand the present invention, and the
present invention is not restricted to a structure including all the components illustrated
21
above. Further, a portion of the configuration of an embodiment can be replaced with
the configuration of another embodiment, or the configuration of a certain embodiment
can be added to the configuration of another embodiment. Moreover, a portion or all of
the configurations of each embodiment can be added to, deleted from or replaced with
other configurations. The configurations and functions described above can be realized
through software by having a processor interpret and execute programs for realizing
the respective functions. The respective configurations, functions and the like
described above can be realized by software by the processor interpreting and
executing programs for realizing the respective functions.
[0092]
The information such as the programs, tables and files for realizing the
respective functions can be stored in storage devices such as memories, hard disks or
SSDs (Solid State Drives), or in memory media such as IC cards, SD cards or DVDs.
Only the control lines and information lines considered necessary for description are
illustrated in the drawings, and not necessarily all the control lines and information lines
required for production are illustrated. In actual application, it can be considered that
almost all the components are mutually coupled.
[Reference Signs List]
[0093]
1: Configuration viewer screen, 11: configuration information, 21: client, 22: server, 24:
cloud service (IaaS), 26/27: proxy server, 28 cloud configuration storage system, 50:
cloud connection information, 51: cloud management table, 52: cloud service
management table of company A, 53: cloud service management table of company M,
60: cloud service configuration information, 70: cloud configuration history table, 80:
cloud configuration component history table, 103: user connection, 104:VPN
connection, 105: VPN gateway, 106: virtual DC, 107: Internet gateway, 108: load
balancer, 109: network segment, 110: global IP, 111: virtual server, 211: cloud
connection information reception part, 213: configuration storage processing part, 214:
configuration history display processing part, 221: cloud connection information
registration part, 222: configuration information acquisition processing part, 223: cloud
connection information DB, 224: configuration history acquisition processing part, 225:
configuration history DB, 241: cloud service API.

[CLAIMS]
[Claim 1]
A cloud-configuration storage system configured to connect to one or more
cloud service provision systems providing a cloud service, the system comprising:
a client apparatus and a server apparatus,
the client apparatus comprising
a cloud connection information reception part configured to receive from the
user a cloud connection information for constructing a cloud environment,
a configuration storage processing part configured to receive designation of the
cloud environment to be stored, and
a configuration history display processing part configured to perform display
control of a configuration history of the cloud environment being stored,
the server apparatus comprising
a cloud connection information part configured to store and register the cloud
connection information received by the cloud connection information reception part of
the client apparatus in a cloud connection information DB,
a configuration information acquisition processing part configured to acquire
the cloud configuration information constructed in the cloud service provision system
from the cloud service provision system according to a cloud configuration information
acquisition request from the configuration display processing part of the client
apparatus,
a cloud configuration history DB configured to store the configuration
information being acquired as a configuration history information, and
a configuration history acquisition processing part configured to acquire a
configuration history information from the cloud configuration history DB,
wherein the configuration storage processing part having received a cloud
configuration storage command from the user is configured to
extract a cloud ID for acquiring cloud configuration information from the cloud
configuration display request command, and
transmit the configuration display command of the extracted cloud ID to the
configuration information acquisition processing part,
wherein the configuration information acquisition processing part is configured
to
acquire a cloud connection information from the cloud connection information
DB based on the cloud ID,
specify a cloud service provision system acquiring the cloud configuration
information based on the acquired cloud connection information, and
acquire the cloud configuration information from the specified cloud service
provision system and store the information in the cloud configuration history DB, and
wherein the configuration history display processing part is configured to
23
acquire a configuration history from the configuration information acquisition
processing part based on a cloud information whose configuration is to be displayed
received from the user,
generate a cloud configuration diagram using a configuration component icon
corresponding to each configuration element and a connection information based on
the configuration history being acquired, and
display the cloud configuration diagram being generated on the screen.
[Claim 2]
The cloud-configuration storage system according to claim 1, wherein the client
apparatus or the server apparatus comprises
a CPU configured to control an entire apparatus,
a memory configured to store information temporarily,
a storage part configured to store information permanently, and
one or more of a communication part configured to control communication with
an external device, an input part configured to receive information from outside, an
output part configured to output information to the external device, and a display part
configured to display information.
[Claim 3]
The cloud-configuration storage system according to claim 2, wherein the cloud
connection information includes at least a cloud ID configured to uniquely identify the
cloud environment, a cloud provider ID configured to uniquely identify the cloud service
provision system, a cloud name, and a network connection information to the cloud.
[Claim 4]
The cloud-configuration storage system according to claim 3,
wherein the cloud configuration information is composed of a cloud ID, a
configuration apparatus, a configuration component, and a configuration information
setting content,
the configuration apparatus at least includes a virtual data center name, a
virtual network name, a virtual network equipment name, a virtual server name, and a
virtual server associated information,
the configuration component corresponding to the virtual network equipment
name at least includes configuration components of a load balancer, an Internet
gateway, a VPN gateway, a VPN connection, and a user connection,
the configuration component corresponding to the virtual server associated
information at least includes configuration components of a global IP, a security group,
a machine image, a virtual CPU, a virtual memory, and a virtual storage, and
an icon for each configuration apparatus or configuration component is
generated, and a configuration diagram is generated.
[Claim 5]
The cloud-configuration storage system according to claim 4,
wherein the configuration history display processing part is configured to
24
acquire a configuration history as of a point of time designated by the user from
the cloud configuration history DB,
generate a configuration diagram from the configuration history, and
display the configuration diagram being generated.
[Claim 6]
The cloud-configuration storage system according to claim 5,
wherein the configuration history display processing part is configured to
generate a configuration diagram based on a configuration history as of a plurality of
points of time designated by the user, and simultaneously display a plurality of the
configuration diagrams being generated.
[Claim 7]
The cloud-configuration storage system according to claim 4,
wherein the configuration history display processing part is configured to
acquire a configuration history as of a point of time designated by the user from
the cloud configuration history DB,
replicate the configuration history, and
generate and display a configuration diagram based on the configuration
history being replicated.
[Claim 8]
The cloud-configuration storage system according to claim 5,
wherein the configuration history display processing part is configured to
generate configuration diagrams based on a configuration history corresponding to the
point of time designated by the user and based on the configuration history being
replicated, and simultaneously display the plurality of configuration diagrams being
generated.
[Claim 9]
A cloud-configuration storage method of a cloud-configuration storage system
configured to connect to one or more cloud service provision systems providing a cloud
service, the cloud-configuration storage system comprising:
a client apparatus and a server apparatus,
the client apparatus comprising
a cloud connection information reception part configured to receive a cloud
connection information constructing a cloud environment from a user,
a configuration storage processing part configured to receive designation of the
cloud environment to be stored, and
a configuration history display processing part configured to perform display
control of a configuration history of the cloud environment being stored,
the server apparatus comprising
a cloud connection information part configured to store and register the cloud
connection information received by the cloud connection information reception part of
the client apparatus in a cloud connection information DB,
25
a configuration information acquisition processing part configured to acquire
the cloud configuration information constructed in the cloud service provision system
from the cloud service provision system according to a cloud configuration information
acquisition request from the configuration display processing part of the client
apparatus,
a cloud configuration history DB configured to store the configuration
information being acquired as a configuration history information, and
a configuration history acquisition processing part configured to acquire a
configuration history information from the cloud configuration history DB,
wherein the configuration storage processing part having received a cloud
configuration storage command from the user is configured to execute the following
steps of
extracting a cloud ID for acquiring cloud configuration information from the
cloud configuration display request command, and
transmitting a configuration information acquisition command of the extracted
cloud ID to the configuration information acquisition processing part,
wherein the configuration information acquisition processing part is configured
to execute the following steps of
acquiring a cloud connection information from the cloud connection information
DB based on the cloud ID,
specifying a cloud service provision system acquiring the cloud configuration
information based on the acquired cloud connection information, and
acquiring the cloud configuration information from the specified cloud service
provision system and storing the information in the cloud configuration history DB, and
wherein the configuration history display processing part is configured to
execute the following steps of
acquiring a configuration history from the configuration information acquisition
processing part based on a cloud information whose configuration is to be displayed
received from the user,
generating a cloud configuration diagram using a configuration component icon
corresponding to each configuration element and a connection information based on
the configuration history being acquired, and
displaying the cloud configuration diagram being generated on the screen.
[Claim 10]
A cloud-configuration storage program of a cloud-configuration storage system
configured to connect to one or more cloud service provision systems providing a cloud
service, the cloud-configuration storage system comprising:
a client apparatus and a server apparatus,
the client apparatus comprising
a cloud connection information reception part configured to receive a cloud
connection information constructing a cloud environment from a user,a configuration storage processing part configured to receive designation of the
cloud environment to be stored, and
a configuration history display processing part configured to perform display
control of a configuration history of the cloud environment being stored,
the server apparatus comprising
a cloud connection information part configured to store and register the cloud
connection information received by the cloud connection infomiation reception part of
the client apparatus in a cloud connection information DB,
a configuration information acquisition processing part configured to acquire
the cloud configuration information constructed in the cloud service provision system
from the cloud service provision system according to a cloud configuration information
acquisition request from the configuration display processing part of the client
apparatus,
a cloud configuration history DB configured to store the configuration
information being acquired as a configuration history information, and
a configuration history acquisition processing part configured to acquire a
configuration history information from the cloud configuration history DB,
wherein the configuration storage processing part having received a cloud
configuration storage command from the user is configured to execute the following
functions of
extracting a cloud ID for acquiring cloud configuration information from the
cloud configuration display request command, and
transmitting a configuration information acquisition request of the extracted
cloud ID to the configuration information acquisition processing part,
wherein the configuration information acquisition processing part is configured
to execute the following functions of
acquiring a cloud connection information from the cloud connection information
DB based on the cloud ID7
specifying a cloud service provision system acquiring the cloud configuration
information based on the acquired cloud connection information, and
acquiring the cloud configuration information from the specified cloud service
provision system and storing the information in the cloud configuration history DB, and
wherein the configuration history display processing part is configured to
execute the following functions of
acquiring a configuration history from the configuration information acquisition
processing part based on a cloud information whose configuration is to be displayed
received from the user,
generating a cloud configuration diagram using a configuration component icon
corresponding to each configuration element and a connection information based on
the configuration history being acquired, and
displaying the cloud configuration diagram being generated on the screen.