CN110264149A - A kind of operation system checking method and device - Google Patents
A kind of operation system checking method and device Download PDFInfo
- Publication number
- CN110264149A CN110264149A CN201910401762.5A CN201910401762A CN110264149A CN 110264149 A CN110264149 A CN 110264149A CN 201910401762 A CN201910401762 A CN 201910401762A CN 110264149 A CN110264149 A CN 110264149A
- Authority
- CN
- China
- Prior art keywords
- subtask
- task flow
- flow template
- operation system
- verification
- 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
- 238000000034 method Methods 0.000 title claims abstract description 81
- 238000012795 verification Methods 0.000 claims abstract description 137
- 230000002159 abnormal effect Effects 0.000 claims abstract description 19
- 230000008569 process Effects 0.000 claims description 42
- 238000012545 processing Methods 0.000 claims description 7
- 238000004891 communication Methods 0.000 description 10
- 238000013507 mapping Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000006872 improvement Effects 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000011084 recovery Methods 0.000 description 3
- 238000012550 audit Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 241000208340 Araliaceae Species 0.000 description 1
- 235000005035 Panax pseudoginseng ssp. pseudoginseng Nutrition 0.000 description 1
- 235000003140 Panax quinquefolius Nutrition 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 235000008434 ginseng Nutrition 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Engineering & Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Debugging And Monitoring (AREA)
Abstract
This specification provides a kind of operation system checking method and device, different verification subtasks is write in advance, original task flow template is split as the flexible template being made of different IPs to sub- task, new template directly can be formed by subtask when operation system edition upgrading and be loaded according to operation system version identifier, make verification rule with operation system smooth upgrade.Meanwhile by updating current subtask implementation progress, it can be ensured that the task flow template can be reloaded by checking after there is abnormal interrupt continues to execute subsequent subtask, guarantees the consistency that front and back is checked.
Description
Technical field
This specification is related to internet area more particularly to a kind of operation system checking method and device.
Background technique
Verification is to ensure the important means of an operation system fund security, is needed not in each stage of business processing
Same verification rule carries out business verification.Wherein, main road verification is a kind of verification side being interspersed in operation system logical links
Formula, has operation system certain invasive, needs to ensure the height correctness and stability of verification rule, avoids to operation system
It impacts.
In traditional scheme, need to carry out verification verification, but tradition to operation system according to fixed whole verification template
After operation system upgrading, verification template is not easy with operation system smooth upgrade scheme.And traditional scheme is in verification task hair
After raw abnormal interrupt, it is unable to ensure front and back verification consistency when re-executing verification, in main road audit process, this verification
Exception will affect business following link process.
Summary of the invention
In view of the above technical problems, this specification embodiment provides a kind of operation system checking method and device, technical side
Case is as follows:
According to this specification embodiment in a first aspect, provide a kind of operation system checking method, this method comprises:
The identification information for obtaining operation system to be checked, it is corresponding in advance according to the load of the identification information of the operation system
The task flow template of configuration, wherein the task flow template is one group of orderly subtask set, and the difference subtask is for full
The different IPs of sufficient operation system identify demand, the identification information including at least system version；
The identification information for recording loaded task flow template, successively executes wherein included according to the task flow template
Subtask updates the current subtask implementation progress of the task flow template, the subtask implementation progress in the process of implementation
Restore for checking the interruption after exception；
If any subtask executes failure, determine that checking task flow is abnormal, and terminates working as operation system to be checked
Pronucleus is to process.
According to the second aspect of this specification embodiment, a kind of operation system checking device is provided, which includes:
Task flow loading module: for obtaining the identification information of operation system to be checked, according to the mark of the operation system
To know information and loads corresponding preconfigured task flow template, wherein the task flow template is one group of orderly subtask set,
The difference subtask is used to meet the different IPs of operation system to demand, and the identification information includes at least system version mark
Know；
Subtask logging modle: for recording the identification information of loaded task flow template, according to the task flow mould
Plate successively executes subtask wherein included, update in the process of implementation the task flow template current subtask execute into
Degree, the subtask implementation progress are used to check the interruption recovery after exception；
Exception processing module: for when any subtask execute failure after, determine verification task flow be abnormal, end to
Check the current verification process of operation system.
According to the third aspect of this specification embodiment, a kind of computer equipment is provided, including memory, processor and deposit
Store up the computer program that can be run on a memory and on a processor, wherein the processor is realized when executing described program
A kind of operation system checking method, which comprises
The identification information for obtaining operation system to be checked, it is corresponding in advance according to the load of the identification information of the operation system
The task flow template of configuration, wherein the task flow template is one group of orderly subtask set, and the difference subtask is for full
The different IPs of sufficient operation system identify demand, the identification information including at least system version；
The identification information for recording loaded task flow template, successively executes wherein included according to the task flow template
Subtask updates the current subtask implementation progress of the task flow template, the subtask implementation progress in the process of implementation
Restore for checking the interruption after exception；
If any subtask executes failure, determine that checking task flow is abnormal, and terminates working as operation system to be checked
Pronucleus is to process.
Technical solution provided by this specification embodiment writes different verification subtasks in advance, by original task
Flow template is split as the flexible template being made of different IPs to sub- task, and when operation system edition upgrading can be directly by subtask group
The template of Cheng Xin is simultaneously loaded according to operation system version identifier, makes verification rule with operation system smooth upgrade.Meanwhile
By updating current subtask implementation progress, it can be ensured that verification can reload the task flow template after there is abnormal interrupt
Subsequent subtask is continued to execute, guarantees the consistency that front and back is checked.
It should be understood that above general description and following detailed description be only it is exemplary and explanatory, not
This specification embodiment can be limited.
In addition, any embodiment in this specification embodiment does not need to reach above-mentioned whole effects.
Detailed description of the invention
In order to illustrate more clearly of this specification embodiment or technical solution in the prior art, below will to embodiment or
Attached drawing needed to be used in the description of the prior art is briefly described, it should be apparent that, the accompanying drawings in the following description is only
The some embodiments recorded in this specification embodiment for those of ordinary skill in the art can also be attached according to these
Figure obtains other attached drawings.
Fig. 1 is a kind of flow chart of the operation system checking method shown in one exemplary embodiment of this specification；
Fig. 2 is another flow chart of the operation system checking method shown in one exemplary embodiment of this specification；
Fig. 3 is a kind of stream of the operation system verification abnormal interrupt restoration methods shown in one exemplary embodiment of this specification
Cheng Tu；
Fig. 4 is a kind of flow chart of the task flow template configuration method shown in one exemplary embodiment of this specification；
Fig. 5 is that one kind of the operation system checking device of the task based access control stream shown in one exemplary embodiment of this specification is shown
It is intended to；
Fig. 6 is a kind of structural schematic diagram of computer equipment shown in one exemplary embodiment of this specification.
Specific embodiment
Example embodiments are described in detail here, and the example is illustrated in the accompanying drawings.Following description is related to
When attached drawing, unless otherwise indicated, the same numbers in different drawings indicate the same or similar elements.Following exemplary embodiment
Described in embodiment do not represent all embodiments consistent with this specification.On the contrary, they are only and such as institute
The example of the consistent device and method of some aspects be described in detail in attached claims, this specification.
It is only to be not intended to be limiting this explanation merely for for the purpose of describing particular embodiments in the term that this specification uses
Book.The "an" of used singular, " described " and "the" are also intended to packet in this specification and in the appended claims
Most forms are included, unless the context clearly indicates other meaning.It is also understood that term "and/or" used herein is
Refer to and includes that one or more associated any or all of project listed may combine.
It will be appreciated that though various information may be described using term first, second, third, etc. in this specification, but
These information should not necessarily be limited by these terms.These terms are only used to for same type of information being distinguished from each other out.For example, not taking off
In the case where this specification range, the first information can also be referred to as the second information, and similarly, the second information can also be claimed
For the first information.Depending on context, word as used in this " if " can be construed to " ... when " or
" when ... " or " in response to determination ".
This specification embodiment provide a kind of operation system checking method and it is a kind of for execute this method based on appointing
The operation system checking device of business stream.The operation system checking method that the present embodiment is related to is described in detail below, referring to
Shown in Fig. 1, this method be may comprise steps of:
S101 obtains the identification information of operation system to be checked, and is loaded and is corresponded to according to the identification information of the operation system
Preconfigured task flow template；
In traditional scheme, when operation system has new version, it may deposit same on production environment difference host on line
The new early version different situations of one operation system, when being checked, if for operation system a whole set of verification rule not with
The upgrading of operation system and upgrade, have that be likely to occur verification abnormal, report by mistake or fail to report.
In order to enable to check rule with operation system smooth upgrade, on the one hand, the present embodiment sets task flow template
For one group of orderly subtask set, the difference subtask is used to meet the different IPs of operation system to demand, wherein orderly son
Set of tasks is the subtask set after arranging subtask according to predetermined order, when carrying out the verification of corresponding operation system,
The subtask that will successively be executed according to the predetermined order in task flow template.
Subtask is set as minimum verification unit by the present embodiment, can be quickly anti-after new version occurs in operation system
Answer, by combine subtask form new task flow template, compared with it is original for each default pinned task flow template more
Add convenient and efficient.
On the other hand, before verification, the identification information of operation system to be checked is obtained, identification information includes at least system
Version identifier loads corresponding preconfigured task flow template according to the identification information of the operation system.
S102 records the identification information of loaded task flow template, is successively executed wherein according to the task flow template
The subtask for including updates the current subtask implementation progress of the task flow template in the process of implementation, and the subtask is held
Traveling degree is used to check the interruption recovery after exception；
Specifically, can configure a kind of record file, as the execution of verification task updates verification stream in record file
The current implementation progress of journey, the implementation progress can be considered the implementation progress of orderly subtask set in the present embodiment.
S103 determines that checking task flow is abnormal, and terminates operation system to be checked if any subtask executes failure
Current verification process.
Specifically, during according to traffic flow template sequence subtasking, probably due to a variety of causes causes
Task abnormity, such as task flow template and operation system mismatch；After some subtask in task flow template executes exception,
Determine that verification task flow is abnormal and terminates the current verification process of operation system to be checked.
This specification embodiment also provides a kind of more specific operation system checking method, and shown in Figure 2, this method can
With the following steps are included:
S201 obtains the identification information of operation system to be checked, and is loaded and is corresponded to according to the identification information of the operation system
Preconfigured task flow template；
Wherein, the task flow template is one group of orderly subtask set, and the difference subtask is for meeting business system
The different IPs of system identify demand, the identification information including at least system version；
When operation system has new version, need gradually to cover new version each host of production environment on line
On, and during this covering, the same new early version of operation system on production environment difference host on line may be deposited
Different situations have prepared different verification rules in traditional scheme just for different business systems, and there is no be directed to operation system
This application scenarios prepares corresponding treatment measures in edition upgrading progress, when being checked, if for operation system
The whole series verification rule does not upgrade with the upgrading of operation system, has and is likely to occur verification exception, reports by mistake or fail to report.
The present embodiment makes improvement to this, first obtains the identification information of operation system to be checked, in the identification information at least
It is identified including system version, it is generally the case that the identification information can be specifically set as system name and version number.
It is appreciated that in the present embodiment, needing to be pre-configured with comprising operation system identification information and corresponding task flow
The one-to-one relationship of template specifically can be pre-configured with mapping library, by every group of system name and version number, this group of system name
Task flow template ID corresponding with version number pre-establishes mapping relations.
For example: (system name and version number can be considered for the system name for obtaining operation system to be checked and version number
The identification information of operation system), it is inquired in preconfigured mapping library according to system name and version number, is recorded in the mapping library
The system name of operation system and the one-to-one relationship of version number and preconfigured task flow template ID, the mapping relations
The form of expression specifically refer to the following table 1.
| System A (version 1.1) | System A (version 1.2) | System A (version 1.3) | … | |
| Task flow template ID | a110 | a120 | a130 | … |
| System B (version 2 .2) | System B (version 2 .3) | System B (version 2 .4) | ||
| Task flow template ID | b220 | b230 | b240 |
Table 1
S202 records the identification information of loaded task flow template；
S203 successively starts to execute subtask wherein included according to the task flow template；
S204 after execution starts in any verification subtask, records institute in current subtask implementation progress record file
State subtask mark and corresponding beginning execution information；
Specifically, can configure a kind of record file, as the execution of verification task updates verification stream in record file
The current implementation progress of journey, the implementation progress can be considered the implementation progress of orderly subtask set in the present embodiment.
Citing is illustrated the recording process:
It include a string of orderly subtasks in task flow template, subtask ID is respectively 1000-1006, loading tasks flow template
Afterwards, subtask 1000 is first begun to, while recording corresponding subtask implementation progress, the tool of the record in record file
Body form is permissible are as follows: " subtask ID:1000, current to execute movement: to start to execute "；
Further, after subtask 1000 runs succeeded, corresponding subtask can be recorded in record file again and held
Traveling degree, the concrete form of the record can be with are as follows: " subtask ID:1000, current to execute movement: to run succeeded "；
After subtask 1000 runs succeeded, next height is continued to execute according to the subtask execution sequence in task flow template
Task 1001, while recording corresponding subtask implementation progress in record file, the concrete form of the record can be with are as follows: " son
Task ID: 1001, current to execute movement: to start to execute " ... and so on, with the continuation of verification process, constantly updates son and appoint
The executive condition of business, with the current verification implementation progress of determination.
It is worth noting that: the subtask records the record content of file and recording mode can be according to concrete application scene
Sets itself, as long as meeting record current the needs of checking progress；Such as, it in the implementation procedure of a subtask, can incite somebody to action
Start to execute, executive process, the movements such as run succeeded all are recorded, and it is (as every in only recorded can also only to record one of movement
A subtask starts to execute)；Further, more custom contents can also be added in record, such as corresponding movement is touched
The time is sent out, concrete form can be with are as follows: " subtask ID:1001, it is current to execute movement: to start to execute, current time: 10:21 ".
Further, can run succeeded in whole subtasks, for operation system whole verification process after, will be right
The subtask implementation progress record file answered is deleted.
Does S205 judge that currently performed subtask runs succeeded? if current subtask runs succeeded, step is executed
S206 terminates process if current subtask executes failure；
Does S206, judge whether the subtask in the task flow template is all finished? if subtask is without all
It is finished, goes successively to next subtask, and re-execute the steps S203, if subtask is all finished, terminate
Process；
During being executed to task flow template, the case where interruption if there is the verification task abnormity being carrying out, then
The consistency that front and back is checked be must assure that ensure that service link will not be impacted.It in this case, can be according to above
In record information reload original task flow template and continue to execute, to ensure verification consistency.
It is appreciated that can first the appearance reason to the abnormal interrupt be carried out before reloading task flow template and executing
Detection, and reload task flow template because after correcting the exception root and execute verification.
It is shown in Figure 3, method is re-executed after interrupting for verification task abnormity, specifically includes the following steps:
S301 reloads the task flow template according to pre-recorded task flow template identification；
The step includes institute above in the task flow template primarily to reload the task flow template executed originally
It states, the last time executes the subtask implementation progress recorded when verification, and the present embodiment can be completed according to the subtask implementation progress
The abnormal interrupt of verification task restores, i.e., this restores that the verification implementation progress for connecting the last time is continued to execute core after checking
It is right.
S302 determines subsequent pending subtask according to pre-recorded current subtask implementation progress；
S303 continues to execute subsequent pending subtask, updates the current son of the task flow template in the process of implementation
Task execution progress.
Does S304 judge that currently performed subtask runs succeeded? if current subtask runs succeeded, step is executed
S305 terminates process if current subtask executes failure；
Does S305, judge whether the subtask in the task flow template is all finished? if subtask is without all
It is finished, goes successively to next subtask, and re-execute the steps S303, if subtask is all finished, terminate
Process；
Verification is to ensure the important means of an operation system fund security, is needed not in each stage of business processing
Same verification rule carries out business verification.Wherein, main road verification is a kind of verification side being interspersed in operation system logical links
Formula, has operation system certain invasive, needs to ensure the height correctness and stability of verification rule, avoids to operation system
It impacts.
In traditional scheme, need to carry out verification verification, but tradition to operation system according to fixed whole verification template
After operation system upgrading, verification template is not easy with operation system smooth upgrade scheme.And traditional scheme is in verification task hair
After raw abnormal interrupt, it is unable to ensure front and back verification consistency when re-executing verification, in main road audit process, this verification
Exception will affect business following link process.
As can be seen that the present embodiment is split as multiple subtasks by that will check task, and in verification process constantly more
The implementation progress of new record subtask can pass through pre-recorded task flow template identification after abnormal interrupt occurs in verification
Predecessor's business flow template is reloaded, directly starts to execute subsequent subtask by the subtask implementation progress of record, it is ensured that again
It executes front and back when verification and checks consistency.
Task flow template mentioned above is pre-configured with, and illustrates the configuration mode of task flow template below, ginseng
Examine Fig. 4, comprising the following steps:
S401 obtains the basis verification rule write in advance；
S402 determines the corresponding operation system of task flow template to be configured, according to the business scenario of the operation system,
Corresponding business verification rule is obtained in the business verification rule base write in advance；
The basis verification rule and business verification rule are combined configuration, to generate and the industry by S403
The corresponding task flow template of the identification information of business system.
Specifically, the verification demand of the operation system can be analyzed, determines that composition is described according to the verification demand and appoint
The orderly subtask set of business flow template；
By in the set of orderly subtask, the basis verification rule or business of corresponding different subtasks check regular configuration
Into task flow template, to generate task flow template corresponding with the identification information of the operation system.
Before configuration task flow template, it is necessary first to write corresponding verification rule, check rule to meet business system
The verification for different aspect verification demand of uniting executes step.It specifically, can be by verification rule by basis verification rule and service interfacing
Verification rule distinguishes, and verification rule in basis meets the general purpose core of most operation system verification demands to rule, industry
Business docking verification rule meets the non-universal verification rule of operation system a certain kind business verification demand.
Wherein, verification rule is distinguished by basis verification rule and service interfacing verification rule, is for the ease of rear
When continued access enters new business, without the rule code of overlapping development basis verification rule, this part rule of overlapping development is avoided to make
At the wasting of resources.
Citing is illustrated basis verification rule and service interfacing verification rule:
Basis verification rule A is write, business checks rule B and business checks rule C, in configuration task flow template, base
Plinth verification rule A can be applied to most task flow templates, and business verification rule B can be applied to task flow template a, task flow
Wherein, there is the correspondence system of task flow template a, task flow template b template b ... business to check the business that rule B can be checked；Industry
Business verification rule C can be applied to task flow template d, task flow template g ... wherein, task flow template d, task flow template g's
The business that there is correspondence system business verification rule C can check.
After writing the regular verification rule with service interfacing of a lot of basis verification, different rules is formed into task one by one
Flow template.Each verification task flow template establishes corresponding relationship with corresponding operation system name and version number, is to guarantee verification rule
The then key of smooth upgrade and verification consistency.
Corresponding to above method embodiment, this specification embodiment also provides a kind of operation system verification of task based access control stream
Device, it is shown in Figure 5, the apparatus may include: task flow loading module 510, subtask logging modle 520 and exception
Manage module 530；
Task flow loading module 510: for obtaining the identification information of operation system to be checked, according to the operation system
Identification information loads corresponding preconfigured task flow template, wherein the task flow template is one group of orderly subtask collection
It closes, the difference subtask is used to meet the different IPs of operation system to demand, and the identification information includes at least system version
Mark；
Subtask logging modle 520: for recording the identification information of loaded task flow template, according to the task flow
Template successively executes subtask wherein included, update in the process of implementation the task flow template current subtask execute into
Degree, the subtask implementation progress are used to check the interruption recovery after exception；
Exception processing module 530: for determining that verification task flow is abnormal, tying after any subtask executes and fails
The current verification process of beam operation system to be checked.
This specification embodiment also provides a kind of computer equipment, includes at least memory, processor and is stored in
On reservoir and the computer program that can run on a processor, wherein processor realizes aforementioned business system when executing described program
System checking method, the method include at least:
The identification information for obtaining operation system to be checked, it is corresponding in advance according to the load of the identification information of the operation system
The task flow template of configuration, wherein the task flow template is one group of orderly subtask set, and the difference subtask is for full
The different IPs of sufficient operation system identify demand, the identification information including at least system version；
The identification information for recording loaded task flow template, successively executes wherein included according to the task flow template
Subtask updates the current subtask implementation progress of the task flow template, the subtask implementation progress in the process of implementation
Restore for checking the interruption after exception；
If any subtask executes failure, determine that checking task flow is abnormal, and terminates working as operation system to be checked
Pronucleus is to process.
Fig. 6 shows one kind provided by this specification embodiment and more specifically calculates device hardware structural schematic diagram,
The equipment may include: processor 1010, memory 1020, input/output interface 1030, communication interface 1040 and bus
1050.Wherein processor 1010, memory 1020, input/output interface 1030 and communication interface 1040 are real by bus 1050
The now communication connection inside equipment each other.
Processor 1010 can use general CPU (Central Processing Unit, central processing unit), micro- place
Reason device, application specific integrated circuit (Application Specific Integrated Circuit, ASIC) or one
Or the modes such as multiple integrated circuits are realized, for executing relative program, to realize technical side provided by this specification embodiment
Case.
Memory 1020 can use ROM (Read Only Memory, read-only memory), RAM (Random Access
Memory, random access memory), static storage device, the forms such as dynamic memory realize.Memory 1020 can store
Operation service system and other applications are realizing technology provided by this specification embodiment by software or firmware
When scheme, relevant program code is stored in memory 1020, and execution is called by processor 1010.
Input/output interface 1030 is for connecting input/output module, to realize information input and output.Input and output/
Module can be used as component Configuration (not shown) in a device, can also be external in equipment to provide corresponding function.Wherein
Input equipment may include keyboard, mouse, touch screen, microphone, various kinds of sensors etc., output equipment may include display,
Loudspeaker, vibrator, indicator light etc..
Communication interface 1040 is used for connection communication module (not shown), to realize the communication of this equipment and other equipment
Interaction.Wherein communication module can be realized by wired mode (such as USB, cable etc.) and be communicated, can also be wirelessly
(such as mobile network, WIFI, bluetooth etc.) realizes communication.
Bus 1050 include an access, equipment various components (such as processor 1010, memory 1020, input/it is defeated
Outgoing interface 1030 and communication interface 1040) between transmit information.
It should be noted that although above equipment illustrates only processor 1010, memory 1020, input/output interface
1030, communication interface 1040 and bus 1050, but in the specific implementation process, which can also include realizing normal fortune
Other assemblies necessary to row.In addition, it will be appreciated by those skilled in the art that, it can also be only comprising real in above equipment
Component necessary to existing this specification example scheme, without including all components shown in figure.
This specification embodiment also provides a kind of computer readable storage medium, is stored thereon with computer program, the journey
Operation system checking method above-mentioned is realized when sequence is executed by processor, the method includes at least:
The identification information for obtaining operation system to be checked, it is corresponding in advance according to the load of the identification information of the operation system
The task flow template of configuration, wherein the task flow template is one group of orderly subtask set, and the difference subtask is for full
The different IPs of sufficient operation system identify demand, the identification information including at least system version；
The identification information for recording loaded task flow template, successively executes wherein included according to the task flow template
Subtask updates the current subtask implementation progress of the task flow template, the subtask implementation progress in the process of implementation
Restore for checking the interruption after exception；
If any subtask executes failure, determine that checking task flow is abnormal, and terminates working as operation system to be checked
Pronucleus is to process.
Computer-readable medium includes permanent and non-permanent, removable and non-removable media can be by any method
Or technology come realize information store.Information can be computer readable instructions, data structure, the module of program or other data.
The example of the storage medium of computer includes, but are not limited to phase change memory (PRAM), static random access memory (SRAM), moves
State random access memory (DRAM), other kinds of random access memory (RAM), read-only memory (ROM), electric erasable
Programmable read only memory (EEPROM), flash memory or other memory techniques, read-only disc read only memory (CD-ROM) (CD-ROM),
Digital versatile disc (DVD) or other optical storage, magnetic cassettes, tape magnetic disk storage or other magnetic storage devices
Or any other non-transmission medium, can be used for storage can be accessed by a computing device information.As defined in this article, it calculates
Machine readable medium does not include temporary computer readable media (transitorymedia), such as the data-signal and carrier wave of modulation.
For device embodiment, since it corresponds essentially to embodiment of the method, so related place is referring to method reality
Apply the part explanation of example.The apparatus embodiments described above are merely exemplary, wherein described be used as separation unit
The unit of explanation may or may not be physically separated, and component shown as a unit can be or can also be with
It is not physical unit, it can it is in one place, or may be distributed over multiple network units.It can be according to actual
The purpose for needing to select some or all of the modules therein to realize this specification scheme.Those of ordinary skill in the art are not
In the case where making the creative labor, it can understand and implement.
As seen through the above description of the embodiments, those skilled in the art can be understood that this specification
Embodiment can be realized by means of software and necessary general hardware platform.Based on this understanding, this specification is implemented
Substantially the part that contributes to existing technology can be embodied in the form of software products the technical solution of example in other words,
The computer software product can store in storage medium, such as ROM/RAM, magnetic disk, CD, including some instructions are to make
It is each to obtain computer equipment (can be personal computer, server or the network equipment etc.) execution this specification embodiment
Method described in certain parts of a embodiment or embodiment.
Operation system, device, module or the unit that above-described embodiment illustrates, specifically can be real by computer chip or entity
It is existing, or realized by the product with certain function.It is a kind of typically to realize that equipment is computer, the concrete form of computer
It can be personal computer, laptop computer, cellular phone, camera phone, smart phone, personal digital assistant, media to broadcast
It puts in device, navigation equipment, E-mail receiver/send equipment, game console, tablet computer, wearable device or these equipment
Any several equipment combination.
The above is only the specific embodiment of this specification embodiment, it is noted that for the general of the art
For logical technical staff, under the premise of not departing from this specification embodiment principle, several improvements and modifications can also be made, this
A little improvements and modifications also should be regarded as the protection scope of this specification embodiment.
Claims (13)
1. a kind of operation system checking method, which comprises
The identification information for obtaining operation system to be checked is pre-configured with according to the load of the identification information of the operation system is corresponding
Task flow template, wherein the task flow template is one group of orderly subtask set, and the difference subtasks are for meeting industry
The different IPs of business system identify demand, the identification information including at least system version；
The identification information for recording loaded task flow template successively executes son wherein included according to the task flow template and appoints
Business, updates the current subtask implementation progress of the task flow template, the subtask implementation progress is used in the process of implementation
Interruption after checking exception restores；
If any subtask executes failure, determine that checking task flow is abnormal, terminate operation system to be checked works as pronucleus
To process.
2. the method as described in claim 1, the current subtask for updating the task flow template in the process of implementation is held
After traveling degree, further includes:
If any verification subtask runs succeeded, next verification subtask is continued to execute, until all verification subtasks execute
It finishes.
3. the method as described in claim 1, the current subtask for updating the task flow template in the process of implementation is held
Traveling degree, comprising:
After execution starts in any verification subtask, the subtask is recorded in current subtask implementation progress record file and is marked
Know and corresponding beginning execution information.
4. the method as described in claim 1, described to terminate after the current verification process for checking operation system, further includes:
The task flow template is reloaded according to pre-recorded task flow template identification；
Subsequent pending subtask is determined according to pre-recorded current subtask implementation progress；
Continue to execute subsequent pending subtask, update in the process of implementation the task flow template current subtask execute into
Degree.
5. the method as described in claim 1, the configuration mode of the task flow template, comprising:
Obtain the basis verification rule write in advance；
Determine that the corresponding operation system of task flow template to be configured is write according to the business scenario of the operation system in advance
Business verification rule base in obtain corresponding business verification rule；
The basis verification rule and business verification rule are combined configuration, to generate the mark with the operation system
Know the corresponding task flow template of information.
6. method as claimed in claim 5, described to be combined the basis verification rule and business verification rule
Configuration, to generate task flow template corresponding with the identification information of the operation system, comprising:
The verification demand for analyzing the operation system determines the orderly son for forming the task flow template according to the verification demand
Set of tasks；
By in the set of orderly subtask, the basis verification rule of corresponding different subtasks or the regular configuration of business verification are taken office
It is engaged in flow template, to generate task flow template corresponding with the identification information of the operation system.
7. a kind of operation system checking device, described device include:
Task flow loading module: for obtaining the identification information of operation system to be checked, believed according to the mark of the operation system
Breath loads corresponding preconfigured task flow template, wherein the task flow template is one group of orderly subtask set, described
Different subtasks are used to meet the different IPs of operation system to demand, and the identification information is identified including at least system version；
Subtask logging modle: for recording the identification information of loaded task flow template, according to the task flow template according to
It is secondary to execute subtask wherein included, the current subtask implementation progress of the task flow template, institute are updated in the process of implementation
Interruption of the subtask implementation progress for after checking exception is stated to restore；
Exception processing module: for determining that verification task flow is abnormal, terminating wait check after any subtask executes and fails
The current verification process of operation system.
8. device as claimed in claim 7, the current subtask for updating the task flow template in the process of implementation is held
After traveling degree, further includes:
If any verification subtask runs succeeded, next verification subtask is continued to execute, until all verification subtasks execute
It finishes.
9. device as claimed in claim 7, the current subtask for updating the task flow template in the process of implementation is held
Traveling degree, comprising:
After execution starts in any verification subtask, the subtask is recorded in current subtask implementation progress record file and is marked
Know and corresponding beginning execution information.
10. device as claimed in claim 7, described to terminate after the current verification process for checking operation system, further includes:
The task flow template is reloaded according to pre-recorded task flow template identification；
Subsequent pending subtask is determined according to pre-recorded current subtask implementation progress；
Continue to execute subsequent pending subtask, update in the process of implementation the task flow template current subtask execute into
Degree.
11. device as claimed in claim 7, the configuration mode of the task flow template, comprising:
Obtain the basis verification rule write in advance；
Determine that the corresponding operation system of task flow template to be configured is write according to the business scenario of the operation system in advance
Business verification rule base in obtain corresponding business verification rule；
The basis verification rule and business verification rule are combined configuration, to generate the mark with the operation system
Know the corresponding task flow template of information.
12. device as claimed in claim 11, described that the basis verification rule and business verification rule are carried out group
Configuration is closed, to generate task flow template corresponding with the identification information of the operation system, comprising:
The verification demand for analyzing the operation system determines the orderly son for forming the task flow template according to the verification demand
Set of tasks；
By in the set of orderly subtask, the basis verification rule of corresponding different subtasks or the regular configuration of business verification are taken office
It is engaged in flow template, to generate task flow template corresponding with the identification information of the operation system.
13. a kind of computer equipment including memory, processor and stores the meter that can be run on a memory and on a processor
Calculation machine program, wherein the processor realizes the method as described in claim 1 when executing described program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910401762.5A CN110264149A (en) | 2019-05-15 | 2019-05-15 | A kind of operation system checking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910401762.5A CN110264149A (en) | 2019-05-15 | 2019-05-15 | A kind of operation system checking method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110264149A true CN110264149A (en) | 2019-09-20 |
Family
ID=67913132
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910401762.5A Pending CN110264149A (en) | 2019-05-15 | 2019-05-15 | A kind of operation system checking method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110264149A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113835848A (en) * | 2020-06-24 | 2021-12-24 | 上海寒武纪信息科技有限公司 | Task processing method and device, computer equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106569786A (en) * | 2015-10-10 | 2017-04-19 | 阿里巴巴集团控股有限公司 | Development method of service application and system |
| CN107506181A (en) * | 2017-07-17 | 2017-12-22 | 阿里巴巴集团控股有限公司 | Business processing, data processing method, device and electronic equipment |
| CN107864193A (en) * | 2017-10-26 | 2018-03-30 | 阿里巴巴集团控股有限公司 | Method for processing business, device, system and service equipment |
| CN108628947A (en) * | 2018-04-02 | 2018-10-09 | 阿里巴巴集团控股有限公司 | A kind of business rule matched processing method, device and processing equipment |
| CN108694564A (en) * | 2018-06-07 | 2018-10-23 | 阿里巴巴集团控股有限公司 | A kind of task status control method and device |
| CN109558237A (en) * | 2017-09-27 | 2019-04-02 | 北京国双科技有限公司 | A kind of task status management method and device |
-
2019
- 2019-05-15 CN CN201910401762.5A patent/CN110264149A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106569786A (en) * | 2015-10-10 | 2017-04-19 | 阿里巴巴集团控股有限公司 | Development method of service application and system |
| CN107506181A (en) * | 2017-07-17 | 2017-12-22 | 阿里巴巴集团控股有限公司 | Business processing, data processing method, device and electronic equipment |
| CN109558237A (en) * | 2017-09-27 | 2019-04-02 | 北京国双科技有限公司 | A kind of task status management method and device |
| CN107864193A (en) * | 2017-10-26 | 2018-03-30 | 阿里巴巴集团控股有限公司 | Method for processing business, device, system and service equipment |
| CN108628947A (en) * | 2018-04-02 | 2018-10-09 | 阿里巴巴集团控股有限公司 | A kind of business rule matched processing method, device and processing equipment |
| CN108694564A (en) * | 2018-06-07 | 2018-10-23 | 阿里巴巴集团控股有限公司 | A kind of task status control method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113835848A (en) * | 2020-06-24 | 2021-12-24 | 上海寒武纪信息科技有限公司 | Task processing method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110442652B (en) | Cross-chain data processing method and device based on block chain | |
| EP3387528B1 (en) | Updating dependent services | |
| US8719787B2 (en) | System and method for server migration synchronization | |
| JP6788178B2 (en) | Setting support program, setting support method and setting support device | |
| CN110674047B (en) | Software testing method and device and electronic equipment | |
| CN110347590A (en) | The interface testing control method and device of operation system | |
| US9256850B2 (en) | Orphan token management during in-flight process system migration | |
| CN107368426B (en) | Test method and test device | |
| US9380001B2 (en) | Deploying and modifying a service-oriented architecture deployment environment model | |
| US11243742B2 (en) | Data merge processing based on differences between source and merged data | |
| CN111723102A (en) | Intelligent contract updating method and device | |
| CN112559373B (en) | Software compatibility management method and system | |
| CN110264149A (en) | A kind of operation system checking method and device | |
| US8819494B2 (en) | Automatically changing parts in response to tests | |
| US20160267172A1 (en) | Constraint free model | |
| CN109766125A (en) | Recognition methods and the device of conflict are produced the equalizer between batch | |
| CN109961230A (en) | A kind of configuration method of index, device, storage medium and electronic equipment | |
| CN112882921B (en) | Fault simulation method and device | |
| US9483241B2 (en) | Method ranking based on code invocation | |
| CN113626220A (en) | Micro-service control method and system | |
| CN111782271A (en) | Software and hardware interaction method and device and storage medium | |
| US12143498B2 (en) | Trust and traceability for software development life cycle | |
| US12056353B2 (en) | Dynamically assigning storage objects to compartment constructs of a storage system to reduce application risk | |
| US20080104389A1 (en) | Computer system model generation with tracking of actual computer system configuration | |
| CN109002287B (en) | Management method and device for software in cloud data system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190920 |
|
| RJ01 | Rejection of invention patent application after publication |