CN109165082A - System smooth upgrading method based on container - Google Patents
System smooth upgrading method based on container Download PDFInfo
- Publication number
- CN109165082A CN109165082A CN201810957239.6A CN201810957239A CN109165082A CN 109165082 A CN109165082 A CN 109165082A CN 201810957239 A CN201810957239 A CN 201810957239A CN 109165082 A CN109165082 A CN 109165082A
- Authority
- CN
- China
- Prior art keywords
- module
- docker
- user
- mark
- updated
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Abstract
The present disclosure proposes a kind of system smooth upgrading method based on container, comprising: module docker of the distribution address IPv6 to system；The mark id of login user is modified according to the address IPv6 of module docker；According to user's access state of mark id determining module docker；And system upgrade is carried out according to user's access state of module docker.The unaware upgrading of system may be implemented based on the system smooth upgrading method of container for the disclosure, eliminate or reduce the delay time of system upgrade process.
Description
Technical field
This disclosure relates to which container and kubernetes distributed technical field more particularly to a kind of system based on container are flat
Sliding upgrade method.
Background technique
During traditional system upgrade ,-the update server data file-mistake restarted since it is desired that by shutdown
Journey, so often will appear the case where needing the waiting time.It, can be great if having system user that system is used just
Influence the usage experience of user.So how to realize the smooth upgrade of system, accomplish that user's unaware is an important topic.
For docker container as a kind of emerging technology, core is the virtualization technology relied on linux kernel function, tool
There are the advantages such as lightweight, virtualization, the fast, portable of deployment, facilitates continuous integrating, make continuous integrating by being associated with code
It is very convenient.
Kubernetes is an open source, for managing the application of the containerization in cloud platform in multiple main frames,
The target of Kubernetes be allow deployment container using simple and efficient.
Summary of the invention
(1) technical problems to be solved
Present disclose provides a kind of system smooth upgrading method based on container, it is above existing at least partly to solve
Technical problem.
(2) technical solution
According to one aspect of the disclosure, a kind of system smooth upgrading method based on container is provided, comprising:
The address IPv6 is distributed to the module docker of system；
The mark id of login user is modified according to the address IPv6 of module docker；
According to user's access state of mark id determining module docker；And
System upgrade is carried out according to user's access state of module docker.
In some embodiments, according to the address IPv6 of module docker modify login user mark id the step of it
Before, further include user's logging state of determining system, if no user logging state, then system upgrade is directly carried out, if having
User's logging state then modifies the mark id of login user according to the address IPv6 of module docker.
In some embodiments, the system comprises multiple module docker, in the distribution address IPv6 to the module of system
In the step of docker, the address IPv6 that each module docker is distributed is different.
In some embodiments, in the step of carrying out system upgrade according to user's access state of module docker, if
One module docker to be updated is no user access state, then is updated to this module docker to be updated；If
There is user's access state, then wouldn't be updated.
In some embodiments, to be updated to this if a module docker to be updated is no user access state
Module docker be updated, the pod with new function is placed under the former pod in this module to be updated；If having
User's access state wouldn't be then updated, and track the mark that user is accessed corresponding to this module docker to be updated
Id, until after mark id changes, then carry out the update of pod.
In some embodiments, if multiple module docker of system are to be updated, each module docker is successively updated,
All pod to be updated of each module docker of system are completed after updating, and are cut off former module pod, are started new pod, thus
Complete update and the system upgrade of each module.
In some embodiments, it includes: login module, projects module, procurement module, contract that the system, which is ERP system,
Module, invoice module, system management module.
In some embodiments, the step of modifying the mark id of login user according to the address IPv6 of module docker
In, the mark id of the login user is revised as to last two of the address IPv6 of the module docker of its logged in node,
Last two differences in the address IPv6 of each module docker.
In some embodiments, the step of modifying the mark id of login user according to the address IPv6 of module docker
In, by the last two+current time in the address IPv6 of the mark id of the user module docker for being revised as its logged in node,
Last two differences in the address IPv6 of each module.
In some embodiments, according to mark id determining module docker user's access state the step of in, statistics
The mark id of current whole login user, if IPv6 address of the mark id of whole login users with any module to be updated
The last two+current time in the last address two/IPv6 it is different, then any module to be updated is that no user accesses shape
State, otherwise, any module to be updated are to have user's access state.
(3) beneficial effect
It can be seen from the above technical proposal that the disclosure is at least had based on the system smooth upgrading method of container following to be had
One of beneficial effect:
(1) the unaware upgrading of system may be implemented in method of disclosure, when eliminating or reducing the delay of system upgrade process
Between, improve the usage experience of system user.
(2) method of disclosure, it is ensured that some or certain module/flow nodes of halt system, without to being
The other parts of system have an impact.
(3) method of disclosure, each docker only distribute the address IPv6, can effectively avoid being attacked, one
Determine the safety that ensure that system in degree.
Detailed description of the invention
Fig. 1 is the basic framework figure according to embodiment of the present disclosure ERP system.
Fig. 2 is according to ERP system smooth upgrading method flow chart of the embodiment of the present disclosure based on container.
Specific embodiment
For the purposes, technical schemes and advantages of the disclosure are more clearly understood, below in conjunction with specific embodiment, and reference
The disclosure is further described in attached drawing.
A kind of system smooth upgrading method based on container of the disclosure realizes the unaware upgrading of ERP system, eliminates system
The delay time of escalation process improves the usage experience of system user.
The system smooth upgrading method based on container uses docker container technique and Kubernetes distribution frame
Structure mainly comprises the steps that
The address IPv6 is distributed to the module docker of system: if system includes multiple modules, to the modules of system
Docker distributes the different addresses IPv6, guarantees that the address IPv6 of each module is different.
The mark id of login user is modified according to the address IPv6 of module docker: after logging in system by user, distribution is stepped on
Mark id of last position (or multidigit) of the address node IP v6 as user is recorded, when user's operation module, by the user's
Mark id be changed to last position of the address IPv6 of the node (be also readily modified as the rear multidigit of the address IPv6 of the node, can be with
It is changed to the last one or more+current time in the address IPv6 of the node).It wherein, before this step, further include determining system
User's logging state, if no user logging state, i.e., system no user logs in, then can directly carry out system upgrade, if
There is user's logging state, then modifies the mark id of login user according to the address IPv6 of module docker.
According to user's access state of mark id determining module docker: in system update, judging the current institute of system
There is the pod for whether thering is user to access any module docker to be updated in login user, for any mould to be updated
Block docker, determine whether have in the mark id of all login users it is last with the address IPv6 of the module docker to be updated
One identical mark id (if in abovementioned steps being the rear multidigit that the mark id of the user is changed to the address IPv6 of the node,
Then determine accordingly whether have in the mark id of all login users with it is more behind the address IPv6 of the module docker to be updated
The identical mark id in position；If being that the mark id of the user is changed to last position of the address IPv6 of the node or more in abovementioned steps
Position+current time then determines in the mark id of all login users whether there is the module docker's to be updated with this accordingly
The address the IPv6 identical mark id of last one or more+current time), if nothing, this module docker's to be updated
User's access state is no user access state, otherwise to there is user's access state.
And system upgrade is carried out according to user's access state of module docker: if the module that system one is to be updated
User's access state of docker is no user access state, then updates replacement node pod immediately；If have user access shape
State, then the mark id for continuing to track user corresponding to module docker (are accessing the user of this module docker
Mark id), until mark id change after, then carry out this module docker pod update.
If there is multiple pod require to update, then each pod is successively updated according to abovementioned steps.
In one embodiment, system of the disclosure based on container is discussed in detail so that ERP system upgrades as an example smoothly to rise
Grade method.Certain method of disclosure, which is not limited to ERP system upgrading, can be also used for the upgrading of other systems.
Specifically, project is purchased, contract, invoice and system administration 6 as shown in Figure 1, the ERP system includes: to log in
A module, those skilled in the art it is to be understood that the module that the disclosure is included for system quantity and type
And with no restriction.The corresponding system module of each node node.Meanwhile each module can have different processes, so often
Each process of pod respective modules under a node.
Different modules being put into different node nodes, each node is exactly a docker, multiple pod are stored,
Store each flow nodes of each module.It the use of docker is some or the certain moulds that can guarantee only to need halt system
Block/flow nodes has an impact without the other parts to system.Each docker only distributes the address IPv6.One
Aspect, the address IPv6 is very sufficient, and on the other hand, the address IPv6 is less to be attacked, and ensure that the safety of system to a certain extent
Property.
When user log in after, distribution log in the address node IP v6 after mark id of the two+current time as user, when with
When family operates certain module, the mark id of the user is changed to two+current time behind the address IPv6 of the node.Firstly, because
Latter two of the address IPv6 of each node are different, can determine the user has entered which mould of system according to mark id
Block；Secondly, might have multiple users while accessing the Module nodes, so increasing current time, can distinguish different
User.In addition it is also possible to distribute log in the address node IP v6 last/the mark id of rear multidigit as user, can also divide
With log in the address node IP v6 last/the mark id of rear multidigit+current time as user, correspondingly, working as user's operation
When certain module, the mark id of the user is changed to the latter position in the address IPv6/rear multidigit or the address node IP v6 of the node
Latter position/rear multidigit+current time.
When system update, the pod with new function is placed under the node (docker) of former pod first, is then counted
The mark id of current all login users, if the mark id front two of none of user and the node to be updated
Behind the address IPv6 two it is identical, then illustrate no user access the node.If so, then continuing to track mark id, wait until
After mark id changes, then carry out the update of pod.Former module pod is finally cut off, new pod is started, completes the module more
Newly.
If system update includes the update of multiple pod, successively docker where pod is judged, if useful
Family access, then successively updates multiple pod.
The present embodiment method effectively increases the upgrading efficiency of company's ERP system, and the unaware liter of ERP system may be implemented
Grade eliminates the delay time of system upgrade process, improves the usage experience of system user.
As shown in Fig. 2, the present embodiment method contains the distribution of the address each module docker, system user allocation identification is given
Id judges currently whether all users access more new node, node updates process etc. to system.Specifically, this method includes
Following steps:
1, the different addresses IPv6 is distributed to six big module docker of the ERP system, guarantees the IPv6 of disparate modules
Two are different from behind address.
2, user log in after, distribution log in the address node IP v6 after mark id of the two+current time as user, when with
When family operates certain module, the mark id of the user is changed to two+current time behind the address IPv6 of the node.
3, when system update, according to the mark id of user, judge whether the current all users of system have user's access should
The pod of module docker, if it is not, updating replacement node pod immediately；If so, then continuing to track mark id, wait until
After mark id changes, then carry out the update of pod.
4, if there is multiple pod require to update, then the operation of step 3 is successively carried out to each pod, successively update each
pod。
Particular embodiments described above has carried out further in detail the purpose of the disclosure, technical scheme and beneficial effects
Describe in detail it is bright, it is all it should be understood that be not limited to the disclosure the foregoing is merely the specific embodiment of the disclosure
Within the spirit and principle of the disclosure, any modification, equivalent substitution, improvement and etc. done should be included in the guarantor of the disclosure
Within the scope of shield.
So far, attached drawing is had been combined the embodiment of the present disclosure is described in detail.According to above description, art technology
Personnel should have clear understanding based on the ERP system smooth upgrading method of container to the disclosure.
It should be noted that in attached drawing or specification text, the implementation for not being painted or describing is affiliated technology
Form known to a person of ordinary skill in the art, is not described in detail in field.In addition, the above-mentioned definition to each element and method is simultaneously
It is not limited only to various specific structures, shape or the mode mentioned in embodiment, those of ordinary skill in the art can carry out letter to it
It singly changes or replaces.
Certainly, according to actual needs, the step of method of disclosure also includes other, due to the same disclosure innovation without
It closes, details are not described herein again.
Particular embodiments described above has carried out further in detail the purpose of the disclosure, technical scheme and beneficial effects
Describe in detail bright, it should be understood that the foregoing is merely the specific embodiment of the disclosure, be not limited to the disclosure, it is all
Within the spirit and principle of the disclosure, any modification, equivalent substitution, improvement and etc. done should be included in the protection of the disclosure
Within the scope of.
Claims (10)
1. a kind of system smooth upgrading method based on container, comprising:
The address IPv6 is distributed to the module docker of system；
The mark id of login user is modified according to the address IPv6 of module docker；
According to user's access state of mark id determining module docker；And
System upgrade is carried out according to user's access state of module docker.
2. according to the method described in claim 1, wherein,
It further include determining system before the step of modifying the mark id of login user according to the address IPv6 of module docker
User's logging state then directly carries out system upgrade, if there is user's logging state, then basis if no user logging state
The mark id of the address the IPv6 modification login user of module docker.
3. method according to claim 1 or 2, wherein
The system comprises multiple module docker, in the step of distributing module docker of the address IPv6 to system, each mould
The address IPv6 that block docker is distributed is different.
4. according to the method described in claim 1, wherein,
In the step of carrying out system upgrade according to user's access state of module docker, if a module docker to be updated
For no user access state, then this module docker to be updated is updated；If there is user's access state, then wouldn't
It is updated.
5. according to the method described in claim 4, wherein,
If a module docker to be updated is no user access state, this module docker to be updated is carried out more
Newly, the pod with new function is placed under the former pod in this module to be updated；If there is user's access state, then wouldn't
It is updated, tracks the mark id for accessing user corresponding to this module docker to be updated, until mark id changes
Afterwards, then the update of pod is carried out.
6. according to the method described in claim 1, wherein,
If multiple module docker of system are to be updated, each module docker is successively updated, in each module docker of system
All pod to be updated complete after updating, cut off former module pod, start new pod, thus complete each module update and
System upgrade.
7. according to the method described in claim 1, wherein, the system is that ERP system includes: login module, and projects module is adopted
Purchase module, contract module, invoice module, system management module.
8. according to the method described in claim 1, wherein, in the mark for modifying login user according to the address IPv6 of module docker
In the step of knowing id, the mark id of the login user is revised as to the address IPv6 of the module docker of its logged in node
Last two, last two differences in the address IPv6 of each module docker.
9. according to the method described in claim 1, wherein, in the mark for modifying login user according to the address IPv6 of module docker
In the step of knowing id, by last two of the address IPv6 of the mark id of the user module docker for being revised as its logged in node
+ current time, last two differences in the address IPv6 of each module.
10. method according to claim 8 or claim 9, wherein
In the step of according to the user's access state for identifying id determining module docker, the mark of current whole login users is counted
Id is known, if last two/IPv6 address of the mark id of whole login users with the address IPv6 of any module to be updated
Last two+current time is different, then any module to be updated is no user access state, and otherwise, this is any to be updated
Module be have user's access state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810957239.6A CN109165082A (en) | 2018-08-21 | 2018-08-21 | System smooth upgrading method based on container |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810957239.6A CN109165082A (en) | 2018-08-21 | 2018-08-21 | System smooth upgrading method based on container |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109165082A true CN109165082A (en) | 2019-01-08 |
Family
ID=64896377
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810957239.6A Pending CN109165082A (en) | 2018-08-21 | 2018-08-21 | System smooth upgrading method based on container |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109165082A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111258609A (en) * | 2020-01-19 | 2020-06-09 | 北京百度网讯科技有限公司 | Upgrading method and device of Kubernetes cluster, electronic equipment and medium |
| CN111327640A (en) * | 2020-03-24 | 2020-06-23 | 广西梯度科技有限公司 | Method for setting IPv6 for Pod in Kubernetes |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102217284A (en) * | 2011-06-17 | 2011-10-12 | 华为技术有限公司 | Address processing method, gateway device, ap |
| US20150341428A1 (en) * | 2014-05-20 | 2015-11-26 | Citrix Systems, Inc. | Systems and methods for providing load balancing as a service |
| CN105376303A (en) * | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN105677394A (en) * | 2015-12-30 | 2016-06-15 | 北京奇艺世纪科技有限公司 | Method and apparatus for upgrading application on terminal device |
| CN106293820A (en) * | 2016-08-02 | 2017-01-04 | 山东大学 | Exploitation test O&M integral system, deployment, full dose and increment updating method |
| CN106575427A (en) * | 2014-08-12 | 2017-04-19 | 艾高特有限责任公司 | A zero-knowledge environment based social networking engine |
| US20170295140A1 (en) * | 2016-04-12 | 2017-10-12 | Cryptzone North America, Inc. | Systems and methods for protecting network devices by a firewall |
| CN107436790A (en) * | 2017-08-14 | 2017-12-05 | 郑州云海信息技术有限公司 | A kind of component upgrade management method and device |
| CN107515776A (en) * | 2017-07-18 | 2017-12-26 | 深信服科技股份有限公司 | The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing |
| CN107680295A (en) * | 2017-06-12 | 2018-02-09 | 平安科技（深圳）有限公司 | Automatic teller machine control update method and device |
-
2018
- 2018-08-21 CN CN201810957239.6A patent/CN109165082A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102217284A (en) * | 2011-06-17 | 2011-10-12 | 华为技术有限公司 | Address processing method, gateway device, ap |
| US20150341428A1 (en) * | 2014-05-20 | 2015-11-26 | Citrix Systems, Inc. | Systems and methods for providing load balancing as a service |
| CN106575427A (en) * | 2014-08-12 | 2017-04-19 | 艾高特有限责任公司 | A zero-knowledge environment based social networking engine |
| CN105376303A (en) * | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN105677394A (en) * | 2015-12-30 | 2016-06-15 | 北京奇艺世纪科技有限公司 | Method and apparatus for upgrading application on terminal device |
| US20170295140A1 (en) * | 2016-04-12 | 2017-10-12 | Cryptzone North America, Inc. | Systems and methods for protecting network devices by a firewall |
| CN106293820A (en) * | 2016-08-02 | 2017-01-04 | 山东大学 | Exploitation test O&M integral system, deployment, full dose and increment updating method |
| CN107680295A (en) * | 2017-06-12 | 2018-02-09 | 平安科技（深圳）有限公司 | Automatic teller machine control update method and device |
| CN107515776A (en) * | 2017-07-18 | 2017-12-26 | 深信服科技股份有限公司 | The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing |
| CN107436790A (en) * | 2017-08-14 | 2017-12-05 | 郑州云海信息技术有限公司 | A kind of component upgrade management method and device |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111258609A (en) * | 2020-01-19 | 2020-06-09 | 北京百度网讯科技有限公司 | Upgrading method and device of Kubernetes cluster, electronic equipment and medium |
| CN111258609B (en) * | 2020-01-19 | 2023-08-01 | 北京百度网讯科技有限公司 | Upgrading method and device of Kubernetes cluster, electronic equipment and medium |
| CN111327640A (en) * | 2020-03-24 | 2020-06-23 | 广西梯度科技有限公司 | Method for setting IPv6 for Pod in Kubernetes |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104135539B (en) | Date storage method, SDN controllers and distributed network storage system | |
| CN103399778B (en) | A kind of virtual machine online bulk migration method and apparatus | |
| CN105684357A (en) | Management of addresses in virtual machines | |
| CN110661842B (en) | Resource scheduling management method, electronic equipment and storage medium | |
| CN103516802A (en) | Method and device for achieving seamless transference of across heterogeneous virtual switch | |
| CN106326226B (en) | The method and system of log-on data library service in a kind of public cloud | |
| US20160283275A1 (en) | Dynamic workload deployment for data integration services | |
| US20160188319A1 (en) | Cloud infrastructure for reducing storage facility code load suspend rate by redundancy check | |
| CN104317639B (en) | The method of the existing virtual machines of computer cloud platform adapter vCenter | |
| US11397622B2 (en) | Managed computing resource placement as a service for dedicated hosts | |
| CN104601680A (en) | Resource management method and device | |
| US9697266B1 (en) | Management of computing system element migration | |
| CN109165082A (en) | System smooth upgrading method based on container | |
| WO2021104156A1 (en) | Network service management method, device, and system | |
| US10645162B2 (en) | Filesystem I/O scheduler | |
| CN104363306A (en) | Private cloud management control method for enterprise | |
| CN104298761A (en) | Implementation method for master data matching between heterogeneous software systems | |
| CN106020795A (en) | Realization method and device of VDI desktop personal data disk | |
| CN109150964A (en) | A kind of transportable data managing method and services migrating method | |
| CN105262604B (en) | Virtual machine migration method and equipment | |
| US9870234B2 (en) | Automatic identification of returned merchandise in a data center | |
| US10680890B2 (en) | Non-disruptively splitting a coordinated timing network | |
| CN105978744A (en) | Resource allocation method, device and system | |
| US11416563B1 (en) | Query language for selecting and addressing resources | |
| US11829254B2 (en) | Techniques for scalable distributed system backups |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190108 |