WO2019179459A1

WO2019179459A1 - Method and system for verifying software version

Info

Publication number: WO2019179459A1
Application number: PCT/CN2019/078856
Authority: WO
Inventors: 吴成文; 张钰
Original assignee: 中兴通讯股份有限公司
Priority date: 2018-03-23
Filing date: 2019-03-20
Publication date: 2019-09-26
Also published as: CN110297753A

Abstract

Disclosed is a method for verifying a software version. The method comprises: in a master-slave structure service network containing a master device and a slave device, where the slave device generates a new software version, the slave device loading and activating the new software version; if the slave device can successfully start the new software version, the slave device performing master-slave service synchronization with the master device, and performing master-slave switching after the completion of the synchronization; and after the slave device bears a service as a new master device, a software version management and testing platform performing service testing to verify the new software version. Further disclosed is a system for verifying a software version.

Description

Method and system for verifying software version

The present application claims the priority of the Chinese Patent Application, the entire disclosure of which is hereby incorporated by reference.

Technical field

The present disclosure relates to the field of communication technologies, for example, to a method and system for verifying a software version.

Background technique

Synstem Testing combines software, computer hardware, peripherals, networks and other elements to perform one or more assembly and validation tests of an information system. System testing is a test conducted on the entire product system. The purpose is to verify whether the final software system meets the product requirements and follows the system design to find out where the requirements are inconsistent or contradictory, thus proposing a more complete solution.

The system test process includes: developing test plans, designing test cases, performing system tests, defect management, and correcting errors. Because system testing usually begins with test planning and design test cases after product requirements and system design documentation are completed, the testers responsible for system testing and the developers responsible for software development typically work in parallel. When the tester finds a problem, the developer is usually notified to modify the code for the problem, but the modified code can easily lead to new problems, which leads to instability of the software version.

With the development of technology, people are increasingly relying on the network in their lives. Therefore, the reliability of the software version running on the network device and the update speed of the software function are put forward higher requirements. How to make the system test better serve the software Version verification, to avoid running unstable software versions on network devices, and shortening the software version generation cycle, is a problem to be solved.

Summary of the invention

The embodiments of the present disclosure provide a method and system for verifying a software version, which can shorten the time for the system to test and verify the software version, and improve the reliability of the software version.

In an embodiment, an embodiment of the present disclosure provides a method for verifying a software version, including:

In the active/standby service network including the primary device and the standby device, in the case that the standby device generates a new software version, the standby device loads and activates the new software version;

In the case that the standby device can successfully start the new software version, the standby device performs the master/slave service synchronization with the master device, and performs the active/standby switchover after the synchronization is completed.

After the standby device carries the service as a new primary device, the software version management and test platform performs a service test to verify the new software version.

In an embodiment, an embodiment of the present disclosure provides a system for verifying a software version, including:

The master device is configured to carry services in the active/standby structure service network including the master device and the standby device.

The standby device is configured to load and activate the new software version when a new software version is generated, and synchronize the active and standby services with the master device when the new software version can be successfully started. Perform the active/standby switchover after the synchronization is complete.

The software version management and test platform is configured to perform a service test to verify the new software version after the standby device carries the service as a new primary device.

DRAWINGS

FIG. 1 is a flowchart of a method for verifying a software version according to an embodiment of the present disclosure;

2 is a schematic diagram of a system for verifying a software version according to an embodiment of the present disclosure;

3 is a schematic diagram of a test system for verifying a software version in Example 1 of the embodiment of the present disclosure;

4 is a schematic diagram of a test system for verifying a software version in Example 2 of the embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a test system for verifying a software version in Example 3 of the embodiment of the present disclosure.

detailed description

Embodiments of the present disclosure will be described below with reference to the accompanying drawings. The embodiments in the present application and the features in the embodiments may be arbitrarily combined with each other without conflict.

Example 1

As shown in FIG. 1a, an embodiment of the present disclosure provides a method for verifying a software version, including:

Step 110: In the active/standby service network including the primary device and the standby device, in the case that the standby device generates a new software version, the standby device loads and activates the new software version.

Step 120: In the case that the standby device can successfully start the new software version, the standby device performs the master/slave service synchronization with the master device, and performs the active/standby switchover after the synchronization is completed.

Step 130: After the standby device carries the service as a new primary device, the software version management and test platform performs a service test to verify the new software version.

In an embodiment, the master device and the standby device are two independent devices, or the master device and the standby device are two different main control boards (main masters) disposed in one device. The number of the master devices is one, and the number of the standby devices may be one or more; for example, the master device is a master router, and the standby device is a standby router; or The master device is the main control board of the router, and the standby device is the standby main control board of the router.

In an embodiment, after the standby device loads and activates the new software version, the method further includes:

If the standby device is unable to successfully start the new software version, the standby device re-rolls back to the old software version before the new software version, and sends a new software version to the software version management and test platform. Version start failure notification.

In an embodiment, after receiving the new version startup failure notification, the software version management and test platform forwards the new version startup failure notification to the relevant personnel.

In one embodiment, prior to generating a new software version, the method further comprises:

The software version management and test platform obtains the code from the code server to the local and compiles by running the automated build script according to the set time.

The automated compilation script is written according to the requirements of the software and hardware operating environment of the new software version; wherein the hardware environment requirements are: device port, line card type, etc.; software environment requirements such as: protocol type, software function set Wait.

The software version management and test platform can automatically compile unattended by automatically obtaining code from the code server.

In an embodiment, after the software version management and test platform acquires the code from the code server to the local and compiles according to the set time, the software version management and test platform further includes:

If the compilation is successful, the software version management and test platform sends a notification that the new software version is successfully compiled to the relevant personnel; if the compilation fails, the software version management and test platform sends the new software version to the relevant personnel to compile the error. Notice. In an embodiment, the notification of successful completion of the new software version compilation or the notification of the new software version compilation error may be notified to the relevant personnel by means of short message or other communication means.

In one embodiment, the software version management and test platform performs business testing to verify new software versions, including:

If the new software version verification fails, the software version management and test platform sends a verification failure notification to the relevant personnel;

If the new software version is verified, the software version management and test platform sends a verification pass notification to the relevant personnel.

The verification may be notified to the relevant personnel by using a short message or other communication means through the notification or the verification failure notification.

In an embodiment, when the primary device and the standby device are routers, the software version management and test platform performs a service test to verify a new software version, including:

If the traffic forwarding corresponding to the service function of all services is successful, the software version management and test platform determines that the new software version is verified;

If the traffic forwarding corresponding to the service function of any one of the services is unsuccessful, the software version management and test platform determines that the new software version verification fails (ie, the verification fails), and sends an error location notification to the relevant personnel.

The error location notification may be notified to the relevant personnel by using a short message or other communication manner.

Example 2

As shown in FIG. 2, an embodiment of the present disclosure provides a system for verifying a software version, including:

The master device 201 is configured to carry the service in the active/standby structure service network including the master device and the standby device.

The standby device 202 is configured to load and activate the new software version if a new software version is generated. If the new software version can be successfully started, synchronize the active and standby services with the primary device, and synchronize. After the completion of the active/standby switchover;

The software version management and test platform 203 is configured to perform a service test to verify the new software version after the new primary device carries the service;

In an embodiment, the software version management and testing platform is further configured to acquire the code from the code server to the local and compile according to the set time by running the automated compilation script;

In an embodiment, the software version management and test platform is further configured to send a notification that the new software version is successfully compiled to the relevant personnel if the compilation is successful; and send the relevant personnel to the relevant personnel if the compilation fails. The new software version compiles a notification of the error. In an embodiment, the notification of successful completion of the new software version compilation or the notification of the new software version compilation error may be notified to the relevant personnel by means of short message or other communication means.

In an embodiment, the standby device is further configured to re-roll back to the old software version before the new software version if the new software version cannot be successfully started, and to the software The version management and test platform sends a new version start failure notification;

The software version management and test platform is further configured to receive the new version startup failure notification, and forward the new version startup failure notification to the relevant personnel;

In an embodiment, the software version management and test platform is configured to: if the new software version verification fails, send a verification failure notification to the relevant personnel; if the new software version verification passes, send the relevant software to the relevant personnel. Verify by notification.

In an embodiment, when the primary device and the standby device are routers, the software version management and test platform is configured to: if the traffic forwarding corresponding to the service function of all services is successful, determine the new If the traffic forwarding corresponding to the service function of any one of the services is unsuccessful, it is determined that the new software version verification fails, and the error location notification is sent to the relevant personnel.

Example 3

The technical solutions of the embodiments of the present disclosure are explained below by some examples.

Example 1

The test system shown in FIG. 3 includes a code server 10, a software version management and test platform (such as a personal computer (PC)) 20, a router 30, and a tester 40.

Wherein, the code server is set to provide the code of the software version to be verified. The PC is set up to get the code from the code server to the local and compile at a set time by running an automated build script. The router is a communication device to be upgraded (software version upgrade), and includes an active board 301 and a backup board 302. The main board is configured to carry a service, which is responsible for forwarding and controlling traffic, and the standby board does not carry services, that is, The standby board can receive traffic but does not forward it. The tester is set to test whether the traffic forwarding is normal, send data packets to the router, and receive data packets forwarded by the router.

The PC can acquire the code from the code server according to the set time in an unattended manner, and then compile the code by executing a script, wherein the compiled hardware environment and the software environment are preset, for example, which device is used. , which line card, which software feature set has requirements. If the compilation fails, the compilation failure message is returned and the SMS message notification is triggered to the relevant code personnel and the version manager to resolve the compilation error. If the compilation is successful, a new software version is created and generated according to preset conditions (eg, version name, etc.), and the version manager is notified by SMS or by other means of communication.

In this test system, the main board and the standby board of the router adopt the method of superimposing networking. After the new software version is generated, the new software version is loaded on the standby board. After the activation and restart, the service between the standby board and the active board is synchronized. After the synchronization is completed, the two are switched between active and standby. The original active board becomes the original board. The new spare board, the original spare board becomes the new main board. Check whether the hardware environment of the new main board is normal, whether the traffic forwarding of the service is normal, and whether the functions are normal. If there is hardware abnormality or packet loss or other abnormality, you can trigger SMS notification or use other communication methods to inform the relevant. The person is positioned incorrectly. If the new main board is tested properly, you can trigger SMS notifications or notify the version manager via the other communication methods to release the new software version.

Example 2

The test system shown in FIG. 4 includes a code server 10, a software version management and test platform (eg, PC) 20, a router 30, a tester 40, and a switch 50. Wherein, the code server is set to provide the code of the software version to be verified. The switch is set up to interconnect the code server, PC, and router into a local area network. The PC is set to retrieve code from the code server, compile the code according to a pre-set command, and generate a new software version. The router is a communication device to be upgraded (software version upgrade), and includes an active board 301 and a backup board 302. The main board is responsible for receiving service traffic and forwarding, and the standby board can receive service traffic but does not forward. The tester is set up for traffic testing: sending packets to the router and receiving packets forwarded by the router. In the test system of this example, the switch can be used to obtain code from a remote code server for version compilation, and software version upgrade for a remote router. The test system of this example verifies that the new software version is the same as the test system in Example 1.

Example 3

The test system shown in FIG. 5 includes: a code server 10, a software version management and test platform (such as a PC) 20, a main router 301, a backup router 302, and a plurality of testers (a first tester 401, a second tester) 402) and switch 50.

The code server is set to provide the code for the software version to be verified. The switch is set up to interconnect the code server, PC, primary router, and standby router. The PC is set to retrieve code from the code server, compile the code according to a pre-set command, and generate a new software version. The primary router is responsible for receiving traffic and forwarding it. The standby router can receive traffic but does not forward it. The first tester is configured to send data packets to the primary router and receive data packets sent by the primary router. The second tester is configured to send data packets to the standby router and receive data packets sent by the standby router.

The PC can use the Git command to obtain code from the remote code server to the local location at an unattended time, and then compile the code by executing a script, wherein the compiled hardware environment and the software environment are preset. For example, which device to use, which line card, which software feature set is required, and so on. The Git instruction is a distributed code version management system instruction. If the compilation fails, the compilation failure message is returned and the SMS message notification is triggered to the relevant code personnel and the version manager to resolve the compilation error. If the compilation is successful, a new software version is created and generated according to preset conditions (eg, version name, etc.), and the version manager is notified by SMS or by other means of communication.

In this test system, the primary router and the standby router adopt the method of overlay networking. After the new software version is generated, the new software version is loaded on the standby router. After the activation and restart, the standby router and the primary router perform service synchronization. After the synchronization is complete, the two perform the active/standby switchover. The original primary router becomes the new one. The standby router, the original standby router becomes the new primary router. Check whether the hardware environment of the new main router is normal, whether the traffic forwarding of one or more services is normal, and whether the required functions are normal. If there is a hardware exception or packet loss or the function is not normal, the SMS can be triggered. Notify or use other means of communication to inform the person concerned of the wrong location. If the new primary router is all tested properly, you can trigger SMS notifications or notify the version manager via the other communication methods to release the new software version.

Compared with the related art, a method and system for verifying a software version provided by an embodiment of the present disclosure, in a service network including a master device and a standby device, in a case where a new software version is generated by the standby device And the standby device loads and activates the new software version; if the standby device can start the new software version, the master device performs synchronization with the master device, and performs active/standby switchover after the synchronization is completed; After the standby device carries the service as a new primary device, the software version management and test platform performs a service test to verify the new software version. The embodiments of the present disclosure can shorten the time for the system test to verify the software version and improve the reliability of the software version.

Example 4

In an embodiment, an embodiment of the present disclosure further provides a computer readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the method of any of the above embodiments.

Storage medium - any one or more types of memory devices or storage devices. In practical applications, the foregoing storage medium may be a volatile memory, such as a random access memory (RAM), or a non-volatile memory, such as a read-only memory. Read-Only Memory (ROM), flash memory, Hard Disk Drive (HDD) or Solid-State Drive (SSD); or a combination of the above types of memory, and to the processor Provide instructions and data.

The storage medium may further include: a compact disc read-only memory (CD-ROM), a floppy disk or a magnetic tape device; a computer system memory or a random access memory such as a dynamic random access memory (Dynamic Random Access Memory, DRAM), (Double Data Rate Random Access Memory, DDR RAM), Static Random Access Memory (SRAM), Extended Data Output Random Access Memory (EDO RAM), Lan A Rambus Random Access Memory (Rambus RAM) or the like; a non-volatile memory such as a flash memory, a magnetic medium such as a hard disk or an optical storage; a register or other similar type of memory element or the like. The storage medium may also include other types of memory or a combination thereof.

The processor may be an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), or a Programmable Logic Device (Programmable Logic). Device, PLD), at least one of a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a microcontroller, and a microprocessor.

Additionally, the storage medium may be located in a first computer system in which the program is executed, or may be located in a different second computer system, the second computer system being coupled to the first computer system via a network, such as the Internet. The second computer system can provide program instructions to the first computer for execution. The term "storage medium" can include two or more storage media that can reside in different locations (eg, in different computer systems connected through a network). A storage medium may store program instructions (eg, a computer program) that can be executed by one or more processors.

Claims

A method of verifying a software version, including:

In the active/standby service network including the primary device and the standby device, in the case that the standby device generates a new software version, the standby device loads and activates the new software version;

In the case that the standby device can successfully start the new software version, the standby device synchronizes with the master device for the active/standby service, and performs the active/standby switchover after the synchronization is completed.

After the standby device carries the service as a new primary device, the software version management and test platform performs a service test to verify the new software version.
The method of claim 1, before the generating device generates a new software version, further comprising:

The software version management and test platform acquires code from the code server to the local and compiles by running the automated compilation script according to the set time.
The method according to claim 2, wherein after the software version management and test platform acquires the code from the code server to the local and compiles according to the set time by running the automatic compilation script, the software version management and test platform further includes:

In the case that the compilation is successful, the software version management and test platform sends a notification that the new software version is successfully compiled;

In case the compilation fails, the software version management and test platform sends a notification of the new software version compilation error.
The method of claim 1, after the standby device loads and activates the new software version, further comprising:

In the case that the standby device cannot successfully start the new software version, the standby device re-rolls back to the old software version before the new software version, and goes to the software version management and test platform. Send a new version to start a failure notification.
The method of claim 1 wherein said software version management and test platform performs a business test to verify said new software version, comprising:

In the case that the new software version verification fails, the software version management and test platform sends a verification failure notification;

In the case where the new software version verification is passed, the software version management and test platform sends a verification pass notification.
The method of claim 1, wherein, in a case where both the master device and the standby device are routers, the software version management and test platform performs a service test to verify the new software version, including:

The software version management and test platform determines that the new software version is verified after the traffic forwarding corresponding to the service function of all the services is successfully forwarded;

In the case that the traffic forwarding corresponding to the service function of any one of the services is not successfully forwarded, the software version management and test platform determines that the new software version verification fails, and sends an error location notification.
The method of claim 4, further comprising the software version management and test platform receiving a new version start failure notification and forwarding the new version start failure notification to the relevant personnel.
A system for verifying software versions, including:

The master device is configured to carry services in the active/standby structure service network including the master device and the standby device.

The standby device is configured to load and activate the new software version when a new software version is generated, and synchronize the active and standby services with the master device when the new software version can be successfully started. Perform the active/standby switchover after the synchronization is complete.

The software version management and test platform is configured to perform a service test to verify the new software version after the standby device carries the service as a new primary device.
The system of claim 8 wherein:

The software version management and testing platform is further configured to acquire code from the code server to the local and compile according to the set time by running the automated compilation script.
The system of claim 9 wherein:

The software version management and test platform is further configured to send a notification that the new software version is successfully compiled if the compilation is successful; and to notify the new software version compilation error when the compilation fails.
The system of claim 8 wherein:

The standby device is further configured to, after loading and activating the new software version, re-roll back to the old software before the new software version if the new software version cannot be successfully started. Version, and send a new version start failure notification to the software version management and test platform;

The software version management and test platform is further configured to receive the new version startup failure notification, and forward the new version startup failure notification to the relevant personnel.
The system of claim 8 wherein:

The software version management and test platform is configured to: send a verification failure notification if the new software version verification fails; and send a verification approval notification if the new software version verification is passed.
The system of claim 8, wherein in the case that both the master device and the standby device are routers, the software version management and test platform is configured to:

The software version management and test platform determines that the new software version is verified after the traffic forwarding corresponding to the service function of all the services is successfully forwarded;

In the case that the traffic forwarding corresponding to the service function of any one of the services is not successfully forwarded, the software version management and test platform determines that the new software version verification fails, and sends an error location notification.
A storage medium having stored therein a computer program, wherein the computer program is arranged to perform the method of any one of claims 1 to 7 at runtime.