CN116170316A - Network system, instance management and control method, device and storage medium - Google Patents
Network system, instance management and control method, device and storage medium Download PDFInfo
- Publication number
- CN116170316A CN116170316A CN202310139017.4A CN202310139017A CN116170316A CN 116170316 A CN116170316 A CN 116170316A CN 202310139017 A CN202310139017 A CN 202310139017A CN 116170316 A CN116170316 A CN 116170316A
- Authority
- CN
- China
- Prior art keywords
- instance
- edge cloud
- cloud node
- edge
- management
- 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
- 238000000034 method Methods 0.000 title claims abstract description 104
- 238000003860 storage Methods 0.000 title claims abstract description 45
- 238000007726 management method Methods 0.000 claims description 469
- 238000013508 migration Methods 0.000 claims description 129
- 230000005012 migration Effects 0.000 claims description 127
- 230000008569 process Effects 0.000 claims description 42
- 230000015654 memory Effects 0.000 claims description 32
- 238000004590 computer program Methods 0.000 claims description 16
- 230000002159 abnormal effect Effects 0.000 claims description 10
- 238000012545 processing Methods 0.000 abstract description 38
- 230000004044 response Effects 0.000 abstract description 12
- 230000009286 beneficial effect Effects 0.000 abstract description 5
- 230000000694 effects Effects 0.000 abstract description 4
- 238000012423 maintenance Methods 0.000 description 190
- 238000012544 monitoring process Methods 0.000 description 86
- 238000004891 communication Methods 0.000 description 43
- 238000010276 construction Methods 0.000 description 33
- 230000006870 function Effects 0.000 description 28
- 230000008030 elimination Effects 0.000 description 21
- 238000003379 elimination reaction Methods 0.000 description 21
- 239000012634 fragment Substances 0.000 description 18
- 238000010586 diagram Methods 0.000 description 12
- 230000005540 biological transmission Effects 0.000 description 11
- 238000009826 distribution Methods 0.000 description 11
- 230000009471 action Effects 0.000 description 10
- 238000001914 filtration Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 9
- 238000007405 data analysis Methods 0.000 description 7
- 238000012217 deletion Methods 0.000 description 7
- 230000037430 deletion Effects 0.000 description 7
- 238000013467 fragmentation Methods 0.000 description 4
- 238000006062 fragmentation reaction Methods 0.000 description 4
- 230000010354 integration Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 238000012795 verification Methods 0.000 description 4
- 230000000903 blocking effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000009118 appropriate response Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 238000005315 distribution function Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000000737 periodic effect Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000007123 defense Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- 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/0893—Assignment of logical groups to network elements
-
- 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/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
-
- 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/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
-
- 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/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1012—Server selection for load balancing based on compliance of requirements or conditions with available server resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1021—Server selection for load balancing based on client or server locations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- 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/0894—Policy-based network configuration management
Abstract
The embodiment of the application provides a network system, an instance management and control method, equipment and a storage medium. In the embodiment of the application, in combination with the concept of edge computing, consider that the capability of cloud computing is put to the edge side closer to the terminal, and then a network system including edge cloud nodes is provided, in the network system, an instance capable of providing cloud computing service for a service demander is deployed in the edge cloud nodes, and under the control of central control equipment, the instance can provide cloud computing service for the service demander, so that the purpose of providing service for users by means of resources in the edge cloud nodes is achieved, and the effect of processing the cloud computing put to the edge cloud nodes closer to the terminal is realized, thereby being beneficial to reducing response delay and bandwidth cost.
Description
The present application is a divisional application of patent application with application number 2019102774654 and application date 2019, 04 month 08, and patent name "network system, example management and control method, equipment and storage medium".
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a network system, an instance management and control method, an instance management and control device, and a storage medium.
Background
At present, the concept of cloud computing is proposed based on centralized resource management and control, and even if a plurality of data centers are used for interconnection and interworking, all software and hardware resources are regarded as unified resources to be managed, scheduled and sold. With the advent of the age of 5G and the internet of things and the gradual increase of cloud computing applications, requirements of a terminal side on performances such as time delay and bandwidth of cloud resources are higher and higher, and a centralized cloud network cannot meet the requirements of the terminal side on the cloud resources which are increased day by day.
Disclosure of Invention
Aspects of the present application provide a network system, an instance management and control method, an instance management and control device, and a storage medium, which are used to reduce response delay of a service and reduce bandwidth cost.
The embodiment of the application provides an example management and control method, which comprises the following steps: determining at least one instance deployed in at least one edge cloud node in a network system, the at least one instance being operable to provide cloud computing services for service requesters; the at least one instance is managed for the at least one instance to provide cloud computing services for the service demander.
The embodiment of the application also provides a network system, which comprises: a central management and control device, and at least one edge cloud node; at least one instance is deployed in the at least one edge cloud node, and the at least one instance can provide cloud computing services for service requesters; the central control device is configured to control the at least one instance, so that the at least one instance provides cloud computing service for the service demander.
The embodiment of the application also provides a central control device, which comprises: a memory and a processor; the memory is used for storing a computer program; the computer program, when executed by the processor, causes the processor to implement the steps in the example management and control methods provided by embodiments of the present application.
The present embodiments also provide a computer-readable storage medium storing a computer program, which when executed by one or more processors causes the one or more processors to implement steps in an example management method provided by the embodiments of the present application.
In the embodiment of the application, in combination with the concept of edge computing, the capability of cloud computing is considered to be placed on the edge side closer to the terminal, and then a network system comprising edge cloud nodes is provided, in the network system, instances for providing cloud computing services are deployed in the edge cloud nodes, and under the control of central control equipment, the instances can provide cloud computing services, so that the purpose of providing services for users by means of resources in the edge cloud nodes is achieved, and the effect of processing the cloud computing in the edge cloud nodes closer to the terminal is realized, thereby being beneficial to reducing response delay of the services and reducing bandwidth cost.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
fig. 1a is a schematic structural diagram of a network system according to an exemplary embodiment of the present application;
fig. 1b is a schematic structural diagram of a central control device and an edge control device according to an exemplary embodiment of the present application;
fig. 1c is a schematic structural diagram of another network system according to an exemplary embodiment of the present application;
FIG. 2a is a flow chart of an example management and control method according to an exemplary embodiment of the present application;
FIG. 2b is a flow chart of an example upgrade method provided by an exemplary embodiment of the present application;
FIG. 2c is a flowchart illustrating an example migration method according to an exemplary embodiment of the present application
Fig. 3 is a schematic structural diagram of a central control device according to an exemplary embodiment of the present application.
Detailed Description
For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
Aiming at the technical problem that the existing centralized cloud network cannot meet the increasingly high cloud resource demands of the terminal, in some embodiments of the application, in combination with the concept of edge computing, the capability of cloud computing is considered to be put on the edge side closer to the terminal, and then a network system comprising edge cloud nodes is provided, in the network system, instances for providing cloud computing services are deployed in the edge cloud nodes, and under the control of central control equipment, the instances can provide cloud computing services, so that the purpose of providing services for users by means of resources in the edge cloud nodes is achieved, the effect of processing the cloud computing in the edge cloud nodes closer to the terminal is realized, the service response time delay is reduced, and the bandwidth cost is reduced.
The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.
Fig. 1a is a schematic structural diagram of a network system according to an exemplary embodiment of the present application. As shown in fig. 1a, the network system 100 includes: a central management and control device 101 and at least one edge cloud node 102; at least one edge cloud node 102 is network connected to the central management and control apparatus 101.
The network system 100 of the present embodiment is a cloud computing platform built on an edge infrastructure based on the cloud computing technology and the capability of edge computing, and is a cloud platform with the capabilities of computing, networking, storage, security, and the like at an edge location.
The network system 100 of the present embodiment may be regarded as an edge cloud network system, corresponding to a central cloud or a conventional cloud computing platform. The edge cloud is a relative concept, and the edge cloud is a cloud computing platform relatively close to a terminal, or is different from a central cloud or a traditional cloud computing platform, the central cloud or the traditional cloud computing platform can comprise a data center with large resource scale and concentrated position, and the edge cloud node covers a wider network range, so that the edge cloud node has the characteristic of being closer to the terminal, the resource scale of a single edge cloud node is smaller, but the number of the edge cloud nodes is large, and a plurality of edge cloud nodes form a component part of the edge cloud in the embodiment. The terminal in this embodiment refers to a demand end of a cloud computing service, and may be, for example, a terminal or a user end in the internet, or a terminal or a user end in the internet of things. An edge cloud network is a network built based on the infrastructure between a central cloud or a conventional cloud computing system and terminals. Wherein the network system 100 comprises at least one edge cloud node 102, each edge cloud node 102 comprising a series of edge infrastructures including, but not limited to: distributed Data Center (DC), wireless room or cluster, operator's communication network, core network devices, base stations, edge gateways, home gateways, computing devices and/or storage devices, and the like, and corresponding network environments, and the like. Here, the location, capabilities, and contained infrastructure of the different edge cloud nodes 102 may or may not be the same.
The network system 100 of the embodiment, in combination with a central network such as a central cloud or a traditional cloud computing platform and a terminal, may form a network architecture of "cloud edge end three-body collaboration", in which tasks such as network forwarding, storage, calculation and/or intelligent data analysis may be placed in each edge cloud node 102 in the network system 100 for processing, and since each edge cloud node 102 is closer to the terminal, response delay may be reduced, pressure of the central cloud or the traditional cloud computing platform may be reduced, and bandwidth cost may be reduced.
How to reasonably schedule multiple edge cloud node resources, and how to manage multiple edge cloud nodes for cloud computing services with correct and stable logic, is an important challenge. In the network system 100 of the present embodiment, a central management and control device 101 is deployed, where the central management and control device 101 uses the edge cloud nodes 102 as management and control objects, and in aspects of resource scheduling, mirror image management, instance management, operation and maintenance, network, security, and the like, at least one edge cloud node 102 in the network system 100 is uniformly managed and controlled, so that cloud computing services are put into each edge cloud node 102 for processing. In deployment implementation, the central management and control device 101 may be deployed in one or more cloud computing data centers, or may be deployed in one or more traditional data centers, where the central management and control device 101 and at least one edge cloud node managed by the central management and control device may together form an edge cloud network, and this embodiment is not limited to this.
For one edge cloud node 102, various resources, such as computing resources of CPU, GPU, etc., memory, storage resources of hard disk, network resources of bandwidth, etc., may be provided externally. In addition, the edge Yun Jiedian 102 can also create corresponding instances from the mirror image, through which various cloud computing services are provided outside. The image is a basic file required for creating an instance in the edge cloud node, for example, may be an image file of an operating system, an application, or an operation configuration required for providing cloud computing service for a user, and may be a file manufactured according to a specific series of files and a certain format, which meets the computing deployment requirement of the edge cloud node. In addition, the image forms are various, and may be Virtual Machine (VM) image files, container (dock) image files, or application package files of various types, and the image forms may be related to a virtualization technology that needs to be used by the cloud computing service, which is not limited in this embodiment. Corresponding to the mirror image, the implementation form of the instance may be a virtual machine, a container, an application program, or the like.
In combination with the foregoing, in this embodiment, the central management and control device 101 may perform resource scheduling on at least one edge cloud node 102 according to resource requirements, or may perform mirror image management and distribution on at least one edge cloud node 102 according to mirror image requirements, or may, of course, perform resource scheduling on at least one edge cloud node 102 according to cloud computing service requirements, and provide mirror images for at least one edge cloud node 102. The cloud computing service requirements include resource requirements and mirror image requirements. Alternatively, the central controlling device 101 may provide a demand submission portal to the outside, which may be a web page, an application page, a command window, or the like. The role of the demand submitting portal is for the demand direction central control apparatus 101 to submit its own demand description information.
For the resource demander, the resource demand description information may be submitted to the central control apparatus 101 through the above-described demand submitting portal, the resource demand description information including: edge cloud node selection parameters and resource selection parameters; the edge cloud node selection parameters include scheduling domain and/or performance requirements of the edge cloud node, etc., and the resource selection parameters include resource type, number of resources, performance requirements of the resource device, etc. The central management and control device 101 may schedule resources for at least one edge cloud node according to the resource requirement description information. Optionally, the resource scheduling method includes: the central management and control equipment 101 determines a scheduled target edge cloud node and scheduled resource information in the target edge cloud node from at least one edge cloud node 102 of the network system 100 according to the resource demand description information; and controlling corresponding resource equipment in the target edge cloud node to allocate or reserve resources according to the resource information.
For the image demand party, the image demand description information can be submitted to the central management and control device 101 through the demand submitting entrance, and the image demand description information can point to an image to be used, can be the image itself, can also be identification information such as the name, ID and the like of the image, can also be some function description information for cloud computing service, and can reflect the required image. The central control equipment 101 can acquire the mirror image according to the mirror image demand description information; the image is provided to an edge cloud node in the network system 100, which needs the image, so that the edge cloud node creates a corresponding instance according to the image, and the instance provides corresponding cloud computing service to the outside.
For the cloud computing service demander, service demand description information can be submitted to the central control device 101 through the above-mentioned demand submitting entrance, where the service demand description information includes resource demand description information and mirror demand description information. For the resource requirement description information and the mirror requirement description information, reference may be made to the foregoing descriptions, and details thereof will not be repeated herein. It should be noted that, the resource requirement description information and the mirror image requirement description information in the service requirement description information may be submitted together or separately. The central management and control device 101 can schedule resources of at least one edge cloud node 102 in the network system 100 according to the service demand description information; the scheduled resources in the at least one edge cloud node 102 are mirrored to provide corresponding cloud computing services using the scheduled resources in the at least one edge cloud node.
For the detailed procedure of the above-mentioned resource scheduling and mirror image management and distribution, see the following embodiments, which are not described in detail herein.
In this embodiment, the central management and control device 101 may not only provide a mirror image for at least one edge cloud node 102 for the edge cloud node 102 to create a corresponding instance, but also may manage an instance in the at least one edge cloud node 102. Examples in the at least one edge cloud node 102 may be at least one, i.e., one or more. Examples of the edge cloud nodes may be created according to images provided by the central control device 101, may be created according to other images, or may be migrated from other edge cloud nodes or other systems, which is not limited. The instance in the at least one edge cloud node 102 may provide cloud computing services to a service demander, where the service demander may be any device, application, system, or another service that requires the cloud computing services provided using the instance in the edge cloud node. Taking the system as an example, the service demander may be, but is not limited to: an online video system, a risk management and control system, a client information management system, a data distribution system and the like. The central management and control device 101 may manage at least one instance of at least one edge cloud node 102, facilitating the instance providing cloud computing services for service requesters.
The central controlling device 101 may perform various controls on at least one instance, for example, at least one of upgrade, migration, shutdown, restart, and release, but not limited thereto. Example upgrades and migration are described in detail below.
Example upgrades:
in practical applications, it is possible to upgrade the image or the corresponding instance with the change of the service requirement or the update of the image version. The central managing and controlling device 101 performs upgrade and control on the instance mainly includes:
the central control device 101 determines an instance to be upgraded from at least one instance, and the instance to be upgraded may be one or more; and sending an upgrading request to the service demand side so that the service demand side can determine an upgrading strategy for the to-be-upgraded instance by combining the service condition on the to-be-upgraded instance. The upgrade request carries identification information of the to-be-upgraded instance, such as an ID, a name and the like of the to-be-upgraded instance, or an ID, a name and the like of a service corresponding to the to-be-upgraded instance, or information such as an ID, a name and the like of an image corresponding to the to-be-upgraded instance. After receiving the upgrade request, the service demander can determine an instance to be upgraded according to the upgrade request, and in combination with service conditions on the instance to be upgraded, for example, a service request on the instance to be upgraded, a response state of the service request, and the like, judge whether the instance to be upgraded is suitable for upgrading, what time is suitable for upgrading, what method is adopted for upgrading, and the like, so that an upgrade policy can be generated for the instance to be upgraded and returned to the central control equipment 101. The central control device 101 receives an upgrade policy sent by the service requiring party, and upgrades the instance to be upgraded according to the upgrade policy.
In an alternative embodiment, the service demander may determine when the instance to be upgraded may be upgraded in combination with the service situation on the instance to be upgraded, for example, the number of service requests (for short, stock service requests) that have been received and have not yet been completed, whether there is a new service request (incremental service request), and so on, that is, the upgrade policy may include the upgrade time. If the stock service requests on the instance to be upgraded are all responded and incremental service requests are not available, in this case, the service request for upgrading the instance to be upgraded is not interrupted and the user experience is not affected, and the instance to be upgraded is considered to be upgraded. For the service demander, when the to-be-upgraded instance is considered to be upgraded, an upgrade notification can be returned to the central control device 101, wherein the upgrade notification carries time information for indicating the central control device 101 to upgrade the to-be-upgraded instance after receiving the upgrade notification, and the mode of carrying the time information by the upgrade notification can be explicit or implicit. For the central control device 101, an upgrade to an instance to be upgraded may be performed after receiving the upgrade notification.
Of course, in addition to the above manner, the service demander may also estimate a suitable upgrade time in combination with the service situation on the instance to be upgraded, and send the upgrade time to the central management and control device 101 with the upgrade notification. After receiving the upgrade notification, the central control device 101 obtains an upgrade time from the upgrade notification, and starts to upgrade the instance to be upgraded at the upgrade time.
The upgrade policy may include an upgrade time determined by the service demander in conjunction with the traffic conditions on the instance to be upgraded. Of course, the upgrade policy may not include upgrade time, and the upgrade time may be determined by the central control apparatus 101 according to the status of the instance to be upgraded, the load condition of the central control apparatus 101, and other factors. In addition, the upgrade policy may include an upgrade method, where the upgrade method refers to a method adopted to upgrade an instance to be upgraded, and may be determined by a service demander in combination with a service situation on the instance to be upgraded. The upgrade method is different according to the different image types. If the upgrade policy includes an upgrade time, the central control device 101 may start upgrading the instance to be upgraded at the upgrade time specified in the upgrade policy; if the upgrade policy includes an upgrade method, the central management and control device 101 may upgrade the instance to be upgraded by adopting the upgrade method specified in the upgrade policy; if the upgrade policy includes an upgrade time and an upgrade method, the central management and control device 101 may use the upgrade method specified in the upgrade policy to start upgrading the instance to be upgraded at the upgrade time specified in the upgrade policy.
Optionally, the upgrade to an instance may be initiated by the central management and control device 101. For example, the central control device 101 may monitor version information of an image corresponding to each instance, and when a new version of the image is found, may determine that an instance corresponding to the new version of the image needs to be updated; or, the running state, life cycle and other information of each instance can be monitored, and when problems such as loopholes, instability, incomplete functions, overlarge consumption of CPU or memory resources and the like occur in the running process of the instance are found, the instance with the problems can be determined to need to be updated.
Optionally, the upgrading of the instance may also be initiated by the service demander. For example, when an instance needs to be upgraded according to a service requirement, the service requirement party may send upgrade description information to the central control device 101, where the upgrade description information includes instance filtering conditions, and based on the instance filtering conditions, an instance to be upgraded may be filtered out of a plurality of instances. The instance filtering condition may be identification type information of the instance to be upgraded, for example, an ID and a name of the instance to be upgraded, or an ID and a name of an image corresponding to the instance to be upgraded, or an ID and a name of a service corresponding to the instance to be upgraded, which may determine the instance to be upgraded. Alternatively, if all the instances need to be upgraded, the instance filtering condition may also be identification information indicating that all the instances are upgraded, for example, "all", "1", etc., and the identification information may be flexibly set. For the central control device 101, upgrade description information sent by a service requiring party can be received, an instance filtering condition is obtained from the upgrade description information, and according to the instance filtering condition, an instance to be upgraded is determined from at least one instance; then sending an upgrade request to a service demand side to request the service demand side to combine the service condition on the instance to be upgraded to determine an upgrade strategy for the upgrade instance; after the service demand side returns the upgrade policy of the to-be-upgraded instance, the to-be-upgraded instance can be upgraded according to the upgrade policy.
The upgrading of the instance to be upgraded mainly means that: and shutting down the instance to be upgraded, updating the instance to be upgraded according to the image of the corresponding version (generally referred to as a new version), and restarting the instance after updating. The image version required for upgrading the instance to be upgraded may be determined by the central control device 101, for example, the latest version of the corresponding image may be used as the image version required for upgrading, or may be specified by the service demander. Alternatively, the service demander may provide the update description information to the central management device 101 with the image version required for the update, for example, the update description information may include information such as "update image version a to image version B for all or a specified instance". Based on this, the central management and control device 101 may obtain an image version required for upgrade from the upgrade description information, and then upgrade the instance to be upgraded by using an image corresponding to the image version according to the upgrade policy. When the instance to be upgraded is completely upgraded, the instance upgrading process is finished.
Instance migration:
in practical applications, migration of instances is required in some cases. For example, in the event that an entire edge cloud node fails or is unavailable, instances in that edge cloud node need to be migrated into other edge cloud nodes. For another example, in the event that a physical machine carrying an instance fails or is down, the instance on that physical machine needs to be migrated to other physical machines. As another example, some or some instances may need to be migrated from one edge cloud node to other edge cloud nodes because of traffic needs. For another example, in the case where resource merge is required, migration of one or some instances is also required. Under the control of the central control device 101, an instance in the edge cloud node may be migrated, where the migration process mainly includes:
The central controlling device 101 determines an instance to be migrated from the at least one instance. The instance to be migrated may be one or more; if the number of the to-be-migrated instances is multiple, the multiple to-be-migrated instances can be deployed in the same edge cloud node or in different edge cloud nodes.
In some application scenarios, the central management and control device 101 may monitor a state of at least one instance deployed in at least one edge cloud node 102, and obtain, according to the state of at least one instance, a failed instance and/or an instance having a specified event in operation as an instance to be migrated, thereby migrating the instance to be migrated. The failed instance refers to an instance that cannot normally run, for example, an instance on a physical machine that is down, an instance that is down itself, and the like, where the instance needs to be migrated so as to be able to continue to provide cloud computing service for a service demander. The specified events mainly refer to events which can still normally run after some examples appear, and the specified events can be flexibly set according to application requirements, so that the specified events are not limited. For example, the specified events may be early warning or alarm events, and the examples are still operational (i.e. not failed) although some early warning or alarm events occur, but have hidden trouble, and can be timely migrated before failure, so as to avoid the problems of service interruption and the like caused by failure. In addition, the central management and control device 101 maintains information of each edge cloud node and information of each instance deployed in each edge cloud node, based on which, an edge cloud node to which an instance to be migrated belongs can be determined, and for convenience of description and distinction, an edge Yun Jiedian to which the instance to be migrated belongs before migration is denoted as a first edge cloud node.
In other application scenarios, as time is accumulated, some resource fragments appear in the edge cloud node, or an instance with larger resource specification needs to be deployed, but the available resources meeting the resource specification requirements may not be available on the resource equipment in the edge cloud node, and under these conditions, the resources in the edge cloud node can be merged through instance migration, so that the resource fragments can be fully utilized, further, resource blocks with larger specification are produced, and the improvement of the resource utilization rate is facilitated. Based on this, the central controlling device 101 may determine an instance to be migrated from at least one instance according to the resource merging requirement, and further migrate the instance to be migrated. The resource merging is mainly a process of integrating resource fragments through instance migration, and after integration, the resource fragments in the edge cloud nodes are reduced or even absent, which is beneficial to improving the resource utilization rate in the edge cloud nodes. It should be noted that the resource merging requirement may be system level or node level. The system-level resource merging refers to integrating resource fragments in the whole network system through instance migration from the dimension consideration of the whole network system; node-level resource merging refers to integrating resource fragments in edge cloud nodes through instance migration from the dimension consideration of the edge cloud nodes.
Alternatively, the resource merge requirement may be provided by the service demander. For example, when a service demander needs to deploy a new instance, if available resources on each resource device in an edge cloud node serving the service demander are insufficient to carry the new instance, migration of the instance in the edge cloud node may be required to implement resource integration, so as to provide sufficient resources for the new instance. Alternatively, the resource merge requirement may be a periodic behavior of the resource scheduling module of the central management and control device 101. For example, the resource scheduling module of the central management and control device 101 periodically performs resource fragmentation checking, and when the fragmentation rate reaches a certain threshold and the instance migration can be performed, integrates the resource fragments in each edge cloud node, so as to improve the resource utilization rate in the edge cloud node.
The resource merging requirement comprises information related to resource merging. For example, the resource merging requirement may include information of an instance that needs to be migrated for achieving the resource merging purpose, based on which an instance to be migrated may be directly determined according to the resource merging requirement. For another example, the resource merging requirement may include information of an edge cloud node that needs resource merging. Based on the above, according to the resource merging requirement, the edge cloud node needing resource merging can be determined, and in the embodiment, the edge cloud node needing resource merging is called a first edge cloud node; and then, the to-be-migrated instance can be determined by combining the available resources remained on each resource device in the first edge cloud node and the resources required by each instance in the first edge cloud node.
Regardless of the application scenario, after determining the instance to be migrated, the central control device 101 may determine whether the first edge cloud node to which the instance to be migrated belongs meets an intra-node migration condition; if the first edge cloud node meets the intra-node migration condition, performing intra-edge cloud node migration on the instance to be migrated; and if the first edge cloud node does not meet the intra-node migration condition, migrating the instance to be migrated across the edge cloud node.
Optionally, the central controlling device 101 may determine whether the first edge cloud node is currently in an available state; if the first edge cloud node is currently in an available state, judging whether available resources of the first edge cloud node are enough to bear an instance to be migrated; if the available resources of the first edge cloud node are enough to bear the instance to be migrated, determining that the first edge cloud node meets the intra-node migration condition; if the first edge cloud node is in an unavailable state currently or available resources of the first edge cloud node are insufficient to bear an instance to be migrated, determining that the first edge cloud node does not meet the intra-node migration condition. In the present embodiment, migration of instances is divided into two types: intra-node migration and cross-node migration. The available resources of the first edge cloud node mainly refer to available resources on each station of resource equipment in the first edge cloud node; accordingly, determining whether the available resources of the first edge cloud node are sufficient to carry the instance to be migrated mainly refers to determining whether the available resources exist in the first edge cloud node to be sufficient to carry the resource device of the instance to be migrated.
It should be noted that, in the resource merging scenario, the migration of the instance to implement the resource merging is mainly intra-node migration, and of course, may also be cross-node migration. Optionally, in determining the instance to be migrated according to the available resources remaining on each resource device in the first edge cloud node and the resources required by each instance in the first edge cloud node, the resource device to which the instance to be migrated needs to be migrated may also be determined, where the resource device is a resource device where the available resources remaining in the first edge cloud node may carry the instance to be migrated. Of course, if there are no remaining available resources in the first edge cloud node that can carry the resource device of the instance to be migrated, the cross-node migration may be performed for the instance to be migrated. In view of the purpose of resource merging, in the process of performing cross-node migration on the instance to be migrated, preferentially migrating the instance to be migrated to the resource equipment which is already used in other edge cloud nodes and can bear the instance to be migrated by the remaining available resources; further, under the condition that a plurality of resource devices which are used and the rest available resources can bear the instance to be migrated are available, the resource devices with high matching degree between the rest available resources and the resources needed by the instance to be migrated can be selected based on the principle of minimum resource fragments, and fewer resource fragments or no resource fragments are generated as much as possible.
For intra-node migration: optionally, the continuity of the cloud computing service provided by the instance may be ensured by a thermo-migration technique, which may be referred to in the prior art and will not be described herein.
For cross-node migration: the central management and control device 101 may select a second edge cloud node from the at least one edge cloud node, where the second edge cloud node is different from the first edge cloud node, and available resources in the second edge cloud node are sufficient to carry the instance to be migrated, that is, sufficient resources are available; and migrating the instance to be migrated to a second edge cloud node, and sending the attribute information of the instance to be migrated in the second edge cloud node to a service demand party so that the service demand party can conduct service scheduling on the instance to be migrated based on the attribute information. The attribute information of the to-be-migrated instance in the second edge cloud node refers to information required by the outside (e.g., a service demander or a third party authorized by the service demander) to perform service scheduling on the to-be-migrated instance after the to-be-migrated instance is migrated to the second edge cloud node, and may include, for example, but not limited to: and the second edge cloud node is located in the region, the operator information and/or public network IP and other information. Taking a service demand party as an example, according to the region and the operator information where the second edge cloud node is located in the attribute information, and combining the information such as the operator information and the region of the network used by the terminal initiating the service request, whether the service request is distributed to the to-be-migrated instance in the second edge cloud node can be judged; if the service request is determined to be distributed to the to-be-migrated instance in the second edge cloud node, the public network IP in the attribute information can be provided for the terminal through the scheduling capability of the system, and the request of the terminal can access to the to-be-migrated instance in the second edge cloud node, so that the purpose of scheduling the service request of the terminal to the to-be-migrated instance in the second edge cloud node is achieved.
Alternatively, in selecting the second edge cloud node, the following manner may be employed, but is not limited to:
mode 1: according to the distance between other edge cloud nodes and the first edge cloud node, selecting an edge cloud node with the distance from the first edge cloud node smaller than a set distance threshold value, or selecting an edge cloud node closest to the first edge cloud node, or optionally selecting one edge cloud node from N edge cloud nodes closest to the first edge cloud node as a second edge cloud node. In the mode 1, the second edge cloud node is closest to or closer to the first edge cloud node, so that data transmission time can be saved, and migration efficiency can be improved. Optionally, the distance between the other edge cloud nodes and the first edge cloud node may be an average distance between the other edge cloud nodes and the first edge cloud node, or may be a distance between the centers of the other edge cloud nodes and the first edge cloud node, or may be a distance between the closest outer edge of the other edge cloud nodes and the first edge cloud node, or the like, which may be adaptively defined according to requirements.
Mode 2: an edge cloud node with relatively sufficient bandwidth resources can be selected from the other edge cloud nodes according to the bandwidth resources of the other edge cloud nodes, for example, an edge Yun Jiedian with the largest bandwidth resource or with the bandwidth resource larger than a set bandwidth threshold value or with lower bandwidth utilization rate is selected as the second edge cloud node. In the mode 2, the bandwidth resources of the second edge cloud node are sufficient, so that the data transmission rate can be improved, and the migration efficiency can be improved.
Mode 3: according to the current load conditions of other edge cloud nodes, an edge cloud node with relatively lighter load can be selected, for example, an edge Yun Jiedian with the smallest load or with the load smaller than a set load threshold is selected as a second edge cloud node. In the mode 3, the load of the second edge cloud node is lighter, enough resources can be provided, and the migration of the instance can be processed in time, so that the migration efficiency is improved.
Optionally, when migrating the instance to be migrated to the second edge cloud node, the central management and control device 101 may reserve or allocate resources for the instance to be migrated in the second edge cloud node according to the resource requirement of the instance to be migrated; and after the resource reservation or allocation is successful, migrating the instance to be migrated to the reserved or allocated resource in the second edge cloud node. For example, the information such as the type of the resource, the amount of the resource and/or the performance requirement of the resource equipment required by the instance to be migrated can be determined according to the resource requirement of the instance to be migrated, and the resource reservation or the allocation can be performed in the second edge cloud node according to the information, so that the resource guarantee can be provided for the successful migration of the instance. Regarding the process of the central controlling device 101 performing resource reservation or allocation for the instance to be migrated in the second edge cloud node, the content of the subsequent resource scheduling portion may be referred to, and will not be described herein.
Optionally, if the instance to be migrated is a failed instance, i.e. an instance that cannot operate normally, the central controlling device 101 may also notify the service demander of the migration event, so that the service demander may perform an appropriate response action, such as updating information of the instance in the service demander, or performing a disaster recovery response for a downtime condition in the process of migrating the instance. Further, the attribute information of the instance to be migrated in the second edge cloud node can be provided to the service demander together in the process of notifying the migration event. Of course, after the to-be-migrated instance is successfully migrated to the second edge cloud node, attribute information of the to-be-migrated instance in the second edge cloud node may be provided to the service demander.
Optionally, if the to-be-migrated instance is an instance in which a specified event occurs in the operation process, that is, an instance in which the specified event occurs but still can operate normally, the central control device 101 may further send a migration request to the service demander, so that the service demander determines a migration policy for the to-be-migrated instance in combination with the service condition on the to-be-migrated instance; and receiving a migration strategy sent by the service demand side, and migrating the instance to be migrated to the second edge cloud node according to the migration strategy. The migration policy mainly includes at least one of information of whether to migrate, migration time and migration mode. Alternatively, the service demander may determine when to migrate according to the number of the stock service requests and the incremental service requests on the to-be-migrated instance and the response state, for example, may determine to migrate the instance if the stock service requests on the to-be-migrated instance have been responded, and the incremental service requests are not more.
Further alternatively, the central managing and controlling device 101 may send the attribute information of the instance to be migrated in the second edge cloud node to the service demander together with the above-mentioned migration request. Or, after the to-be-migrated instance is successfully migrated to the second edge cloud node, the attribute information of the to-be-migrated instance in the second edge cloud node may be provided to the service demander.
Further optionally, if the to-be-migrated instance is an instance that has a specified event but still can operate normally, in the migration process, the to-be-migrated instance can continue to operate in the first edge cloud node, so that the service request in the migration process can be continuously scheduled to the to-be-migrated instance in the first edge cloud node, and service continuity is ensured. And under the condition that the to-be-migrated instance is successfully migrated to the second edge cloud node, and the service demander ensures that new service requests are all scheduled to the second edge cloud node, and the service requests in the first edge cloud node are gradually reduced, and finally no new service request exists, namely, no service request exists on the to-be-migrated instance running in the first edge cloud node, the central management and control equipment can release the to-be-migrated instance in the first edge cloud node. Optionally, after determining that there are no more service requests on the to-be-migrated instance running in the first edge cloud node, the service demander may send a release notification to the central management and control device 101 after determining that there are neither stock service requests nor incremental service requests; the central management and control device 101 receives a release notification sent by the service demander, and releases the instance to be migrated running in the first edge cloud node according to the release notification. Further, the central managing and controlling device 101 may synchronize the running state of the instance to be migrated running in the first edge cloud node to the instance to be migrated in the second edge cloud node.
Further, no matter what kind of instance is to be migrated, the migration of the instance to be migrated to the second edge cloud node is mainly to control a process that corresponding resource equipment in the second edge cloud node creates the instance to be migrated on reserved or allocated resources according to a mirror image or an instance snapshot corresponding to the instance to be migrated. Optionally, the central managing and controlling device 101 may provide an application image or an instance snapshot corresponding to the instance to be migrated to the corresponding resource device in the second edge cloud node, so that the corresponding resource device in the second edge cloud node creates the instance to be migrated on the reserved or allocated resource according to the application image or the instance snapshot, but is not limited thereto.
Optionally, the central control device 101 of the present embodiment may encapsulate its own control functions such as instance upgrade, instance migration, and the like into a series of application programming interfaces (Application Programming Interface, APIs) and open to the service demander for use. These open APIs are referred to as open APIs (openapis) through which central controlling device 101 may interact with service requesters.
It should be noted that, in the network system 100, the central controlling device 101 may directly control and schedule the at least one edge cloud node 102, but is not limited thereto. As shown in fig. 1b, in the network system 100, an edge management and control device 103 is included in addition to the central management and control device 101 and the at least one edge cloud node 102. The number of the edge management and control devices 103 may be one or more. In addition, edge management and control device 103 may be deployed in one or more edge cloud nodes 102. In an alternative embodiment, as shown in fig. 1b, edge management and control devices 103 are deployed in each edge cloud node 102. Further, each edge cloud node includes one or more resource devices, and optionally, the edge management and control device 103 may be deployed on one resource device in a centralized manner, or may be deployed on multiple resource devices in a decentralized manner. In addition, each edge cloud node may include one or more proprietary devices in addition to the resource devices, where the edge management device 103 may be deployed centrally on one proprietary device or distributed across multiple proprietary devices. Where proprietary devices refer to physical devices used to deploy edge management devices 103, as opposed to resource devices. In addition, the edge management and control device 103 may also be deployed with the center management and control device 101, which is not limited herein. In addition, the central management and control device 101 may be deployed in one or more cloud computing data centers or traditional data centers, and may also be deployed in an edge cloud network with at least one edge cloud node.
The central management and control device in this embodiment may be a logic device with capabilities of resource scheduling, mirror image management, etc., where these functions may be implemented by deploying one physical machine or virtual machine, or may be deployed in a decentralized manner on multiple physical machines or virtual machines. Of course, the central control device of the embodiment may also be one or more physical devices with capabilities of resource scheduling, mirror image management, and the like. The embodiment of the present application is not limited to the implementation structure of the central control device 101, and any device structure with the above-mentioned capabilities is applicable to the embodiment of the present application.
Similar to the central management and control device 101, the edge management and control device 103 may also be a logic device, where the capability may be implemented on one physical machine (for example, a resource device or a proprietary device in an edge cloud node) or a virtual machine, or may be distributed and deployed on multiple physical machines (for example, a resource device or a proprietary device in an edge cloud node) or virtual machines. Of course, the edge management device may also be one or more physical devices with corresponding capabilities. The implementation structure of the edge management and control device 103 is not limited, and any device structure with corresponding capability is applicable to the embodiments of the present application.
In this embodiment, the edge management and control device 103 may assist, cooperate with the central management and control device 101 to manage and schedule at least one edge cloud node 102. With the assistance of the edge management and control device 103, the central management and control device 101 can manage and schedule at least one edge cloud node 102 more conveniently and efficiently, so as to achieve the purpose of fully utilizing edge resources.
Wherein, a secure, encrypted communication channel can be established between the central management and control device 101 and the edge management and control device 103, and interaction can be performed based on the communication channel. The communication channel includes a control interface and a data interface, and the central control device 101 performs interaction of a control plane and a data plane with the edge control device 103 based on the control interface and the data interface, so as to complete scheduling and control of the edge cloud node 102. The data interface is used for data transmission between the central control device 101 and the edge control device 103. The control interface has, but is not limited to, the following functions:
1. resource scheduling capability: the central management and control device 101 can perform resource scheduling on edge cloud nodes from multiple dimensions through a control interface (which can be simply called a resource scheduling interface) with resource scheduling capability, and the edge cloud nodes are objects for performing resource scheduling by the central management and control device 101;
2. Mirror management and distribution capabilities: the central management and control device 101 can provide the mirror image to the edge Yun Jiedian through a control interface (simply referred to as a mirror image management interface) with mirror image management and distribution capability, so that an edge cloud node can create a corresponding instance according to the received mirror image, and provide corresponding cloud computing service through the instance;
3. operation and maintenance management capability: the central management and control device 101 performs operation and maintenance management on the edge cloud nodes through a control interface (abbreviated as an operation and maintenance management interface) with operation and maintenance management capability, and the operation and maintenance management includes but is not limited to: applications, virtualization software, etc. in the edge cloud nodes are managed, and the state, resource usage, infrastructure, etc. of the instances are monitored.
Corresponding to the capabilities of the control interface described above, the central control apparatus 101 of the present embodiment has, but is not limited to, the following functions:
1. the edge cloud nodes can be scheduled according to service demand description information, such as the specification of cloud computing service, the area where the cloud computing service needs to be deployed, the distribution of an operator network, network delay, load conditions, bandwidth cost, required resource types and/or performance requirements of resource equipment, and the like;
2. the method comprises the steps that a mirror image required by cloud computing service can be acquired, and the mirror image is provided for corresponding resource equipment in an edge cloud node for configuration installation, so that the corresponding resource equipment can create corresponding examples to provide the cloud computing service;
3. Edge cloud nodes may be operation-and-maintenance controlled, including but not limited to: and controlling the states, resource consumption, infrastructure conditions and the like of the applications, the virtualized components and the instances in the edge cloud nodes, and realizing remote operation and maintenance, log management and the like.
In addition to the above functions, the central control device may also have other functions, such as a security function, involving security of the central control device, security of links between the central control device and the edge control device and between the edge cloud nodes, security of the edge cloud nodes; is responsible for maintaining networking information in a network system and the like.
In the network system 100, at least one edge cloud node 102 may form a resource pool, and each edge cloud node 102 serves as a scheduling object to provide various resources or cloud computing services under the scheduling of the central management and control device 101. The central management and control device 101 and the edge management and control device 102 cooperate with each other, so that resource scheduling can be performed on at least one edge cloud node 102, mirror image management and distribution can also be performed on at least one edge cloud node 102, and of course, not only resource scheduling can be performed on at least one edge cloud node 102, but also mirror images can be provided for at least one edge cloud node 102. In addition to resource scheduling and image management and distribution for edge cloud nodes 102, managing instances in edge cloud nodes 102 is also a problem that network system 100 needs to solve, and successfully solving this problem is also the basis for "putting cloud computing into edge cloud nodes closer to the terminal for processing". To this end, the central management and control device 101 and the edge management and control device 103 cooperate with each other, and may further manage an instance in the at least one edge cloud node 102, such as at least one of upgrade, migration, shutdown, restart, and release.
Optionally, in the process of upgrading the to-be-upgraded instance, the edge management and control device 103 may assist the central management and control device 101 to upgrade the to-be-upgraded instance by using the image corresponding to the image version according to the upgrade policy. For example, the central controlling device 101 may send an image corresponding to the upgrade policy and the image version to the edge controlling device 103, and the edge controlling device 103 upgrades the instance to be upgraded by using the image corresponding to the image version according to the upgrade policy. Further, if the edge management and control device 103 is disposed in each edge cloud node, the central management and control device 101 may send the image corresponding to the upgrade policy and the image version to the edge management and control device 103 in the edge cloud node to which the to-be-upgraded instance belongs, and the edge management and control device 103 in the edge cloud node to which the to-be-upgraded instance belongs uses the image corresponding to the image version to upgrade the to-be-upgraded instance according to the upgrade policy. For the edge management and control device 103, an upgrade method indicated by an upgrade policy may be adopted, and at an upgrade time indicated by the upgrade policy, an image corresponding to an image version is provided to a resource device where an instance to be upgraded is located, and the resource device upgrades the instance to be upgraded by using the image. For other descriptions of upgrading the instance to be upgraded, reference may be made to the descriptions in the foregoing embodiments, and no further description is given here.
Optionally, in the process of migrating the to-be-migrated instance, the edge management and control device 103 may assist the central management and control device 101 to control the corresponding resource device in the second edge cloud node to reserve or allocate resources for the to-be-migrated instance. The central management and control device 101 may determine, according to the resource requirement of the instance to be migrated, the scheduled resource information in the second edge cloud node, provide the resource information to the edge management and control device 103, and control, by the edge management and control device 103, the corresponding resource device in the second edge cloud node to reserve or allocate resources for the instance to be migrated according to the resource information. Further, if the edge management and control device 103 is disposed in the second edge cloud node, the central management and control device 101 may provide resource information to the edge management and control device 103 in the second edge cloud node, and the edge management and control device 103 in the second edge cloud node controls, according to the resource information, the corresponding resource device in the second edge cloud node to reserve or allocate resources for the instance to be migrated.
In addition, in the process of migrating the instance to be migrated, the edge management and control device 103 may also assist the central management and control device 101 to migrate the instance to be migrated to the resource reserved or allocated by the corresponding resource device in the second edge cloud node. The central management and control device 101 may send a migration instruction to the edge management and control device 103, where the migration instruction instructs the edge management and control device 103 to obtain a mirror image or an instance snapshot corresponding to the instance to be migrated and provide the mirror image or the instance snapshot to corresponding resource devices in the second edge cloud node, so that the corresponding resource devices in the second edge cloud node create the instance to be migrated on the reserved or allocated resources according to the mirror image or the instance snapshot. Further, if the edge management and control device 103 is deployed in the second edge cloud node, the central management and control device 101 may send a migration instruction to the edge management and control device 103 in the second edge cloud node, instruct the edge management and control device 103 in the second edge cloud node to obtain a mirror image or snapshot corresponding to the instance to be migrated and provide the mirror image or snapshot to corresponding resource devices in the second edge cloud node, so that the corresponding resource devices in the second edge cloud node create the instance to be migrated on the reserved or allocated resources according to the mirror image or snapshot.
Alternatively, if the instance migration process uses snapshots, the manner in which the edge management and control device 103 obtains the snapshots may be different depending on the storage manner of the snapshots. If the snapshot is stored in the first edge cloud node, whether the state of the first edge cloud node is available or not is checked, if the first edge cloud node is in an unavailable state, the snapshot is not suitable for instance migration, and the mirror image is needed to be used for instance migration instead; if the first edge cloud node is in an available state, the edge management and control device may obtain a snapshot from the first edge cloud node. If the snapshots are stored in other edge cloud nodes in a scattered manner, the process of taking the snapshots is irrelevant to the state of the first edge cloud node, and the edge management and control device can take the snapshots from the other edge cloud nodes under the condition that the other edge cloud nodes are in an available state. After the edge management and control equipment acquires the snapshot, the snapshot copy is provided for corresponding resource equipment in the second edge cloud node, and the corresponding resource equipment creates an instance to be migrated through the snapshot. The data saved during snapshot can be restored through the snapshot creation instance.
Optionally, if the instance migration process uses a mirror image, when the edge management and control device 103 obtains the mirror image, it may first determine whether the mirror image corresponding to the instance to be migrated is stored in the second edge cloud node. If the second edge cloud node has the corresponding mirror image, the edge management and control equipment can directly provide the corresponding mirror image in the second edge cloud node for corresponding resource equipment in the second edge cloud node, so that the corresponding resource equipment can create an instance to be migrated through the mirror image. If the second edge cloud node does not have the corresponding mirror image, the edge management and control device can request the corresponding mirror image from the central management and control device; the central control equipment can acquire the mirror image from the mirror image library and provide the mirror image for the edge control equipment, or instruct the edge control equipment to acquire the mirror image from other edge cloud nodes storing the corresponding mirror image; the edge management and control equipment is provided for corresponding resource equipment in the second edge cloud node after obtaining the corresponding mirror image, and the corresponding resource equipment is provided for creating an instance to be migrated through the mirror image. The process that the central management and control device instructs the edge management and control device to obtain the image from the other edge cloud nodes storing the corresponding image may refer to the description in the related embodiments of image management and distribution, which is not described herein.
In the following embodiments of the present application, various other functions achieved by the central control device or the cooperation of the central control device and the edge control device will be described.
Resource scheduling function:
the central management and control device may schedule resources of at least one edge cloud, mainly determining a target edge cloud node that may be scheduled and resource information that may be scheduled in the target edge cloud node from at least one edge cloud node 102 in the network system 100 according to service requirement description information; and sending the resource information to the edge management and control equipment 103, so that the edge management and control equipment 103 controls corresponding resource equipment in the target edge cloud node to perform resource allocation or reservation. Optionally, the number of the target edge cloud nodes may be specified by a user, or may be determined autonomously by the resource central management and control device according to the service requirement description information, and may be one or a plurality of target edge cloud nodes. The service requirement description information can be directly submitted by the service requirement party, or can be extracted or calculated from the service related information submitted by the service requirement party. The service demander may be a user, or may be an application, a physical machine, or another service that requires a certain service, or the like.
The resource scheduling functions described herein mainly include, but are not limited to, two aspects of selection of edge cloud nodes and scheduling of resources within edge cloud nodes. The method comprises the steps of determining scheduled resource information in a target edge cloud node and providing the resource information, wherein the resource scheduling in the edge cloud node is specifically embodied in the operation of determining the scheduled resource information in the target edge cloud node and providing the resource information, and the main purpose is to distribute cloud computing services to final basic resources, such as resource equipment of a server and the like, on the granularity of each edge cloud node. The central management and control equipment can maintain the information of resources contained in each edge cloud node, and the information is used as a basis of resource scheduling.
Optionally, the service requirement description information includes an edge cloud node selection parameter and a resource selection parameter. The edge cloud node selection parameters refer to parameters required for selecting a target edge cloud node; the resource selection parameter refers to information required to select a resource scheduled within an edge cloud node. Based on the information, the central management and control equipment can analyze the edge cloud node selection parameters and the resource selection parameters from the service demand description information; and determining a scheduled target edge cloud node from at least one edge cloud node according to the edge cloud node selection parameters, and determining scheduled resource information in the target edge cloud node according to the resource selection parameters.
For example, qoS requirements of the scheduling domain and/or cloud computing service may be included in the service requirement description information, and these parameters may be used as edge cloud node selection parameters. Wherein the dispatch domain points to an area where cloud computing services need to be deployed, which determines the geographic location of edge cloud nodes that should be dispatched. QoS requirements of a cloud computing service may include requirements of the cloud computing service for network latency, load conditions, and/or bandwidth costs, among others. Based on the above, the central management and control device can select the edge cloud node capable of meeting the requirements of the scheduling domain and/or the QoS as the target edge cloud node according to the requirements of the scheduling domain and/or the QoS of the cloud computing service by combining the geographic position and the resource remaining amount of at least one edge cloud node.
For example, the central control device may select, according to the scheduling domain, an edge cloud node pointed by the scheduling domain as a target edge cloud node in combination with a geographic location of at least one edge cloud node. Or, the central control device may further select, as the target edge cloud node, an edge cloud node that meets the requirements of network delay, load condition and/or bandwidth cost from the edge cloud nodes according to QoS requirements of the cloud computing service, for example, requirements of network delay, load condition and/or bandwidth cost. Of course, the central management and control device may also select, as the target edge cloud node, an edge cloud node capable of meeting the requirements of the scheduling domain and the QoS simultaneously in combination with the geographic location and the resource remaining amount of at least one edge cloud node according to the requirements of the QoS of the scheduling domain and the cloud computing service.
The service requirement description information may include, in addition to information including QoS requirements of the scheduling domain and/or the cloud computing service, parameters such as a resource type, a resource number, and/or performance of the resource device required by the cloud computing service, which may be used as resource selection parameters. Based on this, the central management and control device may determine, after determining the target edge cloud node, the scheduled resource information in the target edge cloud node according to the resource selection parameter. The resource information here may include: the information such as the resource type, the resource quantity and/or the performance requirement on the resource equipment is convenient for the edge management and control equipment to control the corresponding resource equipment in the target edge cloud node to allocate or reserve the resource according to the information. For example, resource types may include, but are not limited to: and the CPU, the GPU and other computing resources, memory, hard disk and other storage resources, bandwidth resources and other resource types. Taking CPU resources as an example, the number of the resources can be 12 CPUs, 24 CPUs and the like, taking memory resources as an example, the number of the resources can be 16G memory, 32G memory and the like; taking bandwidth resources as an example, the number of resources may be 1M bandwidth, 10M bandwidth, etc.
Optionally, the central management and control device may further have a function of computing power arrangement, where computing power arrangement is for a relatively complex application scenario, and binds multiple cloud computing services together as a minimum resource requirement unit, so that in a resource scheduling process, multiple cloud computing services bound together may be taken as a whole, and one or several edge cloud nodes may be selected for them, and resources may be provided for them together by the same or several edge cloud nodes. The computing power arrangement improves the diversity of resource scheduling, increases the flexibility of resource scheduling, and does not affect the whole flow of resource scheduling.
Mirror image management and distribution function:
the mirror image management function of the central management control equipment mainly aims at managing mirror images and providing required mirror images for edge cloud nodes. In this way, the edge cloud node may create instances on the respective resource devices according to the mirror image, and thereby provide the user with the desired cloud computing services from the created instances.
In practical applications, the scenarios that need to provide mirroring for edge cloud nodes are diverse. For example, in the event that a user (e.g., a service demander) submits service demand description information, the central management and control device may provide a corresponding mirror image for the target edge cloud node being scheduled. For another example, when the existing instance on the edge cloud node provides the cloud computing service for the user, the user may submit the capacity expansion requirement to the central control device when the user needs to perform service expansion, and in order to achieve the capacity expansion purpose, a corresponding mirror image needs to be provided for the edge cloud node that is providing the cloud computing service for the user at present, so that the edge cloud node creates a new instance based on the mirror image, thereby achieving the capacity expansion purpose. For convenience of description and distinction, in the following description, an edge Yun Jiedian for which mirroring is required is denoted as a third edge cloud node, which may be any edge cloud node in the network system, depending on an application scenario. The mirror image management function of the central control device is described below by taking the central control device as an example of providing a mirror image for the third edge cloud node.
When the mirror image needs to be provided for the third edge cloud node, the central control equipment can firstly determine a target mirror image which needs to be provided for the third edge cloud node; and then, providing the target image for the third edge cloud node so that the third edge cloud node can provide cloud computing services by utilizing the target image.
In the network system 100 of the present embodiment, a mirror library for storing mirrors in the system is maintained. The user may choose to use the images in the image library. For example, a mirror configuration interface may be provided to the user with a drop down menu that includes a number of mirrors available for user selection, which the user may select for his own use. Based on the above, when the mirror image needs to be provided for the third edge cloud node, the central control device can acquire the mirror image required by the third edge cloud node from the mirror image library, then provide the mirror image for the third edge cloud node, and open the use authority of the mirror image to the corresponding user. Optionally, the central management and control device may directly issue the target image to the third edge cloud node, or instruct the third edge cloud node to download the target image to the designated storage location.
In addition, the central control device can also maintain the corresponding relation between the issued image and the edge cloud node where the issued image is located. The corresponding relation can comprise the identification information of the issued mirror image and the identification information of the edge cloud node where the issued mirror image is located. Issued images refer to images that the central management and control device has provided (e.g., issued) to one or more edge cloud nodes; the edge cloud node where the issued image is located refers to the edge cloud node to which the issued image is provided. The same image may be provided (e.g., issued) to one edge cloud node or may be provided (e.g., issued) to multiple edge cloud nodes.
Based on the corresponding relation between the maintained issued mirror image and the edge cloud node where the issued mirror image is located, when the mirror image is required to be provided for the third edge cloud node, the central management and control equipment can also control the third edge cloud node to acquire the mirror image from other edge cloud nodes which already have the mirror image, the mirror image is not required to be directly provided for the third edge cloud node, the processing burden of the central management and control equipment can be reduced to a certain extent, and under the condition of reasonable control, the acquisition efficiency of the mirror image can also be improved.
In detail, when the mirror image needs to be provided for the third edge cloud node, the central management and control device may determine that the mirror image needs to be provided for the third edge cloud node, and in the embodiment of the present application, the mirror image needs to be provided for the third edge cloud node is recorded as a target mirror image for convenience of description and distinction; according to the information of the target image, matching is carried out in the corresponding relation between the maintained issued image and the edge cloud node where the issued image is located; if a fourth edge cloud node corresponding to the target image is matched in the corresponding relation, which means that the target image is already provided to the fourth edge cloud node, the target image at the fourth edge cloud node can be provided to the third edge cloud node; the number of the fourth edge cloud nodes can be one or a plurality of the fourth edge cloud nodes in the network system. For the third edge cloud node, a target image at the fourth edge cloud node may be acquired under the control of the central management and control device 101.
Here, in the case where the network system 100 includes the edge management and control device 103, the central management and control device may specifically send information of the fourth edge cloud node and the target image to the edge management and control device; the edge management and control device 103 provides the target image at the fourth edge cloud node to corresponding resource devices in the third edge cloud node according to the information of the fourth edge cloud node and the target image, so that the corresponding resource devices create an instance capable of providing cloud computing service according to the target image, and further provide the cloud computing service for the service demander. The information of the fourth edge cloud node may be any information capable of identifying the fourth edge cloud node, for example, may be information such as an ID, a name, or a geographic location of the fourth edge cloud node. The information of the target image may be any information capable of identifying the target image, for example, an ID, a name, or a number of the target image, or the like.
Further, in the case that the edge management and control devices 103 are disposed in the third edge cloud node and the fourth edge cloud node, the central management and control device 101 may specifically send the information of the fourth edge cloud node and the target image to the edge management and control device in the third edge cloud node, so that the edge management and control device in the third edge cloud node obtains the target image from the fourth edge cloud node through a communication channel between the edge management and control device in the fourth edge cloud node and provides the target image to the corresponding resource device in the third edge cloud node. For the edge management and control device 103 in the third edge cloud node, the information of the fourth edge cloud node and the target image sent by the central management and control device 101 can be received, the target image is obtained from the fourth edge cloud node through a communication channel between the information of the fourth edge cloud node and the edge management and control device in the fourth edge cloud node, and the target image is provided for corresponding resource devices in the third edge cloud node, so that the corresponding resource devices can create an instance capable of providing cloud computing service according to the target image, and further provide cloud computing service.
Still further, a process for the edge management and control device 103 in the third edge cloud node to obtain the target image from the fourth edge cloud node through a communication channel between the edge management and control device and the edge management and control device in the fourth edge cloud node includes: the edge management and control device 103 in the third edge cloud node sends a request for acquiring the target image to the edge management and control device 103 in the fourth edge cloud node through a communication channel between the edge management and control device and the edge management and control device in the fourth edge cloud node, wherein the request carries information of the target image. The edge management and control device 103 in the fourth edge cloud node receives the request, judges whether the target image exists in the fourth edge cloud node according to the information of the target image carried in the request, and returns the target image to the edge management and control device 103 in the third edge cloud node or returns the storage address of the target image in the fourth edge cloud node to the edge management and control device 103 in the third edge cloud node through a communication channel between the edge management and control device 103 in the third edge cloud node when the target image exists in the fourth edge cloud node. The edge management and control device 103 in the third edge cloud node receives the target image returned by the edge management and control device 103 in the fourth edge cloud node, or receives the storage address of the target image returned by the edge management and control device 103 in the fourth edge cloud node, and reads or downloads the target image according to the storage address.
It should be noted that, the edge management and control device 103 in the third edge cloud node and the edge management and control device 103 in the fourth edge cloud node may establish a communication channel by themselves, or may establish a channel under the control of the central management and control device 101. Optionally, the central control device may also control the establishment of a communication channel between different edge control devices, and is responsible for maintaining information about existing communication channels between edge control devices, for example, information about which edge control devices have established a communication channel between edge control devices, when the communication channel is established, the state of the communication channel, the duration of the maintenance, and so on. Based on the above, after determining that the target image has been provided to the fourth edge cloud node and before providing the information of the fourth edge cloud node and the target image to the edge management and control device in the third edge cloud node, the central management and control device may further determine, according to the maintained information of the existing communication channel between the edge management and control devices, whether the communication channel already exists between the edge management and control device in the third edge cloud node and the edge management and control device in the fourth edge cloud node; if the judgment result is negative, that is, a communication channel does not exist between the edge management and control equipment in the third edge cloud node and the edge management and control equipment in the fourth edge cloud node, the edge management and control equipment in the third edge cloud node and the edge management and control equipment in the fourth edge cloud node can be controlled to establish the communication channel, so that the edge management and control equipment in the third edge cloud node can acquire the target image from the fourth edge cloud node through the communication channel. And after the edge management and control device in the third edge cloud node and the edge management and control device in the fourth edge cloud node establish a communication channel, the center management and control device provides information of the fourth edge cloud node and the target image to the edge management and control device in the third edge cloud node. Of course, if the judgment result is yes, that is, a communication channel already exists between the edge management and control device in the third edge cloud node and the edge management and control device in the fourth edge cloud node, the information of the fourth edge cloud node and the target image can be directly provided to the edge management and control device in the third edge cloud node.
It should be noted that, after the central management and control device provides the information of the fourth edge cloud node and the target image to the edge management and control device in the third edge cloud node, the central management and control device may determine, according to the information of the existing communication channel between the maintained edge management and control devices, whether the communication channel already exists between the edge management and control device in the third edge cloud node and the edge management and control device in the fourth edge cloud node; if the judgment result is negative, that is, a communication channel does not exist between the edge management and control equipment in the third edge cloud node and the edge management and control equipment in the fourth edge cloud node, the edge management and control equipment in the third edge cloud node and the edge management and control equipment in the fourth edge cloud node can be controlled to establish the communication channel, so that the edge management and control equipment in the third edge cloud node can acquire the target image from the fourth edge cloud node through the communication channel.
In some optional embodiments, in order to ensure efficiency of the third edge cloud node to acquire the target image, before providing the target image at the fourth edge cloud node to the third edge cloud node, the central management and control device may further determine, according to an attribute of the fourth edge cloud node, whether the fourth edge cloud node is suitable for providing the target image for the third edge cloud node; if the judgment result is yes, namely the fourth edge cloud node is suitable for providing the target mirror image for the third edge cloud node, the target mirror image at the fourth edge cloud node can be provided for the third edge cloud node; if the judgment result is negative, the target image can be obtained from the image library and provided to the third edge cloud node.
It is worth to describe that, according to different application scenarios and application requirements, different attributes of the fourth edge cloud node can be combined, and whether the fourth edge cloud node is suitable for providing the target mirror image for the third edge cloud node can be judged from different angles. The following is illustrative:
for example, it may be determined whether the operator to which the fourth edge cloud node belongs is the same as the operator to which the first edge cloud node belongs in combination with the operator to which the fourth edge cloud node belongs; if the judgment result is yes, the fourth edge cloud node and the first edge cloud node are edge cloud nodes under the same operator, data transmission can be carried out on the fourth edge cloud node and the first edge cloud node, the data transmission rate is faster than the data transmission rate of the cross operator, and the method is suitable for providing a target mirror image for the first edge cloud node.
For another example, in combination with the position attribute of the fourth edge cloud node, whether the distance between the fourth edge cloud node and the third edge cloud node is smaller than a set distance threshold value may be determined; if the judgment result is yes, the fact that the fourth edge cloud node is relatively close to the third edge cloud node is indicated, and the object mirror image is provided for the third edge cloud node, so that the fourth edge cloud node relatively close to the third edge cloud node provides the mirror image for the third edge cloud node, the third edge cloud node can conveniently and rapidly acquire the mirror image, and efficiency is improved. The distance between the fourth edge cloud node and the third edge cloud node can be the average distance between the two edge cloud nodes, the distance between the centers of the two edge cloud nodes, the distance between the nearest outer edges of the two edge cloud nodes and the like, and can be flexibly defined according to requirements.
For another example, whether the available bandwidth of the fourth edge cloud node is greater than a set bandwidth threshold may be determined in combination with the bandwidth attribute of the fourth edge cloud node; if the judgment result is yes, the fourth edge cloud node is abundant in bandwidth resources, and is suitable for providing the target mirror image for the third edge cloud node, so that the fourth edge cloud node with abundant bandwidth resources provides the mirror image for the third edge cloud node, the transmission rate of the mirror image can be ensured, the third edge cloud node can conveniently and rapidly acquire the mirror image, and the efficiency is improved.
For another example, whether the load capacity of the fourth edge cloud node is smaller than a set load capacity threshold value may be determined by combining the load attribute of the fourth edge cloud node; if the judgment result is yes, the fourth edge cloud node is light in load and suitable for providing a target mirror image for the third edge cloud node, and therefore the fourth edge cloud node with light load provides the mirror image for the third edge cloud node, on one hand, load balancing can be achieved, on the other hand, the third edge cloud node can acquire the mirror image conveniently and rapidly, and efficiency is improved.
It should be noted that the above-listed ways may be used alternatively or in any combination, and this will not be described in any way.
Further, in the case that the fourth edge cloud node is plural, the above several modes may be combined with plural attributes of the fourth edge cloud node, so as to select a fourth edge cloud node suitable for providing the target image for the first edge cloud node. For example, if there are multiple fourth edge cloud nodes, the operators to which the multiple fourth edge cloud nodes belong may be combined, and a fourth edge cloud node that belongs to the same operator as the first edge cloud node may be selected from the multiple fourth edge cloud nodes; furthermore, if the selected fourth edge cloud nodes are still multiple, the fourth edge cloud node with the minimum load or lower than the set load threshold can be selected from the selected fourth edge cloud nodes according to the load of the selected fourth edge cloud nodes, and a target mirror image is provided for the first edge cloud node.
In some alternative embodiments, it may be that the target image has already been provided to the third edge cloud node, for example, in a traffic volume expansion scenario, the image that needs to be used for creating a new instance in the edge cloud node that is currently providing cloud computing service for the service demander is the same as the image that is used by the previous instance, and if the image that is used by the previous instance is also saved in the edge cloud node, the image may not be provided repeatedly for the edge cloud node. For this case, in order to save resources, before providing the target image at the fourth edge cloud node to the third edge cloud node, the central management and control device may determine whether the maintained correspondence between the issued image and the edge cloud node where the issued image is located includes the third edge cloud node; if the judgment result is yes, the fact that the target mirror image is provided for the third edge cloud node is indicated, and the target mirror image is still stored in the third edge cloud node, information of the target mirror image can be provided for the third edge cloud node, the third edge cloud node can read the target mirror image stored in the third edge cloud node, the target mirror image does not need to be transmitted again, and network resources consumed by transmitting the target mirror image can be saved; if the judgment result is negative, the target image is not provided for the third edge cloud node, or the target image does not exist in the third edge cloud node, the target image at the fourth edge cloud node can be provided for the third edge cloud node. Under the condition that edge management and control equipment is deployed in the third edge cloud node, if the central management and control equipment judges that the corresponding relation between the maintained issued image and the edge cloud node where the issued image is located contains the target image, information of the target image can be provided to the edge management and control equipment in the third edge cloud node, the edge management and control equipment in the third edge cloud node can acquire the target image from a space for storing the image in the third edge cloud node according to the information of the target image, and the target image is provided to corresponding resource equipment in the third edge cloud node so as to provide an instance capable of providing cloud computing service for the corresponding resource equipment according to the creation of the target image.
Further alternatively, it is possible that the same edge cloud node provides multiple cloud computing services for the same user or different users, i.e., multiple images may be received, which may be stored in the edge cloud node. The edge cloud node may provide a certain storage space for storing the image. Considering that the storage space of the images in the edge cloud nodes has a certain limit, in order to have enough storage space to store the newly received images, the edge cloud nodes need to eliminate the locally stored images. In this embodiment, the central management and control device is responsible for providing a mirrored elimination policy for the edge cloud nodes. The central management and control equipment can generate a mirror image elimination strategy, the elimination strategy is issued to each edge cloud node, and each edge cloud node eliminates the stored mirror image according to the elimination strategy. Under the condition that the network system comprises the edge management and control equipment, the central management and control equipment can issue an elimination strategy to the edge management and control equipment, and the edge management and control equipment performs elimination processing on the images stored in each edge cloud node according to the elimination strategy. Further, under the condition that edge management and control equipment is deployed in each edge cloud node, the central management and control equipment can issue an elimination strategy to the edge management and control equipment in each edge cloud node, and the edge management and control equipment in each edge cloud node performs elimination processing on the images stored in the edge cloud nodes to which the edge cloud node belongs according to the elimination strategy.
Alternatively, the elimination policy may be an earliest-received-time elimination policy, that is, the image with the earliest receiving time is preferentially eliminated according to the receiving time of the image. Alternatively, the elimination policy may be a least frequently used elimination policy, i.e., images with the least frequently used are preferentially eliminated according to the frequency of use of the images. Alternatively, the elimination policy may be a maximum resource occupation elimination policy, that is, the mirror image occupying the maximum storage space is eliminated preferentially according to the size of the storage space occupied by the mirror image.
For the edge cloud node, the image stored in the node can be eliminated periodically according to the elimination strategy; or, when the new image needs to be received or acquired, judging whether the node has enough storage space to store the new image, and when the node does not have enough storage space, performing elimination processing on the image stored in the node according to the elimination strategy so as to store the new image. Taking an example that the third edge cloud node needs to acquire the target image from the fourth edge cloud node, before edge management and control equipment in the third edge cloud node acquires the target image from the fourth edge cloud node, the edge management and control equipment in the third edge cloud node can judge whether the third edge cloud node has enough storage space to store the target image; and if the third edge cloud node does not have enough storage space, performing elimination processing on the images stored in the third edge cloud node according to the elimination policy so as to have enough storage space to store the target images. Alternatively, if there is enough storage space in the third edge cloud node, the image stored in the third edge cloud node may not be obsolete temporarily.
Optionally, as shown in fig. 1c, the network system 100 further includes: the mirror image construction device 104. The image construction device 104 may be deployed in one or more edge cloud nodes, and is mainly responsible for construction, verification, etc. of an application image. The image construction device 104 may provide an edge cloud environment, may construct an image adapted to the edge cloud environment, may also verify whether the image is adapted to the edge cloud environment, may reconstruct an image that is not adapted to the edge cloud environment, or may output a prompt message of the disagreement, etc. Based on the image construction device 104, the user can add an image to the network system 100.
In an alternative implementation manner of the newly added image, the user (for example, the service demander) may submit a third request for the newly added image to the central control device, where the third request includes image construction information; the central control equipment sends a construction request to the mirror image construction equipment, wherein the construction request comprises mirror image construction information; after receiving the construction request, the mirror image construction equipment acquires mirror image construction information from the construction request, constructs a mirror image adapted to the edge cloud environment according to the mirror image construction information, and returns the constructed mirror image to the central management and control equipment; the central control equipment receives the newly constructed mirror image returned by the mirror image construction equipment and adds the newly constructed mirror image into the mirror image library, so that the mirror image library is continuously enriched.
In another alternative implementation manner of newly added mirror images, a rule and a specification of the mirror images can be provided for users (such as service demander), so that the users can make or generate the mirror images themselves, and the mirror images generated or made by the users are required to meet related requirements of security, specification and the like of the edge cloud environment. After the user makes or generates the image, a fourth request for adding the image to be added may be sent to the central control device, where the fourth request includes the image to be added, and the added image is the image made or generated by the user. The central control equipment receives a fourth request, acquires a mirror image to be newly added from the fourth request, and sends the mirror image to be newly added to the mirror image construction equipment; the image construction equipment adapts the image to be newly added to the edge cloud environment; if the image to be newly added is matched with the edge cloud environment, the image construction equipment returns a message for the image to be newly added to be matched with the edge cloud environment to the central control equipment; if the image to be newly added is not matched with the edge cloud environment, the image construction equipment returns a message that the image to be newly added is not matched with the edge cloud environment to the central control equipment.
For the central control equipment, if a message of adapting to the environment of the newly added mirror image and the edge cloud returned by the mirror image construction equipment is received, adding the newly added mirror image into a mirror image library; if a message that the image to be newly added is not adapted to the edge cloud environment is received, which is returned by the image construction service image construction equipment, or the user is informed to re-submit the image to be newly added after the image to be newly added is reconstructed, or the user is informed to provide a reconstruction method of the image to be newly added, so that the image construction service image construction equipment can reconstruct the image to be newly added into the image adapted to the edge cloud environment according to the reconstruction method. If the user provides a reconstruction method of the image to be newly added, the central management and control equipment can provide the reconstruction method for the image construction equipment, the image construction equipment reconstructs the image to be newly added according to the reconstruction method, so that the image is matched with the edge cloud environment, and the reconstructed image is returned to the central management and control equipment; the central control equipment receives the reconstructed mirror image and adds the reconstructed mirror image into a mirror image library.
The image construction device 104 may be a logic device with functions of image construction, verification, etc. (for example, may be an example that may provide an image construction environment and resources, and may have functions of application deployment, image verification, etc.), where these functions may be implemented by deploying one physical machine or virtual machine, or may be distributed and deployed on multiple physical machines or virtual machines. Of course, the image construction device 104 of the present embodiment may be one or more physical devices having functions of image construction, verification, and the like. The embodiment of the application is not limited to the implementation structure of the mirror image construction device, and all the device structures with the functions are applicable to the embodiment of the application.
In the embodiment of the application, not only the images can be newly added into the image library, but also the images which are not used or are not used for a long time can be deleted, so that the storage space is saved. For example, the central control device may periodically or in real time count the usage frequency of each image in the image library, take the image whose usage frequency is less than the frequency threshold as the image to be deleted, and execute the image deletion procedure to delete the image. For another example, the central management and control device may also receive a mirror image deletion request submitted by a user (for example, a service demander), take a mirror image that is indicated to be deleted by the mirror image deletion request as a mirror image to be deleted, and execute a mirror image deletion procedure to delete the mirror image. The image deletion request may carry information of the image to be deleted, such as an ID, a name, or a number.
For the central management and control device, any mode can be used but not limited to the above method for determining the image to be deleted, after the image to be deleted is determined, the image to be deleted can be deleted from the image library on one hand, and on the other hand, the edge cloud node storing the image to be deleted can be indicated to delete the image to be deleted. The central management and control equipment can match the maintained corresponding relationship between the issued mirror image and the edge cloud node where the issued mirror image is located according to the mirror image to be deleted, and determine the edge cloud node where the mirror image to be deleted is stored according to the matching result. If the fifth edge cloud node corresponding to the mirror image to be deleted is matched in the corresponding relation, the fact that the mirror image to be deleted is issued to the fifth edge cloud node is described, the mirror image to be deleted is still stored in the fifth edge cloud node, then a deleting instruction is sent to the fifth edge cloud node, and the deleting instruction carries information of the mirror image to be deleted so as to instruct the fifth edge cloud node to delete the mirror image to be deleted stored in the fifth edge cloud node. The fifth edge cloud node may be one or more.
Here, in the case where the network system 100 includes the edge management and control device 103, the center management and control device may specifically send a deletion instruction to the edge management and control device 103; the edge management and control equipment 103 receives a deleting instruction issued by the central management and control equipment, acquires the information of the mirror image to be deleted from the deleting instruction, and judges whether the mirror image to be deleted is stored in the fifth edge cloud node according to the information of the mirror image to be deleted; and if the images to be deleted are stored, deleting the images to be deleted in the fifth edge cloud node. Further, if the edge management and control device 103 is disposed in the fifth edge cloud node, the central management and control device 101 may specifically send the deletion instruction to the edge management and control device 103 in the fifth edge cloud node; the edge management and control equipment 103 in the fifth edge cloud node receives a deleting instruction issued by the central management and control equipment, acquires the information of the mirror image to be deleted from the deleting instruction, and judges whether the mirror image to be deleted is stored in the fifth edge cloud node according to the information of the mirror image to be deleted; and if the images to be deleted are stored, deleting the stored images to be deleted in the fifth edge cloud node.
The central management and control equipment deletes the mirror image to be deleted from the mirror image library, and the edge cloud node storing the mirror image to be deleted also deletes the mirror image to be deleted stored in the central management and control equipment, so that the mirror image deleting process is completed.
In any manner, for the resource devices in the edge cloud node, after the images are acquired, resources such as computing, network, storage and the like can be provided for the examples in a virtualized form through the capability supported by hardware or software under the control of the central management and control device 101 or the edge management and control device 103, and the corresponding images can be mounted to the corresponding examples in the form of a system disk. After the instance is created, the instance is started in an attempt, and after the corresponding instance is successfully started, the cloud computing service can be provided by utilizing the capabilities of the resource devices. The resource equipment provides resources such as calculation, network and storage for the instance under the control of the edge management and control equipment, and the method comprises the following steps: the edge management and control equipment applies for related computing resources, storage resources and/or network resources from the resources allocated or reserved in the target edge node according to the resource template provided by the central management and control equipment; and performing the creation action of the related resources by calling the actuators such as computation, storage, network and the like in the target edge cloud node. Wherein the creating action of the resource comprises: processing and storing related resources, creating a system disk of an instance according to configuration information of the mirror image and mirror image content, and creating a corresponding data disk according to a resource template; creating instance-dependent network resources, such as IP addresses, virtual switches, etc.; and creating the computing resource in conjunction with the resource template.
Operation and maintenance management function:
in the embodiment of the present application, the central management and control device may perform operation and maintenance management and control on at least one edge cloud node with the assistance of the edge management and control device. In detail, the edge management and control equipment can perform operation and maintenance monitoring on at least one edge cloud node and report operation and maintenance monitoring data to the central management and control equipment, so that the central management and control equipment can manage and control the at least one edge cloud node according to the operation and maintenance monitoring data. The central management and control equipment can carry out operation and maintenance management and control on at least one edge cloud node according to operation and maintenance monitoring data reported by the edge management and control equipment. Optionally, for the edge management and control device, the operation and maintenance monitoring can be performed on at least one edge cloud node under the control of the central management and control device, and the operation and maintenance monitoring data is reported to the central management and control device, so that the central management and control device performs operation and maintenance management and control on the at least one edge cloud node according to the operation and maintenance monitoring data. Or, the edge management and control device may periodically perform operation and maintenance monitoring on at least one edge cloud node according to the timing task and report operation and maintenance monitoring data to the central management and control device. In any implementation mode, the edge management and control device mainly performs functions of monitoring, data acquisition, reporting and the like, and the operation and maintenance decision is determined by the central management and control device.
The central control device controls the edge control device to perform operation and maintenance monitoring on at least one edge cloud node, which can be but is not limited to the following optional embodiments:
in an alternative embodiment, the central control device may send a first type of operation and maintenance monitoring instruction to the edge control device, so as to instruct the edge control device to perform operation and maintenance monitoring on at least one edge cloud node from at least one operation and maintenance dimension, and report operation and maintenance monitoring data on the at least one operation and maintenance dimension to the central control device. The first type of operation and maintenance monitoring instruction is a monitoring instruction for instructing the edge management and control equipment to perform operation and maintenance monitoring on at least one edge cloud node from at least one operation and maintenance dimension and reporting operation and maintenance monitoring data on at least one operation and maintenance dimension. For the edge management and control equipment, a first type of operation and maintenance monitoring instruction sent by the central management and control equipment can be received, operation and maintenance monitoring is carried out on at least one edge cloud node in at least one operation and maintenance dimension according to the first type of operation and maintenance monitoring instruction, and operation and maintenance monitoring data in at least one operation and maintenance dimension is reported to the central management and control equipment. And the central management and control equipment performs operation and maintenance management and control on at least one edge cloud node according to the operation and maintenance monitoring data in at least one operation and maintenance dimension reported by the edge management and control equipment. It should be noted that at least one operation dimension can be flexibly set according to application requirements and preset into the edge management and control equipment and the center management and control equipment. See the following examples for examples of the dimension of the operation and maintenance.
In another alternative embodiment, the central management and control device may selectively perform operation and control on at least one edge cloud node in one or some operation and control dimensions. Based on the operation and maintenance monitoring instruction, the central control device can send a second type of operation and maintenance monitoring instruction to the edge control device, wherein the second type of operation and maintenance monitoring instruction corresponds to the appointed operation and maintenance dimension and is used for indicating the edge control device to perform operation and maintenance monitoring on at least one edge cloud node in the appointed operation and maintenance dimension and reporting operation and maintenance monitoring data in the appointed operation and maintenance dimension. And for the edge management and control equipment, a second type of operation and maintenance monitoring instruction sent by the central management and control equipment can be received, operation and maintenance monitoring is carried out on at least one edge cloud node in a designated operation and maintenance dimension according to the second type of operation and maintenance monitoring instruction, and operation and maintenance monitoring data in the designated operation and maintenance dimension are reported to the central management and control equipment, so that the central management and control equipment can carry out operation and maintenance management and control on at least one edge cloud node according to the operation and maintenance monitoring data in the designated operation and maintenance dimension. The central management and control equipment is also used for receiving the operation and maintenance monitoring data in the appointed operation and maintenance dimension sent by the edge management and control equipment, and performing operation and maintenance management and control on at least one edge cloud node according to the operation and maintenance monitoring data in the appointed operation and maintenance dimension.
Optionally, the edge management and control device periodically performs operation and maintenance monitoring on the at least one edge cloud node according to the timing task may perform operation and maintenance monitoring on the at least one edge cloud node from the at least one operation and maintenance dimension according to the timing task; further, the operation and maintenance monitoring data in at least one operation and maintenance dimension can be reported to the central management and control equipment. The monitoring periods in different operation dimensions can be the same or different. For example, the edge management and control device may perform security breach scanning on the edge cloud node every 10 minutes, or perform traffic monitoring on the edge cloud node every 5 minutes.
It should be noted that the specified operation dimension may be one or more. In the case that the specified operation and maintenance dimensions are plural, each specified operation and maintenance dimension may correspond to one second type operation and maintenance monitoring instruction, that is, the central management and control device may send plural second type operation and maintenance monitoring instructions to the edge management and control device, and each second type operation and maintenance monitoring instruction corresponds to one specified operation and maintenance dimension. Or, when the number of the designated operation and maintenance is multiple, the multiple designated operation and maintenance dimensions may also correspond to the same second type operation and maintenance monitoring instruction, that is, the central management and control device may send a second type operation and maintenance monitoring instruction to the edge management and control device, where the second type operation and maintenance monitoring instruction corresponds to the multiple designated operation and maintenance dimensions.
The at least one or specified dimension may include, but is not limited to, the following dimensions: object dimension in run state, log dimension, security dimension, resource dimension, etc. Further, the object dimensions in the run state may include a run state dimension of the object and/or a lifecycle dimension of the object; the security dimension may include: traffic attack dimension and/or security vulnerability dimension.
In combination with the several operation and maintenance dimensions listed above, the central control device performs operation and maintenance control on at least one edge cloud node with the assistance of the edge control device, including but not limited to at least one of the following operation and maintenance control examples:
operation and maintenance control example 1: the central control equipment controls the edge control equipment to monitor the state of an object in an operation state in at least one edge cloud node. The control mode comprises the steps of sending a first type of operation and maintenance monitoring instruction or sending a second type of operation and maintenance monitoring instruction corresponding to the operation state dimension of the object to the edge management and control equipment. The edge management and control equipment is controlled by the central management and control equipment, or periodically monitors the state of the object in the running state in at least one edge cloud node according to the timing task, and reports the monitored running state of the object in the running state to the central management and control equipment. The central management and control equipment identifies an object with abnormal running state from the running state of the object in the running state, which is reported by the edge management and control equipment, and for convenience of description and distinction, the object with abnormal running state is called a target object and is subjected to exception processing aiming at the target object. Wherein, the objects in the running state in the edge cloud node include, but are not limited to: examples, images, containers, other virtual components, physical machines, CPUs, and/or hard disks, etc. The abnormal condition of the running state may be different according to the object in the running state. For example, for an instance, possible exception conditions include, but are not limited to: interrupts, errors, and/or faults, etc. As another example, for a physical machine, possible exceptions include, but are not limited to: dead halt, black screen, alarm and/or flashing back of an application running on the physical machine, etc. Depending on the target object and the abnormal conditions of the running state, the abnormal handling manner may also be different, for example, but not limited to: and alarming, stopping or restarting the target object, migrating, deleting and reconstructing the target object and the like.
Operation and maintenance control example 2: the central control device controls the edge control device to monitor the life cycle of the object in the running state in the at least one edge cloud node. The control mode comprises the steps of sending a first type of operation and maintenance monitoring instruction or sending a second type of operation and maintenance monitoring instruction corresponding to the life cycle dimension of the object to the edge management and control equipment. The edge management and control equipment monitors the life cycle of the object in the running state in at least one edge cloud node under the control of the central management and control equipment or periodically according to the timing task, and reports the monitored life cycle of the object in the running state to the central management and control equipment. And the central management and control equipment controls the running object to stop, restart after stopping, and migrate or delete according to the life cycle of the running object reported by the edge management and control equipment.
Operation and maintenance control example 3: the central control equipment controls the edge control equipment to collect log data in at least one edge cloud node. The control mode comprises the steps of sending a first type of operation and maintenance monitoring instruction or sending a second type of operation and maintenance monitoring instruction corresponding to the log dimension to the edge management and control equipment. The edge management and control equipment is controlled by the central management and control equipment, or periodically collects log data in at least one edge cloud node according to a timing task, and reports the collected log data to the central management and control equipment. The central control equipment receives the log data reported by the edge control equipment, performs data analysis on the log data, and executes subsequent actions according to the data analysis result, such as charging, wind control, increase and/or decrease of instances and the like. Depending on the log data, the follow-up actions may also be different. Alternatively, the log data may include, but is not limited to: data such as various performances, indexes and the like in the edge cloud node, for example: the bandwidth flow of the instance, the current running condition of the instance, the IO load of the instance, the bandwidth flow of the physical machine, the current running condition of the physical machine, the IO load of the physical machine, the running condition of the edge management and control equipment and/or the running condition of other virtualization components, and the like.
Optionally, the central control device not only can collect log data of each edge cloud node reported by the edge control device, but also has the capability of data inspection, and for some data, if the data stored by the central control device and the data in the edge cloud node are inconsistent, the central control device can actively synchronize the latest data to the edge cloud node, for example, can synchronize the latest version of mirror image to the edge cloud node.
Operation and maintenance control example 4: the central control equipment controls the edge control equipment to monitor the flow of at least one edge cloud node. The control mode comprises the steps of sending a first type of operation and maintenance monitoring instruction or sending a second type of operation and maintenance monitoring instruction corresponding to the flow attack dimension to the edge management and control equipment. And the edge management and control equipment monitors the flow of at least one edge cloud node under the control of the central management and control equipment or periodically according to the timing task, and reports the monitored flow attack event to the central management and control equipment. And the central control equipment performs blocking processing on the traffic attack event in the edge cloud node. Optionally, the edge management and control device may further report the monitored traffic data to the central management and control device, where the central management and control device may further perform traffic attack defense on at least one edge cloud node according to the traffic data.
Operation and maintenance control example 5: the central control equipment controls the edge control equipment to scan network security vulnerabilities for at least one edge cloud node. The control mode comprises the steps of sending a first type of operation and maintenance monitoring instruction or sending a second type of operation and maintenance monitoring instruction corresponding to the network security dimension to the edge management and control equipment. And the edge management and control equipment performs network security vulnerability scanning on at least one edge cloud node under the control of the central management and control equipment or periodically according to a timing task, and reports the scanned network security vulnerability problem to the central management and control equipment. The central control equipment receives the network security hole problem reported by the edge control equipment and repairs the network security hole problem.
Operation and maintenance control example 6: the central controlling device controls the edge controlling device to monitor the resource usage in the at least one edge cloud node. The control mode comprises the steps of sending a first type of operation and maintenance monitoring instruction or sending a second type of operation and maintenance monitoring instruction corresponding to the resource dimension to the edge management and control equipment. The edge management and control equipment monitors the resource consumption in at least one edge cloud node under the control of the central management and control equipment or periodically according to the timing task, and reports the monitored resource consumption information to the central management and control equipment. And the central management and control equipment performs resource capacity expansion or capacity reduction on at least one edge cloud node according to the resource consumption information reported by the edge management and control equipment. The resources herein include various kinds of resource information such as device resources such as physical machines, storage resources, computing resources such as CPUs, GPUs, network resources such as bandwidths, and the like.
Further, if edge management and control equipment is deployed in each edge cloud node, each edge management and control equipment can perform operation and maintenance monitoring on the edge cloud node to which the edge management and control equipment belongs under the control of the central management and control equipment and report operation and maintenance monitoring data in the edge cloud node to which the edge management and control equipment belongs to the central management and control equipment. The central management and control equipment can receive operation and maintenance monitoring data reported by the edge management and control equipment in each edge cloud node, and perform operation and maintenance management and control on each edge cloud node according to the operation and maintenance monitoring data in each edge cloud node.
The embodiment of the application is not limited to the implementation structures of the central management and control equipment and the edge management and control equipment. Optionally, as shown in fig. 1b, a structural frame of the central control device includes: the system comprises a resource scheduling management and control module, a mirror image management and control module and a central operation and maintenance module; the central operation and maintenance module further comprises: a central monitoring unit, a central log unit, a central security unit, etc. Accordingly, a structural framework of an edge management and control apparatus is shown in fig. 1b, comprising: the system comprises a resource scheduling service module, a mirror image service module and an edge operation and maintenance module; the edge operation and maintenance module further comprises: an edge monitoring unit, an edge log unit, an edge security unit, and the like.
The resource scheduling management and control module in the central management and control device and the resource scheduling service module in the edge management and control device are mutually matched, so that resource scheduling can be performed on the edge cloud node, and the resource scheduling function can be described below. The mirror image management and control module in the central management and control device is matched with the mirror image service module in the edge management and control device, mirror image management and distribution can be performed on the edge cloud nodes, and the mirror image management and distribution functions can be described below.
The central operation and maintenance module in the central management and control equipment is matched with the edge operation and maintenance module in the edge management and control equipment, so that operation and maintenance management and control can be carried out on the edge cloud nodes. The above operation and maintenance control examples 1-6 can be implemented by the corresponding units in the central operation and maintenance module and the edge operation and maintenance module shown in fig. 1b in a matched manner. The operation and maintenance control example 3 can be implemented by matching a central log unit in the central operation and maintenance module with an edge log unit in the edge operation and maintenance module. In detail, the central log unit sends a first type operation and maintenance monitoring instruction or a second type operation and maintenance monitoring instruction corresponding to the log dimension to the edge log unit; the edge log unit collects log data in the edge cloud nodes according to the first class or the second class operation and maintenance monitoring instructions and reports the log data to the central log unit; and the central log unit performs data analysis on the log data and executes subsequent actions according to the data analysis result. Operation and maintenance control examples 4 and 5 can be implemented by matching a central security unit in the central operation and maintenance module with an edge security unit in the edge operation and maintenance module. In detail, the central security unit sends a first class operation and maintenance monitoring instruction or a second class operation and maintenance instruction corresponding to a flow attack or network security dimension to the edge security unit; the edge security unit can monitor the flow of the edge cloud node or scan the network security vulnerabilities according to the first class or the second class of operation and maintenance instructions, and report the monitored flow attack event or the network security vulnerabilities to the central security unit; the central security unit blocks traffic attack events or repairs network security vulnerability problems. The operation and maintenance control examples 1, 2 and 6 can be realized by matching a central monitoring unit in the central operation and maintenance module and an edge monitoring unit in the edge operation and maintenance module, and detailed implementation processes are not repeated.
From the above, with the assistance of the edge management and control device, the central management and control device can know the health, the resource consumption, the log data and/or the infrastructure of each instance in the edge cloud node, and can realize remote operation and maintenance, log management and the like.
In the embodiment of the application, except that the central management and control equipment can perform operation and maintenance management and control on at least one edge cloud node, the edge management and control equipment can autonomously perform operation and maintenance management and control on at least one edge cloud node under the condition that the central management and control equipment does not perform operation and maintenance management and control on the edge cloud node or cannot perform operation and maintenance management and control on the edge cloud node.
For example, the edge management and control device may monitor a connection condition between the edge management and control device and the central management and control device, and in a case that the connection between the edge management and control device and the central management and control device is lost, it may be determined that the central management and control device cannot perform operation and maintenance management and control on the edge cloud nodes, and then at least one edge cloud node may be autonomously performed operation and maintenance management and control from at least one operation and maintenance dimension.
For another example, in a manner that the central control device sends a first type of operation and maintenance monitoring instruction to the edge control device to control the edge control device to perform operation and maintenance monitoring on at least one edge cloud node, the edge control device may wait to receive the first type of operation and maintenance monitoring instruction sent by the central control device, and if the first type of operation and maintenance monitoring instruction sent by the central control device is not received, it may be determined that the central control device does not perform operation and maintenance control on the at least one edge cloud node or cannot perform operation and maintenance control on the at least one edge cloud node from at least one operation and maintenance dimension autonomously. Optionally, the edge management and control device and the central management and control device may pre-agree on a waiting duration of the first type of operation and maintenance monitoring instruction, and if the waiting duration is longer than the waiting duration and the first type of operation and maintenance monitoring instruction sent by the central management and control device is not received, it is determined that the first type of operation and maintenance monitoring instruction sent by the central management and control device is not received.
For another example, in a manner that the central control device sends a second type of operation and maintenance monitoring instruction corresponding to the designated operation and maintenance dimension to the edge control device so as to control the edge control device to perform operation and maintenance monitoring on at least one edge cloud node from the designated operation and maintenance dimension, the edge control device may wait to receive the second type of operation and maintenance monitoring instruction sent by the central control device, and if the second type of operation and maintenance monitoring instruction sent by the central control device is not received in the designated operation and maintenance dimension, it may be determined that the central control device does not perform operation and maintenance control on the at least one edge cloud node in the designated operation and maintenance dimension or cannot perform operation and maintenance control on the at least one edge cloud node from the designated operation and maintenance dimension autonomously.
Further optionally, if the edge management and control device autonomously performs operation and control on the at least one edge cloud node from the at least one operation and maintenance dimension under the condition that the edge management and control device loses connection with the central management and control device, after the connection with the central management and control device is restored, operation and maintenance management and control data during the connection loss can be synchronized to the central management and control device. It should be noted that the operation and maintenance control data mainly includes data such as a policy, a manner, an effect, and the like of operation and maintenance control, and of course, may also include operation and maintenance monitoring data.
The at least one or specified dimension may include, but is not limited to, the following dimensions: object dimension in run state, log dimension, security dimension, resource dimension, etc. Further, the object dimensions in the run state may include a run state dimension of the object and/or a lifecycle dimension of the object; the security dimension may include: traffic attack dimension and/or security vulnerability dimension.
In combination with the several operation and maintenance dimensions listed above, the edge management and control device autonomously performs operation and maintenance control on at least one edge cloud node, including but not limited to at least one of the following operation and maintenance control examples:
operation and maintenance control example a: and autonomously monitoring the state of the object in the running state in at least one edge cloud node, and performing exception handling on the monitored object with the abnormal running state. For the objects in the running state, abnormal conditions of the running state, and the like, reference may be made to the above description, and the description thereof will not be repeated.
Optionally, in example a, the edge management and control device is specifically configured to, when performing exception handling for the target object: analyzing the abnormal running state of the target object, and determining at least one candidate processing mode according to an analysis result; and acquiring a target processing mode from at least one candidate processing mode, and performing exception processing on the target object according to the target processing mode.
Furthermore, when the edge management and control device acquires the target processing mode, the edge management and control device is specifically configured to: reporting at least one candidate processing mode to the central control equipment under the condition that the edge control equipment is connected with the central control equipment, so that the central control equipment can select the processing mode; receiving a processing mode returned by the central control equipment as a target processing mode; or outputting at least one candidate processing mode to the edge operation and maintenance management personnel under the condition that the edge management and control equipment and the central management and control equipment are out of connection, so that the edge operation and maintenance personnel can select the processing mode from the candidate processing modes; responding to the selection operation of the edge operation and maintenance management personnel, and determining the selected processing mode as a target processing mode; or under the condition that the connection with the central control equipment is lost, selecting a target processing mode from at least one candidate processing mode according to a set selection strategy.
And b, the operation and maintenance control example autonomously monitors the life cycle of the object in the running state in at least one edge cloud node, and controls the object in the running state to stop, restart or delete after stopping according to the monitoring result. For a container or instance, the container or instance may be controlled to stop executing, restart after stopping, or delete, etc.
Operation and maintenance control example c: and automatically collecting log data in at least one edge cloud node, carrying out data analysis on the log data, and executing subsequent actions according to the data analysis result. The log data includes, but is not limited to, bandwidth traffic of an instance in the edge cloud node, current running conditions of the instance, IO load of the instance, bandwidth traffic of the physical machine, current running conditions of the physical machine, IO load of the physical machine, running conditions of the edge management and control device, and/or running conditions of other virtualized components, etc. Optionally, follow-up actions such as charging, wind control, resource reallocation and the like can be performed according to the analysis result of the log data, but the method is not limited to the following.
And d, an operation and maintenance management example autonomously monitors traffic of at least one edge cloud node and performs blocking processing on monitored traffic attack events.
Operation and maintenance control example e: and autonomously scanning network security vulnerabilities of at least one edge cloud node, and repairing scanned network security vulnerabilities.
Operation and maintenance control example f: and autonomously monitoring the resource consumption in the at least one edge cloud node, and carrying out resource capacity expansion or capacity reduction on the at least one edge cloud node according to the monitoring result. Resources herein include, but are not limited to: device resources such as physical machines, storage resources such as memories and magnetic disks, computing resources such as CPUs and GPUs, and network resources such as bandwidths. When the consumption is high, the capacity of the resources can be expanded, and when the consumption is low, the capacity of the resources can be reduced.
Further, if edge management and control equipment is deployed in each edge cloud node, each edge management and control equipment can autonomously perform operation and maintenance management and control on the edge cloud node to which the center management and control equipment belongs under the condition that the center management and control equipment does not perform operation and maintenance management and control on the edge cloud node to which the center management and control equipment belongs.
Optionally, in examples a-e of the foregoing example in which the edge management and control device autonomously performs operation and control on the at least one edge cloud node, the edge management and control device may perform operation and control on the at least one edge cloud node periodically according to a timing task. For example, in example d, the edge management and control device may monitor traffic of at least one edge cloud node every 10 minutes according to the timing task, and perform blocking processing for the monitored traffic attack event. For another example, in example e, the edge management and control device may scan at least one edge cloud node for network security vulnerabilities every 5 minutes according to a timing task and fix the scanned network security vulnerabilities. Of course, the edge management and control device may also autonomously perform operation and control on at least one edge cloud node according to an autonomous policy in other manners, for example, may autonomously perform operation and control on at least one edge cloud node at a certain fixed time point every day.
In combination with the above examples 1-6 and examples a-f, in this embodiment, the central management and control device is combined with the edge management and control device, and the central management and control device can perform operation and maintenance management and control on at least one edge cloud node with the assistance of the edge management and control device, in addition to that, the edge management and control device also has a certain self-operation and maintenance management and control capability, and can perform operation and maintenance management and control on the edge cloud node autonomously under the condition that the central management and control device does not perform operation and maintenance management and control on the edge cloud node or cannot perform operation and maintenance management and control on the edge cloud node, so as to implement two-stage operation and maintenance management and control, perform operation and maintenance management and control on the edge cloud node more fully and comprehensively, provide conditions for "putting cloud computing into the edge cloud node closer to a terminal, and further provide cloud computing service for users with the help of resources in the edge cloud node, thereby being beneficial to reducing response delay, reducing pressure of a central cloud or traditional cloud computing platform, and reducing bandwidth cost.
In summary, in the network system provided by the embodiment of the application, the resources, mirror images, examples, operation and maintenance and the like of the edge cloud nodes are uniformly managed and controlled based on the centralized management and control mode, so that the edge cloud nodes can be managed and coordinated to the greatest extent, errors caused by single-point self-control or asynchronous whole network information can be reduced, and the optimization of resource scheduling can be achieved by utilizing the characteristic of centralized management and control, so that the situation of local resource waste of the edge is avoided.
In addition to the network system described above, embodiments of the present application provide example management methods from the perspective of a central management facility, as described in detail below.
Fig. 2a is a flow chart of an example management and control method according to an exemplary embodiment of the present application. As shown in fig. 2a, the method comprises:
at least one instance deployed in at least one edge cloud node in a network system is determined, wherein the at least one instance can provide cloud computing services for a service demander.
22a, managing at least one instance for the at least one instance to provide cloud computing services for the service demander.
In this embodiment, the network system includes at least one edge cloud node, where at least one instance is deployed, where the at least one instance may provide cloud computing services for a service demander. The central management and control equipment determines at least one instance in the edge cloud nodes, and manages the at least one instance so that the at least one instance can provide cloud computing service for the service demander. The service demander here may be any device, application, system or another service that needs to use the cloud computing service provided by the instance in the edge cloud node. Taking the system as an example, the service demander may be, but is not limited to: an online video system, a risk management and control system, a client information management system or a data distribution system, etc.
Optionally, the central controlling device may perform various controls on at least one instance, and may include at least one of upgrade, migration, shutdown, restart, and release, for example, but not limited thereto.
As shown in fig. 2b, the process of upgrading and controlling the instance by the central control device includes the following steps:
21b, determining an instance to be upgraded from the at least one instance;
22b, sending an upgrade request to the service demand side so that the service demand side can determine an upgrade strategy for the to-be-upgraded instance by combining the service condition on the to-be-upgraded instance;
23b, receiving an upgrade strategy returned by the service demand side, and upgrading the instance to be upgraded according to the upgrade strategy.
In practical applications, it is possible to upgrade the image or the corresponding instance with the change of the service requirement or the update of the image version. The central management and control device can determine an instance to be upgraded from at least one instance, and the instance to be upgraded can be one or more; and sending an upgrading request to the service demand side so that the service demand side can determine an upgrading strategy for the to-be-upgraded instance by combining the service condition on the to-be-upgraded instance. The upgrade request carries identification information of the to-be-upgraded instance, such as an ID, a name and the like of the to-be-upgraded instance, or an ID, a name and the like of a service corresponding to the to-be-upgraded instance, or information such as an ID, a name and the like of an image corresponding to the to-be-upgraded instance. After receiving the upgrade request, the service demander can determine an instance to be upgraded according to the upgrade request, and in combination with service conditions on the instance to be upgraded, such as service request and response state on the instance to be upgraded, judge whether the instance to be upgraded is suitable for upgrading, what time is suitable for upgrading, what method is adopted for upgrading, and the like, so as to generate an upgrade strategy for the instance to be upgraded and return the upgrade strategy to the central management and control equipment. The central control equipment receives an upgrade strategy sent by the service demand side, and upgrades the instance to be upgraded according to the upgrade strategy.
In an alternative embodiment, the service demander may determine when the instance to be upgraded may be upgraded in combination with the service situation on the instance to be upgraded, for example, the number of service requests (for short, stock service requests) that have been received and have not yet been completed, whether there is a new service request (incremental service request), and so on, that is, the upgrade policy may include the upgrade time. Based on this, the central management and control device can start to upgrade the instance to be upgraded at the upgrade time specified in the upgrade policy. In addition, the upgrade policy may include an upgrade method, based on which the central management and control device may upgrade the instance to be upgraded using the upgrade method specified in the upgrade policy. Optionally, the upgrade policy may include an upgrade time and an upgrade method, and the central control device may use the upgrade method specified in the upgrade policy to start upgrading the instance to be upgraded at the upgrade time specified in the upgrade policy. Optionally, the upgrade policy may further include information such as whether to upgrade, and in the case of upgrade, further includes upgrade time and/or upgrade method.
In an alternative embodiment, the upgrade to an instance may be initiated by the central management and control device. For example, the central management and control device may monitor version information of an image corresponding to each instance, and when a new version of the image is found, may determine that an instance corresponding to the new version of the image needs to be updated; or, the running state, life cycle and other information of each instance can be monitored, and when problems such as loopholes, instability, incomplete functions, overlarge consumption of CPU or memory resources and the like occur in the running process of the instance are found, the instance with the problems can be determined to need to be updated.
In an alternative embodiment, the upgrade to an instance may also be initiated by the service demander. For example, when an instance needs to be upgraded according to a service requirement, the service requirement party can send upgrade description information to the central management and control equipment, wherein the upgrade description information comprises instance filtering conditions. In this case, step 21b includes: receiving upgrade description information sent by a service demand side; an instance to be upgraded is determined from the at least one instance according to instance filtering conditions.
The upgrading of the instance to be upgraded mainly means that: and shutting down the instance to be upgraded, updating the instance to be upgraded according to the image of the corresponding version (generally referred to as a new version), and restarting the instance after updating. The image version required for upgrading the instance to be upgraded can be determined by the central control device, for example, the latest version of the corresponding image is used as the image version required for upgrading, and can also be specified by the service demander. Alternatively, the service demander may provide the upgrade description information to the central management and control device with the image version required for the upgrade, for example, the upgrade description information may include information such as "upgrade image version a to image version B for all or a specified instance". Based on this, upgrade the instance to be upgraded according to the upgrade policy, including: and according to the upgrade strategy, upgrading the instance to be upgraded by utilizing the image corresponding to the image version.
Further, in the case that the network system includes the edge management and control device, according to the upgrade policy, the upgrading of the instance to be upgraded by using the image corresponding to the image version may be: and sending the image corresponding to the upgrade strategy and the image version to edge control equipment in the network system, so that the edge control equipment upgrades the instance to be upgraded by utilizing the image corresponding to the image version according to the upgrade strategy.
As shown in fig. 2c, the process of migration control of an instance by the central control device includes the following steps:
21c, determining an instance to be migrated from at least one instance, wherein the instance to be migrated belongs to the first edge cloud node;
22c, judging that the first edge cloud node meets the intra-node migration condition; if the judgment result is yes, namely the first edge cloud node meets the intra-node migration condition, executing the step 23c; if the result is negative, that is, the first edge cloud node does not meet the intra-node migration condition, step 24c is executed.
And 23c, performing migration in the edge cloud node on the instance to be migrated.
And 24c, migrating the instance to be migrated across the edge cloud nodes.
In some cases migration of instances is required. For example, in the event that an entire edge cloud node fails or is unavailable, instances in that edge cloud node need to be migrated into other edge cloud nodes. For another example, in the event that a physical machine carrying an instance fails or is down, the instance on that physical machine needs to be migrated to other physical machines. As another example, some or some instances may need to be migrated from one edge cloud node to other edge cloud nodes because of traffic needs. For another example, in the case where resource merge is required, migration of one or some instances is also required.
Under the control of the central control equipment, the instances in the edge cloud nodes can be migrated. The central controlling device determines an instance to be migrated from the at least one instance. The instance to be migrated may be one or more; if the number of the to-be-migrated instances is multiple, the multiple to-be-migrated instances can be deployed in the same edge cloud node or in different edge cloud nodes.
Optionally, the central management and control device may monitor a state of at least one instance deployed in the at least one edge cloud node, and obtain, as the instance to be migrated, the instance that has failed and/or the instance that has a specified event in operation according to the state of the at least one instance. The failed instance refers to an instance that cannot normally run, for example, an instance on a physical machine that is down, an instance that is down itself, and the like. The specified events mainly refer to events which can still normally run after some examples appear, and the specified events can be flexibly set according to application requirements, so that the specified events are not limited. For example, the specified events may be early warning or alarm events, etc., and the examples may still be operational (i.e. not faulty) although some early warning or alarm events occur, but the examples may be migrated before the fault. In addition, the central management and control device maintains information of each edge cloud node and information of each instance deployed in each edge cloud node, based on the information, an edge cloud node to which an instance to be migrated belongs can be determined, and for convenience of description and distinction, an edge Yun Jiedian to which the instance to be migrated belongs before migration is denoted as a first edge cloud node.
Optionally, the central control device may determine an instance to be migrated from at least one instance according to the resource merging requirement, and further migrate the instance to be migrated. The resource merging is mainly a process of integrating resource fragments through instance migration, and after integration, the resource fragments in the edge cloud nodes are reduced or even absent, which is beneficial to improving the resource utilization rate in the edge cloud nodes. It should be noted that the resource merging requirement may be system level or node level. The system-level resource merging refers to integrating resource fragments in the whole network system through instance migration from the perspective of the whole network system; node-level resource merging refers to integrating resource fragments in edge cloud nodes through instance migration from the point of view of the edge cloud nodes.
Alternatively, the resource merge requirement may be provided by the service demander. For example, when a service demander needs to deploy a new instance, if available resources on each resource device in an edge cloud node serving the service demander are insufficient to carry the new instance, the instance in the edge cloud node can be migrated to realize resource integration, so that enough resources are provided for the new instance. Alternatively, the resource merge requirement may be a periodic behavior of the central management and control device. For example, the central management and control device periodically performs resource fragmentation checking, and when the fragmentation rate reaches a certain threshold and the instance migration can be performed, integrates the resource fragments in each edge cloud node, so as to improve the resource utilization rate in the edge cloud node.
The resource merging requirement comprises information related to resource merging. For example, the resource merging requirement may include information of an instance that needs to be migrated for achieving the resource merging purpose, based on which an instance to be migrated may be directly determined according to the resource merging requirement. For another example, the resource merging requirement may include information of an edge cloud node that needs resource merging. Based on the above, according to the resource merging requirement, the edge cloud node needing resource merging can be determined, and in the embodiment, the edge cloud node needing resource merging is called a first edge cloud node; and then, the to-be-migrated instance can be determined by combining the available resources remained on each resource device in the first edge cloud node and the resources required by each instance in the first edge cloud node.
Regardless of the application scenario, after determining the instance to be migrated, the central control device may determine whether the first edge cloud node to which the instance to be migrated belongs meets an intra-node migration condition; if the first edge cloud node meets the intra-node migration condition, performing intra-edge cloud node migration on the instance to be migrated; and if the first edge cloud node does not meet the intra-node migration condition, migrating the instance to be migrated across the edge cloud node.
Optionally, the central management and control device may determine whether the first edge cloud node is currently in an available state; if the first edge cloud node is currently in an available state, judging whether available resources of the first edge cloud node are enough to bear an instance to be migrated; if the available resources of the first edge cloud node are enough to bear the instance to be migrated, determining that the first edge cloud node meets the intra-node migration condition; if the first edge cloud node is in an unavailable state currently or available resources of the first edge cloud node are insufficient to bear an instance to be migrated, determining that the first edge cloud node does not meet the intra-node migration condition. In the present embodiment, migration of instances is divided into two types: intra-node migration and cross-node migration. The available resources of the first edge cloud node mainly refer to available resources on each station of resource equipment in the first edge cloud node; accordingly, determining whether the available resources of the first edge cloud node are sufficient to carry the instance to be migrated mainly refers to determining whether the available resources exist in the first edge cloud node to be sufficient to carry the resource device of the instance to be migrated.
It should be noted that, in the resource merging scenario, the migration of the instance to implement the resource merging is mainly intra-node migration, and of course, may also be cross-node migration. Optionally, in determining the instance to be migrated according to the available resources remaining on each resource device in the first edge cloud node and the resources required by each instance in the first edge cloud node, the resource device to which the instance to be migrated needs to be migrated may also be determined, where the resource device is a resource device where the available resources remaining in the first edge cloud node may carry the instance to be migrated. Of course, if there are no remaining available resources in the first edge cloud node that can carry the resource device of the instance to be migrated, the cross-node migration may be performed for the instance to be migrated. In view of the purpose of resource merging, in the process of performing cross-node migration on the instance to be migrated, preferentially migrating the instance to be migrated to the resource equipment which is already used in other edge cloud nodes and can bear the instance to be migrated by the remaining available resources; further, under the condition that a plurality of resource devices which are used and the rest available resources can bear the instance to be migrated are available, the resource devices with high matching degree between the rest available resources and the resources needed by the instance to be migrated can be selected based on the principle of minimum resource fragments, and fewer resource fragments or no resource fragments are generated as much as possible.
For intra-node migration: optionally, the continuity of the cloud computing service provided by the instance may be ensured by a thermo-migration technique, which may be referred to in the prior art and will not be described herein.
For cross-node migration: the central management and control equipment can select a second edge cloud node from at least one edge cloud node, the second edge cloud node is different from the first edge cloud node, and available resources in the second edge cloud node are enough to bear an instance to be migrated, namely enough resources are available; and migrating the instance to be migrated to a second edge cloud node, and sending the attribute information of the instance to be migrated in the second edge cloud node to a service demand party so that the service demand party can conduct service scheduling on the instance to be migrated based on the attribute information. The attribute information of the to-be-migrated instance in the second edge cloud node refers to information required by the outside (e.g., a service demander or a third party authorized by the service demander) to perform service scheduling on the to-be-migrated instance after the to-be-migrated instance is migrated to the second edge cloud node, and may include, for example, but not limited to: and the second edge cloud node is located in the region, the operator information and/or public network IP and other information.
Alternatively, in selecting the second edge cloud node, the following manner may be employed, but is not limited to:
mode 1: according to the distance between other edge cloud nodes and the first edge cloud node, selecting an edge cloud node with the distance from the first edge cloud node smaller than a set distance threshold value, or selecting an edge cloud node closest to the first edge cloud node, or optionally selecting one edge cloud node from N edge cloud nodes closest to the first edge cloud node as a second edge cloud node. In the mode 1, the second edge cloud node is closest to or closer to the first edge cloud node, so that data transmission time can be saved, and migration efficiency can be improved.
Mode 2: an edge cloud node with relatively sufficient bandwidth resources can be selected from the other edge cloud nodes according to the bandwidth resources of the other edge cloud nodes, for example, an edge Yun Jiedian with the largest bandwidth resource or with the bandwidth resource larger than a set bandwidth threshold value or with lower bandwidth utilization rate is selected as the second edge cloud node. In the mode 2, the bandwidth resources of the second edge cloud node are sufficient, so that the data transmission rate can be improved, and the migration efficiency can be improved.
Mode 3: according to the current load conditions of other edge cloud nodes, an edge cloud node with relatively lighter load can be selected, for example, an edge Yun Jiedian with the smallest load or with the load smaller than a set load threshold is selected as a second edge cloud node. In the mode 3, the load of the second edge cloud node is lighter, enough resources can be provided, and the migration of the instance can be processed in time, so that the migration efficiency is improved.
Optionally, when migrating the instance to be migrated to the second edge cloud node, the central management and control device may reserve or allocate resources for the instance to be migrated in the second edge cloud node according to the resource requirement of the instance to be migrated; and after the resource reservation or allocation is successful, migrating the instance to be migrated to the reserved or allocated resource in the second edge cloud node. For example, the information such as the type of the resource, the amount of the resource and/or the performance requirement of the resource equipment required by the instance to be migrated can be determined according to the resource requirement of the instance to be migrated, and the resource reservation or the allocation can be performed in the second edge cloud node according to the information, so that the resource guarantee can be provided for the successful migration of the instance.
Optionally, if the instance to be migrated is a faulty instance, i.e. an instance that cannot operate normally, the central management and control device may also notify the service demander of the migration event, and the service demander may perform an appropriate response action, such as updating information of the instance in the service demander, or performing a disaster recovery response for a downtime condition in the process of migrating the instance. Further, the attribute information of the instance to be migrated in the second edge cloud node can be provided to the service demander together in the process of notifying the migration event. Of course, after the to-be-migrated instance is successfully migrated to the second edge cloud node, attribute information of the to-be-migrated instance in the second edge cloud node may be provided to the service demander.
Optionally, if the to-be-migrated instance is an instance in which a specified event occurs in the operation process, that is, an instance in which the specified event occurs but still can operate normally, the central control device may further send a migration request to the service demander, so that the service demander determines a migration policy for the to-be-migrated instance in combination with a service condition on the to-be-migrated instance; and receiving a migration strategy sent by the service demand side, and migrating the instance to be migrated to the second edge cloud node according to the migration strategy. The migration policy mainly includes at least one of information of whether to migrate, migration time and migration mode.
Further optionally, the central management and control device may send the attribute information of the instance to be migrated in the second edge cloud node to the service demander together with the migration request one. Or, after the to-be-migrated instance is successfully migrated to the second edge cloud node, the attribute information of the to-be-migrated instance in the second edge cloud node may be provided to the service demander.
Further optionally, if the to-be-migrated instance is an instance that has a specified event but still can normally operate, in the migration process, the to-be-migrated instance continues to operate in the first edge cloud node, so that the service request in the migration process can be continuously scheduled to the to-be-migrated instance in the first edge cloud node, and service continuity is ensured. And under the condition that the to-be-migrated instance is successfully migrated to the second edge cloud node, the service demander ensures that new service requests are all scheduled to be migrated to the second edge cloud node, and the service requests in the first edge cloud node are gradually reduced and finally no new service request exists, namely, no service request exists on the to-be-migrated instance running in the first edge cloud node, the central management and control equipment can release the to-be-migrated instance in the first edge cloud node. Optionally, after determining that there is no service request on the to-be-migrated instance running in the first edge cloud node, the service demander may send a release notification to the central management and control device after determining that there is no stock service request or incremental service request; and the central control equipment receives a release notice sent by the service demand side, and releases the instance to be migrated running in the first edge cloud node according to the release notice. Furthermore, the central management and control equipment can synchronize the running state of the instance to be migrated running in the first edge cloud node to the instance to be migrated in the second edge cloud node.
Further, no matter what kind of instance is to be migrated, the migration of the instance to be migrated to the second edge cloud node is mainly to control a process that corresponding resource equipment in the second edge cloud node creates the instance to be migrated on reserved or allocated resources according to a mirror image or snapshot corresponding to the instance to be migrated.
Further, in the case that the network system includes the edge management and control device, the central management and control device may determine, according to the resource requirement of the instance to be migrated, the scheduled resource information in the second edge cloud node, send the resource information to the edge management and control device, and according to the resource information, the edge management and control device controls the corresponding resource device in the second edge cloud node to reserve or allocate resources for the instance to be migrated. And then, the central management and control equipment can send a migration instruction to the edge management and control equipment, wherein the migration instruction instructs the edge management and control equipment to acquire a mirror image or an instance snapshot corresponding to the instance to be migrated and provide the mirror image or the instance snapshot to corresponding resource equipment in the second edge cloud node, so that the corresponding resource equipment in the second edge cloud node can create the instance to be migrated on the reserved or allocated resources according to the mirror image or the instance snapshot. Further, if the edge management and control device is deployed in the second edge cloud node, the central management and control device may send a migration instruction to the edge management and control device in the second edge cloud node, instruct the edge management and control device in the second edge cloud node to obtain a mirror image or a snapshot corresponding to the instance to be migrated and provide the mirror image or the snapshot to corresponding resource devices in the second edge cloud node, so that the corresponding resource devices in the second edge cloud node create the instance to be migrated on the reserved or allocated resources according to the mirror image or the snapshot.
In the embodiment of the method, under the control of the central control equipment, the instance in the edge cloud node can provide cloud computing service for the service demand party, so that the purpose of providing service for users by means of resources in the edge cloud node is achieved, the situation that cloud computing is put into the edge cloud node which is closer to the terminal for processing is realized, response time delay is reduced, the pressure of central cloud or a traditional cloud computing platform and the like corresponding to the edge cloud node is reduced, and bandwidth cost is reduced.
It should be noted that, in some of the flows described in the above embodiments and the drawings, a plurality of operations appearing in a specific order are included, but it should be clearly understood that the operations may be performed out of the order in which they appear herein or performed in parallel, the sequence numbers of the operations such as 21a, 22a, etc. are merely used to distinguish between the various operations, and the sequence numbers themselves do not represent any execution order. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.
Fig. 3 is a schematic structural diagram of a central control device according to an exemplary embodiment of the present application. As shown in fig. 3, the central controlling apparatus includes: a memory 31 and a processor 32.
The memory 31 is used for storing a computer program and may be configured to store other various data to support operations on the central management and control apparatus. Examples of such data include instructions, messages, pictures, videos, etc. for any application or method operating on the central management device.
A processor 32 coupled to the memory 31 for executing the computer program in the memory 31 for: determining at least one instance deployed in at least one edge cloud node in a network system, the at least one instance being operable to provide cloud computing services for service requesters; at least one instance is managed for at least one instance to provide cloud computing services for a service demander.
Optionally, the controlling of the at least one instance includes: at least one of upgrade, migration, shutdown, restart, and release.
In an alternative embodiment, as shown in fig. 3, the central management and control apparatus further includes: a communication component 33. Based on this, the processor 32, when upgrading at least one instance, is specifically configured to: determining an instance to be upgraded from at least one instance; sending an upgrade request to the service-requiring party through the communication component 33, so that the service-requiring party can determine an upgrade strategy for the instance to be upgraded in combination with the service condition on the instance to be upgraded; and receiving an upgrade strategy returned by the service demand party through the communication component 33, and upgrading the instance to be upgraded according to the upgrade strategy.
Further, the processor 32, when determining an instance to be upgraded from the at least one instance, is specifically configured to: receiving, by the communication component 33, upgrade description information sent by the service demander, the upgrade description information including instance filtering conditions; an instance to be upgraded is determined from the at least one instance according to instance filtering conditions.
Further, the upgrade description information further includes: the mirror version required for the upgrade. Then, when the processor 32 upgrades the instance to be upgraded according to the upgrade policy, the method specifically is used for: and according to the upgrade strategy, upgrading the instance to be upgraded by utilizing the image corresponding to the image version.
Further, when the processor 32 upgrades the instance to be upgraded by using the image corresponding to the image version according to the upgrade policy, the processor is specifically configured to: and sending the image corresponding to the upgrade strategy and the image version to edge control equipment in the network system, so that the edge control equipment upgrades the instance to be upgraded by utilizing the image corresponding to the image version according to the upgrade strategy. Among other things, upgrade policies include, but are not limited to: whether to upgrade, upgrade time, and upgrade method.
In an alternative embodiment, processor 32 is specifically configured to, upon migration of at least one instance: determining an instance to be migrated from at least one instance, wherein an edge Yun Jiedian to which the instance to be migrated belongs is marked as a first edge cloud node; if the first edge cloud node meets the intra-node migration condition, carrying out intra-edge cloud node migration on the instance to be migrated; and if the first edge cloud node does not meet the intra-node migration condition, migrating the instance to be migrated across the edge cloud node.
Optionally, the processor 32 is specifically configured to, when determining an instance to be migrated from at least one instance: according to the state of at least one instance, the failed instance and/or the instance with the appointed event in the running process are taken as the instance to be migrated.
Optionally, the processor 32 is specifically configured to, when determining an instance to be migrated from at least one instance: and determining an instance to be migrated from at least one instance according to the resource merging requirements.
Further, the processor 32 is specifically configured to, when determining the instance to be migrated according to the resource merging requirement: according to the resource merging requirements, determining a first edge cloud node needing resource merging; and determining the instance to be migrated according to the available resources remained on each resource device in the first edge cloud node and the resources required by each instance in the first edge cloud node.
Optionally, the processor 32 is further configured to: judging whether the first edge cloud node is in an available state or not; if the first edge cloud node is in an available state, judging whether available resources of the first edge cloud node are enough to bear an instance to be migrated; if the available resources of the first edge cloud node are enough to bear the instance to be migrated, determining that the first edge cloud node meets the intra-node migration condition; if the first edge cloud node is in an unavailable state or the available resources of the first edge cloud node are insufficient to bear the instance to be migrated, determining that the first edge cloud node does not meet the intra-node migration condition.
Optionally, when the processor 32 performs migration of the instance to be migrated across the edge cloud node, the processor is specifically configured to: selecting a second edge cloud node from the at least one edge cloud node, the second edge cloud node being different from the first edge cloud node; and migrating the instance to be migrated to a second edge cloud node, and sending the attribute information of the instance to be migrated in the second edge cloud node to a service demand party so that the service demand party can conduct service scheduling on the instance to be migrated based on the attribute information.
Optionally, if the instance to be migrated is an instance in which a specified event occurs during the running process, that is, an instance in which the specified event occurs but is still able to run normally, the processor 32 is specifically configured to, when migrating the instance to be migrated to the second edge cloud node: sending a migration request to a service requiring party through a communication component 33 so that the service requiring party can determine a migration strategy for an instance to be migrated in combination with the service condition on the instance to be migrated; and receiving a migration policy sent by the service demander through the communication component 33, and migrating the instance to be migrated to the second edge cloud node according to the migration policy.
Optionally, the processor 32 is specifically configured to, when migrating the instance to be migrated into the second edge cloud node: controlling corresponding resource equipment in the second edge cloud node to reserve or allocate resources for the instance to be migrated according to the resource requirements of the instance to be migrated; and after the resource reservation or allocation is successful, migrating the instance to be migrated to the resource reserved or allocated by the corresponding resource equipment in the second edge cloud node.
Optionally, the processor 32 is specifically configured to, when migrating the instance to be migrated to the resource reserved or allocated by the corresponding resource device in the second edge cloud node: and controlling corresponding resource equipment in the second edge cloud node to establish the instance to be migrated on the reserved or allocated resources according to the mirror image or snapshot corresponding to the instance to be migrated.
Further optionally, the processor 32 is specifically configured to: and sending a migration instruction to edge management and control equipment in the network system, wherein the migration instruction instructs the edge management and control equipment to acquire a mirror image or an instance snapshot corresponding to the instance to be migrated and provide the mirror image or the instance snapshot to corresponding resource equipment in a second edge cloud node so that the corresponding resource equipment can create the instance to be migrated on reserved or allocated resources.
Optionally, the processor 32 is further configured to: receiving a release notification sent by the service demander through the communication component 33, and releasing the instance to be migrated running in the first edge cloud node according to the release notification; in the migration process, the instance to be migrated continues to run in the first edge cloud node; wherein the release notification is sent by the service demander after determining that there are no more service requests on the instance to be migrated running in the first edge cloud node.
Further, as shown in fig. 3, the central control apparatus further includes: a display 34, a power supply assembly 35, and an audio assembly 36. Only a part of the components are schematically shown in fig. 3, which does not mean that the central controlling device only comprises the components shown in fig. 3. In addition, the components within the dashed box in fig. 3 are optional components, depending on the implementation of the central management and control apparatus. If the central controlling device is a server-like device, the display 34 and the audio component 36 may optionally be excluded; if the central control device is a terminal-type device, a display 34 and an audio component 36 may optionally be included.
Accordingly, embodiments of the present application also provide a computer-readable storage medium storing a computer program, which when executed by one or more processors, causes the one or more processors to implement the steps or operations described in the above embodiments of the method as being executable by a central management device.
The communication assembly of fig. 3 is configured to facilitate wired or wireless communication between the device in which the communication assembly is located and other devices. The device in which the communication component is located may access a wireless network based on a communication standard, such as WiFi,2G or 3G, or a combination thereof. In one exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component may further include a Near Field Communication (NFC) module, radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and the like.
The display in fig. 3 described above includes a screen, which may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation.
The power supply assembly in fig. 3 provides power for various components of the device in which the power supply assembly is located. The power components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the devices in which the power components are located.
The audio component of fig. 3 described above may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive external audio signals when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a speech recognition mode. The received audio signal may be further stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.
Claims (10)
1. An instance management method, comprising:
determining at least one instance deployed in at least one edge cloud node in a network system, the at least one instance being operable to provide cloud computing services for service requesters;
managing the at least one instance for the at least one instance to provide cloud computing services for the service demander;
wherein managing the at least one instance includes at least migrating the at least one instance, the migrating including migrating between different edge cloud nodes when the edge cloud nodes are unavailable and migrating within the same edge cloud node when the edge cloud nodes are available.
2. The method of claim 1, wherein migrating the at least one instance comprises:
determining an instance to be migrated from the at least one instance, wherein the instance to be migrated belongs to a first edge cloud node;
If the first edge cloud node meets the intra-node migration condition, performing intra-edge cloud node migration on the instance to be migrated;
and if the first edge cloud node does not meet the intra-node migration condition, migrating the to-be-migrated instance across the edge cloud node.
3. The method of claim 2, wherein determining an instance to migrate from the at least one instance comprises:
according to the state of the at least one instance, the instance with the fault and/or the instance with the appointed event in the running process are used as the instance to be migrated; or alternatively
And determining an instance to be migrated from at least one instance according to the resource merging requirements.
4. The method as recited in claim 2, further comprising:
judging whether the first edge cloud node is in an available state or not;
if the first edge cloud node is in an available state, judging whether available resources of the first edge cloud node are enough to bear the instance to be migrated;
if the available resources of the first edge cloud node are enough to bear the instance to be migrated, determining that the first edge cloud node meets the intra-node migration condition;
and if the first edge cloud node is in an unavailable state or the available resources of the first edge cloud node are insufficient to bear the instance to be migrated, determining that the first edge cloud node does not meet the intra-node migration condition.
5. The method according to any one of claims 2-4, wherein migrating the instance to be migrated across edge cloud nodes comprises:
selecting a second edge cloud node from the at least one edge cloud node, the second edge cloud node being different from the first edge cloud node;
and migrating the to-be-migrated instance into the second edge cloud node, and sending attribute information of the to-be-migrated instance in the second edge cloud node to the service demander so that the service demander can conduct service scheduling on the to-be-migrated instance based on the attribute information.
6. A network system, comprising: a central management and control device, and at least one edge cloud node;
at least one instance is deployed in the at least one edge cloud node, and the at least one instance can provide cloud computing services for service requesters;
the central control device is used for controlling the at least one instance to provide cloud computing service for the service demander;
wherein managing the at least one instance includes at least migrating the at least one instance, the migrating including migrating between different edge cloud nodes when the edge cloud nodes are unavailable and migrating within the same edge cloud node when the edge cloud nodes are available.
7. An instance management method, comprising:
determining at least one instance deployed in at least one edge cloud node in a network system, the at least one instance being operable to provide cloud computing services for service requesters;
managing the at least one instance for the at least one instance to provide cloud computing services for the service demander;
wherein the managing includes at least upgrading the at least one instance, the upgrading including: when the service demand changes, the mirror image version is updated or the operation of the instance is abnormal, determining the instance to be upgraded; acquiring an upgrade policy and a new version image of an instance to be upgraded, wherein the upgrade policy at least comprises the new version image; and according to the upgrading strategy, shutting down the instance to be upgraded, updating the instance to be upgraded according to the new version image, and restarting the instance after the updating is completed.
8. A network system, comprising: a central management and control device, and at least one edge cloud node;
at least one instance is deployed in the at least one edge cloud node, and the at least one instance can provide cloud computing services for service requesters;
the central control device is used for controlling the at least one instance to provide cloud computing service for the service demander;
Wherein the managing includes at least upgrading the at least one instance, the upgrading including: when the service demand changes, the mirror image version is updated or the operation of the instance is abnormal, determining the instance to be upgraded; acquiring an upgrade policy and a new version image of an instance to be upgraded, wherein the upgrade policy at least comprises the new version image; and according to the upgrading strategy, shutting down the instance to be upgraded, updating the instance to be upgraded according to the new version image, and restarting the instance after the updating is completed.
9. A central management and control apparatus, comprising: a memory and a processor;
the memory is used for storing a computer program; the computer program, when executed by the processor, causes the processor to carry out the steps of the method of any one of claims 1-5 and claim 7.
10. A computer readable storage medium storing a computer program, which when executed by one or more processors causes the one or more processors to implement the steps of any one of claims 1-5 and 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310139017.4A CN116170316A (en) | 2019-04-08 | 2019-04-08 | Network system, instance management and control method, device and storage medium |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910277465.4A CN111800282B (en) | 2019-04-08 | 2019-04-08 | Network system, instance management and control method, device and storage medium |
| CN202310139017.4A CN116170316A (en) | 2019-04-08 | 2019-04-08 | Network system, instance management and control method, device and storage medium |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910277465.4A Division CN111800282B (en) | 2019-04-08 | 2019-04-08 | Network system, instance management and control method, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116170316A true CN116170316A (en) | 2023-05-26 |
Family
ID=72751930
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910277465.4A Active CN111800282B (en) | 2019-04-08 | 2019-04-08 | Network system, instance management and control method, device and storage medium |
| CN202310139017.4A Pending CN116170316A (en) | 2019-04-08 | 2019-04-08 | Network system, instance management and control method, device and storage medium |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910277465.4A Active CN111800282B (en) | 2019-04-08 | 2019-04-08 | Network system, instance management and control method, device and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (2) | CN111800282B (en) |
| WO (1) | WO2020207266A1 (en) |
Families Citing this family (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112486667B (en) * | 2020-11-03 | 2022-03-18 | 深圳市中博科创信息技术有限公司 | Method and device for accurately processing data based on edge calculation |
| CN112769897B (en) * | 2020-12-21 | 2023-04-18 | 北京百度网讯科技有限公司 | Synchronization method and device of edge calculation message, electronic equipment and storage medium |
| CN114760313B (en) * | 2020-12-29 | 2023-11-24 | 中国联合网络通信集团有限公司 | Service scheduling method and service scheduling device |
| CN113190378B (en) * | 2020-12-31 | 2024-04-02 | 华数云科技有限公司 | Edge cloud disaster recovery method based on distributed cloud platform |
| CN113296903A (en) * | 2021-02-01 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Edge cloud system, edge control method, control node and storage medium |
| CN112995682B (en) * | 2021-04-21 | 2021-08-03 | 军事科学院系统工程研究院网络信息研究所 | Method and device for deploying and migrating video cloud service |
| CN113259359B (en) * | 2021-05-21 | 2022-08-02 | 重庆紫光华山智安科技有限公司 | Edge node capability supplementing method, system, medium and electronic terminal |
| CN113572821A (en) * | 2021-07-05 | 2021-10-29 | 山东师范大学 | Edge cloud node task cooperative processing method and system |
| CN113342478B (en) * | 2021-08-04 | 2022-02-01 | 阿里云计算有限公司 | Resource management method, device, network system and storage medium |
| CN113992675A (en) * | 2021-10-26 | 2022-01-28 | 云知声（上海）智能科技有限公司 | IOT cloud platform and edge gateway cooperative work method, system and storage medium |
| CN114070851A (en) * | 2021-11-15 | 2022-02-18 | 中国电信集团系统集成有限责任公司 | Service recovery method, storage medium and system based on MEC edge cloud |
| CN113992499B (en) * | 2021-11-16 | 2023-08-15 | 中电信数智科技有限公司 | Disaster recovery method, storage medium and system based on service dynamic migration |
| CN114338166A (en) * | 2021-12-29 | 2022-04-12 | 支付宝(杭州)信息技术有限公司 | Edge device risk processing method, device, equipment and cloud server |
| CN114301775B (en) * | 2021-12-31 | 2023-07-28 | 中国联合网络通信集团有限公司 | Method and device for managing stock service and computer readable storage medium |
| CN114301809B (en) * | 2021-12-31 | 2024-02-09 | 郑州云海信息技术有限公司 | Edge computing platform architecture |
| CN114401183A (en) * | 2022-01-17 | 2022-04-26 | 杭州瑞网广通信息技术有限公司 | Edge cloud disaster recovery system, method and device based on distributed cloud platform |
| CN114553726B (en) * | 2022-02-23 | 2023-06-02 | 深圳市众功软件有限公司 | Network security operation and maintenance method and system based on functions and resource levels |
| CN114760304A (en) * | 2022-03-30 | 2022-07-15 | 中国电信股份有限公司 | Computing power information processing method and system and computing power gateway |
| CN117640629A (en) * | 2022-08-17 | 2024-03-01 | 维沃移动通信有限公司 | Calculation task migration method, device and equipment |
| CN115361389B (en) * | 2022-10-20 | 2023-04-11 | 阿里巴巴（中国）有限公司 | Cloud computing instance creating method and device |
| CN116094923B (en) * | 2023-01-30 | 2023-08-25 | 杭州优云科技有限公司 | Gateway updating method and device after cloud instance migration and electronic equipment |
| CN116887220A (en) * | 2023-08-10 | 2023-10-13 | 谷梵科技(青田)有限公司 | V2X service high availability method, system, device and storage medium based on cloud edge cooperation |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8244874B1 (en) * | 2011-09-26 | 2012-08-14 | Limelight Networks, Inc. | Edge-based resource spin-up for cloud computing |
| CN101977242A (en) * | 2010-11-16 | 2011-02-16 | 西安电子科技大学 | Layered distributed cloud computing architecture and service delivery method |
| CN107018539A (en) * | 2016-01-27 | 2017-08-04 | 中兴通讯股份有限公司 | The ambulant processing method and processing device of application |
| CN107295699A (en) * | 2016-03-30 | 2017-10-24 | 中兴通讯股份有限公司 | The terminating approach and device of application example, using, edge calculations platform, node |
| CN109218455B (en) * | 2017-06-30 | 2021-04-09 | 华为技术有限公司 | Application instance address conversion method and device |
| CN109429284B (en) * | 2017-08-31 | 2020-08-25 | 华为技术有限公司 | Instance switching method, related device, instance switching system and storage medium |
| KR101926394B1 (en) * | 2017-09-19 | 2018-12-07 | 경희대학교 산학협력단 | System of cloud computing and method for detaching load in cloud computing system |
| CN108632813B (en) * | 2018-05-21 | 2021-05-28 | 北京邮电大学 | Mobility management method and system for mobile edge computing |
| CN109302483B (en) * | 2018-10-17 | 2021-02-02 | 网宿科技股份有限公司 | Application program management method and system |
| CN110266744A (en) * | 2019-02-27 | 2019-09-20 | 中国联合网络通信集团有限公司 | Location-based edge cloud resource dispatching method and system |
-
2019
- 2019-04-08 CN CN201910277465.4A patent/CN111800282B/en active Active
- 2019-04-08 CN CN202310139017.4A patent/CN116170316A/en active Pending
-
2020
- 2020-03-27 WO PCT/CN2020/081570 patent/WO2020207266A1/en active Application Filing
Also Published As
| Publication number | Publication date |
|---|---|
| CN111800282A (en) | 2020-10-20 |
| CN111800282B (en) | 2023-03-28 |
| WO2020207266A1 (en) | 2020-10-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111800282B (en) | Network system, instance management and control method, device and storage medium | |
| CN111800281B (en) | Network system, management and control method, equipment and storage medium | |
| CN111800283B (en) | Network system, service providing and resource scheduling method, device and storage medium | |
| CN115633050B (en) | Mirror image management method, device and storage medium | |
| WO2022161430A1 (en) | Edge cloud system, edge management and control method, management and control node, and storage medium | |
| CN113301078B (en) | Network system, service deployment and network division method, device and storage medium | |
| CN111800285B (en) | Instance migration method and device and electronic equipment | |
| CN113742031B (en) | Node state information acquisition method and device, electronic equipment and readable storage medium | |
| CN112035228A (en) | Resource scheduling method and device | |
| CN113296882A (en) | Container arranging method, device, system and storage medium | |
| CN113569987A (en) | Model training method and device | |
| CN111045745A (en) | Method and system for managing configuration information | |
| CN112910937B (en) | Object scheduling method and device in container cluster, server and container cluster | |
| WO2020063550A1 (en) | Policy decision method, apparatus and system, and storage medium, policy decision unit and cluster | |
| CN109697112B (en) | Distributed intensive one-stop operating system and implementation method | |
| CN112269647A (en) | Node scheduling, switching and coordinating method and corresponding device, equipment and medium thereof | |
| CN114301909B (en) | Edge distributed management and control system, method, equipment and storage medium | |
| CN115080309A (en) | Data backup system, method, storage medium, and electronic device | |
| CN116016644A (en) | Service request processing method, network device and computer readable storage medium | |
| CN113282396A (en) | Image processing method, system, device, computer equipment and storage medium | |
| CN113986662A (en) | Edge cluster monitoring method and system | |
| CN113553194A (en) | Hardware resource management method, device and storage medium | |
| CN113138717B (en) | Node deployment method, device and storage medium | |
| CN117369942A (en) | Method and system for arranging and automatically deploying application service resources | |
| CN114327752A (en) | Micro-service configuration method, device and equipment |
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 |