CN104702423A - Version dynamic-management method and device for distributed system - Google Patents
Version dynamic-management method and device for distributed system Download PDFInfo
- Publication number
- CN104702423A CN104702423A CN201310647908.7A CN201310647908A CN104702423A CN 104702423 A CN104702423 A CN 104702423A CN 201310647908 A CN201310647908 A CN 201310647908A CN 104702423 A CN104702423 A CN 104702423A
- Authority
- CN
- China
- Prior art keywords
- version
- file
- business board
- master control
- download
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
In a version dynamic-management method for a distributed system provided by the invention, a main control board manages and controls the version of the whole system in a unified manner. The method comprises the following steps: the main control board indicates a service board to perform version updating; the service board starts version updating and downloading after receiving the indication; the service board downloads a version file successfully, and uses the successfully downloaded version file to update a current version file; and the service board is restarted after version file updating.
Description
Technical field
The present invention relates to network device management field, particularly relate to a kind of version dynamic management approach of distributed system.
Background technology
Current core net constantly carries out dilatation along with constantly adapting to the demand in market, and final equipment of the core network will develop into a huge cluster tool.The version management how effectively could carrying out equipment is particularly outstanding instantly.Version management in the past, depends on manual site and safeguards; The cutover of existing network or upgrading, operating personnel are manual to be in advance uploaded to version on the memory of all devices respectively by network.Under this mode, the device version of existing network controls to become blank, and the efficiency of version updating can only be ensured by artificial; The standard operation of operating personnel can only be instructed by reference books, cannot avoid occurring human error; Can not shield the accident in version updating process completely, such as, in version updating process, equipment restarts the version updating failure caused.Version management cannot be ensured in efficiency and reliability.The upgrading tool of current use is that one can, directly by arranging device IP, adopt FTP mode by the upgrade software under the equipment that is automatically the uploaded to specified path of the files in batch of renewal.In version updating, the operating process that live version upgrades can be simplified, raise the efficiency.Adopt upgrading tool to carry out existing network version updating, instead of part manual operations, substantially increase the efficiency of version updating, but still the demand of existing network version dynamic management cannot be met; The version compatibility of equipment, the validity of version, still need artificial guarantee.
Summary of the invention
For the problems referred to above, the present invention proposes a kind of version dynamic management approach of distributed system, comprising: master control borad indicating services plate carries out version updating; After business board receives described instruction, start version updating and download; After business board success download version file, the version file using described success to download upgrades current version file; After version file upgrades, business board is restarted.
Preferably, the method also comprises: business board, to master control borad transmission board login request message, carries business board current version number; Described master control borad judges whether access according to business board current version number: if access, then return registration response success message to business board, plate register flow path terminates; Otherwise master control borad indicating services plate carries out version updating.Wherein, basis for estimation is whether version number meets baseline version matching principle, such as: different baseline version not access, each patch release under same baseline version and its debug version compatible.
Preferably, version updating is downloaded and is specifically comprised: business board signs in master control borad and reads revision table file, and the content of version file with described revision table file is strictly mated; Download all strictly version files that the match is successful.Wherein, all version file list of file names of revision table file record version and version file length.
Preferably, after business board success download version file, the version file using described success to download upgrades current version file and specifically comprises: business board carries out length check to the version file downloaded successively according to the file size of described revision table file record, if verification succeeds, then the version file of described download is used to replace current version file; Once verify unsuccessfully, then stop verification, restart version updating and download.
Preferably, the method also comprises detection Current hardware type when business board starts, and when starting version updating download, under signing in master control borad memory device version default path, selects corresponding version file according to its type of hardware.
The present invention also proposes a kind of edition management device of distributed system, and this device comprises configuration module, for configuring each device version Matching Relationship; Memory module, for storing the version file of each version of each equipment; Control module, for according to device version Matching Relationship each in configuration module, judges also whether indicating equipment carries out version updating; Transport module, during for needing when equipment to carry out version updating, provides the download of version file in described memory module.
Method provided by the invention had both met the multi-version compatibility under existing network certain condition; existing network equipment automatic version updating under certain condition can be made again; in version updating, device version upgrades and is separated with device hardware type, has good abnormal protection measure.Adopt the present invention can meet the demand of existing network version dynamic management, reduce existing network maintenance cost, simple version is new technological process more simultaneously.
Accompanying drawing explanation
Fig. 1 is version dynamic management approach flow chart of the present invention.
Embodiment
For making object of the present invention, technical scheme and beneficial effect are clearly understood, hereafter will be described in further detail each technical scheme of the present invention by reference to the accompanying drawings.It should be noted that, when not conflicting, the technical characteristic in each embodiment of the application and embodiment can combine mutually arbitrarily.
Under the present invention is applicable to distributed structure/architecture, the effective way to manage of one that the version for devices in system carries out.Under distributed structure/architecture, all devices unification carries out equipment control maintenance by a master control borad, and other equipment carry out interacting message by communication between plates respectively and between master control borad as independently business board.
Please refer to accompanying drawing 1, is version dynamic management approach flow chart of the present invention.Basic skills of the present invention comprises: business board, to master control borad transmission board login request message, carries business board current version number; Master control borad judges whether to need to upgrade version according to business board current version number, if without the need to upgrading version, then return registration response success message to business board, plate register flow path terminates; Otherwise master control borad indicating services plate carries out version updating; After business board receives described instruction, start version updating and download; Business board carries out version backup, and whether the version file that verification is downloaded is correct, if correctly, then uses correct version file to upgrade current version file; After version file upgrades, business board is restarted, and again initiates veneer registration request; If verify incorrect, then again initiate registration request.
The key step of the method comprises: recover when business board and master control borad communication between plates lose even, or in Added Business plate situation, first business board sends out plate login request message to master control borad, carries business board current version number.Now master control borad needs originally to control effectively to whole half tone.The first step: master control borad effectively judges whether to allow its access according to business board current version number.Basis for estimation is whether version number meets baseline version matching principle, and namely whether baseline version R00xD0xB0x is consistent; If the match is successful, master control borad thinks that its version number is legal, and direct Returning plate registration response success message is to business board, and plate register flow path terminates; If it fails to match, master control borad thinks that its version number is illegal, and need upgrade version just can access; Second step: master control borad bill plate version updating Indication message is to business board.Business board is receiving after single board edition that master control borad sends upgrades Indication message, starts version updating downloading process: a) FTP signs under master control borad memory device mates version path corresponding to this plate type of hardware; B) the All Files detailed bill under master control borad current path is obtained; C) read updatefilelist.txt file content under master control borad current path and strictly mate with lists of documents file; D) all files that the match is successful are prepared to download.Business board downloads the file that the match is successful successively, and download file is added suffix .temp temporary file form with old file name is kept under this locality deposits the default path of version.After business board has been downloaded, the size byte number of download file is mated with log file byte number in updatefilelist.txt file, if the match is successful, then delete original file, temporary file is removed suffix .temp and rename; All download files mate successively, once occur that it fails to match, then stop coupling, business board sends out plate login request message to master control borad again, restarts version updating; If all the match is successful, business board autoboot.Business board starts the version number after carrying renewal successfully and again sends out plate registration request to master control borad subsequently.Now master control borad judges that business board current version number and baseline version are number consistent and thinks that its version is legal version, and bill plate registration reply message is to business board; Plate register flow path terminates.
In said method, master control borad is to the unified management of the whole network version and control; System clearly plans that version is in version number corresponding to each stage, and if version number is R00xD0xB0xSPx.xx, baseline version number is R00xD0xB0x, SPx is patch release number, and .xx is interim debug version number.Recover when business board and master control borad communication between plates lose even, or in Added Business plate situation, all can send out plate login request message and carry business board current version number to master control borad by trigger business plate, whether effectively service control plate current version is carried out by master control borad, realize different baseline version not access, the edition compatibility of each patch release under same baseline version and the debug version of patch release.The multiple check of business board in version updating process; Updatefilelist.txt file is with the supporting issue of version, and its content is All Files list of file names (comprise file name suffix, upper and lower case letter is strictly distinguished), the file size (byte number) that version is issued.Business board when starting version and downloading by updatefilelist.txt file in version file name judge which file needs to download under version path; After download completes, whether the file being verified download by version file details in updatefilelist.txt file is consistent with original, thus realizes the verification upgrading version, ensures the accuracy of version updating.Realized by message mechanism based on the communication between plates under distributed system architecture; Lose at business board and master control borad communication between plates and connect rear recovery, or in Added Business plate situation, business board all needs to send out plate login request message to master control borad, and Version Control makes business board version updating automatically start, and guarantees the full-automation of version updating process.Version updating is separated with device hardware type; Detect Current hardware type when business board starts, when starting version download, under FTP signs in master control borad memory device version default path, according to its type of hardware coupling respective file, make version updating process shield device hardware type.
Example 1 is based on the dynamic version update method under distributed system
For the whole network version updating, restart after master control borad A version updating completes, current version number is R001B01D07SP2:
1) all business boards of core net all initiate plate registration request to master control borad A, carry business board current version R001B01D06SP2;
2) master control borad A judges that all business board current versions number do not mate with baseline version number (R001B01D07), needs to carry out version updating, performs step 3); Otherwise execution step 8);
3) master control borad A bill plate version updating Indication message gives all business boards;
4) each business board is receiving after single board edition that master control borad A sends upgrades Indication message, starts version updating downloading process respectively: a) FTP signs under master control borad memory device mates version path corresponding to this plate type of hardware; B) the All Files detailed bill under master control borad current path is obtained; C) read updatefilelist.txt file content under master control borad current path and strictly mate with lists of documents file; D) all files that the match is successful are prepared to download;
5) each business board downloads the file that the match is successful successively, and download file is added suffix .temp temporary file form with old file name is kept under this locality deposits the default path of version;
6) after each business board has been downloaded, respectively the size byte number of download file is mated with log file byte number in updatefilelist.txt file, if the match is successful, then delete original file, temporary file is removed suffix .temp and rename; All download files mate successively, once occur that it fails to match, then stop coupling, perform step 1); If all the match is successful for all download files, perform step 7);
7) each business board restarts, and current version number is R001B01D07SP2; Perform step 1);
8) master control borad A bill plate registration reply message gives each business board, and result is successfully; The whole network version updating flow process terminates.
Example 2 is based on the dynamic version update method under distributed system
Business board B so that core net dilatation adding hardware type is Linux for server OS:
1) business board B version (R001D01B05) of delivering does not mate with existing network master control borad A version (R001D01B06SP2), when business board B is newly-increased be added to core net after, to master control borad A initiation plate registration request, carry business board current version number;
2) master control borad A judges that business board B current version number does not mate with baseline version number (R001B01D06), needs to carry out version updating, performs step 3); Otherwise execution step 8);
3) master control borad A bill plate version updating Indication message is to business board B;
4) business board B is receiving after single board edition that master control borad A sends upgrades Indication message, starts version updating downloading process: a) FTP signs in master control borad memory device to mate this plate type of hardware be under the version path of Linux; B) the All Files detailed bill under master control borad current path is obtained; C) read updatefilelist.txt file content under master control borad current path and strictly mate with lists of documents file; D) all files that the match is successful are prepared to download;
5) business board B downloads the file that the match is successful successively, and download file is added suffix .temp temporary file form with old file name is kept under this locality deposits the default path of version; ;
6) after business board B has downloaded, the size byte number of download file is mated with log file byte number in updatefilelist.txt file, if the match is successful, then delete original file, temporary file is removed suffix .temp and rename; All download files mate successively, once occur that it fails to match, then stop coupling, perform step 1); If all the match is successful for all download files, perform step 7);
7) business board B restarts, and current version number is R001B01D06SP2; Perform step 1);
8) master control borad A bill plate registration reply message is successfully to business board B, result; Version updating flow process terminates.
Example 3 is based on the dynamic version update method under distributed system
Be that the business board B that TSP plate operating system is Vxworks platform upgrades interim debug version for example with type of hardware, master control borad has upgraded temporary version (R001B01D07SP2.02):
1) because business board B need upgrade temporary version debugging, current version number (R001B01D07SP2), by master control borad A bill plate version updating Indication message to business board B;
2) business board B is receiving after single board edition that master control borad A sends upgrades Indication message, starts version updating downloading process: a) FTP signs in master control borad memory device to mate this plate type of hardware be under the version path of Vxworks; B) the All Files detailed bill under master control borad current path is obtained; C) read updatefilelist.txt file content under master control borad current path and strictly mate with lists of documents file; D) all files that the match is successful are prepared to download;
3) business board B downloads the file that the match is successful successively, and download file is added suffix .temp temporary file form with old file name is kept under this locality deposits the default path of version;
4), after business board B has downloaded, the file of local All Files name band .temp suffix is mated with updatefilelist.txt file record byte number, if the match is successful, then deletes original file, temporary file is renamed; All download files mate successively, if all the match is successful, then perform step 7); If once occur that it fails to match, then stop coupling, perform step 1);
5) business board B restarts;
6) business board B initiates plate registration request to master control borad A, carries business board current version R001B01D07SP2.02;
7) master control borad A judges that business board current version number does not need to carry out version updating, and bill plate registration reply message is successfully to business board B, result; Version updating flow process terminates.
The present invention also proposes a kind of edition management device of distributed system, and this device comprises configuration module, for configuring each device version Matching Relationship; Memory module, for storing the version file of each version of each equipment; Control module, for according to device version Matching Relationship each in configuration module, judges also whether indicating equipment carries out version updating; Transport module, during for needing when equipment to carry out version updating, provides the download of version file in described memory module.
As can be seen from above method and each specific embodiment, at least there is following beneficial effect in the method that the present invention proposes:
1, the version dynamic management under distributed system is achieved; Master control borad can control effectively to whole net device version: invalid permission of device version is come into force; Multi-version compatibility under same baseline version;
2, solve the automatic renewal of version under existing distributed kernel net system, simplify version updating flow process, improve version updating efficiency;
3, version updating multiple check and abnormal protection, improves reliability and the stability of version updating;
4, version updating is separated with type of hardware, decreases manual maintenance cost.
Above-described embodiment is only the present invention's part embodiment, instead of whole embodiments.Within the spirit and principles in the present invention all, those of ordinary skill in the art, not making any amendment done under creative work prerequisite, equivalent replacement or improvement etc., all should belong within the scope of protection of the invention.
Claims (10)
1. a version dynamic management approach for distributed system, master control borad carries out unified management and control to system-wide version, it is characterized in that, comprising:
Master control borad indicating services plate carries out version updating;
After business board receives described instruction, start version updating and download;
After business board success download version file, the version file using described success to download upgrades current version file;
After version file upgrades, business board is restarted.
2. method according to claim 1, is characterized in that, also comprises:
Business board, to master control borad transmission board login request message, carries business board current version number;
Described master control borad judges whether access according to business board current version number: if access, then return registration response success message to business board, plate register flow path terminates; Otherwise master control borad indicating services plate carries out version updating.
3. method according to claim 2, is characterized in that, described basis for estimation is whether version number meets baseline version matching principle.
4. method according to claim 3, is characterized in that, described baseline version matching principle is specially: different baseline version not access, each patch release under same baseline version and its debug version compatible.
5. method according to claim 1, is characterized in that, described version updating is downloaded and comprised: business board signs in master control borad and reads revision table file, and the content of version file with described revision table file is strictly mated; Download all strictly version files that the match is successful.
6. method according to claim 5, is characterized in that, all version file list of file names of described revision table file record version and version file length.
7. the method according to claim 1 ~ 6 any one, it is characterized in that, after described business board success download version file, the version file using described success to download upgrades current version file and specifically comprises: business board carries out length check to the version file downloaded successively according to the file size of described revision table file record, if verification succeeds, then the version file of described download is used to replace current version file.
8. method according to claim 7, is characterized in that, also comprises, once verify unsuccessfully, then stops verification, restarts version updating and downloads.
9. method according to claim 1, it is characterized in that, also comprise: when described business board starts, detect Current hardware type, when starting version updating download, under signing in master control borad memory device version default path, select corresponding version file according to its type of hardware.
10. a version dynamic management device for distributed system, is characterized in that, this device comprises configuration module, memory module and control module and transport module,
Described configuration module, for configuring each device version Matching Relationship;
Described memory module, for storing the version file of each version of each equipment;
Described control module, for according to device version Matching Relationship each in configuration module, judges also whether indicating equipment carries out version updating;
Described transport module, during for needing when equipment to carry out version updating, provides the download of version file in described memory module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310647908.7A CN104702423A (en) | 2013-12-04 | 2013-12-04 | Version dynamic-management method and device for distributed system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310647908.7A CN104702423A (en) | 2013-12-04 | 2013-12-04 | Version dynamic-management method and device for distributed system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104702423A true CN104702423A (en) | 2015-06-10 |
Family
ID=53349216
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310647908.7A Pending CN104702423A (en) | 2013-12-04 | 2013-12-04 | Version dynamic-management method and device for distributed system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104702423A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111273924A (en) * | 2020-01-10 | 2020-06-12 | 杭州迪普科技股份有限公司 | Software updating method and device |
| CN111562926A (en) * | 2020-04-03 | 2020-08-21 | 江苏能电科技有限公司 | System and method for updating circuit breaker firmware |
| CN113515304A (en) * | 2021-06-10 | 2021-10-19 | 锐捷网络股份有限公司 | Interaction method and device between board cards based on frame type network equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101179430A (en) * | 2007-12-03 | 2008-05-14 | 中兴通讯股份有限公司 | Device and method of controlling distributed system software version updating |
| CN101753524A (en) * | 2008-12-15 | 2010-06-23 | 青岛海信传媒网络技术有限公司 | Method and system for upgrading software |
| CN101853173A (en) * | 2010-05-27 | 2010-10-06 | 杭州华三通信技术有限公司 | Software upgrading method and device of programmable logic device of distributed system |
| CN101989920A (en) * | 2009-08-03 | 2011-03-23 | 华为技术有限公司 | Distributed communication equipment version upgrading method and device and system thereof |
| US20110153791A1 (en) * | 2009-12-17 | 2011-06-23 | Honeywell International Inc. | Systems and methods for managing configuration data at disconnected remote devices |
| CN102195796A (en) * | 2010-03-19 | 2011-09-21 | 杭州华三通信技术有限公司 | Method and equipment for updating software version of distributed dual master control equipment |
| CN103248669A (en) * | 2012-12-13 | 2013-08-14 | 武汉东为科技有限公司 | Distributed software upgrade system and method |
-
2013
- 2013-12-04 CN CN201310647908.7A patent/CN104702423A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101179430A (en) * | 2007-12-03 | 2008-05-14 | 中兴通讯股份有限公司 | Device and method of controlling distributed system software version updating |
| CN101753524A (en) * | 2008-12-15 | 2010-06-23 | 青岛海信传媒网络技术有限公司 | Method and system for upgrading software |
| CN101989920A (en) * | 2009-08-03 | 2011-03-23 | 华为技术有限公司 | Distributed communication equipment version upgrading method and device and system thereof |
| US20110153791A1 (en) * | 2009-12-17 | 2011-06-23 | Honeywell International Inc. | Systems and methods for managing configuration data at disconnected remote devices |
| CN102195796A (en) * | 2010-03-19 | 2011-09-21 | 杭州华三通信技术有限公司 | Method and equipment for updating software version of distributed dual master control equipment |
| CN101853173A (en) * | 2010-05-27 | 2010-10-06 | 杭州华三通信技术有限公司 | Software upgrading method and device of programmable logic device of distributed system |
| CN103248669A (en) * | 2012-12-13 | 2013-08-14 | 武汉东为科技有限公司 | Distributed software upgrade system and method |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111273924A (en) * | 2020-01-10 | 2020-06-12 | 杭州迪普科技股份有限公司 | Software updating method and device |
| CN111562926A (en) * | 2020-04-03 | 2020-08-21 | 江苏能电科技有限公司 | System and method for updating circuit breaker firmware |
| CN113515304A (en) * | 2021-06-10 | 2021-10-19 | 锐捷网络股份有限公司 | Interaction method and device between board cards based on frame type network equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7389104B2 (en) | Upgrading a database from a first version to a second version | |
| CN103902299B (en) | A kind of update method and system of software version | |
| CN107239288B (en) | Version upgrading method and device for mobile terminal | |
| CN103530150B (en) | A kind of long-range method updating of (SuSE) Linux OS | |
| CN110083374B (en) | Upgrade rollback method, system and terminal equipment | |
| KR102057527B1 (en) | System and method for automatic cloud-based full-data backup and restore on mobile devices | |
| CN102025778A (en) | Software version upgrading work method based on Shell | |
| CN102609281B (en) | Distributed software patch update method and system | |
| US10516526B2 (en) | Data transmitting method, server and client | |
| US20070061800A1 (en) | System and method for updating software in a network device | |
| CN107153560B (en) | Version upgrading method, server and system | |
| US20160378458A1 (en) | Method and device for system application installation package, and terminal | |
| CN105808274A (en) | Software upgrading method and system as well as corresponding clients and servers | |
| CN105653329A (en) | Application management method, apparatus and system | |
| TW201621647A (en) | Operating system updating method | |
| CN102193841B (en) | Backup method and device of Subversion configuration database | |
| CN104702633A (en) | Version updating method and version updating device | |
| CN104702423A (en) | Version dynamic-management method and device for distributed system | |
| CN112152846A (en) | Metering instrument remote upgrading method based on Internet of things | |
| CN114840242A (en) | System upgrading method and device of electronic equipment and readable storage medium | |
| CN107766063A (en) | A kind of method and system of batch upgrade software | |
| US20040192280A1 (en) | System for updating application software of data acquisition devices | |
| CN103984585A (en) | Method for upgrading Linux kernel in running process of kernel module capable of being plugged in thermal mode | |
| CN108121552B (en) | Automatic patching method based on XenServer | |
| CN111949311B (en) | Gray level release method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20150610 |