CN107528709A - A kind of configuration status backing method and device - Google Patents
A kind of configuration status backing method and device Download PDFInfo
- Publication number
- CN107528709A CN107528709A CN201610457995.3A CN201610457995A CN107528709A CN 107528709 A CN107528709 A CN 107528709A CN 201610457995 A CN201610457995 A CN 201610457995A CN 107528709 A CN107528709 A CN 107528709A
- Authority
- CN
- China
- Prior art keywords
- subtask
- task
- configuration
- state
- reverse
- 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.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
- H04L41/0863—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions by rolling back to previous configuration versions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the present invention provides a kind of configuration status backing method and device, by obtaining task and corresponding inverse task；Task is used to configure the more network equipments, and inverse task is used to be retracted according to the network equipment of task configuration successful, it is return back to state before configuration；If task does not run succeeded completely, inverse task is performed, the state for making all-network equipment corresponding to task return back to before configuration；When being configured according to task to the more network equipments, it is likely to occur partial network devices configuration successful, the situation of partial network devices configuration failure, the network equipment that inverse task is used to will be configured to work(is retracted, it is set to return back to state before configuration, thereby guarantee that all-network equipment is in configuring preceding state, it ensure that the atomicity and uniformity to more network equipments configurations, and inverse task performs automatically, the network equipment is operated one by one without operation maintenance personnel, O＆M efficiency is improved, ensure that maintenance work is simplified.
Description
Technical field
The present invention relates to the communications field, more particularly to a kind of configuration status backing method and device.
Background technology
With the development of the communication technology, the equipment in network is more and more, due to the complexity of network structure, causes to net
The managing special of network equipment is difficult, realizes that the deployment of business is also especially difficult.In order to realize the centralized Control to the network equipment,
Realized simultaneously under the more network equipments using SDN (Software Defined Network, software defined network) controller
It is transported to when putting, in order to ensure the atomicity and uniformity that are configured to the more network equipments, if some network equipments configuration is lost
Lose, then all network equipments should all return to original state, and return to will be configured to the network equipment of work(and match somebody with somebody
State is, it is necessary to which operation maintenance personnel carries out recovery configuring one by one before putting, and labor intensive, time, O＆M efficiency is very low.
The content of the invention
The embodiment of the present invention mainly solving the technical problems that, there is provided a kind of configuration status backing method and device, solve
In the prior art, when realizing while the more network equipments being configured, if some network equipments configuration fails, by O＆M people
The network equipment that member will be configured to work(one by one returns to state before configuration, labor intensive, time, the problem of O＆M efficiency is low.
In order to solve the above technical problems, the embodiment of the present invention provides a kind of configuration status backing method, including：
Acquisition task and corresponding inverse task；Task is used to configure the more network equipments, and inverse task is used for
It will be retracted according to the network equipment of task configuration successful, it is return back to state before configuration；
If task does not run succeeded completely, inverse task is performed, all-network equipment corresponding to task is return back to and matches somebody with somebody
State before putting.
In order to solve the above technical problems, the embodiment of the present invention provides a kind of configuration status rollback device, including：
Acquisition module, for obtaining task and corresponding inverse task；Task is used to configure the more network equipments,
Inverse task is used to be retracted according to the network equipment of task configuration successful, it is return back to state before configuration；
Processing module, if not run succeeded completely for task, inverse task is performed, makes all-network corresponding to task
The state that equipment is return back to before configuration.
In order to solve the above technical problems, the embodiment of the present invention also provides a kind of computer-readable storage medium, computer storage is situated between
Computer executable instructions are stored with matter, the configuration status that computer executable instructions are used to perform foregoing any one retracts
Method.
The beneficial effects of the invention are as follows：
The configuration status backing method and device provided according to embodiments of the present invention, by obtain task and it is corresponding reversely
Task；Task is used to configure the more network equipments, and inverse task is used for the network equipment according to task configuration successful
Retracted, it is return back to state before configuration；If task does not run succeeded completely, inverse task is performed, makes task corresponding
All-network equipment return back to configuration before state；Using such scheme, the more network equipments are being matched somebody with somebody according to task
When putting, in fact it could happen that partial network devices configuration successful, the situation of partial network devices configuration failure, inverse task are used to match somebody with somebody
Put the successful network equipment to be retracted, it is return back to state before configuration, thereby guarantee that all network equipments are in matching somebody with somebody
State before putting, atomicity and uniformity to more network equipments configurations are ensure that, and inverse task performs automatically,
The network equipment is operated one by one without operation maintenance personnel, improves O＆M efficiency, ensure that maintenance work is simplified, is improved
The efficiency of service deployment and flexibility.
Brief description of the drawings
Fig. 1 is a kind of flow chart for configuration status backing method that the embodiment of the present invention one provides；
Fig. 2 is the structural representation of the storage architecture for the transaction (affairs) that the embodiment of the present invention one provides；
The schematic diagram changed between each state of task that Fig. 3 provides for the embodiment of the present invention one；
Fig. 4 is a kind of flow chart for configuration status backing method that the embodiment of the present invention one provides；
Fig. 5 is a kind of schematic network structure that the embodiment of the present invention one provides；
Fig. 6 is a kind of structural representation for configuration status rollback device that the embodiment of the present invention two provides.
Embodiment
The embodiment of the present invention is described in further detail below by embodiment combination accompanying drawing.
Embodiment one
In order to ensure the atomicity and uniformity that are configured to the more network equipments, and in order to improve O＆M efficiency,
Efficiency and the flexibility of service deployment are improved, the present embodiment provides a kind of configuration status backing method, refers to Fig. 1, including with
Lower step：
S101：Acquisition task and corresponding inverse task, task are used to configure the more network equipments, inverse task
For will be retracted according to the network equipment of task configuration successful, it is set to return back to state before configuration.
In order to realize the centralized Control to the network equipment, realized using SDN controllers and issued simultaneously to the more network equipments
Configuration, SDN controllers obtain task and corresponding inverse task；Task is used to configure the more network equipments.SDN is controlled
Device creates inverse task corresponding with the task after being issued by dispatch layer for task is got, and inverse task is used for basis
The network equipment of task configuration successful is retracted so that the more network equipments of configuration are all in the state before configuration, in root
When being configured according to task to the more network equipments, in fact it could happen that partial network devices configuration successful, partial network devices configuration
The situation of failure, the network equipment that inverse task is used to will be configured to work(are retracted, and it is return back to state before configuration.
S102：If task does not run succeeded completely, inverse task is performed, all-network equipment corresponding to task is retracted
State before to configuration.
In the case where task does not run succeeded completely, then inverse task is performed, make all-network equipment corresponding to task
The state returning back to before configuration, ensure that the atomicity and uniformity configured to the more network equipments, and improve O＆M
It efficiency, ensure that maintenance work is simplified, improve efficiency and the flexibility of service deployment.
Wherein, task includes multiple subtasks, a corresponding reverse subtask, each subtask；One subtask is used to match somebody with somebody
A network equipment is put, a reverse subtask is used to be retracted a network equipment according to subtask configuration successful,
It is set to return back to state before configuration, such as when task includes this 3 subtasks of A, B, C, subtask A, B, C are respectively used to configure net
Network equipment X, Y, Z, a corresponding reverse subtask, each subtask, subtask A, B, C reverse subtask are respectively a, b, c,
When being configured according to subtask A to network equipment X, in fact it could happen that network equipment X configuration successfuls, it is also possible to network occur and set
The situation of standby X configuration failures, if at least one failure of subtask B, C and subtask A successes, reverse subtask a is used for will configuration
Successful network equipment X is retracted, and it is return back to state before configuration.
If task does not run succeeded completely, performing inverse task includes：If at least one subtask performs failure, it is determined that
Reverse subtask corresponding to its difference, perform all reverse subtasks in addition to corresponding reversely subtask.
If performing failure at least one subtask, before determining reverse subtask corresponding to its difference, in addition to：Perform
All subtasks, and after the implementing result of all subtasks is received, judge whether that at least one subtask performs failure.
Because the subtask for performing failure shows that the network equipment corresponding to the subtask is not configured to work(, in order to ensure to more
The atomicity and uniformity that the platform network equipment is configured, do not have to its configuration status then so configuring the failed network equipment
Retracted, namely without carrying out reverse subtask corresponding to it.So only need to be by the net corresponding to the subtask to run succeeded
The configuration status of network equipment is retracted, namely need to only will be configured to the state that the network equipment of work(is returned to before its configuration
.
When being configured to the more network equipments simultaneously, in order to keep atomicity and uniformity, if an at least network
Device configuration fails, then the state of all network equipments is required for the state returned to before configuration, is every using such scheme
The platform network equipment all sets reverse subtask corresponding to a subtask and one, and subtask is used to match somebody with somebody the network equipment
Put, reverse subtask is used for the state for making the network equipment of a configuration successful return back to before its configuration, if at least one son is appointed
It is engaged in performing failure, determines reverse subtask corresponding to its difference, performs automatically all reverse in addition to corresponding reversely subtask
Subtask so that the state that the network equipment of configuration successful is return back to before its configuration, if the network equipment of configuration successful has more,
Reverse subtask corresponding to then performing this more network equipments automatically, without manual operation, improves O＆M efficiency, ensure that fortune
Dimension work is simplified, and improves efficiency and the flexibility of service deployment.
Wherein, at least one subtask performs and unsuccessfully included：The execution time of at least one subtask exceedes default hold
Row time threshold.When being configured at the same time to the more network equipments, subtask corresponding to every network equipment, which starts simultaneously at, holds
OK, when the execution time of at least one subtask exceeding default execution time threshold, then it is assumed that hold at least one subtask
Row failure.
The time point for performing reverse subtask is：Treat that all subtasks perform completion, then start to perform reverse subtask；
Or treat that the execution time of subtask exceedes default execution time threshold, then start to perform reverse subtask.
Task includes multiple subtasks, if some subtask is not because network failure or other reasonses return for a long time
Implementing result, this just influences whether the execution state of whole task, so being for one threshold value of execution duration setting of subtask
It is necessary, still do not returned when reaching default execution time threshold, be considered as subtask and perform failure.
Task includes multiple subtasks, and the state of subtask may decide that the state gone out on missions.The execution time of subtask
More than default execution time threshold, the subtask is also to perform failure.As long as there is a sub- tasks carrying failure, then task
State is to perform failure；If whole subtasks run succeeded, the state of task is just to run succeeded.
When occurring first sub- tasks carrying failure in task, or there is subtask and perform the time exceeding default execution
During time threshold, then result of the SDN controllers in time by tasks carrying failure reports dispatch layer.
Present embodiments provide transaction mechanism that is a kind of while being configured to the more network equipments, Ye Jiti
For a task that is a kind of while being configured to the more network equipments.Transaction includes 2 attributes：It is atomicity, consistent
Property.Atomicity refers to that a transaction is an indivisible work unit,
Either all operations that transaction includes all are done, or do not do.Uniformity refers to that transaction must
Must database is changed to another coherency state from a coherency state.Uniformity and atomicity are closely related.
Or the transaction mechanism that the present embodiment provides can ensure the whole configuration successfuls of this transaction, or all
Configuration failure.
In order to realize the centralized Control to the network equipment, realized using SDN controllers and issued simultaneously to the more network equipments
Configuration, SDN controllers can be divided into client and server end, and transaction mechanism is initiated by dispatch layer, and dispatch layer issues
This subtask carries an identifier, for representing once dispatching for task, and supervised by the identifier to client in task
Listen the implementing result of the subtask.After client receives task, client first handles this subtask, and obtains holding for this subtask
Row result, task action result and identifier are advertised to dispatch layer together.Scheduling between dispatch layer and client is different
What step performed, i.e., dispatch layer withouts waiting for the result of client, but result is actively reported dispatch layer by client.Scheduling
The request of layer needs client and server cooperation is common to complete.
After client receives being sent by dispatch layer for task, task is first parsed, calculates the network equipment number to be configured, so
The request of the sub-mark symbol of application distribution corresponding number is sent to server end afterwards.Server end receives the request that client is sent
Afterwards, server end is created and stores transaction structures as shown in Figure 2, and each sub-mark is accorded with to the character string number of composition
Group returns to client.In transaction structures, F represents that client receives the identifier entrained by task, S1, S2, S3 ...
Sn represents the sub-mark symbol that client application is arrived.Server end is stored task and inverse task, task
For being configured to the more network equipments, inverse task is used to be retracted according to the network equipment of task configuration successful,
It is set to return back to state before configuration.
Apply to sub-mark after according with, client is that each network equipment builds a subtask configured, each
Subtask is identified with a sub- identifier, and is accorded with by the sub-mark and tracked and monitor the implementing result of subtask.For
When each network equipment builds a subtask, a reverse subtask corresponding with the subtask can be also built simultaneously, instead
It is used to be retracted a network equipment according to subtask configuration successful to subtask, it is return back to state before configuration.
After client obtains the implementing result of subtask, the implementing result of subtask is advertised to server end, but it is objective
Family end is not aware that the implementing result of whole task, and client sends the implementing result that whole task is inquired about in application
Request, server end first sets the state of corresponding subtask after the implementing result of subtask is received.Server end traversal is each
The state of the state of subtask, more new task, and the state of task is returned into client.State after subtask performs is divided into
SUCCESS (success) and FAIL (failure).Server end return to the task of client state include WAIT (wait),
SUCCESS, FAIL and DISCARD (discarding).Wherein, WAIT expressed portions molecule tasks carrying success, other subtasks still exist
The state of execution, when server end return state be to wait for state, illustrate that whole task has not been completed, to continue waiting for.
The subtask that SUCCESS represents all has all run succeeded, and server end returns to the whole tasks carrying success of the state description.
FAIL is represented once finding that some subtask therein performs failure, then the state of whole task to be arranged into failure, serviced
Device end returns to the whole tasks carrying failure of the state description.DISCARD is represented before the execution of current subtask terminates, and has had son
Tasks carrying fails, and server end returns to the whole tasks carrying failure of the state description, and has reported dispatch layer, client
End receives DISCARD and no longer does any processing.
Because client is after the implementing result of subtask is obtained, just sends application to server end and inquire about whole task
Implementing result request, so the state that server end returns to the task of client be WAIT, SUCCESS, FAIL and
The one kind of DISCARD in these four.And the state of task also includes START (startup), server end is being created and stored such as Fig. 2
After shown transaction structures, the state of task is set to START, and sub-mark symbol is returned into client.
Referring to Fig. 3, the change between each state of task is specific as follows：
START to WAIT：Into after START, server end just waits the implementing result of client notice subtask at any time,
When the implementing result for first subtask that server end receives is to run succeeded, the state of task is just transformed into from START
WAIT。
WAIT to SUCCESS：If the state of task is WAIT, illustrates that existing part subtask runs succeeded, not yet occur
Perform the subtask of failure.When the notice that server end receives is the implementing result of last subtask and last height
During tasks carrying success, the state of task is just from WAIT to SUCCESS.
WAIT to FAIL：If the state of task is WAIT, illustrates that existing part subtask runs succeeded, not yet perform
The subtask of failure.When the implementing result for the subtask that server end receives is to perform failure, the state of task is just from WAIT
To FAIL.
FAIL to DISCARD：If the state of task is FAIL, illustrate existing one sub- tasks carrying failure, whole task
It has been failed that, the implementing result of current subtask does not interfere with the state of task, i.e. a subtask has performed failure, does not have to
The implementing result of a subtask of the pipe after this subtask is success or failure, and now the state of task is just from FAIL
To DISCARD.
DISCARD to DISCARD：If the state of task is DISCARD, whole task has failed, current subtask
Implementing result does not interfere with the state of task, that is, the implementing result for not having to manage current subtask is success or failure, and this is former
Or DISCARD states the state of business is just from DISCARD to DISCARD, i.e.,.
Client is handled according to the task status received, and principle is：WAIT represents that task is not carried out terminating, and does not locate
Reason, will not report dispatch layer；SUCCESS represents to run succeeded, and reports dispatch layer；FAIL is represented to perform failure, reported
Dispatch layer；DISCARD represents that task has performed failure, no longer does any processing.
When a task exceedes default execution time threshold in server end storage time, server end tells client
Task time-out, if client receives the information for the task time-out that server end is sent, then it represents that tasks carrying fails, and reports
Dispatch layer discharges related resource simultaneously.
Wherein, when performing failure due to some subtask and cause whole tasks carrying to fail, in order to ensure task
Atomicity and uniformity, the subtask to run succeeded is retracted using fallback mechanism so that the network equipment of configuration successful
It return back to state before configuring.If at least one subtask performs failure, it is determined that reverse subtask corresponding to its difference, execution remove
Corresponding reversely all reverse subtasks outside subtask.Because the subtask for performing failure shows network corresponding to the subtask
Equipment is not configured to work(, in order to ensure the atomicity and uniformity that are configured to the more network equipments, so configuration is failed
The network equipment do not have to then be retracted its state, namely without carrying out reverse subtask corresponding to it.So it will need to only hold
The successful subtask of row is retracted, namely need to only will be configured to state that the network equipment of work(is returned to before its configuration i.e.
Can.
In the present embodiment, the configuration operation of SDN controllers to the network equipment is the bottom, most basic operation, and SDN is controlled
The south orientation passage that device processed uses need to ensure the atomicity of this configuration operation, be handled by transaction modes.Example
As NETCONF (Network Configuration Protocol, network configuration protocol) can be used to be used as south orientation for SDN controllers
Passage, NETCONF can ensure the atomicity of a NETCONF message interaction in itself, so being operated for most configurations, such as
Fruit produces mistake, it is not required that retracts.Therefore if whole tasks carrying failure is, it is necessary to which the part to retract is performed in whole task
Those successful subtasks.
Require that client while structure positive configuration subtask, builds corresponding reversely son in the present embodiment
Task, and server end management is transferred into the reverse subtask, the reverse subtask will call when needing and retracting.Rollback when
After machine has been performed both by all subtasks；Or judge that the execution time of some subtask exceedes default hold in server end
Row time threshold, at this moment think that the subtask performs failure, it is necessary to which the subtask to have run succeeded is retracted, for super
When task in be also not carried out terminate subtask, be defaulted as performing failure, do not do rollback processing.
Reverse subtask is scheduled by server end, server end judges go out on missions satisfaction execution failure or time-out,
And after the condition on the opportunity that retracts, server end can directly carry out rollback processing, and client and dispatch layer need not perceive rollback
Handling process.
Referring to Fig. 4, the present embodiment also example illustrates for a specific example, specific as follows：
The present embodiment uses south orientation passages of the NETCONF as SDN controllers.Reason has these points：1st, NETCONF makes
With XML (Extensible Markup Language, extensible markup language) as configuration data and the coding of protocol message
Mode, XML can express the management object of modelling that is complicated, having internal logical relationship, substantially increase operating efficiency
With objective metric.According to XML this advantage, the dependence between configuration can be expressed using XML, so as to shield
Fall perception of the NETCONF operating levels to dependence.The 2nd, as long as NETCONF equipment realizes wrong rollback ability urn:
ietf:params:netconf:capability:rollback-on-error:1.0, referring to rfc6241, in structure configuration report
The error-option (error option) of configuration message is arranged to rollback-on-error (retract mistake) when literary, with regard to energy
Ensure the atomicity of the configuration operation of each NETCONF message.3rd, the reverse message for building NETCONF messages is also easy to.
Fig. 5 is one and carries out central controlled network using SDN controllers, it is assumed that dispatch layer is handed down to SDN controllers one
Individual task：Create S1 to S7 tunnel.It is to make how current configuration to be described below in detail using transaction mechanism
It is configured to for a task on the more network equipments.
S201：Dispatch layer is handed down to one task of client of SDN controllers：Create S1 to S7 tunnel.Task
One identifier of middle carrying.
Dispatch layer is handed down to one task of client of SDN controllers：Create S1 to S7 tunnel.Carried in task
One identifier create-tunnel-1 (establishment-tunnel -1) and the relevant information for creating tunnel.Dispatch layer passes through asynchronous system
This task is called, then create-tunnel-1 is added in the queue for monitoring implementing result, is then back to.
S202：Client, which calculates, to be configured the tunnel and needs while configure S1, S2, S3, S7 this four nodes, therefore to service
Device end sends the request of application four sub- identifiers of distribution.
After the client of SDN controllers receives the task that identifier is create-tunnel-1, with reference on SDN controllers
Topology information calculate and configure the tunnel and need while configure S1, S2, S3, S7 this four nodes, need four sons times altogether
It is engaged in complete this configuration, therefore the request of application four sub- identifiers of distribution is sent to server end.
S203：Server end distributes four sub- identifiers, and returns to client.
After server end receives the request that identifier is create-tunnel-1 and sub-mark symbol number is 4, server end
Storage architecture is created, the sub-mark symbol of the identifier comprising task and four subtasks, four subtasks are separately dispensed into
Create-tunnel-1-s1, create-tunnel-1-s2, create-tunnel-1-s3, create-tunnel-1-s7 make
Accorded with for sub-mark, and sub-mark symbol is returned into client, while the state of task is arranged to START.Sub-mark symbol is used for
Subtask corresponding to mark and tracking.
S204：Client builds reverse subtask corresponding to four subtasks and four, and the reverse son built is appointed
Trustship be engaged in server end.Each subtask carries a sub- identifier.
After client receives four sub- identifiers, reverse subtask corresponding to four subtasks and four is built, structure
Four subtasks are built in the form of message, and four reverse subtasks of structure are also built in the form of message, by what is built
Reverse subtask trustship is to server end.Each subtask carries a sub- identifier, asynchronously subtasking, leads to
Cross the implementing result that sub-mark symbol monitors subtask.
S205：Client monitors the implementing result of subtask, by the implementing result notification server end of subtask, and waits
Server end returns to the state of task, and respective handling is carried out according to the state of task.Client repeats S205 operation always, directly
Implementing result is all returned to all subtasks.
If the task status that client receives server end return is WAIT, expression task is not carried out terminating, client
Do not handle, dispatch layer will not be reported；If the task status that client receives server end return is SUCCESS, represent to perform
Success, client report dispatch layer；If the task status that client receives server end return is FAIL, expression performs mistake
Lose, client reports dispatch layer；If the task status that client receives server end return has represented task for DISCARD
Failure is performed, client no longer does any processing.
S206：Server end finds the corresponding subtask of storage by sub-mark symbol, and sets its state.Then travel through
All subtasks in addition, the state of task are calculated according to State Transferring mechanism, and the state of task is returned into client
End.Server end judges whether all execution terminates for all subtasks simultaneously, if then determining whether to calculate what is gone out on missions
State is SUCCESS, FAIL or DISCARD, and respective handling is done according to the state of task.
Server end receives the implementing result of the subtask of client transmission, and after the request of query task state, leads to
The sub-mark symbol for crossing subtask carrying finds the corresponding subtask of storage, and sets its state.Then traversal is all in addition
Subtask, the state of task is calculated according to State Transferring mechanism, and the state of task is returned into client.Service simultaneously
Device end judges whether all subtasks all perform and terminated, if then determining whether that calculating the state gone out on missions is
SUCCESS, FAIL or DISCARD, if SUCCESS, then delete task and its comprising subtask, discharge resource；If
It is FAIL or DISCARD, then triggers rollback flow, reverse subtask corresponding to the subtask that calling has run succeeded, treat anti-
To subtask perform terminate after, delete task and its comprising subtask, discharge resource.
S207：The execution time that server end checks subtask exceedes default execution time threshold, then notifies client
Mission failure is held, and triggers rollback flow, reverse subtask corresponding to the subtask that calling has run succeeded, treats reverse son
After tasks carrying terminates, delete task and its comprising subtask, discharge resource.
The configuration status backing method provided according to the present embodiment, by obtaining task and corresponding inverse task；Task
For being configured to the more network equipments, inverse task is used to be retracted according to the network equipment of task configuration successful,
It is set to return back to state before configuration；If task does not run succeeded completely, inverse task is performed, makes all-network corresponding to task
The state that equipment is return back to before configuration；Using such scheme, when being configured according to task to the more network equipments, may go out
Existing partial network devices configuration successful, the situation of partial network devices configuration failure, inverse task are used for the net that will be configured to work(
Network equipment is retracted, and it is return back to state before configuration, thereby guarantees that the shape that all network equipments are in before configuration
State, atomicity and uniformity to more network equipments configurations are ensure that, and inverse task performs automatically, without O＆M people
Member operates to the network equipment one by one, improves O＆M efficiency, ensure that maintenance work is simplified, improve service deployment
Efficiency and flexibility.
Embodiment two
In order to ensure the atomicity and uniformity that are configured to the more network equipments, and in order to improve O＆M efficiency,
Efficiency and the flexibility of service deployment are improved, the present embodiment provides a kind of configuration status rollback device, refers to Fig. 6, including：
Acquisition module 601, for obtaining task and corresponding inverse task, task is used to match somebody with somebody the more network equipments
Put, inverse task is used to be retracted according to the network equipment of task configuration successful, it is return back to state before configuration.
In order to realize the centralized Control to the network equipment, task and corresponding inverse task are obtained using acquisition module 601；
Task is used to configure the more network equipments, and inverse task is used to be returned according to the network equipment of task configuration successful
Move back, it is return back to state before configuration, when being configured according to task to the more network equipments, in fact it could happen that subnetwork is set
Standby configuration successful, the situation of partial network devices configuration failure, the network equipment that inverse task is used to will be configured to work(are returned
Move back, it is return back to state before configuration.
Processing module 602, if not run succeeded completely for task, inverse task is performed, make to own corresponding to task
The state that the network equipment is return back to before configuration.
Acquisition module 601 is created corresponding with the task after being issued by dispatch layer for task is got by processing module 602
Inverse task, inverse task be used for will be retracted according to the network equipment of task configuration successful, before it is return back to configuration
State.In the case where task does not run succeeded completely, processing module 602 performs inverse task, makes all nets corresponding to task
The state that network equipment is return back to before configuration, the atomicity and uniformity configured to the more network equipments is ensure that, and improved
O＆M efficiency, ensure that maintenance work is simplified, improves efficiency and the flexibility of service deployment.
Wherein, task includes multiple subtasks, a corresponding reverse subtask, each subtask；One subtask is used to match somebody with somebody
A network equipment is put, a reverse subtask is used to be retracted a network equipment according to subtask configuration successful,
It is set to return back to state before configuration, such as when task includes this 3 subtasks of A, B, C, subtask A, B, C are respectively used to configure net
Network equipment X, Y, Z, a corresponding reverse subtask, each subtask, subtask A, B, C reverse subtask are respectively a, b, c,
When being configured according to subtask A to network equipment X, in fact it could happen that network equipment X configuration successfuls, it is also possible to network occur and set
The situation of standby X configuration failures, if at least one failure of subtask B, C and subtask A successes, reverse subtask a is used for will configuration
Successful network equipment X is retracted, and it is return back to state before configuration.Processing module 602 is used for：If at least one subtask
Perform failure, determine it respectively corresponding to reverse subtask, perform except corresponding reversely all reverse subtasks in addition to subtask.
If processing module 602 is additionally operable to perform failure at least one subtask, determine that reversely son is appointed corresponding to its difference
Before business, all subtasks are performed, and after the implementing result of all subtasks is received, judge whether that at least one son is appointed
Business performs failure.
Because the subtask for performing failure shows that the network equipment corresponding to the subtask is not configured to work(, in order to ensure to more
The atomicity and uniformity that the individual network equipment is configured, do not have to its configuration status then so configuring the failed network equipment
Retracted, namely without carrying out reverse subtask corresponding to it.So the subtask to run succeeded need to only be retracted i.e.
Can, namely need to only will be configured to the state that the network equipment of work(is returned to before its configuration.
When being configured to the more network equipments simultaneously, in order to keep atomicity and uniformity, if an at least network
Device configuration fails, then the state of all network equipments is required for the state returned to before configuration, is every using such scheme
The platform network equipment all sets reverse subtask corresponding to a subtask and one, and subtask is used to match somebody with somebody the network equipment
Put, reverse subtask is used for the state for making the network equipment of a configuration successful return back to before its configuration, if at least one son is appointed
Business performs failure, then processing module 602 determines reverse subtask corresponding to its difference, automatic to perform except corresponding reverse subtask
Outer all reverse subtasks so that the state that the network equipment of configuration successful is return back to before its configuration, if the net of configuration successful
Network equipment has more, then processing module 602 performs reverse subtask corresponding to this more network equipments automatically, without artificial behaviour
Make, improve O＆M efficiency, ensure that maintenance work is simplified.
Wherein, at least one subtask performs and unsuccessfully included：The execution time of at least one subtask exceedes default hold
Row time threshold.When being configured at the same time to the more network equipments, subtask corresponding to every network equipment, which starts simultaneously at, holds
OK, when the execution time of at least one subtask exceeding default execution time threshold, then it is assumed that hold at least one subtask
Row failure.
The time point that processing module 602 performs reverse subtask is：Treat that all subtasks perform completion, then processing module
602 start to perform reverse subtask；Or treat that the execution time of subtask exceedes default execution time threshold, then handle mould
Block 602 starts to perform reverse subtask.
Task includes multiple subtasks, if some subtask is not because network failure or other reasonses return for a long time
Implementing result, this just influences whether the execution state of whole task, so being for one threshold value of execution duration setting of subtask
It is necessary, still do not returned when reaching default execution time threshold, be considered as subtask and perform failure.
Task includes multiple subtasks, and the state of subtask may decide that the state gone out on missions.The execution time of subtask
More than default execution time threshold, the subtask is also to perform failure.As long as there is a sub- tasks carrying failure, then task
State is to perform failure；If whole subtasks run succeeded, the state of task is just to run succeeded.
When occurring first sub- tasks carrying failure in task, or there is subtask and perform the time exceeding default execution
During time threshold, then processing module 602 is in time by tasks carrying reporting failure to dispatch layer.
Present embodiments provide transaction mechanism that is a kind of while being configured to the more network equipments, Ye Jiti
For a task that is a kind of while being configured to the more network equipments.Transaction includes 2 attributes：It is atomicity, consistent
Property.Atomicity refers to that a transaction is an indivisible work unit, all behaviour that transaction includes
Either work is all done, or do not do.Uniformity refers to that transaction must database is changed to from a coherency state
Another coherency state.Uniformity and atomicity are closely related.
Transaction mechanism is initiated by dispatch layer, and acquisition module 601 obtains this subtask that task scheduling layer issues,
An identifier is carried in task, for representing once dispatching for task, and monitors by the identifier execution of the subtask
As a result.After acquisition module 601 receives task, this subtask is first handled, and obtains the implementing result of this subtask, by tasks carrying
As a result and identifier is advertised to dispatch layer together.The request of dispatch layer needs acquisition module 601 to be cooperated with processing module 602 altogether
With completion.
After acquisition module 601 receives being sent by dispatch layer for task, task is first parsed by processing module 602, calculating will match somebody with somebody
The network equipment number put, then distribute the sub-mark symbol of corresponding number.Processing module 602 is created and stored as shown in Figure 2
Transaction structures.In transaction structures, F represents that acquisition module 601 receives identifier entrained by task, S1,
S2, S3 ... Sn represent the sub-mark symbol being assigned to.Processing module 602 is stored task and inverse task, task be used for pair
The more network equipments are configured, and inverse task is used to be retracted according to the network equipment of task configuration successful, makes its time
Fall back on state before configuring.
After being assigned to sub-mark symbol, processing module 602 is that each network equipment builds a subtask configured,
Each subtask is identified with a sub- identifier, and is accorded with by the sub-mark and tracked and monitor the implementing result of subtask.
Processing module 602 when building a subtask for each network equipment, can also build simultaneously one it is corresponding with the subtask
Reverse subtask, reverse subtask be used for a network equipment according to subtask configuration successful is retracted, make its time
Fall back on state before configuring.
After processing module 602 obtains the implementing result of subtask, the state of corresponding subtask is first set.Processing module 602
Travel through the state of each subtask, the state of more new task.State after subtask performs is divided into SUCCESS and FAIL.Task
State includes WAIT, SUCCESS, FAIL and DISCARD.Wherein, WAIT expressed portions molecule tasks carrying success, other subtasks
Still in the state of execution, when the state of task is to wait for state, illustrates that whole task has not been completed, to continue waiting for.
SUCCESS represents that all subtask has all run succeeded, the state of task for SUCCESS illustrate whole tasks carrying into
Work(.FAIL is represented once finding that some subtask therein performs failure, then the state of whole task to be arranged into failure, appointed
The state of business is that FAIL illustrates whole tasks carrying failure.DISCARD is represented before the execution of current subtask terminates, and has had son
Tasks carrying fails, and the state of task illustrates whole tasks carrying failure for DISCARD, and has reported dispatch layer.
The state of task except WAIT, SUCCESS, FAIL and DISCARD these four, also a kind of state is START, place
Module 602 is managed after creating and storing transaction structures as shown in Figure 2, the state of task is set to START.
Referring to Fig. 3, the change between each state of task is specific as follows：
START to WAIT：Into after START, when the implementing result for first subtask that processing module 602 receives is to hold
When going successfully, the state of task is just transformed into WAIT from START.
WAIT to SUCCESS：If the state of task is WAIT, illustrates that existing part subtask runs succeeded, not yet occur
Perform the subtask of failure.When the notice that processing module 602 receives be the implementing result of last subtask and last
When subtask runs succeeded, the state of task is just from WAIT to SUCCESS.
WAIT to FAIL：If the state of task is WAIT, illustrates that existing part subtask runs succeeded, not yet perform
The subtask of failure.When the implementing result for the subtask that processing module 602 receives is to perform failure, the state of task just from
WAIT to FAIL.
FAIL to DISCARD：If the state of task is FAIL, illustrate existing one sub- tasks carrying failure, whole task
It has been failed that, the implementing result of current subtask does not interfere with the state of task, i.e. a subtask has performed failure, does not have to
The implementing result of a subtask of the pipe after this subtask is success or failure, and now the state of task is just from FAIL
To DISCARD.
DISCARD to DISCARD：If the state of task is DISCARD, whole task has failed, current subtask
Implementing result does not interfere with the state of task, that is, the implementing result for not having to manage current subtask is success or failure, and this is former
Or DISCARD states the state of business is just from DISCARD to DISCARD, i.e.,.
Processing module 602 is handled according to the task status received, and principle is：WAIT represents that task is not carried out tying
Beam, do not handle, dispatch layer will not be reported；SUCCESS represents to run succeeded, and reports dispatch layer；FAIL expressions perform failure,
Report dispatch layer；DISCARD represents that task has performed failure, no longer does any processing.
When a task exceedes default execution time threshold in the storage time of processing module 602, then it represents that tasks carrying
Failure, reports dispatch layer while discharges related resource.
Wherein, when performing failure due to some subtask and cause whole tasks carrying to fail, in order to ensure task
Atomicity and uniformity, the subtask to run succeeded is retracted using fallback mechanism so that the network equipment of configuration successful
It return back to state before configuring.If at least one subtask performs failure, it is determined that reverse subtask corresponding to its difference, execution remove
Corresponding reversely all reverse subtasks outside subtask..Because the subtask for performing failure shows net corresponding to the subtask
Network equipment is not configured to work(, in order to ensure the atomicity and uniformity that are configured to the more network equipments, so configuration not into
The network equipment of work(does not have to then be retracted its state, namely without carrying out reverse subtask corresponding to it.So only need by
The subtask to run succeeded is retracted, namely need to only will be configured to the state that the network equipment of work(is returned to before its configuration
.
In the present embodiment, it is the bottom, most basic operation to the configuration operation of the network equipment, used south orientation leads to
Road need to ensure the atomicity of this configuration operation, be handled by transaction modes.Such as NETCONF can be used
(Network Configuration Protocol, network configuration protocol) is used as south orientation passage, and NETCONF can ensure in itself
The atomicity of NETCONF message interaction, so being operated for most configurations, if producing mistake, it is not required that retract.
Therefore if whole tasks carrying failure is, it is necessary to which the part to retract is those subtasks to be run succeeded in whole task.
Required in the present embodiment while positive configuration subtask is obtained, and obtain corresponding reversely son and appoint
Business, the reverse subtask will call when needing and retracting.After the opportunity of rollback has been performed both by all subtasks；Or locating
Reason module 602 judges that the execution time of some subtask exceedes default execution time threshold, at this moment thinks that the subtask is held
Row failure is, it is necessary to the subtask to have run succeeded be retracted, for the son times for being also not carried out terminating in overtime task
Business, is defaulted as performing failure, does not do rollback processing.
Reverse subtask is scheduled by processing module 602, processing module 602 judge go out on missions satisfaction perform failure or
After time-out, and the condition on the opportunity that retracts, processing module 602 can directly carry out rollback processing, and dispatch layer need not perceive rollback
Handling process.
The present embodiment also example illustrates for a specific example, specific as follows：
The present embodiment uses NETCONF as south orientation passage.Reason has these points：1st, NETCONF uses XML
(Extensible Markup Language, extensible markup language) as configuration data and the coded system of protocol message,
XML can express the management object of modelling that is complicated, having internal logical relationship, substantially increase operating efficiency and object
Standardization.According to XML this advantage, the dependence between configuration can be expressed using XML, so as to mask
Perception of the NETCONF operating levels to dependence.The 2nd, as long as NETCONF equipment realizes wrong rollback ability urn:ietf:
params:netconf:capability:rollback-on-error:1.0, referring to rfc6241, when building configuration message
The error-option (error option) of configuration message is arranged to rollback-on-error (retract mistake), it is ensured that
The atomicity of the configuration operation of each NETCONF message.3rd, the reverse message for building NETCONF messages is also easy to.
Assuming that acquisition module 601 obtains the task issued by dispatch layer：Create S1 to S7 tunnel.It is detailed below
Thin description is current configuration is configured to as a task on the more network equipments using transaction mechanism.
Acquisition module 601 obtains the task issued by dispatch layer：Create S1 to S7 tunnel.Carried in task
One identifier.
Acquisition module 601 obtains the task issued by dispatch layer：Create S1 to S7 tunnel.Carried in task
One identifier create-tunnel-1 (establishment-tunnel -1) and the relevant information for creating tunnel.Dispatch layer passes through asynchronous system
This task is called, then create-tunnel-1 is added in the queue for monitoring implementing result, is then back to.
Processing module 602, which calculates, to be configured the tunnel and needs while configure S1, S2, S3, S7 this four nodes, therefore to each
Node distributes a sub- identifier.
After acquisition module 601 gets the task that identifier is create-tunnel-1, with reference to opening up on SDN controllers
Flutter information and calculate and configure the tunnel and need while configure S1, S2, S3, S7 this four nodes, need four subtasks altogether
This configuration is completed, therefore a sub- identifier is distributed to each node.And storage architecture is created, include the mark of a task
Symbol and the sub-mark symbol of four subtasks, four subtasks are separately dispensed into create-tunnel-1-s1, create-
Tunnel-1-s2, create-tunnel-1-s3, create-tunnel-1-s7 accord with as sub-mark, while by the shape of task
State is arranged to START.Sub-mark symbol be used for mark and track corresponding to subtask.
Processing module 602 builds reverse subtask corresponding to four subtasks and four, and each subtask carries one
Sub-mark accords with.Four subtasks of structure are built in the form of message, four reverse subtasks of structure also structure in the form of message
Build.Each subtask carries a sub- identifier, asynchronously subtasking, is accorded with by sub-mark and monitors subtask
Implementing result.
Processing module 602 monitors the implementing result of subtask, and carries out respective handling according to the state of task.
If task status is WAIT, expression task is not carried out terminating, and processing module 602 is not handled, and will not report tune
Spend layer；If task status is SUCCESS, represent to run succeeded, processing module 602 reports dispatch layer；If task status is
FAIL, expression perform failure, and processing module 602 reports dispatch layer；If task status is DISCARD, expression task has been held
Row failure, processing module 602 no longer do any processing.
Processing module 602 finds the corresponding subtask of storage by sub-mark symbol, and sets its state.Then traversal is another
Outer all subtasks, the state of task is calculated according to State Transferring mechanism.Processing module 602 judges that all sons are appointed simultaneously
Whether business, which all performs, is terminated, if it is SUCCESS, FAIL or DISCARD then to determine whether to calculate the state gone out on missions, root
Respective handling is done according to the state of task.
The sub-mark symbol that processing module 602 is carried by subtask finds the corresponding subtask of storage, and sets its shape
State.Then the other all subtasks of traversal, the state of task is calculated according to State Transferring mechanism.Processing module 602 simultaneously
Judge whether all subtasks all perform to terminate, if then determine whether to calculate the state gone out on missions be SUCCESS,
FAIL or DISCARD, if SUCCESS, then delete task and its comprising subtask, discharge resource；If FAIL or
DISCARD, then rollback flow is triggered, reverse subtask corresponding to the subtask that calling has run succeeded, treats reverse subtask
After execution terminates, delete task and its comprising subtask, discharge resource.
The execution time that processing module 602 checks subtask exceedes default execution time threshold, whole tasks carrying
Failure, rollback flow is triggered, reverse subtask corresponding to the subtask that calling has run succeeded, treats that reverse subtask performs knot
Shu Hou, delete task and its comprising subtask, discharge resource.
The configuration status rollback device provided according to the present embodiment, task and corresponding anti-is obtained by acquisition module 601
To task；Task is used to configure the more network equipments, and inverse task is used to be set according to the network of task configuration successful
It is standby to be retracted, it is return back to state before configuration；If processing module 602 does not run succeeded completely for task, perform anti-
To task, the state for making all-network equipment corresponding to task return back to before configuration；Using such scheme, according to task to more
When the platform network equipment is configured, in fact it could happen that partial network devices configuration successful, the situation of partial network devices configuration failure,
The network equipment that inverse task is used to will be configured to work(is retracted, and it is return back to state before configuration, is thereby guaranteed that all
The network equipment is in the state before configuration, ensure that the atomicity and uniformity to more network equipments configurations, and reversely
Task is performed automatically, and the network equipment is operated one by one without operation maintenance personnel, O＆M efficiency is improved, ensure that O＆M
Work is simplified, and improves efficiency and the flexibility of service deployment.
A kind of computer-readable storage medium is also provided in another embodiment, and being stored with computer in computer-readable storage medium can
Execute instruction, computer executable instructions are used for the configuration status backing method for performing any one of embodiment one.
Obviously, those skilled in the art should be understood that each module of the embodiments of the present invention or each step can be used
General computing device realizes that they can be concentrated on single computing device, or be distributed in multiple computing device institutes
On the network of composition, alternatively, they can be realized with the program code that computing device can perform, it is thus possible to by they
It is stored in storage medium (ROM/RAM, magnetic disc, CD) and is performed by computing device, and in some cases, can be with not
The order being same as herein performs shown or described step, or they are fabricated to each integrated circuit modules respectively, or
Multiple modules or step in them are fabricated to single integrated circuit module to realize by person.So the present invention is not restricted to appoint
What specific hardware and software combines.
Above content is to combine the further description that specific embodiment is made to the embodiment of the present invention, it is impossible to is recognized
The specific implementation of the fixed present invention is confined to these explanations.For general technical staff of the technical field of the invention,
Without departing from the inventive concept of the premise, some simple deduction or replace can also be made, should all be considered as belonging to the present invention
Protection domain.
Claims (10)
1. a kind of configuration status backing method, including：
Acquisition task and corresponding inverse task；The task is used to configure the more network equipments, the inverse task
For will be retracted according to the network equipment of the task configuration successful, it is set to return back to state before configuration；
If the task does not run succeeded completely, the inverse task is performed, makes all-network equipment corresponding to the task
The state returning back to before configuration.
2. configuration status backing method as claimed in claim 1, it is characterised in that the task includes multiple subtasks, often
An individual corresponding reverse subtask, the subtask；One subtask is used to configure the network equipment, an institute
State reverse subtask to be used to be retracted according to the network equipment of the subtask configuration successful, return back to it
State before configuration；
If the task does not run succeeded completely, performing the inverse task includes：If at least one subtask
Perform failure, determine it respectively corresponding to reverse subtask, perform except corresponding reversely all reversely sons in addition to subtask
Task.
3. configuration status backing method as claimed in claim 2, it is characterised in that at least one subtask performs
Unsuccessfully include：The execution time of at least one subtask exceedes default execution time threshold.
4. configuration status backing method as claimed in claim 2 or claim 3, it is characterised in that described to perform the reverse subtask
Including：Treat that all subtasks perform completion, then start to perform the reverse subtask；Or treat the subtask
The execution time exceedes default execution time threshold, then starts to perform the reverse subtask.
5. configuration status backing method as claimed in claim 2 or claim 3, it is characterised in that if at least one son
Tasks carrying fails, before determining reverse subtask corresponding to its difference, in addition to：All subtasks are performed, and are being connect
After the implementing result for receiving all subtasks, judge whether that at least one subtask performs failure.
6. a kind of configuration status rollback device, including：
Acquisition module, for obtaining task and corresponding inverse task；The task is used to configure the more network equipments,
The inverse task is used to be retracted according to the network equipment of the task configuration successful, before it is return back to configuration
State；
Processing module, if not run succeeded completely for the task, the inverse task is performed, is made corresponding to the task
The state that all-network equipment is return back to before configuration.
7. configuration status rollback device as claimed in claim 6, it is characterised in that the task includes multiple subtasks, often
An individual corresponding reverse subtask, the subtask；One subtask is used to configure the network equipment, an institute
State reverse subtask to be used to be retracted according to the network equipment of the subtask configuration successful, return back to it
State before configuration；
The processing module is used for：If at least one subtask performs failure, reverse subtask corresponding to its difference is determined,
Perform all reverse subtasks in addition to the corresponding reversely subtask.
8. configuration status rollback device as claimed in claim 7, it is characterised in that at least one subtask performs
Unsuccessfully include：The execution time of at least one subtask exceedes default execution time threshold.
9. configuration status rollback device as claimed in claim 7 or 8, it is characterised in that the processing module is used for：Wait own
The subtask perform completion, then start to perform the reverse subtask；Or treat that the execution time of the subtask exceedes
Default execution time threshold, then start to perform the reverse subtask.
10. configuration status rollback device as claimed in claim 7 or 8, it is characterised in that the processing module is additionally operable to：Hold
All subtasks of row, and after the implementing result of all subtasks is received, judge whether at least one described
Subtask performs failure.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610457995.3A CN107528709A (en) | 2016-06-22 | 2016-06-22 | A kind of configuration status backing method and device |
| PCT/CN2017/083729 WO2017219775A1 (en) | 2016-06-22 | 2017-05-10 | Configuration state rollback method and device, and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610457995.3A CN107528709A (en) | 2016-06-22 | 2016-06-22 | A kind of configuration status backing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107528709A true CN107528709A (en) | 2017-12-29 |
Family
ID=60734148
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610457995.3A Withdrawn CN107528709A (en) | 2016-06-22 | 2016-06-22 | A kind of configuration status backing method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107528709A (en) |
| WO (1) | WO2017219775A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111478801A (en) * | 2020-03-27 | 2020-07-31 | 烽火通信科技股份有限公司 | Communication equipment configuration management method and system |
| CN111488367A (en) * | 2020-04-16 | 2020-08-04 | 深圳前海微众银行股份有限公司 | Method, device and equipment for realizing data consistency and computer storage medium |
| CN112965850A (en) * | 2021-03-23 | 2021-06-15 | 上海云轴信息科技有限公司 | Method and equipment for realizing workflow in middle platform system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102193780A (en) * | 2010-03-08 | 2011-09-21 | 华为技术有限公司 | Affair implementation method and affair implementation device |
| CN102420703A (en) * | 2011-11-29 | 2012-04-18 | 华为技术有限公司 | Configuration rollback method and equipment |
| US20140062875A1 (en) * | 2012-09-06 | 2014-03-06 | Panasonic Corporation | Mobile device with an inertial measurement unit to adjust state of graphical user interface or a natural language processing unit, and including a hover sensing function |
| CN104410517A (en) * | 2011-11-29 | 2015-03-11 | 华为技术有限公司 | Backspace configuring method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100555958C (en) * | 2007-07-03 | 2009-10-28 | 中兴通讯股份有限公司 | Collocation method in the Element management system |
| CN100535863C (en) * | 2007-12-06 | 2009-09-02 | 华为技术有限公司 | Method and apparatus for realizing configuring affair |
| US8776018B2 (en) * | 2008-01-11 | 2014-07-08 | International Business Machines Corporation | System and method for restartable provisioning of software components |
| CN102271057B (en) * | 2011-08-02 | 2015-08-05 | 大唐移动通信设备有限公司 | Parameter updating method and equipment |
-
2016
- 2016-06-22 CN CN201610457995.3A patent/CN107528709A/en not_active Withdrawn
-
2017
- 2017-05-10 WO PCT/CN2017/083729 patent/WO2017219775A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102193780A (en) * | 2010-03-08 | 2011-09-21 | 华为技术有限公司 | Affair implementation method and affair implementation device |
| CN102420703A (en) * | 2011-11-29 | 2012-04-18 | 华为技术有限公司 | Configuration rollback method and equipment |
| CN104410517A (en) * | 2011-11-29 | 2015-03-11 | 华为技术有限公司 | Backspace configuring method and device |
| US20140062875A1 (en) * | 2012-09-06 | 2014-03-06 | Panasonic Corporation | Mobile device with an inertial measurement unit to adjust state of graphical user interface or a natural language processing unit, and including a hover sensing function |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111478801A (en) * | 2020-03-27 | 2020-07-31 | 烽火通信科技股份有限公司 | Communication equipment configuration management method and system |
| CN111488367A (en) * | 2020-04-16 | 2020-08-04 | 深圳前海微众银行股份有限公司 | Method, device and equipment for realizing data consistency and computer storage medium |
| CN111488367B (en) * | 2020-04-16 | 2024-07-02 | 深圳前海微众银行股份有限公司 | Method, device, equipment and computer storage medium for realizing data consistency |
| CN112965850A (en) * | 2021-03-23 | 2021-06-15 | 上海云轴信息科技有限公司 | Method and equipment for realizing workflow in middle platform system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2017219775A1 (en) | 2017-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108449350B (en) | Multi-protocol arranging method and device | |
| CN108255592A (en) | A kind of Quartz clusters timing task processing system and method | |
| CN113569987A (en) | Model training method and device | |
| CN106663030A (en) | Scalable fault resilient communications within distributed clusters | |
| CN110046039A (en) | Method for scheduling task and system, control centre's server and storage medium | |
| CN104657150B (en) | Automatic operation and maintenance method in cluster environment | |
| CN107181789A (en) | A kind of distributed lock implementation method and device | |
| CN113742031A (en) | Node state information acquisition method and device, electronic equipment and readable storage medium | |
| CN104508625A (en) | Abstraction models for monitoring of cloud resources | |
| CN104021078A (en) | Software monitoring device and method | |
| CN107528709A (en) | A kind of configuration status backing method and device | |
| CN103399787B (en) | A kind of MapReduce operation streaming dispatching method and dispatching patcher calculating platform based on Hadoop cloud | |
| CN112685179A (en) | Resource deployment system and method based on cost on cloud | |
| WO2022016969A1 (en) | Data processing method and device | |
| WO2021129862A1 (en) | Method and apparatus for managing container cluster node resource pool | |
| CN105824618A (en) | Real-time message processing method for Storm | |
| CN110611707A (en) | Task scheduling method and device | |
| CN110569113A (en) | Method and system for scheduling distributed tasks and computer readable storage medium | |
| CN110740047B (en) | Network slice management arrangement system | |
| CN112333065A (en) | Automatic opening method and device for IPRAN Ethernet private line | |
| CN109257396A (en) | A kind of distributed lock dispatching method and device | |
| CN106452899B (en) | A kind of distributed data digging system and method | |
| CN109104304B (en) | Distributed real-time fault processing method | |
| EP4024761A1 (en) | Communication method and apparatus for multiple management domains | |
| CN105872055A (en) | Online monitoring method and system for computer systems in network distributed deployment mode |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20171229 |