JP2016045675A - Software release method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To shorten work times of newly releasing software and updating the software in a service providing system, prevent a construction work error between a commercial environment and a laboratory environment, and prevent an operational error in the commercial environment.SOLUTION: A system comprises: a commercial environment that has a commercial server to be used in a service providing; and a laboratory environment that has a verification server implementing a test targeting software for the commercial server. In the laboratory environment, the test of software is performed using the verification server, and a virtual server template for release to the commercial server is prepared from the verification server to be established by the tested software. In the commercial environment, the commercial server is constructed by an image copy using the virtual server template for release to the commercial server.SELECTED DRAWING: Figure 2

Description

  The subject matter disclosed herein relates to software release and update techniques.

  Browsing of web services used from mobile phones and communication terminals (hereinafter referred to as mobile phones and mobile terminals) is indispensable as a social infrastructure system. For web systems that provide web services, There is a need for high availability and high reliability with no service interruption 24/7. A Web system that provides a Web service includes a plurality of server devices (hereinafter referred to as “servers”) in which a load balancer or a distribution device is installed in the preceding stage.

  In order to improve the availability and reliability of the Web system, when updating the software executed on the server, update is performed after the distribution of the software update target server is suppressed by the load balancer or the distribution device. Similarly, when a new server software is released, after the server is constructed in a commercial environment, distribution is performed after connection to a load balancer or distribution device.

  These methods aim to avoid a decrease in the processing performance of the entire system and a partial suspension of the service even when some servers in the system fall into a failure or a reduction in processing speed.

JP 2009-217395 A

  Software update inside the server in an environment having a service providing system (hereinafter, an environment having a service providing system is referred to as a commercial environment), such as a conventional web system to which a mobile terminal is connected, is a backup of data before update. Reflect the updated contents after acquisition. After confirming that there are no problems with the update contents, release the distribution suppression of the software update target server using the load balancer or distribution device. Similarly, for a new software release inside the server, the constructed server is connected to a load balancer or a distribution device, and distribution is performed. If a problem occurs, distribution to the constructed server is suppressed, and if there is no problem, the release is completed.

  Also, in order to confirm that there are no problems with the contents of new software releases and updates, the environment that simulates the service provision system (hereinafter referred to as the lab environment) New software release or update at. After a new software release or update, conduct a test, such as by using a test mobile device, to confirm that there are no problems.

  The new method of software release or update work by the conventional method has the following problems.

  The first problem is that the impact on the entire society when service impact occurs due to work mistakes is large, so new software release or update work can only be performed during times of low use by end users, reducing work time It is necessary.

  The second problem is that the lab environment may not be the same as the commercial environment, so there is no problem in the test performed in the lab environment, but there is a possibility that a problem may occur when it is put in the commercial environment. It is.

  A third problem is that when a worker in charge performs a new software release or update operation in a commercial environment, an operation error may occur when a setting change is performed on a server in the commercial environment.

  The first problem is that the network load can be reduced and the time for software update work can be shortened when updating software by the method of distributing the network load (paragraphs 0009 and 0010 of Patent Document 1). However, the technique of Patent Document 1 has a problem that it is not possible to reduce the backup acquisition time of the pre-update data. Since the time required to move the data for acquiring the backup data depends on the amount of the backup data, there is still a problem that the work time becomes longer due to the backup acquisition work.

  The above problems similarly exist in any communication service that the server provides to the communication terminal, that is, in the service providing system.

  In new releases or updates of software for service delivery systems (referred to as software releases), work time is reduced, construction work errors due to environmental differences between the commercial environment and the lab environment are prevented, and commercial work Provide new release and update methods that can sometimes prevent operational mistakes during software update operations.

  In this specification, in a lab environment, a new software release or update verification server is built, and the software that is the target of the new software release or update is tested. A technology for newly releasing or updating software for a commercial server in a commercial environment by creating a virtual server template and image copying the created virtual server template to the commercial environment is disclosed.

  The verification server in this specification is newly constructed when software is newly released, and is constructed by image copy from backup data of a release virtual server template when updated. When software is updated, the update target software is tested in the lab environment using a verification server constructed by copying an image from backup data of a virtual server template for release.

  That is, what is disclosed in this specification includes a first environment (for example, a commercial environment) having a commercial server used for service provision, and a verification server that performs a test on the commercial server software. In a system including a second environment (for example, a lab environment), software testing using the verification server is performed in the second environment, and the verification server constructed by the tested software is used as a commercial server. This is a software release method for creating a commercial server by creating a virtual server template for release in the first environment and by copying an image using the virtual server template for release to the commercial server in a first environment.

  The present specification further discloses that, in the second environment, a copy of the created virtual server template for release to the commercial server is created and stored as a post-release backup.

  Furthermore, in the above release method, it is disclosed that a verification server used for updating software released to the first environment is constructed using the stored post-release backup stored in the second environment.

  In order to make a commercial release virtual server template that exists in the lab environment function as a commercial backup, backup of the server that exists in the commercial environment, the virtual server template for commercial release that exists in the lab environment, and the virtual server template is a work. It is assumed that only the person in charge performs the operation and the customer does not perform the operation.

  According to the disclosure, the backup of the software to be updated necessary for the software update work of the commercial server existing in the commercial environment is acquired in the lab environment, so that the backup acquisition work in the commercial environment before the update becomes unnecessary and the work time is shortened. Is possible.

  Moreover, since the release contents and update contents for the commercial environment and the laboratory environment can be made the same, it is possible to eliminate the environmental difference between the commercial environment and the laboratory environment.

  In addition, by performing the release to the commercial environment by image copy, it is possible to minimize the operation error by the person in charge of the new software release or update work in the commercial environment.

  The disclosure enables new releases and updates of software that are highly available and reliable.

It is a schematic block diagram which illustrates the method of the conventional software new release or update. It is a schematic block diagram which illustrates the method of a software new release or update in a present Example. It is a block diagram which illustrates the update method of the software with respect to the server in which a dynamic change file exists. It is an operation | movement procedure diagram which illustrates the outline of the conventional software update method. It is an operation | movement procedure diagram which illustrates the outline of the software update method of a present Example. It is a schematic block diagram of the hardware and software of the conventional verification server and a commercial server. It is a schematic block diagram of the verification server of this example, the virtual server template for commercial release, and the hardware and software of a commercial server.

  First, a conventional software new release or update method will be described with reference to FIG.

  Conventional software new releases or updates are provided in the lab environment 105 with a physical server 201 for verification used to verify new software releases or updates in the lab environment. A commercial server 202 is provided.

  Conventionally, by using the verification physical server 201, a new server is constructed at the time of new software release, and the update work at the time of software update is performed. The person in charge of the new software release or update constructs the software on the verification physical server 201 and performs the test.

  The commercial server 202 is a server that processes service traffic from end users, and is configured in the commercial environment 106. Conventionally, at the time of commercial release, software is created and tested by the conventional physical server for verification 201, and after confirming that there is no problem, a new release or setting change is performed on the commercial server 202.

  The storage device 203 is a backup device that stores data before update before software update work is performed on the commercial server 202. When a problem occurs in the commercial release work, the commercial server 202 is restored using the backup data stored in the storage device 203.

  Next, examples will be described with reference to the drawings.

  FIG. 2 is a block diagram illustrating a method for new software release or update.

  The system of the present embodiment is created in the lab environment 105 after verifying that there is no problem by performing a test on the verification server 101 used for verification of the contents of the new software release or update, and the verification server 101. Commercial release data (abbreviated as commercial release) 102 and post-release backup data (abbreviated as post-release backup) 104 created after a successful new software release or update. And a commercial server 103 to be updated.

  The verification server 101 in the lab environment 105 and the commercial server 103 in the commercial environment 106 are, for example, virtual servers realized on a computer by a virtualization technique. The commercial release 102 and the post-release backup 104 are virtual server templates created by the virtualization template technology. The virtual server template indicates a virtual server configured as a specification that does not permit power-on and reference from the virtual machine list.

  In the case of a new release, a person in charge of a new software release or update performs a new creation using the verification server 101 in a virtual environment existing in the lab environment 105, constructs software, and performs a test. In the case of updating, construction and testing are performed by image copying from the post-release backup 104 existing in the lab environment 105 to the verification server 101.

  The commercial release 102 is created by creating software on the verification server 101 and conducting a test, confirming that there are no problems, and then creating a template for the verification server 101 built with the tested software. This is a copy of the verification server 101. The verification server 101 is released by templating, and the commercial release 102 is released to the commercial server 103 in the physically separated commercial environment 106 by image copy at the time of commercial release.

  The post-release backup 104 is a virtual server template created after the new software release and update operations of the commercial server 103 in the commercial environment 106 are completed. When the work in the commercial environment 106 is completed, the commercial release 103 is renamed, and data is stored in the lab environment 105 as a backup 104 after the release.

  The commercial server 103 is a virtual server that processes service traffic from end users, and is configured in the commercial environment 106. The person in charge of the new software release or update releases or updates the commercial server 103 by using an image copy of the commercial release 102 obtained by converting the verification server 101 into a virtual server template. Since the image copy of the virtual server template is used, the commercial release 102 can be reliably constructed.

  If a problem occurs after release or update, the post-release backup 104 corresponding to the one old state of the release or update is used to restore the state before release. If the release is successful, the work in the commercial environment 106 is completed.

  FIG. 3 illustrates a software update operation for a server in which a file created inside the server while the commercial server 103 is operating (hereinafter, a file created inside the server during operation is referred to as a dynamic change file). Show how to do it.

  The virtual server includes three virtual hard disks, and each hard disk includes an OS 301, software 302, and a definition file 303.

  The OS 301 is an area for storing OS data to be installed on the virtual server. When a new OS is installed on a virtual server, data is stored in the virtual hard disk.

  The software 302 is a hard disk in which software for a new release or update work is stored. New software releases store data in this virtual hard disk.

  The definition file 303 is a virtual hard disk that stores different information between the commercial release 102 and the commercial server 103. The information different between the commercial release 102 and the commercial server 103 indicates information specific to each server such as log data, IP address, and MAC address generated as a result of processing traffic flowing into the commercial server. Information relating to the difference between the commercial release 102 and the commercial server 103 is stored in the definition file 303.

  In the software update operation, the software 302 in the commercial release 102 in the lab environment 105 is replaced with the software 302 in the commercial server 103 existing in the commercial environment 106 to complete the update.

  FIG. 4 is an operation procedure diagram showing an example of conventional software update. The verification physical server 201 includes source code correction 401, compilation 402, and load module execution 403, and the commercial server 202 includes backup 404, source copy 405, compilation 406, load module execution 407, and backup deletion 408.

  The software update work is performed on the verification physical server 201. If there is no problem, the commercial server 202 performs the update work. After the source code correction 401 is performed in the verification physical server 201, the compilation 402 and the load module execution 403 are performed, a test is performed to check whether there is a problem in the updated contents. If there is a problem, the source code correction 401 is performed again, and the compilation 402 and the load module execution 403 are performed again. If there is no problem in the update contents, obtain a backup 404 before starting the software update work on the commercial server 202, execute the source copy 405 from the contents of the source code correction 401 made on the physical server for verification 201, Compile 402 and load module execution 403 are executed. After the load module execution 403, if there is no problem, the backup deletion 408 from the commercial server 202 is executed.

  FIG. 5 is an operation procedure diagram showing an embodiment of software update of the present embodiment. The verification server 101 includes steps of source code correction 501, compilation 502, and load module execution 503, and includes steps of virtual server template conversion 504, virtual server image copy 503, virtual server activation 504, load module Each step of execution 505 is provided.

  The processing of the verification server 101 and the commercial release 102 is performed in the lab environment 105, and the processing of the commercial server 103 is performed in the commercial environment 106.

  In the software update work performed in this embodiment, the update work (501 to 503) of the verification server 101 is performed. If there is no problem, the virtual server template 504 of the verification server 101 is created and the commercial release 102 is created. Software update is realized by performing image copy 505 on the commercial release 103 for the created commercial release 102.

  Specifically, the source code correction 501 is performed in the verification server 101, the compilation 502 and the load module execution 503 are performed, and then a test is performed as to whether there is a problem in the updated contents. If there is a problem, the source code correction 501 is performed again, and the compilation 502 and the load module execution 503 are performed again. If there is no problem in the update contents, the virtual server template creation 504 of the created verification server 101 is performed to create the commercial release 102.

  Further, the virtual server image copy 505 is performed to the commercial server 103, and the virtual server activation 506 is performed. Software update is realized by executing the load module execution 507 on the activated commercial server 103.

  After the completion of the virtual server template 504 of the verification server 101, the post-release backup 104 is created in step 508. The step 508 of creating the post-release backup 104 is preferably executed after confirming that no problem occurs in the software update on the commercial server 103.

  FIG. 6 is a hardware and software configuration diagram of a conventional verification physical server 201 and commercial server 202. The verification physical server 201 includes a physical hard disk 601, OS 602, software 603, software 604, software development environment 605, source code 606, and object module 607. The commercial server 202 includes physical hard disk 608, OS 609, software 610, software 611. A software development environment 612, a source code 613, and an object module 614.

  FIG. 7 is a hardware and software configuration diagram of the verification server 101, the commercial release 102, and the commercial server 103 according to this embodiment.

  The verification server 101 includes a virtual hard disk 701, a virtual hard disk 702, software 703, a software development environment 704, source code 705, and an object module 706. The commercial release 102 includes a virtual hard disk 707, a virtual hard disk 708, software 709, a software development environment 710, source code 711, and an object module 712. The commercial server 103 includes a virtual hard disk 713, a virtual hard disk 714, software 715, a software development environment 716, source code 717, and an object module 718.

  In the conventional hardware and software configuration, the commercial server 202 and the verification physical server 201 are different in hardware. Therefore, the source code 606 created by the verification physical server 201 is applied to the commercial server 202 and newly released or updated. In this case, the source code 606 created by the verification physical server 201 needs to be arranged at a specific location in the physical hard disk 608 of the commercial server 202. Since it was placed at a specific location, there was a possibility of mistakes due to human factors. In addition, it is necessary to obtain a backup of the data before performing the software update operation on the commercial server 202, and the software update operation takes time.

  In the hardware and software configuration of the present embodiment, after the test of the source code 705 created by the verification server 101 is completed, the verification server 101 is converted into a virtual server template and stored as a commercial release 102. Arrangement in the commercial server 103 is completed by copying the image of the commercial release 102, so that errors due to human factors during software update work can be reduced. Further, since the backup of the commercial server 202 is acquired and stored as the post-release backup 104 in the verification server 101, it is not necessary to acquire a backup in the commercial environment 106, leading to a reduction in work time.

  In addition, since the verification server 101, the commercial release 102, and the commercial server 103 create OS data and software data in units of virtual hard disks, only the virtual hard disk in which the software data is stored is migrated during software update work. It's okay.

  101: Server for verification, 102: Virtual server template for commercial release, 103: Commercial virtual server, 104: Backup virtual server template after release, 105: Lab environment, 106: Commercial environment, 201: Physical server for verification, 202: Commercial Physical server 203: Storage device 301: Virtual hard disk for storing OS area 302: Virtual hard disk for storing software area 303: Virtual hard disk for storing definition file area

Claims (3)

In a system comprising: a first environment having a commercial server used for service provision; and a second environment having a verification server for performing a test for the commercial server software,
In the second environment,
Test the software using the verification server,
Create a virtual server template for release to the commercial server from the verification server constructed by the tested software,
A software release method characterized in that, in the first environment, the commercial server is constructed by image copying using the virtual server template for release to the commercial server. The software release method according to claim 1,
In the second environment, a copy of the created virtual server template for release to the commercial server is created and stored as a post-release backup. The software release method according to claim 2,
In the second environment,
A software release method characterized by constructing the verification server used for updating software released to the first environment by using the stored post-release backup.

Images