WO2014006739A1 - Ordinateur de gestion, procédé de dotation en infrastructure et programme - Google Patents

Ordinateur de gestion, procédé de dotation en infrastructure et programme Download PDF

Info

Publication number
WO2014006739A1
WO2014006739A1 PCT/JP2012/067299 JP2012067299W WO2014006739A1 WO 2014006739 A1 WO2014006739 A1 WO 2014006739A1 JP 2012067299 W JP2012067299 W JP 2012067299W WO 2014006739 A1 WO2014006739 A1 WO 2014006739A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
base
management
business system
infrastructure
Prior art date
Application number
PCT/JP2012/067299
Other languages
English (en)
Japanese (ja)
Inventor
悠介 森田
幸生 中野
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2012/067299 priority Critical patent/WO2014006739A1/fr
Publication of WO2014006739A1 publication Critical patent/WO2014006739A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources

Definitions

  • the present invention relates to a computer system that provides a system environment capable of executing services.
  • the present invention relates to a computer, a method, and a program that provide a system environment that reflects the state of an operating business system.
  • a platform-provided cloud service such as PaaS (Platform as a Service) provides a platform (environment) that can operate a business such as a network application and a Web service as a service.
  • PaaS Platinum as a Service
  • PaaS Platform as a Service
  • a base what is configured and set as follows is called a base.
  • OS such as a DBMS and an application server
  • OS kernel parameters are set according to the hardware configuration.
  • middleware parameters are set in consideration of the arrangement of middleware.
  • the service provider is a user who manages the image (file) and provides the infrastructure by deploying the image (file).
  • a service user is a user who builds a business system on the provided infrastructure and operates the business system.
  • the infrastructure provided by the service provider is described as the standard infrastructure, and is distinguished from the infrastructure on which the business system operated by the service user is constructed.
  • the infrastructure information indicates parameters that can be dynamically changed by the service user after the service provider provides the infrastructure. Specifically, OS kernel parameters and middleware parameters are shown.
  • Patent Document 1 discloses a virtual environment construction support system in which a user can passively configure an optimal virtual environment by selecting a business system that is close to the operating business system from business systems that have been used in the past. Is disclosed.
  • Patent Document 1 when a new standard infrastructure is provided, the service user needs to set the standard infrastructure in consideration of the requirements of the operating business system. In other words, when a new standard infrastructure is changed, it is necessary for the service user to appropriately reset the infrastructure information set from the infrastructure on which the business system is constructed.
  • one of the purposes is to dynamically reflect the operating state of the business system that has been operated so far on the changed standard infrastructure.
  • a typical example of the invention disclosed in the present application is as follows. That is, a management computer that manages a business system built on a platform that provides a computer system that executes business applications, the management computer being connected to a processor, a storage medium connected to the processor, and the processor
  • a computer system provided by the infrastructure is configured by virtual computer resources generated from a group of physical computer resources, and the management computer is configured to connect the business system via the network interface.
  • the policy that defines the A platform information acquisition unit that acquires business platform information, which is information related to the configuration of the platform in the system, and generates difference information based on the business platform information and the platform information provided at the time of building the business system A difference information acquisition unit, and a distribution base information generation unit that generates distribution base information for building the business system on a new base based on the difference information and the base information,
  • a platform information acquisition unit that acquires business platform information, which is information related to the configuration of the platform in the system, and generates difference information based on the business platform information and the platform information provided at the time of building the business system
  • a difference information acquisition unit and a distribution base information generation unit that generates distribution base information for building the business system on a new base based on the difference information and the base information
  • the business base information of the first target business system is acquired, difference information is generated using the business base information and the first base information, and the generated difference information and the second Parameter information is generated using the policy for generating the second base information for providing the base, and the second base information
  • the base reflecting the operating business system can be dynamically provided. it can.
  • FIG. 1 is a block diagram showing the configuration of a computer system in the first embodiment of the present invention.
  • the computer system includes a management computer 100 and a plurality of business systems 300.
  • the business system 300 is a system constructed using a standard infrastructure provided by a service provider.
  • the infrastructure refers to an environment in which computer resources necessary for operating a business system are provided, and middleware and OS parameters are set.
  • a standard infrastructure is provided to a service user, and the service user constructs a business system using the standard infrastructure.
  • the standard infrastructure on which the business system 300 is constructed provides a load balancer 310, a virtual machine 320, and a virtual storage device 330 as computer resources. It is also assumed that OS 321 parameters and middleware parameters corresponding to the hardware configuration of a physical computer and storage system that provide computer resources are set.
  • the load balancer 310 is a computer that distributes the processing load in the virtual machine 320 and the virtual storage device 330.
  • the virtual machine 320 is a computer that executes a predetermined job.
  • middleware such as an OS 321, APS 322, and DB 323, and an application 324 operate.
  • the virtual storage device 330 stores information necessary for business.
  • a method of allocating an LU generated from a storage area included in the storage system can be considered.
  • the load balancer 310, the virtual machine 320, and the virtual storage device 330 are virtual processors such as a virtual processor, a virtual memory, a virtual storage area, and a virtual network interface provided by a virtualization program (not shown) that implements a virtualization function. It consists of typical computer resources.
  • the virtual computer resource is provided by a data center including a computer, a storage device, a network device, and the like, for example.
  • the management computer 100 is a computer that manages a business system 300 in operation and a standard infrastructure for constructing the business system 300. Specifically, the management computer 100 holds an image file as information for generating a standard infrastructure.
  • the image file includes at least infrastructure information for storing parameters necessary for generating a standard infrastructure.
  • the management computer 100 when the management computer 100 provides a standard infrastructure and then creates a new standard infrastructure, the management computer 100 reflects the parameters changed during operation of the business system and creates a new standard infrastructure.
  • the standard platform with changed parameters is also referred to as a business platform. If the standard platform and business platform are not distinguished, they are described as the platform.
  • the management computer 100 includes a base information storage unit 110, a system management unit 120, and a base management unit 130.
  • the base information storage unit 110 stores various information necessary for providing the base. Specifically, the basic information storage unit 110 stores a basic image file 140, a system association table 150, an image association table 160, and a deployment image file 170.
  • the basic image file 140 is an image file for generating a standard infrastructure to be provided to service users. Accordingly, the basic image file 140 does not reflect the parameters changed in the business system. It includes base information 141 and policy 142. Note that the basic image file 140 includes one or more policies 142.
  • the infrastructure information 141 stores information necessary for providing a standard infrastructure.
  • the policy 142 stores information necessary for generating the standard infrastructure. Details of the base information 141 and the policy 142 will be described later with reference to FIGS.
  • the deployment image file 170 is an image file for providing a new standard infrastructure generated based on business infrastructure infrastructure information.
  • the deployment image file 170 includes infrastructure information 171 in which parameters changed during operation of the business system are reflected.
  • the deployment image file 170 is an image file that provides a new standard base for the business base in operation, and therefore does not include information corresponding to the policy 142.
  • the system relation table 150 stores information indicating the relation between the business system 300 and the standard infrastructure provided when the business system 300 is constructed. Details of the system relation table 150 will be described later with reference to FIG.
  • the image relation table 160 stores information indicating the relation between image files. Details of the image association table 160 will be described later with reference to FIG.
  • the system management unit 120 monitors the business system 300 in operation.
  • the system management unit 120 includes a business system monitoring unit 121 and a base information acquisition unit 122.
  • the business system monitoring unit 121 acquires information related to the operating state of the computer resources included in the business system 300.
  • the operating state of the computer resource includes, for example, usage rates of processors and memories allocated to the virtual machine 320, IOPS, and the like.
  • the infrastructure information acquisition unit 122 acquires the infrastructure information of the business infrastructure.
  • Information acquired by the business system monitoring unit 121 and the base information acquisition unit 122 is input to the base management unit 130.
  • the infrastructure management unit 130 manages the standard infrastructure, and generates a deployment image file 170 that is information for providing a new standard infrastructure based on the information input from the system management unit 120.
  • the base management unit 130 includes an event acquisition unit 131, a base operation determination unit 132, a difference information extraction unit 133, an image file generation unit 134, and a result display unit 135.
  • the event acquisition unit 131 analyzes the event and determines whether to generate an image file (deployment image file 170) for providing a new standard infrastructure.
  • the infrastructure operation determination unit 132 determines a method for generating the deployment image file 170.
  • the difference information extraction unit 133 compares the basic information on the standard infrastructure and the basic information on the business infrastructure, and acquires difference information such as changed parameters.
  • the image file generation unit 134 newly generates a deployment image file 170 based on the acquired difference information.
  • the result display unit 135 generates information for displaying information related to the deployment image file 170 to the service user or the service provider, and displays information related to the deployment image file 170 based on the generated display information. .
  • the data center (not shown) in which the business system 300 is constructed and the management computer 100 are connected to each other via the network 200.
  • the network 200 may have various wired and wireless configurations such as LAN, WAN, and SAN.
  • the present invention may be any network as long as the data center (not shown) and the management computer 100 can communicate with each other.
  • the network 200 includes a plurality of network devices (not shown).
  • the network device includes, for example, a switch and a gateway.
  • FIG. 2 is a block diagram illustrating the hardware configuration of the management computer 100 in the first embodiment of the present invention.
  • the management computer 100 includes a processor 400, a main storage device 410, a secondary storage device 420, an optical drive 440, an input device 450, an output device 460, and a network interface 470.
  • the processor 400 executes a program stored in the main storage device 410.
  • the main storage device 410 stores a program executed by the processor 400 and information necessary for executing the program.
  • a memory or the like can be considered.
  • the main storage device 410 stores programs for realizing the system management unit 120 and the infrastructure management unit 130.
  • the main storage device 410 includes a work area 500 that is used during execution of various processes.
  • the secondary storage device 420 stores various information managed by the management computer 100.
  • an HDD Hard Disk Drive
  • an SSD Solid State Drive
  • the secondary storage device 420 includes a storage area for realizing the base information storage unit 110.
  • the input device 450 is a device for inputting various information or commands to the management computer 100, and includes a keyboard, a mouse, a touch panel, and the like.
  • the output device 460 is a device for outputting a processing result or the like to an administrator, and includes a display.
  • the network interface 470 is an interface for connecting to other devices via a network.
  • the program stored in the main storage device 410 may be stored in the secondary storage device 420.
  • the processor 400 reads the program from the secondary storage device 420, loads the read program onto the main storage device 410, and executes the loaded program.
  • the information stored in the secondary storage device 420 may be stored in an optical storage medium.
  • the processor 400 acquires information from the optical storage medium input to the optical drive 440 and stores the acquired information in the secondary storage device 420.
  • the management computer 100 itself may not include the secondary storage device 420.
  • the configuration may be such that the management computer 100 is connected to the secondary storage device 420 existing outside via a network.
  • the management computer 100 may be configured to be connected to a storage system having a plurality of secondary storage devices 420.
  • FIG. 3 is an explanatory diagram showing an example of the system relation table 150 in the first embodiment of the present invention.
  • the system relation table 150 stores information indicating the correspondence between the business system 300 and the standard infrastructure provided when the business system 300 is constructed. Specifically, the system association table 150 includes an identification number 601, a system ID 602, and an image ID 603.
  • the identification number 601 is an identification number for uniquely identifying an entry included in the system association table 150.
  • the system ID 602 is an identifier for uniquely identifying the business system 300 in the computer system.
  • the image ID 603 is an identifier of an image file corresponding to the standard base provided when the business system 300 is constructed.
  • the identifier of the basic image file 140 corresponding to the standard infrastructure is stored in the image ID 603 of the entry whose identification number 601 is “1”, “2”, and “4”, and the identification number 601 is “ In the image ID 603 of the entries “3”, “5”, and “6”, the identifier of the deployment image file 170 corresponding to the newly provided standard infrastructure is stored.
  • FIG. 4 is an explanatory diagram showing an example of the image association table 160 in the first embodiment of the present invention.
  • the image association table 160 stores information indicating the correspondence between image files. Specifically, the image association table 160 includes an identification number 701, a route 702, and a node 703.
  • the identification number 701 is an identification number for uniquely identifying an entry included in the image association table 160.
  • a route 702 is an identifier of an image file that is a basis of a newly generated image file.
  • the node 703 is an identifier of a newly generated image file or an updated image file based on the image file corresponding to the route 702.
  • the identifier of the updated basic image file 140 is stored in the node 703, and the identifier of the basic basic image file 140 is stored in the route 702. It is assumed that the image association table 160 is updated by the service provider. Note that the present invention is not limited to the method for updating the image relation table 160, and a method for automatically updating the image relation table 160 may be used.
  • the updated or added basic image file 140 is also referred to as an updated basic image file 140.
  • the basic image file 140 that is the basis of the updated basic image file 140 is also referred to as a pre-update basic image file 140.
  • FIG. 5 is an explanatory diagram showing an example of the correspondence between image files in the first embodiment of the present invention.
  • the solid arrow indicates the correspondence between the pre-update basic image file 140 and the image file newly generated based on the pre-update basic image file 140.
  • the deployment image file 170-1 and the deployment image file 170-3 indicate that the basic image file 140-1 is generated as the pre-update basic image file 140.
  • the deployment image file 170-4 is generated based on the deployment image file 170-1, and indicates that the pre-update basic image file 140 is the basic image file 140-1.
  • a dotted arrow indicates the relevance of the basic image file 140 specified by the policy 142.
  • the basic image file 140-1 indicates that the policy 142 for the basic image file 140-2 and the basic image file 140-3 is held.
  • FIG. 6 is an explanatory diagram showing an example of the base information 141 in the first embodiment of the present invention.
  • the base information 141 is information described in XML.
  • the present invention is not limited to this.
  • the base information 141 stores information necessary for generating a standard base.
  • the base information 141 includes description information 811, description information 804, and description information 805.
  • the description information 811 describes infrastructure information related to computer resources provided by the standard infrastructure.
  • the description information 811 includes description information 801, description information 802 and description information 803.
  • the description information 801 describes information related to the virtual machine 320
  • the description information 802 describes information related to the virtual network
  • the description information 803 describes information related to the virtual storage device 330.
  • the description information 804 describes information related to the OS 321, and the description information 805 describes information related to middleware. That is, in the description information 804 and the description information 805, software setting information in the standard infrastructure is described.
  • the base information 141 may include placement information indicating the number of virtual machines, virtual networks, and virtual storages, and connection relationships.
  • description information 801, the description information 804, and the description information 805 will be described using the description information 801, the description information 804, and the description information 805 as an example.
  • FIG. 7A is an explanatory diagram showing an example of description information 801 in the first embodiment of the present invention.
  • FIG. 7B is an explanatory diagram showing an example of description information 804 in the first embodiment of the present invention.
  • FIG. 7C is an explanatory diagram illustrating an example of the description information 805 according to the first embodiment of this invention.
  • information about the virtual machine 320-1 is described in the first to twelfth lines of the description information. Specifically, in the first line of the description information 801, the business content executed by the virtual machine 320, the name of the virtual machine 320, and the identifier of the virtual machine 320 are described. Further, the OS 321 identifier is described in the seventh line of the description information 801, and the middleware identifier is described in the ninth line. Similar information is described for the other lines.
  • the name and identifier of the OS 321 are described in the first line of the description information 804, and various parameters set in the OS 321 are described in the second line to the fourteenth line.
  • the first line describes the middleware type, name, and identifier
  • the second to nineteenth lines describe various parameters that are set in the middleware.
  • the necessary parameters can be acquired from the business system 300 based on the information indicating the storage location of the parameter described in the 16th line of the description information 805. .
  • FIG. 8 is an explanatory diagram showing an example of the policy 142 in the first embodiment of the present invention.
  • the policy 142 stores information necessary for generating the base information 141 to be included in the new image file.
  • the policy 142 includes an identification number 901, S_KEY 902, M_KEY 903, P_KEY 904, and a rule 905.
  • the identification number 901 is an identification number for uniquely identifying an entry included in the policy 142.
  • S_KEY 902 is an identifier for uniquely identifying a computer resource provided in the standard infrastructure.
  • M_KEY 903 is an identifier for uniquely identifying middleware in a computer resource.
  • P_KEY 904 is an identifier for uniquely identifying a parameter in the middleware.
  • the rule 905 is a conversion rule for calculating a parameter corresponding to the entry from the base information 141 or the difference information.
  • the conversion rule stores text information and mathematical formulas. For example, information such as “the first entry included in the difference information described later and the (m + 1) th value are summed and the sum is divided by 3” is stored.
  • FIGS. 9A and 9B are flowcharts for explaining processing executed by the business system monitoring unit 121 in the first embodiment of the present invention.
  • the business system monitoring unit 121 repeatedly performs the processing described below during operation (steps S101 to S123).
  • the business system monitoring unit 121 determines whether or not a certain period has elapsed (step S103). In this embodiment, since the processing is periodically executed, the business system monitoring unit 121 uses a timer or the like to determine whether or not a certain period has elapsed since the previous processing was completed.
  • the business system monitoring unit 121 If it is determined that the certain period has not elapsed, the business system monitoring unit 121 returns to step S103 and continues to wait until the certain period has elapsed.
  • step S105 the business system monitoring unit 121 starts a loop process of the business system 300.
  • the business system monitoring unit 121 selects a target business system 300 from the business systems 300 in the computer system, and performs steps S107 to S119 on the selected business system 300. Repeat the process up to.
  • the loop process of the business system 300 ends (step S121).
  • the business system monitoring unit 121 acquires performance information of the application 324 running on the selected business system 300 (step S107).
  • the business system monitoring unit 121 acquires, for example, application response, DBMS throughput, and the like as performance information of the application 324.
  • the acquired application performance information is stored in the work area 500.
  • the application performance information acquisition method is a known technique, a detailed description thereof is omitted, but the present invention is not limited to the application performance information acquisition method.
  • the business system monitoring unit 121 starts loop processing of the virtual machine 320 (step S109).
  • the business system monitoring unit 121 selects a target virtual machine 320 from the virtual machines 320 included in the selected business system 300, and selects the selected virtual machine 320.
  • the process of step S111 is repeatedly executed.
  • the loop process of the virtual machine 320 ends (step S113).
  • the business system monitoring unit 121 acquires the load information of the selected virtual machine 320 (step S111).
  • the business system monitoring unit 121 acquires, for example, the usage rate of the virtual processor, the usage rate of the virtual memory, the IOPS of the virtual I / O device, and the like assigned to the virtual machine 320 as load information of the virtual machine 320.
  • the acquired performance information of the virtual machine 320 is stored in the work area 500.
  • the method for acquiring the load information of the virtual machine 320 is a known technique, a detailed description thereof will be omitted, but the present invention is not limited to the method for acquiring the performance information of the virtual machine 320.
  • the business system monitoring unit 121 determines whether the performance of the application 324 satisfies a predetermined condition based on the acquired performance information of the application 324 (step S115).
  • the business system monitoring unit 121 compares the performance information of the application 324 acquired last time with the performance information of the application 324 acquired this time, and determines whether or not the performance of the application 324 has decreased by a predetermined threshold value or more. It is conceivable to determine this.
  • the determination conditions are set in advance.
  • the service user or the service provider may input using a predetermined interface.
  • step S121 If it is determined that the performance of the acquired application 324 does not satisfy the predetermined condition, the business system monitoring unit 121 proceeds to step S121.
  • the business system monitoring unit 121 determines that the performance of the virtual machine 320 satisfies the predetermined condition based on the acquired load information of the virtual machine 320. It is determined whether or not (step S117).
  • the business system monitoring unit 121 compares the load information of the virtual machine 320 acquired last time with the performance information of the virtual machine 320 acquired this time, and the performance of the virtual machine 320 decreases by a predetermined threshold value or more. A method for determining whether or not there is a possibility is considered.
  • the determination conditions are set in advance.
  • the service user or the service provider may input using a predetermined interface.
  • step S121 If it is determined that the performance of the virtual machine 320 does not satisfy the predetermined condition, the business system monitoring unit 121 proceeds to step S121.
  • the business system monitoring unit 121 calls the infrastructure management unit 130 (step S119) and proceeds to step S121.
  • the business system monitoring unit 121 notifies the event acquisition unit 131 that the infrastructure management unit 130 has been called.
  • the notification includes the identification number of the business system 300 that satisfies both the conditions of step S115 and step S117.
  • the infrastructure management unit 130 can identify the business system 300 to be processed.
  • the business system monitoring unit 121 ends the processing when the loop processing of the business system 300 ends.
  • step S115 and step S117 are examples of conditions as long as it is determined that a new standard infrastructure needs to be generated.
  • the standard infrastructure for building a business system is scaled out. Can be considered.
  • the standard base for constructing the business system is scaled in due to a decrease in the load of the virtual machine 320 in the business system.
  • FIGS. 10A and 10B are flowcharts for explaining processing executed by the infrastructure management unit 130 in the first exemplary embodiment of the present invention.
  • the infrastructure management unit 130 executes processing periodically. There are two triggers for generating the deployment image file 170.
  • One opportunity is when a new deployment image file 170 of the business system 300 is generated in accordance with a change in the state of the business system 300.
  • the state change of the business system 300 is detected by the system management unit 120 as described above. In the following description, this opportunity is also referred to as a business opportunity.
  • Another opportunity is when a new deployment image file 170 of the business system 300 related to the basic image file 140 is generated as the basic image file 140 is updated or added.
  • the basic image file 140 is updated or added by the service provider.
  • this opportunity is also referred to as a management opportunity.
  • the business system monitoring unit 121 calls the infrastructure management unit 130.
  • the business system monitoring unit 121 notifies the identifier of the business system 300 to be processed when calling the infrastructure management unit 130.
  • the infrastructure management unit 130 detects the updated basic image file 140 and generates a deployment image file 170.
  • the base management unit 130 initializes an event flag (step S201).
  • the infrastructure management unit 130 sets the value of the event flag to “0”.
  • the value of the event flag is stored in the work area 500. Therefore, in the following description, when the value of the event flag is output, it indicates that the value on the work area 500 has been updated.
  • the infrastructure management unit 130 calls the event acquisition unit 131 and instructs the execution of the process (step S203). Details of processing executed by the event acquisition unit 131 will be described later with reference to FIG.
  • the infrastructure management unit 130 continues to wait until it receives a processing completion notification from the event acquisition unit 131. Note that the event acquisition unit 131 sets “0” or “1” in the event flag as a processing result as described later.
  • the base management unit 130 determines whether it has been called from the system management unit 120 (step S205).
  • the infrastructure management unit 130 determines whether or not the event flag is “1”. When it is determined that the event flag is “1”, the infrastructure management unit 130 determines that the system management unit 120 has called the event flag.
  • the infrastructure management unit 130 calls the infrastructure operation determination unit 132 and instructs execution of the process (step S207). At this time, the infrastructure management unit 130 notifies the infrastructure operation determination unit 132 of the identifier of the business system 300 to be processed. Details of processing executed by the base operation determination unit 132 will be described later with reference to FIG. 12A.
  • the infrastructure management unit 130 continues to wait until it receives a process completion notification from the infrastructure operation determination unit 132. As described later, the base operation determination unit 132 sets “1” in the event flag as a processing result, and outputs the identifier of the target basic image file 140 to the work area 500 or “ Set to “0”.
  • the target basic image file 140 represents the basic image file 140 provided when the business system 300 to be processed is constructed.
  • the infrastructure management unit 130 determines whether the deployment image file 170 can be generated (step S209).
  • the infrastructure management unit 130 determines whether or not the event flag is “0”. If it is determined that the event flag is “0”, the infrastructure management unit 130 determines that the deployment image file 170 cannot be generated.
  • the infrastructure management unit 130 ends the process. At this time, the infrastructure management unit 130 instructs the result display unit 135 to display that the deployment image file 170 cannot be generated.
  • the infrastructure management unit 130 calls the difference information extraction unit 133 (step S211). At this time, the infrastructure management unit 130 notifies the difference information extraction unit 133 of the identifier of the business system 300 to be processed and the identifier of the target basic image file 140. Details of the processing executed by the difference information extraction unit 133 will be described later with reference to FIG.
  • the infrastructure management unit 130 continues to wait until it receives a processing completion notification from the difference information extraction unit 133.
  • the difference information extraction unit 133 outputs the difference information to the work area 500 as a processing result as will be described later.
  • the infrastructure management unit 130 Upon receiving the processing completion notification from the difference information extraction unit 133, the infrastructure management unit 130 calls the image file generation unit 134 (step S213). At this time, the infrastructure management unit 130 notifies the image file generation unit 134 of the identifier of the business system 300 to be processed, the identifier of the target basic image file 140, and difference information. Details of processing executed by the image file generation unit 134 will be described later with reference to FIG. 17A.
  • the infrastructure management unit 130 continues to wait until it receives a processing completion notification from the image file generation unit 134. Note that the image file generation unit 134 outputs the deployment image file 170 to the work area 500 as a processing result as described later.
  • the infrastructure management unit 130 calls the result display unit 135 (step S215) and ends the processing.
  • step S205 If it is determined in step S205 that the system management unit 120 has not called the system management unit 120, the infrastructure management unit 130 starts loop processing of the image file (step S251).
  • the base management unit 130 selects a processing target image file from the basic image file 140 and the deployment image file 170 stored in the base information storage unit 110, and the selected processing target image file In contrast, the processing from step S253 to step S261 is repeatedly executed. When the processing is executed for all image files, the image file loop processing ends (step S263).
  • the base management unit 130 initializes an event flag (step S253).
  • the process in step S253 is the same as the process in step S201, and the event flag is set to “0”.
  • the infrastructure management unit 130 calls the infrastructure operation determination unit 132 and instructs the execution of the process (step S255). At this time, the base management unit 130 notifies the base operation determination unit 132 of the identifier of the selected processing target image file. Details of processing executed by the base operation determination unit 132 will be described later with reference to FIG. 12B.
  • the infrastructure management unit 130 continues to wait until it receives a process completion notification from the infrastructure operation determination unit 132.
  • the platform operation determination unit 132 sets “0” in the event flag or “2” in the event flag as a processing result as will be described later, and the identifier and update of the update basic image file 140 The identifier of the previous basic image file 140 is output to the work area 500.
  • the infrastructure management unit 130 determines whether or not the deployment image file 170 needs to be generated (step S257).
  • the infrastructure management unit 130 determines whether or not the event flag is “0”. When the event flag is “0”, it is determined that the deployment image file 170 need not be generated.
  • the infrastructure management unit 130 proceeds to step S265.
  • the infrastructure management unit 130 calls the difference information extraction unit 133 and instructs execution of the process (step S259). At this time, the infrastructure management unit 130 notifies the difference information extraction unit 133 of the identifier of the updated basic image file 140. Details of the processing executed by the difference information extraction unit 133 will be described later with reference to FIG.
  • the infrastructure management unit 130 continues to wait until it receives a processing completion notification from the difference information extraction unit 133.
  • the difference information extraction unit 133 outputs the difference information to the work area 500 as a processing result as will be described later.
  • the base management unit 130 calls the image file generation unit 134 (step S261).
  • the infrastructure management unit 130 notifies the image file generation unit 134 of the identifier of the business system 300 to be processed, the identifier of the updated basic image file 140, and the difference information. Details of the processing executed by the image file generation unit 134 will be described later with reference to FIG. 17B.
  • the infrastructure management unit 130 continues to wait until it receives a processing completion notification from the image file generation unit 134.
  • the image file generation unit 134 stores the deployment image file 170 in the base information storage unit 110 as a processing result as described later.
  • step S265 is the same as the process of step S215.
  • FIG. 11 is a flowchart for explaining processing executed by the event acquisition unit 131 according to the first embodiment of this invention.
  • the event acquisition unit 131 starts processing when called from the infrastructure management unit 130.
  • the event acquisition unit 131 determines whether the processing trigger is a business trigger (step S301).
  • the event acquisition unit 131 determines whether a notification indicating that the infrastructure management unit 130 has been called from the business system monitoring unit 121 has been received.
  • the event acquisition unit 131 ends the processing. In this case, the event flag is “0”.
  • the event acquisition unit 131 sets the event flag to “1” (step S303) and ends the processing.
  • FIGS. 12A and 12B are flowcharts for explaining the processing executed by the base operation determination unit 132 in the first embodiment of the present invention.
  • FIG. 12A shows processing in the case of a business opportunity
  • FIG. 12B shows processing in the case of a management opportunity.
  • the infrastructure operation determination unit 132 starts processing when called from the infrastructure management unit 130.
  • the event flag that is set and the information that is input differ depending on the trigger of the process. Specifically, in the case of a business opportunity, “1” is set in the event flag, and the identifier of the business system 300 to be processed is input. In the case of a management opportunity, “0” is set in the event flag. And the identifier of the selected processing target image file is input.
  • the base operation determination unit 132 determines whether the processing trigger is a business trigger (step S401).
  • the base operation determination unit 132 determines whether or not the event flag is “1”. When the event flag is “1”, it is determined that the processing trigger is a business trigger. Note that the processing from step S403 to step S415 is processing when called in step S207. Further, the processing from step S451 to step S461 is processing when called in step S255.
  • the infrastructure operation determination unit 132 refers to the system association table 150 based on the identifier of the business system 300 to be processed, and corresponds to the business system 300 to be processed.
  • the file identifier is specified (step S403).
  • the infrastructure operation determination unit 132 acquires an image file corresponding to the business system 300 to be processed from the infrastructure information storage unit 110 based on the identified identifier of the image file (step S405). At this time, the acquired image file is set as a processing target image file.
  • the infrastructure operation determination unit 132 determines whether the processing target image file is the basic image file 140 (step S407).
  • the base operation determination unit 132 determines whether or not the policy 142 is included in the processing target image file.
  • the processing target image file is the basic image file 140. That is, the processing target image file itself becomes the target basic image file 140.
  • the processing target image file is the deployment image file 170.
  • the base operation determination unit 132 ends the processing. At this time, the base operation determination unit 132 outputs the identifier of the business system 300 to be processed and the identifier of the target basic image file 140 to the work area 500 as processing results.
  • the basic operation determination unit 132 refers to the image association table 160 (step S409), and the basic image file 140 that is related to the processing target image file 140 is obtained. Is determined (step S411). Specifically, the following processing is executed.
  • the infrastructure operation determination unit 132 refers to the node 703 in the image relation table 160 and searches for an entry that matches the identifier of the processing target image file. If there is no entry that matches the identifier of the processing target image file, it is determined that there is no basic image file 140 related to the image file.
  • the infrastructure operation determination unit 132 When there is an entry that matches the identifier of the processing target image file, the infrastructure operation determination unit 132 refers to the route 702 of the entry and identifies an image file that matches the identifier stored in the route 702. Further, the base operation determination unit 132 determines whether the specified image file is the basic image file 140.
  • the specified image file is the basic image file 140
  • the infrastructure operation determination unit 132 When it is determined that the identified image file is the deployment image file 170, the infrastructure operation determination unit 132 performs the same search process as described above using the identifier of the deployment image file 170 as a search key.
  • the basic image file 140 related to the deployment image file 170 becomes the target basic image file 140.
  • step S411 The above is the process of step S411.
  • the base operation determination unit 132 ends the processing. At this time, the base operation determination unit 132 outputs the identifier of the business system 300 to be processed and the identifier of the target basic image file 140 to the work area 500 as processing results.
  • step S411 when it is determined that there is no basic image file 140 related to the processing target image file, the base operation determination unit 132 notifies an error (step S413), and “0” is set in the event flag. "Is set (step S415), and then the process is terminated.
  • the base operation determination unit 132 calls the result display unit 135 and instructs to display an error.
  • step S401 If it is determined in step S401 that the processing trigger is not a business trigger, that is, a management trigger, the base operation determination unit 132 determines that the processing target image from the base information storage unit 110 based on the identifier of the processing target image file. A file is acquired (step S451).
  • the base operation determination unit 132 determines whether or not the acquired processing target image file is the basic image file 140 (step S453).
  • the processing in step S453 is the same as that in step 407.
  • the base operation determination unit 132 determines whether or not the acquired processing target image file is the updated basic image file 140 (step) S459). In step S459, the following processing is executed.
  • the infrastructure operation determination unit 132 refers to the node 703 in the image relation table 160 and searches for an entry that matches the identifier of the processing target image file. If there is no entry that matches the identifier of the processing target image file, it is determined that it is not the update basic image file 140.
  • the infrastructure operation determination unit 132 When there is an entry that matches the identifier of the processing target image file, the infrastructure operation determination unit 132 refers to the route 702 of the entry and identifies an image file that matches the identifier stored in the route 702. Further, the base operation determination unit 132 determines whether the specified image file is the basic image file 140.
  • the base operation determination unit 132 acquires the identifier stored in the route 720 as the identifier of the pre-update basic image file 140.
  • the base operation determination unit 132 ends the processing.
  • the base operation determination unit 132 sets “2” in the event flag (step S461) and ends the processing. At this time, the base operation determination unit 132 outputs the identifier of the processing target image file (update basic image file 140) and the identifier of the pre-update basic image file 140 to the work area 500 as processing results.
  • step S453 If it is determined in step S453 that the processing target image file is the deployment image file 170, the infrastructure operation determination unit 132 refers to the image association table 160 (step S455) and is related to the processing target image file. It is determined whether or not the basic image file 140 exists (step S457).
  • step S455 and step S457 is the same processing as step S409 and step S411. That is, the target basic image file 140 is specified.
  • the base operation determination unit 132 ends the process.
  • step S459 it is determined whether or not the target basic image file 140 is the updated basic image file 140.
  • the base operation determination unit 132 ends the process.
  • the base operation determination unit 132 sets “2” in the event flag (step S461) and ends the process. At this time, the base operation determination unit 132 outputs the identifier of the update basic image file 140 (target basic image file 140) and the identifier of the pre-update basic image file 140 to the work area 500 as processing results.
  • step S407 the processing from step S407 to step S411 will be described.
  • a policy 142 when generating a deployment image file 170 for providing a new standard infrastructure, a policy 142 is used as described later. Therefore, in the processing from step S407 to step S411, it is determined whether or not the policy 142 for generating the deployment image file 170 exists. Specifically, it is determined as follows.
  • the base operation determination unit 132 ends the process because the policy 142 exists.
  • the infrastructure operation determination unit 132 searches for the basic image file 140 related to the deployment image file 170.
  • the base operation determination unit 132 notifies an error. This is because a new deployment image file 170 cannot be generated. If there is a related basic image file 140 as a result of the search process (YES in step S411), the base operation determination unit 132 ends the process.
  • step S453 processing from step S453 to step S461 will be described.
  • the process of the management opportunity is executed.
  • the basic operation determination unit 132 determines whether the basic image file 140 is the updated basic image file 140.
  • the base operation determination unit 132 determines that it is a management opportunity, and sets “2” in the event flag.
  • the base operation determination unit 132 determines whether the target basic image file 140 exists.
  • the base operation determination unit 132 ends the process as it is.
  • the base operation determination unit 132 determines whether the target basic image file 140 is the updated basic image file 140.
  • the base operation determination unit 132 determines that it is a management opportunity, and sets “2” in the event flag.
  • step S453 to step S461 is processing for determining a management opportunity, it is not necessary to notify an error as in step S413.
  • FIG. 13 is a flowchart for explaining processing executed by the difference information extraction unit 133 in the first embodiment of the present invention.
  • the difference information extraction unit 133 starts processing when called from the infrastructure management unit 130.
  • the event flag to be set and the information to be input differ depending on the processing trigger.
  • “1” is set in the event flag, and the identifier of the business system 300 to be processed and the identifier of the target basic image file 140 are input.
  • “2” is set in the event flag, and the identifier of the basic image file 140 before update and the identifier of the basic image file 140 before update are input.
  • the difference information extraction unit 133 determines whether the processing trigger is a business trigger (step S501).
  • the difference information extraction unit 133 determines whether or not the event flag is “1”. When the event flag is “1”, it is determined that the processing trigger is a business trigger. When the event flag is “2”, it is determined that the processing trigger is a management trigger.
  • the difference information extraction unit 133 calls the base information acquisition unit 122 and instructs the start of the processing (step S503). At this time, the difference information extraction unit 133 notifies the base information acquisition unit 122 of the identifier of the business system 300 to be processed.
  • the difference information extraction unit 133 continues to wait until a process completion notification is received from the base information acquisition unit 122.
  • the infrastructure information acquisition unit 122 outputs a business infrastructure infrastructure information table 1100 (see FIG. 15) to the work area 500 as a processing result as described later.
  • the difference information extraction unit 133 When the difference information extraction unit 133 receives the processing completion notification from the platform information acquisition unit 122, the difference information extraction unit 133 generates the standard platform information table 1000 (see FIG. 14) for the business system 300 to be processed (step S505). . Specifically, the following processing is executed.
  • the difference information extraction unit 133 acquires the target basic image file 140 from the base information storage unit 110 based on the notified identifier of the target basic image file 140. Further, the difference information extraction unit 133 refers to the acquired basic information 141 of the target basic image file 140 and generates a standard basic information table 1000 (see FIG. 14).
  • the difference information extraction unit 133 identifies the virtual machine 320 with reference to the description information 811 in which the infrastructure information is described.
  • the difference information extraction unit 133 refers to the description information 804 in which information about the OS 321 is described and the description information 805 in which information about the middleware is described, and acquires various parameters set in the identified virtual machine. After that, the difference information extraction unit 133 generates the standard base information table 1000 (see FIG. 14) using the acquired parameters.
  • the standard infrastructure information table 1000 generated by the difference information extraction unit 133 and the business infrastructure information table 1100 generated by the infrastructure information acquisition unit 122 will be described.
  • FIG. 14 is an explanatory diagram showing an example of the base information table 1000 of the standard base in the first embodiment of the present invention.
  • FIG. 15 is an explanatory diagram showing an example of the business platform information table 1100 according to the first embodiment of this invention.
  • Standard base information table 1000 includes identification number 1001, S_KEY 1002, M_KEY 1003, P_KEY 1004, value 1005, and summary 1006.
  • the identification number 1001 is an identification number for uniquely identifying an entry included in the base information table 1000.
  • S_KEY 1002 is an identifier for uniquely identifying a computer resource provided in the standard infrastructure.
  • S_KEY 1002 is the same as S_KEY 902.
  • M_KEY 1003 is an identifier for uniquely identifying middleware in a computer resource.
  • M_KEY 1003 is the same as M_KEY 903.
  • P_KEY 1004 is an identifier for uniquely identifying a parameter in the middleware.
  • P_KEY 1004 is the same as P_KEY 904.
  • Value 1005 is a specific parameter value.
  • Outline 1006 is information indicating the meaning of the parameter.
  • the business platform information table 1100 includes an identification number 1101, S_KEY 1102, M_KEY 1103, P_KEY 1104, and a value 1105.
  • the identification numbers 1101, S_KEY1102, M_KEY1103, P_KEY1104 and value 1105 are the same as the identification numbers 1001, S_KEY1002, M_KEY1003, P_KEY1004 and value 1005, respectively.
  • the difference information extraction unit 133 compares the base information table 1100 of the business system 300 with the base information table 1000 of the standard base (step S507), and determines whether there is a difference between the two base information tables. Determination is made (step S509).
  • the difference information extraction unit 133 determines that there is a difference between the two base information tables.
  • the difference information extraction unit 133 ends the process. In this case, since it is not necessary to newly generate the deployment image file 170, the infrastructure management unit 130 may end the processing without calling the image file generation unit 134 and the result display unit 135.
  • the difference information extraction unit 133 stores the base information table 1100 of the business base in the work area 500 as the difference information (step S511), and ends the processing. To do.
  • step S501 If it is determined in step S501 that the processing trigger is a management trigger, the difference information extraction unit 133 refers to the system association table 150 based on the identifier of the pre-update basic image file 140 (step S551), and updates. It is determined whether or not there is a business system 300 associated with the previous basic image file 140 (step S553). Specifically, the following processing is executed.
  • the difference information extraction unit 133 refers to the image ID 603 of the system association table 150 and searches for an entry that matches the identifier of the pre-update basic image file 140. If there is no entry that matches the identifier of the pre-update basic image file 140, it is determined that there is no business system 300 associated with the pre-update basic image file 140.
  • the business system 300 corresponding to the system ID 602 of the entry becomes the business system 300 related to the pre-update basic image file 140.
  • the difference information extraction unit 133 ends the process. In this case, it is not necessary to newly generate the deployment image file 170 when the basic image file 140 is updated.
  • the difference information extraction unit 133 starts loop processing of the business system 300 (step S555).
  • the difference information extraction unit 133 selects the business system 300 to be processed from the business systems 300 searched in step S551, and performs step S557 and step 5 for the selected business system 300.
  • the process of step S559 is repeatedly executed.
  • the loop processing of the business system 300 ends (step S561).
  • the difference information extraction unit 133 calls the base information acquisition unit 122 and instructs execution of the process (step S557). At this time, the difference information extraction unit 133 notifies the identifier of the selected business system 300. Note that the process of step S557 is the same as the process of step S503.
  • the difference information extraction unit 133 stores the business platform base information table 1100 output from the base information acquisition unit 122 in the work area 500 as difference information (step S559).
  • the difference information extraction unit 133 ends the processing.
  • FIG. 16 is a flowchart for explaining processing executed by the base information acquisition unit 122 according to the first embodiment of this invention.
  • the base information acquisition unit 122 starts processing when called from the difference information extraction unit 133.
  • the event flag to be set and the information to be input differ depending on the processing trigger.
  • the infrastructure information acquisition unit 122 determines whether the processing trigger is a business trigger (step S601).
  • the difference information extraction unit 133 determines whether or not the event flag is “1”. When the event flag is “1”, it is determined that the processing trigger is a business trigger. When the event flag is “2”, it is determined that the processing trigger is a management trigger.
  • the basic information acquisition unit 122 refers to the system association table 150 based on the identifier of the business system 300 and identifies the identifier of the basic image file 140 corresponding to the business system. Is identified (step S603).
  • the base information acquisition unit 122 can specify the basic image file 140 by executing the same process as in step S455.
  • the base information acquisition unit 122 acquires the basic image file 140 corresponding to the business system 300 from the base information storage unit 110 based on the identified identifier of the basic image file 140 (step S605). Thereafter, the base information acquisition unit 122 proceeds to step S607.
  • the basic information acquisition unit 122 acquires the updated basic image file 140 from the basic information storage unit 110 based on the identifier of the pre-update basic image file 140 (Step S1). S605). Thereafter, the base information acquisition unit 122 proceeds to step S607.
  • the base information acquisition unit 122 refers to the base information 141 of the acquired basic image file 140 and specifies the storage location of various parameters (step S607).
  • the base information acquisition unit 122 identifies the storage location of the parameter by referring to the twelfth line of the description information 805 shown in FIG. 7B.
  • the base information acquisition unit 122 acquires various parameters from the business system 300 based on the specified parameter storage position (step S609).
  • the infrastructure information acquisition unit 122 acquires information on the business system 300 from the storage area provided by the data center based on the specified parameter storage location.
  • a storage area to be stored is specified, and predetermined parameters are acquired from the storage area.
  • the base information acquisition unit 122 generates a base information table 1100 for the business base based on the acquired parameters (step S611).
  • the infrastructure information acquisition unit 122 outputs the business infrastructure infrastructure information table 1100 generated to the difference information extraction unit 133 (step S613), and ends the process.
  • the base information table 1100 is given the identifier of the processing target image file as the name.
  • FIGS. 17A and 17B are flowcharts for explaining the processing executed by the image file generation unit 134 in the first embodiment of the present invention.
  • the image file generation unit 134 starts processing when called from the infrastructure management unit 130.
  • the event flag to be set and the information to be input differ depending on the processing trigger.
  • “1” is set in the event flag, and the identifier and difference information of the target basic image file 140 are input.
  • “2” is set in the event flag, and the identifier of the basic image file 140 to be updated, the identifier of the basic image file 140 before update, and the difference information are input.
  • difference information In the case of a business opportunity, one piece of difference information corresponding to the business system 300 to be processed is input. In the case of a management opportunity, difference information is input for the number of business systems 300 related to the pre-update basic image file 140.
  • the image file generation unit 134 determines whether the processing trigger is a business trigger (step S701).
  • the image file generation unit 134 determines whether or not the event flag is “1”. When the event flag is “1”, it is determined that the processing trigger is a business trigger. When the event flag is “2”, it is determined that the processing trigger is a management trigger.
  • the image file generation unit 134 retrieves the policy 142 included in the target basic image file 140 from the basic information storage unit 110 based on the identifier of the target basic image file 140. Obtain (step S703).
  • the image file generation unit 134 starts loop processing of the policy 142 (step S705).
  • the image file generation unit 134 selects the policy 142 to be processed from the acquired policies 142, and performs the processing from step S707 to step S711 on the selected policy 142 to be processed. Repeatedly.
  • the loop processing of the policy 142 ends (step S713).
  • the image file generation unit 134 newly generates a base information table using the selected policy 142 and the difference information (step S707). Specifically, the following processing is executed.
  • the image file generation unit 134 refers to the policy 142 based on the difference information S_KEY1102, M_KEY1103, and P_KEY1104, and searches for a matching entry.
  • the image file generation unit 134 generates a new base information table by calculating various parameters based on the difference information value 1105 and the rule 905 of the matching entry of the policy 142.
  • the image file generation unit 134 generates a new deployment image file 170 by reflecting the newly generated basic information table to the basic image file 140 specified by the selected policy 142 (step S110). S709).
  • the generated deployment image file 170 is stored in the base information storage unit 110.
  • the image file generation unit 134 updates the image association table 160 (step S711).
  • the image file generation unit 134 adds a new entry to the image association table 160. Further, the image file generation unit 134 stores the identifier of the target basic image file 140 in the route 702 of the added entry, and adds the identifier of the newly generated deployment image file 170 to the node 703 of the entry. .
  • the deployment image file 170 is determined so as not to overlap with the identifiers of other deployment image files 170.
  • the image file generating unit 134 ends the processing.
  • deployment image files 170 corresponding to the number of policies 142 are generated for one business system 300.
  • the image file generation unit 134 includes the basic information file 140 from the basic information storage unit 110 in the target basic image file 140 based on the identifier of the pre-update basic image file 140.
  • the policy 142 to be acquired is acquired (step S751).
  • the image file generation unit 134 acquires only the policy 142 indicating the designation to the update basic image file 140 among the policies 142 included in the pre-update basic image file 140.
  • the image file generation unit 134 starts a loop process for difference information (step S753).
  • a deployment image file 170 is generated for each difference information.
  • the image file generation unit 134 selects the difference information to be processed from the plurality of pieces of difference information, and performs the processes from step S755 to step S759 on the selected difference information to be processed. Run repeatedly. When the process is executed for all the difference information, the difference information loop process ends (step S761).
  • the image file generation unit 134 newly generates a base information table using the acquired policy 142 and the selected difference information (step S755). Note that the process of step S755 is the same as the process of step S707.
  • the image file generation unit 134 reflects the newly generated basic information table on the basic image file 140 specified by the acquired policy 142, that is, the updated basic image file 140, thereby creating a new deployment file.
  • An image file 170 is generated (step S757).
  • the process in step S757 is the same as the process in step S709.
  • the generated deployment image file 170 is stored in the base information storage unit 110.
  • the image file generation unit 134 updates the image association table 160 (step S759).
  • the process in step S759 is the same as the process in step S711.
  • the image file generation unit 134 ends the processing.
  • the deployment image file 170 is generated for each update basic image file 140 by the number of difference information.
  • FIG. 18 is a flowchart for explaining processing executed by the result display unit 135 in the first embodiment of the present invention.
  • the result display unit 135 starts processing when called from the infrastructure management unit 130.
  • the infrastructure management unit 130 outputs the newly generated identifier of the deployment image file 170 to the result display unit 135.
  • the result display unit 135 notifies the service user and the service provider that a new deployment image file 170 has been generated (step S801). Note that the result display unit 135 may transmit the notification only to either the service provider or the service user.
  • the result display unit 135 determines whether or not a reference request has been received from the service user or the service provider (step S803).
  • the result display unit 135 When it is determined that the reference request has not been received from the service user or the service provider, the result display unit 135 returns to step S803 and continues to wait until the reference request is received. Note that the result display unit 135 may end the process if the reference request is not received within a certain period.
  • the result display unit 135 displays the list information of the deployment image file 170 based on the authority of the sender of the reference request (step S805). ), The process is terminated.
  • the result display unit 135 displays list information of all generated deployment image files 170
  • a result display unit Reference numeral 135 displays list information of the deployment image file 170 related to the business system 300 used by the service user.
  • list information of the deployment image file 170 includes the configuration of computer resources, OS and middleware parameters, and the like. Note that the present invention is not limited to the information displayed by the result display unit 135.
  • the policy adoption definition stores information such as “apply when response difference in business system response is greater than or equal to a predetermined threshold”.
  • the image file generation unit 134 can acquire only the necessary policy 142 by referring to the policy adoption definition based on the performance information and load information stored in the work area 500.
  • the management computer 100 generates the deployment image file 170 reflecting the state of the base of the operating business system 300 regardless of whether it is a business opportunity or a management opportunity. Can do.
  • the business system 300 corresponding to the operational business system 300 can be easily constructed, and the same business can be continued. That is, by providing an optimal standard base for each business system 300, it is possible to reduce the burden of adjustment work on the business system of the service user and prevent mistakes due to the adjustment work.
  • the management computer 100 detects the occurrence of the business opportunity and the management opportunity by periodically executing the process.
  • the second embodiment based on the notification from the outside, The difference is that the occurrence of triggers and management triggers is detected.
  • the management computer 100 executes a business opportunity process when an image file generation request is received from the business system 300, and a management opportunity process when an image file generation request is received from the service provider. Execute.
  • FIG. 19 is a block diagram showing the configuration of the computer system in the second embodiment of the present invention.
  • the virtual machine 320 includes a base information monitoring unit 1200.
  • the base information monitoring unit 1200 monitors the business base.
  • the base information monitoring unit 1200 holds the base information of the standard base provided when the business system 300 is constructed, that is, the base information 141 of the basic image file 140 in order to monitor the business base.
  • the base information monitoring unit 1200 holds the monitoring result as a log. Note that the base information monitoring unit 1200 may discard the monitoring result when a certain period has elapsed since the monitoring result was acquired.
  • one virtual machine 320 includes the base information monitoring unit 1200, but the present invention is not limited to this.
  • each virtual machine 320 may include the base information monitoring unit 1200.
  • the base information monitoring unit 1200 included in each virtual machine 320 monitors information on the business base related to its own virtual machine 320 and communicates with the other base information monitoring unit 1200, thereby other virtual machines 320. What is necessary is just to grasp the information of the business base related to
  • a virtualization program (not shown) for managing the virtual machine 320 may include the base information monitoring unit 1200.
  • any configuration may be used as long as the business system 300 can monitor the operating state of the virtual machine 320 or the like.
  • FIG. 20 is a flowchart for explaining processing executed by the base information monitoring unit 1200 in the second embodiment of the present invention.
  • the base information monitoring unit 1200 repeatedly performs the processing described below during operation (steps S901 to S909).
  • the base information monitoring unit 1200 refers to the base information 141 and acquires various parameters in the business system 300 (step S903).
  • the base information monitoring unit 1200 refers to each description information of the base information 141, specifies the storage position of various parameters, and acquires the various parameters from the specified storage position. At this time, the base information monitoring unit 1200 generates a base information table 1100 for the business base based on the acquired parameters, and holds the base information table 1100 for the base business base as a monitoring result.
  • the base information monitoring unit 1200 compares the previous monitoring result with the current monitoring result, and determines whether or not the business base has changed (step S905). Note that the processing in step S905 is the same as the processing in step S509, and thus the description thereof is omitted.
  • the platform information monitoring unit 1200 repeatedly performs the same processing until the business system is stopped.
  • the platform information monitoring unit 1200 transmits the platform information table 1100 that is the current monitoring result to the management computer 100 (step S907).
  • the infrastructure information monitoring unit 1200 also transmits the identifier of the business system 300 together with the business infrastructure basic information table 1100.
  • FIG. 21 is a flowchart for explaining processing executed by the business system monitoring unit 121 in the second embodiment of the present invention.
  • the business system monitoring unit 121 repeatedly performs the processing described below during operation (steps S1001 to S1009).
  • the business system monitoring unit 121 determines whether the business platform information table 1100 has been received (step S1003).
  • the business system monitoring unit 121 continues to wait until the business infrastructure basic information table 1100 is received.
  • the business system monitoring unit 121 identifies the business system 300 to be processed (step S1005).
  • the business system monitoring unit 121 acquires the identifier of the business system 300 received together with the business platform information table 1100.
  • the business system monitoring unit 121 calls the infrastructure management unit 130 (step S1007) and proceeds to step S1009.
  • the business system monitoring unit 121 notifies the identifier of the specified business system 300.
  • the infrastructure management unit 130 can identify the business system 300 to be processed.
  • 22A and 22B are flowcharts for explaining the processing executed by the infrastructure management unit 130 in the second embodiment of the present invention.
  • the second embodiment is different in that the loop processing of the image file is omitted at the management opportunity. This is because there is no need to specify the updated basic image file 140 because a notification indicating that the updated basic image file 140 has been added is input in advance from the service provider.
  • FIG. 23 is a flowchart for explaining processing executed by the base operation determining unit 132 in the second embodiment of the present invention.
  • the processing of the business opportunity is the same as that of the first embodiment.
  • the process from step 451 to step 459 is omitted from the first embodiment.
  • FIG. 24 is a flowchart for explaining processing executed by the difference information extraction unit 133 in the second embodiment of the present invention.
  • the processing of the management opportunity is the same as that of the first embodiment.
  • the processing from step S501 to step S509 is omitted. This is because the base information table 1100 transmitted from the base information monitoring unit 1200 is registered as difference information.
  • the processes executed by the event acquisition unit 131, the image file generation unit 134, and the result display unit 135 are the same as those in the first embodiment.
  • the process is executed when it is necessary to provide a new standard infrastructure. Therefore, when the service provider or the service user rethinks the standard infrastructure, a new standard can be quickly obtained. It is possible to present information on the base or provide a new standard base.
  • the infrastructure information monitoring unit 1200 transmits the business infrastructure infrastructure information table 1100 to the management computer 100, but the present invention is not limited to this.
  • the infrastructure information monitoring unit 1200 may transmit the infrastructure information 141 (XML file) of the business infrastructure itself.
  • FIG. 25 is a flowchart for explaining processing executed by the difference information extraction unit 133 in a modification of the second embodiment of the present invention.
  • the difference information extraction unit 133 converts the received base information 141 into the base information table 1100 of the business base (step S1101), and the converted base information table 1100 of the business base is converted. Is stored as difference information (step S511). Other processing is the same.
  • the base information monitoring unit 1200 it is not necessary for the base information monitoring unit 1200 to generate the base information table 1100 for the business base, so the load on the business system 300 can be reduced.
  • the third embodiment is different in that the effort for setting the policy 142 is reduced by using the intermediate image file.
  • FIG. 26 is a block diagram showing the configuration of the computer system in the third embodiment of the present invention.
  • the third embodiment is different in that the base information storage unit 110 stores the intermediate image file 1300.
  • the intermediate image file 1300 is an image file that mediates the policy 142 set between the basic image files 140, and includes one or more policies 1301.
  • the policy 142 included in the basic image file 140 is a policy that specifies the intermediate image file 1300.
  • the other hardware configuration of the management computer 100 is the same as that of the first embodiment, and the description thereof is omitted.
  • the procedure for generating a new deployment image file 170 is different.
  • the management computer 100 generates the meta infrastructure information table 1500 (see FIG. 28) using the infrastructure information 141 and the policy 142 of the basic image file 140.
  • the management computer 100 generates the business infrastructure information table 1100 using the meta infrastructure information table 1500 (see FIG. 28) and the policy 1301.
  • the management computer 100 generates the deployment image file 170 by reflecting the business platform information table 1100 to the platform information 141 included in the basic image file 140 specified by the policy 1301. A specific generation method will be described later.
  • FIG. 27 is an explanatory diagram showing an example of the policy 142 included in the basic image file 140 in the third embodiment of the present invention.
  • the basic image file 140 includes a policy 142 that specifies the intermediate image file 1300 instead of the policy 142 that specifies the other basic image file 140.
  • the policy 142 stores information necessary for generating the meta infrastructure information table 1500.
  • FIG. 27 shows a policy 142 for generating the meta infrastructure information table 1500 from the infrastructure information 141 for constructing a business system that operates two application servers and one database server.
  • the policy 142 includes an identification number 1401, MIDDLE_KEY 1402, and a rule 1403.
  • the identification number 1401 is the same as the identification number 901.
  • MIDDLE_KEY 1402 is an identifier for uniquely identifying a parameter group in the meta infrastructure information table 1500.
  • the rule 1403 is a conversion rule for calculating a parameter corresponding to an entry from the base information 141 or the difference information.
  • the conversion rule stores text information and mathematical formulas. For example, “the total value of the first entry and the second entry of the difference information is stored in C1” “the value of the second entry of the difference information is stored in C1, and the value of the m + 2 entry of the difference information is C2 And the like are stored.
  • FIG. 28 is an explanatory diagram showing an example of the meta-basis information table 1500 in the third embodiment of the present invention.
  • the meta infrastructure information table 1500 includes an identification number 1501, MIDDLE_KEY 1502, and a parameter group 1503.
  • the identification number 1501 is an identification number for uniquely identifying an entry included in the meta infrastructure information table 1500.
  • MIDDLE_KEY 1502 is an identifier for uniquely identifying a parameter group.
  • the parameter group 1503 stores various parameter values. In this embodiment, various parameters are calculated based on the rules 1403 included in the policy 142.
  • FIG. 29 is an explanatory diagram illustrating an example of a policy 1301 included in the intermediate image file 1300 according to the third embodiment of this invention.
  • the policy 1301 stores information necessary for generating the base information 141 to be included in the new image file.
  • the policy 142 includes an identification number 1601, S_KEY 1602, M_KEY 1603, P_KEY 1604, and a rule 1605.
  • the identification numbers 1601, S_KEY1602, M_KEY1603, and P_KEY1604 are the same as the identification numbers 901, S_KEY902, M_KEY903, and P_KEY904.
  • the conversion rule stored in the rule 1605 is different from the conversion rule stored in the rule 905. That is, the rule 1605 stores a conversion rule for generating a new base information table 1100 based on the meta base information table 1500 and the policy 1301.
  • FIG. 30 is an explanatory diagram showing the relationship between the image file 140 and the policy in the third embodiment of the present invention.
  • each basic image file 140 holds a policy 142 that designates the intermediate image file 1300, and the intermediate image file 1300 holds a policy 1301 that designates each basic image file 140.
  • the basic image file 140 holds a policy 142 that specifies the intermediate image file 1300 instead of the policy 142 that specifies the other basic image file 140.
  • the intermediate image file 1300 holds a policy 1301 that specifies a plurality of basic image files 140.
  • the basic image file 140 can designate another basic image file 140 via the intermediate image file 1300.
  • the policy 142 for specifying the intermediate image file 1300 in the basic image file 140 it is not necessary to set the policy 142 for specifying the other basic image file 140.
  • FIGS. 31A and 31B are flowcharts for explaining processing executed by the image file generation unit 134 in the third embodiment of the present invention.
  • the image file generation unit 134 starts processing when called from the infrastructure management unit 130.
  • difference information In the case of a business opportunity, one piece of difference information corresponding to the business system 300 to be processed is input. In the case of a management opportunity, difference information is input for the number of business systems 300 related to the pre-update basic image file 140.
  • the image file generation unit 134 determines whether the processing trigger is a business trigger (step S701).
  • the image file generation unit 134 retrieves the policy 142 included in the target basic image file 140 from the basic information storage unit 110 based on the identifier of the target basic image file 140. Obtain (step S703).
  • the image file generation unit 134 starts loop processing of the policy 142 (step S1201).
  • the image file generation unit 134 selects the processing target policy 142 from the acquired policies 142, and the processing from step S1203 to step S1213 is performed on the selected processing target policy 142. Repeatedly. When the processing is executed for all the policies 142, the loop processing of the policies 142 ends (step S1215).
  • the image file generation unit 134 generates the meta infrastructure information table 1500 using the selected policy 142 and the difference information (step S1203). Specifically, the following processing is executed.
  • the image file generation unit 134 refers to the policy 142 and selects one entry. For example, the image file generation unit 134 selects entries in order from the top.
  • the image file generation unit 134 calculates various parameters based on the rule 1403 of the selected entry, and generates the meta infrastructure information table 1500.
  • the image file generation unit 134 starts loop processing of the policy 1301 (step S1205).
  • the image file generation unit 134 selects the policy 1301 to be processed from the policies 1301 included in the intermediate image file 1300, and performs the processing from step S1207 on the selected policy 1301 to be processed.
  • the process of step S1211 is repeatedly executed.
  • the loop processing of policy 1301 ends (step S1213).
  • the image file generation unit 134 generates a new base information table using the selected policy 1301 and the meta base information table 1500 (step S1207). Specifically, the following processing is executed.
  • the image file generation unit 134 refers to the policy 1301 and selects one entry. For example, the image file generation unit 134 selects entries in order from the top.
  • the image file generation unit 134 calculates various parameters based on the rule 1505 of the selected entry, and generates a new base information table.
  • the image file generation unit 134 generates a new deployment image file 170 by reflecting the newly generated basic information table on the basic image file 140 specified by the selected policy 1301. (Step S1209). Further, the image file generation unit 134 updates the image association table 160 (step S1211).
  • the image file generation unit 134 adds a new entry to the image association table 160. Further, the image file generation unit 134 stores the identifier of the target basic image file 140 in the route 702 of the added entry, and adds the identifier of the newly generated deployment image file 170 to the node 703 of the entry. .
  • the deployment image file 170 is determined so as not to overlap with the identifiers of other deployment image files 170.
  • the image file generating unit 134 ends the processing.
  • the number of policies 142 in the target basic image file 140 is m and the number of policies 1301 in the intermediate image file 1300 is n
  • one business system 300 is multiplied by m and n.
  • the number of the deployed image files 170 is generated by the number of values obtained.
  • step S701 When it is determined in step S701 that the processing trigger is a management trigger, the image file generation unit 134 changes the basic information storage unit 110 to the pre-update basic image file 140 based on the identifier of the pre-update basic image file 140.
  • the included policy 142 is acquired (step S751).
  • the image file generation unit 134 starts a loop process for difference information (step S1251).
  • the image file generation unit 134 selects the difference information to be processed from the plurality of pieces of difference information, and uses the acquired policy 142 and the selected difference information, the meta infrastructure information table 1500. Is generated (step S1253). When the process is executed for all the difference information, the difference information loop process ends (step S1255).
  • step S1253 is the same process as step S1203.
  • the image file generation unit 134 starts the loop processing of the meta infrastructure information table 1500 (step S1257).
  • the image file generation unit 134 selects the target meta infrastructure information table 1500 from the meta infrastructure information table 1500 generated in step S1253, and the selected meta infrastructure information table For 1500, the processing from step S1259 to step S1265 is repeatedly executed.
  • the loop process of the meta infrastructure information table 1500 ends (step S1267).
  • the image file generation unit 134 acquires the policy 1301 from the intermediate image file 1300 (step S1259).
  • the image file generation unit 134 refers to the intermediate image file 1300 specified by the policy 142 and acquires the policy 1301 specifying the update basic image file 140.
  • the image file generation unit 134 newly generates a base information table using the acquired policy 1301 and the selected meta base information table 1500 (step S1261). Note that the process of step S1261 is the same as the process of step S1207.
  • the image file generation unit 134 generates a new deployment image file 170 by reflecting the newly generated base information table to the updated basic image file 140 (step S1263). Further, the image file generation unit 134 updates the image association table 160 (step S1266).
  • the processes in steps S1263 and S1266 are the same as the processes in steps S1209 and S1211.
  • the image file generation unit 134 ends the processing.
  • the third embodiment since it is not necessary to set the policy 142 between all the related basic image files in the basic image file 140, it is possible to save time and effort for generating a new deployment image file 170. Can be reduced. In addition, it is possible to reduce the trouble of setting the policy 142 by the service provider.
  • the first embodiment, the second embodiment, and the third embodiment can be implemented in combination, and the same effect can be obtained with any combination.
  • a plurality of components included in the management computer 100 may be a single component.
  • the various software illustrated in the present embodiment can be stored in various recording media (for example, non-temporary storage media) such as electromagnetic, electronic, and optical, and through a communication network such as the Internet. It can be downloaded to a computer.
  • recording media for example, non-temporary storage media
  • a communication network such as the Internet. It can be downloaded to a computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'objectif de l'invention est de fournir un ordinateur, un procédé et un programme offrant une infrastructure qui reflète l'état d'un système de gestion en fonctionnement. L'invention concerne un ordinateur de gestion qui gère un système de gestion construit sur une infrastructure qui fournit un système informatique exécutant une application de gestion. L'invention permet de conserver des informations d'infrastructure et une politique, et dans le cas où il est nécessaire de générer des informations sur l'infrastructure de distribution pour construire, sur une seconde infrastructure, un premier système de gestion d'objets qui a été construit sur une première infrastructure fournie par les premières informations d'infrastructure, acquiert les informations d'infrastructure de gestion du premier système de gestion d'objets, génère des informations de différence au moyen des informations d'infrastructure de gestion et des premières informations d'infrastructure, et au moyen des informations de différence et d'une politique permettant de générer des informations de seconde infrastructure pour fournir la seconde infrastructure, génère des informations de paramètres. D'après les informations des paramètres et les informations de la seconde infrastructure, les informations de distribution permettant de construire le premier système de gestion d'objets sur la seconde infrastructure sont générées.
PCT/JP2012/067299 2012-07-06 2012-07-06 Ordinateur de gestion, procédé de dotation en infrastructure et programme WO2014006739A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/067299 WO2014006739A1 (fr) 2012-07-06 2012-07-06 Ordinateur de gestion, procédé de dotation en infrastructure et programme

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2012/067299 WO2014006739A1 (fr) 2012-07-06 2012-07-06 Ordinateur de gestion, procédé de dotation en infrastructure et programme

Publications (1)

Publication Number Publication Date
WO2014006739A1 true WO2014006739A1 (fr) 2014-01-09

Family

ID=49881528

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/067299 WO2014006739A1 (fr) 2012-07-06 2012-07-06 Ordinateur de gestion, procédé de dotation en infrastructure et programme

Country Status (1)

Country Link
WO (1) WO2014006739A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016056236A1 (fr) * 2014-10-08 2016-04-14 日本電気株式会社 Dispositif de traitement d'informations, procédé de traitement d'informations et support d'enregistrement

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007183747A (ja) * 2006-01-05 2007-07-19 Hitachi Ltd 物理サーバ間のシステム移動方法およびシステム移動システム
JP2009122963A (ja) * 2007-11-15 2009-06-04 Hitachi Ltd デプロイ方法およびシステム
WO2011117958A1 (fr) * 2010-03-20 2011-09-29 株式会社Pfu Dispositif de gestion de machine virtuelle, procédé de gestion de machine virtuelle, et programme
JP2011248658A (ja) * 2010-05-27 2011-12-08 Hitachi Ltd 仮想サーバデプロイ管理装置及び方法、そのプログラム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007183747A (ja) * 2006-01-05 2007-07-19 Hitachi Ltd 物理サーバ間のシステム移動方法およびシステム移動システム
JP2009122963A (ja) * 2007-11-15 2009-06-04 Hitachi Ltd デプロイ方法およびシステム
WO2011117958A1 (fr) * 2010-03-20 2011-09-29 株式会社Pfu Dispositif de gestion de machine virtuelle, procédé de gestion de machine virtuelle, et programme
JP2011248658A (ja) * 2010-05-27 2011-12-08 Hitachi Ltd 仮想サーバデプロイ管理装置及び方法、そのプログラム

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016056236A1 (fr) * 2014-10-08 2016-04-14 日本電気株式会社 Dispositif de traitement d'informations, procédé de traitement d'informations et support d'enregistrement
US10261805B2 (en) 2014-10-08 2019-04-16 Nec Corporation Information processing apparatus for acquiring and classifying components in a configuration definition, information processing method, and recording medium

Similar Documents

Publication Publication Date Title
US8494996B2 (en) Creation and revision of network object graph topology for a network performance management system
US9501309B2 (en) Monitoring hypervisor and provisioned instances of hosted virtual machines using monitoring templates
US9674639B2 (en) Method and apparatus for virtualized network function chaining management
US11093296B2 (en) System, virtualization control apparatus, method for controlling a virtualization control apparatus, and program
EP3963442A1 (fr) Couche de données déclarative et réactive pour interfaces utilisateur basées sur des composants
US20160210175A1 (en) Method of allocating physical computing resource of computer system
JPWO2015049789A1 (ja) リソース管理システムおよびリソース管理方法
CN103430150A (zh) 在云计算系统中创建资源的技术
JP2006285316A (ja) サーバ性能計測方法及びサーバ性能計測システム並びにこれらに用いるコンピュータプログラム
US11442897B2 (en) Optimizing content storage through stubbing
US9378039B2 (en) Virtual machine storage replication schemes
JP6293683B2 (ja) 計算機システム及び計算機システムの性能障害の対処方法
JP5652480B2 (ja) データベース更新通知方法
CN111124475A (zh) 存储管理的方法、电子设备和计算机可读存储介质
WO2018131556A1 (fr) Dispositif de commande de réglage de ressources, système de commande de réglage de ressources, procédé de commande de réglage de ressources et support d'enregistrement lisible par ordinateur
US20180176289A1 (en) Information processing device, information processing system, computer-readable recording medium, and information processing method
JP2017162257A (ja) 負荷監視プログラム、負荷監視方法、情報処理装置、および情報処理システム
EP2975518A1 (fr) Système de traitement d'informations et procédé pour application de déplacement
WO2013171944A1 (fr) Système de gestion de machine virtuelle, procédé de gestion de machine virtuelle et programme
JP6393612B2 (ja) システムのバックアップ装置及びバックアップ方法
US20140173065A1 (en) Automated configuration planning
US20210184926A1 (en) Network management device and network management method
JP2019008454A (ja) 情報処理システムおよびリソース割り当て方法
JP5792325B2 (ja) 計算機システム、データ管理方法及びプログラム
WO2014006739A1 (fr) Ordinateur de gestion, procédé de dotation en infrastructure et programme

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: 12880690

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12880690

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP