CN108737468B - Cloud platform service cluster, construction method and device - Google Patents
Cloud platform service cluster, construction method and device Download PDFInfo
- Publication number
- CN108737468B CN108737468B CN201710258881.0A CN201710258881A CN108737468B CN 108737468 B CN108737468 B CN 108737468B CN 201710258881 A CN201710258881 A CN 201710258881A CN 108737468 B CN108737468 B CN 108737468B
- Authority
- CN
- China
- Prior art keywords
- cluster
- node
- service
- nodes
- component
- 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
Images
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
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- 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/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Abstract
The embodiment of the invention provides a cloud platform service cluster, a construction method and a device, the method deploys a first node non-containerized assembly cluster, a first node containerized assembly cluster and a cluster management platform assembly on a first node cluster node, and the cluster management platform assembly comprises a containerized cluster management platform assembly and a non-containerized cluster management platform assembly, thereby realizing the non-containerized cluster service, realizing the management control on service access based on the non-containerized cluster service, simultaneously solving the problem that a part of management tools are difficult to implement containerized and highly available, and solving the problem that the prior art does not have a good solution to other non-containerized services in the cluster.
Description
Technical Field
The invention relates to the field of cloud platform application, in particular to a cloud platform service cluster, a construction method and a device.
Background
The cloud platform or the cloud computing platform can integrate various existing business capabilities and provide platform services for software applications and the like in the current cloud computing technical background. The method can measure and calculate the infrastructure capacity according to the service capacity for the lower layer, call a bottom layer API (Application Programming Interface) to realize the scheduling of various resources, provide a service scheduling center function for the upper layer, monitor various resources of the platform in real time, and open the resources to the upper layer user in the form of API.
High availability clustering refers to a server clustering technique aimed at reducing service interruption time. The system can provide services to the outside continuously by protecting the business program of the user, and the fault influence caused by software, hardware or human is reduced to the minimum. The high performance is a higher demand on the basis of high availability, which is provided by cluster users, in the technical background of cloud computing development. The high-performance and high-availability cluster can reduce the response time of user requests, reduce the consumption of resource scheduling in the cluster and realize the load balance of cluster nodes or components on the premise of ensuring uninterrupted user service.
Receiving an abnormal message of a first container sent by a proxy service system, and restarting or switching the first container through the proxy service system according to the abnormal message; the method achieves high availability of the container cluster to a certain extent, but there is no good solution for other non-containerized services in the cluster.
Disclosure of Invention
The embodiment of the invention provides a cloud platform service cluster, a construction method and a device, which are used for at least solving the problem that no good solution is provided for other non-containerized services in the cluster in the prior art.
In one aspect, a cloud platform service cluster construction method is provided, which includes:
respectively selecting nodes from a cloud platform node library as a first node cluster node, a basic and common service node and a service node;
deploying a first node non-containerized component cluster and a first node containerized component cluster on a first node cluster node;
deploying cluster management platform components on a first node cluster node, wherein the cluster management platform components comprise containerized cluster management platform components and non-containerized cluster management platform components;
deploying a public service assembly cluster and a basic service assembly cluster on a basic service node and a public service node;
deploying a service cluster and a service performance component of the service cluster on a service node;
configuring a network address of an internal local area network, and associating a first node cluster node, a basic and public service node and node internal components and nodes of a service node;
applying for the public network address, binding and exposing the network address.
In one aspect, a cloud platform service cluster building apparatus is provided, including: a selection module, a deployment module, an association module, and an exposure module, wherein,
the selection module is used for respectively selecting nodes from the cloud platform node library as a first node cluster node, a basic and public service node and a service node;
the deployment module is used for deploying the first node non-containerized component cluster and the first node containerized component cluster on the first node cluster node; deploying cluster management platform components on a first node cluster node, wherein the cluster management platform components comprise containerized cluster management platform components and non-containerized cluster management platform components; deploying a public service assembly cluster and a basic service assembly cluster on a basic service node and a public service node; deploying a service cluster and a service performance component of the service cluster on a service node;
the association module is used for configuring a network address of an internal local area network and associating the first node cluster node, the basic and public service nodes and node internal components of the service nodes and the nodes;
the exposure module is used for applying for a public network address and binding and exposing the network address.
In one aspect, a cloud platform service cluster is provided, including: a cluster management platform module, a public service module, a service cluster module and a service access opening module, wherein,
the service access opening module is used for receiving user operation based on the public network address;
the cluster management platform module is used for executing user operation through the public service module and the service cluster module based on a network address of an internal local area network, and comprises a first node cluster node, a cluster management platform assembly is deployed on the first node cluster node, the first node cluster node comprises a first node non-containerized assembly cluster and a first node containerized assembly cluster, and the cluster management platform assembly comprises a containerized cluster management platform assembly and a non-containerized cluster management platform assembly;
the public service module is used for providing basic service and public service, the public service module comprises a foundation and a public service node, and the foundation and the public service node comprise a public service assembly cluster and a basic service assembly cluster;
the service cluster module is used for providing service cluster service, and comprises service nodes, and the service nodes are deployed with service clusters and service cluster service performance components.
In another aspect, a computer storage medium is provided, where computer-executable instructions are stored in the computer storage medium, and the computer-executable instructions are used to execute the foregoing cloud platform service cluster building method.
The embodiment of the invention has the following beneficial effects:
the embodiment of the invention provides a cloud platform service cluster, a construction method and a device, the cloud platform service cluster method comprises the steps of selecting a node from a cloud platform node library as a first node cluster node, deploying a first node non-containerized component cluster and a first node containerized component cluster on the first node cluster node, and deploying a cluster management platform component, wherein the cluster management platform component comprises a containerized cluster management platform component and a non-containerized cluster management platform component, so that the non-containerized cluster service is realized, the management control on service access is realized based on the non-containerized cluster service, the problem that a part of management tools are difficult to implement containerized and high in availability is solved, and the problem that the prior art does not well solve other non-containerized services in the cluster is solved. Furthermore, the cloud platform service cluster provided by the invention adopts a distributed architecture, and the first node cluster node, the foundation and the public service node are completely separated from the service nodes providing the service cluster, so that the high availability of the service cluster is ensured.
Drawings
Fig. 1 is a block diagram of a cloud platform service cluster building apparatus according to a first embodiment of the present invention;
fig. 2 is a flowchart of a cloud platform service cluster building method according to a first embodiment of the present invention;
fig. 3 is a structural diagram of a cloud platform service cluster according to a first embodiment of the present invention;
fig. 4 is a structural diagram of a cloud platform service cluster according to a second embodiment of the present invention;
fig. 5 is a flowchart of a cloud platform service cluster building method according to a second embodiment of the present invention;
fig. 6 is a timing diagram of a cloud platform service cluster construction method according to a second embodiment of the present invention;
fig. 7 is a block diagram of a computer according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In practical application, the containerization component provided by the embodiment of the invention is a functional component which can be realized by using a container, and after the functional components are containerized, the functional components are similar to building blocks in use and can be directly selected to be built according to own requirements, so that a user can conveniently develop and use the functional components; correspondingly, the non-containerized components are functional components which cannot adopt containerization processing, such as functional components for managing and controlling service access, and the like, aiming at the components, the invention is directly constructed in a non-containerized component mode, realizes non-containerized cluster service, realizes the management and control of the service access based on the non-containerized cluster service, simultaneously solves the problem that part of management tools are difficult to containerize and highly available to implement, and solves the problem that the prior art does not well solve other non-containerized services in the cluster. In practical applications, taking OpenStack (an open source project developed by NASA and Rackspace in cooperation and intended to provide software for construction and management of public and private clouds) as an example, when upgrading or degrading OpenStack, two ways are usually available, namely a management way based on Packages, or a management way based on Images, and the main purpose of containerizing OpenStack is to optimize the OpenStack management way based on Images, and the containerized OpenStack management scheme solves the most troublesome OpenStack availability and management and maintenance problems in the current mainstream OpenStack deployment system.
The invention will now be further explained by means of embodiments in conjunction with the accompanying drawings.
The first embodiment:
fig. 1 is a block diagram of a cloud platform service cluster building apparatus according to a first embodiment of the present invention, and as can be seen from fig. 1, the cloud platform service cluster building apparatus according to this embodiment includes: a selection module 11, a deployment module 12, an association module 13, and an exposure module 14, wherein,
the selection module 11 is used for respectively selecting nodes from the cloud platform node library as a first node cluster node, a foundation and public service node and a service node;
the deployment module 12 is configured to deploy the first-node non-containerized component cluster and the first-node containerized component cluster on the first-node cluster node; deploying cluster management platform components on a first node cluster node, wherein the cluster management platform components comprise containerized cluster management platform components and non-containerized cluster management platform components; deploying a public service assembly cluster and a basic service assembly cluster on a basic service node and a public service node; deploying a service cluster and a service performance component of the service cluster on a service node;
the association module 13 configures the network address of the internal local area network, and associates the first node cluster node, the basic and public service nodes and the node internal components and nodes of the service node; in the application, in order to reduce the occupation of public network IP (network address), communication among components in most clusters and among clusters is realized through an internal local area network, the network addresses reside in a first node cluster in a service mode, and service migration can be carried out after the nodes are down so as to ensure uninterrupted access;
the exposure module 14 is used for applying for a public network address, and binding and exposing the network address; the public network address of the application is an access address provided for a user to access.
The embodiment provides a cloud platform service cluster construction device, a node is selected from a cloud platform node library as a first node cluster node, a first node non-containerized component cluster and a first node containerized component cluster are deployed on the first node cluster node, and a cluster management platform component is deployed and comprises a containerized cluster management platform component and a non-containerized cluster management platform component, so that the non-containerized cluster service is realized, management control over service access is realized based on the non-containerized cluster service, the problem that a part of management tools are difficult to implement containerized and highly available is solved, and the problem that the prior art does not have a good solution for other non-containerized services in the cluster is solved.
In some embodiments, the number of nodes of the head node cluster node is greater than two; the deployment module 12 in the above embodiment is configured to deploy a non-containerized component cluster management tool on the head node cluster node, deploy at least one virtual network address service through the non-containerized component cluster management tool, set the virtual network address service to pass through each node in the cloud platform node library, and deploy a non-containerized end point component on the head node cluster node; the virtual network address service management system is also used for respectively deploying containerization component cluster management tools on the head node cluster nodes, respectively deploying containerization end point components on the head node cluster nodes, and binding the containerization end point components with the virtual network address service.
In some embodiments, the exposure module 14 in the above embodiments is configured to create an infrastructure as a service network port for the external virtual network address service, assign a network address of the external virtual network address service to the infrastructure as a service network port; and applying for a public network address for the infrastructure serving network port, and binding the public network address to the infrastructure serving network port.
In some embodiments, the selection module 11 in the foregoing embodiments is configured to select, as the first node cluster node, at least three nodes with an odd number from among the platform, i.e., service control role nodes in the cloud platform node library, select at least two nodes from among the cloud platform node libraries other than the first node cluster node as the foundation and common service nodes, and select at least one node from among the cloud platform node libraries other than the first node cluster node and the foundation and common service nodes as the service node.
The cloud platform service cluster constructed in this embodiment adopts a distributed architecture, and the first node cluster node, the foundation and the common service node are completely separated from the service nodes providing the service cluster, so that high availability of the service cluster is ensured.
In practical applications, the cloud platform service cluster building apparatus according to this embodiment may be implemented based on a computer platform, and at this time, all functions of the selection module 11, the deployment module 12, the association module 13, and the exposure module 14 are implemented by running corresponding computer programs by a processor of a computer, such as a CPU.
At this moment, the computer communicates with the cloud platform through the external interface of the cloud platform to realize resource calling and deployment, and specifically, a processor of the computer is used for: respectively selecting nodes from a cloud platform node library as a head node cluster node, a basic and common service node and a service node, deploying a first node non-containerized component cluster and a first node containerized component cluster on a first node cluster node, deploying cluster management platform components on the cluster nodes of the first node, wherein the cluster management platform components comprise containerized cluster management platform components and non-containerized cluster management platform components, a common service component cluster and a base service component cluster are deployed on the base and common service nodes, the method comprises the steps of deploying a service cluster and a service performance component of the service cluster on a service node, configuring a network address of an internal local area network, associating a cluster node of a first node, a foundation and a public service node and the node internal component and the node of the service node, applying for a public network address, and binding and exposing the network address.
Fig. 2 is a flowchart of a cloud platform service cluster construction method according to a first embodiment of the present invention, and as can be seen from fig. 2, the cloud platform service cluster construction method according to this embodiment includes:
s201: respectively selecting nodes from a cloud platform node library as a first node cluster node, a basic and common service node and a service node;
s202: deploying a first node non-containerized component cluster and a first node containerized component cluster on a first node cluster node;
s203: deploying cluster management platform components on a first node cluster node, wherein the cluster management platform components comprise containerized cluster management platform components and non-containerized cluster management platform components;
s204: deploying a public service assembly cluster and a basic service assembly cluster on a basic service node and a public service node;
s205: deploying a service cluster and a service performance component of the service cluster on a service node;
s206: configuring a network address of an internal local area network, and associating a first node cluster node, a basic and public service node and node internal components and nodes of a service node;
s207: applying for a public network address, and binding and exposing the network address;
through the implementation of steps S206 and S207, the cloud platform service cluster is isolated and protected in the network communication layer, the platforms communicate with each other on the basis of the internal network, and the platforms communicate with each other on the basis of the external network, so that the isolation is realized in the network layer, when providing services to external users (product users), the users can only access the external service interface of the cloud platform service cluster through the external network (i.e., the public network), but cannot access the internal components/nodes of the cloud platform service cluster, and the like, thereby ensuring that the internal components/nodes are not attacked by external data, and improving the security of the cloud platform service cluster.
The embodiment provides a cloud platform service cluster construction method, a node is selected from a cloud platform node library as a first node cluster node, a first node non-containerized component cluster and a first node containerized component cluster are deployed on the first node cluster node, and a cluster management platform component is deployed and comprises a containerized cluster management platform component and a non-containerized cluster management platform component, so that the non-containerized cluster service is realized, management control over service access is realized based on the non-containerized cluster service, the problem that partial management tools are difficult to implement containerized and highly available is solved, and the problem that the prior art does not have a good solution for other non-containerized services in a cluster is solved.
In some embodiments, the number of nodes of the head node cluster node is greater than two; at this time, step S202 in the above embodiment includes:
respectively deploying non-containerization component cluster management tools on the first node cluster nodes;
deploying at least one virtual network address service through a non-containerized component cluster management tool, and setting the virtual network address service to pass through each node in a cloud platform node library;
respectively deploying non-containerization end point components on the head node cluster node;
respectively deploying containerization component cluster management tools on the first node cluster nodes;
respectively deploying containerization end point components on the head node cluster node;
binding the containerized endpoint component with the virtual network address service.
In some embodiments, step S207 in the above embodiments includes:
creating an infrastructure as a service network port for external virtual network address service;
assigning a network address of an external virtual network address service to an infrastructure as a service network port;
applying for a public network address for an infrastructure-as-a-service network port;
the public network address is bound to the infrastructure, i.e. the service network port.
In practical applications, after step S207, an effective security mechanism may also be provided, such as the access rights of different users may be restricted through the network plane.
In some embodiments, step S201 in the above embodiments includes:
selecting at least three nodes with odd number from the platform, namely the service control role nodes of the cloud platform node library as a first node cluster node;
selecting at least two nodes as basic and public service nodes in a cloud platform node library outside a first node cluster node;
and selecting at least one node as a service node from the cloud platform node library except the head node cluster node and the basic and public service nodes.
The cloud platform service cluster constructed in this embodiment adopts a distributed architecture, and the first node cluster node, the foundation and the common service node are completely separated from the service nodes providing the service cluster, so that high availability of the service cluster is ensured.
Fig. 3 is a structural diagram of a cloud platform service cluster according to a first embodiment of the present invention; as can be seen from fig. 3, the cloud platform service cluster provided in this embodiment includes: a cluster management platform module 31, a common service module 32, a service cluster module 33, and a service access opening module 34, wherein,
the service access opening module 34 is configured to receive a user operation based on the public network address;
the cluster management platform module 31 is configured to execute a user operation through the public service module and the service cluster module based on a network address of the internal local area network, and includes a first-node cluster node, where the first-node cluster node is deployed with a cluster management platform component, the first-node cluster node includes a first-node non-containerized component cluster and a first-node containerized component cluster, and the cluster management platform component includes a containerized cluster management platform component and a non-containerized cluster management platform component;
the public service module 32 is used for providing basic services and public services, and the public service module comprises basic and public service nodes, wherein the basic and public service nodes comprise a public service component cluster and a basic service component cluster;
the service cluster module 33 is configured to provide a service cluster service, and the service cluster module includes service nodes, and the service nodes are deployed with service clusters and service performance components of the service clusters.
The embodiment provides a cloud platform service cluster, wherein a first node non-containerized component cluster, a first node containerized component cluster and a cluster management platform component are deployed on a first node cluster node, the cluster management platform component comprises a containerized cluster management platform component and a non-containerized cluster management platform component, the non-containerized cluster service is realized, management control over service access is realized based on the non-containerized cluster service, the problem that a part of management tools are difficult to implement in a containerized and high-availability mode is solved, and the problem that the prior art does not have a good solution to other non-containerized services in the cluster is solved.
In some embodiments, the head node cluster node, the base and common service nodes, and the service node in the above embodiments are independent of each other. The cloud platform service cluster provided by this embodiment adopts a distributed architecture, and the first node cluster node, the foundation and the common service node are completely separated from the service nodes providing the service cluster, so as to ensure high availability of the service cluster. In practical application, the first node cluster node is realized by a computer in a cloud platform through a corresponding operating system, and the foundation, the public service node and the service node can be realized by bottom infrastructure such as a single chip microcomputer of the cloud platform.
FIG. 7 is a block diagram of a computer according to an embodiment of the present invention; as can be seen from fig. 7, the computer provided in this embodiment includes: a communication bus 71, a communication unit 72, a processor 73, a memory 74 and a computer program stored on the memory 74 and executable on the processor, wherein,
the communication bus 71 is used for realizing communication connection among the communication unit 72, the processor 73 and the memory 74;
the communication unit 72 is used for communicating with an external interface of the cloud platform;
the processor 73 is adapted to execute a computer program to perform the following steps:
respectively selecting nodes from a cloud platform node library as a first node cluster node, a basic and common service node and a service node;
deploying a first-node non-containerized component cluster and a first-node containerized component cluster on a first-node cluster node, and deploying a cluster management platform component on the first-node cluster node, wherein the cluster management platform component comprises a containerized cluster management platform component and a non-containerized cluster management platform component;
deploying a public service assembly cluster and a basic service assembly cluster on a basic service node and a public service node, and deploying a service cluster and a service performance assembly of the service cluster on the service node;
configuring a network address of an internal local area network, and associating a first node cluster node, a basic and public service node and node internal components and nodes of a service node;
applying for the public network address, binding and exposing the network address.
In some embodiments, the processor 73 in the above embodiments is further configured to execute a computer program to implement the following steps:
respectively deploying non-containerization component cluster management tools on the first node cluster nodes;
deploying at least one virtual network address service through a non-containerized component cluster management tool, and setting the virtual network address service to pass through each node in a cloud platform node library;
respectively deploying non-containerization end point components on the head node cluster node;
respectively deploying containerization component cluster management tools on the first node cluster nodes;
respectively deploying containerization end point components on the head node cluster node;
binding the containerized endpoint component with the virtual network address service.
In some embodiments, the processor 73 in the above embodiments is further configured to execute a computer program to implement the following steps:
creating an infrastructure as a service network port for external virtual network address service;
assigning a network address of an external virtual network address service to an infrastructure as a service network port;
applying for a public network address for an infrastructure-as-a-service network port;
the public network address is bound to the infrastructure, i.e. the service network port.
In some embodiments, the processor 73 in the above embodiments is further configured to execute a computer program to implement the following steps:
selecting at least three nodes with odd number from the platform, namely the service control role nodes of the cloud platform node library as a first node cluster node;
selecting at least two nodes as basic and public service nodes in a cloud platform node library outside a first node cluster node;
and selecting at least one node as a service node from the cloud platform node library except the head node cluster node and the basic and public service nodes.
The embodiment provides a computer platform, wherein a node is selected from a cloud platform node library as a first node cluster node according to user operation, a first node non-containerized component cluster and a first node containerized component cluster are deployed on the first node cluster node, and a cluster management platform component is deployed and comprises a containerized cluster management platform component and a non-containerized cluster management platform component, so that a non-containerized cluster service is realized, management control over service access is realized based on the non-containerized cluster service, the problem that a part of management tools are difficult to implement containerized and highly available is solved, and the problem that the prior art does not have a good solution for other non-containerized services in a cluster is solved.
Second embodiment:
the present invention will now be further explained with reference to specific application scenarios.
With the development of cloud computing technology, cloud computing users put more personalized and complicated demands on cloud computing platform service clusters. The requirements include how to deploy a service cluster in a complex scene, how to manage a plurality of multi-class service clusters across regions, how to guarantee service cluster service for a long time, how to guarantee continuous uninterrupted normal operation of a service cluster carrier, how to guarantee efficient scheduling inside the cluster, how to improve the experience of using the cluster by a user, and the like. The present embodiment proposes a new system solution to these needs.
Specifically, as shown in fig. 4, this embodiment mainly provides a cluster system framework capable of deploying and managing a plurality of high-available high-performance service clusters in a physical machine scene, a virtual machine scene, and other mixed scenes. The system framework is a distributed system framework, and the system framework also comprises a containerized cluster system component and a non-containerized cluster system component which are flexibly deployed or deployed by using a main-standby mode and a multi-main mode, so that the cluster system is realized, meanwhile, the uninterrupted service duration of a system cluster is reliably ensured, and the operation and scheduling performance of internal components of the cluster system and the access performance of external users are greatly improved.
In order to deploy the cluster system framework shown in fig. 4, as shown in fig. 5 and fig. 6, the method provided by this embodiment includes:
s501: and deploying the head node non-containerized component cluster.
S501-1) selecting three PaaS (platform as a service) control role nodes as head node cluster nodes, respectively deploying non-containerization component cluster management tools such as a pacemaker and the like, and realizing mutual trust, clock synchronization, certificate authentication and the like of SSH (Secure Shell) between the head nodes.
S501-2) deploying a plurality of VIP (Virtual IP) services by the non-containerized component cluster management tool, wherein the VIP services are respectively used for uniform access of different users, the VIP services can be randomly and uniformly deployed on different head nodes by the non-containerized component cluster management tool based on a load balancing strategy, and meanwhile, the VIP is allowed to pass through each node by setting a security strategy at a port management position of IaaS (Infrastructure as a Service).
S501-3) deploying an endpoint component on any node in the first node cluster, such as Haproxy and the like, and cloning the endpoint component to all nodes of the first node cluster by a cloning method, wherein the endpoint component is mainly used for health check of the database cluster.
The first node cluster is used for deploying and managing the service cluster, comprises most basic applications for managing the service cluster, and in order to achieve high availability, the number of the first node clusters is odd and is more than or equal to 3.
S502: and deploying the head node containerized cluster.
S502-1) selecting 3 nodes where non-container component clusters are located, deploying container component cluster management tools such as a docker swarm and other tools, creating a cluster on any one node in the role of an administrator, and adding other two nodes into the cluster in the role of the administrator after obtaining a token of a first head node; the first node is voted as the master role, and once the node is abnormal or the container tool of the node is abnormal, other nodes are voted as the master role.
S502-2) deploying end point components in the containerized component cluster, firstly, using a containerized component cluster management tool to create a temporary facility network for data synchronization and backup of the container cluster, secondly, creating end point component services in the containerized cluster in a global mode, wherein the containers acquire an IP address from a resource pool of a configuration file, take the container with the minimum IP address as a first container, and add other containers into the components to form the end point component cluster. The endpoint component actually performs the function of an LB (Load Balance) component and provides health check and resource recovery and migration services of various components.
S502-3) binding the three client instances of the endpoint component with the VIP in the S501-2), wherein the three client instances are respectively used for external users to access the scheduling cluster and the internal scheduling of the cloud platform service cluster system, once a certain node is abnormal, the instances of the endpoint component and the VIP can be rapidly switched to other nodes in the first node cluster
S503: a cluster management platform component is deployed in the head node cluster.
These components are containerized, as well as non-containerized components that run on host in the form of processes, so deployment occurs in two types. The cluster management platform components mainly include components interacting with the underlying IaaS, a management platform internal scheduling component, an internal extended function component, an application component exposed to the upper SaaS (Software as a Service), a database, and a message queue.
S503-1) deploying containerized components, wherein the deployment modes are different due to different characteristics of the platform management components; some components are run in the form of tools of the containerized component cluster management tool and others are launched in the form of service creation of the containerized component cluster management tool. Taking the containerized component cluster management tool as docker for example, a part of containerized components are started on three head nodes in a docker run form of docker, after the start, the containerized components are cluster-combined by means of their own internal logic, a network for data synchronization and backup is generally a host network (in an internet protocol, host represents a local computer capable of accessing other machines), and another containerized component, such as a database tool container described below, is started in a docker service create form of docker, which is a new characteristic of the containerized cluster management tool docker swap, unlike the docker run, and can be started on a designated node in a certain number of replication number patterns or a global pattern, and data synchronization and backup are performed through a temporary facility network of the docker swap, and LB processing is performed on component access of the type, and keep-alive processing is carried out on the containers on each node.
S503-2) deploying the non-containerized component, wherein the deployment mode is as follows: the service is deployed in a certain head node, operations such as start-stop, health check, component resource migration and the like are performed on the component by creating an Open Cluster Framework (OCF) file, and if the component is in a multi-master mode, the component needs to be expanded to all head nodes through cloning. If the component does not need to be cloned, the node where the component resides is the main node, other nodes are standby, and once the node or the component on the node is abnormal, the service can be guaranteed not to be interrupted through recovery and migration.
S503-3) registering the cluster management platform component with the endpoint component in S502-2), and performing health check on the components by the endpoint component and realizing resource recovery and migration.
S504: a common service module is deployed.
The module consists of two types of components, namely a public service component and a basic service component, wherein the public service component comprises a database, a message queue, log processing, a software warehouse and the like, and the module is mainly used for internal scheduling and performance improvement of a cluster management platform and a service cluster.
S504-1) selecting a number of nodes outside the head node cluster and tagging the nodes with a specific tag, such as shared or exclusive. If shared, it may be considered possible to deploy several service components on the node, and if exclusive, only a single component is allowed to be deployed on the node.
S504-2) similar to S503, common component deployment is carried out, if containerized components are deployed in different modes according to component characteristics, if non-containerized components are deployed, generally speaking, a first service is deployed on a certain node, and the service is deployed on other nodes through cloning.
S504-3) registers the components with the endpoint components in S502-2), so that the endpoint components can be managed and scheduled uniformly.
S505: and initiating service cluster deployment by relying on the cluster management platform and the common service module established in the steps S503 and S504, and deploying corresponding service cluster service performance components.
S505-1) selecting a plurality of nodes besides the first node cluster and the node where the public service resides, marking the nodes with main or auxiliary node labels according to the service cluster type, if a plurality of same clusters exist, marking corresponding labels at the same time, and in the actual deployment stage, preferentially deploying the service cluster which is firstly marked with the labels.
S505-2) packaging the components in a package mode according to roles, and performing operations such as service cluster deployment, service component deployment and the like on the role nodes in a first-come first-deployed mode; if a certain component occupies the master node and the slave node at the same time, other components on the master node and the slave node cannot be deployed at the same time; if a certain component only preempts the master node or the slave node, the packages in the same role can only wait for deployment, and the packages in different roles can be deployed at the same time. If the service cluster needs to be configured with multiple main nodes, storage nodes and LB nodes, the nodes need to be additionally selected and marked with corresponding labels for deployment
S505-3) registering the deployed component with the endpoint component in S502-2)
S506: external exposure of external VIPs is performed.
S506-1) creating an IaaS network port for the external VIP, and assigning the address of the external VIP to the port;
s506-2) binding an unused large network floating IP to the port until the cloud platform service cluster system is deployed.
As shown in fig. 4, the high-availability high-performance cloud platform service cluster system provided in this embodiment includes: a cluster management platform module 31, a common service module 32, a high-availability high-performance service cluster module 33, a service access opening module 34, etc., wherein,
the cluster management platform module 31 is generally responsible for interacting with the bottom layer to dispatch resources, and at the same time, provides infrastructure for service cluster deployment, including providing public service access such as a database, a message queue, and a log, and also may be responsible for personalized functions such as elastic expansion and contraction of the service cluster. The module can be responsible for deploying the service cluster, implementing the deployment of HA of the components in the service cluster and registering and maintaining the components besides realizing the high availability of the module. The energy module can adapt to more complex scenes such as virtual machine clusters, physical machine clusters, mixed clusters and the like;
the public service module 32 is generally used for providing basic services for a plurality of service clusters and cluster management platform modules, the HA of storage, data synchronization and the like is realized by the public service module, and the API is uniformly scheduled by the cluster management platform module;
the High-Availability High-performance service cluster module 33, that is, the service cluster module shown in fig. 3, is generally used for user service deployment, and in order to ensure High Availability, the cluster itself implements HA (High Availability), and various components including improving cluster service performance are deployed in the cluster.
Since the above modules relate to the implementation of the containerized component and the non-containerized component HA during deployment, the following focuses on the deployment flow of the two types of components:
containerized component deployment instance:
the deployment of the database tool cluster comprises the following steps:
firstly, randomly selecting a node on a first node cluster to deploy a first database tool, such as a MariaDB container, wherein the container needs to be attached to a certain temporary facility network, the temporary facility network is temporarily named as NET1, an IP address resource pool is set for the container in a configuration file of the database tool container, the resource pool is generally empty, and the container is generally considered as a main container of the database cluster in the setting mode;
a global schema database tool container is created in the head node cluster in the form of service creation of a containerized component cluster management tool, and a designated port is exposed on host. The containers reside on each node due to a global mode, and the number of containers with the same name on each node is not more than two, the containers need to be attached to a NET1 network at the same time, but an IP quota needs to be given in an IP address resource pool of a configuration file, so that the containers can conveniently obtain corresponding IPs, and because a database tool can be searched in NET1 and mutually found, the containers created in the step are sequentially added into a cluster where a main container is located;
modifying the mode of adding the three containers created in the second batch into a mode of not waiting for the main assembly, modifying the starting mode of one container, and shutting down the main container created in the first batch, wherein the creation of the database tool cluster is completed, and the reconnection of the database tool cannot be influenced by the restarting of any container or the restarting of the cluster;
the IP and port of Host are registered with the endpoint component.
The deployment of the message queue tool cluster comprises the following steps:
creating a second temporary facility network, tentatively named NET2, using the containerized component cluster management tool;
creating a message queue tool such as a rabbitmq container in a global mode in a first node cluster, and setting a background process of a containerization assembly cluster management tool in a background of a certain container, wherein the container needs to be hung on NET2 when being started, and enough IP address resource pools need to be configured in a starting configuration file;
after the container is started, the message queue tool cluster connection is carried out according to the following steps: after the containers are started, an effective IP is obtained from the resource pool, the minimum IP address is determined after the background process is operated, and the rest containers are sequentially added into the message queue tool cluster from small to large; in the application, the container with the smallest IP is the master control role, a new master control role can be voted again after the container is dead or a node is dead, and if the cluster is restarted, the container can acquire the IP again and reconnect;
the IP and port of Host are registered with the endpoint component.
Non-containerized component deployment instance:
respectively copying the components to all nodes of a head node cluster, and creating corresponding OCF files for the components;
the OCF file is moved into an identification directory of a non-containerized component cluster management tool, an OCF test is carried out before the components are online, and if the OCF file is written to be in accordance with the standard, all tests are back to pass;
setting parameters such as time intervals for monitoring component resources, setting characteristics such as dependency relationship and node affinity of the component resources, and starting the component on any node;
the component is cloned and the clone attribute is set.
Finally, an implementation example of the service access opening module 34 is as follows:
first, a user interaction interface Web application component needs to be deployed. The component is typically a B/S (Browser/Server) architecture, the way of interacting with the endpoint component is typically a RESTful (Representational State Transfer), which is a software architecture style, request, the interface can provide deployment of clustered public services with HA options and deployment of clustered services; in the application, the user interaction interface component can also provide functions of cluster service deployment blueprint design, service mirror image uploading, service version upgrading rollback, service monitoring alarm, intelligent fault tracing and the like.
Second, an endpoint component of the module needs to be implemented. The endpoint component resides in the head node cluster. The component needs to realize the HA of the component itself in a deployment stage and is responsible for the LBs of other components including cluster management platform components, components in a public service module, service cluster performance components and the like, an independent container needs to be used in an internal interaction stage to be responsible for binding with the internal VIP, once the container is abnormal, the internal VIP can migrate among other nodes in a head node cluster at any time, and the internal VIP is also switched in a binding mode along with the container and always kept on the same node. In addition, the end point component needs to additionally provide a container to be bound with the external VIP, and once the external VIP accesses the abnormal container or the abnormal container, the end point component can be switched to other nodes in the cluster in a binding mode. The user interaction interface component is typically accessed via an external VIP.
Finally, the service cluster interface finally receives the RESTful request message forwarded by the endpoint component, and the service cluster deploys the specific service according to the message body.
Compared with the prior art, the method and the system architecture of the embodiment can efficiently manage the complex service cluster in the complex scene and provide good service: because the system architecture is distributed, a cluster management platform module, a high-availability high-performance service cluster module and a public service module in the modules are respectively resident in different node clusters, horizontal expansion is realized inside the node clusters, the duration of uninterrupted normal service can be ensured, and between the node clusters, the service cluster module depends on the cluster management platform module and the public service module, so that the hierarchy of cluster system service can be ensured in the longitudinal direction, and the operation performance of the cluster system is improved. The system comprises a cluster management platform module, a public service module, a high-availability high-performance service cluster module, a service access development module, a service access management module and a resource scheduling module, wherein the cluster management platform module can provide creation and maintenance of a plurality of clusters and implement the HA of the cluster management module, the public service module mainly provides basic service for a service cluster and the cluster management platform, the high-availability high-performance service cluster module is mainly used for service deployment and implementation of the HA of the service cluster, the service access development module mainly provides a cloud platform service cluster deployment and management entrance for a user and is responsible for internal message processing and resource scheduling, and the module currently resides in a node cluster of the cluster management platform module. The invention can greatly improve the efficiency of deploying, applying and managing a plurality of multi-class service clusters and cluster services for users in various scenes, and greatly reduce the fault rate of cluster service.
In summary, the implementation of the embodiment of the present invention has at least the following advantages:
the embodiment of the invention provides a cloud platform service cluster, a construction method and a device, the cloud platform service cluster method comprises the steps of selecting a node from a cloud platform node library as a first node cluster node, deploying a first node non-containerized component cluster and a first node containerized component cluster on the first node cluster node, and deploying a cluster management platform component, wherein the cluster management platform component comprises a containerized cluster management platform component and a non-containerized cluster management platform component, so that the non-containerized cluster service is realized, the management control on service access is realized based on the non-containerized cluster service, the problem that a part of management tools are difficult to implement containerized and high in availability is solved, and the problem that the prior art does not well solve other non-containerized services in the cluster is solved. Furthermore, the cloud platform service cluster provided by the invention adopts a distributed architecture, and the first node cluster node, the foundation and the public service node are completely separated from the service nodes providing the service cluster, so that the high availability of the service cluster is ensured.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
In particular, in some embodiments, the present invention also provides a computer readable storage medium storing one or more programs, the one or more programs being executable to implement the steps of:
respectively selecting nodes from a cloud platform node library as a first node cluster node, a basic and common service node and a service node;
deploying a first-node non-containerized component cluster and a first-node containerized component cluster on a first-node cluster node, and deploying a cluster management platform component on the first-node cluster node, wherein the cluster management platform component comprises a containerized cluster management platform component and a non-containerized cluster management platform component;
deploying a public service assembly cluster and a basic service assembly cluster on a basic service node and a public service node, and deploying a service cluster and a service performance assembly of the service cluster on the service node;
configuring a network address of an internal local area network, and associating a first node cluster node, a basic and public service node and node internal components and nodes of a service node;
applying for the public network address, binding and exposing the network address.
In some embodiments, one or more of the procedures in the above embodiments may be executed to implement the steps of:
respectively deploying non-containerization component cluster management tools on the first node cluster nodes;
deploying at least one virtual network address service through a non-containerized component cluster management tool, and setting the virtual network address service to pass through each node in a cloud platform node library;
respectively deploying non-containerization end point components on the head node cluster node;
respectively deploying containerization component cluster management tools on the first node cluster nodes;
respectively deploying containerization end point components on the head node cluster node;
binding the containerized endpoint component with the virtual network address service.
In some embodiments, one or more of the procedures in the above embodiments may be executed to implement the steps of:
creating an infrastructure as a service network port for external virtual network address service;
assigning a network address of an external virtual network address service to an infrastructure as a service network port;
applying for a public network address for an infrastructure-as-a-service network port;
the public network address is bound to the infrastructure, i.e. the service network port.
In some embodiments, one or more of the procedures in the above embodiments may be executed to implement the steps of:
selecting at least three nodes with odd number from the platform, namely the service control role nodes of the cloud platform node library as a first node cluster node;
selecting at least two nodes as basic and public service nodes in a cloud platform node library outside a first node cluster node;
and selecting at least one node as a service node from the cloud platform node library except the head node cluster node and the basic and public service nodes.
The above embodiments are only examples of the present invention, and are not intended to limit the present invention in any way, and any simple modification, equivalent change, combination or modification made by the technical essence of the present invention to the above embodiments still fall within the protection scope of the technical solution of the present invention.
Claims (10)
1. A cloud platform service cluster construction method comprises the following steps:
respectively selecting nodes from a cloud platform node library as a first node cluster node, a basic and common service node and a service node;
deploying a first node non-containerized component cluster and a first node containerized component cluster on the first node cluster node;
deploying cluster management platform components on the head node cluster node, wherein the cluster management platform components comprise a containerized cluster management platform component and a non-containerized cluster management platform component;
deploying a common service component cluster and a basic service component cluster on the base and common service nodes;
deploying a service cluster and a service performance component of the service cluster on the service node;
configuring a network address of an internal local area network, and associating the first node cluster node, the basic and public service nodes and node internal components and nodes of the service node;
applying for the public network address, binding and exposing the network address.
2. The cloud platform service cluster building method of claim 1, wherein the number of nodes of the head node cluster node is greater than two; the deploying of the head node non-containerized component cluster and the head node containerized component cluster on the head node cluster node comprises:
respectively deploying non-containerization component cluster management tools on the head node cluster nodes;
deploying at least one virtual network address service through the non-containerized component cluster management tool, and setting the virtual network address service to pass through each node in the cloud platform node library;
respectively deploying non-containerization end point components on the head node cluster node;
respectively deploying containerization component cluster management tools on the head node cluster nodes;
respectively deploying containerization end point components on the head node cluster node;
binding the containerized endpoint component with the virtual network address service.
3. The cloud platform service cluster building method of claim 1, wherein the applying for a public network address, and the binding and exposing of the network address comprises:
creating an infrastructure as a service network port for external virtual network address service;
assigning a network address of the external virtual network address service to the infrastructure as a service network port;
applying for a public network address for the infrastructure-as-a-service network port;
binding the public network address to the infrastructure as a service network port.
4. The cloud platform service cluster building method of any one of claims 1 to 3, wherein the respectively selecting nodes from the cloud platform node library as a head node cluster node, a base and common service node, and a service node comprises:
selecting at least three nodes with odd number from the platform, namely the service control role nodes of the cloud platform node library as the head node cluster nodes;
selecting at least two nodes as the basic and public service nodes in a cloud platform node library outside the head node cluster node;
and selecting at least one node as a service node from the head node cluster node and a cloud platform node library except the basic and public service nodes.
5. A cloud platform service cluster building device comprises: a selection module, a deployment module, an association module, and an exposure module, wherein,
the selection module is used for respectively selecting nodes from the cloud platform node library as a first node cluster node, a foundation and public service node and a service node;
the deployment module is used for deploying the head node non-containerized component cluster and the head node containerized component cluster on the head node cluster node; deploying cluster management platform components on the head node cluster node, wherein the cluster management platform components comprise a containerized cluster management platform component and a non-containerized cluster management platform component; deploying a common service component cluster and a basic service component cluster on the base and common service nodes; deploying a service cluster and a service performance component of the service cluster on the service node;
the association module is used for configuring a network address of an internal local area network and associating the first node cluster node, the basic and public service nodes and node internal components and nodes of the service node;
the exposure module is used for applying for a public network address, and binding and exposing the network address.
6. The cloud platform service cluster building apparatus of claim 5, wherein the number of nodes of the head node cluster node is greater than two; the deployment module is used for respectively deploying a non-containerization component cluster management tool on the head node cluster node, deploying at least one virtual network address service through the non-containerization component cluster management tool, setting the virtual network address service to respectively deploy a non-containerization end point component on the head node cluster node through each node in the cloud platform node library; the cluster management tool is also used for respectively deploying containerization component cluster management tools on the head node cluster nodes, respectively deploying containerization end point components on the head node cluster nodes, and binding the containerization end point components with the virtual network address service.
7. The cloud platform service cluster building apparatus of claim 5, wherein the exposing module is configured to create an infrastructure as a service network port for an external virtual network address service, assign a network address of the external virtual network address service to the infrastructure as a service network port; and applying for a public network address for the infrastructure serving network port, and binding the public network address to the infrastructure serving network port.
8. The cloud platform service cluster building apparatus of any one of claims 5 to 7, wherein the selecting module is configured to select, as the head node cluster node, at least three nodes with an odd number from among platform service control role nodes in the cloud platform node library, select at least two nodes from among cloud platform node libraries other than the head node cluster node as the basic and common service nodes, and select at least one node from among the head node cluster node and the cloud platform node libraries other than the basic and common service nodes as a service node.
9. A cloud platform service cluster, comprising: a cluster management platform module, a public service module, a service cluster module and a service access opening module, wherein,
the service access opening module is used for receiving user operation based on a public network address;
the cluster management platform module is used for executing the user operation through the public service module and the service cluster module based on a network address of an internal local area network, and comprises a first node cluster node, a cluster management platform assembly is deployed on the first node cluster node, the first node cluster node comprises a first node non-containerized assembly cluster and a first node containerized assembly cluster, and the cluster management platform assembly comprises a containerized cluster management platform assembly and a non-containerized cluster management platform assembly;
the public service module is used for providing basic service and public service, the public service module comprises a foundation and public service nodes, and the foundation and the public service nodes comprise a public service assembly cluster and a basic service assembly cluster;
the service cluster module is used for providing service cluster service, and comprises service nodes, and the service nodes are deployed with service clusters and service cluster service performance components.
10. The cloud platform service cluster of claim 9, wherein said head node cluster node, said base and common service nodes, and said business nodes are independent of each other.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710258881.0A CN108737468B (en) | 2017-04-19 | 2017-04-19 | Cloud platform service cluster, construction method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710258881.0A CN108737468B (en) | 2017-04-19 | 2017-04-19 | Cloud platform service cluster, construction method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108737468A CN108737468A (en) | 2018-11-02 |
| CN108737468B true CN108737468B (en) | 2021-11-12 |
Family
ID=63925342
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710258881.0A Active CN108737468B (en) | 2017-04-19 | 2017-04-19 | Cloud platform service cluster, construction method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108737468B (en) |
Families Citing this family (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109491763B (en) * | 2018-11-14 | 2021-07-20 | 北京奇艺世纪科技有限公司 | System deployment method and device and electronic equipment |
| CN111262898B (en) * | 2018-12-01 | 2022-06-14 | 阿里巴巴集团控股有限公司 | Service degradation processing method and device and electronic equipment |
| CN109361775A (en) * | 2018-12-14 | 2019-02-19 | 北京盛元通科技发展有限责任公司 | A kind of cloud service platform |
| CN109799998B (en) * | 2018-12-18 | 2023-02-10 | 深圳先进技术研究院 | OpenStack cluster configuration and batch deployment method and system |
| CN112148348B (en) * | 2019-06-28 | 2023-10-20 | 杭州海康威视数字技术股份有限公司 | Task processing method, device and storage medium |
| CN112532675B (en) * | 2019-09-19 | 2023-04-18 | 贵州白山云科技股份有限公司 | Method, device and medium for establishing network edge computing system |
| CN111008023B (en) * | 2019-12-06 | 2024-01-09 | 无锡华云数据技术服务有限公司 | Instance deployment method and system |
| CN111131449B (en) * | 2019-12-23 | 2021-03-26 | 华中科技大学 | Method for constructing service clustering framework of water resource management system |
| CN111741097B (en) * | 2020-06-15 | 2021-04-02 | 星环信息科技(上海)股份有限公司 | Method for tenant to monopolize node, computer equipment and storage medium |
| CN112084000A (en) * | 2020-07-20 | 2020-12-15 | 北京百度网讯科技有限公司 | Container cluster testing method and device |
| CN111857963A (en) * | 2020-07-28 | 2020-10-30 | 山东超越数控电子股份有限公司 | Container arrangement implementation method, device, equipment and medium for Proxmox VE |
| CN111782232A (en) * | 2020-07-31 | 2020-10-16 | 平安银行股份有限公司 | Cluster deployment method and device, terminal equipment and storage medium |
| CN112084007A (en) * | 2020-09-10 | 2020-12-15 | 星辰天合（北京）数据科技有限公司 | NAS storage upgrading method and device based on virtual machine technology |
| CN112087516A (en) * | 2020-09-10 | 2020-12-15 | 星辰天合（北京）数据科技有限公司 | Storage upgrading method and device based on Docker virtualization technology |
| CN112148429A (en) * | 2020-09-22 | 2020-12-29 | 江苏银承网络科技股份有限公司 | Information processing method and device for managing container arrangement engine cluster |
| CN113507489B (en) * | 2020-09-30 | 2022-10-14 | 西部证券股份有限公司 | Visual deployment, operation and maintenance method of financial private cloud |
| CN112732532A (en) * | 2021-01-15 | 2021-04-30 | 上海浪潮云计算服务有限公司 | Method for managing cluster assembly and centralized managing container service control assembly |
| CN112925609B (en) * | 2021-03-01 | 2022-03-15 | 浪潮云信息技术股份公司 | OpenStack cloud platform upgrading method and device |
| CN113204353B (en) * | 2021-04-27 | 2022-08-30 | 新华三大数据技术有限公司 | Big data platform assembly deployment method and device |
| CN113434370A (en) * | 2021-08-24 | 2021-09-24 | 统信软件技术有限公司 | Server cluster deployment method and device, computing equipment and storage medium |
| CN114567556A (en) * | 2022-03-07 | 2022-05-31 | 海尔数字科技（上海）有限公司 | Virtual machine storage system |
| CN114510152B (en) * | 2022-04-18 | 2022-07-26 | 梯度云科技(北京)有限公司 | Method and device for constructing meta-universe system based on container |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105354076A (en) * | 2015-10-23 | 2016-02-24 | 深圳前海达闼云端智能科技有限公司 | Application deployment method and device |
| CN105376303A (en) * | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN105554015A (en) * | 2015-12-31 | 2016-05-04 | 北京轻元科技有限公司 | Management network and method for multi-tenant container cloud computing system |
| CN105743995A (en) * | 2016-04-05 | 2016-07-06 | 北京轻元科技有限公司 | Transplantable high-available container cluster deploying and managing system and method |
| CN106027643A (en) * | 2016-05-18 | 2016-10-12 | 无锡华云数据技术服务有限公司 | Resource scheduling method based on Kubernetes container cluster management system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9043767B2 (en) * | 2011-04-12 | 2015-05-26 | Pivotal Software, Inc. | Release management system for a multi-node application |
| CN102624919A (en) * | 2012-03-30 | 2012-08-01 | 电子科技大学 | Distributed service integrated system for service-oriented architecture and application method thereof |
| US9575797B2 (en) * | 2015-03-20 | 2017-02-21 | International Business Machines Corporation | Virtual machine migration between hypervisor virtual machines and containers |
| CN105138389B (en) * | 2015-07-30 | 2019-01-11 | 北京京东尚科信息技术有限公司 | The management method and system of virtual unit in a kind of cluster |
-
2017
- 2017-04-19 CN CN201710258881.0A patent/CN108737468B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105354076A (en) * | 2015-10-23 | 2016-02-24 | 深圳前海达闼云端智能科技有限公司 | Application deployment method and device |
| CN105376303A (en) * | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN105554015A (en) * | 2015-12-31 | 2016-05-04 | 北京轻元科技有限公司 | Management network and method for multi-tenant container cloud computing system |
| CN105743995A (en) * | 2016-04-05 | 2016-07-06 | 北京轻元科技有限公司 | Transplantable high-available container cluster deploying and managing system and method |
| CN106027643A (en) * | 2016-05-18 | 2016-10-12 | 无锡华云数据技术服务有限公司 | Resource scheduling method based on Kubernetes container cluster management system |
Non-Patent Citations (1)
| Title |
|---|
| 基于容器云平台的网络资源管理与配置系统设计与实现;陈星宇;《中国优秀硕士学位论文全文数据库 信息科技辑》;20160715;第10-15页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108737468A (en) | 2018-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108737468B (en) | Cloud platform service cluster, construction method and device | |
| US11294699B2 (en) | Dynamically scaled hyperconverged system establishing minimum supported interoperable communication protocol between clusters in a cluster group | |
| US11704144B2 (en) | Creating virtual machine groups based on request | |
| US11146620B2 (en) | Systems and methods for instantiating services on top of services | |
| US10275851B1 (en) | Checkpointing for GPU-as-a-service in cloud computing environment | |
| US10701139B2 (en) | Life cycle management method and apparatus | |
| CN105207798B (en) | Service arrangement method and device in software defined network | |
| Zhang et al. | Cloud computing: state-of-the-art and research challenges | |
| WO2019179453A1 (en) | Virtual machine creation method and apparatus | |
| US8756597B2 (en) | Extending functionality of legacy services in computing system environment | |
| CN108293041B (en) | Distributed system, resource container allocation method, resource manager and application controller | |
| US20170063714A1 (en) | System and Method for Network Function Virtualization Resource Management | |
| US11392422B1 (en) | Service-managed containers for container orchestration service | |
| CN111641515B (en) | VNF life cycle management method and device | |
| WO2020135228A1 (en) | Cloud platform deployment method and apparatus, server and storage medium | |
| CN111324571A (en) | Container cluster management method, device and system | |
| US11740936B2 (en) | Method and system for managing cloud resources | |
| TW201229795A (en) | Web service patterns for globally distributed service fabric | |
| KR20210096259A (en) | Allocate compute resources | |
| WO2017181829A1 (en) | Virtualization platform operation method and virtualization platform | |
| JP2024512209A (en) | Information processing method based on IoT devices, related devices and storage media | |
| CN113204353A (en) | Big data platform assembly deployment method and device | |
| CN109309581B (en) | Container management system crossing hardware architecture | |
| CN105763545B (en) | A kind of BYOD method and device | |
| JP2024501005A (en) | Management method and device for container clusters |
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 |