CN114567648A - Distributed cloud system - Google Patents
Distributed cloud system Download PDFInfo
- Publication number
- CN114567648A CN114567648A CN202210303789.2A CN202210303789A CN114567648A CN 114567648 A CN114567648 A CN 114567648A CN 202210303789 A CN202210303789 A CN 202210303789A CN 114567648 A CN114567648 A CN 114567648A
- Authority
- CN
- China
- Prior art keywords
- cloud
- edge
- component
- components
- edge cloud
- 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
- 230000005540 biological transmission Effects 0.000 claims description 29
- 230000001419 dependent effect Effects 0.000 claims description 20
- 238000000034 method Methods 0.000 abstract description 8
- 238000007726 management method Methods 0.000 description 68
- 238000005516 engineering process Methods 0.000 description 8
- 238000009434 installation Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000004083 survival effect Effects 0.000 description 1
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/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5019—Ensuring fulfilment of SLA
-
- 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Abstract
The application provides a distributed cloud system. The distributed cloud system includes: a center cloud and at least one edge cloud; the central cloud is connected with the edge cloud, and the edge cloud is used for providing at least one cloud service; the edge cloud is provided with a first type of component and a second type of component, the first type of component provides components used by cloud service for the edge cloud, and the second type of component is part of management and control components used by the edge cloud; and a third type of component is deployed in the central cloud, and the third type of component is a component except the second type of component in the management and control components used by the edge cloud. According to the method and the device, the edge cloud can use the part of the management and control assembly to execute part of management and control capacity, the function of remote management and control of the center cloud on the edge cloud is reduced, and meanwhile, excessive computing resources of the edge cloud cannot be occupied.
Description
Technical Field
The application relates to a cloud computing technology, in particular to a distributed cloud system.
Background
Cloud computing services (also called cloud services) are an Internet Technology (IT) service model supported by cloud computing Technology. Examples of common cloud services include an Electronic Computer Service (ECS) and a Relational Database (RDS).
At present, a scheme for providing cloud services by using a distributed cloud system is proposed to improve a Service-Level agent (SLA) of the cloud services. In the scheme, the distributed cloud system comprises a center cloud and an edge cloud, and cloud services are provided for users through the edge cloud. By the scheme, the efficiency of providing the cloud service can be improved. However, how to manage and control the edge cloud in the distributed cloud system is a problem to be solved.
Disclosure of Invention
The application provides a distributed cloud system to solve the problem of how to manage and control edge clouds.
In a first aspect, the present application provides a distributed cloud system, comprising: a center cloud and at least one edge cloud; the central cloud is connected with the edge cloud, and the edge cloud is used for providing at least one cloud service;
the edge cloud is deployed with a first class of components and a second class of components, the first class of components are components used for providing the cloud service for the edge cloud, and the second class of components are part of management and control components used for managing and controlling the edge cloud;
and a third type of component is deployed in the central cloud, and the third type of component is a component except for the second type of component in a control component used for controlling the edge cloud.
Optionally, the second type of component is a component related to the transmission parameter of the edge cloud in the management and control component.
Optionally, the transmission parameter includes at least one of:
transmission delay, network bandwidth.
Optionally, the second type of component includes at least one of:
a metering and billing component of the cloud service, a component related to high availability of the cloud service.
Optionally, the third type of component includes at least one of:
the system comprises a component for carrying out resource scheduling on the edge cloud, a component for carrying out resource arrangement on the edge cloud, and a component for carrying out unified management and control on cloud services provided by the edge cloud.
Optionally, the first type of component includes:
a component that provides the cloud service, and a component on which the cloud service depends.
Optionally, the component on which the cloud service is provided includes at least one of:
the system runs dependent components and network access dependent components.
Optionally, the cloud service provided by the edge cloud is related to the computing resources of the edge cloud and the service requirements of the edge cloud.
Optionally, the distributed cloud system further includes: an edge cloud management platform;
the edge cloud management platform is connected with the edge cloud and used for providing the first type of components and the second type of components for the edge cloud.
Optionally, the edge cloud management platform is disposed in the center cloud.
According to the distributed cloud system, the components used by the edge cloud for providing the cloud service are used as the first class of components, part of the management and control components used by the edge cloud are used as the second class of components, the first class of components and the second class of components are deployed in the edge cloud, and the components except the second class of components in the management and control components used by the edge cloud are deployed in the center cloud. Through the distributed cloud system, the edge cloud can provide cloud services based on the first type of components, and the richness of the cloud services provided by the distributed cloud is improved. Moreover, through the distributed cloud system, the edge cloud can independently execute the control capacity corresponding to the second type of component, and the remote control function of the central cloud on the edge cloud is reduced. By deploying the third type of component in the central cloud, occupation of edge cloud computing resources is reduced, stability of cloud service provided by the distributed cloud is guaranteed, excessive computing resources of the edge cloud are not occupied, and richness and efficiency of cloud service provided by the edge cloud are improved.
Drawings
In order to more clearly illustrate the technical solutions in the present application or the prior art, the following briefly introduces the drawings needed to be used in the description of the embodiments or the prior art, and obviously, the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive labor.
FIG. 1 is a schematic diagram of a distributed cloud system;
fig. 2 is a schematic architecture diagram of a distributed cloud system provided in the present application;
fig. 3 is a schematic architecture diagram of another distributed cloud system provided in the present application.
With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
To make the objects, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described clearly and completely with reference to the accompanying drawings in the present application, and it is obvious that the described embodiments are some, but not all embodiments of the present application. 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 application.
The following first explains the concept of nouns involved in the present application:
cloud computing (cloud computing): the method is characterized in that huge data computing processing programs are decomposed into innumerable small programs through a network cloud, and then the small programs are processed and analyzed through a system consisting of a plurality of servers to obtain results and the results are returned to a user.
Cloud service: the cloud service is an IT service mode supported by cloud computing technology. Currently, a distributed cloud system is proposed to enable a distributed cloud to provide a cloud service by deploying components corresponding to the cloud service on the distributed cloud.
Edge cloud: the edge cloud is a cloud computing platform constructed on an edge infrastructure based on the core of the cloud computing technology and the capability of edge computing. In some embodiments, the edge cloud may also be referred to as a local cloud, and in this application, the edge cloud and the local cloud are equivalent in concept and are not distinguished.
A central cloud: the central cloud can be connected with each edge cloud, and performs resource scheduling and the like for each edge cloud. The edge cloud, the central cloud and the internet of things terminal can form an end-to-end technical architecture of 'cloud edge end three-body cooperation'.
Illustratively, fig. 1 is a schematic diagram of a distributed cloud system. As shown in fig. 1, a distributed cloud system may include a central cloud, and a plurality of edge clouds. And the central cloud is connected with each edge cloud. Among other things, edge clouds may be used to provide various different types of cloud services. The plurality of edge clouds may provide the same cloud service, may also provide the same cloud service for some edge clouds, may also provide different cloud services for each edge cloud, may also provide a cloud service for the plurality of edge clouds, and may be specifically determined according to actual deployment requirements.
The plurality of edge clouds and the center cloud may belong to the same cloud service provider, or a part of the edge clouds and the center cloud belong to the same cloud service provider, and the rest of the edge clouds and the center cloud belong to different cloud service providers, or the plurality of edge clouds and the center cloud all belong to different cloud service providers.
It should be understood that fig. 1 is only an example of a distributed cloud system including one central cloud, and the number of central clouds of the distributed cloud system is not limited in the present application. In some embodiments, the distributed cloud system may also include multiple central clouds.
In the distributed cloud system, the edge cloud to which each center cloud is connected is different. Taking the example that the distributed cloud system includes a center cloud a, a center cloud B, and edge clouds 1 to 3, in this implementation manner, for example, the center cloud a is connected to the edge cloud 1 and the edge cloud 2, and the center cloud B is connected to the edge cloud 3.
Alternatively, in the distributed cloud system, a portion of the center cloud may connect to one or more of the same edge clouds. Still taking the above example as an example, in this implementation, for example, center cloud a is connected with edge cloud 1 and edge cloud 2, and center cloud B is connected with edge cloud 2 and edge cloud 3. That is, both center cloud a and center cloud B are connected to edge cloud 2. In this implementation manner, the cloud service provided by the connection between the edge cloud 2 and the center cloud a may be the same as or different from the cloud service provided by the connection between the edge cloud 2 and the center cloud B.
As mentioned previously, cloud services may be provided through an edge cloud in the distributed cloud system described above. Therefore, how to manage the edge cloud in the distributed cloud system to ensure the provision of the cloud service is crucial.
However, how to reasonably deploy the management and control component to realize management and control of the edge cloud is a problem to be solved urgently at present.
The edge cloud is usually managed by deploying a management and control component, but there is no standard or protocol agreement on how to deploy the management and control component in the distributed cloud system.
If the management and control component is completely deployed in the center cloud, namely the edge cloud is remotely managed and controlled by the center cloud, the requirements on the center cloud and the edge cloud are high in this deployment mode. For example, the stability of the network link between the central cloud and the edge cloud requires that, for example, once the network link between the central cloud and the edge cloud has network problems such as network jitter or network failure, the central cloud cannot remotely control the edge cloud in time, which easily causes the cloud service provided by the edge cloud to be abnormal, and further causes the SLA that cannot realize the cloud service to be improved.
If the management and control component is completely deployed on the edge cloud, that is, the edge cloud realizes complete management and control by itself. The deployment mode occupies computing resources of the edge cloud, so that the resource requirement on local cloud nodes is high. Especially for those edge clouds with limited size and less computing resources, the deployment method is liable to cause the computing resources of the edge clouds for providing cloud services to be less, which may further cause the efficiency of the edge clouds for providing cloud services to be reduced, and the types of providing cloud services to be reduced. In addition, the management and control efficiency is low due to the respective management and control modes of the edge clouds.
Therefore, in consideration of the above factors, the present application provides a distributed cloud system that deploys part of the management and control components on the edge cloud and part of the management and control components on the center cloud. That is, the management and control component is deployed on the center cloud and the edge cloud in a distributed manner, and is not limited to being deployed on one side (for example, all the management and control components are deployed on the center cloud, or all the management and control components are deployed on the edge cloud), so that the edge cloud can use the part of the management and control components to execute part of management and control capability, the function of remote management and control of the center cloud on the edge cloud is reduced, too much computing resources of the edge cloud are not occupied, and the management and control efficiency of the edge cloud is improved. The deployment mode is suitable for any distributed cloud system, and is particularly suitable for the distributed cloud system with less computing resources of the edge cloud.
The distributed cloud system provided by the present application is described in detail below with reference to specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.
Fig. 2 is a schematic diagram of an architecture of a distributed cloud system provided in the present application. As shown in fig. 2, the distributed cloud system may include: a center cloud and at least one edge cloud. It should be understood that fig. 2 is an exemplary illustration of a distributed cloud system provided herein, taking a central cloud corresponding to 3 edge clouds as an example.
Wherein the center cloud is connected with the edge cloud. It should be understood that the present application is not limited to the connection between the center clouds and the edge clouds. For example, the central cloud and the edge cloud may be connected by a wireless network, a wired network, or a fifth Generation Mobile Communication Technology (5th Generation Mobile Communication Technology, 5G). In addition, the number of nodes deployed by the central cloud, the physical forms of the nodes, and the physical forms of the number of nodes deployed by the edge cloud are not limited.
For any edge cloud, the edge cloud can be used to provide at least one cloud service. Whether the central cloud provides the cloud service is not limited.
Regarding the introduction between the edge cloud and the cloud service, reference may be made to the description in the corresponding embodiment of fig. 1. It should be understood that the present application does not limit the type of cloud services provided by the edge cloud. Taking a cloud Service as an example, the cloud Service may be, for example, an elastic computing cloud Service (e.g., a cloud server, etc.), a database cloud Service (a cloud database, a time sequence database, a graph database, etc.), a big data computing cloud Service (an open source big data platform, a retrieval and analysis Service, etc.), an internet of things cloud Service (e.g., internet of things application development, internet of things device management, etc.), a log Service, a Storage cloud Service, such as any one of block Storage, Object Storage Service (OSS), file Storage, data migration, etc.
Thus, in this embodiment, an edge cloud may be deployed with: a first type of component, and a second type of component.
The first class of components provides components used by the edge cloud to provide cloud services. Optionally, the first type of components used by the edge cloud to provide different cloud services may not be repeated. Alternatively, the first type of component used by the edge cloud to provide different cloud services may also exist the same. In addition, the number of the first-type components corresponding to each cloud service is not limited in the present application.
The second type of component is a portion of the governing components used by the governing edge cloud. The second type of component is deployed in the edge cloud, so that the edge cloud has the management and control capability corresponding to the second type of component, management and control of the center cloud on the edge cloud are reduced, the possibility that the management and control efficiency is low due to network problems and the like between the center cloud and the edge cloud is avoided, and the efficiency of managing and controlling the edge cloud is improved. Illustratively, the second type of component may include, for example, a component having a higher requirement on transmission parameters such as transmission delay.
The central cloud may be deployed with a third class of components. The third type of component is a component except the second type of component in a management and control component used for managing and controlling the edge cloud. Compared with the corresponding computing resources of the edge cloud in the distributed cloud system, the computing resources of the center cloud are usually larger, that is, the original service of the center cloud is not affected when the center cloud deploys the third type of component.
The third type of components are deployed in the center cloud, so that the occupation of edge cloud computing resources is reduced, the efficiency of providing cloud services by the edge cloud is improved, more computing resources can be used for providing the cloud services by the edge cloud, and the richness of the cloud services provided by the edge cloud is further improved.
It should be understood that the present application is not limited to the above edge cloud, and whether other components are deployed in the center cloud. For example, the edge cloud may also be deployed with components for configuring the edge cloud, and the central cloud may also be deployed with components for configuring the central cloud. In addition, it should be understood that the present application is not limited to how the first type of component, the second type of component, and the third type of component are determined, how the first type of component and the second type of component are deployed in the edge cloud, and how the third type of component is deployed in the center cloud.
In this embodiment, a component used by an edge cloud to provide cloud services is used as a first class component, a part of management components used by the edge cloud is used as a second class component, the first class component and the second class component are deployed in the edge cloud, and components except the second class component in the management components used by the edge cloud are deployed in the central cloud. Through the distributed cloud system, the edge cloud can provide cloud services based on the first type of components, and the richness of the cloud services provided by the distributed cloud is improved. Moreover, through the distributed cloud system, the edge cloud can independently execute the control capacity corresponding to the second type of component, and the remote control function of the central cloud on the edge cloud is reduced. Through deploying the third type of components in the center cloud, occupation of edge cloud computing resources is reduced, the stability of cloud service provided by the distributed cloud is guaranteed, meanwhile, excessive computing resources of the edge cloud cannot be occupied, and the richness and the efficiency of the cloud service provided by the edge cloud are improved.
The following respectively describes the first type of component, the second type of component, and the third type of component in detail:
the first type of component:
before introducing the first type of component, the types of cloud services provided by the edge cloud in the distributed cloud system are described. As a possible implementation, the cloud services provided by the edge cloud may be related to, for example, the computing resources of the edge cloud, as well as the service requirements of the edge cloud.
In some embodiments, for each edge cloud, at least one cloud service with deployment requirements corresponding to the edge cloud may be determined first. Then, under the deployment requirement, determining the cloud service provided by the edge cloud according to the computing resources occupied by the cloud services with the deployment requirement and the computing resources of the edge cloud. Alternatively, for each edge cloud, at least one cloud service that can be provided by the edge cloud may be determined according to the computing resources of the edge cloud. Then, a cloud service with the largest service demand (or larger than a preset demand) of the edge cloud in the at least one cloud service may be used as the cloud service provided by the edge cloud.
For example, taking cloud service 1, cloud service 2, and cloud service 3 as examples, table 1 shows the computing resources respectively occupied by the 3 cloud services, and an example of the service requirements of the edge cloud:
TABLE 1
| Cloud service | Occupied computing resources | Service requirements of edge clouds |
| Cloud service 1 | 1 | 2 |
| Cloud service 2 | 2 | 3 |
| Cloud service 3 | 3 | 1 |
For example, assuming that the maximum computing resource available for the edge cloud is less than 3, taking the contents shown in table 1 as an example, the cloud services that the edge cloud can deploy are cloud service 1 and cloud service 2. If the service requirement of the cloud service 2 is greater than that of the cloud service 1, it may be determined that the cloud service provided by the edge cloud is the cloud service 1.
It should be understood that the present application does not limit how to determine the cloud service corresponding to each edge cloud in the distributed cloud system. For example, a user may determine a cloud service corresponding to each edge cloud by analyzing the computing resources of the edge cloud and the service requirements of the edge cloud. Or, the cloud service provided by the edge cloud may also be determined according to the computing resources of the edge cloud and the service requirement of the edge cloud through the edge cloud management platform, and the like, which is not described herein again.
The following describes the first type of components in detail based on the required cloud service:
as a possible implementation, the first type of component may include: components that provide cloud services, and components that the provision of cloud services relies upon.
For example, the above components for providing cloud services may include: the cloud service installation package comprises an installation package component corresponding to the cloud service, an installation package component corresponding to the cloud service installed to a component of the edge cloud, and the like.
Illustratively, the components on which the cloud service provision depends include at least one of: components on which the system runs, components on which network access depends, and the like.
In some embodiments, using the system operation dependent component, the edge cloud may operate a program code corresponding to the cloud service to implement the function of the cloud service.
Illustratively, the system operation dependent component may include, for example, at least one of: storage class components, components that can use storage class cloud services for data storage, virtualization hosts, load balancing nodes, management and control class components (e.g., local physical device management and monitoring components), and the like. The Storage cloud service may be, for example, an Elastic Block Storage (EBS) cloud service.
The network access dependent component may be, for example, a component that enables an edge cloud to have communication capabilities. The communication referred to herein may include one or more of communication between an edge cloud and an edge cloud, communication between an edge cloud and a center cloud, communication between nodes constituting an edge cloud, communication between an edge cloud and a terminal device located on a user side (i.e., a terminal device using the cloud service), and the like.
Illustratively, the component for enabling the edge cloud to have the communication capability may comprise at least one of the following components: a component supporting internal network capability of a Private network (VPC), a component supporting external network capability of an Elastic public network IP (EIP), and the like.
Optionally, as mentioned above, the edge cloud may provide at least one cloud service. Taking an example that one edge cloud provides multiple cloud services, if there are the same components in the corresponding first type of components between different cloud services, optionally, only one of the same components may be deployed on the edge cloud. In this implementation, the edge cloud may share one component when providing the different cloud services described above. By the method, the number of the components deployed on the edge cloud is further reduced, and further the computing capacity of the edge cloud for providing cloud services is improved. Alternatively, the first type components corresponding to different cloud services provided by an edge cloud may be independent of each other. Under the implementation, an independent first-class component is deployed on the edge cloud for each cloud service.
Taking an example of providing cloud services 1, 2, and 3 by an edge cloud, assume that a first type of component corresponding to each cloud service is shown in table 2 below:
TABLE 2
For example, as shown in table 2, the component B in the first type of component corresponding to the cloud service 1 is the same as the component B in the first type of component corresponding to the cloud service 2. Optionally, one component B may be deployed on the edge cloud, and the edge cloud may provide cloud service 1 and cloud service 2 based on the one component B and other components shown in table 1. Alternatively, two components B may be deployed on the edge cloud, where one component B is used to provide the cloud service 1 and the other component B is used to provide the cloud service 2.
In this embodiment, the components providing the cloud service and the components depending on providing the cloud service are deployed in the edge cloud as the first type of components, so that the edge cloud in the distributed cloud system can provide the cloud service based on the components providing the cloud service and the components depending on providing the cloud service, thereby ensuring that the edge cloud can provide the cloud service.
The second type of component described above is described in detail below:
as a possible implementation manner, the second type component may be a component in the management and control component related to the transmission parameter between the edge cloud and the center cloud.
Optionally, the transmission parameter may include at least one of the following: transmission delay, network bandwidth, network transmission rate, delay-bandwidth product, etc.
Illustratively, taking the above transmission parameters including transmission delay and network bandwidth as an example, the second component may include at least one of the following components: the network link transmission control device comprises a control component requiring transmission delay to be smaller than preset transmission delay, a control component requiring network bandwidth to be larger than preset network bandwidth, a control component requiring transmission delay to be smaller than preset transmission delay and requiring network bandwidth to be larger than preset network bandwidth, a control component requiring transmission delay to be not matched with transmission delay which can be met by a current network link, a control component requiring network bandwidth to be not matched with network bandwidth which can be met by the current network link and the like.
Illustratively, the second type of component may include, for example, at least one of: a metered billing component of the cloud service, a component related to High Availability (HA) of the cloud service, and the like.
The metering and charging component of the cloud service is deployed in the edge cloud, so that the edge cloud can timely perform metering and charging on the user using the cloud service provided by the edge cloud, the accuracy of the metering and charging is improved, and the user experience is further improved. In some embodiments, the role of the above-described components related to high availability of cloud services may include, for example, at least one of: the method comprises the steps of monitoring and eliminating faults, backing up and protecting data, reporting the operation condition of the edge cloud at any time or at regular time, sending a report and an alarm when the cloud service provided by the edge cloud is abnormal, and the like. By deploying the components related to high availability of the cloud service on the edge cloud, the edge cloud has the management and control function corresponding to the management and control components, even if a network problem exists between the center cloud and the local cloud, the edge cloud can timely perform fault detection, timely perform data backup and the like, and the possibility of abnormity of the provided cloud service is reduced.
Under the implementation mode, the second type of components related to the transmission parameters of the edge cloud are deployed on the edge cloud, so that the edge cloud can have the control capacity corresponding to the second type of components, compared with the existing method of performing remote control on the edge cloud through the center cloud, the method reduces the possibility that network problems cause incapability of performing control on the edge cloud, further improves the control efficiency on the edge cloud, reduces the possibility that the edge cloud provides abnormal cloud service, and further improves the stability of providing the cloud service by the edge cloud.
In some embodiments, the second type of component may be deployed in an edge cloud or a central cloud. When the transmission parameters between the central cloud and the edge cloud meet the requirements of the second type of component, the second type of component can be deployed in the central cloud to reduce the occupation of the computing resources of the edge cloud.
Further, as another possible implementation manner, the transmission parameters may further include: and (4) network transmission fault tolerance rate. In this implementation, the second type of component may include, for example, a policing component that is less tolerant to network transmissions. By using the control component with smaller network transmission fault tolerance as the second type of component to be deployed in the edge cloud, the possibility that the interference of network transmission signals between the center cloud and the edge cloud causes problems in the control of the edge cloud is reduced, and the accuracy of the control of the edge cloud is improved.
As another possible implementation manner, the second type of component may further include: and the management and control component has higher requirement on cloud encryption of the management and control edge. The management and control component with higher requirement on the encryption of the pair of management and control edge clouds is deployed in the edge clouds as the second type of component, so that the edge clouds can execute the management and control capacity corresponding to the management and control component, and the management and control can be performed through a platform except the edge clouds, the interaction of the management and control component executed by the edge clouds and other platforms is reduced, and the security of the management and control of the edge clouds is improved.
The third type of component is described in detail below:
as a possible implementation, the third component may include at least one of the following: the system comprises a component for carrying out resource scheduling on the edge cloud, a component for carrying out resource arrangement on the edge cloud, a component for carrying out unified management and control on cloud services provided by the edge cloud and the like. The third type of components often occupy more computing resources, and can be deployed in the central cloud due to more computing resources of the central cloud.
The central cloud uses a component for resource scheduling of the edge cloud and a component for resource arrangement of the edge cloud, can judge the current computing resource states of each edge cloud and the central cloud, and reasonably distributes working resources according to the current computing resource states, so that the edge cloud can respond to the service request corresponding to the cloud service. The central cloud is used for uniformly managing and controlling the cloud service provided by the edge cloud and is deployed in the central cloud, and the edge clouds connected with the central cloud can be uniformly managed and controlled, so that the operation efficiency of the distributed cloud system is improved, and the stability of the cloud service provided by the distributed cloud system is improved.
For example, the above components for uniformly managing cloud services provided by an edge cloud may include at least one of the following components: the system comprises a component for carrying out authority management on users using cloud services, a component for providing periodic report statistics on various data during distributed cloud operation, a management portal component and the like. Among other things, the management portlet can be used to provide a user with a portal to configure various items of the distributed cloud system.
Fig. 3 is a schematic architecture diagram of another distributed cloud system provided in the present application. As shown in fig. 3, as a possible implementation manner, the distributed cloud system may further include: an edge cloud management platform. Wherein, the edge cloud management platform can be connected with the edge cloud. In this implementation, the edge cloud management platform may be configured to provide the first class of components and the second class of components to the edge cloud.
Optionally, the edge cloud management platform may be disposed in a central cloud to improve the concentration of the distributed cloud system, and improve the convenience of the edge cloud management platform in interacting with the edge cloud. Alternatively, the edge cloud management platform may be independent of the central cloud. Still alternatively, the edge cloud management platform may also be disposed in an edge cloud.
It should be understood that the present application is not limited to how the edge cloud management platform provides the first type of component and the second type of component. In addition, the application does not limit whether the edge cloud management platform directly deploys the first type of components and the second type of components in the edge cloud, and how the edge cloud management platform deploys the first type of components and the second type of components in the edge cloud.
In this embodiment, the first type of component and the second type of component are provided for the edge cloud through the edge cloud management platform, so that the automatic component deployment of the edge cloud is realized, the efficiency of determining the first type of component and the second type of component is improved, and the efficiency of providing the cloud service by the edge cloud is further improved.
It should be understood that the distributed cloud system provided by the application can be applicable to edge clouds of any scale, especially edge clouds of a smaller scale, and can reduce the function of remote control of the edge clouds by a central cloud, and meanwhile, the distributed cloud system does not occupy too many computing resources of the edge clouds, and guarantees that enough computing resources of the edge clouds can be used for providing cloud services. The distributed cloud system provided by the present application is exemplarily illustrated below with an edge cloud 1 as an edge cloud with smaller computing resources and an edge cloud 2 as an edge cloud with larger computing resources as an example:
for edge cloud 1:
the edge cloud 1 may provide a cloud service that occupies less computing resources, or provide a smaller variety of cloud services. Such as a cloud Server (ECS), Load balancing (SLB), etc.
At this time, the first type of components deployed on the edge cloud 1 may include, for example: the ECS installation package component, the component dependent on system operation corresponding to the ECS, the component dependent on network access corresponding to the ECS, the SLB installation package component, the component dependent on system operation corresponding to the SLB, the component dependent on network access corresponding to the SLB and the like.
For example, the system operation dependent component corresponding to the ECS may include, for example, a storage class component, or may use a storage class cloud service for data storage. For example, the storage-class cloud service can store cloud service operation data to a system disk of a distributed cloud and a flexibly mounted data cloud. In addition, the storage cloud service may also store metadata corresponding to local management, partition consistency correspondence management data, and the like.
Taking the network access dependent component corresponding to the ECS as an example, the network access dependent component corresponding to the ECS may include: a component supporting VPC intranet capability, a component supporting EIP extranet capability and the like. The component supporting the VPC intranet capability provides routing distribution on the overlay (a virtualization technology mode superimposed on a network architecture) level to a Virtual Gateway (VGW). The components supporting the EIP extranet capability provide the route distribution of the Internet Gateway (IGW) in the north-south direction to the virtual Gateway at the overlay level.
The second type of components deployed on the edge cloud 1 may include, for example: and managing and controlling components related to the transmission delay and the network bandwidth of the edge cloud. Optionally, the second type of component may provide a management and control capability required when the edge cloud provides the ECS service. Illustratively, the second type of component may include, for example: a metering and charging component of the cloud service, a local HA survival detection component and the like.
And the central cloud is provided with components except the second type of components in the management and control components used by the edge cloud.
For edge cloud 2:
the edge cloud 2 may provide cloud services that consume more computing resources, or may provide more kinds of cloud services, for example, the edge cloud 2 may provide ECS, SLB, and Relational Database Service (RDS).
At this time, the first type of components deployed on the edge cloud 2 may include, for example: the system comprises an ECS installation package component, a system operation dependent component corresponding to the ECS, a network access dependent component corresponding to the ECS, an SLB installation package component, a system operation dependent component corresponding to the SLB, a network access dependent component corresponding to the SLB, an RDS installation package component, a system operation dependent component corresponding to the RDS, a network access dependent component corresponding to the RDS and the like.
For the above-mentioned SLB cloud service, in some embodiments, the edge cloud 2 providing the SLB cloud service may be deployed based on multiple X86 servers, and based on these servers, the edge cloud 2 may provide a load balancing service to the outside. Load Balance Switch (LSW) can be used as a unified access network hardware device for these servers, and has high hardware performance and high availability. In some embodiments, there are typically multiple cloud services that all rely on the LSW. Therefore, if the computing resources occupied by the SLB are small, the edge cloud 2 can provide the SLB cloud service using the existing LSW. If the computing resources occupied by the SLB are large, the physical machine of the edge cloud 2 may be expanded.
The second type of components deployed on the edge cloud 2 may include, for example, the aforementioned second type of components deployed on the edge cloud 1, and the HA components corresponding to RDS, etc.
And the central cloud is provided with components except the second type of components in the management and control components used by the edge cloud.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and these modifications or substitutions do not depart from the scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A distributed cloud system, comprising: a center cloud and at least one edge cloud; the central cloud is connected with the edge cloud, and the edge cloud is used for providing at least one cloud service;
the edge cloud is deployed with a first class of components and a second class of components, the first class of components are components used for providing the cloud service for the edge cloud, and the second class of components are part of management and control components used for managing and controlling the edge cloud;
and the central cloud is deployed with a third type of component, and the third type of component is a component except the second type of component in a control component used for controlling the edge cloud.
2. The distributed cloud system of claim 1, wherein said second class of components are ones of governing components related to transmission parameters between said edge cloud and said center cloud.
3. The distributed cloud system of claim 2, wherein said transmission parameters include at least one of:
transmission delay, network bandwidth.
4. The distributed cloud system of claim 3, wherein said second class of components comprises at least one of:
a metering and billing component of the cloud service, a component related to high availability of the cloud service.
5. The distributed cloud system of any of claims 2-4, wherein said third class of components comprises at least one of:
the system comprises a component for carrying out resource scheduling on the edge cloud, a component for carrying out resource arrangement on the edge cloud, and a component for carrying out unified management and control on cloud services provided by the edge cloud.
6. The distributed cloud system of any of claims 1-4, wherein said first class of components comprises:
a component that provides the cloud service, and a component on which the cloud service depends.
7. The distributed cloud system of claim 6, wherein said components on which said cloud service is provided comprise at least one of:
the system runs dependent components and network access dependent components.
8. The distributed cloud system of any of claims 1-4, wherein cloud services provided by said edge cloud are related to computing resources of said edge cloud and service requirements of said edge cloud.
9. The distributed cloud system of any of claims 1-4, wherein said distributed cloud system further comprises: an edge cloud management platform;
the edge cloud management platform is connected with the edge cloud and used for providing the first type of components and the second type of components for the edge cloud.
10. The distributed cloud system of claim 9, wherein said edge cloud management platform is disposed in said central cloud.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210303789.2A CN114567648A (en) | 2022-03-24 | 2022-03-24 | Distributed cloud system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210303789.2A CN114567648A (en) | 2022-03-24 | 2022-03-24 | Distributed cloud system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114567648A true CN114567648A (en) | 2022-05-31 |
Family
ID=81720531
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210303789.2A Pending CN114567648A (en) | 2022-03-24 | 2022-03-24 | Distributed cloud system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114567648A (en) |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20180118393A (en) * | 2017-04-21 | 2018-10-31 | 에스케이텔레콤 주식회사 | Distributed cloud computing system, apparatus and control method thereof using the system |
| US20190087231A1 (en) * | 2017-09-19 | 2019-03-21 | University-Industry Cooperation Group Of Kyung-Hee University | System of cloud computing and method for detaching load in cloud computing system |
| CN110572448A (en) * | 2019-08-30 | 2019-12-13 | 烽火通信科技股份有限公司 | distributed edge cloud system architecture |
| CN110851145A (en) * | 2019-09-30 | 2020-02-28 | 烽火通信科技股份有限公司 | Edge cloud installation and maintenance method and system based on container arrangement |
| CN111800283A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Network system, service providing and resource scheduling method, device and storage medium |
| CN111800281A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Network system, management and control method, device and storage medium |
| CN112003924A (en) * | 2020-08-20 | 2020-11-27 | 浪潮云信息技术股份公司 | Industrial internet-oriented edge cloud platform building method and system |
| CN112272234A (en) * | 2020-10-23 | 2021-01-26 | 杭州卷积云科技有限公司 | Platform management system and method for realizing edge cloud collaborative intelligent service |
| WO2021056949A1 (en) * | 2019-09-24 | 2021-04-01 | 厦门网宿有限公司 | Edge application management method and system |
| CN113242319A (en) * | 2021-07-09 | 2021-08-10 | 军事科学院系统工程研究院网络信息研究所 | Cloud edge cooperative work method and system based on video cloud service architecture |
| CN113300866A (en) * | 2020-06-16 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Node capacity control method, device, system and storage medium |
| CN113515316A (en) * | 2021-07-29 | 2021-10-19 | 广州高维网络科技有限公司 | Novel edge cloud operating system |
| CN113722077A (en) * | 2021-11-02 | 2021-11-30 | 腾讯科技（深圳）有限公司 | Data processing method, system, related device, storage medium and product |
| CN113726843A (en) * | 2021-07-13 | 2021-11-30 | 阿里巴巴新加坡控股有限公司 | Edge cloud system, data transmission method, device and storage medium |
-
2022
- 2022-03-24 CN CN202210303789.2A patent/CN114567648A/en active Pending
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20180118393A (en) * | 2017-04-21 | 2018-10-31 | 에스케이텔레콤 주식회사 | Distributed cloud computing system, apparatus and control method thereof using the system |
| US20190087231A1 (en) * | 2017-09-19 | 2019-03-21 | University-Industry Cooperation Group Of Kyung-Hee University | System of cloud computing and method for detaching load in cloud computing system |
| CN111800283A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Network system, service providing and resource scheduling method, device and storage medium |
| CN111800281A (en) * | 2019-04-08 | 2020-10-20 | 阿里巴巴集团控股有限公司 | Network system, management and control method, device and storage medium |
| CN110572448A (en) * | 2019-08-30 | 2019-12-13 | 烽火通信科技股份有限公司 | distributed edge cloud system architecture |
| WO2021056949A1 (en) * | 2019-09-24 | 2021-04-01 | 厦门网宿有限公司 | Edge application management method and system |
| CN110851145A (en) * | 2019-09-30 | 2020-02-28 | 烽火通信科技股份有限公司 | Edge cloud installation and maintenance method and system based on container arrangement |
| CN113300866A (en) * | 2020-06-16 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Node capacity control method, device, system and storage medium |
| CN112003924A (en) * | 2020-08-20 | 2020-11-27 | 浪潮云信息技术股份公司 | Industrial internet-oriented edge cloud platform building method and system |
| CN112272234A (en) * | 2020-10-23 | 2021-01-26 | 杭州卷积云科技有限公司 | Platform management system and method for realizing edge cloud collaborative intelligent service |
| CN113242319A (en) * | 2021-07-09 | 2021-08-10 | 军事科学院系统工程研究院网络信息研究所 | Cloud edge cooperative work method and system based on video cloud service architecture |
| CN113726843A (en) * | 2021-07-13 | 2021-11-30 | 阿里巴巴新加坡控股有限公司 | Edge cloud system, data transmission method, device and storage medium |
| CN113515316A (en) * | 2021-07-29 | 2021-10-19 | 广州高维网络科技有限公司 | Novel edge cloud operating system |
| CN113722077A (en) * | 2021-11-02 | 2021-11-30 | 腾讯科技（深圳）有限公司 | Data processing method, system, related device, storage medium and product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3526933B1 (en) | Method and system for monitoring performance of slices | |
| US8099488B2 (en) | Real-time monitoring of service agreements | |
| US7099879B2 (en) | Real-time monitoring of service performance through the use of relational database calculation clusters | |
| Ward et al. | Observing the clouds: a survey and taxonomy of cloud monitoring | |
| EP3072260B1 (en) | Methods, systems, and computer readable media for a network function virtualization information concentrator | |
| US20030120764A1 (en) | Real-time monitoring of services through aggregation view | |
| CN108370341B (en) | Resource allocation method, virtual network function manager and network element management system | |
| EP1361761A1 (en) | Telecommunications network management system and method for service monitoring | |
| US20050160318A1 (en) | Managing analysis of a degraded service in a grid environment | |
| US20140201642A1 (en) | User interface for visualizing resource performance and managing resources in cloud or distributed systems | |
| Trihinas et al. | Monitoring elastically adaptive multi-cloud services | |
| CN109873714B (en) | Cloud computing node configuration updating method and terminal equipment | |
| CN111258971A (en) | Application state monitoring alarm system and method based on access log | |
| CN108390907B (en) | Management monitoring system and method based on Hadoop cluster | |
| De Franceschi et al. | Performance evaluation for proactive network management | |
| US11595471B1 (en) | Method and system for electing a master in a cloud based distributed system using a serverless framework | |
| CN110932902A (en) | Cross-domain switching resource dynamic allocation method | |
| CN114567648A (en) | Distributed cloud system | |
| CN115499432A (en) | Family terminal computing resource management system and computing resource scheduling method | |
| CN114338670A (en) | Edge cloud platform and three-level cloud control platform for internet traffic with same | |
| CN113271335A (en) | System for managing and controlling operation of cloud computing terminal and cloud server | |
| Hage Hassan et al. | Virtualization for performance guarantees of state estimation in cyber-physical energy systems | |
| Srivastava et al. | Architectural support for mode-driven fault tolerance in distributed applications | |
| EP4161016A1 (en) | Storing configuration data changes to perform root cause analysis for errors in a network of managed network devices | |
| CN112398707B (en) | Distributed automatic test management method, device, equipment and storage medium |
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 |