CN112882790A - Cloud edge cooperative management method based on distributed cloud platform - Google Patents
Cloud edge cooperative management method based on distributed cloud platform Download PDFInfo
- Publication number
- CN112882790A CN112882790A CN202011630671.8A CN202011630671A CN112882790A CN 112882790 A CN112882790 A CN 112882790A CN 202011630671 A CN202011630671 A CN 202011630671A CN 112882790 A CN112882790 A CN 112882790A
- Authority
- CN
- China
- Prior art keywords
- cloud
- edge
- platform
- management
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 98
- 238000003860 storage Methods 0.000 claims description 45
- 230000006978 adaptation Effects 0.000 claims description 27
- 238000000034 method Methods 0.000 claims description 17
- 238000011084 recovery Methods 0.000 claims description 14
- 230000008569 process Effects 0.000 claims description 12
- 238000004458 analytical method Methods 0.000 claims description 6
- 238000012986 modification Methods 0.000 claims description 5
- 230000004048 modification Effects 0.000 claims description 5
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 238000013507 mapping Methods 0.000 claims description 3
- 239000012792 core layer Substances 0.000 abstract description 3
- 239000010410 layer Substances 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000004140 cleaning Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000005206 flow analysis Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000013508 migration Methods 0.000 description 2
- 230000005012 migration Effects 0.000 description 2
- 239000000523 sample Substances 0.000 description 2
- 239000013589 supplement Substances 0.000 description 2
- 206010033799 Paralysis Diseases 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 210000004556 brain Anatomy 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000009792 diffusion process Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000007480 spreading Effects 0.000 description 1
- 238000003892 spreading Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5072—Grid computing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45587—Isolation or security of virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a cloud edge collaborative management method based on a distributed cloud platform, which is characterized in that Docker containers are managed and arranged through Kubernets, and a core layer of a multi-cloud management platform encapsulates self service components in different Docker containers; the multi-cloud management platform is arranged based on the distributed architecture, the cooperative relationship between the central cloud and the edge cloud is realized, the resource requirement of the edge cloud can be met through the calling of the central cloud to the resources, and meanwhile, the residual resources of the edge cloud or the central cloud can be fully utilized.
Description
Technical Field
The invention relates to the field of cloud platforms, in particular to a cloud edge collaborative management method based on a distributed cloud platform.
Background
With the advent of the big data era, the processing requirements of a large amount of data are difficult to meet by a user terminal component, and therefore the concept of a cloud platform is provided. Conventional cloud platforms are classified into three types, including storage type cloud platforms based on data storage, computing type cloud platforms based on data processing, and comprehensive type cloud platforms considering both storage and computing. The cloud platform can provide instant software service and development environment for the user, and the cost of using and developing programs by the user is reduced.
However, with the commercial deployment of 5G, the arrival of everything interconnection and the further increase of terminal types and applications, the traditional cloud platform computing with a centralized architecture cannot meet the requirements of "large connection, low delay and large bandwidth" on the terminal side. The rapid growth of network data puts high demands on the storage capacity and the computing capacity of a cloud center of a centralized architecture. On the other hand, in the conventional cloud platform, all data and computation are placed in the cloud computing center, and if the cloud computing center is turned off or restarted, the whole network system is paralyzed, and the robustness is low. Finally, different cloud centers in the traditional cloud platform are independent of each other, information and resources are not transmitted among the different cloud centers, the coordination performance is lacked, the unified scheduling management of the resources is difficult to perform, and the allocation of the resources is inconvenient. Therefore, a management method for cooperation between the center cloud and the edge cloud is needed.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provides a cloud edge cooperative management method based on a distributed cloud platform, which is used for uniformly scheduling and managing the resources of edge clouds in a cloud center.
A cloud edge collaborative management method based on a distributed cloud platform comprises the following steps:
step 1: deploying a multi-cloud management platform; the multi-cloud management platform comprises a central cloud and an edge cloud;
step 2: a super administrator allocates accounts for users of a central cloud or an edge cloud on a multi-cloud management platform;
and step 3: the central cloud or the edge cloud logs in a multi-cloud management platform by using the allocated account number to manage, schedule and newly add the cloud resources;
and 4, step 4: a user issues operation on a multi-cloud management platform; the user can issue operation on a multi-cloud management platform of the edge cloud; a core module of the multi-cloud management platform receives an operation instruction, and analyzes the operation instruction to obtain a corresponding service data request; the core module of the multi-cloud management platform is arranged in the central cloud;
and 5: an API route processor of the core module analyzes the service data request to obtain analysis data;
step 6: the API routing analyzer combines the mapping relation of the current edge cloud user according to the analysis data and selects a southbound interface of the center cloud according to the authority and the parameters;
and 7: the southbound interface processes the service data request and issues an API request to a target API adaptation module; wherein the API adaptation module is arranged in the edge cloud;
and 8: after receiving a service data request from a core module of the multi-cloud management platform, the API adaptation module transfers the service data request to a message processing center of the API adaptation module;
and step 9: the message processing center processes the information, then generates a URL required by an API of the edge cloud, and configures a corresponding request message body and parameters according to the service data request;
step 10: the cloud interface of the edge cloud sends out resource requests and scheduling of the multi-cloud resource pool according to the corresponding request message body and the parameters; and realizing cloud edge cooperation.
Furthermore, the deployment of the multi-cloud management platform in the step 1 adopts a micro-service architecture, and the deployment is realized through a Docker container; the center cloud and the edge cloud communicate in a REST API and message queue mode; deployment of cloud management bottom servers of the central cloud and the edge cloud is achieved by kubernets; the central cloud and the edge cloud are both arranged in the same backbone network, and the backbone network adopts MPLS VPN.
Further, the network of the central cloud is issued by using an sdn controller through netconf, and the storage of the central cloud uses centralized storage; the edge cloud adopts super-convergence architecture deployment, the computation, storage and network convergence deployment of the edge cloud, the central management platform instruction is uniformly received, the network of the edge cloud is realized by using an openstack neutron component, and the storage of the edge cloud is developed secondarily by using ceph.
Further, the edge cloud adopts independent storage, including independent distributed storage and independent disk array storage; and selecting a block object, object storage and file storage according to the node service requirement by a storage mode.
Further, the account allocation in the step 2 includes an account allocation type, an account node and an account authority; the account types comprise a tenant account, a tourist account and an administrator account; the account number authority comprises a node use authority and a node redistribution authority, wherein the node use authority refers to the calling authority of a certain node resource, and the node redistribution authority refers to the authority for redistributing the node with the calling authority.
Further, in step 3, the content of management scheduling includes management of a cloud host, a cloud hard disk, and a cloud firewall.
Further, the management scheduling of the cloud host includes operations of creating, querying, deleting, modifying, starting and stopping, suspending/restoring, migrating, backing up/restoring the virtual machine, changing/revoking host configuration, loading/viewing/unloading the cloud hard disk, and creating/viewing/deleting the virtual network card; the management scheduling of the cloud hard disk comprises the operations of applying for, destroying, inquiring, checking, setting a label, mounting, unloading and snapshotting the cloud hard disk; the management scheduling of the cloud firewall comprises the operations of rule creation, deletion, inquiry and modification of the cloud firewall.
Further, the target API adaptation module in step 7 represents an API adaptation module corresponding to the edge cloud to be called, which is obtained according to the service data request in step 4; the target API adaptation module includes API adaptation modules of at least one edge cloud.
Further, when the service data request is processed, the priority of the service data request is firstly judged, and the API requests are sequentially issued according to the priority for a plurality of service data requests received simultaneously.
Further, the target API adaptation module selects an edge cloud that is near the edge cloud that issued the operation in step 4, including the edge cloud; the cloud-edge collaboration in the step 10 includes resource collaboration, security policy collaboration, application management collaboration, service management collaboration, and edge-edge collaboration; and the edge cloud is also provided with a disaster recovery end.
The invention has the beneficial effects that:
the method comprises the steps that a multi-cloud management platform is arranged based on a distributed architecture, the cooperative relation between a central cloud and an edge cloud is achieved, the resource requirement of the edge cloud can be met through the calling of the central cloud to resources, and meanwhile, the residual resources of the edge cloud or the central cloud can be fully utilized;
by setting resource cooperation, computing resources, storage resources and network resources of the center cloud and the edge cloud can be fully utilized;
by setting security strategy cooperation, a firewall, a security group, flow cleaning and flow analysis are respectively arranged at two ends of a network, malicious flow is found in time, and malicious flow diffusion is avoided;
the central cloud and the edge cloud are arranged to realize communication through a backbone network, so that the response delay of a service system is low;
the Docker containers are managed and arranged through Kubernets, the core layer of the multi-cloud management platform encapsulates the service components of the Docker containers in different Docker containers, and when a server goes down, the Docker containers can be replaced in a Kubernets cluster in time.
Drawings
Fig. 1 is a schematic block diagram of cloud edge coordination according to a first embodiment of the present invention;
fig. 2 is a control relationship diagram of a center cloud and an edge cloud according to a first embodiment of the present invention;
fig. 3 is a diagram of a multi-cloud management platform structure according to a first embodiment of the present invention;
fig. 4 is a schematic block diagram of a side disaster recovery apparatus according to a first embodiment of the present invention.
Detailed Description
The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict.
It should be noted that the drawings provided in the following embodiments are only for illustrating the basic idea of the present invention, and the components related to the present invention are only shown in the drawings rather than drawn according to the number, shape and size of the components in actual implementation, and the type, quantity and proportion of the components in actual implementation may be changed freely, and the layout of the components may be more complicated.
The first embodiment is as follows:
as shown in fig. 1 to 3, a cloud edge collaborative management method based on a distributed cloud platform includes the following steps:
step 1: deploying a multi-cloud management platform; the multi-cloud management platform comprises a central cloud and an edge cloud;
step 2: a super administrator allocates accounts for users of a central cloud or an edge cloud on a multi-cloud management platform;
and step 3: the central cloud or the edge cloud logs in a multi-cloud management platform by using the allocated account number to manage, schedule and newly add the cloud resources;
and 4, step 4: a user issues operation on a multi-cloud management platform; the user can issue operation on a multi-cloud management platform of the edge cloud; a core module of the multi-cloud management platform receives an operation instruction, and analyzes the operation instruction to obtain a corresponding service data request; the core module of the multi-cloud management platform is arranged in the central cloud;
and 5: an API route processor of the core module analyzes the service data request to obtain analysis data;
step 6: the API routing analyzer combines the mapping relation of the current edge cloud user according to the analysis data and selects a southbound interface of the center cloud according to the authority and the parameters;
and 7: the southbound interface processes the service data request and issues an API request to a target API adaptation module; wherein the API adaptation module is arranged in the edge cloud;
and 8: after receiving a service data request from a core module of the multi-cloud management platform, the API adaptation module transfers the service data request to a message processing center of the API adaptation module;
and step 9: the message processing center processes the information, then generates a URL required by an API of the edge cloud, and configures a corresponding request message body and parameters according to the service data request;
step 10: the cloud interface of the edge cloud sends out resource requests and scheduling of the multi-cloud resource pool according to the corresponding request message body and the parameters; and realizing cloud edge cooperation.
The deployment of the multi-cloud management platform in the step 1 adopts a micro-service architecture, a core layer of the multi-cloud management platform encapsulates service components of the multi-cloud management platform into different Docker containers, the deployment is realized through the Docker containers, and the Docker containers are managed and arranged through Kubernetes; the center cloud and the edge cloud communicate in a REST API and message queue mode; the deployment of the cloud management bottom layer servers of the central cloud and the edge cloud is realized by kubernets. The network of the central cloud is issued by using an sdn controller through netconf, and the storage of the central cloud uses centralized storage; the edge cloud is deployed by adopting a super-convergence architecture, wherein the computation, storage and network convergence deployment of the edge cloud uniformly receive a central management platform instruction, the network of the edge cloud is realized by using an openstack neutron component, and the storage of the edge cloud is developed secondarily by using ceph. The central cloud and the edge cloud are uniformly distributed in the same backbone network, and the backbone network adopts MPLS VPN, so that the communication safety and the communication speed of the edge cloud and the central cloud are ensured. When the underlying server is down in the embodiment, the docker container runs on the kubernets cluster, so that the server resources can be easily converted, and the stable and continuous operation of the underlying server is ensured. It should be noted that in some other embodiments, the edge cloud can also use independent storage, including independent distributed storage, independent disk array storage, and the like, and the storage manner may select a block object, an object storage, a file storage, and the like according to the service requirement of the node.
The distributed account in the step 2 comprises a distributed account type, an account node and an account authority; the account types comprise a tenant account, a tourist account, an administrator account and the like, the tenant account is an account for setting lease time, the administrator account is an account for managing nodes and authority of a corresponding center cloud or edge cloud, and the tourist account is an experience account; the account node is a corresponding node of the edge cloud; the account number authority comprises a node use authority and a node redistribution authority, wherein the node use authority refers to the calling authority of a certain node resource, and the node redistribution authority refers to the authority for redistributing the node with the calling authority. It should be noted that the account assignment may be performed in a central cloud or an edge cloud.
In the step 3, the content of management scheduling includes management of the cloud host, the cloud hard disk and the cloud firewall, where the cloud host management includes operations of creating, querying, deleting, modifying, starting and stopping, suspending/restoring, migrating, backing up/restoring the virtual machine, changing/cancelling host configuration, loading/viewing/unloading the cloud hard disk, creating/viewing/deleting the virtual network card, and the like for the cloud host; the cloud hard disk management comprises the operations of applying for, destroying, inquiring, checking, setting labels, mounting, unloading, snapshotting and the like on the cloud hard disk; the cloud firewall management comprises the operations of rule creation, deletion, inquiry, modification and the like on the cloud firewall. The management of the cloud host, the cloud hard disk and the cloud firewall is used for realizing the management of the full life cycle of the multi-cloud management platform.
And the target API adaptation module in the step 7 represents an API adaptation module corresponding to the edge cloud which is obtained according to the service data request in the step 4 and needs to be called. The target API adaptation module includes API adaptation modules of at least one edge cloud. When processing the service data request, the priority of the service data request is judged, and for a plurality of service data requests received at the same time, the API requests are sequentially issued according to the priority. It should be noted that in this example, the target API adaptation module is generally selected in the vicinity of the edge cloud issuing the operation in step 4, and includes the edge cloud.
The cloud-edge collaboration in step 10 includes resource collaboration, security policy collaboration, application management collaboration, service management collaboration, and edge-edge collaboration.
The resource cooperation comprises the cooperation of infrastructure resources such as computing resource cooperation, storage resource cooperation and network resource cooperation provided by edge nodes arranged in edge clouds for value-added network services, and the life cycle management of edge node equipment. The computing resource collaborative representation is that in the case that the resources of the edge cloud are insufficient, the resources of the center cloud or other edge clouds are called through steps 6 and 7 to supplement so as to meet the demand of the computing resources of the edge cloud sending the request, wherein the resources of the center cloud or other edge clouds include bare computers, virtual machines, containers and the like. The storage resource cooperation means that when the storage capacity of the edge cloud is difficult to meet the storage requirement, part of data of the edge cloud is transmitted through a network and stored in the center cloud; and when the edge cloud calls the part of data, the part of data is transmitted back to the edge cloud through the network. The network resource cooperation means that the central cloud and the edge clouds are connected through a backbone network, wherein at least one connection network is arranged between one edge cloud and one central cloud; when the network with the shortest distance between the edge cloud and the center cloud is congested, the network controller senses the congestion and leads the traffic between the edge cloud and the center cloud to other idle networks. The network controller comprises a central controller and a network probe, wherein the central controller is arranged in the central cloud, and the network probe is arranged in the edge cloud.
The security policy cooperation comprises two parts, one part is a network of an edge cloud access center cloud, a firewall and a security group are arranged at one end of the edge cloud, and on the other hand, the flow cleaning and flow analysis processes are arranged when network data of the center cloud is accessed, wherein the existing method is adopted for the flow cleaning and the flow analysis. In the process of transmitting the network of the edge cloud and the network of the center cloud, if the center cloud finds that malicious traffic exists in a certain edge cloud, all the connection networks with the edge cloud are cut off, and the malicious traffic is prevented from spreading in the whole multi-cloud management platform.
The application collaborative management is as described in step 3.
The service management cooperation means that unified arrangement of network services is realized on a multi-cloud management platform, and through the steps 6 and 7, the central cloud simultaneously processes a plurality of service data requests, classifies the service data requests according to priority levels, and sequentially issues API requests.
The edge-edge cooperation means that when simultaneous deployment or application live migration is performed on different edge clouds, the central cloud can deploy an application on an edge cloud with a high demand in advance according to the demands of the application on the different edge clouds at different time points, and issue a strategy, so that the application is gradually migrated to other corresponding edge clouds with demands, and smooth migration of the application is realized.
In the implementation process of the embodiment, the edge cloud computing can provide a targeted computing power for the terminal-side data source through the infrastructure distributed in the closest distance to the terminal of the edge cloud. The calculation forces can end part of data processing at the edge side, and the other part of the data processing can be processed and then transmitted back to the central cloud. Therefore, the edge cloud computing provides a new elastic computing resource, realizes the cooperation and the cooperation with the center cloud, and provides cloud computing service meeting the technical requirements for the terminal. The edge cloud computing realizes the synergy of low time delay and low cost, can effectively resist unstable factors such as network jitter and the like, and improves the overall robustness of the system.
As shown in fig. 4, in order to enhance the stability of the cloud management platform, a disaster recovery end is further disposed on the edge cloud to implement edge disaster recovery, where the method for arranging edge disaster recovery includes the following steps:
step S1: the edge cloud in the multi-cloud management platform has at least two nodes; selecting two nodes in the edge cloud, namely a node I and a node II; in the example, the first node and the second node are located in different edge clouds; the method comprises the steps of getting through a network between two nodes, wherein the network comprises a management layer and a service layer;
step S2: arranging a production end and a disaster recovery end at an edge node; the production end and the disaster backup end adopt super-fusion deployment, and a virtualized kernel platform and distributed storage are deployed; the production end comprises a node I, and the node I is used as a management node and a service node; the disaster recovery end comprises a node II which is used as a disaster recovery node;
step S3: deploying recovery management modules SRM on a virtualization management layer of a node I and a node II, and butting a storage copy adapter SRA of a node in a storage layer;
step S4: adding a computing host in a node I to a local address pool, adding a computing host in a node II to a remote address pool, and simultaneously establishing remote equipment between the node I and the node II to complete the configuration synchronization of the virtual machines; the remote equipment can quickly receive data and quickly complete the copying;
step S5: establishing an asynchronous remote copy strategy and a data synchronization strategy, and designating block equipment of a node I and a node II;
step S6: establishing an asynchronous remote copying relation between the block equipment of the node I and the block equipment of the node II, and configuring a data synchronization strategy between the block equipment; wherein the data synchronization strategy is carried out after the establishment of the asynchronous remote copy relationship is completed; and finishing the arrangement of the disaster recovery devices.
The virtual machine configuration in the step S4 includes virtual machine specification, network and security.
In the step S5, the block device is an RBD device; the RBD device represents a block device provided by Ceph distributed storage, wherein the block device adopts a Ceph system as a core bottom layer. When the virtual machine of the edge cloud is directly interfaced with the RBD device, a cluster file system (ocfs2) based on a shared disk is not used, the granularity of storage use is changed from a host machine to a virtual machine, and the problem of Fence does not exist. The Fence represents a mechanism of the cluster file system, and the purpose of setting the Fence mechanism is to prevent the file system cluster from generating a 'brain crack' problem and ensure the consistency of shared storage data.
When the block device in the node one and the block device in the node two are remotely copied in one step in step S6, the storage block is copied in lun units.
After the edge disaster recovery is finished, when the first node fails, the SRM of the second node executes a self-defined switching script and reconfigures the IP address of the virtual machine of the edge cloud on the second node, so that the network configuration of the second node is consistent with that of the first node; and completing the switching process of the edge disaster recovery, and ensuring that the edge cloud can stably operate, thereby ensuring the stability of the multi-cloud management platform.
In the implementation process of edge disaster recovery, if a node I fails, the node II with consistent data can replace the node I at the first time, so that the core service system can be timely recovered at another edge node through the virtualized HA, and the normal operation of the core service system is not affected. On the other hand, by adopting the first node and the second node of the adjacent edge cloud, edge data safety backup is rapidly realized, the bandwidth resource of a long-distance link with the cloud end is saved while the transmission time of the cloud end is saved, the high reliability of the distributed cloud platform is greatly improved, and the method is a powerful supplement for a cloud edge backup mode.
The above description is only one specific example of the present invention and should not be construed as limiting the invention in any way. It will be apparent to persons skilled in the relevant art(s) that, having the benefit of this disclosure and its principles, various modifications and changes in form and detail can be made without departing from the principles and structures of the invention, which are, however, encompassed by the appended claims.
Claims (10)
1. A cloud edge collaborative management method based on a distributed cloud platform is characterized by comprising the following steps:
step 1: deploying a multi-cloud management platform; the multi-cloud management platform comprises a central cloud and an edge cloud;
step 2: a super administrator allocates accounts for users of a central cloud or an edge cloud on a multi-cloud management platform;
and step 3: the central cloud or the edge cloud logs in a multi-cloud management platform by using the allocated account number to manage, schedule and newly add the cloud resources;
and 4, step 4: a user issues operation on a multi-cloud management platform; the user can issue operation on a multi-cloud management platform of the edge cloud; a core module of the multi-cloud management platform receives an operation instruction, and analyzes the operation instruction to obtain a corresponding service data request; the core module of the multi-cloud management platform is arranged in the central cloud;
and 5: an API route processor of the core module analyzes the service data request to obtain analysis data;
step 6: the API routing analyzer combines the mapping relation of the current edge cloud user according to the analysis data and selects a southbound interface of the center cloud according to the authority and the parameters;
and 7: the southbound interface processes the service data request and issues an API request to a target API adaptation module; wherein the API adaptation module is arranged in the edge cloud;
and 8: after receiving a service data request from a core module of the multi-cloud management platform, the API adaptation module transfers the service data request to a message processing center of the API adaptation module;
and step 9: the message processing center processes the information, then generates a URL required by an API of the edge cloud, and configures a corresponding request message body and parameters according to the service data request;
step 10: the cloud interface of the edge cloud sends out resource requests and scheduling of the multi-cloud resource pool according to the corresponding request message body and the parameters; and realizing cloud edge cooperation.
2. The cloud edge collaborative management method based on the distributed cloud platform according to claim 1, wherein deployment of the multi-cloud management platform in step 1 is achieved through a Docker container by adopting a micro-service architecture; the center cloud and the edge cloud communicate in a REST API and message queue mode; deployment of cloud management bottom servers of the central cloud and the edge cloud is achieved by kubernets; the central cloud and the edge cloud are both arranged in the same backbone network, and the backbone network adopts MPLS VPN.
3. The cloud-edge collaborative management method based on the distributed cloud platform as claimed in claim 2, wherein the network of the central cloud is distributed by using sdn controller through netconf, and the storage of the central cloud uses centralized storage; the edge cloud adopts super-convergence architecture deployment, the computation, storage and network convergence deployment of the edge cloud, the central management platform instruction is uniformly received, the network of the edge cloud is realized by using an openstack neutron component, and the storage of the edge cloud is developed secondarily by using ceph.
4. The cloud edge collaborative management method based on the distributed cloud platform as claimed in claim 2, wherein the edge cloud employs independent storage, including independent distributed storage, independent disk array storage; and selecting a block object, object storage and file storage according to the node service requirement by a storage mode.
5. The cloud-edge collaborative management method based on the distributed cloud platform according to claim 1, wherein the account allocation in the step 2 includes an account allocation type, an account node and an account authority; the account types comprise a tenant account, a tourist account and an administrator account; the account number authority comprises a node use authority and a node redistribution authority, wherein the node use authority refers to the calling authority of a certain node resource, and the node redistribution authority refers to the authority for redistributing the node with the calling authority.
6. The cloud-edge collaborative management method based on the distributed cloud platform as claimed in claim 1, wherein in the step 3, the content of the management scheduling includes management of a cloud host, a cloud hard disk and a cloud firewall.
7. The cloud-edge collaborative management method based on the distributed cloud platform of claim 6, wherein the management scheduling of the cloud host includes operations of creating, querying, deleting, modifying, starting and stopping, suspending/resuming, migrating, backing up/resuming a virtual machine, changing/revoking a host configuration, loading/viewing/unloading a cloud hard disk, and creating/viewing/deleting a virtual network card; the management scheduling of the cloud hard disk comprises the operations of applying for, destroying, inquiring, checking, setting a label, mounting, unloading and snapshotting the cloud hard disk; the management scheduling of the cloud firewall comprises the operations of rule creation, deletion, inquiry and modification of the cloud firewall.
8. The cloud edge collaborative management method based on the distributed cloud platform according to claim 1, wherein the target API adaptation module in step 7 represents an API adaptation module corresponding to an edge cloud to be called, which is obtained according to the service data request in step 4; the target API adaptation module includes API adaptation modules of at least one edge cloud.
9. The cloud edge collaborative management method based on the distributed cloud platform as claimed in claim 8, wherein when the service data request is processed, the priority of the service data request is firstly judged, and for a plurality of service data requests received simultaneously, the API requests are sequentially issued according to the priority.
10. The cloud-edge collaborative management method based on the distributed cloud platform according to claim 8, wherein the target API adaptation module issues an edge cloud in step 4, which is close to the operated edge cloud, to select the edge cloud, including the edge cloud; the cloud-edge collaboration in the step 10 includes resource collaboration, security policy collaboration, application management collaboration, service management collaboration, and edge-edge collaboration; and the edge cloud is also provided with a disaster recovery end.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011630671.8A CN112882790A (en) | 2020-12-31 | 2020-12-31 | Cloud edge cooperative management method based on distributed cloud platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011630671.8A CN112882790A (en) | 2020-12-31 | 2020-12-31 | Cloud edge cooperative management method based on distributed cloud platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112882790A true CN112882790A (en) | 2021-06-01 |
Family
ID=76046526
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011630671.8A Pending CN112882790A (en) | 2020-12-31 | 2020-12-31 | Cloud edge cooperative management method based on distributed cloud platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112882790A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113625352A (en) * | 2021-08-11 | 2021-11-09 | 王佳馨 | Urban underground space resistivity sensing system and data acquisition method based on cloud edge-end cooperation |
| CN114095964A (en) * | 2021-11-19 | 2022-02-25 | 中国联合网络通信集团有限公司 | Fault recovery method and device and computer readable storage medium |
| CN114124951A (en) * | 2021-10-18 | 2022-03-01 | 浪潮通信信息系统有限公司 | Method and system for constructing industry cloud service instance in multi-cloud environment |
| CN114401183A (en) * | 2022-01-17 | 2022-04-26 | 杭州瑞网广通信息技术有限公司 | Edge cloud disaster recovery system, method and device based on distributed cloud platform |
| CN114567648A (en) * | 2022-03-24 | 2022-05-31 | 阿里巴巴（中国）有限公司 | Distributed cloud system |
| CN114710489A (en) * | 2022-03-31 | 2022-07-05 | 浪潮云信息技术股份公司 | Distributed cloud resource scheduling method and device and distributed cloud |
| CN115473898A (en) * | 2022-11-14 | 2022-12-13 | 杭州欧若数网科技有限公司 | Graph database management method and system in edge computing scene |
| WO2023109062A1 (en) * | 2021-12-14 | 2023-06-22 | 中电信数智科技有限公司 | Cloud disaster recovery system and method, electronic device, and storage medium |
| CN117032940A (en) * | 2023-10-08 | 2023-11-10 | 北京小米移动软件有限公司 | System, method and device for scheduling resources, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103297507A (en) * | 2013-05-13 | 2013-09-11 | 西安电子科技大学 | Cloud computing operation system and method for providing services to users |
| CN110569101A (en) * | 2018-06-05 | 2019-12-13 | 华为技术有限公司 | Method and device for managing container service |
| CN110851145A (en) * | 2019-09-30 | 2020-02-28 | 烽火通信科技股份有限公司 | Edge cloud installation and maintenance method and system based on container arrangement |
| CN111726403A (en) * | 2020-06-11 | 2020-09-29 | 深圳市赛宇景观设计工程有限公司 | Cross-cloud-platform big data management method and system |
| WO2020207264A1 (en) * | 2019-04-08 | 2020-10-15 | 阿里巴巴集团控股有限公司 | Network system, service provision and resource scheduling method, device, and storage medium |
| CN111901173A (en) * | 2020-07-30 | 2020-11-06 | 山东超越数控电子股份有限公司 | Cloud edge cooperative system construction method, device, equipment and readable medium |
-
2020
- 2020-12-31 CN CN202011630671.8A patent/CN112882790A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103297507A (en) * | 2013-05-13 | 2013-09-11 | 西安电子科技大学 | Cloud computing operation system and method for providing services to users |
| CN110569101A (en) * | 2018-06-05 | 2019-12-13 | 华为技术有限公司 | Method and device for managing container service |
| WO2020207264A1 (en) * | 2019-04-08 | 2020-10-15 | 阿里巴巴集团控股有限公司 | Network system, service provision and resource scheduling method, device, and storage medium |
| CN111800283A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Network system, service providing and resource scheduling method, device and storage medium |
| CN110851145A (en) * | 2019-09-30 | 2020-02-28 | 烽火通信科技股份有限公司 | Edge cloud installation and maintenance method and system based on container arrangement |
| CN111726403A (en) * | 2020-06-11 | 2020-09-29 | 深圳市赛宇景观设计工程有限公司 | Cross-cloud-platform big data management method and system |
| CN111901173A (en) * | 2020-07-30 | 2020-11-06 | 山东超越数控电子股份有限公司 | Cloud edge cooperative system construction method, device, equipment and readable medium |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113625352A (en) * | 2021-08-11 | 2021-11-09 | 王佳馨 | Urban underground space resistivity sensing system and data acquisition method based on cloud edge-end cooperation |
| CN114124951A (en) * | 2021-10-18 | 2022-03-01 | 浪潮通信信息系统有限公司 | Method and system for constructing industry cloud service instance in multi-cloud environment |
| CN114124951B (en) * | 2021-10-18 | 2024-04-26 | 浪潮通信信息系统有限公司 | Method and system for constructing industry cloud service instance in multi-cloud environment |
| CN114095964A (en) * | 2021-11-19 | 2022-02-25 | 中国联合网络通信集团有限公司 | Fault recovery method and device and computer readable storage medium |
| CN114095964B (en) * | 2021-11-19 | 2023-05-26 | 中国联合网络通信集团有限公司 | Fault recovery method and device and computer readable storage medium |
| WO2023109062A1 (en) * | 2021-12-14 | 2023-06-22 | 中电信数智科技有限公司 | Cloud disaster recovery system and method, electronic device, and storage medium |
| CN114401183A (en) * | 2022-01-17 | 2022-04-26 | 杭州瑞网广通信息技术有限公司 | Edge cloud disaster recovery system, method and device based on distributed cloud platform |
| CN114567648A (en) * | 2022-03-24 | 2022-05-31 | 阿里巴巴（中国）有限公司 | Distributed cloud system |
| CN114710489A (en) * | 2022-03-31 | 2022-07-05 | 浪潮云信息技术股份公司 | Distributed cloud resource scheduling method and device and distributed cloud |
| CN115473898A (en) * | 2022-11-14 | 2022-12-13 | 杭州欧若数网科技有限公司 | Graph database management method and system in edge computing scene |
| CN117032940A (en) * | 2023-10-08 | 2023-11-10 | 北京小米移动软件有限公司 | System, method and device for scheduling resources, electronic equipment and storage medium |
| CN117032940B (en) * | 2023-10-08 | 2024-02-13 | 北京小米移动软件有限公司 | System, method and device for scheduling resources, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113190378B (en) | Edge cloud disaster recovery method based on distributed cloud platform | |
| CN112882790A (en) | Cloud edge cooperative management method based on distributed cloud platform | |
| EP4049435B1 (en) | Dynamic resource movement in heterogeneous computing environments including cloud edge locations | |
| CN109743415B (en) | Public cloud network elastic IP implementation method and system | |
| CN108737468B (en) | Cloud platform service cluster, construction method and device | |
| US11917446B1 (en) | Mobility of cloud compute instances hosted within communications service provider networks | |
| US9999030B2 (en) | Resource provisioning method | |
| US11356500B1 (en) | Disaggregated processing of radio-based applications | |
| JP6113849B2 (en) | Method and apparatus for automatically deploying geographically distributed applications in the cloud | |
| CN107209710B (en) | Node system, server device, scaling control method, and program | |
| CN113364850B (en) | Software-defined cloud-edge collaborative network energy consumption optimization method and system | |
| WO2017071169A1 (en) | Method, device and server for service migration during software upgrade under nfv architecture | |
| US11669360B2 (en) | Seamless virtual standard switch to virtual distributed switch migration for hyper-converged infrastructure | |
| WO2014169870A1 (en) | Virtual network element automatic loading and virtual machine ip address acquisition method and system, and storage medium | |
| WO2012068867A1 (en) | Virtual machine management system and using method thereof | |
| CN111880902A (en) | Pod creation method, device, equipment and readable storage medium | |
| CN113900773B (en) | Super-fusion scheduling method based on domestic platform virtual machine and container | |
| CN109587286A (en) | A kind of equipment connection control method and device | |
| CN108345490B (en) | Method and system for deploying virtual machine in NFV | |
| WO2017185992A1 (en) | Method and apparatus for transmitting request message | |
| CN109525413B (en) | CDN network function virtualization management method, device and system | |
| CN109992373A (en) | Resource regulating method, approaches to IM and device and task deployment system | |
| CN114615268B (en) | Service network, monitoring node, container node and equipment based on Kubernetes cluster | |
| CN112822062A (en) | Management method for desktop cloud service platform | |
| CN112398668B (en) | IaaS cluster-based cloud platform and node switching method |
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 |