KR101776286B1 - Server management method - Google Patents

Server management method Download PDF

Info

Publication number
KR101776286B1
KR101776286B1 KR1020150179129A KR20150179129A KR101776286B1 KR 101776286 B1 KR101776286 B1 KR 101776286B1 KR 1020150179129 A KR1020150179129 A KR 1020150179129A KR 20150179129 A KR20150179129 A KR 20150179129A KR 101776286 B1 KR101776286 B1 KR 101776286B1
Authority
KR
South Korea
Prior art keywords
patch
server
management engine
job information
virtual server
Prior art date
Application number
KR1020150179129A
Other languages
Korean (ko)
Other versions
KR20170071146A (en
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 KR1020150179129A priority Critical patent/KR101776286B1/en
Publication of KR20170071146A publication Critical patent/KR20170071146A/en
Application granted granted Critical
Publication of KR101776286B1 publication Critical patent/KR101776286B1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H04L41/0879—Manual configuration through operator
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L67/16—

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Environmental & Geological Engineering (AREA)
  • Stored Programmes (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The present invention is a computer-readable recording medium storing a program for causing a computer to execute the steps of: receiving and registering job information from a database-attached web service server; delivering a patch command to a patch target server in accordance with job information registered in a management engine unit database; And executing the patch using the patch file stored in the patch file distribution server according to the delivered patch command.

Description

Server Management Method {SERVER MANAGEMENT METHOD}

The present invention relates to a server management method, and more particularly, to a server management method for automatically patching a server according to job information registered by an administrator.

In response to rapidly changing business needs, the requirements for service support in the Information Technology (IT) sector are becoming more complex and more demanding.

There is a need to improve the complexity of management of multiple servers, to secure a server environment that can respond to continuously changing business needs, and to operate these servers.

However, conventionally, a plurality of servers operating on Hyper-V and VMWare are manually patched by the administrator. In this method, as the number of servers increases, the workload increases greatly, There is a problem that an error occurs or an omission occurs due to an increase in fatigue.

The background art of the present invention is disclosed in Korean Patent Application Publication No. 10-2014-0102482 (2014.08.22) entitled " Virtualized environment backup system and method ".

It is an object of the present invention to provide a server management method for automatically patching a server according to job information registered by an administrator.

It is another object of the present invention to provide a server management method that can perform management and operation of a server effectively by automating a patch of a server and enable stable server management.

It is still another object of the present invention to provide a server management method that improves the security of a server by reflecting fast patches, and can grasp the causes and results of a failure occurrence based on a check on the server and respond quickly.

According to an aspect of the present invention, there is provided a server management method comprising: receiving task information from a web service server; Transmitting a patch command to a server to be a patch target according to the job information registered in the database unit by the management engine unit; And performing the patch using the patch file stored in the patch file distribution server according to the patch command received from the management engine unit by the server.

In the step of receiving and registering the job information, the web service server receives the job information from the administrator terminal, and after the web service server transmits the job information to the database unit, Is registered.

The present invention is characterized by further comprising the step of backing up an operating system mounted on the server by receiving a backup command from the management engine unit before performing a patch using the patch file.

The job information of the present invention includes a patch request list and an execution date and time for the server to be patched.

The patch request list of the present invention includes a list of the servers, a group and a patch order, and the patch order is set according to a predetermined dependency between the servers.

The management engine of the present invention transmits a maintenance mode entry command to the monitoring unit before the patch command is transmitted to the server, and when the monitoring unit enters the maintenance mode entry command, And a step of skipping the step of skipping.

The management engine unit of the present invention may further include a step of checking the patch progress status for each server and storing the patch progress status in the database unit.

The database unit of the present invention generates a patch report in a patch progress state for each server and transmits the patch report to the web service server to be displayed as an administrator terminal.

The present invention is characterized in that the monitoring unit checks the server after the patching of the server is completed and transmits the check result to the management engine unit, and the management engine unit stores the check result in the database unit .

The database unit of the present invention generates a patch report as a result of the server-specific inspection, and transmits the generated patch report to the web service server to display the patch report to the administrator terminal.

The server management method according to one aspect of the present invention automatically patches a server, effectively manages and operates the server through patch automation of the server, and enables stable server management.

The server management method according to one aspect of the present invention improves the security of the server by reflecting the quick patches, and when the failure occurs, the cause and the result of the failure can be grasped based on the inspection of the server, so that the server can respond quickly.

1 is a block diagram of a server management apparatus according to an embodiment of the present invention.
2 is an exemplary view of a patch request list according to an embodiment of the present invention.
3 is an illustration of a patch report in accordance with an embodiment of the present invention.
4 is a flowchart of a server management method according to an embodiment of the present invention.

Hereinafter, a server management method according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings. In this process, the thicknesses of the lines and the sizes of the components shown in the drawings may be exaggerated for clarity and convenience of explanation. Further, the terms described below are defined in consideration of the functions of the present invention, which may vary depending on the user, the intention or custom of the operator. Therefore, definitions of these terms should be made based on the contents throughout this specification.

FIG. 1 is a block diagram of a server management apparatus according to an embodiment of the present invention. FIG. 2 is an exemplary view of a patch request list according to an exemplary embodiment of the present invention. FIG. Fig. 7 is an example of a patch report. Fig.

1, a server management apparatus according to an embodiment of the present invention includes an administrator terminal 10, a web service server 20, a database unit 30, a backup server 40, a monitoring unit 50, A file distribution server 60, a virtual server 70, and a management engine unit 80. [ Here, the administrator terminal 10, the web service server 20, the database unit 30, the backup server 40, the monitoring unit 50, the patch file distribution server 60, the virtual server 70, (80) are connected to each other through various wired / wireless communication networks to transmit / receive various information.

For reference, the virtual server 70 will be described as an example in this embodiment. However, the technical scope of the present invention is not limited to this, and can be applied to a physical server.

The administrator terminal 10 is a terminal device that allows an administrator who operates and manages the virtual server 70 to access the web service server 20 and the management engine unit 80 and provides a user interface for patching a virtual server.

More specifically, the administrator terminal 10 accesses the web service server 20 and inputs job information for a virtual server patch. The job information includes a patch request list and an execution date and time for the virtual server 70 to be a patch target.

The patch request list defines a virtual server 70 to be a patch target, and the patch request list includes a list of virtual servers 70, a group, and a patch order. As the virtual servers 70 are managed as a group based on the patch request list, the patches of the virtual servers 70 can be managed as a group. This will be described later.

The patch order is determined by the dependency of the virtual server 70. The dependency of the virtual server 70 is information that serves as a reference for defining the patch order when the patch of the virtual server 70 is performed and is information on the relationship between the virtual servers 70 related to the patch order. That is, the dependency of the virtual server 70 is information on the relationship between the virtual servers 70 when there is a virtual server 70 to be patched before any one of the virtual servers 70 is patched, May be formed between the virtual servers 70. Therefore, the patch order of each virtual server 70 is defined by the above dependency, and the patches of the virtual server 70 are sequentially performed by this dependency.

The execution date and time are time information to be executed for each virtual server 70 or group of each virtual server 70. The execution date and time is set as the date and time.

That is, the administrator can efficiently manage the patches of the respective virtual servers 70 by inputting the job information through the administrator terminal 10 as described above.

The administrator terminal 10 accesses the web service server 20 and displays a patch report on the patch progress status or the check result of the virtual server 70. [ In this way, the administrator can check the patch progress status and the check result of each virtual server 70 in real time.

The patch report can be displayed for each group of the virtual server 70 as a patch progress state and a check result for each virtual server 70. The patch report will be described later.

In addition, the administrator terminal 10 can receive and display the patch progress status of the virtual server 70 in real time from the management engine unit 80 even while the virtual server 70 is in the process of patching. In this case, the administrator can check the patch progress status of each virtual server 70 in real time, and can quickly perform patching and management for each virtual server 70 based on the real time.

The patch progress status includes whether or not the patch is currently being executed for the patch of the virtual server 70, whether the patch is currently being executed, whether the patch has been completed, whether the patch has been completed and the virtual server 70 is being rebooted, Whether it is being inspected, and so on.

As a result of the check, whether the status of the virtual server 70 in which the patch has been completed is in a normal state or not may be included.

The administrator terminal 10 may include a personal computer (PC), a laptop computer, a smart pad, etc. In addition, the administrator terminal 10 may be provided with an operating program to input / output various information, And an apparatus for transmitting and receiving various information by connecting to the engine unit 80 or the like.

The virtual server 70 reads the patch file from the patch file distribution server 60 in accordance with the patch command of the management engine unit 80 and patches the patch file using the patch file. As the virtual server 70, a virtual server 70 operating in various virtualization environments such as Hyper-V, VMWare, Ctrix Xen, and KVM may be employed.

The virtual server 70 has greatly increased in number as the service support of the IT (Information Technology) sector is expanded. As a result, it takes a very long time to manage the virtual server 70. Therefore, there has been a need to efficiently perform management and operation of the virtual server 70.

The web service server 20 receives job information from the administrator terminal 10 and registers the job information in the database unit 30. [

The web service server 20 exposes the patch report generated in the database unit 30 to the administrator terminal 10 so that the administrator can recognize the patch progress state and the check result of each virtual server 70. [

The database unit 30 receives and registers the job information from the web service server 20 and transfers the job information to the management engine unit 80. The management engine unit 80 transmits the job information to the virtual server 70 according to the job information, So that the user can perform the patch of the user.

The database unit 30 receives the patch progress status and the check result from the management engine unit 80, generates a patch report, and transmits the generated patch report to the web service server 20.

The backup server 40 backs up the operating system of the virtual server 70 to be patched in advance before the patch according to the backup command of the management engine unit 80. [ This allows you to cope with patch failures and error occurrences.

The backup command includes information on the virtual server 70 as a patch target, that is, the virtual server 70 as a backup target, information on the operating system of the virtual server 70, backup date and time, and the like. Accordingly, the backup server 40 backs up the operating system of the corresponding virtual server 70 at the backup date and time.

The patch file distribution server 60 stores the patch file. The patch file distribution server 60 detects the patch file according to a request of the virtual server 70 and delivers the patch file to the virtual server 70. [

When the monitoring unit 50 receives a maintenance mode entry command from the management engine unit 80, the monitoring unit 50 enters the maintenance mode. The maintenance mode entry command includes information on the virtual server 70 to be a patch target, execution date and time to execute the patch, and the like.

In the maintenance mode, the monitoring unit 50 skips a failure event occurring in the virtual server 70 currently being patched.

That is, a plurality of failure events may occur during the patching of the virtual server 70. [ The monitoring unit 50 skips the occurrence of a failure event in the virtual server 70 during the patching process so that the administrator terminal 10 can notify the administrator terminal 10 of an unnecessary guide character or information (The failure event generated in the patch process of the virtual server 70 is a normal event during the patch) and the like are prevented from being transmitted.

When the patch of the virtual server 70 is completed, the monitoring unit 50 enters the control mode in the maintenance mode. In the control mode, the monitoring unit 50 checks whether the corresponding virtual server 70 is in a normal state, and transmits the check result to the management engine unit 80. In this case, the monitoring unit 50 compares the operation state of the virtual server 70 that has been patched with the previously stored normal operation state, and derives the check result according to the comparison result. As described above, (70) is in a steady state.

The management engine unit 80 pats the operating system of the virtual server 70 according to the job information registered in the database unit 30. [ That is, the management engine unit 80 sequentially performs a series of processes from mounting the workflow for patching the operating system of the virtual server 70 to fetching the virtual server 70 based on the workflow .

First, the management engine unit 80 reads the job information registered in the database unit 30 and, based on the job information, checks whether there is enough free space for a patch of the virtual server 70, In advance can be performed normally.

If it is determined that the patch of the virtual server 70 can be normally performed as a result of the preliminary check, the management engine unit 80 transmits a backup command to the backup server 40, for example, a virtual server 70, that is, information on the virtual server 70 as a backup target, information on the operating system of the virtual server 70, and backup date and time. The backup server 40 backs up the operating system of the virtual server 70 to be patched in advance before the patch according to the backup command.

In addition, the management engine unit 80 transmits to the monitoring unit 50 a maintenance mode entry command, for example, information on the virtual server 70 to be a patch target, and an execution date and time to perform the patch, do. Accordingly, the monitoring unit 50 enters the maintenance mode.

Thereafter, the management engine unit 80 delivers the patch command to the virtual server 70 as the patch target, and the virtual server 70 receives the patch file from the patch file distribution server 60 and executes the patch do. In this case, as shown in FIG. 2, the management engine unit 80 performs and manages patches based on the group of the virtual servers 70 defined in the patch request list among the job information.

In addition, the management engine unit 80 checks the patch progress status of each virtual server 70 being patched, and transmits the patch progress status to the database unit 30. [

At this time, the database unit 30 stores the patch progress status for each virtual server 70 received from the management engine unit 80. [ The database unit 30 generates a patch report for each virtual server group on the basis of the patch progress status and the web service server 20 transmits the patch report from the database unit 30 when there is a request from the administrator terminal 10 And displays it to the corresponding manager terminal 10.

Referring to FIG. 3, a patch report may include at least one of a patch progress state and a check result for each virtual server group. That is, the patch report may include a virtual server group being updated, a virtual server group being rebooted, a virtual server group being checked for a core service, a virtual server group being checked for applications, and a virtual server group having been updated, A patch progress state may be included.

Thereafter, when the patch is completed in the virtual server 70, the monitoring unit 50 enters the control mode in the maintenance mode and checks whether the corresponding virtual server 70 having completed the patch is in a normal state, To the management engine unit (80).

At this time, the management engine unit 80 transmits the check result to the database unit 30 so that it can be stored.

In addition, the database unit 30 generates a patch report using the patch progress state and the check result.

Hereinafter, a method according to an embodiment of the present invention will be described in detail with reference to FIG.

4 is a flowchart of a server management method according to an embodiment of the present invention.

Referring to FIG. 4, the administrator first accesses the web service server 20 using the administrator terminal 10. At this time, when the job information is input by the administrator, the administrator terminal 10 transmits the job information to the web service server 20.

When the web service server 20 receives job information from the administrator terminal 10 (S10), the web service server 20 transmits the job information to the database unit 30 (S12), and the database unit 30 registers the job information (S14 ).

The management engine unit 80 receives the job information from the database unit 30 in step S16 and registers the job information of the virtual server 70 on the basis of the job information Pre-check to see if the patch can be done normally.

If it is determined that the patch of the virtual server 70 can be normally performed as a result of the preliminary check, the management engine unit 80 delivers the backup command to the backup server 40 according to the job information (S18).

The backup server 40 backs up the operating system of the virtual server 70 to be patched according to the backup command of the management engine unit 80 (S20).

When backup is completed by the backup server 40, the management engine unit 80 transmits a maintenance mode entry command to the monitoring unit 50 according to the job information (S22).

Accordingly, the monitoring unit 50 enters the maintenance mode (S24), and the management engine unit 80 delivers the patch command to the virtual server 70 as a patch target (S26).

The virtual server 70 receiving the patch command receives the patch file from the patch file distribution server 60 and executes the patch (S28). In this case, the management engine unit 80 performs and manages patches for each virtual server group defined in the patch request list among the job information.

Meanwhile, in the process of executing the patch as described above, a failure event may be generated in each virtual server 70, and when an actual failure event occurs, the monitoring unit 50 skips the failure event (S30, S32 ).

The management engine unit 80 checks the patch progress state until the patch of each virtual server 70 is completed (S34), and transmits the patch progress state to the database unit 30 (S36) . At this time, the database unit 30 stores the patch progress status for each virtual server group received from the management engine unit 80 (S38).

On the other hand, when the patch is completed in the virtual server 70, the monitoring unit 50 enters the control mode in the maintenance mode, checks whether the virtual server 70 is in a normal state, 80 (S40, S42).

In addition, the management engine unit 80 transfers the check result received from the monitoring unit 50 to the database unit 30 (S44), and the database unit 30 stores the check result (S46).

After storing the patch progress state and the check result, the database unit 30 generates a patch report using at least one of the patch progress state and the check result (S48).

For reference, in the present embodiment, after the patch for the virtual server 70 is completed, the patch report is generated using the patch progress state and the check result, but the technical scope of the present invention is not limited thereto. That is, the database unit 30 can generate a patch report in real time for each virtual server group, even before the patches for all the virtual servers 70 are completed.

As described above, the server management method according to an embodiment of the present invention automatically patches the virtual server 70, effectively manages and manages the virtual server 70 through patch automation of the virtual server 70, Server management can be done.

The server management method according to one aspect of the present invention improves the security of the virtual server 70 by reflecting quick patches and detects the cause and the result of the failure based on the check of the virtual server 70, So that they can respond.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is clearly understood that the same is by way of illustration and example only and is not to be taken by way of limitation, I will understand. Accordingly, the true scope of the present invention should be determined by the following claims.

10:
20: Web service server
30: Database part
40: Backup server
50: Monitoring section
60:
70: Virtual Server
80: management engine section

Claims (10)

Receiving and registering job information from a database-attached web service server;
Transmitting a patch command to a server to be a patch target according to the job information registered in the database unit by the management engine unit; And
And performing a patch using the patch file stored in the patch file distribution server according to the patch command received from the management engine unit by the server,
Wherein the job information includes a patch request list and an execution date and time for the server,
Wherein the patch request list includes a list of servers and a group and a patch order, the patch order is set according to a predetermined dependency between the servers,
The dependency is information serving as a criterion for defining the patch order when a patch of the server is performed,
Further comprising the step of pre-checking whether the management engine has free space for a patch of the server according to the job information,
The step of receiving and registering the job information includes receiving the job information from the administrator terminal by the web service server and registering the job information after the web service server transmits the job information to the database unit ,
Further comprising the step of backing up an operating system mounted on the server by receiving a backup command from the management engine unit before performing a patch using the patch file,
The backup command includes information on the server, information on the operating system of the server, and backup date and time,
The management engine transmits a maintenance mode entry command to the monitoring unit before delivering the patch command to the server, and when the monitoring unit enters the maintenance mode entry command, skips the failure event of the server generated during the patch Further comprising:
Wherein the management engine unit further comprises a step of checking the patch progress status for each server and storing the patch progress status in the database unit,
Wherein the patch progress state is determined based on whether the patch is being checked for a patch of the server, whether the patch is currently being executed, whether the patch of the server has been completed, whether the patch of the server has been completed and the server is being rebooted, Whether the patch of the server is completed and the server is under state check,
The database unit generates a patch report in the patch progress state for each server, and transmits the patch report to the web service server to be displayed as an administrator terminal.
After completing the patching of the server, the monitoring unit checks the server and transmits the check result to the management engine unit. The management engine unit stores the check result in the database unit,
The database unit generates a patch report using at least one of the patch progress status and the check result for each server, and transmits the patch report to the web service server to be exposed to the administrator terminal.
Wherein the patch report includes at least one of a patch progress status and a check result for each group of the servers,
Wherein the patch report includes a server group being updated, a server group being rebooted, a server group being checked for core service, a server group being checked for an application, and a server group having been updated.
delete delete delete delete delete delete delete delete delete
KR1020150179129A 2015-12-15 2015-12-15 Server management method KR101776286B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020150179129A KR101776286B1 (en) 2015-12-15 2015-12-15 Server management method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020150179129A KR101776286B1 (en) 2015-12-15 2015-12-15 Server management method

Publications (2)

Publication Number Publication Date
KR20170071146A KR20170071146A (en) 2017-06-23
KR101776286B1 true KR101776286B1 (en) 2017-09-07

Family

ID=59283714

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020150179129A KR101776286B1 (en) 2015-12-15 2015-12-15 Server management method

Country Status (1)

Country Link
KR (1) KR101776286B1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012168710A (en) * 2011-02-14 2012-09-06 Fujitsu Ltd Information processing system, information processing method, and control program
WO2013140524A1 (en) * 2012-03-19 2013-09-26 富士通株式会社 Program, administration server, and patch scheduling method

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012168710A (en) * 2011-02-14 2012-09-06 Fujitsu Ltd Information processing system, information processing method, and control program
WO2013140524A1 (en) * 2012-03-19 2013-09-26 富士通株式会社 Program, administration server, and patch scheduling method

Also Published As

Publication number Publication date
KR20170071146A (en) 2017-06-23

Similar Documents

Publication Publication Date Title
US11416342B2 (en) Automatically configuring boot sequence of container systems for disaster recovery
US9280374B2 (en) Virtual machine asynchronous patch management
CN107534571B (en) Method, system and computer readable medium for managing virtual network functions
US11307939B2 (en) Low impact snapshot database protection in a micro-service environment
US7703091B1 (en) Methods and apparatus for installing agents in a managed network
JP2022520005A (en) Patch management in a hybrid computing environment
JP6788178B2 (en) Setting support program, setting support method and setting support device
CN107193607B (en) Method and apparatus for updating code file, storage medium, processor, and terminal
US20140149696A1 (en) Virtual machine backup using snapshots and current configuration
US10721125B2 (en) Systems and methods for update propagation between nodes in a distributed system
CN108733553B (en) Docker-based test device configuration method, device and system
US10715594B2 (en) Systems and methods for update propagation between nodes in a distributed system
US20140380265A1 (en) Software change process orchestration
EP2474910B1 (en) Setting program, workflow creating method, and work flow creating apparatus
JP2011060035A (en) System, method and program for deploying application
US9552226B1 (en) Predictive order status system and method for computing environment
CN110727575A (en) Information processing method, system, device and storage medium
CN110268378A (en) The method for creating the data backup of virtual automation solution, the computer program of implementation method and the virtual server run by method
CN112328297B (en) Method and device for upgrading Android system running compatibly on Linux
EP3321808B1 (en) Verification system and verification method
CN102959499B (en) Computer system, storage volume management method
KR101899298B1 (en) Processing system for automation of cloud and process operating based virtual environment and processing method thereof
US9953293B2 (en) Method for controlling changes of replication directions in a multi-site disaster recovery environment for high available application
JP7025298B2 (en) Environment construction support system and environment construction support method
KR101776286B1 (en) Server management method

Legal Events

Date Code Title Description
AMND Amendment
E601 Decision to refuse application
AMND Amendment
GRNT Written decision to grant
X701 Decision to grant (after re-examination)