Gray release method for IOM system

Abstract

The invention discloses a gray release method for an IOM system, and the method comprises the steps: releasing a new version into a gray environment, detecting whether an online service of the new version is normal, and releasing the new version into an original production environment when the online service of the new version is detected to be normal, thereby finishing the release of the new version. According to the invention, barriers between a production environment and a test environment are mainly eliminated, including different environments, different configurations, different codes andthe like, so that a new version can be published on line for verification earlier than before. According to the invention, version upgrading can be flexibly carried out. A certain release risk is avoided, and the influence range of product iterative upgrade is reduced; Feedback suggestions of a user are rapidly obtained, product functions are perfected, and product quality is improved. Inconvenience brought to a user due to outage release is avoided, package sending at night is not needed, and operation and maintenance and the working time of developers are more rational. The method has a disaster recovery capability, and reduces the risks of server crash, system interface abnormity and the like caused by full release.

Description

Technical field [0001] The present invention relates to software version update technology, in particular to a gray-scale release method for IOM system. Background technique [0002] When a new system or a new business goes online, a major challenge for maintenance personnel is how to switch between the new and the old system without affecting the online business. At present, most maintenance personnel release versions during the low peak period of the business at night, and many businesses can only verify their success until the next day when the business volume is normal. No matter how complete the automation and manual testing is done before going online, more or less failures may occur after the release, affecting the normal circulation of the business system, and the scope of influence is uncontrollable. It is not possible to fully hope that all potential failures will be discovered during offline testing. In the case of version upgrade failures that cannot be avoided 100%,...

AI Technical Summary

Problems solved by technology

The existing version release method adopts the form of full release, and replaces the new and old versions of all servers. This release method is relatively simple and can upgrade all servers to the latest state at one time. However, this release method There are also certain risks. If the release of a new version causes an online failure, it will affect all users using the system. The scope of the impact is large. The operation and maintenance personnel need to roll back the version urgently, and continue to release the new version next time. Increased the working hours of operation and maintenance personnel, and also caused a certain impact on the system

Images