CN105045619B - Multi-level multinode version distributed method based on fixed-bandwidth in cloud computing environment - Google Patents
Multi-level multinode version distributed method based on fixed-bandwidth in cloud computing environment Download PDFInfo
- Publication number
- CN105045619B CN105045619B CN201510393438.5A CN201510393438A CN105045619B CN 105045619 B CN105045619 B CN 105045619B CN 201510393438 A CN201510393438 A CN 201510393438A CN 105045619 B CN105045619 B CN 105045619B
- Authority
- CN
- China
- Prior art keywords
- version
- node
- configuration
- distributed
- transmission
- 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.)
- Active
Links
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The present invention relates to a kind of methods for realizing multi-level multinode version distributed in cloud computing environment based on fixed-bandwidth, carry out the definition of version distributed transmission mode, distribution policy and nodal information including development period and are configured；Runtime parses the nodal information of configuration, the distribution policy of version to provide the support to data transmission；The monitoring phase collects the result of version distributed into row information and monitors the Distribution status of nodes at different levels.Using the method for realizing multi-level multinode version distributed in the cloud computing environment of this kind of structure based on fixed-bandwidth, using the version distributed pattern of multi-level multinode, it can be under the premise of existing network bandwidth be made full use of, the strategy issued using classification, application is upgraded, the download time of application upgrade is reduced, promotes the efficiency of upgrading, the influence to production system in upgrading can be reduced simultaneously, enhance the robustness of application and the stability of system；It is more intuitive to the process of version distributed, there is wider application range.
Description
Technical field
The present invention relates to computer enterprise application technologies under computer application technology more particularly to cloud computing environment to lead
A kind of method for realizing multi-level multinode version distributed in domain, in particular to cloud computing environment based on fixed-bandwidth.
Background technology
At present, in industry application and development, unavoidably the application of exploitation is upgraded, is repaired including BUG, iteration
Exploitation function enhancing etc., it is also more and more using the node of deployment under cloud computing environment, between each node by network into
Row interconnects, and the network bandwidth between node is also each identical, using optical network between some nodes, has plenty of gigabit
Net, enterprise also are based on cost consideration, and rental is fixed bandwidth, as 1M, 2M etc..With the increase of machine node, rise
Grade brings a large amount of workload, and with being continuously increased for upgrade package size, net is also brought for the node of dispersion throughout
The challenge of network flow, particularly to having applied for that the enterprise of fixed-bandwidth brings challenge；For the result of multinode version distributed
Monitoring, also brings challenge to operation maintenance personnel.How application is quickly upgraded, while can also reduce to network bandwidth
It occupies, and can Distribution Results be carried out with effective monitoring and compare urgent problems as enterprise.
Under cloud computing environment, the version distributed of enterprise is different according to the degree of enterprise implement informationization, generally use master
Slave pattern or by hand distribution both of which.Principal and subordinate's distribution mode is exactly that main version distributed server is configured in computer room, other
Node pulls down the update action that version carries out version again all from key plate book server；It is distributed as system manager by hand using hand
The mode of work respectively takes version and manual version updating is carried out on each node.Enterprise is to cope with the net that version distributed is brought
The most frequently used practice of network problems of liquid flow is exactly to increase network bandwidth, original bandwidth is upgraded, from several million to tens even
Up to a hundred million, accelerate the transmission speed of version distributed；Simultaneously to reduce influence of the edition upgrading to regular traffic, version distributed
Action usually all carries out after regular traffic stops doing business；Monitoring for Distribution Results, then generally use, which increases input, monitors O＆M
Personnel solve.
Based on current common version distributed scheme, increase network bandwidth and many cost consumptions are brought to enterprise, with
The increase of physical node quantity, cost, which will also be brought, exponentially to be increased, and many pressure is also brought to enterprise operation；It is right
In the monitoring of version distributed, not using the pattern of Centralized Monitoring, it is completely dependent on operation maintenance personnel and passes through to each physical node system
The inquiry of administrator could grasp the distribution situation of version, this increases a large amount of workload to operation maintenance personnel, simultaneously for into
Originally great waste is also resulted in.
Invention content
The shortcomings that the purpose of the present invention is overcoming the above-mentioned prior art, provide one kind can realize making full use of it is existing
The strategy that is issued under the premise of having network bandwidth, using classification, application is upgraded, download time for reducing application upgrade,
It is promoted in the efficiency upgraded, the cloud computing environment with broader applications range and multi-level multinode version is realized based on fixed-bandwidth
The method of this distribution.
To achieve these goals, multi-level multinode version is realized based on fixed-bandwidth in cloud computing environment of the invention
The method of distribution has following form：
The method for realizing multi-level multinode version distributed in the cloud computing environment based on fixed-bandwidth, main feature
It is that the method includes the following steps：
(1) development period, carries out the definition of version distributed transmission mode, distribution policy and nodal information configuration；
(2) runtime parses the nodal information of configuration, the distribution policy of version to provide the branch to data transmission
It holds；
(3) the monitoring phase collects the result of version distributed into row information and monitors the Distribution status of nodes at different levels.
Preferably, the step (1), includes the following steps：
The relevant information of this node is configured in (1-1), including server info, intermediate node information, leaf node information；
The transmission mode of (1-2) configuration version distribution；
The distribution policy of (1-3) configuration version distribution；
The conversation strategy of (1-4) configuration version；
Strategy is sent in (1-5) configuration version publication result.
More preferably, the relevant information that this node is configured, includes the following steps：
(1-1-1) creates the configuration file config.xml of node；
The type of this node is configured in (1-1-2), is divided into master server, intermediate conveyor node, leaf node three types；
The attribute information of this node is configured in (1-1-3), the port information of IP address, opening including this node；
The superior node information of this node is configured in (1-1-4), the port of IP address, opening including this node.
More preferably, the transmission mode of configuration version distribution, includes the following steps：
(1-2-1) is opened and is changed configuration file config.xml；
The procotol of (1-2-2) configuration version distribution, supports HTTP, TCP both of which.
More preferably, the distribution policy of configuration version distribution, includes the following steps：
(1-3-1) is opened and is changed configuration file config.xml；
The transmission of (1-3-2) configuration version sends the size of packet；
Whether the mark of breakpoint transmission is supported in the transmission of (1-3-3) configuration version；
Start the number of thread in the transmission of (1-3-4) configuration version；
The queue size distributed in the transmission of (1-3-5) configuration version；
Retransmission policy during (1-3-6) configuration version error of transmission.
More preferably, the conversation strategy of the configuration version, includes the following steps：
(1-4-1) is opened and is changed configuration file config.xml；
(1-4-2) configuration version warehouse minimum value；
(1-4-3) configuration version warehouse maximum value；
The out-of-service time of version in (1-4-4) configuration version warehouse；
Whether (1-4-5) configuration version warehouse is automatically deleted the mark of legacy version.
More preferably, described configuration version publication result on send strategy, include the following steps：
(1-5-1) is opened and is changed configuration file config.xml；
The server address sent on (1-5-2) configuration version Distribution Results, the port of IP and opening including server
Information；
The network transmission protocol sent on (1-5-3) configuration version Distribution Results, including TCP, HTTP；
The data package size sent in (1-5-4) configuration result；
Retransmission policy when being sent unsuccessfully in (1-5-5) configuration result.
Preferably, the step (2), includes the following steps：
(2-1) parses the configuration information of node；
The network transmission protocol of (2-2) version distributed is realized；
The parsing of (2-3) version distributed strategy；
(2-4) version conversation strategy parses；
(2-5) version distributed result Command Line Parsing；
(2-6) version distributed is to nodes at different levels；
Support is sent in (2-7) version distributed result.
More preferably, the configuration information of the parsing node, includes the following steps：
(2-1-1) opens configuration file config.xml；
(2-1-2) parses the type of node, according to the master server of configuration, intermediate conveyor node, three type of leaf node
Type carries out node type and is handled accordingly；
(2-1-3) parses the attribute information of node, the port information of IP address, opening including this node, if node
Type for master server or intermediate conveyor node, then corresponding agreement transmission can be opened according to the value of configuration and is supported；
(2-1-4) parses the superior node information of node, the port of IP address, opening including this node, if node
Type for intermediate conveyor node or leaf node, then establish the connection with superior node.
More preferably, the network transmission protocol of the version distributed is realized, is included the following steps：
(2-2-1) defines the network transmission protocol interface ITransfer of version distributed；
(2-2-2) realizes interface ITransfer, including being based on TCP and HTTP by the corresponding adapter of protocol definition is used
Two kinds of version transmission mode；
(2-2-3) network transmission protocol supports configuration file transfer.xml definition, according to different protocol configuration phases
Class is realized in the transmission answered.
More preferably, the parsing of the version distributed strategy, includes the following steps：
(2-3-1) opens configuration file config.xml；
(2-3-2) selects corresponding transmission adaptor according to the distribution type of configuration；
(2-3-3) parsing version transmission sends the size of packet, sets in corresponding transmission adaptor attribute；
Whether the mark of breakpoint transmission, setting to corresponding transmission adaptor category are supported in (2-3-4) parsing version transmission
In property；
Start the number of thread in (2-3-5) parsing version transmission, start corresponding thread pool；
(2-3-6) parses the queue size distributed in version transmission, forms version point if node type is master server
The task queue of hair；
(2-3-7) parse version error of transmission when retransmission policy, version distributed when the error occurs by retransmission policy into
The repeating transmission of row data.
More preferably, version conversation strategy parsing, includes the following steps：
(2-4-1) opens configuration file config.xml；
(2-4-2) parsing version warehouse minimum value, and in assignment to the object properties in version warehouse；
(2-4-3) parsing configuration version warehouse maximum value, and in assignment to the object properties in version warehouse；
The out-of-service time of version in (2-4-4) parsing configuration version warehouse, and in assignment to the object properties in version warehouse；
Whether (2-4-5) parsing configuration version warehouse is automatically deleted the mark of legacy version, and assignment is to pair in version warehouse
As in attribute；
(2-4-6) starts the maintenance thread of version repository, and the cleaning operation of version is carried out by the attribute of version repository object.
More preferably, the version distributed result Command Line Parsing, includes the following steps：
(2-5-1) opens configuration file config.xml；
The network transmission protocol sent on (2-5-2) parsing configuration version Distribution Results, including TCP, HTTP, selection is corresponding
Network transmission adapter；
The server address sent on (2-5-3) parsing configuration version Distribution Results, IP's and opening including server
Port information establishes the connection with above sending server；
The data package size sent in (2-5-4) parsing configuration result sets the association attributes of corresponding transmission adaptor；
Retransmission policy when being sent unsuccessfully in (2-5-5) parsing configuration result, send when the error occurs in version distributed result
The repeating transmission of data is carried out by retransmission policy.
More preferably, the version distributed includes the following steps to nodes at different levels：
(2-6-1) opens configuration file config.xml；
(2-6-2) node type is master server or intermediate conveyor node, then by corresponding transmission adaptor and biography
Defeated attribute carries out the data transmission of version；
Distribution queue size in (2-6-3) version distributed according to configuration carries out the flow control of version distributed；
The data packet for carrying out version distributed in (2-6-4) version distributed according to the data package size of configuration controls；
It supports to identify according to the breakpoint transmission of configuration in (2-6-5) version distributed, the corresponding end of transmission data of record
Pointer position.
More preferably, support is sent in the version distributed result, included the following steps：
The server address sent on (2-7-1) parsing configuration version Distribution Results, establishes the connection with above sending server；
(2-7-2) selects different result treatments, if node type is master server, opens according to the type of node
The persistence operation of dynamic Distribution Results；If node type is intermediate transmission node, the distribution of the leaf node received
As a result it is transferred to its superior node；
(2-7-3) is sent when the error occurs according to retransmission policy when being sent unsuccessfully in configuration result in version distributed result
The repeating transmission of data is carried out by retransmission policy.
Preferably, the step (3), includes the following steps：
(3-1) version uploads；
(3-2) version library management, the calcellation of version retract；
(3-3) version is retransmitted；
(3-4) version distributed collection；
(3-5) version distributed result is shown.
More preferably, the version uploads, and includes the following steps：
(3-1-1) prepares the version file uploaded；
(3-1-2) selects the version file to be uploaded by the Browse button of the page；
After the association attributes such as (3-1-3) setting version number, " upload " button is clicked, version file is uploaded to main service
Device；
After (3-1-4) master server receives file, according to the task queue size of configuration, start corresponding thread to version
The distribution of one lower node of this progress；
After (3-1-5) intermediate conveyor node receives file, according to the task queue size of configuration, start corresponding thread pair
Version carries out the distribution of a lower node, the multistage distribution of version is completed, until leaf node；
(3-1-6) leaf node receives the update replacement operation of the laggard style of writing part of version file.
More preferably, the version library management, the calcellation of version retract, and include the following steps：
(3-2-1) is into the maintenance page of version repository；
(3-2-2) is first newest newer patch；
(3-2-3) clicks " calcellation " button and carries out calcellation operation, and the order of calcellation is distributed to master server, is then passed through
Instruction is finally transferred to leaf node by intermediate transmission node, and patch is cancelled；
(3-2-4) clicks " rollback " button and carries out rollback operation, and the order of rollback is distributed to master server, is then passed through
Instruction is finally transferred to leaf node by intermediate transmission node, rollback to last revision.
More preferably, the version is retransmitted, and is included the following steps：
(3-3-1) carries out the monitoring interface of version distributed；
(3-3-2) finds the node of distribution failure, and select according to Distribution status；
(3-3-3) clicks " repeating transmission " button, and version is again sent on the node of failure.
More preferably, the version distributed collection, includes the following steps：
(3-4-1) master server starts the port of collection, receives Distribution Results data, and be persisted to database；
(3-4-2) intermediate conveyor node collects the version distributed of each leaf node as a result, and result is summarized being transferred to
Grade node；
(3-4-3) leaf node is the state transfer of version distributed to its superior node.
More preferably, version distributed result displaying, includes the following steps：
(3-5-1) reads version distributed result from database
The hierarchical relationship that (3-5-2) is uploaded by Distribution Results data loads data into tree structure
(3-5-3) shows the structure tree of node
(3-5-4) clicks the leaf node of structure tree, checks the Distribution Results of node, if distribution failure, can view
Corresponding error message, while repeating transmission operation is carried out to the node of distribution failure by " repeating transmission " button.
The method for realizing multi-level multinode version distributed in the cloud computing environment of the present invention based on fixed-bandwidth, using more
The version distributed pattern of level multinode, can under the premise of existing network bandwidth is made full use of, using the strategy that issues of classification,
Application is upgraded, the download time of application upgrade is reduced, promotes the efficiency of upgrading, while can be reduced in upgrading to production
The influence of system enhances the robustness of application and the stability of system；It, can be more straight by the real time monitoring to Distribution Results
See displaying Distribution status.The present invention provides one kind under cloud environment, quick version distributed is supported, Distribution Results are supervised in real time
Control, running efficiency of system is higher, stable and reliable for performance, while develops that maintenance cost is relatively low, and rapidly adapts to the change of business demand
Change and technique variation.
The method for employing the version distributed of the multi-level multinode based on fixed-bandwidth in the cloud computing environment of the invention,
So that the work to version distributed is more simple and efficient, by the strategy pattern of multistage distribution, net can be effectively saved
Network bandwidth, while by concentrating collection and displaying to version distributed result, the posture of distribution can be grasped in real time, greatly increased
Control and monitoring to version distributed；Meanwhile method using the present invention, it is more intuitive to the process of version distributed, it improves
The efficiency of distribution, efficient and convenient, running efficiency of system is higher, stable and reliable for performance, reduces the cost that exploitation is safeguarded；And increase
Strong system portability and scalability, make user be absorbed in the processing of service logic；Moreover, this method also is able to soon
Speed adapts to variation and the technique variation of business demand, can support and establish high modularization and again the software system of high integration
System, the scope of application is relatively broad, to lay a solid foundation in enterprise's application to the management of version distributed.
Description of the drawings
Fig. 1 is version in the method for the version distributed of the multi-level multinode based on fixed-bandwidth in cloud computing environment of the present invention
The flow chart of this distribution.
Fig. 2 is version in the method for the version distributed of the multi-level multinode based on fixed-bandwidth in cloud computing environment of the present invention
This transmission ITransfer interfaces and the class figure for realizing class.
Fig. 3 is to be saved in the method for the version distributed of the multi-level multinode based on fixed-bandwidth in cloud computing environment of the present invention
Point NodeInfo class figures.
Fig. 4 is version in the method for the version distributed of the multi-level multinode based on fixed-bandwidth in cloud computing environment of the present invention
The physical node deployment mode figure of this distribution.
Specific embodiment
In order to more clearly describe the technology contents of the present invention, carried out with reference to specific embodiment further
Description.
The method application of the version distributed of the multi-level multinode based on fixed-bandwidth in the cloud computing environment of the present invention
In the version distributed specific embodiment based on business function iterative development：Business function is described as realizing specific service logic
Module shows as the resource file of a system, including class file, page file, configuration file etc..
The method of the version distributed of multi-level multinode based on fixed-bandwidth in enterprise's cloud computing environment, including exploitation
Phase realizes the definition of version distributed transmission mode, distribution policy and nodal information configuration；Nodal information of the runtime to configuration, version
This distribution policy is parsed, and provides the support to data transmission；The monitoring phase collects the result of version distributed into row information,
Monitor the Distribution status of nodes at different levels.Development period, realizes that the definition of version distributed transmission mode, distribution policy and nodal information are matched
The operation put, the relevant information including this node is configured, including server info, intermediate node information, leaf node information；Match
Put the transmission mode of version distributed；The distribution policy of configuration version distribution；The conversation strategy of configuration version；Configuration version publication knot
Strategy is sent on fruit.Runtime parses the nodal information of configuration, the distribution policy of version, provides the branch to data transmission
The operation held, the configuration information including parsing node；The network transmission protocol of version distributed is realized；The solution of version distributed strategy
Analysis；Version conversation strategy parses；Version distributed result Command Line Parsing；Version distributed is to nodes at different levels；It is sent in version distributed result
It supports.The monitoring phase is distributed version, and the result of distribution is collected into row information, monitors the behaviour of the Distribution status of nodes at different levels
Make, uploaded including version；Version library management, the calcellation of version retract；Version is retransmitted；Version distributed collection；Version distributed
As a result it shows.
Development period in the embodiment, realizes that version distributed transmission mode defines, distribution policy and nodal information are configured
Operation includes the following steps：
The relevant information of this node is configured in (1-1), including server info, intermediate node information, leaf node information, packet
Include following steps：
(1-1-1) creates the configuration file config.xml of node, and the form of configuration file is as follows：
The type of this node is configured in (1-1-2), is divided into master server, intermediate conveyor node, leaf node three types,
Definition format is as follows：
<Group name=" Default ">
<ConfigValue key=" servertype ">master/medium/leaf</configValue>
</group>
The attribute information of this node is configured in (1-1-3), the port information of IP address, opening including this node：
The superior node information of this node is configured in (1-1-4), the port of IP address, opening including this node：
The transmission mode of (1-2) configuration version distribution, includes the following steps：
(1-2-1) is opened and is changed configuration file config.xml
The procotol of configuration version distribution, supports HTTP, TCP both of which
<Group name=" transfer_info ">
<ConfigValue key=" type ">tcp/http</configValue>
</group>
The distribution policy of (1-2-2) configuration version distribution, includes the following steps：
It opens and changes configuration file config.xml
Configuration version transmission sends the size of packet
Whether the mark of breakpoint transmission is supported in configuration version transmission
Start the number of thread in configuration version transmission
The queue size distributed in configuration version transmission
Retransmission policy during configuration version error of transmission
The form of file is as follows：
The conversation strategy of (1-3) configuration version, includes the following steps：
(1-3-1) is opened and is changed configuration file config.xml；
(1-3-2) configuration version warehouse minimum value；
(1-3-3) configuration version warehouse maximum value；
The out-of-service time of version in (1-3-4) configuration version warehouse；
Whether (1-3-5) configuration version warehouse is automatically deleted the mark of legacy version；
The form of file is as follows：
Strategy is sent in (1-4) configuration version publication result, is included the following steps：
(1-4-1) is opened and is changed configuration file config.xml；
The server address sent on (1-4-2) configuration version Distribution Results, the port of IP and opening including server
Information；
The network transmission protocol sent on (1-4-3) configuration version Distribution Results, including TCP, HTTP；
The data package size sent in (1-4-4) configuration result；
Retransmission policy when being sent unsuccessfully in (1-4-5) configuration result；
The form of file is as follows：
Runtime in the embodiment parses the nodal information of configuration, the distribution policy of version, provides to data
The operation of the support of transmission includes the following steps：
(2-1) parses the configuration information of node, includes the following steps：
(2-1-1) opens configuration file config.xml；
(2-1-2) parses the type of node, according to the master server of configuration, intermediate conveyor node, three type of leaf node
Type carries out node type and is handled accordingly；
(2-1-3) parses the attribute information of node, the port information of IP address, opening including this node, if node
Type for master server or intermediate conveyor node, then corresponding agreement transmission can be opened according to the value of configuration and is supported；
(2-1-4) parses the superior node information of node, the port of IP address, opening including this node, if node
Type for intermediate conveyor node or leaf node, then establish the connection with superior node；
The configuration information of (2-1-5) node forms the class object NodeInfo of node, and class figure is as shown in Figure 1.
The network transmission protocol of (2-2) version distributed is realized, is included the following steps：
(2-2-1) defines the network transmission protocol interface ITransfer of version distributed；
(2-2-2) realizes interface ITransfer, including being based on TCP and HTTP by the corresponding adapter of protocol definition is used
Two kinds of version transmission mode, class figure is as shown in Figure 2；
(2-2-3) network transmission protocol supports configuration file transfer.xml definition, according to different protocol configuration phases
Class is realized in the transmission answered, and form is as follows：
Tcp=com.demo.TCPTransfer
Http=com.demo.HttpTransfer
The parsing of (2-3) version distributed strategy, includes the following steps：
(2-3-1) opens configuration file config.xml；
(2-3-2) selects corresponding transmission adaptor according to the distribution type of configuration；
(2-3-3) parsing version transmission sends the size of packet, sets in corresponding transmission adaptor attribute；
Whether the mark of breakpoint transmission, setting to corresponding transmission adaptor category are supported in (2-3-4) parsing version transmission
In property；
Start the number of thread in (2-3-5) parsing version transmission, start corresponding thread pool；
(2-3-6) parses the queue size distributed in version transmission, forms version point if node type is master server
The task queue of hair；
(2-3-7) parse version error of transmission when retransmission policy, version distributed when the error occurs by retransmission policy into
The repeating transmission of row data；
(2-4) version conversation strategy parses, and includes the following steps：
(2-4-1) opens configuration file config.xml；
(2-4-2) parsing version warehouse minimum value, and in assignment to the object properties in version warehouse；
(2-4-3) parsing configuration version warehouse maximum value, and in assignment to the object properties in version warehouse；
The out-of-service time of version in (2-4-4) parsing configuration version warehouse, and in assignment to the object properties in version warehouse；
Whether (2-4-5) parsing configuration version warehouse is automatically deleted the mark of legacy version, and assignment is to pair in version warehouse
As in attribute；
(2-4-6) starts the maintenance thread of version repository, and the cleaning operation of version is carried out by the attribute of version repository object；
(2-5) version distributed result Command Line Parsing, includes the following steps：
(2-5-1) opens configuration file config.xml；
The network transmission protocol sent on (2-5-2) parsing configuration version Distribution Results, including TCP, HTTP, selection is corresponding
Network transmission adapter；
The server address sent on (2-5-3) parsing configuration version Distribution Results, IP's and opening including server
Port information establishes the connection with above sending server；
The data package size sent in (2-5-4) parsing configuration result sets the association attributes of corresponding transmission adaptor；
Retransmission policy when being sent unsuccessfully in (2-5-5) parsing configuration result, send when the error occurs in version distributed result
The repeating transmission of data is carried out by retransmission policy；
(2-5) version distributed includes the following steps to nodes at different levels：
(2-5-1) opens configuration file config.xml；
(2-5-2) node type is master server or intermediate conveyor node, then by corresponding transmission adaptor and biography
Defeated attribute carries out the data transmission of version；
Distribution queue size in (2-5-3) version distributed according to configuration carries out the flow control of version distributed；
The data packet for carrying out version distributed in (2-5-4) version distributed according to the data package size of configuration controls；
It supports to identify according to the breakpoint transmission of configuration in (2-5-5) version distributed, the corresponding end of transmission data of record
Pointer position；
(2-5-6) version is pushed to each child node from master server, in order to ensure the integrality of version, provides and is based on
The verification mode of MD5, flow chart is as shown in figure 3, physical node deployment mode is as shown in Figure 4.
Support is sent in (2-6) version distributed result, is included the following steps：
The server address sent on (2-6-1) parsing configuration version Distribution Results, establishes the connection with above sending server；
(2-6-2) selects different result treatments, if node type is master server, opens according to the type of node
The persistence operation of dynamic Distribution Results；If node type is intermediate transmission node, the distribution of the leaf node received
As a result it is transferred to its superior node；
(2-6-3) is sent when the error occurs according to retransmission policy when being sent unsuccessfully in configuration result in version distributed result
The repeating transmission of data is carried out by retransmission policy.
(3) the monitoring phase in the embodiment is distributed version, and the result of distribution is collected into row information, monitors sections at different levels
The operation of the Distribution status of point, includes the following steps：
(3-1) version uploads, and includes the following steps：
(3-1-1) prepares the version file uploaded；
(3-1-2) selects the version file to be uploaded by the Browse button of the page；
After the association attributes such as (3-1-3) setting version number, " upload " button is clicked, version file is uploaded to main service
Device；
After (3-1-4) master server receives file, according to the task queue size of configuration, start corresponding thread to version
The distribution of one lower node of this progress；
After (3-1-5) intermediate conveyor node receives file, according to the task queue size of configuration, start corresponding thread pair
Version carries out the distribution of a lower node, the multistage distribution of version is completed, until leaf node；
(3-1-6) leaf node receives the update replacement operation of the laggard style of writing part of version file.
(3-2) version library management, the calcellation of version retract, and include the following steps：
(3-2-1) is into the maintenance page of version repository；
(3-2-2) is first newest newer patch；
(3-2-3) clicks " calcellation " button and carries out calcellation operation, and the order of calcellation is distributed to master server, is then passed through
Instruction is finally transferred to leaf node by intermediate transmission node, and patch is cancelled；
(3-2-4) clicks " rollback " button and carries out rollback operation, and the order of rollback is distributed to master server, is then passed through
Instruction is finally transferred to leaf node by intermediate transmission node, rollback to last revision.
(3-3) version is retransmitted, and is included the following steps：
(3-3-1) carries out the monitoring interface of version distributed；
(3-3-2) finds the node of distribution failure, and select according to Distribution status；
(3-3-3) clicks " repeating transmission " button, and version is again sent on the node of failure.
(3-4) version distributed collection, includes the following steps：
(3-4-1) master server starts the port of collection, receives Distribution Results data, and be persisted to database；
(3-4-2) intermediate conveyor node collects the version distributed of each leaf node as a result, and result is summarized being transferred to
Grade node；
(3-4-3) leaf node is the state transfer of version distributed to its superior node.
(3-5) version distributed result is shown, is included the following steps：
(3-5-1) reads version distributed result from database；
The hierarchical relationship that (3-5-2) is uploaded by Distribution Results data loads data into tree structure；
(3-5-3) shows the structure tree of node；
(3-5-4) clicks the leaf node of structure tree, checks the Distribution Results of node, if distribution failure, can view
Corresponding error message, while repeating transmission operation is carried out to the node of distribution failure by " repeating transmission " button.
By above step, the version of the multi-level multinode based on fixed-bandwidth in the cloud computing environment of the invention is employed
The method of this distribution so that the work to version distributed is more simple and efficient, passes through the strategy pattern of multistage distribution, energy
Network bandwidth is effectively saved, while by concentrating collection and displaying to version distributed result, distribution can be grasped in real time
Posture considerably increases the control and monitoring to version distributed；Meanwhile method using the present invention, to the process of version distributed more
Add intuitively, improve the efficiency of distribution, efficient and convenient, running efficiency of system is higher, stable and reliable for performance, reduces exploitation and safeguards
Cost；And system portability and scalability are enhanced, user is made to be absorbed in the processing of service logic；Moreover,
This method also is able to rapidly adapt to variation and the technique variation of business demand, can support and establish high modularization and again height
The software systems of integration, the scope of application is relatively broad, to lay a solid foundation in enterprise's application to the management of version distributed.
In this description, the present invention is described with reference to its specific embodiment.But it is clear that it can still make
Various modifications and alterations are without departing from the spirit and scope of the invention.Therefore, the description and the appended drawings should be considered as illustrative
And not restrictive.
Claims (19)
1. the method for multi-level multinode version distributed is realized in a kind of cloud computing environment based on fixed-bandwidth, which is characterized in that
The method includes the following steps：
(1) development period, carries out the definition of version distributed transmission mode, distribution policy and nodal information configuration；
(2) runtime parses the nodal information of configuration, the distribution policy of version to provide the support to data transmission；
(3) the monitoring phase collects the result of version distributed into row information and monitors the Distribution status of nodes at different levels；
The step (1), includes the following steps：
The relevant information of this node is configured in (1-1), including server info, intermediate node information, leaf node information；
The transmission mode of (1-2) configuration version distribution；
The distribution policy of (1-3) configuration version distribution；
The conversation strategy of (1-4) configuration version；
Strategy is sent in (1-5) configuration version publication result；
The relevant information that this node is configured, includes the following steps：
(1-1-1) creates the configuration file config.xml of node；
The type of this node is configured in (1-1-2), is divided into master server, intermediate conveyor node, leaf node three types；
The attribute information of this node is configured in (1-1-3), the port information of IP address, opening including this node；
The superior node information of this node is configured in (1-1-4), the port of IP address, opening including this node.
2. the side of multi-level multinode version distributed is realized in cloud computing environment according to claim 1 based on fixed-bandwidth
Method, which is characterized in that the transmission mode of the configuration version distribution includes the following steps：
(1-2-1) is opened and is changed configuration file config.xml；
The procotol of (1-2-2) configuration version distribution, supports HTTP, TCP both of which.
3. the side of multi-level multinode version distributed is realized in cloud computing environment according to claim 1 based on fixed-bandwidth
Method, which is characterized in that the distribution policy of the configuration version distribution includes the following steps：
(1-3-1) is opened and is changed configuration file config.xml；
The transmission of (1-3-2) configuration version sends the size of packet；
Whether the mark of breakpoint transmission is supported in the transmission of (1-3-3) configuration version；
Start the number of thread in the transmission of (1-3-4) configuration version；
The queue size distributed in the transmission of (1-3-5) configuration version；
Retransmission policy during (1-3-6) configuration version error of transmission.
4. the side of multi-level multinode version distributed is realized in cloud computing environment according to claim 1 based on fixed-bandwidth
Method, which is characterized in that the conversation strategy of the configuration version includes the following steps：
(1-4-1) is opened and is changed configuration file config.xml；
(1-4-2) configuration version warehouse minimum value；
(1-4-3) configuration version warehouse maximum value；
The out-of-service time of version in (1-4-4) configuration version warehouse；
Whether (1-4-5) configuration version warehouse is automatically deleted the mark of legacy version.
5. the side of multi-level multinode version distributed is realized in cloud computing environment according to claim 1 based on fixed-bandwidth
Method, which is characterized in that send strategy in the configuration version publication result, include the following steps：
(1-5-1) is opened and is changed configuration file config.xml；
The server address sent on (1-5-2) configuration version Distribution Results, the port information of IP and opening including server；
The network transmission protocol sent on (1-5-3) configuration version Distribution Results, including TCP, HTTP；
The data package size sent in (1-5-4) configuration result；
Retransmission policy when being sent unsuccessfully in (1-5-5) configuration result.
6. the side of multi-level multinode version distributed is realized in cloud computing environment according to claim 1 based on fixed-bandwidth
Method, which is characterized in that the step (2) includes the following steps：
(2-1) parses the configuration information of node；
The network transmission protocol of (2-2) version distributed is realized；
The parsing of (2-3) version distributed strategy；
(2-4) version conversation strategy parses；
(2-5) version distributed result Command Line Parsing；
(2-6) version distributed is to nodes at different levels；
Support is sent in (2-7) version distributed result.
7. the side of multi-level multinode version distributed is realized in cloud computing environment according to claim 6 based on fixed-bandwidth
Method, which is characterized in that the configuration information of the parsing node includes the following steps：
(2-1-1) opens configuration file config.xml；
(2-1-2) parses the type of node, according to the master server of configuration, intermediate conveyor node, leaf node three types, into
Row node type is handled accordingly；
(2-1-3) parses the attribute information of node, the port information of IP address, opening including this node, if the class of node
Type is master server or intermediate conveyor node, then corresponding agreement transmission can be opened according to the value of configuration and is supported；
(2-1-4) parses the superior node information of node, the port of IP address, opening including this node, if the class of node
Type is intermediate conveyor node or leaf node, then establishes the connection with superior node.
8. the side of multi-level multinode version distributed is realized in cloud computing environment according to claim 6 based on fixed-bandwidth
Method, which is characterized in that the network transmission protocol of the version distributed is realized, is included the following steps：
(2-2-1) defines the network transmission protocol interface ITransfer of version distributed；
(2-2-2) realizes interface ITransfer, including two based on TCP and HTTP by the corresponding adapter of protocol definition is used
Kind version transmission mode；
(2-2-3) network transmission protocol supports configuration file transfer.xml definition, corresponding according to different protocol configurations
Class is realized in transmission.
9. the side of multi-level multinode version distributed is realized in cloud computing environment according to claim 6 based on fixed-bandwidth
Method, which is characterized in that the parsing of the version distributed strategy includes the following steps：
(2-3-1) opens configuration file config.xml；
(2-3-2) selects corresponding transmission adaptor according to the distribution type of configuration；
(2-3-3) parsing version transmission sends the size of packet, sets in corresponding transmission adaptor attribute；
The mark of breakpoint transmission whether is supported in (2-3-4) parsing version transmission, is set in corresponding transmission adaptor attribute；
Start the number of thread in (2-3-5) parsing version transmission, start corresponding thread pool；
(2-3-6) parses the queue size distributed in version transmission, forms version distributed if node type is master server
Task queue；
(2-3-7) parses retransmission policy during version error of transmission, and retransmission policy is pressed when the error occurs into line number in version distributed
According to repeating transmission.
10. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 6
Method, which is characterized in that the version conversation strategy parsing includes the following steps：
(2-4-1) opens configuration file config.xml；
(2-4-2) parsing version warehouse minimum value, and in assignment to the object properties in version warehouse；
(2-4-3) parsing configuration version warehouse maximum value, and in assignment to the object properties in version warehouse；
The out-of-service time of version in (2-4-4) parsing configuration version warehouse, and in assignment to the object properties in version warehouse；
Whether (2-4-5) parsing configuration version warehouse is automatically deleted the mark of legacy version, and assignment is to the object category in version warehouse
In property；
(2-4-6) starts the maintenance thread of version repository, and the cleaning operation of version is carried out by the attribute of version repository object.
11. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 6
Method, which is characterized in that the version distributed result Command Line Parsing includes the following steps：
(2-5-1) opens configuration file config.xml；
The network transmission protocol sent on (2-5-2) parsing configuration version Distribution Results, including TCP, HTTP, selects corresponding network
Transmission adaptor；
The server address sent on (2-5-3) parsing configuration version Distribution Results, the port of IP and opening including server
Information establishes the connection with above sending server；
The data package size sent in (2-5-4) parsing configuration result sets the association attributes of corresponding transmission adaptor；
Retransmission policy when being sent unsuccessfully in (2-5-5) parsing configuration result, send when the error occurs in version distributed result by weight
Hair strategy carries out the repeating transmission of data.
12. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 6
Method, which is characterized in that the version distributed includes the following steps to nodes at different levels：
(2-6-1) opens configuration file config.xml；
(2-6-2) node type is master server or intermediate conveyor node, then belongs to by corresponding transmission adaptor and transmission
Property carry out version data transmission；
Distribution queue size in (2-6-3) version distributed according to configuration carries out the flow control of version distributed；
The data packet for carrying out version distributed in (2-6-4) version distributed according to the data package size of configuration controls；
It supports to identify according to the breakpoint transmission of configuration in (2-6-5) version distributed, the finger of the corresponding end of transmission data of record
Pin position.
13. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 6
Method, which is characterized in that send support in the version distributed result, include the following steps：
The server address sent on (2-7-1) parsing configuration version Distribution Results, establishes the connection with above sending server；
(2-7-2) selects different result treatments, if node type is master server, starts and divide according to the type of node
Send out the persistence operation of result；If node type is intermediate transmission node, the Distribution Results of the leaf node received
It is transferred to its superior node；
(2-7-3) is sent when the error occurs by weight according to retransmission policy when being sent unsuccessfully in configuration result in version distributed result
Hair strategy carries out the repeating transmission of data.
14. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 1
Method, which is characterized in that the step (3) includes the following steps：
(3-1) version uploads；
(3-2) version library management, the calcellation of version retract；
(3-3) version is retransmitted；
(3-4) version distributed collection；
(3-5) version distributed result is shown.
15. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 14
Method, which is characterized in that the version uploads, and includes the following steps：
(3-1-1) prepares the version file uploaded；
(3-1-2) selects the version file to be uploaded by the Browse button of the page；
After the association attributes such as (3-1-3) setting version number, " upload " button is clicked, version file is uploaded to master server；
After (3-1-4) master server receives file, according to the task queue size of configuration, start corresponding thread to version into
The distribution of one lower node of row；
After (3-1-5) intermediate conveyor node receives file, according to the task queue size of configuration, start corresponding thread to version
The distribution of a lower node is carried out, the multistage distribution of version is completed, until leaf node；
(3-1-6) leaf node receives the update replacement operation of the laggard style of writing part of version file.
16. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 14
Method, which is characterized in that the version library management, the calcellation of version retract, and include the following steps：
(3-2-1) is into the maintenance page of version repository；
(3-2-2) is first newest newer patch；
(3-2-3) clicks " calcellation " button and carries out calcellation operation, and the order of calcellation is distributed to master server, then passes through centre
Instruction is finally transferred to leaf node by transmission node, and patch is cancelled；
(3-2-4) clicks " rollback " button and carries out rollback operation, and the order of rollback is distributed to master server, then passes through centre
Instruction is finally transferred to leaf node by transmission node, rollback to last revision.
17. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 14
Method, which is characterized in that the version is retransmitted, and is included the following steps：
(3-3-1) carries out the monitoring interface of version distributed；
(3-3-2) finds the node of distribution failure, and select according to Distribution status；
(3-3-3) clicks " repeating transmission " button, and version is again sent on the node of failure.
18. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 14
Method, which is characterized in that the version distributed collection includes the following steps：
(3-4-1) master server starts the port of collection, receives Distribution Results data, and be persisted to database；
(3-4-2) intermediate conveyor node collects the version distributed of each leaf node as a result, and result is summarized being transferred to higher level's section
Point；
(3-4-3) leaf node is the state transfer of version distributed to its superior node.
19. multi-level multinode version distributed is realized based on fixed-bandwidth in cloud computing environment according to claim 14
Method, which is characterized in that the version distributed result displaying includes the following steps：
(3-5-1) reads version distributed result from database
The hierarchical relationship that (3-5-2) is uploaded by Distribution Results data loads data into tree structure
(3-5-3) shows the structure tree of node
(3-5-4) clicks the leaf node of structure tree, checks the Distribution Results of node, if distribution failure, can view corresponding
Error message, while by " repeating transmission " button to distribution failure node carry out repeating transmission operation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510393438.5A CN105045619B (en) | 2015-07-06 | 2015-07-06 | Multi-level multinode version distributed method based on fixed-bandwidth in cloud computing environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510393438.5A CN105045619B (en) | 2015-07-06 | 2015-07-06 | Multi-level multinode version distributed method based on fixed-bandwidth in cloud computing environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105045619A CN105045619A (en) | 2015-11-11 |
| CN105045619B true CN105045619B (en) | 2018-07-10 |
Family
ID=54452183
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510393438.5A Active CN105045619B (en) | 2015-07-06 | 2015-07-06 | Multi-level multinode version distributed method based on fixed-bandwidth in cloud computing environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105045619B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107426298A (en) * | 2017-06-16 | 2017-12-01 | 中铁程科技有限责任公司 | Railway dissemination system processing method and railway dissemination system |
| CN107766508B (en) * | 2017-10-23 | 2021-06-15 | 深圳市中润四方信息技术有限公司 | Method and system for collecting and distributing data files |
| CN110545450B (en) * | 2019-09-09 | 2021-12-03 | 深圳市网心科技有限公司 | Node distribution method, system, electronic equipment and storage medium |
| CN115525302B (en) * | 2022-09-23 | 2023-06-09 | 北京大学 | Deployment method and device for large-scale digital object warehouse cluster |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102385633A (en) * | 2011-12-13 | 2012-03-21 | 方正国际软件有限公司 | File management system using virtual storage directory |
| CN102436373A (en) * | 2011-09-13 | 2012-05-02 | 上海普元信息技术股份有限公司 | Method for realizing resource loading and resource hot-updating in distributed enterprise application system |
| CN102546839A (en) * | 2012-03-25 | 2012-07-04 | 沈阳通用软件有限公司 | Efficient and reliable software distribution method for large scale network |
| CN103051469A (en) * | 2012-09-13 | 2013-04-17 | 曙光信息产业(北京)有限公司 | Centralized configuration management method under cloud environment |
| CN103150304A (en) * | 2011-12-06 | 2013-06-12 | 郑红云 | Cloud database system |
| CN103647830A (en) * | 2013-12-13 | 2014-03-19 | 浪潮电子信息产业股份有限公司 | Dynamic management method for multilevel configuration files in cluster management system |
| CN103778031A (en) * | 2014-01-15 | 2014-05-07 | 华中科技大学 | Distributed system multilevel fault tolerance method under cloud environment |
| CN104184820A (en) * | 2014-08-29 | 2014-12-03 | 城云科技（杭州）有限公司 | Customized template cloud platform dynamic spread deploying method applied under distributed environment |
| CN104391723A (en) * | 2014-12-03 | 2015-03-04 | 山东中创软件工程股份有限公司 | Model packaging and arranging method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9396040B2 (en) * | 2010-12-27 | 2016-07-19 | Nokia Technologies Oy | Method and apparatus for providing multi-level distributed computations |
-
2015
- 2015-07-06 CN CN201510393438.5A patent/CN105045619B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102436373A (en) * | 2011-09-13 | 2012-05-02 | 上海普元信息技术股份有限公司 | Method for realizing resource loading and resource hot-updating in distributed enterprise application system |
| CN103150304A (en) * | 2011-12-06 | 2013-06-12 | 郑红云 | Cloud database system |
| CN102385633A (en) * | 2011-12-13 | 2012-03-21 | 方正国际软件有限公司 | File management system using virtual storage directory |
| CN102546839A (en) * | 2012-03-25 | 2012-07-04 | 沈阳通用软件有限公司 | Efficient and reliable software distribution method for large scale network |
| CN103051469A (en) * | 2012-09-13 | 2013-04-17 | 曙光信息产业(北京)有限公司 | Centralized configuration management method under cloud environment |
| CN103647830A (en) * | 2013-12-13 | 2014-03-19 | 浪潮电子信息产业股份有限公司 | Dynamic management method for multilevel configuration files in cluster management system |
| CN103778031A (en) * | 2014-01-15 | 2014-05-07 | 华中科技大学 | Distributed system multilevel fault tolerance method under cloud environment |
| CN104184820A (en) * | 2014-08-29 | 2014-12-03 | 城云科技（杭州）有限公司 | Customized template cloud platform dynamic spread deploying method applied under distributed environment |
| CN104391723A (en) * | 2014-12-03 | 2015-03-04 | 山东中创软件工程股份有限公司 | Model packaging and arranging method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105045619A (en) | 2015-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105045619B (en) | Multi-level multinode version distributed method based on fixed-bandwidth in cloud computing environment | |
| CN101799751B (en) | Method for building monitoring agent software of host machine | |
| CN110019651A (en) | A kind of streaming regulation engine and business data processing method | |
| CN106407076A (en) | A monitoring method for the operation information of software and hardware based on a domestic CPU and operating system environment | |
| WO2012088905A1 (en) | Polling sub-system and polling method for communication network system and communication apparatus | |
| CN102404381A (en) | Software deployment system and deployment method based on workflow in cloud computing environment | |
| CN104394211A (en) | Hadoop-based user behavior analysis system design and implementation method | |
| CN104572290A (en) | Method and device for controlling message processing threads | |
| WO2020062674A1 (en) | Push method for update data packets and server | |
| CN102325061B (en) | Network monitoring method, equipment and system | |
| CN103034658A (en) | Method and system for querying data and exporting report | |
| CN104753885A (en) | Traffic sheet matching method and device and OpenFlow exchange system | |
| CN107992392A (en) | A kind of automatic monitoring repair system and method for cloud rendering system | |
| CN109614110A (en) | A kind of method and apparatus that message-oriented middleware concentrates deployment | |
| CN103257852B (en) | The method and apparatus that a kind of development environment of distribution application system is built | |
| CN103647817A (en) | Application uploading method | |
| CN109117341A (en) | A kind of monitoring method of virtual machine, device, equipment and medium | |
| CN105490864A (en) | Business module monitoring method based on OSGI | |
| CN100346609C (en) | Configurating data collecting system and its method in network management | |
| CN107807854A (en) | The method and rendering task processing method of a kind of Automatic dispatching Node station | |
| CN109905263A (en) | A kind of automation O&M deployment system | |
| CN105099774B (en) | A kind of router software upgrade method and system | |
| CN108399095B (en) | Method, system, device and storage medium for supporting dynamic management of timed tasks | |
| CN109189431A (en) | A kind of client side upgrading method, device, equipment and readable storage medium storing program for executing | |
| CN102148702B (en) | Method for managing network by utilizing network configuration protocol |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |