CN107659458A - Agent deployment upgrade methods and system based on git Version Controls - Google Patents
Agent deployment upgrade methods and system based on git Version Controls Download PDFInfo
- Publication number
- CN107659458A CN107659458A CN201711063697.7A CN201711063697A CN107659458A CN 107659458 A CN107659458 A CN 107659458A CN 201711063697 A CN201711063697 A CN 201711063697A CN 107659458 A CN107659458 A CN 107659458A
- Authority
- CN
- China
- Prior art keywords
- agent
- deployment
- version
- git
- destination server
- 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.)
- Granted
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/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present invention relates to the deployment upgrade methods of the Agent based on git Version Controls and system, this method includes Agent configuration admin services end component and Git warehouses being deployed to destination server and each self-starting；Agent Daemon serviced components are disposed to destination server；Agent deployment packages are uploaded into Git warehouses and configure Agent deployment strategys；For Agent Daemon serviced component synchronization Agent deployment strategys, and perform command operation corresponding to Agent deployment strategys.This invention simplifies deployment configuration difficulty, realizes the quick rollback of version, and deployment package is separated with configuration file, utilizes Git version mechanisms, there is provided a kind of easy configuration updating and management mechanism, avoids introducing complicated configuration management system.
Description
Technical field
The present invention relates to Agent to dispose upgrade method, more specifically refers to the Agent deployment based on git Version Controls
Upgrade method and system.
Background technology
Traditional computing system is closing, to meet the requirement of uniformity, but social mechanism is open, it is impossible to full
Sufficient condition for consistence, some individuals under this mechanism are in the case of contradiction, it is necessary to reach one by certain negotiation mechanism
Acceptable solution, this this individual calculated in society are referred to as Agent, and these individual organic assemblings, which are then formed, calculates society
Meeting -- Agent system, i.e. Agent refer to reside under a certain environment, can continue independently to play a role, possess presence,
The computational entity of the feature such as reactive, social, initiative.
With the development of Internet advertising distribution technology, increasing system uses Agent architecture design, it is therefore desirable to
Multiple Agent (such as monitoring Agent, deployment Agent, naming Agent, log collection Agent) are deployed to every service
It is also little with pssh, ansible, fabric etc instrument craft installation question if company's machine amount is fewer on device,
But after company's machine amount is more, by hand installation, upgrading, rollback Agent will be pretty troublesome things.At present for deployment and
Speech, using two ways, first, the deployment of batch can also be realized by writing script using ansible etc., by writing Agent peaces
Script is filled, specifies destination server IP address, push installation script performs installation to destination server；The program can also simultaneously
Configuration file is individually pushed to destination server, but deployment is required for the information such as configuration server address, account every time, configures
More troublesome, it is difficult the IP address for knowing server in time that especially the virtual machine of current popular, container, which create server mode,
Etc. information, it is impossible to which Agent deployable state is monitored in real time；And lacking the management of version, renewal every time is required for repairing
Change installation script, rollback efficiency is low；Second, Agent is bundled into mirror image to realize deployment when empty machine creates, but it is this
Mode does not consider the situation of Agent edition upgradings, and it is different to be likely to configuration when Agent is deployed to different servers,
The Agent configurations that manual entry enters to change every are also needed to after the startup of empty machine.
Therefore, it is necessary to design a kind of Agent deployment upgrade methods based on git Version Controls, realization simplifies batch
Deployment configuration difficulty, the quick rollback of version is realized, avoid introducing complicated configuration management system, deployment is simple.
The content of the invention
The defects of it is an object of the invention to overcome prior art, there is provided the Agent deployment upgradings based on git Version Controls
Method and system.
To achieve the above object, the present invention uses following technical scheme：Agent deployment upgradings based on git Version Controls
Method, methods described include：
Agent configuration admin services end component and Git warehouses are deployed to destination server and each self-starting；
Agent Daemon serviced components are disposed to destination server；
Agent deployment packages are uploaded into Git warehouses and configure Agent deployment strategys；
For Agent Daemon serviced component synchronization Agent deployment strategys, and perform and ordered corresponding to Agent deployment strategys
Order operation.
Its further technical scheme is：Agent deployment packages are uploaded into Git warehouses and configure the step of Agent deployment strategys
Suddenly, including in detail below step：
Obtain the Agent deployment packages for needing to dispose and corresponding configuration file；
Agent deployment packages and corresponding configuration file are committed to Git warehouses；
Destination server address is reported, and destination server is grouped；
Every group of destination server is set to need the Agent version informations disposed；
Agent operation command is set.
Its further technical scheme is：For Agent Daemon serviced component synchronization Agent deployment strategys, and perform
Corresponding to Agent deployment strategys the step of command operation, including step in detail below：
Agent Daemon serviced component synchronization Agent deployment strategys；
Obtain the Agent version informations that destination server needs to dispose；
Judge whether Agent version informations and the Agent versions that destination server is currently disposed are consistent；
If so, then updating configuration file corresponding to Agent deployment packages, and upload Agent deployable states；
If it is not, then whether judged by Git version management mechanisms in destination server comprising the Agent versions for needing to dispose
This information；
If having included, the Agent versions that destination server is currently disposed are switched to the Agent versions for needing to dispose,
And into the step of updating Agent deployment packages and corresponding configuration file, and upload Agent deployable states；
If not including, the Agent versions for needing to dispose are downloaded from Git warehouses, and are entered destination server is current
The Agent versions of deployment switch to the step of Agent versions for needing to dispose.
Its further technical scheme is：Configuration file corresponding to Agent deployment packages is updated, and uploads Agent deployable states
The step of, including step in detail below：
Obtain the version information of configuration file corresponding to Agent deployment packages；
Judge whether the version information of configuration file is consistent with the configuration file version information that destination server is current；
If so, then upload Agent deployable states；
If it is not, then whether judged by Git version management mechanisms in destination server comprising the Agent portions for needing to dispose
The version of the corresponding configuration file of administration's bag；
If having included, the version of destination server current configuration file is switched to the Agent deployment packages for needing to dispose
The version information of corresponding configuration file, and enter the step of uploading Agent deployable states；
If not including, the Agent deployment packages that being downloaded from Git warehouses needs to dispose correspond to the version letter of configuration file
Breath, and enter the step of uploading Agent deployable states.
Present invention also offers based on git Version Controls Agent dispose upgrade-system, including component processing unit,
Agent Daemon processing units, deployment package processing unit and deployment unit；
The component processing unit, for Agent configuration admin services end component and Git warehouses to be deployed into destination service
Device and each self-starting；
The Agent Daemon processing units, for disposing Agent Daemon serviced components to destination server；
The deployment package processing unit, for Agent deployment packages to be uploaded into Git warehouses and configure Agent deployment strategys；
The deployment unit, for for Agent Daemon serviced component synchronization Agent deployment strategys, and perform
Command operation corresponding to Agent deployment strategys.
Its further technical scheme is：The deployment package processing unit is including on data acquisition module, submission module, address
Report module, version information setup module and order setup module；
The data acquisition module, for obtaining the Agent deployment packages for needing to dispose and corresponding configuration file；
The submission module, for Agent deployment packages and corresponding configuration file to be committed into Git warehouses；
The address reporting module, is grouped for reporting destination server address, and to destination server；
The version information setup module, the Agent version informations disposed for setting every group of destination server to need；
The order setup module, for setting Agent operation command.
Its further technical scheme is：The deployment unit include synchronization module, Agent version informations acquisition module,
Agent versions judge module, update module, Agent version existence judge module, Agent versions handover module and Agent
Version download module；
The synchronization module, for Agent Daemon serviced component synchronization Agent deployment strategys；
The Agent version informations acquisition module, the Agent version informations disposed for obtaining destination server to need；
The Agent versions judge module, currently dispose for judging Agent version informations and destination server
Whether Agent versions are consistent；
The update module, for if so, then configuration file corresponding to renewal Agent deployment packages, and upload Agent deployment
State；
The Agent versions existence judge module, for if it is not, then judging that target takes by Git version management mechanisms
Whether comprising the Agent version informations for needing to dispose in business device；
The Agent versions handover module, if for having included, Agent versions that destination server is currently disposed
Switch to the Agent versions for needing to dispose；
The Agent versions download module, if for not including, the Agent versions for needing to dispose are downloaded from Git warehouses
This.
Its further technical scheme is：The update module includes FileVersion acquisition submodule, FileVersion judges son
Module, state are uploaded under submodule, FileVersion existence judging submodule, FileVersion switching submodule and FileVersion
Carrier module；
The FileVersion acquisition submodule, for obtaining the version information of configuration file corresponding to Agent deployment packages；
The FileVersion judging submodule, for judging whether the version information of configuration file is current with destination server
Configuration file version information it is consistent；
The state uploads submodule, for if so, then uploading Agent deployable states；
The FileVersion existence judging submodule, for if it is not, then judging that target takes by Git version management mechanisms
Whether the version of configuration file has been corresponded to comprising the Agent deployment packages for needing to dispose in business device；
The FileVersion switching submodule, if for having included, by the version of destination server current configuration file
The Agent deployment packages that switching to needs to dispose correspond to the version information of configuration file；
The FileVersion downloads submodule, if for not including, the Agent for needing to dispose is downloaded from Git warehouses
Deployment package corresponds to the version information of configuration file.
Compared with the prior art, the invention has the advantages that：The deployment of the Agent based on git Version Controls of the present invention rises
Level method, it is automatic to find target clothes by using Agent configuration admin services end component and Agent Daemon serviced components
Business device IP and title, simplify deployment configuration difficulty, Agent Daemon serviced components are easy to all kinds of of monitoring objective server
Agent deployable states, using the Git warehouses version management mechanism of itself, the quick rollback of version is realized, and by deployment package with matching somebody with somebody
File separation is put, utilizes Git version mechanisms, there is provided a kind of easy configuration updating and management mechanism, avoids introducing complicated match somebody with somebody
Put management system.
The invention will be further described with specific embodiment below in conjunction with the accompanying drawings.
Brief description of the drawings
Fig. 1 is the flow chart that the Agent based on git Version Controls that the specific embodiment of the invention provides disposes upgrade method
One；
Fig. 2 is the flow chart that the Agent based on git Version Controls that the specific embodiment of the invention provides disposes upgrade method
Two；
Fig. 3 is specific embodiment of the invention offer Agent deployment packages are uploaded into Git warehouses and configure Agent deployment
The flow chart of strategy；
Fig. 4 is directed to Agent Daemon serviced component synchronization Agent deployment strategys for what the specific embodiment of the invention provided
And perform the flow chart of command operation corresponding to Agent deployment strategys；
Fig. 5 is configuration file corresponding to the renewal Agent deployment packages of specific embodiment of the invention offer and uploads Agent portions
The flow chart of administration's state；
Fig. 6 is the structural frames that the Agent based on git Version Controls that the specific embodiment of the invention provides disposes upgrade-system
Figure；
Fig. 7 is the structured flowchart for the deployment package processing unit that the specific embodiment of the invention provides；
Fig. 8 is the structured flowchart for the deployment unit that the specific embodiment of the invention provides；
Fig. 9 is the structured flowchart for the update module that the specific embodiment of the invention provides.
Embodiment
In order to more fully understand the technology contents of the present invention, technical scheme is entered with reference to specific embodiment
One step introduction and explanation, but it is not limited to this.
Specific embodiment as shown in Fig. 1~9, the deployment upgradings of the Agent based on git Version Controls that the present embodiment provides
Method, it can be used in zabbix-agent batch deployment and escalation process, realization simplifies batch deployment configuration difficulty,
The quick rollback of version is realized, avoids introducing complicated configuration management system, deployment is simple.
As shown in figure 1, present embodiments provide the Agent deployment upgrade methods based on git Version Controls, this method bag
Include：
S1, Agent configuration admin services end component and Git warehouses be deployed to destination server and each self-starting；
S2, Agent Daemon serviced components are disposed to destination server；
S3, Agent deployment packages are uploaded into Git warehouses and configure Agent deployment strategys；
S4, for Agent Daemon serviced component synchronization Agent deployment strategys, and it is corresponding to perform Agent deployment strategys
Command operation.
For above-mentioned S1 steps, Agent configuration admin services end component is responsible for the strategy setting of Agent deployment, monitoring
The deployable state of each server, manage Agent configuration information；Git warehouses mainly store Agent deployment packages and configuration file,
Version management is provided to support；Agent configuration admin services end component and Git warehouses are deployed to destination server and each opened
It is dynamic, destination server can be caused to possess the function in Agent configuration admin services end component and Git warehouses, deployment when
Wait, not comprising any configuration data, Git warehouses are also empty.
In addition, above-mentioned S2 steps, specifically dispose Agent Daemon on the destination server for needing to dispose Agent
Serviced component.Agent Daemon serviced components are deployed on each destination server, are responsible for synchronous deployment strategy and according to plan
The operation such as all kinds of Agent of the machine deployment, upgrading is slightly performed, and is serviced where being reported to Agent configuration admin services end component
Device Agent deployable state；Agent Daemon serviced components typically seldom change, and can be bundled into virtual machine image, this
Sample has got well Daemon services with regard to deployment automatically when virtual machine is newly created, and can configure Daemon start automatic starts, open
After dynamic Daemon programs by report automatically book server IP address and server name to Agent configuration admin services end group
Part.Using Agent patterns, server ip and title can be found automatically, deployment configuration difficulty is simplified, especially in server
Advantage is more highlighted when quantity is more；Agent Daemon serviced components can more facilitate all kinds of Agent portions of monitoring the machine simultaneously
Administration's state, deployment process are simple.
Further, in certain embodiments, above-mentioned S4 steps, Agent deployment packages is uploaded into Git warehouses and matched somebody with somebody
The step of putting Agent deployment strategys, including step in detail below：
S41, obtain the Agent deployment packages for needing to dispose and corresponding configuration file；
S42, Agent deployment packages and corresponding configuration file be committed to Git warehouses；
S43, destination server address is reported, and destination server is grouped；
S44, every group of destination server is set to need the Agent version informations disposed；
S45, the operation command that Agent is set.
For above-mentioned S41 steps to S42 steps, the Agent deployment packages for first disposing needs and corresponding configuration file
Git warehouses are submitted to by Git instruments, in order to realize version management using Git mechanism auxiliary, include storage, the version of version
This renewal, the comparison of version, this switching etc., if not having to Git, directly replace Git warehouses using file storage service
Agent deployment upgrading can be realized, but change version is required for voluntarily realizing the replacement operation of file every time.
For above-mentioned S43 steps to S45 steps, according to the destination server address reported automatically, by destination server
It is grouped, setting every group of destination server to need the Agent version informations disposed, (version information includes title, Agent versions
Number, deployment package Git addresses, corresponding profile address, configuration file version, the account of operation, the destination path etc. of deployment
Attribute), and Agent operation command (start/stop/none) is set.
Further, in certain embodiments, above-mentioned S5 steps, it is synchronous for Agent Daemon serviced components
Agent deployment strategys, and the step of perform command operation corresponding to Agent deployment strategys, including step in detail below：
S51, Agent Daemon serviced component synchronization Agent deployment strategys；
S52, obtain the Agent version informations that destination server needs to dispose；
S53, judge whether Agent version informations and the Agent versions that destination server is currently disposed are consistent；
If so, then S54, configuration file corresponding to renewal Agent deployment packages, and upload Agent deployable states；
If it is not, then S55, whether judged in destination server comprising needing what is disposed by Git version management mechanisms
Agent version informations；
If having included, S56, the Agent versions that destination server is currently disposed are switched to the Agent versions for needing to dispose
This, and enter S54 steps；
If not including, the step of S57, the Agent versions for needing to dispose being downloaded from Git warehouses, and enter S56.
Specifically, above-mentioned S51 steps are to S53 steps, it would be desirable to which the Agent version informations of deployment are worked as with destination server
Whether the Agent versions of preceding deployment are unanimously contrasted, it is therefore an objective to confirm currently whether deployment needs to dispose destination server.
For above-mentioned S55 steps to S57 steps, using Git itself version management mechanism, version can be quickly realized
This rollback；By the way that deployment package is separated with configuration file, Git version mechanisms are utilized, there is provided a kind of easy configuration upgrading
Administrative mechanism, avoid introducing complicated configuration management system.
Further, in certain embodiments, above-mentioned S54 steps, configuration text corresponding to renewal Agent deployment packages
Part, and the step of upload Agent deployable states, including step in detail below：
S541, the version information for obtaining configuration file corresponding to Agent deployment packages；
S542, judge configuration file version information whether the configuration file version information one current with destination server
Cause；
If so, then S543, upload Agent deployable states；
If it is not, then S544, whether judged in destination server comprising needing what is disposed by Git version management mechanisms
Agent deployment packages correspond to the version of configuration file；
If having included, S545, the version of destination server current configuration file is switched to the Agent portions for needing to dispose
The version information of the corresponding configuration file of administration's bag, and enter S543 steps；
If not including, S546, the version that the Agent deployment packages for needing to dispose correspond to configuration file is downloaded from Git warehouses
This information, and enter S543 steps.
By the way that deployment package is separated with configuration file, deployment package and configuration file are updated respectively, utilize Git versions
Present mechanism, there is provided a kind of easy configuration updating and management mechanism, avoid introducing complicated configuration management system.Complete configuration more
After new, by operational order corresponding to performance objective Agent, (agreement Agent deployment packages at least need to provide start/stop/none
The support of several orders), the state information report of deployment is finally facilitated into publisher to Agent configuration admin services end component
Member's monitoring management.
In view of the complexity issue of deployment, Agent configuration admin services end component, Git warehouses and Agent
Daemon serviced components are all realized using go language developments, so need not be relied on other environment when deployment, directly be opened
It is dynamic just to use, the condition depended to third party software is avoided, deployment is simple.
The above-mentioned deployment upgrade methods of the Agent based on git Version Controls, by using Agent configuration admin services end
Component and Agent Daemon serviced components, it is automatic to find destination server IP and title, deployment configuration difficulty is simplified,
Agent Daemon serviced components are easy to all kinds of Agent deployable states of monitoring objective server, utilize the Git warehouses version of itself
This administrative mechanism, the quick rollback of version is realized, and deployment package is separated with configuration file, utilize Git version mechanisms, there is provided
A kind of easy configuration updating and management mechanism, avoids introducing complicated configuration management system.
As shown in fig. 6, the present embodiment additionally provides the Agent deployment upgrade-systems based on git Version Controls, it includes group
Part processing unit 1, Agent Daemon processing units 2, deployment package processing unit 3 and deployment unit 4.
Component processing unit 1, for Agent configuration admin services end component and Git warehouses to be deployed into destination server
And each self-starting.
Agent Daemon processing units 2, for disposing Agent Daemon serviced components to destination server.
Deployment package processing unit 3, for Agent deployment packages to be uploaded into Git warehouses and configure Agent deployment strategys.
Deployment unit 4, for for Agent Daemon serviced component synchronization Agent deployment strategys, and perform Agent portions
Command operation corresponding to administration's strategy.
For above-mentioned component processing unit 1, the strategy that Agent configuration admin services end component is responsible for Agent deployment is set
Put, monitor the deployable state of each server, manage Agent configuration information；Git warehouses mainly store Agent deployment packages and matched somebody with somebody
Put file, there is provided version management is supported；Agent configuration admin services end component and Git warehouses are deployed to destination server simultaneously
Each self-starting, destination server can be caused to possess the function in Agent configuration admin services end component and Git warehouses, in portion
When administration, not comprising any configuration data, Git warehouses are also empty.
In addition, for above-mentioned Agent Daemon processing units 2, specifically deployment Agent destination service is being needed
Agent Daemon serviced components are disposed on device.Agent Daemon serviced components are deployed on each destination server, are responsible for
Synchronous deployment strategy simultaneously operates according to all kinds of Agent of strategy execution the machine deployment, upgrading etc., and is taken to Agent configuration managements
Server A gent deployable state where business end component reports；Agent Daemon serviced components typically seldom change, and can tie
It is bonded in virtual machine image, Daemon services so has been got well with regard to deployment automatically when virtual machine is newly created, can have been configured
Daemon start automatic starts, Daemon programs arrive the IP address for reporting book server automatically and server name after startup
Agent configuration admin services end component, using Agent patterns, can find server ip and title automatically, simplify deployment and match somebody with somebody
Difficulty is put, especially more highlights advantage when number of servers is more；Agent Daemon serviced components can more facilitate simultaneously
All kinds of Agent deployable states of the machine are monitored, deployment process is simple.
Further, in certain embodiments, deployment package processing unit 3 includes data acquisition module 31, submits module
32nd, address reporting module 33, version information setup module 34 and order setup module 35.
Data acquisition module 31, for obtaining the Agent deployment packages for needing to dispose and corresponding configuration file.
Module 32 is submitted, for Agent deployment packages and corresponding configuration file to be committed into Git warehouses.
Address reporting module 33, it is grouped for reporting destination server address, and to destination server.
Version information setup module 34, the Agent version informations disposed for setting every group of destination server to need.
Order setup module 35, for setting Agent operation command.
The Agent deployment packages and corresponding configuration file that first needs are disposed are submitted to Git warehouses by Git instruments, with
It is easy to realize version management, including the storage of version, the renewal of version, the comparison of version, this switching using Git mechanism auxiliary
Deng, if not having to Git, directly replace Git warehouses also to realize that Agent deployment upgrades using file storage service, but every time
Change version is required for voluntarily realizing the replacement operation of file.
According to the destination server address reported automatically, destination server is grouped, every group of destination server is set
(version information includes title, Agent version numbers, deployment package Git addresses, corresponding configuration to the Agent version informations for needing to dispose
File address, configuration file version, the account of operation, the attribute such as destination path of deployment), and set Agent's to perform operation
Order (start/stop/none).
Further, in certain embodiments, deployment unit 4 includes synchronization module 41, Agent version informations obtain mould
Block 42, Agent versions judge module 43, update module 44, Agent version existence judge module 45, Agent versions switching mould
Block 46 and Agent versions download module 47.
Synchronization module 41, for Agent Daemon serviced component synchronization Agent deployment strategys.
Agent version informations acquisition module 42, the Agent version informations disposed for obtaining destination server to need.
Agent versions judge module 43, the Agent currently disposed for judging Agent version informations and destination server
Whether version is consistent.
Update module 44, for if so, then configuration file corresponding to renewal Agent deployment packages, and upload Agent deployment shapes
State.
Agent version existence judge module 45, for if it is not, then judging destination service by Git version management mechanisms
Whether comprising the Agent version informations for needing to dispose in device.
Agent versions handover module 46, if for having included, the Agent versions that destination server is currently disposed are cut
Shift to the Agent versions for needing to dispose.
Agent versions download module 47, if for not including, the Agent versions for needing to dispose are downloaded from Git warehouses
This.
Using Git itself version management mechanism, the rollback of version can be quickly realized；By by deployment package with configuration
File separates, and utilizes Git version mechanisms, there is provided a kind of easy configuration updating and management mechanism, avoids introducing complicated configuration
Management system.
Further, in certain embodiments, update module 44 includes FileVersion acquisition submodule 441, file version
This judging submodule 442, state upload submodule 443, FileVersion existence judging submodule 444, FileVersion switching
Module 445 and FileVersion download submodule 446.
FileVersion acquisition submodule 441, for obtaining the version information of configuration file corresponding to Agent deployment packages.
FileVersion judging submodule 442, for judging whether the version information of configuration file is current with destination server
Configuration file version information it is consistent.
State uploads submodule 443, for if so, then uploading Agent deployable states.
FileVersion existence judging submodule 444, for if it is not, then judging that target takes by Git version management mechanisms
Whether the version of configuration file has been corresponded to comprising the Agent deployment packages for needing to dispose in business device.
FileVersion switching submodule 445, if for having included, the version of destination server current configuration file is cut
The Agent deployment packages that shifting to needs to dispose correspond to the version information of configuration file.
FileVersion downloads submodule 446, if for not including, the Agent portions for needing to dispose are downloaded from Git warehouses
The version information of the corresponding configuration file of administration's bag.
By the way that deployment package is separated with configuration file, deployment package and configuration file are updated respectively, utilize Git versions
Present mechanism, there is provided a kind of easy configuration updating and management mechanism, avoid introducing complicated configuration management system.Complete configuration more
After new, by operational order corresponding to performance objective Agent, (agreement Agent deployment packages at least need to provide start/stop/none
The support of several orders), the state information report of deployment is finally facilitated into publisher to Agent configuration admin services end component
Member's monitoring management.
In view of the complexity issue of deployment, Agent configuration admin services end component, Git warehouses and Agent
Daemon serviced components are all realized using go language developments, so need not be relied on other environment when deployment, directly be opened
It is dynamic just to use, the condition depended to third party software is avoided, deployment is simple.
The above-mentioned deployment upgrade-systems of the Agent based on git Version Controls, by using Agent configuration admin services end
Component and Agent Daemon serviced components, it is automatic to find destination server IP and title, deployment configuration difficulty is simplified,
Agent Daemon serviced components are easy to all kinds of Agent deployable states of monitoring objective server, utilize the Git warehouses version of itself
This administrative mechanism, the quick rollback of version is realized, and deployment package is separated with configuration file, utilize Git version mechanisms, there is provided
A kind of easy configuration updating and management mechanism, avoids introducing complicated configuration management system.
The above-mentioned technology contents that the present invention is only further illustrated with embodiment, in order to which reader is easier to understand, but not
Represent embodiments of the present invention and be only limitted to this, any technology done according to the present invention extends or recreation, by the present invention's
Protection.Protection scope of the present invention is defined by claims.
Claims (8)
1. the Agent deployment upgrade methods based on git Version Controls, it is characterised in that methods described includes：
Agent configuration admin services end component and Git warehouses are deployed to destination server and each self-starting；
Agent Daemon serviced components are disposed to destination server；
Agent deployment packages are uploaded into Git warehouses and configure Agent deployment strategys；
For Agent Daemon serviced component synchronization Agent deployment strategys, and perform order behaviour corresponding to Agent deployment strategys
Make.
2. the Agent deployment upgrade methods according to claim 1 based on git Version Controls, it is characterised in that will
The step of Agent deployment packages upload to Git warehouses and configure Agent deployment strategys, including step in detail below：
Obtain the Agent deployment packages for needing to dispose and corresponding configuration file；
Agent deployment packages and corresponding configuration file are committed to Git warehouses；
Destination server address is reported, and destination server is grouped；
Every group of destination server is set to need the Agent version informations disposed；
Agent operation command is set.
3. the Agent deployment upgrade methods according to claim 1 or 2 based on git Version Controls, it is characterised in that pin
To Agent Daemon serviced component synchronization Agent deployment strategys, and perform the step of command operation corresponding to Agent deployment strategys
Suddenly, including in detail below step：
Agent Daemon serviced component synchronization Agent deployment strategys；
Obtain the Agent version informations that destination server needs to dispose；
Judge whether Agent version informations and the Agent versions that destination server is currently disposed are consistent；
If so, then updating configuration file corresponding to Agent deployment packages, and upload Agent deployable states；
If it is not, then judge whether believed comprising the Agent versions for needing to dispose in destination server by Git version management mechanisms
Breath；
If having included, the Agent versions that destination server is currently disposed are switched to the Agent versions for needing to dispose, gone forward side by side
The step of entering to update Agent deployment packages and corresponding configuration file, and uploading Agent deployable states；
If not including, the Agent versions for needing to dispose are downloaded from Git warehouses, and enter and currently dispose destination server
Agent versions switch to need dispose Agent versions the step of.
4. the Agent deployment upgrade methods according to claim 3 based on git Version Controls, it is characterised in that renewal
Configuration file corresponding to Agent deployment packages, and the step of upload Agent deployable states, including step in detail below：
Obtain the version information of configuration file corresponding to Agent deployment packages；
Judge whether the version information of configuration file is consistent with the configuration file version information that destination server is current；
If so, then upload Agent deployable states；
If it is not, then whether judged by Git version management mechanisms in destination server comprising the Agent deployment packages for needing to dispose
The version of corresponding configuration file；
If having included, the Agent deployment packages that the version of destination server current configuration file, which is switched to, to be needed to dispose correspond to
The version information of configuration file, and enter the step of uploading Agent deployable states；
If not including, the Agent deployment packages that being downloaded from Git warehouses needs to dispose correspond to the version information of configuration file, and
Into the step of uploading Agent deployable states.
5. the Agent deployment upgrade-systems based on git Version Controls, it is characterised in that including component processing unit, Agent
Daemon processing units, deployment package processing unit and deployment unit；
The component processing unit, for Agent configuration admin services end component and Git warehouses to be deployed into destination server simultaneously
Each self-starting；
The Agent Daemon processing units, for disposing Agent Daemon serviced components to destination server；
The deployment package processing unit, for Agent deployment packages to be uploaded into Git warehouses and configure Agent deployment strategys；
The deployment unit, for for Agent Daemon serviced component synchronization Agent deployment strategys, and perform Agent portions
Command operation corresponding to administration's strategy.
6. the Agent deployment upgrade-systems according to claim 5 based on git Version Controls, it is characterised in that the portion
Administration's bag processing unit includes data acquisition module, submits module, address reporting module, version information setup module and order to set
Put module；
The data acquisition module, for obtaining the Agent deployment packages for needing to dispose and corresponding configuration file；
The submission module, for Agent deployment packages and corresponding configuration file to be committed into Git warehouses；
The address reporting module, is grouped for reporting destination server address, and to destination server；
The version information setup module, the Agent version informations disposed for setting every group of destination server to need；
The order setup module, for setting Agent operation command.
7. the Agent deployment upgrade-systems according to claim 6 based on git Version Controls, it is characterised in that the portion
Affixing one's name to unit includes synchronization module, Agent version informations acquisition module, Agent versions judge module, update module, Agent versions
Existence judge module, Agent versions handover module and Agent version download modules；
The synchronization module, for Agent Daemon serviced component synchronization Agent deployment strategys；
The Agent version informations acquisition module, the Agent version informations disposed for obtaining destination server to need；
The Agent versions judge module, the Agent versions currently disposed for judging Agent version informations and destination server
Whether this is consistent；
The update module, for if so, then configuration file corresponding to renewal Agent deployment packages, and upload Agent deployment shapes
State；
The Agent versions existence judge module, for if it is not, then judging destination server by Git version management mechanisms
Inside whether comprising the Agent version informations for needing to dispose；
The Agent versions handover module, if for having included, the Agent versions that destination server is currently disposed switch
The Agent versions disposed to needs；
The Agent versions download module, if for not including, the Agent versions for needing to dispose are downloaded from Git warehouses.
8. it is according to claim 7 based on git Version Controls Agent deployment upgrade-system, it is characterised in that it is described more
New module includes FileVersion acquisition submodule, FileVersion judging submodule, state and uploads submodule, FileVersion existence
Judging submodule, FileVersion switching submodule and FileVersion download submodule；
The FileVersion acquisition submodule, for obtaining the version information of configuration file corresponding to Agent deployment packages；
The FileVersion judging submodule, for judge configuration file version information whether with destination server is current matches somebody with somebody
It is consistent to put file version information；
The state uploads submodule, for if so, then uploading Agent deployable states；
The FileVersion existence judging submodule, for if it is not, then judging destination server by Git version management mechanisms
The version of configuration file inside whether has been corresponded to comprising the Agent deployment packages for needing to dispose；
The FileVersion switching submodule, if for having included, the version of destination server current configuration file is switched
The version information of configuration file is corresponded to the Agent deployment packages for needing to dispose；
The FileVersion downloads submodule, if for not including, the Agent deployment for needing to dispose is downloaded from Git warehouses
The version information of the corresponding configuration file of bag.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711063697.7A CN107659458B (en) | 2017-11-02 | 2017-11-02 | Agent deployment and upgrade method and system based on git version control |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711063697.7A CN107659458B (en) | 2017-11-02 | 2017-11-02 | Agent deployment and upgrade method and system based on git version control |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107659458A true CN107659458A (en) | 2018-02-02 |
| CN107659458B CN107659458B (en) | 2021-04-13 |
Family
ID=61095769
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711063697.7A Active CN107659458B (en) | 2017-11-02 | 2017-11-02 | Agent deployment and upgrade method and system based on git version control |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107659458B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108540341A (en) * | 2018-03-19 | 2018-09-14 | 云宏信息科技股份有限公司 | resource monitoring method and device |
| CN108829433A (en) * | 2018-05-24 | 2018-11-16 | 努比亚技术有限公司 | A kind of web system version dispositions method, equipment and storage medium |
| CN110865831A (en) * | 2018-08-27 | 2020-03-06 | Ovh公司 | Method for improved automatic software update in deploying networked devices |
| CN112272200A (en) * | 2020-09-11 | 2021-01-26 | 苏州浪潮智能科技有限公司 | Management method and device for cloud workload deployment versions of Gitlab container |
| CN112416385A (en) * | 2020-08-13 | 2021-02-26 | 上海哔哩哔哩科技有限公司 | Acquisition component management method and system |
| CN113031977A (en) * | 2021-04-07 | 2021-06-25 | 深圳云之家网络有限公司 | Software batch installation method and related device |
| CN114327499A (en) * | 2021-12-28 | 2022-04-12 | 浪潮卓数大数据产业发展有限公司 | Method, device, equipment and medium for rapid deployment and rollback of remote service |
| CN116820526A (en) * | 2023-08-25 | 2023-09-29 | 建信金融科技有限责任公司 | Operating system upgrading method, device, equipment and storage medium |
| CN117319196A (en) * | 2023-10-26 | 2023-12-29 | 无锡芯光互连技术研究院有限公司 | User server cluster environment deployment management system and method |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101945135A (en) * | 2010-09-20 | 2011-01-12 | 中兴通讯股份有限公司 | Method and system for upgrading widget system |
| US7937482B1 (en) * | 2008-03-27 | 2011-05-03 | Amazon Technologies, Inc. | Scalable consensus protocol |
| CN102339366A (en) * | 2010-07-28 | 2012-02-01 | 上海交泰信息科技有限公司 | OMA (Open Mobile Alliance) DRM (Digital Rights Management) Agent based on radio frequency mobile phone and RO (right object) design method thereof |
| CN102868731A (en) * | 2012-08-27 | 2013-01-09 | 济南大学 | Method and device for software online updating and downloading acceleration |
| CN103049268A (en) * | 2012-12-25 | 2013-04-17 | 中国科学院深圳先进技术研究院 | Naplet based application development and management system |
| US20130232498A1 (en) * | 2012-03-02 | 2013-09-05 | Vmware, Inc. | System to generate a deployment plan for a cloud infrastructure according to logical, multi-tier application blueprint |
| CN106997297A (en) * | 2017-03-31 | 2017-08-01 | 广东亿迅科技有限公司 | A kind of software development management platform and method based on DevOps |
-
2017
- 2017-11-02 CN CN201711063697.7A patent/CN107659458B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7937482B1 (en) * | 2008-03-27 | 2011-05-03 | Amazon Technologies, Inc. | Scalable consensus protocol |
| CN102339366A (en) * | 2010-07-28 | 2012-02-01 | 上海交泰信息科技有限公司 | OMA (Open Mobile Alliance) DRM (Digital Rights Management) Agent based on radio frequency mobile phone and RO (right object) design method thereof |
| CN101945135A (en) * | 2010-09-20 | 2011-01-12 | 中兴通讯股份有限公司 | Method and system for upgrading widget system |
| US20130232498A1 (en) * | 2012-03-02 | 2013-09-05 | Vmware, Inc. | System to generate a deployment plan for a cloud infrastructure according to logical, multi-tier application blueprint |
| CN102868731A (en) * | 2012-08-27 | 2013-01-09 | 济南大学 | Method and device for software online updating and downloading acceleration |
| CN103049268A (en) * | 2012-12-25 | 2013-04-17 | 中国科学院深圳先进技术研究院 | Naplet based application development and management system |
| CN106997297A (en) * | 2017-03-31 | 2017-08-01 | 广东亿迅科技有限公司 | A kind of software development management platform and method based on DevOps |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108540341B (en) * | 2018-03-19 | 2021-01-29 | 云宏信息科技股份有限公司 | Resource monitoring method and device |
| CN108540341A (en) * | 2018-03-19 | 2018-09-14 | 云宏信息科技股份有限公司 | resource monitoring method and device |
| CN108829433A (en) * | 2018-05-24 | 2018-11-16 | 努比亚技术有限公司 | A kind of web system version dispositions method, equipment and storage medium |
| CN110865831B (en) * | 2018-08-27 | 2022-05-27 | Ovh公司 | Method for improved automatic software update in deploying networked devices |
| CN110865831A (en) * | 2018-08-27 | 2020-03-06 | Ovh公司 | Method for improved automatic software update in deploying networked devices |
| CN112416385A (en) * | 2020-08-13 | 2021-02-26 | 上海哔哩哔哩科技有限公司 | Acquisition component management method and system |
| CN112272200A (en) * | 2020-09-11 | 2021-01-26 | 苏州浪潮智能科技有限公司 | Management method and device for cloud workload deployment versions of Gitlab container |
| CN113031977A (en) * | 2021-04-07 | 2021-06-25 | 深圳云之家网络有限公司 | Software batch installation method and related device |
| CN114327499A (en) * | 2021-12-28 | 2022-04-12 | 浪潮卓数大数据产业发展有限公司 | Method, device, equipment and medium for rapid deployment and rollback of remote service |
| CN114327499B (en) * | 2021-12-28 | 2024-05-14 | 浪潮卓数大数据产业发展有限公司 | Method, device, equipment and medium for rapidly deploying and rolling off remote service |
| CN116820526A (en) * | 2023-08-25 | 2023-09-29 | 建信金融科技有限责任公司 | Operating system upgrading method, device, equipment and storage medium |
| CN116820526B (en) * | 2023-08-25 | 2023-11-24 | 建信金融科技有限责任公司 | Operating system upgrading method, device, equipment and storage medium |
| CN117319196A (en) * | 2023-10-26 | 2023-12-29 | 无锡芯光互连技术研究院有限公司 | User server cluster environment deployment management system and method |
| CN117319196B (en) * | 2023-10-26 | 2024-05-14 | 无锡芯光互连技术研究院有限公司 | User server cluster environment deployment management system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107659458B (en) | 2021-04-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107659458A (en) | Agent deployment upgrade methods and system based on git Version Controls | |
| US20220197953A1 (en) | Model pushing method and device, model requesting method and device, storage medium and electronic device | |
| US20210342725A1 (en) | Systems And Methods For Tracking And Representing Data Science Model Runs | |
| CN107301058B (en) | Method for implementing OTA upgrade of television system based on version number segment control | |
| US10084650B2 (en) | Graphical user interface for customizing graphical representations based on registry data | |
| US7366706B2 (en) | Method and apparatus for solution-template based deployment and management of an integration solution | |
| US20170206066A1 (en) | System for the discovery and provisioning of artifacts and composites | |
| CN104918114B (en) | A kind of operating system update method and device | |
| CN106612206A (en) | Apparatus and method for automating the installation and configuration of infrastructure | |
| US8601462B2 (en) | Modifying a multi-module application | |
| US20170012819A1 (en) | System and method for provisioning cloud services across heterogeneous environments | |
| CN102073519B (en) | Software updating method | |
| CN105159718A (en) | Firmware updating method and device | |
| CN109086051A (en) | Application component dispositions method, device and computer storage medium | |
| CN113138781B (en) | CSV configuration updating method and storage medium | |
| US8336057B2 (en) | Method and system for automatically generating message queue scripts | |
| CN105389187A (en) | System update method | |
| CN109002314A (en) | Oftware updating method, device, electronic equipment and storage medium | |
| CN105204910A (en) | Script hot updating method and system | |
| CN112732285B (en) | Upgrading method and device suitable for cloud computing linux operating system and electronic equipment | |
| CN103268242A (en) | Method and device for installing information system | |
| CN117492803A (en) | Intelligent door lock PCBA software upgrading method and system | |
| US20210311712A1 (en) | Validation of desired software state image for hardware incompatibilities | |
| CN115878154A (en) | System and method for upgrading container mirror image version | |
| CN110286915A (en) | Automatically dispose system and method under internet and trusted identity authentication platform |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |