CN107515776A - The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing - Google Patents
The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing Download PDFInfo
- Publication number
- CN107515776A CN107515776A CN201710588136.2A CN201710588136A CN107515776A CN 107515776 A CN107515776 A CN 107515776A CN 201710588136 A CN201710588136 A CN 201710588136A CN 107515776 A CN107515776 A CN 107515776A
- Authority
- CN
- China
- Prior art keywords
- container
- redaction
- current version
- mirror image
- group pod
- 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
-
- 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing.Node to be upgraded in the present invention obtains the first current version container in running status, the first current version container is created in a container group Pod, create redaction container corresponding with redaction mirror image, the redaction container is added in the container group Pod, the configuration information of the first current version container is obtained from the container group Pod, the configuration information is write to the redaction container of the container group Pod, the redaction container of the container group Pod is run, and the first current version container of the container group Pod is deleted.This kind of edition upgrading mode, because redaction container and the first current version container are packaged in same Pod, in running is replaced, the execution of business will not be interrupted, and updating speed is very fast, solving currently can not preferably realize the technical problem that business uninterruptedly upgrades.
Description
Technical field
The present invention relates to container technical field, more particularly to the uninterrupted upgrade method of business, node to be upgraded and readable deposit
Storage media.
Background technology
With the fast development of internet, in order to more rationally and server resource be efficiently used, in the market mostly can
Effective use by certain server using the realization of tactful or resource virtualizing to machine room resource, and container technique is also returned
Belonging to this row, the mode that container technique is shared as a kind of server resource realizes the virtualization of resource, and container technique
The speed of service and performance are better than existing virtualization mode virtual machine management program (Hypervisor), i.e., a kind of operation
Intermediate software layer between physical server and operating system.
For container technique, open source projects Docker is the relatively common application mode of in the market.Docker is that one kind is opened
The application container engine in source, it can be achieved also to be achieved that between different application using being bundled in a transplantable container
Isolation, but in the scene of upgrade application version, existing container platform goes realization to copy using automation operation and maintenance tools more
Shellfish and configuration file and installation kit are issued, and realize final edition upgrading.But this kind of upgrading mode must interrupt
The current version of operation is applied to realize reaching the standard grade for redaction application, and the updating speed of this kind upgrading mode is not ideal,
Therefore the technical problem that business uninterruptedly upgrades can not preferably be realized by existing.
The above is only used for auxiliary and understands technical scheme, does not represent and recognizes that the above is existing skill
Art.
The content of the invention
It is a primary object of the present invention to provide a kind of uninterrupted upgrade method of business, node to be upgraded and readable storage medium
Matter, it is intended to which solution can not preferably realize the technical problem that business uninterruptedly upgrades in the prior art.
To achieve the above object, the present invention provides a kind of uninterrupted upgrade method of business, the described method comprises the following steps：
Node to be upgraded obtains the first current version container in running status, and the first current version container creates
In a container group Pod；
Redaction container corresponding with redaction mirror image is created, the redaction container is added to the container group Pod
In；
The configuration information of the first current version container is obtained from the container group Pod, the configuration information is write
Enter the redaction container of the container group Pod；
The redaction container of the container group Pod is run, and the first current version container of the container group Pod is deleted
Remove.
Preferably, it is described to create redaction container corresponding with redaction mirror image, the redaction container is added to institute
Before stating in container group Pod, methods described also includes：
Application program is split as application component according to preset function border；
Generation micro services corresponding with the application component；
Obtain and distinguish corresponding redaction mirror image with each micro services；
Correspondingly, the redaction container of the operation container group Pod, is specifically included：
Run in the container group Pod and distinguish corresponding redaction container with each redaction mirror image.
Preferably, the acquisition distinguishes corresponding redaction mirror image with each micro services, specifically includes：
In response to the redaction mirror request of user's input, the first redaction mirror image corresponding with the first micro services is obtained,
The redaction mirror request is used to upgrade first micro services；
Correspondingly, corresponding redaction container is distinguished with each redaction mirror image in the operation container group Pod,
Specifically include：
Run the first redaction container corresponding with the first redaction mirror image in the container group Pod.
Preferably, it is described to create redaction container corresponding with redaction mirror image, the redaction container is added to institute
Before stating in container group Pod, methods described also includes：
Redaction mirror request is sent to mirror image warehouse, so that the mirror image warehouse sends the redaction mirror image to institute
Node to be upgraded is stated, the redaction mirror image is preserved in the mirror image warehouse.
Preferably, after the configuration information that the first current version container is obtained from the container group Pod, institute
Stating method also includes：
The configuration information of the first current version container is preserved into the node to be upgraded；
Or,
The configuration information of the first current version container is preserved into default distributed data base.
Preferably, after the redaction container of the operation container group Pod, methods described also includes：
When the redaction container for running the container group Pod breaks down, current version mirror image, the current version are obtained
This mirror image is stored in the node to be upgraded；
The second current version container corresponding with the current version mirror image is created, the second current version container is added
Add in the container group Pod；
First current version of preservation is obtained from the node to be upgraded or in the default distributed data base
The configuration information of container, the configuration information of the first current version container is write to the second current version of the container group Pod
This container；
Run the second current version container of the container group Pod, delete in the container group Pod break down it is new
Edition container.
Preferably, the redaction container of the operation container group Pod, and it is current by the first of the container group Pod
After edition container is deleted, methods described also includes：
The configuration information of the redaction container is obtained from the redaction container of the container group Pod, by the new edition
The configuration information of this container is preserved to default distributed data base.
In addition, to achieve the above object, the present invention also provides a kind of node to be upgraded, and the node to be upgraded includes：Deposit
Reservoir, processor and the uninterrupted ROMPaq of business that is stored on the memory and can run on the processor, institute
State the step of uninterrupted ROMPaq of business is arranged for carrying out the business uninterrupted upgrade method.
In addition, to achieve the above object, the present invention also provides a kind of readable storage medium storing program for executing, is deposited on the readable storage medium storing program for executing
The uninterrupted ROMPaq of business is contained, between realizing described business not when the uninterrupted ROMPaq of business is executed by processor
The step of disconnected upgrade method.
Edition upgrading mode in the present invention, due to redaction container be packaged in the first current version container it is same
In Pod, in running is replaced, the execution of business will not be interrupted, and updating speed is very fast, solving currently can not be compared with
The technical problem that business uninterruptedly upgrades is realized well.
Brief description of the drawings
Fig. 1 is the node structure schematic diagram to be upgraded for the hardware running environment that scheme of the embodiment of the present invention is related to；
Fig. 2 is the schematic flow sheet of the uninterrupted upgrade method first embodiment of business of the present invention；
Fig. 3 is the schematic flow sheet of the uninterrupted upgrade method second embodiment of business of the present invention；
Fig. 4 is the schematic flow sheet of the uninterrupted upgrade method 3rd embodiment of business of the present invention；
Fig. 5 is the schematic flow sheet of the uninterrupted upgrade method fourth embodiment of business of the present invention.
The realization, functional characteristics and advantage of the object of the invention will be described further referring to the drawings in conjunction with the embodiments.
Embodiment
It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, it is not intended to limit the present invention.
Reference picture 1, Fig. 1 are the node structure to be upgraded signal for the hardware running environment that scheme of the embodiment of the present invention is related to
Figure.
As shown in figure 1, the node to be upgraded can include：Processor 1001, such as CPU, communication bus 1002, Yong Hujie
Mouth 1003, network interface 1004, memory 1005.Wherein, communication bus 1002 is used to realize that the connection between these components is led to
Letter.User interface 1003 can include display screen (Display), and optional user interface 1003 can also connect including the wired of standard
Mouth, wave point.Network interface 1004 can optionally include wireline interface, the wave point (such as WI-FI interfaces) of standard.Deposit
Reservoir 1005 can be high-speed RAM memory or stable memory (non-volatile memory), such as magnetic
Disk storage.Memory 1005 optionally can also be the storage device independently of aforementioned processor 1001.
The node to be upgraded can be server or other physical equipments with network connection, for realize service computation,
Data storage or data exchange etc., and multiple nodes to be upgraded can be built into a cluster to realize the efficient of resource
Use.
, can be with it will be understood by those skilled in the art that the structure shown in Fig. 1 does not form the restriction for treating upgrade node
Including than illustrating more or less parts, either combining some parts or different parts arrangement.
As shown in figure 1, it can lead to as in a kind of memory 1005 of computer-readable storage medium including operating system, network
Believe module, Subscriber Interface Module SIM and the uninterrupted ROMPaq of business.
In the node to be upgraded shown in Fig. 1, network interface 1004 is mainly used in connecting other servers, with it is described other
Server enters row data communication；User interface 1003 is mainly used in connecting user terminal, enters row data communication with user terminal；Institute
State node to be upgraded and the uninterrupted ROMPaq of business stored in memory 1005 is called by processor 1001, and perform following
Operation：
The first current version container in running status is obtained, the first current version container is created in a container
In group Pod；
Redaction container corresponding with redaction mirror image is created, the redaction container is added to the container group Pod
In；
The configuration information of the first current version container is obtained from the container group Pod, the configuration information is write
Enter the redaction container of the container group Pod；
The redaction container of the container group Pod is run, and the first current version container of the container group Pod is deleted
Remove.
Further, processor 1001 can call the uninterrupted ROMPaq of the business stored in memory 1005, also hold
Row is following to be operated：
Application program is split as application component according to preset function border；
Generation micro services corresponding with the application component；
Obtain and distinguish corresponding redaction mirror image with each micro services；
Correspondingly, following operate also is performed：
Run in the container group Pod and distinguish corresponding redaction container with each redaction mirror image.
Further, processor 1001 can call the uninterrupted ROMPaq of the business stored in memory 1005, also hold
Row is following to be operated：
In response to the redaction mirror request of user's input, the first redaction mirror image corresponding with the first micro services is obtained,
The redaction mirror request is used to upgrade first micro services；
Correspondingly, following operate also is performed：
Run the first redaction container corresponding with the first redaction mirror image in the container group Pod.
Further, processor 1001 can call the uninterrupted ROMPaq of the business stored in memory 1005, also hold
Row is following to be operated：
Redaction mirror request is sent to mirror image warehouse, so that the mirror image warehouse sends the redaction mirror image to institute
Node to be upgraded is stated, the redaction mirror image is preserved in the mirror image warehouse.
Further, processor 1001 can call the uninterrupted ROMPaq of the business stored in memory 1005, also hold
Row is following to be operated：
The configuration information of the first current version container is preserved into the node to be upgraded；
Or,
The configuration information of the first current version container is preserved into default distributed data base.
Further, processor 1001 can call the uninterrupted ROMPaq of the business stored in memory 1005, also hold
Row is following to be operated：
When the redaction container for running the container group Pod breaks down, current version mirror image, the current version are obtained
This mirror image is stored in the node to be upgraded；
The second current version container corresponding with the current version mirror image is created, the second current version container is added
Add in the container group Pod；
First current version of preservation is obtained from the node to be upgraded or in the default distributed data base
The configuration information of container, the configuration information of the first current version container is write to the second current version of the container group Pod
This container；
Run the second current version container of the container group Pod, delete in the container group Pod break down it is new
Edition container.
Further, processor 1001 can call the uninterrupted ROMPaq of the business stored in memory 1005, also hold
Row is following to be operated：
The configuration information of the redaction container is obtained from the redaction container of the container group Pod, by the new edition
The configuration information of this container is preserved to default distributed data base.
The present embodiment is by such scheme, because redaction container and the first current version container are packaged in same Pod
In, in running is replaced, the execution of business will not be interrupted, and updating speed is very fast, and solving currently can not be preferable
Realize the technical problem that business uninterruptedly upgrades in ground.
Based on above-mentioned hardware configuration, the embodiment of the uninterrupted upgrade method of business of the present invention is proposed.
Reference picture 2, Fig. 2 are the schematic flow sheet of the uninterrupted upgrade method first embodiment of business of the present invention.
In the first embodiment, the uninterrupted upgrade method of the business comprises the following steps：
Step S10：Node to be upgraded obtains the first current version container in running status, first current version
Container is created in a container group Pod；
It is understood that in the normal operation environment of business, the first current version appearance is run in node to be upgraded
Device, also, the first current version container is pre-created in a container group Pod, and the container can run application, Mei Gerong
Safety that device is all mutually isolated therefore that operation process can be ensured.The container is operated in by a kind of virtualization technology to isolate
Different processes on node, so as to reach between process, process and host operating system are mutually isolated, are independent of each other.It is this mutual
Isolated process is just container, and it has a set of file system resource and dependent processes of oneself.For the Pod,
Kubernetes is that Pod is that the minimum deployment of system creation, scheduling and management is single in the container cluster management system that Google increases income
Position, rather than common minimum deployment unit is container.The container group Pod is a kind of arranged mode of container, suitable for tight coupling
The usage scenario of conjunction, such as, if can ensure that one group of service is all deployed on a node to be upgraded, container group Pod can be taken
Mode to the group service carry out layout, one group of service of such layout, cyberspace and storage volume can be shared, that is to say, that
Layout is carried out to the first current version container by the way of container group Pod, the first current version under container group Pod can be made
Container more easily carries out the shared with communicating of data with other containers under the Pod.
Certainly, multiple containers may be present under a Pod and share storage volume space and network namespace etc. together, so should
Multiple containers communication under Pod is more convenient, and the operating first current version container can be pre-created in an appearance
In device group Pod.
Step S20：Redaction container corresponding with redaction mirror image is created, the redaction container is added to the appearance
In device group Pod；
In the specific implementation, container corresponding to being created by mirror image, wherein, can be first by redaction mirror in order to obtain mirror image
As being stored in local, also mirror request can be carried out to the server for preserving the redaction mirror image.The mirror image is in container technique
In be multilayer read only layer unified visual angle, and container be then for mirror image add one it is top, and it is described it is top for it is readable can
Write layer.So create redaction container corresponding with redaction mirror image, it will be appreciated that can to the addition of one layer on redaction mirror image
Read layer is handled with adapting to follow-up practical business.It is therefore desirable to mirror image, container and the container in running status are distinguished, three
Person there is different characteristics, wherein, the container in running status includes the container, the process space also isolated and enters
The process run in journey space.And from actual motion angle, the redaction mirror image can directly be regarded as to a file, be used for
Create the redaction container, you can by the redaction container be interpreted as the redaction mirror image a process or one
Example, and may include executable file, depended software, the library text of the redaction container operation needs in the redaction mirror image
Part and configuration file etc..Wherein, the redaction container is completed to be later used to replace the first current version container in escalation process
Processing data.
It is understood that when creating redaction container corresponding with redaction mirror image, can also be by the redaction container
Added in the container group Pod, in this way, redaction container and the first current version container are run in same Pod.For institute
State Pod, it will be appreciated that it is a container group being made up of some containers, and some containers are closely connected each other, when some appearances
, can more easily shared data and communication, and can be used between some containers between some containers when device is in same Pod
Identical networking command space and network address etc..So when redaction container with the first current version container package same
When in Pod, the redaction container can be conveniently shared data and communication with the first current version container, be packaged in same
In one Pod and realize the key that business uninterruptedly upgrades.
It is understood that it can be different orders in container technique to create container from operation container, also generate not
Same effect.The redaction container according to corresponding to creating redaction mirror image, will obtain a redaction container, redaction in principle
Container is that one layer of readable writable layers are added on redaction mirror image, but the redaction container is not run.
It is understood that when running the redaction container, a run mode container will be obtained, now, except depositing
Outside redaction container, also in the presence of process run in the process space and the process space of isolation etc., so, when the redaction
After container is run, redaction container just has the ability of execution task.So once-existing point, redaction container with it is old
Edition container will be in run mode simultaneously.
Step S30：The configuration information of the first current version container is obtained from the container group Pod, is matched somebody with somebody by described in
Confidence breath writes the redaction container of the container group Pod；
In the specific implementation, the operation of container also needs to some configuration informations, the configuration information includes container operation letter
At least one of in breath, container storage information and container environmental variance, the container operation information refers to be produced in container running
Raw running status record, the container storage information refer to storage location and storage address of container etc., and configuration information can also wrap
Include carry path, issue port, process scheduling information and function services information of container etc..The first current version container is
Through the configuration information be present, in order to realize the automatic upgrading of container version and run redaction container, redaction container will be write
Enter the configuration information, the mode for the configuration information for writing direct the first current version container can be taken.It is additionally, since first
Current version container and redaction container are all in same Pod, so reading and the operation of write-in configuration information not shadow
Ring the first current version container and perform business.
Step S40：Run the redaction container of the container group Pod, and by the first current version of the container group Pod
Container is deleted.
In the specific implementation, the redaction container in the Pod can be run, the first current version in the Pod is deleted
This container, the upgrading of container version is also achieved that, legacy version container is substituted using redaction container.But come for user
Say, during this kind upgrades, business will not be interrupted, because redaction container is in same with the first current version container
In Pod, visual angle is used from user, the minimum shown to user is Pod using unit, during service execution by user
The container that will be unable to perceive carrying out practically in Pod is redaction container or the first current version container i.e. legacy version container,
So upgrading service will not be interrupted the execution of regular traffic, because will be in always in the presence of a container in node to be upgraded
Run mode, either redaction or current version.
It is understood that due to the service characteristic of container, this kind upgrades the execution speed of mode quickly, redaction container
Startup and the deletion of the first current version container be all to be realized with second level, entirely upgraded so user will not perceive
Journey.
The scheme that the present embodiment provides, because redaction container and the first current version container are packaged in same Pod,
In running is replaced, the execution of business will not be interrupted, and updating speed is very fast, and solving currently can not be preferably real
The technical problem that existing business uninterruptedly upgrades.
Reference picture 3, Fig. 3 is the schematic flow sheet of the uninterrupted upgrade method second embodiment of business of the present invention, based on above-mentioned
Embodiment shown in Fig. 2, propose the second embodiment of the uninterrupted upgrade method of business of the present invention.
In a second embodiment, before the step S20, methods described also includes：
Step S201：Application program is split as application component according to preset function border；
It is understood that splitting application in order to significantly more efficient to realize agile development and deployment, micro services can be passed through
The mode of framework (Microservice Architecture) realizes the fractionation to application program, be divided into realize it is single
Each application component of difference in functionality, and each application component collective effect plays a part of initial monomer applications program.Institute
It is overall applicability program or operation system to be divided to state application program, if not applying micro services framework to carry out function division,
The application program will carry out the processing of business, that is, the common operation of operation system instantly with the method for operation of monomer applications
Mode.For the preset function border, that is, how monomer applications program is subjected to preferably division and various ways be present,
The present embodiment is not restricted to this.Wherein, the preset function border can realize application component according to the principle of loose coupling high cohesion
Segmentation, the service characteristic of the loose coupling high cohesion refers to that a service is relied on the basis of other services solely reducing as far as possible
Function is on the spot realized, after the principle according to loose coupling and high cohesion is to realize segmentation, the complexity of interaction between module can be reduced
Degree.It moreover, when actual functional capability is split, both service-oriented function can simply be split, can also be carried out towards layering structure
Segmentation.
It should be appreciated that split the partial function that obtained application component is demonstrated by application program.
Step S202：Generation micro services corresponding with the application component；
In the specific implementation, this kind division framework carries out component clustering according to step S201 is, but implement to tool
In body application scenarios, it is also necessary to specific code realizes function, so, the application program can be entered according to preset function border
Row function is split, and each function has been switched to the code for meeting micro services framework, that is, is generated corresponding with the application component micro-
Service.
Step S203：Obtain and distinguish corresponding redaction mirror image with each micro services；
Certainly, in order to adapt to container technique and create container, micro services corresponding to the application component can be generated as
Mirror image forms in container environment for performing.In other words, by the way that micro services code is packed, you can the convenient portion at any time of generation
The mirror image of administration.Moreover, after redaction mirror image corresponding to generating, the redaction mirror image can be preserved, be easy to deployed in real time and prevent
Only server resource repeatedly generates.
The step S40 is specifically included：
Step S40 '：Run in the container group Pod and distinguish corresponding redaction container with each redaction mirror image, and
The first current version container of the container group Pod is deleted.
It is understood that after generation is with each micro services corresponding redaction mirror image respectively, you can create and described each
Redaction container corresponding to redaction mirror image, and each redaction container is added in the container group, then, by described in
Configuration information is write in each redaction container.Divide in this way, can run in the container group with each redaction mirror image
Not corresponding redaction container.So, the uninterrupted upgrade method first embodiment of business is contrasted, the present embodiment has multiple new editions
This container realizes corresponding application function respectively, that is, is divided into micro services, and first embodiment does not divide micro services then, only exists
One redaction container realizes a monomer applications program.Application program is divided into multiple application components, and generated respectively
A clear advantage be present, that is, exist in corresponding each redaction container, the mode that this kind divides multiple corresponding containers of component generation
When carrying out updating operation and business execution, it may not be necessary to coordinate influence of other service arrangements to this service in service layer, also
Deployment speed can be accelerated so that ensured sustained development deployment is possibly realized, and this is also a big advantage of micro services framework.
The scheme that the present embodiment provides, by redaction container and the first current version container in it ensure that first embodiment
On the basis of being packaged in same Pod, in running is replaced, the execution of business will not be interrupted, meanwhile, the present embodiment
In take micro services framework to application program carry out function division and respectively generation corresponding to redaction container, can also accelerate
The speed that business is performed and redeployed.
Reference picture 4, Fig. 4 is the schematic flow sheet of the uninterrupted upgrade method 3rd embodiment of business of the present invention, based on above-mentioned
Embodiment shown in Fig. 3, propose the 3rd embodiment of the uninterrupted upgrade method of business of the present invention.
In the third embodiment, the step S203 is specifically included：
Step S203 '：In response to the redaction mirror request of user's input, it is new to obtain corresponding with the first micro services first
Release image, the redaction mirror request are used to upgrade first micro services；
It is understood that when taking the framework mode in second embodiment to divide business realizing function, that is,
Say, the business separation towards function is realized by micro services framework, not only facilitates operation maintenance personnel to operate, also causes whole system
Reaction is rapider.Moreover, will be readily apparent, when monomer applications program is split into multiple micro services according to functional boundary,
During with generation with each micro services corresponding each redaction mirror image of difference, it can be held according to each redaction mirror image to upgrade redaction
Device, it is different from first embodiment, redaction container is upgraded according to the redaction mirror image of a monomer.
Since in the specific implementation, each redaction mirror image corresponding to being generated in second embodiment, then work as upgrading service
Demand simply upgrade partial function when, so that it may only obtain the part redaction mirror image in each redaction mirror image to realize part work(
The upgrading of energy, just reduce operand and transmission data that overall business performs.For example, when operation maintenance personnel will upgrade first in incognito
Corresponding to business during application component, a redaction mirror request will be sent, the redaction mirror request is used to upgrade described first
Micro services, then node to be upgraded can get the first redaction mirror image corresponding to first micro services.First redaction
It is local that mirror image can first be stored in node to be upgraded, also can first be stored in mirror image warehouse, by mirror image warehouse ask this first
Redaction mirror image is to get the mirror image.
The step S20 is specifically included：
Step S20 '：The first redaction container corresponding with the first redaction mirror image is created, first redaction is held
Device is added in the container group Pod；
It is understood that being different from step S20, the middle establishments of step S20 ' are corresponding with the first redaction mirror image
One redaction container, and created and each redaction in step S20 due to obtaining redaction mirror image corresponding with each micro services difference
Each redaction container corresponding to mirror image, so, the quantity of the container of establishment is different, and the present embodiment is simply selectively created
Build partial containers.
The step S30 is specifically included：
Step S30 '：The configuration information of the first current version container is obtained from the container group Pod, is matched somebody with somebody by described in
Confidence breath writes the first redaction container of the container group Pod；
In the specific implementation, after the first redaction container is created, the after the configuration information write-in of legacy version is created
In one redaction container.
The step S40 ' is specifically included：
Step S40 "：The first redaction container corresponding with the first redaction mirror image in the container group Pod is run,
And the first current version container of the container group Pod is deleted.
It is understood that after the first redaction mirror image is got, can create corresponding with the first redaction mirror image
The first redaction container, and by the first redaction container be added to the Pod in, to run first in the Pod
Redaction container.In this way, being also achieved that the local upgrading of container business, the portfolio of overall escalation process is reduced, simultaneously
The deployment that container is carried out by micro services framework also improves serious forgiveness, reduces business risk.
The scheme that the present embodiment provides, in response to the redaction mirror request of user's input, obtain and the first micro services pair
The the first redaction mirror image answered, the redaction mirror request is used to upgrade first micro services, and creates and the first new edition
First redaction container corresponding to this mirror image, the first redaction container is added in the container group Pod, from the appearance
The configuration information of the first current version container is obtained in device group Pod, the configuration information is write the container group Pod's
First redaction container, the first redaction container of the container group Pod is run, and it is current by the first of the container group Pod
Edition container is deleted, it should be noted that the first current version container now deleted is corresponding with the first redaction container
Container, that is, need the container upgraded.This kind of edition upgrading mode, micro services framework is taken in second the present embodiment is ensured
Function division is carried out to application program and respectively corresponding to generation on the premise of redaction container, the business that accelerates performs and again
The speed of deployment, meanwhile, realize that the part of corresponding container business upgrades for the function of required upgrading, without of overall importance
Upgrading, more reduce server operation pressure, also it is more convenient with it is quick.
Reference picture 5, Fig. 5 is the schematic flow sheet of the uninterrupted upgrade method fourth embodiment of business of the present invention, based on above-mentioned
Embodiment shown in Fig. 2, propose the fourth embodiment of the uninterrupted upgrade method of business of the present invention.
In the fourth embodiment, before the step S20, methods described also includes：
Step S20 "：Redaction mirror request is sent to mirror image warehouse, so that the mirror image warehouse is by the redaction mirror
The redaction mirror image is preserved as sending to the node to be upgraded, the mirror image warehouse.
It is understood that mirror image warehouse is the place for leaving image file concentratedly, it is easy to node to be upgraded to obtain mirror image,
When node to be upgraded uses mirror image, node to be upgraded sends redaction mirror request to mirror image warehouse, so that the mirror image storehouse
Storehouse sends the redaction mirror image to the node to be upgraded.By taking mirror image warehouse to deposit mirror image, facilitate node more
Mirror image is quickly obtained to realize the establishment of container, also saves the memory space for preserving mirror image.
Before the step S40, methods described also includes：
Step S40 " '：The configuration information of the first current version container is preserved into the node to be upgraded；
Or,
The configuration information of the first current version container is preserved into default distributed data base.
In the specific implementation, in order to flexibly tackle the establishment of redaction container and operation failure, the first current version can be preserved
The configuration information of this container, when the redaction container in the operation container group Pod breaks down, it what is preserved can be used to work as
The configuration information of preceding edition container to recover current version container again, that is to say, that the state rolled back to before upgrading service.Separately
Outside, the configuration information can be preserved in many ways, such as, can be directly by the configuration of the first current version container
Information is preserved to local, or, the configuration information can also be preserved into default distributed data base, above two preserving type
It is all more convenient quick in terms of the configuration information preserved is called.
Certainly, default distributed data base has that a variety of species databases are available, the default distribution in the present embodiment
Formula database can be ETCD databases, and the ETCD is one and increased income and the key assignments storage system of High Availabitity, is mainly used in sharing
Configuration and service discovery, node to be upgraded can be included using the characteristic of ETCD configuration sharing to realize in this embodiment
Other nodes also can be by the ETCD Database vendors data, naturally, node to be upgraded also can be obtained easily in one cluster
The configuration information.
After the step S40, the scheme also includes：
Step S401：When the redaction container for running the container group Pod breaks down, current version mirror image is obtained,
The current version mirror image is stored in the node to be upgraded；
It is understood that in order to prevent redaction container from breaking down to cause business can not assemble for training execution, can pass through
Pre-save the configuration information of the first current version container and set backup rollback mechanism to evade falling the business risk.
So when the redaction container for running the container group Pod breaks down, current version mirror image will be obtained, for again
Current version container corresponding to generation, the state that business process is returned to before upgrading.Wherein, current version mirror image can be stored in
In node to be upgraded, certainly, the current release image can be also stored in mirror image warehouse as redaction mirror image, needed
Conveniently pulled for container corresponding to establishment during use.
Step S402：The second current version container corresponding with the current version mirror image is created, it is current by described second
Edition container is added in the container group Pod；
In the specific implementation, in order to allow service condition to be returned to the state before not upgrading, current version appearance will be re-created
Device is that establishment obtains the second current version container, and then, the second edition container is also added in Pod, because first works as
Preceding edition container is also in the Pod originally.
Step S403：Described the first of preservation is obtained from the node to be upgraded or in the default distributed data base
The configuration information of current version container, the configuration information of the first current version container is write the of the container group Pod
Two current version containers；
It should be appreciated that after the second current version container after establishment is obtained, the second current version container is also
It is different from the first current version container presence in running status, because the second current version container is not actuated not to be had yet
Configuration information.The configuration information being pre-stored in node or ETCD database to be upgraded can be written to the second current version
Container.
Step S404：The second current version container of the container group Pod is run, deletes the hair in the container group Pod
The redaction container of raw failure.
It is understood that the second current version container of the container group Pod can be run, now, should be in operation shape
Second current version container of state is just consistent with the first current version container in running status, is also achieved that when upgrading
The state before not upgrading is returned to during failure.In order to reduce the operand of business and prevent node operation to be upgraded from pausing, can delete
Except the redaction container to break down.
It is understood that step S401 to S404 is described as being intended merely to conveniently understand after step S40, walk
Rapid S401 to S404 is a kind of backup rollback mechanism, for when running redaction container and breaking down to running environment progress and
When the disaster relief, the present embodiment is not restricted for triggering the time of origin of the backup rollback mechanism.Also, backup rollback mechanism is set
The availability and serious forgiveness of this kind upgrading mode can be improved, and reduces node and delays the risk of machine.
Further, next edition upgrading for convenience, the redaction container of the operation container group Pod, and will
After the first current version container of the container group Pod is deleted, methods described also includes, from the new edition of the container group Pod
The configuration information of the redaction container is obtained in this container, the configuration information of the redaction container is preserved to default distribution
Formula database.
It is understood that the distributed data base is used to share configuration, storage configuration and service discovery in a distributed manner.
Wherein, each node in ETCD databases stores complete data, and is ensured by the host-host protocol in ETCD
The data of each node are always maintained at unanimously.And in the present embodiment, will after the first current version container is deleted
The configuration information of redaction container is preserved into ETCD databases, also allows for analyzing in order to be managed for redaction container
Container with recovering the version.
The scheme that the present embodiment provides, by when the redaction container for running the container group Pod breaks down, passing through
The generation of the configuration information of current version mirror image and the first current version container pre-saved is in the second of running status and worked as
Preceding edition container, and be in running status before being somebody's turn to do the second current version container in running status and upgrading first is current
Edition container is consistent, so, the present embodiment is by before running status is returned to when operation troubles occurs does not upgrade, improving
The preparedness of equipment is horizontal in escalation process, also on the premise of it ensure that the stability of upgrading service process, while improves industry
The serious forgiveness of business escalation process.
In addition, the embodiment of the present invention also proposes a kind of readable storage medium storing program for executing, business is stored with the readable storage medium storing program for executing
Uninterrupted ROMPaq, following operation is realized when the uninterrupted ROMPaq of business is executed by processor：
Node to be upgraded obtains the first current version container in running status, and the first current version container creates
In a container group Pod；
Redaction container corresponding with redaction mirror image is created, the redaction container is added to the container group Pod
In；
The configuration information of the first current version container is obtained from the container group Pod, the configuration information is write
Enter the redaction container of the container group Pod；
The redaction container of the container group Pod is run, and the first current version container of the container group Pod is deleted
Remove.
Further, following operation is also realized when the uninterrupted ROMPaq of the business is executed by processor：
Application program is split as application component according to preset function border；
Generation micro services corresponding with the application component；
Obtain and distinguish corresponding redaction mirror image with each micro services；
Correspondingly, following operation is also realized：
Run in the container group Pod and distinguish corresponding redaction container with each redaction mirror image.
Further, following operation is also realized when the uninterrupted ROMPaq of the business is executed by processor：
In response to the redaction mirror request of user's input, the first redaction mirror image corresponding with the first micro services is obtained,
The redaction mirror request is used to upgrade first micro services；
Correspondingly, following operation is also realized：
Run the first redaction container corresponding with the first redaction mirror image in the container group Pod.
Further, following operation is also realized when the uninterrupted ROMPaq of the business is executed by processor：
Redaction mirror request is sent to mirror image warehouse, so that the mirror image warehouse sends the redaction mirror image to institute
Node to be upgraded is stated, the redaction mirror image is preserved in the mirror image warehouse.
Further, following operation is also realized when the uninterrupted ROMPaq of the business is executed by processor：
The configuration information of the first current version container is preserved into the node to be upgraded；
Or,
The configuration information of the first current version container is preserved into default distributed data base.
Further, following operation is also realized when the uninterrupted ROMPaq of the business is executed by processor：
When the redaction container for running the container group Pod breaks down, current version mirror image, the current version are obtained
This mirror image is stored in the node to be upgraded；
The second current version container corresponding with the current version mirror image is created, the second current version container is added
Add in the container group Pod；
First current version of preservation is obtained from the node to be upgraded or in the default distributed data base
The configuration information of container, the configuration information of the first current version container is write to the second current version of the container group Pod
This container；
Run the second current version container of the container group Pod, delete in the container group Pod break down it is new
Edition container.
Further, following operation is also realized when the uninterrupted ROMPaq of the business is executed by processor：
The configuration information of the redaction container is obtained from the redaction container of the container group Pod, by the new edition
The configuration information of this container is preserved to default distributed data base.
The present embodiment is by such scheme, because redaction container and the first current version container are packaged in same Pod
In, in running is replaced, the execution of business will not be interrupted, and updating speed is very fast, and solving currently can not be preferable
Realize the technical problem that business uninterruptedly upgrades in ground.
It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, it is not intended to limit the present invention.
It should be noted that herein, term " comprising ", "comprising" or its any other variant are intended to non-row
His property includes, so that process, method, article or system including a series of elements not only include those key elements, and
And also include the other element being not expressly set out, or also include for this process, method, article or system institute inherently
Key element.In the absence of more restrictions, the key element limited by sentence "including a ...", it is not excluded that including this
Other identical element also be present in the process of key element, method, article or system.
The embodiments of the present invention are for illustration only, do not represent the quality of embodiment.Herein, word
First, second and third use do not indicate that any order.Can be title by these word explanations.
Through the above description of the embodiments, those skilled in the art can be understood that above-described embodiment side
Method can add the mode of required general hardware platform to realize by software, naturally it is also possible to by hardware, but in many cases
The former is more preferably embodiment.Based on such understanding, technical scheme is substantially done to prior art in other words
Going out the part of contribution can be embodied in the form of software product, and the computer software product is stored in a storage medium
In (such as ROM/RAM, magnetic disc, CD), including some instructions to cause a station terminal equipment (can be mobile phone, computer, clothes
Be engaged in device, air conditioner, or network equipment etc.) perform method described in each embodiment of the present invention.
The preferred embodiments of the present invention are these are only, are not intended to limit the scope of the invention, it is every to utilize this hair
The equivalent structure or equivalent flow conversion that bright specification and accompanying drawing content are made, or directly or indirectly it is used in other related skills
Art field, is included within the scope of the present invention.
Claims (10)
1. a kind of uninterrupted upgrade method of business, it is characterised in that the described method comprises the following steps：
Node to be upgraded obtains the first current version container in running status, and the first current version container is created in one
In individual container group Pod；
Redaction container corresponding with redaction mirror image is created, the redaction container is added in the container group Pod；
The configuration information of the first current version container is obtained from the container group Pod, the configuration information is write into institute
State container group Pod redaction container；
The redaction container of the container group Pod is run, and the first current version container of the container group Pod is deleted.
2. the method as described in claim 1, it is characterised in that it is described to create redaction container corresponding with redaction mirror image,
Before the redaction container is added in the container group Pod, methods described also includes：
Application program is split as application component according to preset function border；
Generation micro services corresponding with the application component；
Obtain and distinguish corresponding redaction mirror image with each micro services；
Correspondingly, the redaction container of the operation container group Pod, is specifically included：
Run in the container group Pod and distinguish corresponding redaction container with each redaction mirror image.
3. method as claimed in claim 2, it is characterised in that the acquisition distinguishes corresponding redaction with each micro services
Mirror image, specifically include：
In response to the redaction mirror request of user's input, the first redaction mirror image corresponding with the first micro services is obtained, it is described
Redaction mirror request is used to upgrade first micro services；
Correspondingly, corresponding redaction container is distinguished with each redaction mirror image in the operation container group Pod, specifically
Including：
Run the first redaction container corresponding with the first redaction mirror image in the container group Pod.
4. the method as described in claim 1, it is characterised in that it is described to create redaction container corresponding with redaction mirror image,
Before the redaction container is added in the container group Pod, methods described also includes：
Redaction mirror request is sent to mirror image warehouse, is treated so that the mirror image warehouse sends the redaction mirror image to described
The redaction mirror image is preserved in upgrade node, the mirror image warehouse.
5. the method as described in claim 1, it is characterised in that the configuration information includes container operation information, container storage
At least one of in information and container environmental variance.
6. the method as described in claim 1, it is characterised in that described to obtain described first from the container group Pod current
After the configuration information of edition container, methods described also includes：
The configuration information of the first current version container is preserved into the node to be upgraded；
Or,
The configuration information of the first current version container is preserved into default distributed data base.
7. method as claimed in claim 6, it is characterised in that after the redaction container of the operation container group Pod,
Methods described also includes：
When the redaction container for running the container group Pod breaks down, current version mirror image, the current version mirror are obtained
As being stored in the node to be upgraded；
The second current version container corresponding with the current version mirror image is created, the second current version container is added to
In the container group Pod；
The first current version container of preservation is obtained from the node to be upgraded or in the default distributed data base
Configuration information, the second current version that the configuration information of the first current version container is write to the container group Pod holds
Device；
The second current version container of the container group Pod is run, deletes the redaction to break down in the container group Pod
Container.
8. the method as any one of claim 1 to 7, it is characterised in that the new edition of the operation container group Pod
This container, and by after the first current version container deletion of the container group Pod, methods described also includes：
The configuration information of the redaction container is obtained from the redaction container of the container group Pod, the redaction is held
The configuration information of device is preserved to default distributed data base.
9. a kind of node to be upgraded, it is characterised in that the node to be upgraded includes：Memory, processor and it is stored in described
On memory and the uninterrupted ROMPaq of business that can run on the processor, the uninterrupted ROMPaq of business is by institute
The step of business as any one of claim 1 to 8 uninterrupted upgrade method is realized when stating computing device.
10. a kind of readable storage medium storing program for executing, it is characterised in that be stored with business on the readable storage medium storing program for executing and uninterruptedly upgrade journey
Sequence, business as any one of claim 1 to 8 is realized not when the uninterrupted ROMPaq of business is executed by processor
The step of being interrupted upgrade method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710588136.2A CN107515776B (en) | 2017-07-18 | 2017-07-18 | Method for upgrading service continuously, node to be upgraded and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710588136.2A CN107515776B (en) | 2017-07-18 | 2017-07-18 | Method for upgrading service continuously, node to be upgraded and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107515776A true CN107515776A (en) | 2017-12-26 |
| CN107515776B CN107515776B (en) | 2021-04-09 |
Family
ID=60722579
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710588136.2A Active CN107515776B (en) | 2017-07-18 | 2017-07-18 | Method for upgrading service continuously, node to be upgraded and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107515776B (en) |
Cited By (36)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108683516A (en) * | 2018-03-14 | 2018-10-19 | 聚好看科技股份有限公司 | A kind of upgrade method of application example, device and system |
| CN109101342A (en) * | 2018-07-20 | 2018-12-28 | 北京百度网讯科技有限公司 | Distributed job control method for coordinating, device, computer equipment and storage medium |
| CN109150608A (en) * | 2018-08-22 | 2019-01-04 | 苏州思必驰信息科技有限公司 | Interface service upgrade method and system for voice dialogue platform |
| CN109165082A (en) * | 2018-08-21 | 2019-01-08 | 赛尔网络有限公司 | System smooth upgrading method based on container |
| CN109347652A (en) * | 2018-08-31 | 2019-02-15 | 北京奇艺世纪科技有限公司 | The service management and device of server cluster |
| CN109462657A (en) * | 2018-11-28 | 2019-03-12 | 中国科学院国家天文台 | A kind of expansible long-range observatory's system |
| CN109582441A (en) * | 2018-11-30 | 2019-04-05 | 北京百度网讯科技有限公司 | For providing system, the method and apparatus of container service |
| CN109597605A (en) * | 2018-10-22 | 2019-04-09 | 平安科技（深圳）有限公司 | Using micro services dispositions method, device, storage medium and terminal device |
| CN110119308A (en) * | 2018-02-07 | 2019-08-13 | 北京第一视角科技有限公司 | The system for managing extensive container application |
| CN110286930A (en) * | 2019-06-27 | 2019-09-27 | 腾讯科技（深圳）有限公司 | A kind of cloud platform upgrade method, device, terminal and storage medium |
| CN110569109A (en) * | 2019-09-11 | 2019-12-13 | 广州虎牙科技有限公司 | container updating method, control node and edge node |
| CN110633096A (en) * | 2018-06-21 | 2019-12-31 | 阿里巴巴集团控股有限公司 | Node control method and device, version control method and device and distributed system |
| CN110716826A (en) * | 2018-07-13 | 2020-01-21 | 阿里巴巴集团控股有限公司 | Cloud disk upgrading and scheduling method, cloud host, scheduling device and system |
| CN110781001A (en) * | 2019-10-23 | 2020-02-11 | 广东浪潮大数据研究有限公司 | Kubernetes-based container environment variable checking method |
| CN111241540A (en) * | 2020-01-16 | 2020-06-05 | 南京领行科技股份有限公司 | Service processing method and device |
| CN111324361A (en) * | 2018-12-14 | 2020-06-23 | 中国移动通信集团北京有限公司 | Application upgrading method and device |
| CN111522569A (en) * | 2020-05-09 | 2020-08-11 | 中瓴智行(成都)科技有限公司 | Hypervisor-based embedded multi-system upgrading method and computer-readable storage medium |
| CN111552496A (en) * | 2020-05-07 | 2020-08-18 | 上海道客网络科技有限公司 | System and method for realizing seamless upgrade of sidecar based on temporary container addition |
| CN111552494A (en) * | 2020-04-24 | 2020-08-18 | 星环信息科技（上海）有限公司 | Method, device, system and medium for managing container group |
| CN111638890A (en) * | 2019-03-01 | 2020-09-08 | Abb瑞士股份有限公司 | Online firmware upgrade of nodes in a process control system |
| CN111666088A (en) * | 2020-06-07 | 2020-09-15 | 中信银行股份有限公司 | Pod replacement method and device, electronic equipment and computer-readable storage medium |
| CN111880816A (en) * | 2020-07-24 | 2020-11-03 | 北京浪潮数据技术有限公司 | Kubernetes working load upgrading method, device and equipment |
| CN111897558A (en) * | 2020-07-23 | 2020-11-06 | 北京三快在线科技有限公司 | Kubernets upgrading method and device for container cluster management system |
| CN112199106A (en) * | 2020-10-20 | 2021-01-08 | 新华三信息安全技术有限公司 | Cross-version upgrading method and device and electronic equipment |
| CN112434008A (en) * | 2020-11-18 | 2021-03-02 | 星环信息科技(上海)股份有限公司 | Distributed database upgrading method, device and medium |
| CN112486536A (en) * | 2020-11-30 | 2021-03-12 | 山东浪潮通软信息科技有限公司 | Container-based application program upgrading method, device and medium |
| CN112685069A (en) * | 2019-10-20 | 2021-04-20 | 辉达公司 | Real-time updating of machine learning models |
| CN112799777A (en) * | 2020-12-31 | 2021-05-14 | 杭州朗澈科技有限公司 | Method for preheating scheduling in assembly line |
| CN113132154A (en) * | 2021-03-23 | 2021-07-16 | 北京网聚云联科技有限公司 | eBPF technology-based containerized application smooth upgrading method and system |
| CN113448609A (en) * | 2021-08-30 | 2021-09-28 | 恒生电子股份有限公司 | Container upgrading method, device, equipment and storage medium |
| CN113590146A (en) * | 2021-06-04 | 2021-11-02 | 聚好看科技股份有限公司 | Server and container upgrading method |
| CN113626054A (en) * | 2021-08-16 | 2021-11-09 | 聚好看科技股份有限公司 | Business service updating method and device |
| CN113672253A (en) * | 2021-07-29 | 2021-11-19 | 华人运通(上海)云计算科技有限公司 | Access method, device, equipment and medium for micro service system of vehicle |
| CN113760461A (en) * | 2021-09-07 | 2021-12-07 | 新华智云科技有限公司 | Version upgrading method and computer readable storage medium |
| CN116089154A (en) * | 2023-04-10 | 2023-05-09 | 苏州浪潮智能科技有限公司 | Cloud native application fault processing method, system, equipment and computer medium |
| WO2023185267A1 (en) * | 2022-04-02 | 2023-10-05 | 中兴通讯股份有限公司 | Microservice management method, electronic device, and computer readable storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1946226A (en) * | 2006-10-20 | 2007-04-11 | 华为技术有限公司 | Method, device for upgrading telecommunication equipment and upgrading engine unit |
| CN104410672A (en) * | 2014-11-12 | 2015-03-11 | 华为技术有限公司 | Method of upgrading network function virtualization application as well as method and device for forwarding business |
| CN105162884A (en) * | 2015-09-25 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Cloud management platform based on micro-service architecture |
| US20160142868A1 (en) * | 2014-09-03 | 2016-05-19 | CloudLeaf, Inc. | Systems, methods and devices for asset status determination |
| CN105740048A (en) * | 2016-01-26 | 2016-07-06 | 华为技术有限公司 | Image management method, device and system |
| US20160259811A1 (en) * | 2015-03-06 | 2016-09-08 | Superna Business Consulting, Inc. | Method and system for metadata synchronization |
| US20160274928A1 (en) * | 2015-03-20 | 2016-09-22 | International Business Machines Corporation | Virtual machine migration between hypervisor virtual machines and containers |
| CN106293820A (en) * | 2016-08-02 | 2017-01-04 | 山东大学 | Exploitation test O&M integral system, deployment, full dose and increment updating method |
| US20170054759A1 (en) * | 2015-08-19 | 2017-02-23 | Samsung Sds Co., Ltd. | Method and apparatus for security checking of image for container |
| CN106528224A (en) * | 2016-11-03 | 2017-03-22 | 腾讯科技（深圳）有限公司 | Content updating method and system for Docker container, and server |
| CN106598789A (en) * | 2016-11-30 | 2017-04-26 | 成都华为技术有限公司 | Container service disaster recovery method and device, production site and disaster recovery backup site |
| CN106686132A (en) * | 2017-02-06 | 2017-05-17 | 郑州云海信息技术有限公司 | Yunhai system deployment method and system |
-
2017
- 2017-07-18 CN CN201710588136.2A patent/CN107515776B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1946226A (en) * | 2006-10-20 | 2007-04-11 | 华为技术有限公司 | Method, device for upgrading telecommunication equipment and upgrading engine unit |
| US20160142868A1 (en) * | 2014-09-03 | 2016-05-19 | CloudLeaf, Inc. | Systems, methods and devices for asset status determination |
| CN104410672A (en) * | 2014-11-12 | 2015-03-11 | 华为技术有限公司 | Method of upgrading network function virtualization application as well as method and device for forwarding business |
| US20160259811A1 (en) * | 2015-03-06 | 2016-09-08 | Superna Business Consulting, Inc. | Method and system for metadata synchronization |
| US20160274928A1 (en) * | 2015-03-20 | 2016-09-22 | International Business Machines Corporation | Virtual machine migration between hypervisor virtual machines and containers |
| US20170054759A1 (en) * | 2015-08-19 | 2017-02-23 | Samsung Sds Co., Ltd. | Method and apparatus for security checking of image for container |
| CN105162884A (en) * | 2015-09-25 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Cloud management platform based on micro-service architecture |
| CN105740048A (en) * | 2016-01-26 | 2016-07-06 | 华为技术有限公司 | Image management method, device and system |
| CN106293820A (en) * | 2016-08-02 | 2017-01-04 | 山东大学 | Exploitation test O&M integral system, deployment, full dose and increment updating method |
| CN106528224A (en) * | 2016-11-03 | 2017-03-22 | 腾讯科技（深圳）有限公司 | Content updating method and system for Docker container, and server |
| CN106598789A (en) * | 2016-11-30 | 2017-04-26 | 成都华为技术有限公司 | Container service disaster recovery method and device, production site and disaster recovery backup site |
| CN106686132A (en) * | 2017-02-06 | 2017-05-17 | 郑州云海信息技术有限公司 | Yunhai system deployment method and system |
Cited By (51)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110119308A (en) * | 2018-02-07 | 2019-08-13 | 北京第一视角科技有限公司 | The system for managing extensive container application |
| CN108683516A (en) * | 2018-03-14 | 2018-10-19 | 聚好看科技股份有限公司 | A kind of upgrade method of application example, device and system |
| CN108683516B (en) * | 2018-03-14 | 2021-09-10 | 聚好看科技股份有限公司 | Application instance upgrading method, device and system |
| CN110633096A (en) * | 2018-06-21 | 2019-12-31 | 阿里巴巴集团控股有限公司 | Node control method and device, version control method and device and distributed system |
| CN110716826B (en) * | 2018-07-13 | 2023-11-24 | 阿里巴巴集团控股有限公司 | Cloud disk upgrading and scheduling method, cloud host, scheduling device and system |
| CN110716826A (en) * | 2018-07-13 | 2020-01-21 | 阿里巴巴集团控股有限公司 | Cloud disk upgrading and scheduling method, cloud host, scheduling device and system |
| CN109101342A (en) * | 2018-07-20 | 2018-12-28 | 北京百度网讯科技有限公司 | Distributed job control method for coordinating, device, computer equipment and storage medium |
| CN109101342B (en) * | 2018-07-20 | 2020-07-10 | 北京百度网讯科技有限公司 | Distributed job coordination control method and device, computer equipment and storage medium |
| CN109165082A (en) * | 2018-08-21 | 2019-01-08 | 赛尔网络有限公司 | System smooth upgrading method based on container |
| CN109150608A (en) * | 2018-08-22 | 2019-01-04 | 苏州思必驰信息科技有限公司 | Interface service upgrade method and system for voice dialogue platform |
| CN109347652A (en) * | 2018-08-31 | 2019-02-15 | 北京奇艺世纪科技有限公司 | The service management and device of server cluster |
| CN109597605A (en) * | 2018-10-22 | 2019-04-09 | 平安科技（深圳）有限公司 | Using micro services dispositions method, device, storage medium and terminal device |
| CN109462657A (en) * | 2018-11-28 | 2019-03-12 | 中国科学院国家天文台 | A kind of expansible long-range observatory's system |
| CN109582441A (en) * | 2018-11-30 | 2019-04-05 | 北京百度网讯科技有限公司 | For providing system, the method and apparatus of container service |
| CN111324361A (en) * | 2018-12-14 | 2020-06-23 | 中国移动通信集团北京有限公司 | Application upgrading method and device |
| CN111638890A (en) * | 2019-03-01 | 2020-09-08 | Abb瑞士股份有限公司 | Online firmware upgrade of nodes in a process control system |
| CN110286930B (en) * | 2019-06-27 | 2021-08-20 | 腾讯科技（深圳）有限公司 | Cloud platform upgrading method and device, terminal and storage medium |
| CN110286930A (en) * | 2019-06-27 | 2019-09-27 | 腾讯科技（深圳）有限公司 | A kind of cloud platform upgrade method, device, terminal and storage medium |
| CN110569109A (en) * | 2019-09-11 | 2019-12-13 | 广州虎牙科技有限公司 | container updating method, control node and edge node |
| CN110569109B (en) * | 2019-09-11 | 2022-05-31 | 广州虎牙科技有限公司 | Container updating method, control node and edge node |
| CN112685069A (en) * | 2019-10-20 | 2021-04-20 | 辉达公司 | Real-time updating of machine learning models |
| CN112685069B (en) * | 2019-10-20 | 2024-02-09 | 辉达公司 | Method and system for real-time updating of machine learning models |
| CN110781001B (en) * | 2019-10-23 | 2023-03-28 | 广东浪潮大数据研究有限公司 | Kubernetes-based container environment variable checking method |
| CN110781001A (en) * | 2019-10-23 | 2020-02-11 | 广东浪潮大数据研究有限公司 | Kubernetes-based container environment variable checking method |
| CN111241540A (en) * | 2020-01-16 | 2020-06-05 | 南京领行科技股份有限公司 | Service processing method and device |
| CN111552494A (en) * | 2020-04-24 | 2020-08-18 | 星环信息科技（上海）有限公司 | Method, device, system and medium for managing container group |
| CN111552494B (en) * | 2020-04-24 | 2021-05-11 | 星环信息科技(上海)股份有限公司 | Method, device, system and medium for managing container group |
| CN111552496A (en) * | 2020-05-07 | 2020-08-18 | 上海道客网络科技有限公司 | System and method for realizing seamless upgrade of sidecar based on temporary container addition |
| CN111522569B (en) * | 2020-05-09 | 2023-08-18 | 中瓴智行(成都)科技有限公司 | Hypervisor-based embedded multi-system upgrading method and computer readable storage medium |
| CN111522569A (en) * | 2020-05-09 | 2020-08-11 | 中瓴智行(成都)科技有限公司 | Hypervisor-based embedded multi-system upgrading method and computer-readable storage medium |
| CN111666088A (en) * | 2020-06-07 | 2020-09-15 | 中信银行股份有限公司 | Pod replacement method and device, electronic equipment and computer-readable storage medium |
| CN111897558A (en) * | 2020-07-23 | 2020-11-06 | 北京三快在线科技有限公司 | Kubernets upgrading method and device for container cluster management system |
| CN111880816A (en) * | 2020-07-24 | 2020-11-03 | 北京浪潮数据技术有限公司 | Kubernetes working load upgrading method, device and equipment |
| CN112199106A (en) * | 2020-10-20 | 2021-01-08 | 新华三信息安全技术有限公司 | Cross-version upgrading method and device and electronic equipment |
| CN112199106B (en) * | 2020-10-20 | 2022-08-26 | 新华三信息安全技术有限公司 | Cross-version upgrading method and device and electronic equipment |
| CN112434008A (en) * | 2020-11-18 | 2021-03-02 | 星环信息科技(上海)股份有限公司 | Distributed database upgrading method, device and medium |
| CN112486536A (en) * | 2020-11-30 | 2021-03-12 | 山东浪潮通软信息科技有限公司 | Container-based application program upgrading method, device and medium |
| CN112799777B (en) * | 2020-12-31 | 2024-04-05 | 深圳软通动力信息技术有限公司 | Preheating scheduling method in assembly line |
| CN112799777A (en) * | 2020-12-31 | 2021-05-14 | 杭州朗澈科技有限公司 | Method for preheating scheduling in assembly line |
| CN113132154B (en) * | 2021-03-23 | 2023-01-31 | 北京网聚云联科技有限公司 | eBPF technology-based containerized application smooth upgrading method and system |
| CN113132154A (en) * | 2021-03-23 | 2021-07-16 | 北京网聚云联科技有限公司 | eBPF technology-based containerized application smooth upgrading method and system |
| CN113590146B (en) * | 2021-06-04 | 2023-10-27 | 聚好看科技股份有限公司 | Server and container upgrading method |
| CN113590146A (en) * | 2021-06-04 | 2021-11-02 | 聚好看科技股份有限公司 | Server and container upgrading method |
| CN113672253A (en) * | 2021-07-29 | 2021-11-19 | 华人运通(上海)云计算科技有限公司 | Access method, device, equipment and medium for micro service system of vehicle |
| CN113672253B (en) * | 2021-07-29 | 2023-11-14 | 华人运通(上海)云计算科技有限公司 | Access method, device, equipment and medium for micro-service system of vehicle |
| CN113626054A (en) * | 2021-08-16 | 2021-11-09 | 聚好看科技股份有限公司 | Business service updating method and device |
| CN113448609A (en) * | 2021-08-30 | 2021-09-28 | 恒生电子股份有限公司 | Container upgrading method, device, equipment and storage medium |
| CN113760461B (en) * | 2021-09-07 | 2023-09-05 | 新华智云科技有限公司 | Version upgrading method and computer readable storage medium |
| CN113760461A (en) * | 2021-09-07 | 2021-12-07 | 新华智云科技有限公司 | Version upgrading method and computer readable storage medium |
| WO2023185267A1 (en) * | 2022-04-02 | 2023-10-05 | 中兴通讯股份有限公司 | Microservice management method, electronic device, and computer readable storage medium |
| CN116089154A (en) * | 2023-04-10 | 2023-05-09 | 苏州浪潮智能科技有限公司 | Cloud native application fault processing method, system, equipment and computer medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107515776B (en) | 2021-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107515776A (en) | The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing | |
| CN110535831B (en) | Kubernetes and network domain-based cluster security management method and device and storage medium | |
| US11164280B2 (en) | Graphics layer processing in a multiple operating systems framework | |
| US10209910B2 (en) | Copy-redirect on write | |
| US10938668B1 (en) | Safe deployment using versioned hash rings | |
| US9582319B2 (en) | Migrating virtual machines across network separated data centers | |
| US9128765B2 (en) | Assigning restored virtual machine based on past application usage of requesting user | |
| Kusnetzky | Virtualization: A manager's guide | |
| Doherty | SDN and NFV simplified: a visual guide to understanding software defined networks and network function virtualization | |
| US20210349699A1 (en) | Automatic containerization of operating system distributions | |
| WO2011156922A1 (en) | Method and system for workload distributing and processing across a network of replicated virtual machines | |
| CN112068936B (en) | Workflow management platform and workflow management system | |
| CN110088733A (en) | The layout based on accumulation layer of virtual machine (vm) migration | |
| US20110078681A1 (en) | Method and system for running virtual machine image | |
| US11704120B2 (en) | Out of band layer scrubbing | |
| US10042714B2 (en) | Point-in-time copy on write for golden image | |
| US9378039B2 (en) | Virtual machine storage replication schemes | |
| CN106201566A (en) | The rich big special hot upgrade method of software of profit and equipment | |
| CN103198090A (en) | A method and a system for optimizing storage allocation in a virtual desktop environment | |
| US11150919B2 (en) | Logging of scripts executed in an information technology workflow orchestration system | |
| CN103092674A (en) | Virtual machine system | |
| CN109684028B (en) | Method, device and equipment for separating operating system from user data | |
| US20140214956A1 (en) | Method and apparatus for managing sessions of different websites | |
| US9342527B2 (en) | Sharing electronic file metadata in a networked computing environment | |
| US20230342134A1 (en) | Hybrid approach to performing a lazy pull of container images |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 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 |