CN106603592B - A kind of method and moving apparatus for the application cluster migration based on service model - Google Patents
A kind of method and moving apparatus for the application cluster migration based on service model Download PDFInfo
- Publication number
- CN106603592B CN106603592B CN201510664774.9A CN201510664774A CN106603592B CN 106603592 B CN106603592 B CN 106603592B CN 201510664774 A CN201510664774 A CN 201510664774A CN 106603592 B CN106603592 B CN 106603592B
- Authority
- CN
- China
- Prior art keywords
- container
- resource
- dependence
- application cluster
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Abstract
The method and moving apparatus for the application cluster migration based on service model that the invention discloses a kind of.The present embodiment realizes all nodes of application cluster and the automation migration of dependence by service model；The Software Mirroring relied on by analyzing each host, installs relied on Software Mirroring in batches on the host at target data center, improves application cluster migration velocity, to reduce the downtime of cluster migration；For the environmental parameter of node profile template bound targets application cluster, the configuration file of target cluster is generated, to promote the Configuration File Migration efficiency of application cluster；Mirroring agent of the mirror image warehouse at target data center as target application cluster, obtains from the mirror image warehouse of source data center on demand and caches required mirror image, so that the mirror image of application cluster be accelerated to install.
Description
Technical field
The present invention relates to field of cloud calculation, in particular to the method and migration dress of the application cluster migration based on service model
It sets.
Background technique
Cloud application cluster, which refers to, provides one group of server of internet or enterprise application service based on cloud computing resource pool, leads to
It often include multiple server container nodes, each container node is made of hardware resource and software stack.Hardware resource includes void
Quasi- calculating, storage and Internet resources, are usually provided by the cloud resource pond of cloud data center.The software stack of container node is by mutual
Several layers software sharing, including operating system, platform software and application software of dependence etc..Fortune whether is saved according to container node
State when row, the container node of application cluster can be divided into two classes: one kind is stateless container node, as load balancer,
Web server etc., this kind of container node do not save data when operation；Another kind of is data capsule node, as cache server,
Database server etc. need to save runtime data.In application cluster migration, the involved resource of stateless container node,
The migration of software and configuration, and data capsule node is in addition to involved in stateless container node migrates other than content, need to also be into
The migration of row data.
Cloud application cluster usually needs move across data center when online commercial, failure disaster tolerance and computer room are moved
It moves, by the software of application cluster, configuration, data and topological structure from current data center bulk migration to new data center.
Due to the environmental difference between the complexity and data center of cloud application cluster, cloud application cluster is whole across data center
Body migration is extremely difficult, and existing application cluster moving method all has many problems:
1, it redeploys application cluster: redeploying application cluster, be related to cluster resource application, clustered software installation, collection
The links such as group network configuration, the migration of company-data and configuration file, many links all need manual intervention, and the time is long, easy
Error；
2, wide area network virtual machine (vm) migration: being migrated using V2V, can only realize the software and data Autonomic Migration Framework of single empty machine,
It cannot achieve configuration file Autonomic Migration Framework, cannot achieve the network structure migration of entire application cluster, and due to virtual machine mirror
As larger, across data center copy time is longer.
In recent years the container technique risen provides the system virtualization solution of the shared kernel of lightweight, such as
Docker had not only had the resource isolation characteristic of virtual machine, but also has had lightweight not available for virtual machine, high performance characteristics.With void
Quasi- machine is compared, and container sharing operation system kernel does not have Guest OS, and without hypervisor layers, more light weight, performance are higher,
Container engine supports layering mirror-image property mostly simultaneously, the entire software stack of application container node can be divided into multiple Image Planes
Secondary, by taking web server as an example, software stack can be divided into system software OS, platform software tomcat, application software such as webapp.war
Deng 3 mirror image levels.The image dependency on upper layer is in the mirror image of lower layer, and the mirror image of lower layer is shared for the mirror image on upper layer, thus greatly
The size for reducing image file greatly, so that the speed of the storage of mirror image, transmission and installation is obviously improved.However container technique is only
The software installation of single container node is only simplified, there is no the migrations for solving container node configuration file and runtime data to ask
Topic, also without solving the topological structure of entire cluster and the migration problem of network configuration.
Summary of the invention
One technical problem to be solved by the embodiment of the invention is that: when application cluster, container node configuration file, operation
The migration problem of data, topological structure and network configuration.
According to an aspect of an embodiment of the present invention, a kind of method of the application cluster migration based on service model provided
It include: to obtain the service model file of application cluster, and extract the resource deployment attribute of the application cluster in service model file
With container node state, wherein resource deployment attribute includes: Resource Dependence relationship, software dependence and topological connection relation；
The migration of application cluster is completed according to resource deployment attribute and container node state.
In one embodiment, the service model file of application cluster is obtained, and extracts the application in service model file
The resource deployment attribute and container node state of cluster, specifically include: application is obtained from the service model library of source data center
The service model file of cluster；Service model file is imported to the service model library at target data center；Extract service model text
Resource Dependence relationship, software dependence, topological connection relation and container node state in part.
In one embodiment, according to the Resource Dependence relationship of application cluster, software dependence, Topological dependence and
Container node information completes the migration of application cluster, specifically includes: the state of Resource Dependence relationship and software dependence is set
It is set to unbound, the state of topological connection relation is set as not setting up, the state of container node is set as not creating；According to
Container node state and Resource Dependence relationship are that target application cluster distributes resource；It is target application collection according to software dependence
Group's migration software；By the Data Migration of source application cluster to target application cluster；It is target application collection according to Topological dependence
Group carries out Topology connection configuration.
In one embodiment, it is that target application cluster distributes resource according to Resource Dependence relationship, specifically includes: according to money
Source dependence and container node state are in target application cluster container creation virtual machine；It is answered according to Resource Dependence relationship for target
It is rolled up with the virtual machine creating virtual data in cluster container；It is that target application cluster creates virtual net according to container node state
Network；It is that target application cluster container binds container resource according to Resource Dependence relationship.
In one embodiment, it is created according to Resource Dependence relationship and container node information in target application cluster container empty
Quasi- machine, specifically includes: according to the virtual container node state in container node state, container node and void in Resource Dependence relationship
The dependence of quasi- container node and the resource quota demand of container node calculate the resource requirement of virtual container node；According to
The resource requirement of virtual container node is that virtual container node creates virtual machine, binds virtual machine image, and will be in container node
Container node state be set as having created, wherein virtual machine image includes: system kernel and container engine.
In one embodiment, it is that target application cluster creates virtual data volume according to container node state, specifically includes:
It is what target application cluster created virtual data volume, and container node is relied on according to the virtual data volume in container node information
Virtual machine state is set as having created.
In one embodiment, creating virtual network according to Resource Dependence relationship for target application cluster includes: according to appearance
The virtual network container node state that device node relies on is what target application cluster created virtual network, and container node is relied on
Virtual network state is set as having created.
It in one embodiment, is that target application cluster container binds container resource according to Resource Dependence relationship, it is specific to wrap
It includes: according to the virtual machine dependence in Resource Dependence relationship, binding virtual data volume for container node, closed according to Resource Dependence
Book dependence in system binds virtual data volume for container node；It is relied on and is closed according to the network in Resource Dependence relationship
Virtual network is bound for container node by system；By virtual machine dependence, the state of book dependence and network dependence
It is set as having bound.
In one embodiment, it is target application cluster migration software according to software dependence, specifically includes: according to money
Reversed dependence, the dependence acquisition virtual machine appearance of container and container mirror image of virtual machine and container in the dependence of source
The container image listing of device node；The container engine for calling virtual machine obtains not from the container mirror image warehouse at target data center
The container mirror image deposited, if there is no specified container mirror image, container mirror image storehouses in the container mirror image warehouse at target data center
Library obtains the container mirror image being not present from the container mirror image warehouse of source data center；Container engine is according in Resource Dependence relationship
Image dependency relationship installation container mirror image file；For container bind container image file top layer mirror image, and by resource according to
Image dependency relationship in the relationship of relying is set as having bound.
In one embodiment, when the state of all image dependency relationships is to have bound, log-on data container section
The runtime data migration of point, by the Data Migration of source application cluster to target application cluster.
In one embodiment, the Data Migration of source application cluster to target application cluster is stopped into source application cluster, tool
Body includes: stopping source application cluster, obtains the data when operation of data capsule node in the application cluster of source；Collected according to source application
Data in group when the operation of data capsule node generate snapshot image；Snapshot image is uploaded to the container mirror of source data center
As warehouse；The container engine at target data center obtains mirror snapshot from source mirror image warehouse, and mirror snapshot importing is specified
Container node.
It in one embodiment, is that target application cluster carries out Topology connection configuration according to topological connection relation, it is specific to wrap
It includes: obtaining the link information in topological connection relation；Topology connection property parameters are configured for container；Start Topology connection attribute ginseng
Number, and the state of topological connection relation is set as having been established.
In one embodiment, the method for the present embodiment further include: when Resource Dependence relationship, software dependence and topology
When join dependency relationship is bound, set ready for the state of container node；When all container node states are both configured to
After ready, the migration of application cluster is completed in confirmation.
According to an aspect of the present invention, a kind of moving apparatus of the application cluster migration based on service model provided,
It is characterised by comprising: data obtaining module, for obtaining the service model file of application cluster, and extracts service model text
The resource deployment attribute and container node state of application cluster in part, wherein resource deployment attribute includes: that Resource Dependence closes
System, software dependence and topological connection relation；Cluster transferring module, for according to resource deployment attribute and container node state
Complete the migration of application cluster.
In one embodiment, data obtaining module includes: export subelement, imports subelement and information extraction unit,
Subelement is exported, for obtaining the service model file of application cluster from the service model library of source data center；It is single to import son
Service model file is imported the service model library at target data center by member；Information extraction unit, for extracting service model text
Resource Dependence relationship, software dependence, topological connection relation and container node state in part.
In one embodiment, cluster transferring module, comprising: state set unit, resource allocation unit, software migration list
Member, data migration unit and topological arrangement unit, wherein state set unit, for Resource Dependence relationship and software to be relied on
The state of relationship is set as unbound, and the state of topological connection relation is set as not setting up, and the state of container node is arranged
Not create；Resource allocation unit, for being target application cluster distribution money according to container node state and Resource Dependence relationship
Source；Software migration unit, for being target application cluster migration software according to software dependence；Data migration unit is used for
By the Data Migration of source application cluster to target application cluster；Topological arrangement unit, for being target according to Topological dependence
Application cluster carries out Topology connection configuration.
In one embodiment, resource allocation unit includes: asset creation subelement and resource binding unit, wherein money
Source creates subelement, for creating virtual machine in target application cluster container according to Resource Dependence relationship and container node state；
It is also used to be the virtual machine creating virtual data volume in target application cluster container according to Resource Dependence relationship；It is also used to according to appearance
Device node state is that target application cluster creates virtual network；Resource binding unit, for being target according to Resource Dependence relationship
Application cluster container binds container resource.
In one embodiment, asset creation subelement is specifically used for resource quota demand and appearance according to container node
The dependence of device node and empty machine node calculates the resource requirement of each empty machine node；Asset creation subelement is also used to basis
The resource requirement of virtual container node is that virtual container node creates virtual machine, binds virtual machine image, and by the container section
The state for the virtual machine that point relies on is set as having created, wherein the virtual machine image includes: system kernel and container engine.
In one embodiment, asset creation subelement, specifically for being rolled up according to the virtual data in container node information
Virtual data volume is created for target application cluster, and the state for the virtual machine that the container node relies on is set as having created.
In one embodiment, asset creation subelement, specifically for the virtual network container relied on according to container node
Node state is that target application cluster creates virtual network, and the virtual network state that container node relies on is set as having created
It builds.
In one embodiment, resource binding unit is closed specifically for being relied on according to the virtual machine in Resource Dependence relationship
System；It is also used to bind virtual data volume for container node；Be also used to be according to the book dependence in Resource Dependence relationship
Container node binds virtual data volume；It is also used to be bound according to the network dependence in Resource Dependence relationship for container node
Virtual network；It is also used to be set as having tied up by the state of virtual machine dependence, book dependence and network dependence
It is fixed.
In one embodiment, software migration unit, specifically for according to the virtual machine and container in Resource Dependence relationship
Reversed dependence, the dependence of container and container mirror image obtain the container image listing of virtual machine container node；Also use
In the container engine for calling virtual machine, the container mirror being not present on host is obtained from the container mirror image warehouse at target data center
Picture, if there is no specified container mirror image in the container mirror image warehouse at target data center, container mirror image warehouse is from source data
The container mirror image being not present is obtained in the container mirror image warehouse at center；It is also used to be closed according to the image dependency in Resource Dependence relationship
The file of system's installation container mirror image；It is also used to bind the top layer mirror image of container image file for container, and by Resource Dependence relationship
In image dependency relationship be set as having bound.
In one embodiment, data migration unit is also used to when the state of all image dependency relationships be to have bound
When, the runtime data migration of log-on data container node, by the Data Migration of source application cluster to target application cluster.
In one embodiment, data migration unit is specifically used for stopping source application cluster, obtains number in the application cluster of source
According to container node operation when data；It is also used to be generated according to the data in the application cluster of source when the operation of data capsule node
Snapshot image；Snapshot image is uploaded to the container mirror image warehouse of source data center；The container engine at target data center is from source
Mirror image warehouse obtains mirror snapshot, and mirror snapshot is imported to specified container node.
In one embodiment, topological arrangement unit, specifically for obtaining the link information in topological connection relation；Also use
In for container configure Topology connection property parameters；It is also used to start Topology connection property parameters, and by topological connection relation
State is set as having been established.
In one embodiment, the device of the present embodiment further includes cluster migration units, for when Resource Dependence relationship, soft
When part dependence and Topology connection dependence are bound, set ready for the state of container node；It is also used to work as institute
Have container node state be both configured to it is ready after, confirmation complete application cluster migration.
The present embodiment realizes all nodes of application cluster and the automation migration of dependence by service model；Pass through
The Software Mirroring that each host is relied on is analyzed, relied on Software Mirroring is installed in batches on the host at target data center,
Cluster migration velocity is improved, to reduce the downtime of cluster migration；For node profile template bound targets cluster
Environmental parameter, generate target cluster configuration file, to promote the Configuration File Migration efficiency of cluster；Target data center
Mirroring agent of the mirror image warehouse as target application cluster, obtained from the mirror image warehouse of source data center on demand and cache institute
The mirror image needed, accelerates the mirror image of cluster to install.
By referring to the drawings to the detailed description of exemplary embodiment of the present invention, other feature of the invention and its
Advantage will become apparent.
Detailed description of the invention
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this
Some embodiments of invention without any creative labor, may be used also for those of ordinary skill in the art
To obtain other drawings based on these drawings.
Fig. 1 shows typical cloud application aggregated structure figure.
Fig. 2 shows container application service illustratons of model.
Fig. 3 shows application cluster service model exemplary diagram.
Fig. 4 shows the process signal of one embodiment of the method for the application cluster migration of the invention based on service model
Figure.
Fig. 5 shows being migrated to service model for the method for the application cluster migration of the invention based on service model
The flow diagram of one embodiment of operation.
It is target cluster distribution resource that Fig. 6, which is shown in the method that the application cluster of the invention based on service model migrates,
Operation one embodiment flow diagram.
Fig. 7 shows the target cluster creation virtual machine in the method for the application cluster migration of the invention based on service model
Operation one embodiment flow diagram.
It is that application cluster creation is virtual that Fig. 8, which is shown in the method that the application cluster of the invention based on service model migrates,
The flow diagram of one embodiment of the operation of network.
It is application cluster binding container that Fig. 9, which is shown in the method that the application cluster of the invention based on service model migrates,
The flow diagram of one embodiment of the operation of resource.
Figure 10 shows the application cluster software migration in the method for the application cluster migration of the invention based on service model
Operation one embodiment flow diagram.
Figure 11 shows the fortune to stateful node in the method for the application cluster migration of the invention based on service model
The flow diagram of one embodiment of the operation of Data Migration when row.
Figure 12 shows the behaviour of the Topology connection configuration in the method for the application cluster migration of the invention based on service model
The flow diagram of one embodiment of work.
Figure 13 shows the behaviour of the target cluster starting in the method for the application cluster migration of the invention based on service model
The structural scheme of mechanism of one embodiment of work.
Figure 14 shows the structural schematic diagram of the moving apparatus of the application cluster migration of the invention based on service model.
Figure 15 shows the further embodiment of the moving apparatus of the application cluster migration of the invention based on service model
Structural schematic diagram.
Figure 16 shows the further embodiment of the moving apparatus of the application cluster migration of the invention based on service model
Structural schematic diagram.
Figure 17 shows the further embodiment of the moving apparatus of the application cluster migration of the invention based on service model
Structural schematic diagram.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation description, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.Below
Description only actually at least one exemplary embodiment be it is illustrative, never as to the present invention and its application or make
Any restrictions.Based on the embodiments of the present invention, those of ordinary skill in the art are not making creative work premise
Under every other embodiment obtained, shall fall within the protection scope of the present invention.
Unless specifically stated otherwise, positioned opposite, the digital table of the component and step that otherwise illustrate in these embodiments
It is not limited the scope of the invention up to formula and numerical value.
Simultaneously, it should be appreciated that for ease of description, the size of various pieces shown in attached drawing is not according to reality
Proportionate relationship draw.
Technology, method and apparatus known to person of ordinary skill in the relevant may be not discussed in detail, but suitable
In the case of, technology, method and apparatus should be considered as authorizing part of specification.
It is shown here and discuss all examples in, any occurrence should be construed as merely illustratively, without
It is as limitation.Therefore, the other examples of exemplary embodiment can have different values.
It should also be noted that similar label and letter indicate similar terms in following attached drawing, therefore, once a certain Xiang Yi
Quilt in a attached drawing then in subsequent attached drawing does not need that it is further discussed.
Fig. 1 gives the architecture diagram of a typical cloud application cluster, with reference to Fig. 1, it is assumed that a container application cluster is by 4
A container node is constituted, and is load balancing node a nginx, two Web server node WebApp+tomcat and one respectively
A database node mysql, application cluster are deployed on 3 virtual machines, wherein nginx node, two Web server nodes and
Mysql is deployed in respectively on a virtual machine, and the empty machine and container of entire cluster share the same IP subnet.Wherein mysql is saved
Point is stateful node, and carry virtual volume possesses runtime data, remaining node is stateless node.
Fig. 2 gives an abstract container application service model, describes the constituent element of container application service model.Hold
Device application service model is made of container list, software matrix, the Resources list and connection relationship and dependence, container, money
The node in source and the equal attribute model of software, node can possess one or more attributes, it is zero or more operation and zero or
Multiple relationships.The relationship of node and node is divided into two kinds: dependence and connection relationship, dependence define the installation of node
Order, connection relationship define the communication direction of node.Relationship can also possess attribute and operation, and simple relationship can be in source
Definition, complicated relationship can be defined individually in node.In addition, service model also possess some service model grades public attribute and
Public operation, such as mirror image repository URL, cloud resource management URL etc..Service model library includes a Web server, when service mould
After type is loaded by service model library, the attribute of the node of service model and relationship, state can by REST API Access and modification,
The operation of node and relationship can pass through REST API Calls.Wherein the state of container node include: do not create, it is ready and operation
In, it does not create and refers to that container is not present, it is ready to refer to that container has created, and the Resource Dependence of container, software rely on and connection
Dependence has been bound, and is that a container process has been turned in operation, can externally be provided service.
Fig. 3 gives the service model exemplary diagram of the container application cluster by taking Fig. 1 as an example, and this Figure illustrates 4 container sections
The dependence and connection relationship of point.Wherein Nginx container A relies on virtual machine A, network A and container mirror image Nginx, WebApp
Container A and WebApp container B are dependent on virtual machine B, network A and container mirror image WebApp, Mysql container A rely on virtual machine C,
Book A, network A, container mirror image Mysql and container snapshot MysqlA.Virtual machine A, virtual machine B virtual machine C are all relied on virtually
Machine mirror image Centos_DockerEngine, the virtual machine image encapsulate operating system CentOS base edition and container engine
DockerEngine.Container mirror image WebApp rely on container mirror image Tomcat, container mirror image Nginx, container mirror image Tomcat and
Container mirror image Mysql all relies on container mirror image CentosExt, CentosExt mirror image and encapsulates what upper layer container mirror image was relied on
System library.
The definition of the description languages such as YAML, xml or json can be used in service model, and can be loaded into service model engine,
The class and object (such as Java) for being mapped to language-specific can directly pass through the object reference of language level in service model engine
Attribute, operation and the relationship of service model are accessed, while service model engine externally provides REST api interface, allows external mould
Block passes through the REST API remote access service model based on HTTP.
By taking container NginxA as an example, the nodal analysis method defined using YAML is as follows:
Container:
ID:Nginx container A
Type: Nginx container
State: it does not create
Runtime data: nothing
Network attribute: { network mode: host, host ip }
Quota attribute: CPU core calculation: 2, memory size: 2G, disk size: 1G }
Operating list:
Create container
Start container
Stop container
Resource Dependence list:
Fictitious host computer: { ID: empty machine A, state: unbound ,-operation: bind empty machine }
Virtual network: { ID: network A, state: unbound ,-operation: binding network }
Software relies on list:
Container mirror image: { ID: container mirror image Nginx, state: unbound ,-operation: binding mirror image }
Connection relation list:
Back-end proxy connection: { ID: back-end proxy connection 1, state: not setting up ,-operation: configuration back-end proxy, connection belong to
Property: { front-end port: 80, rear end IP:<WebApp container A network attribute host ip>, back-end ports:<WebApp container A net
Network attribute host port > } }
Back-end proxy connection: { ID: back-end proxy connection 2, state: not setting up ,-operation: configuration back-end proxy, connection belong to
Property: { front-end port: 80, rear end IP:<WebApp container B network attribute host ip>, back-end ports:<WebApp container B net
Network attribute host port > } }
The model of WebApp container A is defined as follows:
Container:
ID:WebApp container A
Type: WebApp container
State: it does not create
Runtime data: nothing
Network attribute: { network mode: bridge joint, container IP, container port, host ip, host port, port mapping }
Quota attribute: CPU core calculation: 2, memory size: 2G, disk size: 5G }
Container operation list:
Create container
Start container
Stop container
Resource Dependence list:
Fictitious host computer: { ID: empty machine B, state: unbound ,-operation: bind empty machine }
Virtual network: { ID: network A, state: unbound ,-operation: binding network }
Software relies on list:
Container mirror image: { ID: container mirror image WebApp, state: unbound ,-operation: binding mirror image }
Connection relation list:
Database connection: { ID: database connection 1, state: not setting up ,-operation: database connection configuration, attribute: { number
According to library IP:<Mysql container A network attribute host ip>,
Database IP:<Mysql container A network attribute host port>,
Database name:<Mysql container A Database Properties database name>,
Database account:<Mysql container A Database Properties database account>,
Database password:<Mysql container A Database Properties database password>} }
The service model of Mysql container A is defined as follows:
Container:
ID:Mysql container A
Type: Mysql container
State: it does not create
Runtime data: have
Capacitor network attribute: Intranet IP, Intranet port, outer net IP, outer net port: 3306, port mapping }
Container quota attribute: CPU core calculation: 4, memory size: 4G, disk size: 50G }
Database Properties: { database name, database account, database password }
Container operation list:
Create container
Start container
Stop container
Export container snapshot
Resource Dependence list:
Fictitious host computer: { ID: empty machine C, state: unbound, operation: bind empty machine }
Book: { ID: book A, state: unbound, operation: binding data volume }
Virtual network: { ID: network A, state: unbound, operation: binding network }
Software relies on list:
Container mirror image: { ID: container mirror image Mysql, state: unbound, operation: binding mirror image }
Container snapshot: { ID: container snapshot MysqlA, state: unbound, operation: binding mirror image }
Fig. 4 is the flow chart of the method for the present invention one embodiment.As shown in figure 4, the method for the embodiment includes:
Step S401, obtains the service model file of application cluster, and extracts application cluster in service model file
Resource deployment attribute and container node state, wherein resource deployment attribute include: Resource Dependence relationship, software dependence and
Topological connection relation.
Step S402 completes the migration of application cluster according to resource deployment attribute and container node state.
The present embodiment realizes all nodes of application cluster and the automation migration of dependence by service model；Pass through
The Software Mirroring that each host is relied on is analyzed, relied on Software Mirroring is installed in batches on the host at target data center,
Cluster migration velocity is improved, to reduce the downtime of cluster migration；For node profile template bound targets cluster
Environmental parameter, generate target cluster configuration file, to promote the Configuration File Migration efficiency of cluster；Target data center
Mirroring agent of the mirror image warehouse as target application cluster, obtained from the mirror image warehouse of source data center on demand and cache institute
The mirror image needed, accelerates the mirror image of cluster to install.
The method that the application cluster migration based on service model of invention is explained in detail below:
One, service model is migrated.
With reference to Fig. 5, service model is migrated in the method for the application cluster migration based on service model, is specifically included
Following steps:
Step S501 exports the service model file of application cluster from the service model library of source data center.
Service model file is imported the service model library at target data center by step S502；Extract service model file
In Resource Dependence relationship, software dependence, topological connection relation and container node state, and by all container node states
It is set as " not setting up ", and sets unbound for the state of Resource Dependence relationship and software dependence, Topology connection is closed
The state of system is set as not setting up, and the state of container node is set as not creating.
In one embodiment, the operation migrated to service model can also include:
Step S503 modifies the cloud resource management URL of service model, and cloud resource management URL is directed toward in target data
The management URL of heart administration agent.
Step S504 modifies the URL attribute in the mirror image warehouse of application model, and the URL attribute in mirror image warehouse is directed toward mesh
Mark the mirror image repository URL of data center.
Two, resource is distributed for target cluster in the method for the application cluster migration based on service model, wherein Fig. 6 is referred to,
It is of the invention be target cluster distribution resource the step of may include following operation:
Step S601 creates virtual machine for target cluster.
Step S602 creates virtual memory for target cluster.
Step S603 creates virtual network for target cluster.
Step S604 is target cluster bonding network network resource.
Following operation is specifically included with reference to Fig. 7, the operating procedure S601 for creating virtual machine for target cluster:
Step S701 calls the virtual machine node query interface of service model engine, and obtaining all container node states is
The virtual machine of " not creating ".
Step S702 is calculated according to the dependence of the resource quota of container node and container node and virtual machine node
The resource requirement of each virtual machine node, wherein resource requirement is the sum of the specification of each container on the virtual machine, including
CPU core number, virutal machine memory size and disk size etc..
Step S703 manages platform, such as the void of cloud computing management platform openstack by the cloud resource of administration agent
Quasi- machine query interface API obtains the virtual machine specification that resource specification is not less than resource requirement.
Step S704 calls the creation of virtual machine node to operate, such as the interface that service model can be called to act on behalf of, according to
Virtual machine image mark, resources of virtual machine specification ID are that the virtual machine node distributes virtual machine, bind virtual machine image, and will hold
Container node state in device node is set as having created, and wherein virtual machine image includes: system kernel and container engine.
Step S705 updates the information such as IP address, the host name of virtual machine node, and will after virtual machine creating success
The state of container node is set as " creation ", to complete the creation of virtual machine.
With reference to Fig. 8, virtual memory 602 is created for target cluster and specifically includes following operation:
Step S801 obtains the virtual data that container node state is " not creating " and rolls up, such as can call service model
Dummy storage node query interface inquired and obtained.
Step S802, call virtual machine memory node creation interface, such as can according to virtual data roll up size and
Type is called and creates.
Step S803 obtains the virtual network node that state is " not creating ", such as can be by calling service model
Dummy storage node query interface is realized.
Step S804 calls " creation " of each virtual network node to operate, such as can be according to information such as network bandwidths
It realizes and calls and create.
Step S805 is flat by the cloud resource management in service model engine internal invocation target data center management agency
The network management api interface of platform creates virtual network.
Step S806, the network address of update virtual network node, gateway IP, subnet are covered after virtual network creates successfully
The information such as code, VLAN ID (Virtual Local Area Network, VlAN), by the state of virtual network node
It is set as " creation ".
With reference to Fig. 9, it can specifically include following steps for the step S603 of target cluster bonding network network resource:
Step S901 obtains container node state and is the Resource Dependence relationship of " unbound ", such as can call service mould
The virtual query interface of type is inquired and is obtained.
Step S902 executes binding virtual machine operations, updates the host of container node for the dependence of virtual machine
IP creates container by the creation container joint of the container engine of administration agent on a virtual machine, and it is relevant initial to carry out container
Change configuration, such as may include the environmental variance of container, resource quota etc., the state of the dependence of virtual machine is changed to "
Binding ".
Step S903 executes binding data volume operation, passes through the carry data of container engine for book dependence
Cigarette mouth is container carry book, the state of dependence is changed to " binding ".
Step S904 executes binding Virtual Network Operations, is matched first by container Engine-Network for network dependence
Interface dispensing containers network is set, is container allocation Microsoft Loopback Adapter, the Microsoft Loopback Adapter of container is bridged to the host bridge of virtual machine
On, the host ip of container and host port are then added to by empty machine network by the network management interface that cloud resource manages platform
VLAN in, the state of network dependence is set as " binding " by the network attribute of final updating container node.
Three, application cluster software migration.
With reference to Figure 10, carrying out in the method for the application cluster migration of the invention based on service model to application cluster is soft
Part migrate the step of may include:
Step S1001 is obtained according to the dependence of the reversed dependence of fictitious host computer and container, container and container mirror image
Container image listing to be mounted is needed to each virtual machine node.
Step S1002 calls the container engine on each empty machine, downloads from the container mirror image warehouse at target data center
The container mirror image being not present on empty machine.
Step S1003, if there is no specified container mirror image, containers in the container mirror image warehouse at target data center
Wall hanging is first downloaded from the container mirror image warehouse of source data center and saves container mirror image in mirror image warehouse.
Mirror image layering is installed to host according to image dependency relational hierarchy in container mirror image by step S1004, container engine
Local mirror image warehouse in, local mirror image warehouse usually by certain support hierarchical file structure union file system such as AUFS
Or BTRFS is realized.
Step S1005 calls the binding mirror image operation of container engine, binds top level container mirror image for each container, and will
Container image dependency relationship is set as " binding "
Step S1006 illustrates application cluster when the container image dependency relationship of all container nodes is " binding "
Stateless node and the software of stateful node installed, can star the runtime data migration of stateful node
Operation.
In one embodiment, the operation that the runtime data of stateful node migrates specifically can wrap with reference to Figure 11
It includes:
Step S1101 stops source application cluster.
Step S1102 exports the runtime data of stateful node in the application cluster of source, by calling leading for container engine
The runtime data of stateful container is exported to snapshot image by snapshot operation out, wherein snapshot image is a kind of special appearance
Device mirror image, incremental data when only including the operation in container.
Step S1103 uploads to snapshot image in the container mirror image warehouse of source data center.
Step S1104, the container engine at target data center request to obtain snapshot image into target mirror image warehouse.
Mirror snapshot is downloaded from the mirror image warehouse of source in step S1105, target mirror image warehouse.
Mirror snapshot is imported into specified container by step S1106, container engine, to realize that runtime data moves
It moves.
With reference to Figure 12, the operation of the Topology connection configuration of the present embodiment can specifically include following steps:
Step S1201 calls the Topology connection query interface of service-Engine, and the state in each container node that obtains is " not
The Topology connection list of foundation ".
The connection attribute parameter of Topology connection, such as the back-end proxy with reference to above-mentioned Nginx container A is arranged in step S1202
Content in "<>" in connection attribute, can will be substituted for the attribute value of corresponding node in model by connection definition, and<WebApp holds
Device A. network attribute host ip > expression takes the host ip attribute of the network attribute collection of WebApp container A node, it is assumed that is
10.10.10.11,<WebApp container A network attribute host port>indicates to take the network attribute collection of WebApp container A node
Host port attribute, it is assumed that be 8080.Then instantiate after connection attribute be front-end port: 80, rear end IP:
10.10.10.10 back-end ports: 8080 }.
Step S1103 executes connection configuration operation, each topological connection relation is owned by a configuration operation, the configuration
Operation is bundled with a provisioning API of administration agent, and the REST API of the container engine of administration agent is called to execute corresponding container
Connection configure operation.Extension container engine is needed exist for, the script configuration REST API in container is provided, specified containers are executed
On specified configuration script.Such as: execute the REST API of the rear end nginx connection configuration are as follows:
Http: //<container host ip>:<container engine port>/<Container ID>/configshell/? shellfile=
Nginx_config.sh&fe_port=80&be_ip=10.10.10.10&be_port=808 0.
After container engine receives the REST API request, pipeline mechanism or SSH are passed through according to the Container ID in URI parameter
The specified container of mechanism connection, executes the specified configuration script nginx_config.sh in container.
The state of topological connection relation is changed to " having been established " after configuration script runs succeeded by step S1204.
Five, target application cluster starts
With reference to Figure 13, the operation of the invention to the starting of target application cluster can specifically include following steps:
Step S1301, when the Resource Dependence relationship, software dependence and Topology connection dependence of container node are tied up
Periodically, the state of container node is set as " ready ".
Step S1302, according to the Topology connection dependence of container, successively starting state is the container of " ready ", and adjusts
Start container after container node starting with the REST API of container engine the state of container node is set to " in operation ".First
Node of the starting with reference to dependence least significant end in Fig. 1, that is, the root node being relied on, the present embodiment are Mysql container A node,
Then successively start the dependence child node of root node, WebApp container A node and WebApp container B node, finally starting topology
The top mode of dependence, that is, Nginx container A node.
Step S1303 completes the migration work of entire application cluster after all container nodes starting of cluster
Figure 14 is the structure of one embodiment of the moving apparatus of the application cluster migration of the invention based on service model
Schematic diagram.With reference to Figure 14, the device of the present embodiment includes, comprising: data obtaining module 1401 and cluster transferring module 1402.
Data obtaining module 1401 for obtaining the service model file of application cluster, and extracts in service model file
Application cluster resource deployment attribute and container node state, wherein resource deployment attribute includes: Resource Dependence relationship, soft
Part dependence and topological connection relation；
Cluster transferring module 1402, for completing moving for application cluster according to resource deployment attribute and container node state
It moves.
In one embodiment, with reference to Figure 15, data obtaining module 1401 includes: export subelement 1501, imports son list
Member 1502 and information extraction unit 1503.
Subelement 1501 is exported, for obtaining the service model text of application cluster from the service model library of source data center
Part.
Subelement 1502 is imported, service model file is imported to the service model library at target data center.
Information extraction unit 1503, for extracting the Resource Dependence relationship in service model file, software dependence, opening up
Flutter connection relationship and container node state.
In one embodiment, with reference to Figure 16, cluster transferring module 1402 includes: state set unit 1601, resource point
With unit 1602, software migration unit 1603, data migration unit 1604 and topological arrangement unit 1605.
Wherein,
State set unit 1601, for setting unbound for the state of Resource Dependence relationship and software dependence,
The state of topological connection relation is set as not setting up, the state of container node is set as not creating.
Resource allocation unit 1602, for being the distribution of target application cluster according to container node state and Resource Dependence relationship
Resource.
Software migration unit 1603, for being target application cluster migration software according to software dependence.
Data migration unit 1604, for by the Data Migration of source application cluster to target application cluster.
Topological arrangement unit 1605, for being that target application cluster carries out Topology connection configuration according to Topological dependence.
In one embodiment, with reference to Figure 17, resource allocation unit 1602 includes: asset creation subelement 1701 and resource
Binding unit 1702.
Asset creation subelement 1701, for being held according to Resource Dependence relationship and container node state in target application cluster
Device creates virtual machine；It is also used to be the virtual machine creating virtual data in target application cluster container according to Resource Dependence relationship
Volume；It is also used to be that target application cluster creates virtual network according to Resource Dependence relationship.
Resource binding unit 1702, for being that target application cluster container binds container resource according to Resource Dependence relationship.
In one embodiment, asset creation subelement 1701 be specifically used for according to the resource quota demand of container node with
And container node and the dependence of empty machine node calculate the resource requirement of each empty machine node；Asset creation subelement is also used to
It is that virtual container node creates virtual machine according to the resource requirement of virtual container node, binds virtual machine image, and by the appearance
The state for the virtual machine that device node relies on is set as having created, wherein the virtual machine image includes: that system kernel and container draw
It holds up.
In one embodiment, asset creation subelement 1701 is specifically used for according to the virtual data in container node information
Volume is that target application cluster creates virtual data volume, and the virtual machine state that container node relies on is set as having created.
In one embodiment, asset creation subelement 1701, specifically for according to the virtual net in container node state
Network container node state is that target application cluster creates virtual network, and sets the virtual network state that container node relies on to
It has created.
In one embodiment, resource binding unit 1702 is specifically used for being relied on according to the virtual machine in Resource Dependence relationship
Relationship；It is also used to bind virtual data volume for container node；It is also used to according to the book dependence in Resource Dependence relationship,
Virtual data volume is bound for container node；It is also used to be tied up according to the network dependence in Resource Dependence relationship for container node
Determine virtual network；It is also used to set the state of virtual machine dependence, book dependence and network dependence to
Binding.
In one embodiment, software migration unit 1603, specifically for according in Resource Dependence relationship virtual machine with
The dependence of the reversed dependence of container, container and container mirror image obtains the container image listing of virtual machine container node；
It is also used to call the container engine of virtual machine, the container being not present on host is obtained from the container mirror image warehouse at target data center
Mirror image, if there is no specified container mirror image in the container mirror image warehouse at target data center, container mirror image warehouse is from source number
According to obtaining the container mirror image being not present in the container mirror image warehouse at center；It is also used to according to the image dependency in Resource Dependence relationship
The file of relationship installation container mirror image；It is also used to bind the top layer mirror image of container image file for container, and Resource Dependence is closed
Image dependency relationship in system is set as having bound.
In one embodiment, data migration unit 1604 is used to when the state of all image dependency relationships be to have tied up
Periodically, the runtime data migration of log-on data container node, moves to target application for the runtime data of source application cluster
Cluster.
In one embodiment, data migration unit 1604 is specifically used for stopping source application cluster, obtains source application cluster
The data when operation of middle data capsule node；It is also used to according to the data in the application cluster of source when the operation of data capsule node
Generate snapshot image；Snapshot image is uploaded to the container mirror image warehouse of source data center；It is also used to the appearance at target data center
Device engine obtains mirror snapshot from source mirror image warehouse, and mirror snapshot is imported to specified container node.
In one embodiment, topological arrangement unit 1605 is specifically used for obtaining the link information in topological connection relation；
It is also used to configure Topology connection property parameters for container；It is also used to start Topology connection property parameters, and Topology connection is closed
The state of system is set as having been established.
In one embodiment, with reference to Figure 16, moving apparatus in this implementation can be with further include: cluster migration units
1606, for when Resource Dependence relationship, software dependence and Topology connection dependence are bound, by the shape of container node
State is set as ready；It is also used to after all container node states are both configured to ready, moving for application cluster is completed in confirmation
It moves.
Those of ordinary skill in the art will appreciate that realizing that all or part of the steps of above-described embodiment can pass through hardware
Complete, relevant hardware can also be instructed to complete by program, program can store in a kind of computer-readable storage
In medium, storage medium mentioned above can be read-only memory, disk or CD etc..
The foregoing is merely presently preferred embodiments of the present invention, is not intended to limit the invention, it is all in spirit of the invention and
Within principle, any modification, equivalent replacement, improvement and so on be should all be included in the protection scope of the present invention.
Claims (24)
1. a kind of method of the application cluster migration based on service model characterized by comprising
The service model file of application cluster is obtained, and extracts the resource deployment category of the application cluster in the service model file
Property and container node state, wherein the resource deployment attribute include: Resource Dependence relationship, software dependence and topology even
Connect relationship；
The migration of application cluster is completed according to the resource deployment attribute and container node state, comprising:
Set unbound for the state of the Resource Dependence relationship and software dependence, by the shape of the topological connection relation
State is set as not setting up, and the state of the container node is set as not creating；
It is that target application cluster distributes resource according to the container node state and Resource Dependence relationship；
It is target application cluster migration software according to the software dependence；
By the Data Migration of source application cluster to target application cluster；
It is that target application cluster carries out Topology connection configuration according to the Topological dependence.
2. the method according to claim 1, wherein it is described obtain application cluster service model file and mention
The resource deployment attribute and container node state for taking the application cluster in the service model file include:
The service model file of application cluster is obtained from the service model library of source data center；
The service model file is imported to the service model library at target data center；
Extract the resource deployment attribute and container node state in the service model file.
3. the method according to claim 1, wherein it is described according to the Resource Dependence relationship be target application collection
Group distributes resource
Virtual machine is created in target application cluster container according to the Resource Dependence relationship and container node state；
According to the virtual machine creating virtual data volume that the Resource Dependence relationship is in target application cluster container；
It is that target application cluster creates virtual network according to Resource Dependence relationship；
It is that target application cluster container binds container resource according to the Resource Dependence relationship.
4. the method according to claim 1, wherein described believe according to the Resource Dependence relationship and container node
Breath creates virtual machine in target application cluster container
Each empty machine section is calculated according to the dependence of the resource quota demand and container node of container node and empty machine node
The resource requirement of point；
It is that virtual container node creates virtual machine according to the resource requirement of virtual container node, binds virtual machine image, and by institute
The state for stating the virtual machine of container node dependence is set as having created；
Wherein the virtual machine image includes: system kernel and container engine.
5. the method according to claim 1, wherein it is described according to the container node state be target application collection
Group's creation virtual data, which is rolled up, includes:
According to the virtual data volume in container node information it is that target application cluster creates virtual data volume, and by the container section
The state for the virtual machine that point relies on is set as having created.
6. the method according to claim 1, wherein it is described according to Resource Dependence relationship be target application cluster create
Building virtual network includes:
It is target application cluster creation virtual network according to the virtual network container node state that the container node relies on, and will
The virtual network state that the container node relies on is set as having created.
7. the method according to claim 1, wherein it is described according to the Resource Dependence relationship be target application collection
Group's container binds container resource
According to the virtual machine dependence in the Resource Dependence relationship, virtual data volume is bound for container node；
According to the book dependence in the Resource Dependence relationship, virtual data volume is bound for container node；
According to the network dependence in the Resource Dependence relationship, virtual network is bound for container node；
The state of the virtual machine dependence, book dependence and network dependence is set as having bound.
8. according to the method described in claim 4, it is characterized in that, it is described according to the software dependence be target application collection
Group migration software include:
It is closed according to the dependence of the reversed dependence of virtual machine and container in the Resource Dependence relationship, container and container mirror image
System obtains the container image listing of virtual machine container node；
The container engine for calling virtual machine obtains the container mirror image that do not deposit from the container mirror image warehouse at target data center, if mesh
It marks and specified container mirror image is not present in the container mirror image warehouse of data center, then appearance of the container mirror image warehouse from source data center
The container mirror image being not present described in being obtained in device mirror image warehouse；
The container engine installs the file of the container mirror image according to the image dependency relationship in the Resource Dependence relationship；
Bind the top layer mirror image of the container image file for the container, and by the image dependency in the Resource Dependence relationship
Relationship is set as having bound.
9. according to the method described in claim 8, it is characterized in that,
When the state of all image dependency relationships is to have bound, the runtime data of log-on data container node is migrated,
By the Data Migration of source application cluster to target application cluster.
10. according to the method described in claim 9, it is characterized in that, the Data Migration by source application cluster is answered to target
Stopping source application cluster with cluster includes:
Stopping source application cluster obtains the data when operation of data capsule node in the application cluster of source；
Snapshot image is generated according to the data in the source application cluster when operation of data capsule node；
The snapshot image is uploaded to the container mirror image warehouse of source data center；
The container engine at target data center obtains the mirror snapshot from source mirror image warehouse, and mirror snapshot importing is referred to
Fixed container node.
11. according to the method described in claim 10, it is characterized in that, it is described according to the topological connection relation be target application
Cluster carries out Topology connection configuration
Obtain the link information in the topological connection relation；
Topology connection property parameters are configured for the container；
Start the Topology connection property parameters, and the state of topological connection relation is set as having been established.
12. according to the method for claim 11, which is characterized in that further include:
When Resource Dependence relationship, software dependence and Topology connection dependence are bound, the state of container node is set
It is set to ready；
After all container node states are both configured to ready, the migration of application cluster is completed in confirmation.
13. a kind of moving apparatus of the application cluster migration based on service model characterized by comprising
Data obtaining module for obtaining the service model file of application cluster, and extracts answering in the service model file
With the resource deployment attribute and container node state of cluster, wherein the resource deployment attribute includes: Resource Dependence relationship, soft
Part dependence and topological connection relation；
Cluster transferring module, for completing the migration of application cluster according to the resource deployment attribute and container node state；
Wherein, the cluster transferring module, comprising: state set unit, resource allocation unit, software migration unit, data are moved
Move unit and topological arrangement unit；
State set unit, for setting unbound for the state of the Resource Dependence relationship and software dependence, by institute
The state for stating topological connection relation is set as not setting up, and the state of the container node is set as not creating；
Resource allocation unit, for being target application cluster distribution money according to the container node state and Resource Dependence relationship
Source；
Software migration unit, for being target application cluster migration software according to the software dependence；
Data migration unit, for by the Data Migration of source application cluster to target application cluster；
Topological arrangement unit, for being that target application cluster carries out Topology connection configuration according to the Topological dependence.
14. moving apparatus according to claim 13, which is characterized in that data obtaining module includes: export subelement, leads
Enter subelement and information extraction unit；
Subelement is exported, for obtaining the service model file of application cluster from the service model library of source data center；
Subelement is imported, the service model file is imported to the service model library at target data center；
Information extraction unit, for extracting the Resource Dependence relationship in the service model file, software dependence, topology even
Connect relationship and container node state.
15. moving apparatus according to claim 13, which is characterized in that the resource allocation unit includes: asset creation
Subelement and resource binding unit,
Wherein,
Asset creation subelement, for being created according to the Resource Dependence relationship and container node state in target application cluster container
Build virtual machine；It is also used to be the virtual machine creating virtual data in target application cluster container according to the Resource Dependence relationship
Volume；It is also used to be that target application cluster creates virtual network according to Resource Dependence relationship；
Resource binding unit, for being that target application cluster container binds container resource according to the Resource Dependence relationship.
16. moving apparatus according to claim 13, it is characterised in that:
Asset creation subelement is specifically used for resource quota demand and container node and empty machine node according to container node
Dependence calculates the resource requirement of each empty machine node；
Asset creation subelement is also used to be that virtual container node creates virtual machine according to the resource requirement of virtual container node, ties up
Determine virtual machine image, and the state for the virtual machine that the container node relies on is set as having created, wherein the virtual machine mirror
As including: system kernel and container engine.
17. moving apparatus according to claim 15, which is characterized in that asset creation subelement is specifically used for according to appearance
Virtual data volume in device nodal information is that target application cluster creates virtual data volume, and the void that the container node is relied on
The state of quasi- machine is set as having created.
18. moving apparatus according to claim 15, it is characterised in that:
Asset creation subelement is answered specifically for the virtual network container node state relied on according to the container node for target
Virtual network is created with cluster, and the virtual network state that the container node relies on is set as having created.
19. moving apparatus according to claim 15, it is characterised in that:
Resource binding unit, specifically for according to the virtual machine dependence in the Resource Dependence relationship；It is also used to as container
Node binding virtual data volume；It is also used to be tied up according to the book dependence in the Resource Dependence relationship for container node
Determine virtual data volume；It is also used to according to the network dependence in the Resource Dependence relationship, binds virtual net for container node
Network；It is also used to be set as having bound by the state of the virtual machine dependence, book dependence and network dependence.
20. moving apparatus according to claim 16, which is characterized in that
Software migration unit, specifically for according to the reversed dependence of virtual machine and container in the Resource Dependence relationship,
The dependence of container and container mirror image obtains the container image listing of virtual machine container node；It is also used to call the appearance of virtual machine
Device engine obtains the container mirror image being not present on host from the container mirror image warehouse at target data center, if target data center
Container mirror image warehouse in there is no specified container mirror image, then container mirror image warehouse is from the container mirror image warehouse of source data center
The container mirror image being not present described in middle acquisition；It is also used to according to the image dependency relationship installation in the Resource Dependence relationship
The file of container mirror image；Be also used to bind the top layer mirror image of the container image file for the container, and by the resource according to
Image dependency relationship in the relationship of relying is set as having bound.
21. moving apparatus according to claim 20, which is characterized in that data migration unit be used for when all mirror images according to
The state for the relationship of relying is when having bound, and the runtime data of log-on data container node migrates, by the operation of source application cluster
When Data Migration to target application cluster.
22. moving apparatus according to claim 21, which is characterized in that data migration unit is applied specifically for stopping source
Cluster obtains the data when operation of data capsule node in the application cluster of source；It is also used to according to number in the source application cluster
According to container node operation when data generate snapshot image；The snapshot image is uploaded to the container mirror image of source data center
Warehouse；The container engine for being also used to target data center obtains the mirror snapshot from source mirror image warehouse, and the mirror image is fast
According to the specified container node of importing.
23. moving apparatus according to claim 22, which is characterized in that topological arrangement unit is specifically used for described in acquisition
Link information in topological connection relation；It is also used to configure Topology connection property parameters for the container；It is also used to start described
Topology connection property parameters, and the state of topological connection relation is set as having been established.
24. moving apparatus according to claim 23, which is characterized in that the moving apparatus further include: cluster migration is single
Member, for when Resource Dependence relationship, software dependence and Topology connection dependence are bound, by the state of container node
It is set as ready；It is also used to after all container node states are both configured to ready, the migration of application cluster is completed in confirmation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510664774.9A CN106603592B (en) | 2015-10-15 | 2015-10-15 | A kind of method and moving apparatus for the application cluster migration based on service model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510664774.9A CN106603592B (en) | 2015-10-15 | 2015-10-15 | A kind of method and moving apparatus for the application cluster migration based on service model |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106603592A CN106603592A (en) | 2017-04-26 |
| CN106603592B true CN106603592B (en) | 2019-10-01 |
Family
ID=58552172
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510664774.9A Active CN106603592B (en) | 2015-10-15 | 2015-10-15 | A kind of method and moving apparatus for the application cluster migration based on service model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106603592B (en) |
Families Citing this family (31)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109246167B (en) * | 2017-07-11 | 2022-04-01 | 阿里巴巴集团控股有限公司 | Container scheduling method and device |
| CN109391664B (en) * | 2017-08-11 | 2021-04-20 | 中国电信股份有限公司 | System and method for multi-cluster container deployment |
| CN107589982B (en) * | 2017-09-12 | 2021-01-15 | 国云科技股份有限公司 | Method for migrating virtual machine from VMware to KVM |
| CN107579898B (en) * | 2017-09-14 | 2020-08-14 | 快云信息科技有限公司 | Method and device for interconnection communication among multiple containers |
| CN107734019B (en) * | 2017-09-29 | 2020-12-25 | 中国石油化工股份有限公司 | System and method for on-line migration of exploration and development containers |
| CN109587281B (en) * | 2017-09-29 | 2020-07-28 | 华为技术有限公司 | Container configuration method and computing node |
| CN107728947A (en) * | 2017-10-13 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of cold moving method of container and system |
| CN107729151A (en) * | 2017-10-19 | 2018-02-23 | 济南浪潮高新科技投资发展有限公司 | A kind of method of cluster management FPGA resource |
| CN107704618B (en) * | 2017-10-27 | 2020-09-25 | 北京航空航天大学 | Thermal migration method and system based on aufs file system |
| CN107734052B (en) * | 2017-11-02 | 2019-12-10 | 华南理工大学 | Load balancing container scheduling method facing component dependence |
| CN109840132B (en) * | 2017-11-27 | 2021-05-14 | 华为技术有限公司 | Arranging method and device of container and storage medium |
| CN109150964B (en) * | 2018-07-06 | 2022-01-11 | 中科星图股份有限公司 | Migratable data management method and service migration method |
| CN109165095B (en) * | 2018-08-16 | 2022-04-15 | 中科边缘智慧信息科技（苏州）有限公司 | Task package based information system rapid opening method |
| CN109005245B (en) * | 2018-09-07 | 2021-09-14 | 广州微算互联信息技术有限公司 | Cloud mobile phone use management method and system |
| CN113383319B (en) | 2018-10-24 | 2024-05-03 | 华为云计算技术有限公司 | Target-driven dynamic object placement optimization |
| CN111352689B (en) * | 2018-12-21 | 2023-04-07 | 中国电信股份有限公司 | Method and device for realizing seamless migration of application containerized deployment |
| CN109857516B (en) * | 2018-12-29 | 2023-12-12 | 航天信息股份有限公司 | Cluster migration method and device based on container |
| CN111756562B (en) * | 2019-03-29 | 2023-07-14 | 深信服科技股份有限公司 | Cluster takeover method, system and related components |
| CN110795162B (en) * | 2019-09-26 | 2022-07-05 | 北京浪潮数据技术有限公司 | Method and device for generating container mirror image file |
| CN111459415B (en) * | 2020-04-15 | 2023-05-23 | 腾讯云计算(长沙)有限责任公司 | Cross-cloud data migration method, device, equipment and storage medium |
| CN111294410B (en) * | 2020-05-11 | 2020-08-14 | 杭州朗澈科技有限公司 | Method for uploading local mirror image file to multi-region private mirror image warehouse |
| CN111522545B (en) * | 2020-07-06 | 2020-10-20 | 嘉兴太美医疗科技有限公司 | Method, device, system and readable medium for dynamically constructing model based on Java |
| CN113946275B (en) * | 2020-07-15 | 2024-04-09 | 中移(苏州)软件技术有限公司 | Cache management method and device and storage medium |
| CN112333003B (en) * | 2020-10-13 | 2022-11-08 | 北京京东尚科信息技术有限公司 | Method and device for acquiring proprietary cloud container cluster gene information |
| CN112558930B (en) * | 2020-12-09 | 2022-02-08 | 苏州空天信息研究院 | Software generation system and method for container service |
| US11762571B2 (en) | 2020-12-21 | 2023-09-19 | International Business Machines Corporation | Migration of uncached data after cutover |
| CN112769617A (en) * | 2021-01-06 | 2021-05-07 | 武汉紫阑信息技术有限公司 | Method for migrating RabbitMQ cluster and computer system |
| CN115134231B (en) * | 2021-03-17 | 2024-03-08 | 北京搜狗科技发展有限公司 | Communication method, device and device for communication |
| CN113359511A (en) * | 2021-06-23 | 2021-09-07 | 陕西工大锐迪信息技术有限公司 | Construction method and device of industrial control simulation network, computer equipment and storage medium |
| CN113326100B (en) * | 2021-06-29 | 2024-04-09 | 深信服科技股份有限公司 | Cluster management method, device, equipment and computer storage medium |
| CN113672337B (en) * | 2021-07-16 | 2024-02-13 | 广东浪潮智慧计算技术有限公司 | Application migration method, device, equipment and computer readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103856548A (en) * | 2012-12-07 | 2014-06-11 | 华为技术有限公司 | Dynamic resource scheduling method and dynamic resource scheduler |
| CN104935618A (en) * | 2014-03-19 | 2015-09-23 | 福建福昕软件开发股份有限公司北京分公司 | Cluster disposition method |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9372726B2 (en) * | 2013-01-09 | 2016-06-21 | The Research Foundation For The State University Of New York | Gang migration of virtual machines using cluster-wide deduplication |
-
2015
- 2015-10-15 CN CN201510664774.9A patent/CN106603592B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103856548A (en) * | 2012-12-07 | 2014-06-11 | 华为技术有限公司 | Dynamic resource scheduling method and dynamic resource scheduler |
| CN104935618A (en) * | 2014-03-19 | 2015-09-23 | 福建福昕软件开发股份有限公司北京分公司 | Cluster disposition method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106603592A (en) | 2017-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106603592B (en) | A kind of method and moving apparatus for the application cluster migration based on service model | |
| CN106020930B (en) | A kind of application management method and system based on application container | |
| US10474438B2 (en) | Intelligent cloud engineering platform | |
| CN105224466B (en) | A kind of integration test method and system based on Docker | |
| CN106790660A (en) | A kind of dispositions method and device for realizing distributed memory system | |
| CN107203388B (en) | REST architecture style-oriented Web service rapid development method | |
| US8949364B2 (en) | Apparatus, method and system for rapid delivery of distributed applications | |
| CN103064742B (en) | A kind of automatic deployment system and method for hadoop cluster | |
| CN105429806B (en) | A kind of device and method of the network function virtualization based on data-driven | |
| CN107579931A (en) | A kind of block chain based on Kubernetes is Service Source adaptation method | |
| CN107301048B (en) | Internal control management system of application response type shared application architecture | |
| CN106790483A (en) | Hadoop group systems and fast construction method based on container technique | |
| CN107357660A (en) | The distribution method and device of a kind of virtual resource | |
| CN110178357A (en) | Cellular service based on cloud in the accessible cloud of remote equipment | |
| US20170048314A1 (en) | Migrating cloud resources | |
| CN109542611A (en) | Database, that is, service system, database dispatching method, equipment and storage medium | |
| CN110658794B (en) | Manufacturing execution system | |
| CN106506703A (en) | Based on the service discovery method of shared drive, apparatus and system, server | |
| CN106953848B (en) | Software defined network implementation method based on ForCES | |
| CN112114784A (en) | Single-Spa-based front-end micro-service system | |
| JPH09506725A (en) | Object-oriented rule-based protocol system | |
| Leymann et al. | Native cloud applications: why monolithic virtualization is not their foundation | |
| CN103646134B (en) | A kind of service-oriented networking analogue system dynamic creation method | |
| CN107544783A (en) | A kind of data-updating method, apparatus and system | |
| CN101861578B (en) | Network operating system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |