CN114826900B - Service deployment processing method and device for distributed cloud architecture - Google Patents
Service deployment processing method and device for distributed cloud architecture Download PDFInfo
- Publication number
- CN114826900B CN114826900B CN202210429489.9A CN202210429489A CN114826900B CN 114826900 B CN114826900 B CN 114826900B CN 202210429489 A CN202210429489 A CN 202210429489A CN 114826900 B CN114826900 B CN 114826900B
- Authority
- CN
- China
- Prior art keywords
- components
- cloud
- network
- bandwidth
- component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 17
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000004590 computer program Methods 0.000 claims description 10
- 230000004044 response Effects 0.000 claims description 10
- 238000004364 calculation method Methods 0.000 claims description 4
- 239000000523 sample Substances 0.000 description 28
- 230000000694 effects Effects 0.000 description 16
- 230000035945 sensitivity Effects 0.000 description 13
- 238000001514 detection method Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000001419 dependent effect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000010187 selection method Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
- H04L43/0894—Packet rate
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the specification provides a service deployment processing method and device for a distributed cloud architecture. The distributed cloud architecture includes a central cloud and a plurality of local cloud nodes, the method comprising: acquiring network condition information from a central cloud to a current local cloud node, wherein the current local cloud node is one of the plurality of local cloud nodes, cloud services required to be provided by the current local cloud node are associated with a plurality of second type components to be deployed, and the plurality of second type components respectively have network capability requirements; for any second type component in the plurality of second type components, determining whether the network condition information meets the network capability requirement of the any second type component, and obtaining a determination result corresponding to the any second type component; and if the determination result is negative, determining the current local cloud node as the deployment position of the arbitrary second class component.
Description
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a service deployment processing method and device aiming at a distributed cloud architecture.
Background
Existing cloud computing scenarios typically involve a central cloud and local cloud nodes. Currently, a deployment scheme related to cloud services generally includes that all components associated with cloud services to be provided by a local cloud node are deployed on the local cloud node, so that the local cloud node has complete management and control capability; or, all components associated with the cloud service required to be provided by the local cloud node are deployed to the central cloud, so that the central cloud is used for carrying out all management and control on the local cloud node. In the two existing deployment schemes, the former has higher resource requirements and lower efficiency on the local cloud nodes, the latter has higher stability requirements on network links between the local cloud nodes and the central cloud, and once the network fails, cloud services deployed by the local cloud nodes cannot work.
Therefore, a reasonable and reliable scheme is urgently needed, and reasonable deployment of cloud service related components required to be provided by the local cloud nodes can be achieved.
Disclosure of Invention
The embodiment of the specification provides a service deployment processing method and device for a distributed cloud architecture, which can realize reasonable deployment of cloud service associated components required to be provided by a local cloud node.
In a first aspect, an embodiment of the present disclosure provides a service deployment processing method for a distributed cloud architecture, where the distributed cloud architecture includes a central cloud and a plurality of local cloud nodes, the method including: acquiring network condition information from the central cloud to a current local cloud node, wherein the current local cloud node is one of the plurality of local cloud nodes, cloud services required to be provided by the current local cloud node are associated with a plurality of second type components to be deployed, and each of the plurality of second type components has network capability requirements; for any second type component in the plurality of second type components, determining whether the network condition information meets the network capability requirement of the any second type component, and obtaining a determination result corresponding to the any second type component; and if the determination result is negative, determining the current local cloud node as the deployment position of the arbitrary second class component.
In some embodiments, the method further comprises: and if the determination result is yes, determining the central cloud as the deployment position of the arbitrary second class component.
In some embodiments, the network capability requirement comprises a bandwidth requirement, and the network condition information comprises a current network bandwidth; and/or the network capability requirement comprises a latency requirement, the network condition information comprising a current network latency.
In some embodiments, when the network capability requirements include bandwidth requirements and latency requirements, the network condition information includes the current network bandwidth and the current network time delay, the determining whether the network condition information meets the network capability requirements of the arbitrary second class component includes: and determining whether the current network bandwidth and the current network time delay meet the bandwidth requirement and the time delay requirement of any second class component at the same time.
In some embodiments, the network capability requirements include bandwidth requirements, the central cloud being configured with a total bandwidth requirement for the current local cloud node relating to the second class of components; the method further comprises: and aiming at the components with the corresponding determined results in the second class of components, determining the respective deployment positions of the components in the central cloud and the current local cloud node according to the total bandwidth requirement and the respective bandwidth requirement of the components.
In some embodiments, the bandwidth requirements of the second class of components include a bandwidth lower bound; and determining, in the central cloud and the current local cloud node, a deployment location of each of the plurality of components according to the total bandwidth requirement and the bandwidth requirement of each of the plurality of components, including: calculating the sum of the bandwidth lower limits of the components; determining whether the sum meets the total bandwidth requirement; in response to determining that the sum meets the total bandwidth requirement, the central cloud is determined as a deployment location for each of the number of components.
In some embodiments, the determining, in the central cloud and the current local cloud node, the deployment location of each of the plurality of components according to the total bandwidth requirement and the bandwidth requirement of each of the plurality of components further comprises: in response to determining that the sum does not meet the total bandwidth requirement, selecting one component from the number of components and determining the current local cloud node as a deployment location for the component; updating the rest of the components to a plurality of components, and continuing to execute the calculation of the sum of the respective lower bandwidths of the components.
In some embodiments, the selecting one component from the plurality of components comprises: and selecting one component from the components according to the order of the lower bandwidth limit from large to small.
In some embodiments, the cloud service further associates a number of first-type components to be deployed, the number of first-type components being components on which the cloud service locally needs to rely; the method further comprises: before the network condition information from the central cloud to the current local cloud node is acquired, the method further comprises: and determining the current local cloud node as the deployment position of the first type of components.
In some embodiments, after determining the current local cloud node as the deployment location of the number of first-type components when the cloud service has not been deployed to the current local cloud node, further comprising: and deploying the cloud service and the first type components to the current local cloud node.
In some embodiments, the cloud service further associates a number of third class components to be deployed, the number of third class components being components that enable remote management and control; the method further comprises: and determining the central cloud as the deployment position of each of the third class of components.
In a second aspect, embodiments of the present disclosure provide a service deployment processing apparatus for a distributed cloud architecture, the distributed cloud architecture including a central cloud and a plurality of local cloud nodes, the apparatus comprising: the system comprises an acquisition unit, a network management unit and a network management unit, wherein the acquisition unit is configured to acquire network condition information from the central cloud to a current local cloud node, the current local cloud node is one of a plurality of local cloud nodes, cloud services required to be provided by the current local cloud node are associated with a plurality of second-class components to be deployed, and each of the plurality of second-class components has network capability requirements; the first determining unit is configured to determine whether the network condition information meets the network capability requirement of any second type component in the plurality of second type components, and obtain a determination result corresponding to the any second type component; and the second determining unit is configured to determine the current local cloud node as the deployment position of the arbitrary second class component if the determination result is negative.
In a third aspect, embodiments of the present specification provide a computer-readable storage medium having stored thereon a computer program, wherein the computer program, when executed in a computer, causes the computer to perform a method as described in any of the implementations of the first aspect.
In a fourth aspect, embodiments of the present specification provide a computing device comprising a memory and a processor, wherein the memory has executable code stored therein, and wherein the processor, when executing the executable code, implements a method as described in any of the implementations of the first aspect.
In a fifth aspect, embodiments of the present specification provide a computer program, wherein the computer program, when executed in a computer, causes the computer to perform a method as described in any of the implementations of the first aspect.
The solution provided by the above embodiments of the present specification relates to a distributed cloud architecture including a central cloud and a plurality of local cloud nodes. In the scheme, network condition information from the central cloud to the current local cloud node can be acquired, wherein the current local cloud node is one of the plurality of local cloud nodes, cloud services required to be provided by the current local cloud node are associated with a plurality of second type components to be deployed, and each of the plurality of second type components has network capability requirements. And then, for any second type component in the plurality of second type components, determining whether the network condition information meets the network capability requirement of the any second type component, and obtaining a determination result corresponding to the any second type component. And then, when the determination result is negative, determining the current local cloud node as the deployment position of the arbitrary second class component. Therefore, the deployment position of the second class component can be determined according to the network capability, so that all components associated with the cloud service can be prevented from being directly deployed at a local cloud node or at a central cloud, and reasonable deployment of the components associated with the cloud service can be realized.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments disclosed in the present specification, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only examples of the embodiments disclosed in the present specification, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is an exemplary system architecture diagram in which some embodiments of the present description may be applied;
FIG. 2 is a flow diagram of one embodiment of a service deployment processing method for a distributed cloud architecture;
FIG. 3 is a flow diagram of one embodiment of a service deployment processing method for a distributed cloud architecture;
FIG. 4 is a flow diagram of one embodiment of a service deployment processing method for a distributed cloud architecture;
FIG. 5 is a schematic illustration of a deployment location determination process for several components;
fig. 6 is a schematic diagram of a structure of a service deployment processing device for a distributed cloud architecture.
Detailed Description
The present specification is further described in detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. The described embodiments are only some of the embodiments of the present description and not all of the embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present application based on the embodiments herein.
For convenience of description, only a portion related to the present invention is shown in the drawings. Embodiments and features of embodiments in this specification may be combined with each other without conflict.
As described above, the existing deployment scheme for deploying all components associated with the cloud service required to be provided by the existing deployment scheme on the local cloud node has higher resource requirements and lower efficiency on the local cloud node. All components related to cloud services required to be provided by the local cloud node are deployed to a deployment scheme of the central cloud, the stability requirement on a network link between the local cloud node and the central cloud is high, and once the network fails, the cloud services deployed by the local cloud node cannot work.
Based on the above, some embodiments of the present disclosure provide a service deployment processing method for a distributed cloud architecture, which can implement reasonable deployment of components associated with cloud services that need to be provided by a local cloud node.
In particular, FIG. 1 illustrates an exemplary system architecture diagram suitable for use in some embodiments of the present description. As shown in fig. 1, the system architecture may include a distributed cloud architecture, as well as a service deployment processing system. The service deployment processing system can perform service deployment processing aiming at the distributed cloud architecture.
The distributed cloud architecture may include a central cloud and a plurality of local cloud nodes (e.g., a plurality of edge cloud nodes shown in fig. 1). The central cloud may be one or more central clouds. A local cloud may be understood as a small-scale deployed cloud that can implement some or all of the cloud's capabilities.
In practice, for any local cloud node in the plurality of local cloud nodes, the service deployment processing system may perform service deployment processing related to the cloud service for the cloud service that needs to be provided by the any local cloud node. The cloud service may be embodied as one or more cloud services and may be determined according to the size and requirements of the arbitrary local cloud node. Further, the cloud service may be manually specified, or may be determined by the service deployment processing system according to a preset cloud service determination policy, which is not specifically limited herein.
Cloud services are understood to be an increasing, usage and interaction pattern of internet-based related services, typically involving the provision of dynamically extensible and often virtualized resources over the internet. The single cloud service may include, for example, ECS (Elastic Compute Service, cloud server), EBS (Elastic Block Storage ), OSS (Object Storage Service, object storage service), SLS (log service), RDS (RelationalDatabase Service, relational database), or SLB (Server Load Balancer, server load balancing), and so on.
In general, cloud services may associate multiple types of components, which may include, for example, a first type of component, a second type of component, and so on. In practice, an association relationship between the cloud service and the associated multiple types of components can be pre-established, and the service deployment processing system can know which components are associated with the cloud service based on the association relationship.
The first type of component may be a component on which cloud services locally need to rely. In particular, the first type of component may be, for example, a cloud service runtime dependent component, or a necessary management component required for local management. The first type of component should generally be deployed at the local cloud node to maintain basic operational use of the local cloud node.
The second type of component may be understood as an optional component of the local cloud node. In other words, the second type of component is not necessarily a component that is deployed at a local cloud node. Moreover, the second type of component may be a component of a network capability sensitive class, such as a management component of a network capability sensitive class, which may include network latency and/or network bandwidth, etc. In practice, network capability requirements may be pre-configured for each second-class component associated with a cloud service, such that a deployment location of each second-class component may be determined according to the network capability, e.g., whether to deploy at a local cloud node or at a central cloud.
Based on the above description, a cloud service that needs to be provided by any local cloud node may be associated with a number of first type components, and the service deployment processing system may, for example, determine the any local cloud node as a deployment location of each of the number of first type components. In addition, the cloud service may further associate a plurality of second-class components, and the service deployment processing system may determine, for example, a deployment location of each of the plurality of second-class components in the central cloud and the arbitrary local cloud node according to a network condition from the central cloud to the arbitrary local cloud node and respective network capability requirements of each of the plurality of second-class components.
By adopting the service deployment processing process, for a plurality of second class components of the network capacity sensitive class associated with the cloud service, the respective deployment positions of the plurality of second class components can be determined according to the network capacity, so that all components associated with the cloud service can be prevented from being directly deployed at a local cloud node or in a central cloud, and reasonable deployment of the components associated with the cloud service can be realized.
In the following, specific implementation steps of the above method are described in connection with specific embodiments.
Referring to fig. 2, a flow 200 of one embodiment of a service deployment processing method for a distributed cloud architecture is shown. The distributed cloud architecture may include a central cloud and a plurality of local cloud nodes. The subject of execution of the method may be the service deployment processing system shown in fig. 1. The method comprises the following steps:
Step 202, obtaining network condition information from a central cloud to a current local cloud node, wherein the current local cloud node is one of the plurality of local cloud nodes, cloud services required to be provided by the current local cloud node are associated with a plurality of second class components to be deployed, and the plurality of second class components have network capability requirements;
step 204, for any second type component in the plurality of second type components, determining whether the network condition information meets the network capability requirement of the any second type component, and obtaining a determination result corresponding to the any second type component;
and 206, if the result of the determination is negative, determining the current local cloud node as the deployment position of any second class component.
In this embodiment, for the explanation of the second type of component, reference may be made to the foregoing related description, which is not repeated here. The network capability requirements may include, for example, bandwidth requirements and/or latency requirements. Based on this, in step 202, the current network bandwidth and/or the current network latency of the central cloud to the current local cloud node may be specifically obtained.
It should be appreciated that the network condition information may include a current network bandwidth and/or a current network latency. For example, when the network capability requirement includes a bandwidth requirement, the network condition information may include a current network bandwidth. When the network capability requirement includes a latency requirement, the network condition information may include a current network latency. When the network capability requirements include bandwidth requirements and latency requirements, the network condition information may include a current network bandwidth and a current network latency.
In practice, the service deployment processing system, the current local cloud node or the central cloud may store the network condition information, and the service deployment processing system may acquire the network condition information from the local, current local cloud node or the central cloud.
The bandwidth requirement may be, for example, a minimum bandwidth requirement, which may include a lower bandwidth limit (which may also be referred to as a minimum bandwidth), and a corresponding bandwidth occupation factor of the second class of components. The bandwidth requirement may, for example, indicate that the ratio of the lower bandwidth limit to the current network bandwidth is less than or equal to the bandwidth occupancy factor. Wherein the bandwidth occupation factor may be a value greater than 0 and less than or equal to 1. In general, the bandwidth occupation factor may be set according to practical situations, for example, when the second class of components have high bandwidth requirements, the bandwidth occupation factor may be set smaller.
The latency requirement may be, for example, a maximum latency tolerance requirement, which may include an upper latency limit (which may also be referred to as a maximum latency), and a corresponding latency sensitivity factor for the second class of components. The delay requirement may indicate, for example, that the ratio of the upper delay bound to the current network delay is greater than or equal to a delay sensitivity factor. The delay sensitivity factor may be a value of 1 or more. Typically, the delay sensitivity factor may be set according to the actual situation, for example, when the second class of components are more sensitive to delay, the delay sensitivity factor may be set higher.
It should be noted that the bandwidth requirements described above may also indicate that the bandwidth lower limit is less than or equal to the product of the bandwidth occupancy factor and the current network bandwidth. The latency requirement may also indicate that the upper latency limit is greater than or equal to the product of the latency sensitivity factor and the current network latency.
Next, in step 204, for any second type component in the plurality of second type components, it may be determined whether the network status information meets the network capability requirement of the any second type component, to obtain a determination result corresponding to the any second type component.
For example, when the network capability requirements include bandwidth requirements and the network condition information includes current network bandwidth, it may be determined in step 204 whether the current network bandwidth meets the bandwidth requirements of any of the second type of components described above.
As another example, when the network capability requirements include latency requirements and the network condition information includes a current network latency, it may be determined whether the current network latency meets the latency requirements of any of the second type of components described above in step 204.
As another example, when the network capability requirements include bandwidth requirements and latency requirements, and the network condition information includes a current network bandwidth and a current network latency, in step 204, it may be determined whether the current network bandwidth and the current network latency satisfy both the bandwidth requirements and the latency requirements of any of the second type of components described above. It should be understood that simultaneous satisfaction herein means that the current network bandwidth meets the bandwidth requirement and the current network delay meets the delay requirement.
It should be noted that, if the bandwidth requirement indicates that the bandwidth lower limit is less than or equal to the product of the bandwidth occupation factor and the current network bandwidth, when determining whether the current network bandwidth from the central cloud to the current local cloud node meets the bandwidth requirement of any second class component, the product of the bandwidth occupation factor in the bandwidth requirement and the current network bandwidth may be calculated. Then, it may be determined whether the lower bandwidth limit in the bandwidth requirement is equal to or less than the product. If the determination is yes, it may be determined that the current network bandwidth meets the bandwidth requirement. If the determination result is negative, it may be determined that the current network bandwidth does not meet the bandwidth requirement.
If the delay requirement indicates that the upper limit of the delay is greater than or equal to the product of the delay sensitivity factor and the current network delay, when determining whether the current network delay from the central cloud to the current local cloud node meets the delay requirement of any second class component, the product of the delay sensitivity factor in the delay requirement and the current network delay can be calculated. Then, it may be determined whether the upper delay bound in the delay requirement is greater than or equal to the product. If the determination result is yes, the current network delay can be determined to meet the delay requirement. If the result of the determination is negative, it can be determined that the current network delay does not meet the delay requirement.
Next, in step 206, if the determination result corresponding to the arbitrary second-class component is no, that is, the determination result indicates that the network status information does not meet the network capability requirement of the arbitrary second-class component, the current local cloud node may be determined as the deployment location of the arbitrary second-class component. In other words, if the determination result is no, it may be determined to deploy any of the second type components to the current local cloud node.
The scheme provided by the embodiment corresponding to fig. 2 can determine the deployment position of the second class of components according to the network capability, so that all components associated with the cloud service can be prevented from being directly deployed at the local cloud node or all components associated with the cloud service are prevented from being deployed at the central cloud, and reasonable deployment of the components associated with the cloud service can be realized.
In practice, for the components corresponding to the above-mentioned components in the second class, the deployment positions of the components may be determined by using multiple methods.
As one implementation, the central cloud may be determined directly as the deployment location of each of the several components. In particular, referring to fig. 3, a flow 300 of one embodiment of a service deployment processing method for a distributed cloud architecture is shown. The distributed cloud architecture may include a central cloud and a plurality of local cloud nodes. The subject of execution of the method may be the service deployment processing system shown in fig. 1. The method comprises the following steps:
Step 302, obtaining network condition information from a central cloud to a current local cloud node, wherein the current local cloud node is one of the plurality of local cloud nodes, cloud services required to be provided by the current local cloud node are associated with a plurality of second class components to be deployed, and the plurality of second class components have network capability requirements;
step 304, for any second type component in the plurality of second type components, determining whether the network condition information meets the network capability requirement of the any second type component, and obtaining a determination result corresponding to the any second type component;
step 306, if the result of the determination is no, determining the current local cloud node as the deployment position of any second class component;
and 308, if the result of the determination is yes, determining the central cloud as the deployment position of any second class component.
In this embodiment, for the explanation of steps 302-306, reference may be made to the relevant explanation of steps 202-206 in the corresponding embodiment of fig. 2, and the description is omitted here. In step 308, the central cloud may be determined as the deployment location of any of the second type components in response to the determination that any of the second type components corresponds to yes. In other words, it may be determined that any of the second-class components is deployed to the central cloud in response to the determination that the corresponding any of the second-class components is yes.
Next, taking the current network delay T1 from the central cloud to the current local cloud node as 100ms (millisecond), the current network bandwidth W1 as 10G (GigaByte), the cloud service required to be provided by the current local cloud node includes ECS and SLB, several second-class components associated with the cloud service ECS and SLB include ECS probe components and SLB probe components, and the network capability requirements of each of the two probe components include bandwidth requirements and delay requirements as an example, a scheme provided by the embodiment is further described.
Under the condition that the bandwidth requirement indicates that the bandwidth lower limit is smaller than or equal to the product of the bandwidth occupation factor and the current network bandwidth, and the time delay requirement indicates that the time delay upper limit is larger than or equal to the product of the time delay sensitivity factor and the current network time delay, the bandwidth requirement of the ECS probe assembly is assumed to comprise the bandwidth lower limit w1 and the bandwidth occupation factor a1, and the time delay requirement comprises the time delay upper limit t1 and the time delay sensitivity factor b1. Where w1=100M (MByte, megabyte), a1=0.1, t1=150 ms, b1=1.
As is well known, 1 g=1024M, and a1×w1=1024M can be calculated based on such a conversion relation. In addition, b1×t1=100 ms can also be calculated. Through comparison, W1<1024M and T1>100ms can be determined, and further it can be determined that the current network bandwidth W1 of the current local cloud node meets the bandwidth requirement of the ECS probe activity assembly, and the current network time delay T1 meets the time delay requirement of the ECS probe activity assembly. Thus, it may be decided to deploy the ECS probe components to the central cloud such that the ECS probe components are remotely managed.
The bandwidth requirement of the SLB probe activity assembly is assumed to include a bandwidth lower limit w2 and a bandwidth occupancy factor a2, and the delay requirement includes a delay upper limit t2 and a delay sensitivity factor b2. Where w2=5m, a2=0.1, t2=30 ms, b2=1. A2×w1=1024m, b2×t1=100 ms can be calculated. Through comparison, W2<1024M and T2<100ms can be determined, and further it can be determined that the current network bandwidth W1 of the current local cloud node meets the bandwidth requirement of the SLB probe activity assembly, but the current network time delay T1 does not meet the time delay requirement of the SLB probe activity assembly. Accordingly, it may be decided to deploy the SLB probe activity component to the current local cloud node such that the SLB probe activity component is locally managed at the current local cloud node.
The solution provided by the corresponding embodiment of fig. 3 may determine, according to the network capability, whether to deploy the second class component to the current local cloud node or to the central cloud. In this way, according to the network condition of the local cloud node, a plurality of second class components related to cloud services required to be provided by the local cloud node can be reasonably deployed to the central cloud and the local cloud node, so that the management and control cost required by the deployment of the local cloud node is reduced, the central cloud is used for realizing unified management and control on the local cloud node, and corresponding cloud services are provided.
As another implementation, when the network capability requirements include bandwidth requirements, the central cloud may be configured with total bandwidth requirements related to the second class of components for the current local cloud node. Based on this, for the components whose corresponding determination results are yes in the above-mentioned components of the second class, for example, each component whose corresponding determination result is yes, the respective deployment positions of the components may be determined in the central cloud and the current local cloud nodes according to the total bandwidth requirement and the respective bandwidth requirement of the each component.
In particular, referring to fig. 4, a flow 400 of one embodiment of a service deployment processing method for a distributed cloud architecture is shown. The distributed cloud architecture may include a central cloud and a plurality of local cloud nodes. The subject of execution of the method may be the service deployment processing system shown in fig. 1. The method comprises the following steps:
step 402, obtaining network condition information from a central cloud to a current local cloud node, wherein the current local cloud node is one of the plurality of local cloud nodes, cloud services required to be provided by the current local cloud node are associated with a plurality of second class components to be deployed, and the plurality of second class components have network capability requirements;
Step 404, for any second type component in the plurality of second type components, determining whether the network condition information meets the network capability requirement of the any second type component, and obtaining a determination result corresponding to the any second type component, wherein the network capability requirement comprises a bandwidth requirement;
step 406, if the determination result is no, determining the current local cloud node as the deployment position of any second class component;
step 408, for the components corresponding to the above-mentioned second-class components, determining the respective deployment positions of the components in the central cloud and the current local cloud node according to the total bandwidth requirements of the central cloud configured for the current local cloud node and related to the second-class components and the respective bandwidth requirements of the components.
In this embodiment, for the explanation of steps 402-406, reference may be made to the relevant explanation of steps 202-206 in the corresponding embodiment of fig. 2, and the explanation is omitted here. It is noted in particular that network capability requirements may include latency requirements as well as bandwidth requirements.
In step 408, for the components corresponding to the above-mentioned components of the second class, the deployment positions of the components may be determined in the central cloud and the current local cloud node according to the total bandwidth requirement of the central cloud configured for the current local cloud node and related to the components of the second class, and the respective bandwidth requirements of the components.
The total bandwidth requirement may include an upper bandwidth proportion limit. The upper bandwidth proportion limit may be a constant not greater than 1, which may be understood as the maximum bandwidth proportion that each second class component for remote control of the local cloud node is able to occupy. In practice, the second class component's control capability may be referred to as a second class control capability, and the upper bandwidth proportion limit may also be understood as the maximum bandwidth proportion that the remote second class control capability of the local cloud node can occupy.
In general, the upper limit of the bandwidth proportion may be set according to practical situations, for example, when the bandwidth is rich, larger may be set. Specifically, for the current local cloud node, a bandwidth proportion upper limit may be generally set to be equal to or greater than a target value and equal to or less than 1. The target value may be, for example, a maximum value of respective bandwidth occupation factors of respective components that meet the bandwidth requirement among the above-mentioned several second class components.
The total bandwidth requirement may, for example, indicate that the sum of respective lower bandwidths of the respective second class of components for remotely controlling the local cloud node is less than or equal to the product of the upper bandwidth proportion limit and the current network bandwidth. Based on this, in step 408, a deployment location determination process as shown in fig. 5 may be performed. The deployment location determination process comprises the steps of:
Step 502, calculating the sum of bandwidth lower limits of a plurality of components;
step 504, determining whether the calculated sum meets the total bandwidth requirement;
step 506, if the result of the determination is yes, determining the central cloud as the deployment position of each of the plurality of components;
step 508, if the result of the determination is no, selecting one component from the plurality of components, and determining the current local cloud node as the deployment position of the component;
step 510, the remaining components of the plurality of components are updated to a plurality of components, and step 502 is continued.
The bandwidth requirements in this embodiment may include a lower bandwidth limit as previously described. In step 502, for a plurality of components corresponding to the plurality of second class components, a sum of respective bandwidth lower limits of the plurality of components may be calculated.
Next, in step 504, it may be determined whether the calculated sum meets the total bandwidth requirement. For example, the network condition information includes a current network bandwidth, the total bandwidth requirement includes an upper bandwidth proportion limit, and a product of the current network bandwidth and the upper bandwidth proportion limit can be calculated. Then, it may be determined whether the sum is equal to or less than the product. If the determination is yes, it may be determined that the sum meets the total bandwidth requirement, and then step 506 may continue. If the determination is negative, it may be determined that the sum does not meet the total bandwidth requirement, and then step 508 may continue.
In step 506, the central cloud may be determined as the deployment location of each of the several components, i.e., it may be determined to deploy each of the several components to the central cloud, in response to determining that the calculated sum meets the total bandwidth requirement.
In step 508, in response to determining that the calculated sum meets the total bandwidth requirement, a component may be selected from the several components and the current local cloud node is determined as a deployment location of the component, i.e., it is determined to deploy the component to the current local cloud node.
When one component is selected from the above-described components, various selection methods may be employed. For example, one component may be randomly selected. For another example, a component may be selected from the plurality of components in order of increasing bandwidth lower limit, for example, a component having the highest bandwidth lower limit may be selected from the plurality of components. For another example, when the network capability requirement further includes a latency requirement, one component may be selected from the several components in order of decreasing latency upper limit, for example, a component having the smallest latency upper limit may be selected from the several components.
Next, in step 510, the remaining components of the plurality of components may be updated to a plurality of components, and step 502 may be performed based on the plurality of components.
Next, taking the current network time delay T1 from the central cloud to the current local cloud node as 10ms, the current network bandwidth W1 as 1G, cloud services required to be provided by the current local cloud node include ECS and SLB, a plurality of second-class components associated with the cloud services ECS and SLB include ECS probe activity components and SLB probe activity components, and respective network capacity requirements of the two probe activity components include bandwidth requirements and time delay requirements as an example, a scheme provided by the embodiment is further described.
Assuming that the bandwidth requirement of the ECS active detection component includes a bandwidth lower limit w1 and a bandwidth occupation factor a1, the delay requirement includes a delay upper limit t1 and a delay sensitivity factor b1, where w1=100m, a1=0.1, t1=150ms, b1=1; the bandwidth requirement of the SLB active detection component comprises a bandwidth lower limit w2 and a bandwidth occupation factor a2, and the delay requirement comprises a delay upper limit t2 and a delay sensitivity factor b2. Wherein w2=5m, a2=0.1, t2=30ms, b2=1; the upper bandwidth ratio limit r in the total bandwidth requirement is 0.1.
Through calculation and comparison, the current network bandwidth W1 of the current local cloud node can be known to meet respective bandwidth requirements of the ECS (electronic control system) activity detection assembly and the SLB activity detection assembly, and the current network time delay T1 meets respective time delay requirements of the ECS activity detection assembly and the SLB activity detection assembly.
Next, for both the ECS probe assembly and the SLB probe assembly, the final deployment location of both needs to be determined.
Specifically, w1+w2=105m and r×w1=102.4m can be calculated. Since 105m >102.4m, it can be determined that the sum of w1 and w2 does not meet the total bandwidth requirement, the ECS probe components and the SLB probe components cannot both be deployed to the central cloud. Thus, one component may be first selected from the ECS probe component and the SLB probe component and it may be determined to deploy the component to the current local cloud node. Considering that the current network bandwidth W1 is low, ECS (electronic control system) probe components with high bandwidth occupation can be selected to be deployed to the current local cloud nodes so as to reduce the requirement on the bandwidth. For the remaining SLB active components, since its lower bandwidth limit w2<102.4M, it can be determined that w2 meets the total bandwidth requirement. Thus, the SLB probe activity component may be selected for deployment to the central cloud.
It should be appreciated that other deployment strategies may also be employed for the ECS probe assembly and the SLB probe assembly. For example, an ECS probe component may be selected for deployment to the central cloud, and an SLB probe component may be selected for deployment to the current local cloud node.
In practice, the total bandwidth requirement as described above may also indicate that the sum of the respective lower bandwidths of the second class components for remotely controlling the local cloud node and the occupation ratio of the current network bandwidth is smaller than or equal to the upper bandwidth ratio limit.
Based on this, step 502 described above may be replaced by calculating the sum of the bandwidth lower limits of the individual components and the occupancy proportion of the current network bandwidth. Specifically, for each of the several components, a ratio of the bandwidth lower limit of the component to the current network bandwidth may be calculated first, and the ratio may be taken as an occupation ratio of the bandwidth lower limit of the component to the current network bandwidth. The sum of the respective occupancy ratios of the several components can then be calculated.
Accordingly, in the step 504, it may be determined whether the sum calculated in the step 502 is equal to or less than the bandwidth occupation ratio in the total bandwidth requirement. If the determination is yes, it may be determined that the sum meets the total bandwidth requirement. If the determination is negative, it may be determined that the sum does not meet the total bandwidth requirement.
According to the scheme provided by the corresponding embodiment of fig. 4, according to the total bandwidth requirement of the central cloud on the current local cloud node configuration related to the second-class components and the respective bandwidth requirements of the components with the corresponding determination results of the second-class components, the respective deployment positions of the components are determined, so that reasonable deployment of the second-class components can be further realized.
In one embodiment, cloud services that are currently required to be provided by the local cloud node may be associated with a plurality of first-type components while associating a plurality of second-type components. The first type of component may be a component on which the cloud service locally needs to depend. In particular, the first type of component may be, for example, a component that the cloud service is dependent on at runtime, or a necessary management component that is required for local management. Based on this, the deployment location of each of the number of first-type components may also be determined. For example, the deployment location of each of the plurality of first type components may be determined prior to obtaining network condition information for the central cloud to the current local cloud node. Since the first type of component is a component on which the cloud service locally needs to depend, the current local cloud node may be determined as the deployment location of each of the several first type of components.
In one embodiment, cloud services that are currently required to be provided by the local cloud node may be associated with a number of second-class components and a number of third-class components. The third type of component can be other components capable of realizing remote control on the local cloud node. It should be appreciated that the third type of component is different from the first and second types of components previously described. In this embodiment, the central cloud may be determined as the deployment location of each of the several third class components.
In one embodiment, a service deployment processing system may have service deployment capabilities. Based on this, in the case where the cloud service to be provided by the current local cloud node is not yet deployed and the cloud service is associated with a plurality of first-type components, the service deployment processing system may deploy the cloud service and the plurality of first-type components to the current local cloud node after determining the current local cloud node as the deployment positions of the plurality of first-type components, respectively. For example, the cloud service and the number of first-class components may be deployed to a data center of a current local cloud node.
In addition, after determining the deployment positions of the second-class components, the service deployment processing system may further deploy the second-class components to corresponding deployment positions.
In addition, in the case that the cloud service required to be provided by the current local cloud node associates a plurality of third class components, the service deployment processing system may further deploy the plurality of third class components to the central cloud after determining the central cloud as a deployment location of each of the plurality of third class components.
With further reference to FIG. 6, the present specification provides one embodiment of a service deployment processing apparatus for a distributed cloud architecture that may be applied to the service deployment processing system shown in FIG. 1. Wherein the distributed cloud architecture may include a central cloud and a plurality of local cloud nodes.
As shown in fig. 6, the service deployment processing apparatus 600 for a distributed cloud architecture of the present embodiment includes: an acquisition unit 601, a first determination unit 602, and a second determination unit 603. The acquiring unit 601 is configured to acquire network condition information from a central cloud to a current local cloud node, where the current local cloud node is one of the plurality of local cloud nodes, and cloud services required to be provided by the current local cloud node are associated with a plurality of second type components to be deployed, and each of the plurality of second type components has a network capability requirement; the first determining unit 602 is configured to determine, for any second-class component in the plurality of second-class components, whether the network status information meets the network capability requirement of the any second-class component, and obtain a determination result corresponding to the any second-class component; the second determining unit 603 is configured to determine the current local cloud node as the deployment location of the arbitrary second class component if the determination result is negative.
In some embodiments, the second determining unit 603 may be further configured to: and if the result of the determination is yes, determining the central cloud as the deployment position of any second class component.
In some embodiments, the network capability requirements may include bandwidth requirements and the network condition information may include current network bandwidth; and/or the network capability requirement may include a latency requirement and the network condition information may include a current network latency.
In some embodiments, where the network capability requirements include bandwidth requirements and latency requirements, the network condition information includes a current network bandwidth and a current network time delay, the first determining unit 602 may be further configured to: and determining whether the current network bandwidth and the current network delay meet the bandwidth requirement and the delay requirement of any second class component at the same time.
In some embodiments, the network capability requirements may include bandwidth requirements, and the central cloud may be configured with total bandwidth requirements related to the second class of components for the current local cloud node; and the second determination unit 603 may be further configured to: and aiming at the components with the corresponding determined results in the second class of components, determining the respective deployment positions of the components in the central cloud and the current local cloud node according to the total bandwidth requirement and the respective bandwidth requirement of the components.
In some embodiments, the bandwidth requirements of the second class of components may include a lower bandwidth limit; and the second determination unit 603 may be further configured to: calculating the sum of the bandwidth lower limits of the components; determining whether the sum meets a total bandwidth requirement; in response to determining that the sum meets the overall bandwidth requirement, a central cloud is determined as a deployment location for each of the several components.
In some embodiments, the second determining unit 603 may be further configured to: in response to determining that the sum does not meet the total bandwidth requirement, selecting one component from the plurality of components, and determining a current local cloud node as a deployment location of the component; and updating the rest of the components into the components, and continuously executing the calculation of the sum of the respective bandwidth lower limits of the components.
In some embodiments, the second determining unit 603 may be further configured to: and selecting one component from the components according to the order of the lower bandwidth limit from large to small.
In some embodiments, the cloud service may also associate several first type components to be deployed, which may be components on which the cloud service locally needs to rely; and the second determination unit 603 may be further configured to: before the acquiring unit 601 acquires network condition information from the central cloud to the current local cloud node, the current local cloud node is determined as a deployment position of the plurality of first-type components.
In some embodiments, the apparatus 600 may further include: a service deployment unit (not shown in the figure) is configured to deploy the cloud service and the plurality of first-type components to the current local cloud node when the cloud service has not been deployed to the current local cloud node, and after the second determination unit 603 determines the current local cloud node as the deployment location of the plurality of first-type components.
In some embodiments, the cloud service may also associate several third-class components to be deployed, which may be components that enable remote management and control; and the second determination unit 603 may be further configured to: a central cloud is determined as a deployment location for each of the number of third class components.
In the embodiment of the apparatus corresponding to fig. 6, the specific processing of each unit and the technical effects brought by the processing may refer to the related description of the method embodiment in the foregoing, and will not be repeated herein.
The embodiments of the present specification also provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed in a computer, causes the computer to execute the service deployment processing method for the distributed cloud architecture described in the above method embodiments, respectively.
The embodiment of the specification also provides a computing device, which comprises a memory and a processor, wherein executable codes are stored in the memory, and when the processor executes the executable codes, the service deployment processing method for the distributed cloud architecture, which is respectively described in the above method embodiments, is realized.
The embodiments of the present specification also provide a computer program, where the computer program when executed in a computer causes the computer to execute the service deployment processing method for the distributed cloud architecture described in the above method embodiments respectively.
Those of skill in the art will appreciate that in one or more of the above examples, the functions described in the various embodiments disclosed herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, these functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
While the foregoing detailed description has described the objects, aspects and advantages of the embodiments disclosed herein in further detail, it should be understood that the foregoing detailed description is merely illustrative of the embodiments disclosed herein and is not intended to limit the scope of the embodiments disclosed herein, but rather any modifications, equivalents, improvements or the like that may be made to the embodiments disclosed herein are intended to be included within the scope of the embodiments disclosed herein.
Claims (14)
1. A service deployment processing method for a distributed cloud architecture, the distributed cloud architecture including a central cloud and a plurality of local cloud nodes, the method comprising:
acquiring network condition information from the central cloud to a current local cloud node, wherein the current local cloud node is one of the plurality of local cloud nodes, cloud services required to be provided by the current local cloud node are associated with a plurality of second type components to be deployed, and the plurality of second type components are management and control components of network capacity sensitive types and have network capacity requirements;
for any second type component in the plurality of second type components, determining whether the network condition information meets the network capability requirement of the any second type component, and obtaining a determination result corresponding to the any second type component;
and if the determination result is negative, determining the current local cloud node as the deployment position of the arbitrary second class component.
2. The method of claim 1, further comprising:
and if the determination result is yes, determining the central cloud as the deployment position of the arbitrary second class component.
3. The method of claim 1, wherein,
The network capability requirements include bandwidth requirements, the network condition information including current network bandwidth; and/or the number of the groups of groups,
the network capability requirement includes a latency requirement, and the network condition information includes a current network latency.
4. The method of claim 3, wherein when the network capability requirements include bandwidth requirements and latency requirements, the network condition information includes the current network bandwidth and the current network time delay, the determining whether the network condition information meets the network capability requirements of the arbitrary second class component comprises:
and determining whether the current network bandwidth and the current network time delay meet the bandwidth requirement and the time delay requirement of any second class component at the same time.
5. A method according to claim 3, wherein network capability requirements include bandwidth requirements, the central cloud being configured with a total bandwidth requirement relating to a second class of components for the current local cloud node; and
the method further comprises the steps of:
and aiming at the components with the corresponding determined results in the second class of components, determining the respective deployment positions of the components in the central cloud and the current local cloud node according to the total bandwidth requirement and the respective bandwidth requirement of the components.
6. The method of claim 5, wherein the bandwidth requirements of the second class of components include a lower bandwidth limit; and
said determining, in the central cloud and the current local cloud node, respective deployment locations of the plurality of components according to the total bandwidth requirement and respective bandwidth requirements of the plurality of components, comprising:
calculating the sum of the bandwidth lower limits of the components;
determining whether the sum meets the total bandwidth requirement;
in response to determining that the sum meets the total bandwidth requirement, the central cloud is determined as a deployment location for each of the number of components.
7. The method of claim 6, wherein the determining, in the central cloud and the current local cloud node, the respective deployment locations of the plurality of components according to the total bandwidth requirement and the respective bandwidth requirements of the plurality of components further comprises:
in response to determining that the sum does not meet the total bandwidth requirement, selecting one component from the number of components and determining the current local cloud node as a deployment location for the component;
updating the rest of the components to a plurality of components, and continuing to execute the calculation of the sum of the respective lower bandwidths of the components.
8. The method of claim 7, wherein said selecting one component from said plurality of components comprises:
and selecting one component from the components according to the order of the lower bandwidth limit from large to small.
9. The method of claim 1, wherein the cloud service is further associated with a number of first-type components to be deployed, the number of first-type components being components on which the cloud service locally needs to rely; and
the method further comprises the steps of:
before the network condition information from the central cloud to the current local cloud node is acquired, the method further comprises:
and determining the current local cloud node as the deployment position of the first type of components.
10. The method of claim 9, wherein after determining the current local cloud node as the deployment location of the number of first-type components when the cloud service has not been deployed to the current local cloud node, further comprising:
and deploying the cloud service and the first type components to the current local cloud node.
11. The method of one of claims 1-10, wherein the cloud service is further associated with a number of third class components to be deployed, the number of third class components being remotely controllable components; and
The method further comprises the steps of:
and determining the central cloud as the deployment position of each of the third class of components.
12. A service deployment processing apparatus for a distributed cloud architecture, the distributed cloud architecture comprising a central cloud and a plurality of local cloud nodes, the apparatus comprising:
the system comprises an acquisition unit, a network capacity management unit and a network capacity management unit, wherein the acquisition unit is configured to acquire network condition information from the central cloud to a current local cloud node, wherein the current local cloud node is one of a plurality of local cloud nodes, cloud services required to be provided by the current local cloud node are associated with a plurality of second type components to be deployed, and the plurality of second type components are management and control components of network capacity sensitive types and respectively have network capacity requirements;
the first determining unit is configured to determine whether the network condition information meets the network capability requirement of any second type component in the plurality of second type components, and obtain a determination result corresponding to the any second type component;
and the second determining unit is configured to determine the current local cloud node as the deployment position of the arbitrary second class component if the determination result is negative.
13. A computer readable storage medium having stored thereon a computer program, wherein the computer program, when executed in a computer, causes the computer to perform the method of any of claims 1-11.
14. A computing device comprising a memory and a processor, wherein the memory has executable code stored therein, which when executed by the processor, implements the method of any of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210429489.9A CN114826900B (en) | 2022-04-22 | 2022-04-22 | Service deployment processing method and device for distributed cloud architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210429489.9A CN114826900B (en) | 2022-04-22 | 2022-04-22 | Service deployment processing method and device for distributed cloud architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114826900A CN114826900A (en) | 2022-07-29 |
| CN114826900B true CN114826900B (en) | 2024-03-29 |
Family
ID=82505713
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210429489.9A Active CN114826900B (en) | 2022-04-22 | 2022-04-22 | Service deployment processing method and device for distributed cloud architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114826900B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110308995A (en) * | 2019-07-08 | 2019-10-08 | 童晓雯 | A kind of edge cloud computing service system edges cloud node deployment device |
| US10848988B1 (en) * | 2019-05-24 | 2020-11-24 | At&T Intellectual Property I, L.P. | Dynamic cloudlet fog node deployment architecture |
| CN112020103A (en) * | 2020-08-06 | 2020-12-01 | 暨南大学 | Content cache deployment method in mobile edge cloud |
| CN112087332A (en) * | 2020-09-03 | 2020-12-15 | 哈尔滨工业大学 | Virtual network performance optimization system under cloud edge cooperation |
| CN112242908A (en) * | 2019-07-16 | 2021-01-19 | 中移(苏州)软件技术有限公司 | Network function deployment method, system and storage medium |
| CN112995682A (en) * | 2021-04-21 | 2021-06-18 | 军事科学院系统工程研究院网络信息研究所 | Method and device for deploying and migrating video cloud service |
| CN113178076A (en) * | 2021-06-30 | 2021-07-27 | 中移(上海)信息通信科技有限公司 | Vehicle-road cooperation system and vehicle-road cooperation method |
| CN113301078A (en) * | 2020-05-22 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Network system, service deployment and network division method, device and storage medium |
| CN113301089A (en) * | 2020-07-28 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Cloud service node deployment method and device |
| CN113301151A (en) * | 2021-05-24 | 2021-08-24 | 南京大学 | Low-delay containerized task deployment method and device based on cloud edge cooperation |
| CN113438678A (en) * | 2021-07-06 | 2021-09-24 | 中国联合网络通信集团有限公司 | Method and device for distributing cloud resources for network slices |
| CN114071582A (en) * | 2021-10-14 | 2022-02-18 | 北京邮电大学 | Service chain deployment method and device for cloud-edge collaborative Internet of things |
-
2022
- 2022-04-22 CN CN202210429489.9A patent/CN114826900B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10848988B1 (en) * | 2019-05-24 | 2020-11-24 | At&T Intellectual Property I, L.P. | Dynamic cloudlet fog node deployment architecture |
| CN110308995A (en) * | 2019-07-08 | 2019-10-08 | 童晓雯 | A kind of edge cloud computing service system edges cloud node deployment device |
| CN112242908A (en) * | 2019-07-16 | 2021-01-19 | 中移(苏州)软件技术有限公司 | Network function deployment method, system and storage medium |
| CN113301078A (en) * | 2020-05-22 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Network system, service deployment and network division method, device and storage medium |
| CN113301089A (en) * | 2020-07-28 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Cloud service node deployment method and device |
| CN112020103A (en) * | 2020-08-06 | 2020-12-01 | 暨南大学 | Content cache deployment method in mobile edge cloud |
| CN112087332A (en) * | 2020-09-03 | 2020-12-15 | 哈尔滨工业大学 | Virtual network performance optimization system under cloud edge cooperation |
| CN112995682A (en) * | 2021-04-21 | 2021-06-18 | 军事科学院系统工程研究院网络信息研究所 | Method and device for deploying and migrating video cloud service |
| CN113301151A (en) * | 2021-05-24 | 2021-08-24 | 南京大学 | Low-delay containerized task deployment method and device based on cloud edge cooperation |
| CN113178076A (en) * | 2021-06-30 | 2021-07-27 | 中移(上海)信息通信科技有限公司 | Vehicle-road cooperation system and vehicle-road cooperation method |
| CN113438678A (en) * | 2021-07-06 | 2021-09-24 | 中国联合网络通信集团有限公司 | Method and device for distributing cloud resources for network slices |
| CN114071582A (en) * | 2021-10-14 | 2022-02-18 | 北京邮电大学 | Service chain deployment method and device for cloud-edge collaborative Internet of things |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114826900A (en) | 2022-07-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200137151A1 (en) | Load balancing engine, client, distributed computing system, and load balancing method | |
| US20050132379A1 (en) | Method, system and software for allocating information handling system resources in response to high availability cluster fail-over events | |
| CN110365748A (en) | Treating method and apparatus, storage medium and the electronic device of business datum | |
| CN111880936A (en) | Resource scheduling method and device, container cluster, computer equipment and storage medium | |
| CN112214288B (en) | Pod scheduling method, device, equipment and medium based on Kubernetes cluster | |
| CN106789308B (en) | GIS service device with micro-service architecture capable of automatically stretching and retracting and control method thereof | |
| CN111694756B (en) | Application program testing method and device | |
| CN107465562B (en) | Method, device and equipment for CTDB custom distribution of virtual IP | |
| US20220070099A1 (en) | Method, electronic device and computer program product of load balancing | |
| CN113434283B (en) | Service scheduling method and device, server and computer readable storage medium | |
| CN111447143A (en) | Business service data transmission method and device, computer equipment and storage medium | |
| CN112631680B (en) | Micro-service container scheduling system, method, device and computer equipment | |
| CN114979286B (en) | Access control method, device, equipment and computer storage medium for container service | |
| CN114826900B (en) | Service deployment processing method and device for distributed cloud architecture | |
| CN112567687B (en) | Availability towards network slicing | |
| CN112035579B (en) | Graph management, data storage and data query methods, devices and storage medium | |
| CN115952003A (en) | Method, device, equipment and storage medium for cluster server load balancing | |
| US12058001B2 (en) | Control device, control method, control program and control system | |
| CN113064694A (en) | Resource scheduling method and device, electronic equipment and storage medium | |
| CN107317880B (en) | Method and device for realizing load balance | |
| CN113204434B (en) | Planned task execution method and device based on k8s and computer equipment | |
| CN111651278A (en) | Dynamic reconstruction method and platform based on software radar | |
| CN117971505B (en) | Method and device for deploying container application | |
| CN111597037B (en) | Job allocation method, job allocation device, electronic equipment and readable storage medium | |
| US20240296064A1 (en) | Job control system and control method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |