CN114217846A - Production method, apparatus, electronic device, medium, and computer program product - Google Patents

Abstract

The present disclosure provides a diversity commissioning method, apparatus, electronic device, medium, and computer program product for version commissioning, which may be used in the technical field of computer product commissioning. The method comprises the following steps: acquiring a production file, wherein the production file comprises at least one of a version file and an image file; acquiring production information; when the production files comprise version files, storing the version files to a version transfer warehouse according to storage rules; when the production files comprise the mirror image files, storing the mirror image files to a mirror image transfer warehouse; generating a marking file, wherein the marking file comprises a production file list and production information; extracting the version file from the version transfer warehouse and/or extracting the mirror image file from the mirror image transfer warehouse according to the marking file; and according to the marked file, the extracted version file and/or image file are put into production.

Description

Production method, apparatus, electronic device, medium, and computer program product

Technical Field

The present disclosure relates to the field of computer production technologies, and more particularly, to a diversity production method and apparatus for version production, an electronic device, a medium, and a computer program product.

Background

Under the condition of rapid development of informatization, people can not leave the Internet and electronic terminal equipment, and the life of people is more and more convenient. However, behind the convenience, there are a very large number of software systems that provide services. For large commercial banks, thousands of systems are required, from the main core transaction, accounting, personal loan, investment and financing, to the management of human resources and employees, to the daily office, development and management, and so on. Most of these systems are deployed and run on production. Based on the particularity of the production and operation environment of the banking industry, the intercommunication between the test environment and the production environment is strictly limited. And the system commissioning needs to deploy the code compiled by the test environment to the production environment.

In addition, as container technology has attracted extensive attention in the industry, there is ample evidence to demonstrate that container technology can greatly improve work efficiency. Virtualization has become a widely recognized way of sharing server resources that provides the system administrator with great flexibility in building operating system instances on demand. The system production product is not only a simple file, but also has the production requirement of container mirror image.

Disclosure of Invention

In view of the above, the present disclosure provides a diverse commissioning method, apparatus, electronic device, computer-readable storage medium, and computer program product for version commissioning that is smooth, flexible, diverse, and simple.

One aspect of the present disclosure provides a diversity commissioning method for version commissioning, including: acquiring a production file, wherein the production file comprises at least one of a version file and an image file; acquiring commissioning information, wherein the commissioning information comprises a system name of a commissioning system; when the production file comprises the version file, storing the version file to a version transfer warehouse according to a storage rule; when the production file comprises the mirror image file, storing the mirror image file to a mirror image transfer warehouse; generating a marker file, wherein the marker file comprises a production file list and the production information, and the production file list comprises a version file list stored to the version transfer warehouse and/or an image file list stored to the image transfer warehouse; extracting the version file from the version transfer warehouse and/or extracting the image file from the image transfer warehouse according to the marking file; and according to the marking file, the extracted version file and/or the image file are put into production.

According to the diversified commissioning method for the version commissioning, the version files are stored in the version transfer warehouse and/or the image files are stored in the image transfer warehouse, and the mark files are generated, so that the commissioning files required by the commissioning system can be managed in a centralized manner, the passage from the test environment to the production environment is controlled strictly, the commissioning is implemented smoothly, and the burden from the test environment to the production environment is reduced for the system commissioning. In addition, the method and the system simultaneously support the pure version files, the pure image files and the mixed production mode of the version files and the image files, increase the flexibility and diversity of production and provide convenience for system production. In addition, the version package of the container technology of the newly added production system can facilitate production of containerized project groups, and avoids complex operations of packaging mirror images into files and then pressing the files into mirror images.

In some embodiments, the commissioning information further comprises at least one of a commissioning date and a commissioning range, wherein the commissioning range comprises a commissioning application of the commissioning system.

In some embodiments, the commissioning information further includes a commissioning type, where the commissioning type includes a commissioning priority, and when the commissioning file includes the version file, the storing the version file to a version relay repository according to a storage rule includes: and when the production files comprise the version files, storing the version files to a version transfer warehouse according to the storage rules according to the production priorities.

In some embodiments, said extracting the version file from the version relay repository and/or extracting the image file from the image relay repository according to the markup file comprises: and extracting the version file from the version transfer warehouse according to the production priority, and/or extracting the image file from the image transfer warehouse.

In some embodiments, the commissioning priority includes regular, agile, and contingency, wherein contingency > agile > regular, in order of urgency.

In some embodiments, after the extracting the version file from the version relay repository and/or the image file from the image relay repository according to the markup file, the method further includes: and storing the extracted version file and/or the image file to an NAS file system.

In some embodiments, the commissioning the extracted version file and/or image file according to the markup file includes: when the version file is extracted, the private cloud acquires the version file and updates the application; when the version file is extracted, transmitting the version file to a public cloud version warehouse, and acquiring the version file from the public cloud version warehouse and updating the application by the public cloud; and when the image file is extracted, transmitting the image file to a container platform corresponding to the image file.

Another aspect of the present disclosure provides a diversity commissioning apparatus for version commissioning, comprising: the system comprises an IT management module, a storage module and a processing module, wherein the IT management module is used for executing and acquiring a production file, and the production file comprises at least one of a version file and an image file; the IT management module is used for executing and acquiring commissioning information, wherein the commissioning information comprises a system name of a commissioning system; the storage module is used for storing the version file to a version transfer warehouse according to a storage rule when the production file comprises the version file; when the production file comprises the image file, the storage module is used for storing the image file to an image transfer warehouse; the generating module is used for executing generation of a marked file, wherein the marked file comprises a production file list and the production information, and the production file list comprises a version file list stored to the version transfer warehouse and/or an image file list stored to the image transfer warehouse; the commissioning module is used for extracting the version file from the version transfer warehouse and/or extracting the mirror image file from the mirror image transfer warehouse according to the marking file; and the commissioning module is used for commissioning the extracted version file and/or the image file according to the marking file.

In some embodiments, the commissioning module comprises: the version server is used for extracting the version file from the version transfer warehouse and putting the extracted version file into production according to the marked file; and the docker server is used for extracting the image file from the image transfer warehouse and putting the extracted image file into production according to the marked file.

Another aspect of the present disclosure provides an electronic device comprising one or more processors and one or more memories, wherein the memories are configured to store executable instructions that, when executed by the processors, implement the method as described above.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.

Another aspect of the disclosure provides a computer program product comprising a computer program comprising computer executable instructions for implementing the method as described above when executed.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

fig. 1 schematically illustrates an exemplary system architecture to which the methods, apparatus, and methods may be applied, in accordance with an embodiment of the present disclosure;

FIG. 2 schematically illustrates a flow diagram of a diversity commissioning method for version commissioning in accordance with an embodiment of the present disclosure;

FIG. 3 schematically illustrates an application environment diagram of a diversity commissioning method for version commissioning according to an embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow diagram for storing a version file to a version staging repository according to storage rules when a production file includes a version file, according to an embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow diagram for extracting a version file from a version relay repository and/or extracting an image file from an image relay repository based on a markup file according to an embodiment of the present disclosure;

FIG. 6 schematically illustrates a flow diagram for commissioning extracted version files and/or image files based on a markup file according to an embodiment of the present disclosure;

FIG. 7 schematically illustrates a block diagram of a diversity commissioning apparatus for version commissioning in accordance with an embodiment of the present disclosure;

FIG. 8 schematically illustrates a block diagram of a configuration of a commissioning module according to an embodiment of the present disclosure;

fig. 9 schematically shows a block diagram of an electronic device according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, necessary security measures are taken, and the customs of the public order is not violated. In the technical scheme of the disclosure, the data acquisition, collection, storage, use, processing, transmission, provision, disclosure, application and other processing are all in accordance with the regulations of relevant laws and regulations, necessary security measures are taken, and the public order and good custom are not violated.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, features defined as "first", "second", may explicitly or implicitly include one or more of the described features.

Under the condition of rapid development of informatization, people can not leave the Internet and electronic terminal equipment, and the life of people is more and more convenient. However, behind the convenience, there are a very large number of software systems that provide services. For large commercial banks, thousands of systems are required, from the main core transaction, accounting, personal loan, investment and financing, to the management of human resources and employees, to the daily office, development and management, and so on. Most of these systems are deployed and run on production. Based on the particularity of the production and operation environment of the banking industry, the intercommunication between the test environment and the production environment is strictly limited. And the system commissioning needs to deploy the code compiled by the test environment to the production environment.

In addition, as container technology has attracted extensive attention in the industry, there is ample evidence to demonstrate that container technology can greatly improve work efficiency. Virtualization has become a widely recognized way of sharing server resources that provides the system administrator with great flexibility in building operating system instances on demand. The system production product is not only a simple file, but also has the production requirement of container mirror image.

In the prior art, a safe and highly available file transmission scheme can be realized based on SFTP, and the system production version can be quickly and efficiently reached to the production environment on the basis of ensuring the safe and stable operation of the production environment. And aiming at systems deployed in different environments, secondary distribution can be performed according to specific scenes. However, file transfers have the following disadvantages: files are all covered in full, and incremental transmission cannot be achieved. When the system is stable, the change amount of the version of each production is smaller, but the full amount of files need to be transmitted for redeployment in each production. The development of container technology cannot be supported, if container mirror images need to be put into operation, the mirror images need to be stored into files, then transmitted and finally released into mirror images, and the use of the mirror images is extremely inconvenient.

Embodiments of the present disclosure provide a diversity commissioning method, apparatus, electronic device, computer-readable storage medium, and computer program product for version commissioning. The diversity commissioning method for the version commissioning comprises the following steps: acquiring a production file, wherein the production file comprises at least one of a version file and an image file; acquiring commissioning information, wherein the commissioning information comprises a system name of a commissioning system; when the production files comprise version files, storing the version files to a version transfer warehouse according to storage rules; when the production files comprise the mirror image files, storing the mirror image files to a mirror image transfer warehouse; generating a marker file, wherein the marker file comprises a production file list and production information, and the production file list comprises a version file list stored to a version transfer warehouse and/or an image file list stored to an image transfer warehouse; extracting the version file from the version transfer warehouse and/or extracting the mirror image file from the mirror image transfer warehouse according to the marking file; and according to the marked file, the extracted version file and/or image file are put into production.

It should be noted that the diversity commissioning method, apparatus, electronic device, computer-readable storage medium and computer program product for version commissioning according to the present disclosure may be used in the field of computer product commissioning, and may also be used in any field other than the field of computer product commissioning, such as the financial field, and the field of the present disclosure is not limited herein.

Fig. 1 schematically illustrates an exemplary system architecture 100 to which the diversity commissioning method, apparatus, electronic device, computer-readable storage medium, and computer program product for version commissioning may be applied, according to embodiments of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the diversity commissioning method for version commissioning provided by the embodiment of the present disclosure may be generally performed by the server 105. Accordingly, the diversity commissioning apparatus for version commissioning provided by the embodiments of the present disclosure may be generally disposed in the server 105. The diversity commissioning method for version commissioning provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the diversity commissioning apparatus for version commissioning provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The diversity commissioning method for version commissioning according to the embodiment of the present disclosure will be described in detail below with fig. 2 to 6 based on the scenario described in fig. 1.

Fig. 2 schematically shows a flow diagram of a diversity commissioning method for version commissioning according to an embodiment of the present disclosure.

As shown in fig. 2, the diversity commissioning method for version commissioning according to this embodiment includes operations S210 to S270.

In operation S210, a commissioning file is acquired, wherein the commissioning file includes at least one of a version file and an image file. IT should be noted that, with reference to fig. 3, after completing code development and packaging in the test environment, the developer uploads the packaged file, that is, the commissioning file, to the IT management module, and since the commissioning system and the application both need to be deployed and operated in the production environment, based on the particularity of the production and operation environment of the banking industry, the intercommunication between the test environment and the production environment is strictly limited. Deploying code compiled for a test environment to a production environment therefore requires setting up isolation zones between the test environment and the production environment.

The acquired production file can be a file which is well packaged by a developer and acquired by an IT management module, and when the actual requirement is that only an application version file of a production system is updated, the acquired production file is a version file; when the actual demand is a version package of a container technology which only updates the production system, an image file of the production file is obtained, wherein the container technology can be understood as effectively dividing resources of a single production system into isolated groups so as to better balance conflicting resource use demands among the isolated groups, and the technology is the container technology. The mirror image file can be understood as a uniform visual angle of a read-only layer and is a production version package in the container technology; and when the actual requirements are to update the application version file of the production system and update the version package of the container technology of the production system, the acquired production files are the version file and the mirror image file.

In operation S220, commissioning information is obtained, where the commissioning information includes a system name of the commissioning system, for example, when a developer uploads a commissioning file to the IT management module, the developer may enter relevant commissioning information, and thus may obtain the commissioning information.

In operation S230, when the commissioning file includes the version file, the version file is stored to the version relay repository according to the storage rule. It will be appreciated that the commissioning file includes a version file when the actual demand is to update only the application version file of the commissioning system, or when the actual demand is to update both the application version file of the commissioning system and a version package of the container technology of the commissioning system.

As some specific examples, the storage rules may be understood as naming the catalog in terms of the department to which the production system belongs, the production system name, and the production date plus the batch, thereby ensuring catalog uniqueness. Of course, the storage rules may also hierarchically name the directories in other forms to ensure uniqueness of the directories. Of course, the storage rule may also be other storage rules in a non-directory form, and the storage rule is not particularly limited herein. Therefore, the version file can be conveniently stored in the version relay warehouse according to the storage rule.

In operation S240, when the commissioning file includes the image file, the image file is stored to the image relay repository. It will be appreciated that the commissioning file includes an image file when the actual demand is a version package that only updates the container technology of the commissioning system, or when the actual demand is a version package that updates both the application version file of the commissioning system and the container technology of the commissioning system.

In operation S250, a markup file is generated, where the markup file includes a production file list and production information, and the production file list includes a version file list stored to the version relay warehouse and/or an image file list stored to the image relay warehouse. It is understood that the markup files and the production systems may be in a one-to-one correspondence, that is, one markup file is generated for one production system.

When the production file only comprises the version file, the production file list comprises a version file list which is stored to a version transfer warehouse and is required by one production system; when the production file only comprises the mirror image file, the production file list comprises a mirror image file list which is stored in a mirror image transfer warehouse and is needed by a production system; when the production files comprise version files and image files, the production file list comprises a version file list required by one production system and an image file list required by one production system, which are stored in the version transfer warehouse.

In operation S260, the version file is extracted from the version relay repository and/or the image file is extracted from the image relay repository according to the markup file. When the file list in the marked file comprises a version file list, extracting the version file on the version file list from a version transfer warehouse to a production module according to the version file list; and when the file list in the marked file comprises the mirror image file list, extracting the mirror image file on the mirror image file list from the mirror image transfer warehouse to the production module according to the mirror image file list. It should be noted that, with reference to fig. 3, the version relay warehouse and the mirror image relay warehouse may be both disposed in the isolation area, and the commissioning module is disposed in the production environment, so that the isolation area can be used to isolate the test environment from the production environment.

In operation S270, the extracted version file and/or image file is produced according to the markup file. It is understood that, since the markup file includes the production information, the production information includes the system name of the production system, and the corresponding version file and/or image file can be produced for the production system according to the system name.

According to the diversified commissioning method for the version commissioning, the version files are stored in the version transfer warehouse and/or the image files are stored in the image transfer warehouse, and the mark files are generated, so that the commissioning files required by the commissioning system can be managed in a centralized manner, the passage from the test environment to the production environment is controlled strictly, the commissioning is implemented smoothly, and the burden from the test environment to the production environment is reduced for the system commissioning. In addition, the method and the system simultaneously support the pure version files, the pure image files and the mixed production mode of the version files and the image files, increase the flexibility and diversity of production and provide convenience for system production. In addition, the version package of the container technology of the newly added production system can facilitate production of containerized project groups, and avoids complex operations of packaging mirror images into files and then pressing the files into mirror images.

In some embodiments of the present disclosure, the commissioning information may further include at least one of a commissioning date and a commissioning range, where the commissioning range includes commissioning applications of the commissioning system, for example, 5 applications, namely, an application a, an application b, an application c, an application d, and an application e, are arranged on the system a that needs to be commissioned, and assuming that the applications to be updated in the current commissioning are the application a, the application b, and the application c, the commissioning range is the application a, the application b, and the application c; assuming that the applications to be updated in the current production are application a, application d and application e, the production ranges are application a, application d and application e.

Therefore, the production information further comprises at least one of the production date and the production range, so that the production target is clearer, the time is more accurate, and the production efficiency and accuracy are improved.

According to some embodiments of the present disclosure, the commissioning information may further include a commissioning type, wherein the commissioning type includes a commissioning priority. As shown in fig. 4, when the commissioning file includes the version file, the operation S230 of storing the version file to the version relay repository according to the storage rule includes an operation S231.

In operation S231: and when the production files comprise the version files, storing the version files to a version transfer warehouse according to the storage rules according to the production priority.

As a possible implementation, the commissioning priority may include regular, agile, and contingency, where contingency > agile > regular, ordered by urgency. It is understood that the version relay warehouse may receive version files of a plurality of production systems, the plurality of production systems may have a production urgency, and the production information includes a production priority such that the version relay warehouse may receive the version files according to the production priority.

For example, the version file corresponding to the commissioning system with emergency degree may be first stored in the version relay warehouse; the version file corresponding to the commissioning system with agile emergency degree can be stored to a version transfer warehouse after emergency; the version file corresponding to the production system of which the degree of urgency is conventional may be finally stored to the version relay warehouse.

Therefore, the situation that a large amount of conventional version files are crowded and cannot be transmitted to the version transfer warehouse and emergent version files wait to be transmitted to the version transfer warehouse can be avoided through the operation S231, so that the production version files are inserted into the version transfer warehouse according to the emergency degree, and the efficiency of storing the production version files to the version transfer warehouse in the production process is improved.

According to some embodiments of the present disclosure, as shown in fig. 5, the operation S260 of extracting the version file from the version relay repository and/or extracting the image file from the image relay repository according to the markup file includes an operation S261.

In operation S261, the version file is extracted from the version relay repository and/or the image file is extracted from the image relay repository according to the commissioning priority. It can be understood that the version transfer warehouse can receive version files of a plurality of production systems with different degrees of urgency, the mirror image transfer warehouse can receive mirror image files of production systems with different degrees of urgency, the version files are extracted from the version transfer warehouse according to the production priority, and/or the mirror image files are extracted from the mirror image transfer warehouse, so that the situation that a large number of conventional production files are crowded and cannot be extracted to a production module and emergent production files wait for extraction can be avoided, the mechanism that the production files are extracted according to the degrees of urgency in an inserting team is achieved, and the production efficiency is improved.

In some embodiments of the present disclosure, as shown in fig. 2, after extracting the version file from the version intermediation repository and/or extracting the image file from the image intermediation repository according to the markup file in operation S260, the diversity commissioning method for the version commissioning further includes operation S280.

In operation S280, the extracted version file and/or image file is stored in the NAS file system, where the NAS file system may be understood as a file for storing a historical production file, has a backup capability, and supports that a problem in a production environment can be quickly returned to a historical stable version, so that safe and stable production operation can be ensured.

Fig. 6 schematically shows a flowchart of commissioning extracted version files and/or image files according to a markup file according to an embodiment of the present disclosure.

Operation S270 includes operations S271 to S273, where the extracted version file and/or image file is put into production according to the markup file.

In operation S271, when the file is extracted and published, the private cloud acquires the version file and updates the application, where the private cloud may be understood as an application system in the bank, and since the private cloud is an internal system in the bank, there are no potential safety hazards such as attacks, the private cloud may directly acquire the version file for updating, which is convenient and fast.

In operation S272, when the published file is extracted, the version file is transmitted to the public cloud version repository, and the public cloud acquires the version file from the public cloud version repository and updates the application, where the public cloud may be understood as an application system outside the bank, and since the private cloud is an external system outside the bank, there may be potential safety hazards such as attacks, the version file needs to be transmitted to the public cloud version repository first, and the public cloud may acquire the version file from the public cloud version repository and update the version file, so that the potential safety hazards are reduced.

In operation S273, when the image file is extracted, the image file is transferred to a container platform corresponding to the image file, so that the arrangement of the image file onto the corresponding container platform can be completed.

Thus, the extracted version file and/or image file can be easily produced from the markup file through operations S271 to S273.

A diversity commissioning method for version commissioning according to an embodiment of the present disclosure is described in detail below. It is to be understood that the following description is illustrative only and is not intended to be in any way limiting of the present disclosure.

Abbreviations and key term definitions follow.

IT operation and maintenance: the method refers to the comprehensive management of the whole bank organization by adopting related methods, means, technologies, systems, flows, documents and the like by a large commercial bank in order to ensure that all branches, all systems, all application systems and the like of the bank can normally work all day long.

Version production process: the software change package is deployed from a development test environment to a production environment in the iterative process of various application systems in enterprise-level IT management.

A cloudy scene: the cloud computing mode refers to a cloud computing use mode with coexisting public cloud and private cloud of a large IT enterprise, wherein the private cloud is used by an internal system of the enterprise, and the public cloud is provided for external customers, tenants and subsidiaries.

And (3) testing environment: the method is used for development and test personnel to use daily, and is mainly used for demand development, test, problem debugging and the like. The system has low access authority level and is not strictly controlled.

The production environment is as follows: the system is an environment deployed by a software system for providing services for users, and comprises a system running environment and real user data. System service access is very strict, and particularly in the financial field, multi-level authorization is often required to access the system service.

Isolation region: the method is an effective isolation area designed for the internal interaction between the development test environment and the production environment in order to meet the specific business requirement of online real-time data interaction between the internal development test environment and the production system. The isolation area is mainly characterized in that networks in a test environment and a production environment can only access the isolation area in a single direction.

A transfer machine: and the server cluster is deployed in the isolation area and is used for communicating the version file transfer server from the development test environment to the production environment.

The container technology comprises the following steps: the technology of effectively dividing resources of a single operating system into isolated groups so as to better balance conflicting resource usage requirements among the isolated groups is container technology.

Container mirroring: mirroring is a uniform view of a stack of read-only layers, which can be understood as a production version package in container technology.

Mirror image warehouse: the particular service used to store the container image may store and retrieve the container image.

The system provides various version modes for system production by combining the SFTP file transmission technology and the container technology. And meanwhile, an NAS file system is established in production and used for storing historical production version files. The service of the private cloud can access the version machine to obtain the version file; public clouds or other areas may support versioning services to proactively push to a specified file repository due to network limitations. And the container mirror image version needs to be pushed to a mirror image warehouse of a corresponding container platform through a production docker service.

The method and the system provide a version file production channel for the user and help the user to realize the version pushing to the production server. A version machine is set up in a production private cloud area, a private cloud service can be directly accessed through a network, and a version is obtained from the version machine; and the version machine of the public cloud or other network areas reaches the specified server through secondary pushing, and the user can acquire the version from the version machine of the corresponding area in a manner similar to that of the private cloud. The version machine can store the version files according to specific strategies, so that the project groups can conveniently return to the corresponding versions.

The process of production of the version file is described below.

The construction steps are as follows: after the test environment completes code development and packaging, developers upload the packaged files to an IT management system and input information related to production, including version urgency (such as routine, agility, emergency and the like).

A pushing step: after the development personnel construct the production delivery version, the IT service pushes the corresponding version file to the version transfer warehouse according to the input production delivery information, and the SFTP is used for transmitting the file in the process. And the priority of version pushing realizes the queue insertion condition according to the type of the version. Urgent versions are highest priority, next agile, and last regular. The pushed version files are named directories according to the department, system, production date and batch to which the system belongs, and the uniqueness of the directories is guaranteed; and after the push is successful, generating a marking file under the directory, wherein the file content comprises a version file list and system production information and represents that the file push transfer machine is completed.

Pulling: the transfer machine always polls locally, finds a new version and informs the version machine to pull. The version machine calculates the priority of the version according to the version file list and the system commissioning information, pulls the version file according to the priority, stores the version file in the NAS file system, and then informs the transfer machine to modify the marked file into the version which is synchronous. And then secondarily pushing the version according to the type of the system (private cloud and public cloud).

An acquisition step: the system change needs to acquire the version file, and the private cloud system can be directly arranged on the system server and download the version file from the version machine.

And (3) secondary pushing: after the version machine pulls the version file, the version file is pushed to the corresponding file server according to the type of the system (private cloud and public cloud). The file system needing secondary pushing can be added according to the actual network condition.

The method and the system provide a channel for image production, and a user uploads the version image to an IT service system when building the version. The IT service system pushes the version file and the image to a version transfer machine and a transfer image warehouse according to the specific production condition. The following describes the transmission process of the image file.

The construction steps are as follows: after the development and packaging of the codes are completed in the test environment, developers upload the version images to an IT management system and input information related to production, including the urgency of the versions (such as routine, agility, emergency and the like).

Pushing a file and mirroring: after a developer builds a production version, an IT service pushes a corresponding version file to a version transfer warehouse according to input production information, and SFTP is used for transmitting the file in the process; and pushing the corresponding mirror image to a transfer mirror image warehouse. And the priority of version pushing realizes the queue insertion condition according to the type of the version. Urgent versions are highest priority, next agile, and last regular. The pushed version files are named directories according to the department, system, production date and batch to which the system belongs, and the uniqueness of the directories is guaranteed; and after the push is successful, generating a marking file under the directory, wherein the file content comprises a version file list and system production information and represents that the file push transfer machine is completed.

Pulling a file and mirroring: the transfer machine always polls locally, finds a new version and informs the version machine to pull. The version machine calculates the priority of the version according to the version file list and the system commissioning information, pulls the version file according to the priority and stores the version file in the NAS file system; and pulling the mirror image to the local through the docker service. The transfer machine is then notified to modify the markup file to have a version that is synchronized.

A pushing step: after the version machine pulls the version file, whether the image is the container platform required to be deployed or not is identified according to the production information, and the docker service is informed to push the image to the corresponding container platform. The container platform can be expanded according to actual conditions.

Based on the above diversity commissioning method for version commissioning, the present disclosure also provides a diversity commissioning device 10 for version commissioning. The diversity commissioning apparatus 10 for version commissioning will be described in detail below with reference to fig. 7.

Fig. 7 schematically shows a block diagram of the configuration of the diversity commissioning apparatus 10 for version commissioning according to an embodiment of the present disclosure.

The diversity commissioning apparatus 10 for version commissioning includes an IT management module 1, a storage module 2, a generation module 3, and a commissioning module 4.

The IT management module 1, the IT management module 1 is configured to perform operation S210: a production file is obtained, wherein the production file comprises at least one of a version file and an image file.

The IT management module 1 is configured to perform operation S220: and acquiring the production information, wherein the production information comprises the system name of the production system.

The storage module 2, when the commissioning file includes the version file, the storage module 2 is configured to perform operation S230: and storing the version file to a version transfer warehouse according to a storage rule.

When the commissioning file includes the image file, the storage module 2 is configured to perform operation S240: and storing the mirror image file to a mirror image transfer warehouse.

A generating module 3, the generating module 3 being configured to perform operation S250: and generating a marker file, wherein the marker file comprises a production file list and production information, and the production file list comprises a version file list stored in a version transfer warehouse and/or an image file list stored in an image transfer warehouse.

A commissioning module 4 configured to perform operation S260: and extracting the version file from the version transfer warehouse and/or extracting the image file from the image transfer warehouse according to the mark file.

The commissioning module 4 is configured to perform operation S270: and according to the marked file, the extracted version file and/or image file are put into production.

Fig. 8 schematically shows a block diagram of the configuration of the commissioning module 4 according to an embodiment of the present disclosure. The commissioning module 4 includes a version server 41 and a docker server 42.

And the version server 41 is configured to extract the version file from the version relay warehouse, and to put the extracted version file into production according to the markup file, so that the version server 41 can conveniently extract the version file from the version relay warehouse and put the extracted version file into production according to the markup file.

The docker server 42 is configured to extract the image file from the image relay warehouse, and put the extracted image file into production according to the mark file, so that the docker server 42 can conveniently extract the image file from the image relay warehouse and put the extracted image file into production according to the mark file.

Since the above-mentioned diversity commissioning apparatus 10 for version commissioning is configured based on a diversity commissioning method for version commissioning, the beneficial effects of the above-mentioned diversity commissioning apparatus 10 for version commissioning are the same as those of the diversity commissioning method for version commissioning, and are not described herein again.

In addition, according to the embodiment of the present disclosure, any plurality of the IT management module 1, the storage module 2, the generation module 3, and the commissioning module 4 may be combined and implemented in one module, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module.

According to an embodiment of the present disclosure, at least one of the IT management module 1, the storage module 2, the generation module 3, and the commissioning module 4 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in any one of three implementations of software, hardware, and firmware, or in a suitable combination of any of them.

Alternatively, at least one of the IT management module 1, the storage module 2, the generation module 3 and the commissioning module 4 may be at least partially implemented as a computer program module which, when executed, may perform a corresponding function.

Fig. 9 schematically shows a block diagram of an electronic device adapted to implement a diversity commissioning method for version commissioning according to an embodiment of the present disclosure.

As shown in fig. 9, an electronic apparatus 900 according to an embodiment of the present disclosure includes a processor 901 which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage portion 908 into a Random Access Memory (RAM) 903. Processor 901 may comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 901 may also include on-board memory for caching purposes. The processor 901 may comprise a single processing unit or a plurality of processing units for performing the different actions of the method flows according to embodiments of the present disclosure.

In the RAM 903, various programs and data necessary for the operation of the electronic apparatus 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other through a bus 904. The processor 901 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 902 and/or the RAM 903. Note that the programs may also be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 900 may also include input/output (I/O) interface 905, input/output (I/O) interface 905 also connected to bus 904, according to an embodiment of the present disclosure. The electronic device 900 may also include one or more of the following components connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The driver 910 is also connected to an input/output (I/O) interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 902 and/or the RAM 903 described above and/or one or more memories other than the ROM 902 and the RAM 903.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. The program code is for causing a computer system to perform the methods of the embodiments of the disclosure when the computer program product is run on the computer system.

The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 901. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal on a network medium, and downloaded and installed through the communication section 909 and/or installed from the removable medium 911. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The computer program, when executed by the processor 901, performs the above-described functions defined in the system of the embodiment of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims (12)

1. A diversity commissioning method for version commissioning, comprising:

acquiring a production file, wherein the production file comprises at least one of a version file and an image file;

acquiring commissioning information, wherein the commissioning information comprises a system name of a commissioning system;

when the production file comprises the version file, storing the version file to a version transfer warehouse according to a storage rule;

when the production file comprises the mirror image file, storing the mirror image file to a mirror image transfer warehouse;

generating a marker file, wherein the marker file comprises a production file list and the production information, and the production file list comprises a version file list stored to the version transfer warehouse and/or an image file list stored to the image transfer warehouse;

extracting the version file from the version transfer warehouse and/or extracting the image file from the image transfer warehouse according to the marking file; and

and according to the marked file, the extracted version file and/or the image file are put into production.

2. The method of claim 1, wherein the commissioning information further comprises at least one of a commissioning date and a commissioning range, wherein the commissioning range comprises a commissioning application of the commissioning system.

3. The method of claim 1, wherein the commissioning information further comprises a commissioning type, wherein the commissioning type comprises a commissioning priority,

when the commissioning file comprises the version file, the storing the version file to a version transfer warehouse according to a storage rule comprises: and when the production files comprise the version files, storing the version files to a version transfer warehouse according to the storage rules according to the production priorities.

4. The method of claim 3, wherein extracting the version file from the version relay repository and/or extracting the image file from the image relay repository according to the markup file comprises: and extracting the version file from the version transfer warehouse according to the production priority, and/or extracting the image file from the image transfer warehouse.

5. The method of claim 3, wherein the commissioning priority includes regular, agile, and contingency, wherein contingency > agile > regular, in order of urgency.

6. The method of claim 1, wherein after the extracting the version file from the version relay repository and/or the image file from the image relay repository according to the markup file, the method further comprises: and storing the extracted version file and/or the image file to an NAS file system.

7. The method according to claim 1, wherein the commissioning the extracted version file and/or image file according to the markup file comprises:

when the version file is extracted, the private cloud acquires the version file and updates the application;

when the version file is extracted, transmitting the version file to a public cloud version warehouse, and acquiring the version file from the public cloud version warehouse and updating the application by the public cloud; and

and when the image file is extracted, transmitting the image file to a container platform corresponding to the image file.

8. A diversity commissioning apparatus for version commissioning, comprising:

the system comprises an IT management module, a storage module and a processing module, wherein the IT management module is used for executing and acquiring a production file, and the production file comprises at least one of a version file and an image file;

the IT management module is used for executing and acquiring commissioning information, wherein the commissioning information comprises a system name of a commissioning system;

the storage module is used for storing the version file to a version transfer warehouse according to a storage rule when the production file comprises the version file;

when the production file comprises the image file, the storage module is used for storing the image file to an image transfer warehouse;

the generating module is used for executing generation of a marked file, wherein the marked file comprises a production file list and the production information, and the production file list comprises a version file list stored to the version transfer warehouse and/or an image file list stored to the image transfer warehouse;

the commissioning module is used for extracting the version file from the version transfer warehouse and/or extracting the mirror image file from the mirror image transfer warehouse according to the marking file; and

and the commissioning module is used for commissioning the extracted version file and/or the image file according to the marking file.

9. The apparatus of claim 8, wherein the commissioning module comprises:

the version server is used for extracting the version file from the version transfer warehouse and putting the extracted version file into production according to the marked file; and

and the docker server is used for extracting the image file from the image transfer warehouse and putting the extracted image file into production according to the marked file.

10. An electronic device, comprising:

one or more processors;

one or more memories for storing executable instructions that, when executed by the processor, implement the method of any of claims 1-7.

11. A computer-readable storage medium having stored thereon executable instructions that when executed by a processor implement a method according to any one of claims 1 to 7.

12. A computer program product comprising a computer program comprising one or more executable instructions which, when executed by a processor, implement a method according to any one of claims 1 to 7.

Images