JP2014164545A - Deployment method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem in which maintenance of an installer becomes complicated in a situation where a variety of variations such as a plurality of environments, a plurality of servers and a plurality of applications coexist.SOLUTION: A deployment method and program comprise input means to start deployment, means to acquire a host name of an execution object, means to specify an environment type and a server type from the host name, means to specify a deployment object application from the server type, means to specify a deployment enforcement application from a deployment flag of the deployment object application, means to allocate the deployment enforcement application to a destination folder, and means to allocate an application setting file corresponding to the specified environment type to the destination folder.

Description

  The present invention relates to a method and program for deploying an application to a server.

  In recent years, the keyword cloud computing or cloud has exploded in the IT industry. The shift from models that purchase and use traditional computer hardware and software to models that purchase and use services on the Internet is accelerating. The cloud is said to have three main categories.

  The first is SaaS (Software as a Service), in which a service provider provides software via the Internet, and a service user mainly uses a browser to use the target software. SaaS is almost the same as the former form called ASP (Application Service Provider). The service provider only needs to build a Web site for providing software on the Internet, and does not need to distribute the software. On the service user side, there is no need to install dedicated software on his / her computer, and in general, the target software can be used only with a browser and its plug-ins. Due to the characteristics of this SaaS, it can be used not only from so-called personal computers but also from mobile terminals such as mobile phones, small laptop computers and tablets.

  The second is PaaS (Platform as a Service), which is an application execution platform via the Internet. One example is Microsoft's Windows (registered trademark) Azure Platform, which provides Windows Azure, which is an application execution environment, and SQL Azure (registered trademark), which is a database execution environment.

  The third is IaaS (Infrastructure as a Service), a virtual machine and storage rental service via the Internet. Examples are Amazon's Amazon EC2 (registered trademark) virtual machine lending, Amazon S3 (registered trademark) storage lending.

  If a service provider wants to start a new business on the Internet, it is not necessary to prepare a computer environment by using PaaS or IaaS, so the initial capital investment is small. PaaS and IaaS are mainly models that charge according to the amount of computer resources used, and service providers can increase computer resources on PaaS and IaaS according to the scale of their business.

  With the progress of cloud computing, it has become possible to develop applications and publish them as services on the Internet easily and at a lower cost than before. In addition, the above-mentioned IaaS virtual machine lending service can be used to build an environment for developing and testing applications only when necessary, which helps to improve the efficiency of development and testing. be able to. When developing and publishing a service, it is necessary to have multiple environments, such as a development environment for performing development, a test environment for performing tests, and a production environment for publishing to the general public. Also, for development purposes, it is necessary to have multiple environments suitable for various purposes, such as for maintaining existing versions, for developing new versions, for testing purposes, for performance testing, for functional testing, etc. May come.

  In order to provide a certain service, it is necessary to place and set the developed application on a server that is a virtual machine or a physical machine. (Hereafter, the task of placing and setting applications on the server is called deployment.) When the number of servers or applications is small, the worker manually places the application files on the server or changes the setting values. There is not much problem even if you go there. However, when the number of applications increases or the number of servers at the placement destination increases, an installer is generally created in order to efficiently perform the placement work.

JP 2004-302929 A

  Patent Document 1 proposes an installation automation method for efficiently installing a plurality of applications. According to this prior art, the installation work in a specific server can be made efficient.

  There is also an automatic installation method generally known as silent installation. The installer can display the user interface and allow the operator to input necessary data when executing the installation. The silent installation described above is a method of automating the installation by previously describing data as an alternative to the input in a response file instead of inputting the data from the user interface.

  However, as described above, under various circumstances such as a plurality of environments, a plurality of servers, a plurality of applications, and the like, there are the following problems when trying to apply these installation automation methods. Even if the same application is arranged separately in a plurality of environments, it is necessary to make application settings according to the environment. Therefore, if automatic installation is to be performed, it is necessary to create and prepare response files corresponding to the number of variations, and this maintenance is troublesome. In addition, it is necessary to appropriately specify and use each server and a response file corresponding to the server, and if this is mistaken, a failure that an unintended application is arranged on the server may occur.

  In order to solve the above problems, the system of the present invention has the following configuration.

  Deployment start input means (S1101), execution target host name acquisition means (S1102), environment type and server type identification means (S1105, 901) from the host name, and deployment target from the server type Means for identifying an application (S1106, 921), means for identifying a deployment application from the deployment flag of the application to be deployed (S1109, S1110, 933), and means for placing the deployment application in a destination folder (S1112) ) And means (S1113) for arranging an application setting file corresponding to the specified environment type in a destination folder.

  According to the deployment method and program of claim 1, it is possible to reduce human mistakes during the deployment work, and it is possible to manage environment dependent variables for each environment type in a unified manner, and maintenance is easy. Become.

Subsystem configuration diagram Multiple environment subsystem configuration diagram Application file structure explanatory diagram Network configuration diagram Computer logical configuration diagram Build server internal configuration diagram Table 1 Server internal configuration diagram Table 2 and Table 3 Table 4 Flow chart part 1 Flow chart part 2

  The specific problem to be solved by the present invention will be described in more detail with reference to FIGS.

  FIG. 1 shows application placement on a server group in a certain subsystem. Reference numeral 101 denotes the entire subsystem. Reference numerals 111 to 115 denote servers. Reference numerals 121 to 123, 131 to 133, and 141 denote applications. For example, 111 and 112 are responsible for the role of the Web server, and applications 01, 02, and 03 are arranged. Similarly, 113 and 114 are WebService servers, and applications 11, 12, and 13 are arranged therein. Similarly, 115 is a Batch server, and the application 21 is arranged.

  FIG. 2 is a diagram showing that a plurality of environments exist as a plurality of subsystems. Reference numerals 201 to 204 denote each subsystem. In order to identify the environment, a name indicating the environment type such as DV1, DV2, EV1, EV2 is given.

  FIG. 3 shows a configuration example of a file group constituting an application. Reference numeral 301 denotes a folder on the file system for storing applications. Reference numeral 311 denotes an application execution file. Reference numeral 312 denotes an application library file. Reference numeral 313 denotes an application setting file. Reference numerals 321 and 322 denote setting contents of the setting file 313. 321 is a setting for EV1, and 322 is a setting for EV2. For example, examples of setting values that need to be changed for each environment, such as address information of a connection destination server used by an application for a communication function, link destination URL information, and database connection information are shown.

  First, as shown in FIG. 1, there are a plurality of server types, and the application to be arranged is different for each server type. Furthermore, as shown in FIG. 2, there are a plurality of environment types. As shown in FIG. 3, each application includes a setting file that needs to be changed for each environment. First, it can be seen that there are application placement variations of the number of server types × the number of environment types.

  In addition, as a characteristic of a service to be disclosed on the Internet, it is usual to periodically upgrade the version on a subsystem basis for the purpose of adding functions or correcting disadvantages. In addition, it is necessary to deploy the version under development to a development environment or test environment for the purpose of debugging and testing. However, the application that needs to be replaced when performing version upgrade is only the application that has been changed. That is, among the many applications in FIG. 1, the replacement target application is different for each version. In addition to the application arrangement variation of the number of server types × the number of environment types described above, the variation for each version is added, so that the complexity of maintenance is further increased.

  If it is intended to support these variations by creating an installer, it is necessary to prepare a response file of the number of server types × the number of environment types. In addition, it is necessary to rebuild the installer by respecifying the installation target application for each version. That is, there is a problem that a great deal of maintenance work such as maintenance of the response file of the installer, redesignation of the installation target application, rebuilding of the installer, etc. is required for many of these variations.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

  FIG. 4 shows an example of a network configuration for carrying out the present invention. Reference numeral 401 denotes a network indicating the Internet or an intranet. Reference numeral 402 denotes a network device for connecting networks such as a router and a switch. A firewall 403 controls communication permission between networks. Reference numeral 404 denotes a LAN (Local Area Network). Reference numerals 405 and 406 denote server computers. Reference numeral 407 denotes a hypervisor, which performs computer virtualization. Reference numeral 408 denotes a virtual machine that operates on the harper visor 407. Reference numeral 409 denotes a client computer. The client computer 409 can access a Web server or an application server running on the server computer 405 or the virtual machine 408 via a network connection. Reference numeral 410 denotes a server computer for building an application. Reference numeral 411 denotes a client computer that is connected to the build server 410 and is used for committing the source code of the application and acquiring a build result.

  FIG. 5 shows a logical configuration of information processing functions of the server computers 405 and 410, the virtual machine 408, and the client computers 409 and 411. A user interface 501 inputs and outputs information using a display, a keyboard, a mouse, and the like. Computers without these hardware can be connected and operated from other computers by remote desktop or the like. A network interface 502 is connected to a network such as a LAN and communicates with other computers and network devices. Reference numeral 504 denotes a ROM in which an embedded program and data are recorded. Reference numeral 505 denotes a RAM which is a temporary memory area. Reference numeral 506 denotes a secondary storage device represented by an HDD. A CPU 503 executes a program read from the ROM 504, RAM 505, secondary storage device 506, and the like. Each unit is connected via an input / output interface 507.

  FIG. 6 shows the internal configuration of the build server 410. Reference numeral 601 denotes a repository that stores a source file 602 of the developed application. Reference numeral 611 denotes a file system on the operating system. Reference numeral 612 denotes an application file group output on the file system 611. Reference numeral 621 denotes a build tool, and 622 denotes a program (1).

  A source file of an application developed on the client computer 409 is stored as a source file 602 in the repository 601. When the build of the application is executed by the build tool 621, the source file 602 is compiled, and an application file group 612 of the final product such as an application execution file is output.

  FIG. 7 shows a table 701 for storing environment dependent variables. Reference numeral 711 denotes a key string, and 712 denotes a value string.

  As shown in FIG. 3, the application setting file 313 needs to set setting values for the environment in order to operate correctly in a plurality of environments. The program (1) 622 searches for a setting file in the application file group 612, acquires environment-dependent variables from the table 701, and embeds them in the setting file 313. For example, assume that the original configuration file is App01.config. In the original configuration file, targetServer =% _ targetServer% is set to identify environment dependent variables. When the program (1) 622 is executed, the character string portion of% _targetServer% is replaced with the environment dependent variable acquired from the table 701 for all environments. For example, the table 701 stores variables for the test 1 environment. The replacement target character string portion in the original App01.config is replaced with the value in the value column 712, and the test 1 environment named App01.config.EV1 is stored. Output the configuration file. This table 701 is prepared for each environment type, and similarly, setting files for other environments are also output. For example, the configuration file for the test 2 environment is App01.config.EV2.

  FIG. 8 shows the internal configuration of the servers 405 and 408. 831 is a file system on the operating system of the server. Reference numeral 832 denotes a folder on the file system 831. Reference numeral 832 denotes a folder in which the application file group (1) 612 output by the build tool 621 and the program (1) 622 is temporarily arranged. Reference numeral 833 denotes a folder on the file system 831. Reference numeral 833 denotes an arrangement destination of the deployment target application, which includes one or a plurality of folders. Reference numeral 834 denotes an application file group (2). The application file group (2) 834 is executed on the servers 405 and 408 and provides application functions. Reference numeral 835 denotes the program (2).

  FIG. 9 shows tables 901 and 921 used by the program (2) 835. Reference numeral 911 denotes a host name string. Reference numeral 912 denotes an environment type column. Reference numeral 913 denotes a server type column. By referring to the table 901, it is possible to determine to which environment a server having a specific host name belongs and which server type. Reference numeral 931 denotes a server type column. Reference numeral 932 denotes an application column. Reference numeral 933 denotes a deployment flag string. By referring to the table 921, an application that needs to be arranged can be identified from the application column 932 for a server of a certain server type. Further, it can be determined from the deployment flag column 933 whether or not those applications are targets of deployment in the current version.

  FIG. 10 shows a table 1001 used by the program (2) 835. Reference numeral 1011 denotes an application string. Reference numeral 1012 denotes an original file storage folder string. Reference numeral 1012 corresponds to any one of folders 832 and lower. Reference numeral 1013 denotes a destination folder string. Reference numeral 1013 corresponds to one of the folders 833 and below. Reference numeral 1014 denotes an application setting file sequence. Reference numeral 1014 denotes the file name of the original application setting file. Reference numeral 1015 denotes an environment-specific application setting file string. Reference numeral 1015 indicates the file name of the setting file for each environment type by replacing the% suffix% portion with the environment types EV1, EV2, and the like. For example, App01.config.EV1, App01.config.EV2, etc.

  FIG. 11 is a flowchart showing a flow of application / deployment execution by the program (2) 835. When the program (2) 835 is executed on the server 405 or 408, a selection input for starting deployment is first received (S1101). When the deployment is canceled, the interruption is notified to the user and the program is terminated (S1108). When the start of deployment is instructed, the program (2) 835 inquires the operating system and acquires the host name of the server 405 or 408 (S1102). Next, the table 901 is searched, and a record matching the acquired host name is acquired (S1103).

  If no matching record is obtained, the user is notified of the interruption and the program is terminated (S1108). If a matching record can be acquired, the environment type and server type to which the server of the corresponding host name belongs are acquired from the record (S1105). The table 921 is further searched from the acquired server types, and a list of applications to be deployed is acquired for the corresponding server types (S1106). If there is no application to be deployed, the interruption is notified to the user and the program is terminated (S1108).

  Next, the number of deployment target applications is determined (S1107). When there are one or more deployment target applications, the following loop processing is executed for each application. First, a deployment flag for the first application is acquired from the deployment flag column 933 (S1109). The acquired deployment flag is determined (S1110). When the deployment flag is determined to be 0, the next loop process is continued without performing any process. When the deployment flag is determined to be 1, the placement information of the application is acquired from the table 1001 (S1111). The copy source and destination of the application file are specified from the original storage folder column 1012 and the destination folder column 1013, and the application file is arranged in the destination folder (S1112).

  Furthermore, the setting file for the environment type specified from the environment type column 912 is renamed to the same name as the original file and placed in the destination folder (S1113). For example, when the host name is “ev1web01”, the environment type is “EV1”, so the prepared App01.config.EV1 is renamed to App01.config and placed in the destination folder. As a result, it is possible to automatically determine the environment type and automatically set the environment dependent variables necessary for the corresponding environment type.

  The loop processing is executed in the same manner for the second and subsequent applications. Finally, a comparison process between the arranged application arrangement information and the original application information is performed (S1114). For example, the file name, time stamp information, version information, and the like of the application file are compared to check whether they match, and verify that the correct file has been placed in the destination folder. If the comparison result is correct, the user is notified of success and the program is terminated (S1116). If the comparison result is not correct, an error is notified to the user and the program is terminated (S1117).

  FIG. 12 is a flowchart when executing a build. Considering that the application is continuously upgraded, when the build server 410 executes a build of a new version, only the application whose source file 602 has been changed is set to “1” in the deployment flag 933. Prepare a means. First, the build is executed by the build tool 621 (S1201). At this time, if a differential build is applied, only the application that has changed is built.

  Thereafter, the following loop processing is executed for each application. First, it is determined whether or not an application has been changed (S1202). If there is a change, “1” is set to the deployment flag 933 of the table 921 (S1203). If there is no change, “0” is set to the deployment flag 933 of the table 921 (S1204). Repeat the loop process for the number of applications. By means of this automatic update means of the deployment flag, it is possible to replace only the application that has been changed when the deployment is performed when the application is upgraded.

  As described above, according to the deployment method and program described above, the information to be managed for each environment is collected in the tables 701, 901, and 921, so that maintenance is facilitated. In addition, the deployer automatically determines the environment type and the server type by simply instructing the program (2) 835 to execute the deployment, and the target application is automatically arranged, thus eliminating human work mistakes. Is possible.

101 Subsystem 111-115 Servers 121-123, 131-133 and 141 Applications

Claims (5)

Deployment start input means (S1101), execution target host name acquisition means (S1102), environment type and server type identification means (S1105, 901) from the host name, and deployment target from the server type Means for identifying an application (S1106, 921), means for identifying a deployment application from the deployment flag of the application to be deployed (S1109, S1110, 933), and means for placing the deployment application in a destination folder (S1112) ) And means (S1113) for arranging an application setting file corresponding to the specified environment type in a destination folder. The deployment method and program according to claim 1, further comprising means (S1111 and 1001) for acquiring arrangement information of the deployment execution application. The deployment method and program according to claim 1, wherein comparison processing (S <b> 1114) of deployed application (834) information and original application (612) information is performed. The deployment flag of the deployment target application according to claim 1 is a means for setting the deployment flag to “1” for the application with change (S1203) and the deployment flag to “0” for the application without change at the time of build execution. The deployment method and program according to claim 1, wherein the deployment method and program are provided by means (S1204). The application setting file according to claim 1 is provided by means for automatically generating an application setting file for each environment type with reference to the environment dependent variable table (701) for each environment type. The deployment method and program described.