Computing power resource arrangement method, system and device and storage medium
By defining orchestration templates and instances, and establishing the association and mapping relationship between virtual instances and orchestration instances, the complexity of computing resource management and cross-platform consistency issues are resolved, enabling efficient and flexible resource management and operation.
Patent Information
- Application Number
- CN202511023931.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-24
- Publication Date
- 2025-11-07
AI Technical Summary
In existing technologies, the maintenance of computing resources is complex, involves a lot of repetitive work, and is difficult to understand and maintain; the resource structure is easily changed at will, which is not conducive to unified management and planning; and it is impossible to achieve a consistent experience across platforms.
By defining orchestration templates and instances, the association and mapping relationship between virtual instances and orchestration instances is established. Core and edge resource orchestration components are used to manage the lifecycle of virtual resources, achieving consistent management across platforms.
It improves resource utilization efficiency, reduces operation and maintenance costs, achieves a consistent management experience across platforms, and has good scalability and flexibility to adapt to changes in business needs.
Smart Images

Figure CN120909700A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application belongs to the technical field of edge computing, and particularly relates to an algorithm resource arrangement method, system, device and storage medium. BACKGROUND
[0002] With the development of 5G high-speed communication system, technologies such as virtual reality and artificial intelligence are gradually emerging and applied in practice. Human production and life are gradually inseparable from Internet, Internet of Things and other technological products. The amount of data generated is increasing, and the demand for real-time data analysis is increasing. Edge computing services can be physically close to data sources to provide faster and more reliable services. Through edge computing services, a large number of multi-cloud heterogeneous computing resources can be deployed.
[0003] In the prior art, open source tool Terraform is provided for support. The definition and configuration of infrastructure are abstracted into code, the resource definition is standardized, the template is written through a declarative language, and various computing power providers (such as cloud computing vendors) are connected through plug-ins, thereby providing a relatively simple way to configure cloud infrastructure and manage cloud resources.
[0004] The prior art has the following technical problems: 1. The prior art calls resources as individual functional modules, and once the resources need to be changed, the process must be re-written, resulting in complex maintenance, repeated work, and long-term use causing the system to be difficult to understand and maintain.
[0005] 2. The configuration file of the open source tool Terraform is lengthy and not uniform, and is difficult to reuse on different platforms. There is no distinction between templates and instances, which makes the resource structure prone to be changed at will, and is not conducive to planning and managing resource allocation as a whole.
[0006] 3. The existing arrangement technology directly operates virtual resources of a cloud computing platform, causing the arrangement logic to be closely coupled with the specific platform. It needs to rely on the management capabilities of each platform, which is difficult to uniformly manage resources and cannot achieve consistent experience across platforms, especially not suitable for scenarios such as edge computing that require a unified resource view. SUMMARY
[0007] The present application provides an algorithm resource arrangement method, system, device and storage medium, which aims to solve the technical problems of the prior art, such as complex maintenance, repeated work, long-term use causing the system to be difficult to understand and maintain, resource structure being prone to be changed at will, being not conducive to planning and managing resource allocation as a whole, and being unable to achieve consistent experience across platforms.
[0008] The technical solution of the present application to solve the above technical problems is as follows: an algorithm resource arrangement method, the method comprising: obtaining a business job, defining one or more orchestration templates through a core resource orchestration component; wherein the orchestration template represents the distribution of computing resource of the business job in a virtualization site and resource requirements; generating one or more orchestration instances based on the orchestration template, and creating an orchestration job corresponding to the orchestration instance through the core resource orchestration component; asynchronously executing the orchestration job through an edge resource orchestration component, and calling a virtual resource pool interface to create a virtual instance according to the orchestration job; establishing an association relationship between the virtual instance and the orchestration instance, and synchronizing state information of the virtual instance to element information of the orchestration instance; after the virtual instance is created, responding to the virtual instance through an edge virtualization platform, generating a virtual resource according to the virtual instance, and establishing a mapping relationship between the virtual instance and the virtual resource; based on the association relationship and the mapping relationship, managing the life cycle of the virtual instance and the virtual resource through the orchestration instance.
[0009] Further, the above also includes: when the orchestration instance is deleted or modified, creating a deletion or modification orchestration job corresponding to the deletion or modification orchestration instance through the core resource orchestration component; asynchronously executing the deletion or modification orchestration job through the edge resource orchestration component, and changing the state information of the corresponding virtual instance according to the deletion or modification orchestration job; responding to the change of the state information of the virtual instance through the edge virtualization platform, deleting or modifying the virtual resource that exists in the mapping relationship, and feeding back to the virtual instance that exists in the mapping relationship after the deletion or modification is completed; the virtual instance changes the state information according to the feedback information, and synchronously updates to the orchestration instance that exists in the association relationship after the change is completed, so that the element information of the orchestration instance is deleted or modified.
[0010] Further, the above-mentioned orchestration template includes: element information, association relationship and constraint relationship; the constraint relationship is used to limit the virtual resource.
[0011] Further, the above-mentioned element information includes: kind, unique identifier, configuration, metadata, computing property and existing property.
[0012] Further, the above uses a common label module to establish a label of the unique identifier of the orchestration instance for the virtual instance, so as to realize the establishment of the association relationship between the virtual instance and the orchestration instance; A tag module is used to establish a tag of a unique identifier of the virtual resource for the virtual instance, so as to establish a mapping relationship between the virtual instance and the virtual resource.
[0013] Further, when the arrangement instance a has an expansion requirement, a new arrangement template b is created by using the core resource arrangement component, wherein the arrangement template a includes an existing virtual network; A new arrangement instance b is generated based on the arrangement template b, and a new virtual instance is created according to the arrangement instance b, the new virtual instance is automatically added to the virtual network, and horizontal expansion of the computing resource of the arrangement instance a is realized. When there is a contraction requirement, the arrangement instance b generated by the arrangement template b is deleted, so as to recycle the virtual instance b and the virtual resource associated therewith and release the computing resource.
[0014] Further, the above also includes: When the arrangement instance has a migration requirement, the original arrangement instance on the original virtualization site is deleted, and a new arrangement instance is created on the target virtualization site based on the original arrangement template, so as to realize migration of the arrangement instance across virtualization sites.
[0015] In a second aspect, the present application also provides an arrangement system of computing resource to solve the above technical problem, comprising: A core resource arrangement component is configured to define one or more arrangement templates according to a business job, wherein the arrangement template represents distribution and resource requirement of the computing resource of the business job in a virtualization site; one or more arrangement instances are generated based on the arrangement template, and an arrangement job corresponding to the arrangement instance is created; An edge resource arrangement component is configured to asynchronously execute the arrangement job, create a virtual instance by calling a virtual resource pool interface according to the arrangement job; an association relationship between the virtual instance and the arrangement instance is established, and state information of the virtual instance is synchronized to element information of the arrangement instance; An edge virtualization platform is configured to respond to the virtual instance after the virtual instance is created, generate a virtual resource according to the virtual instance, and establish a mapping relationship between the virtual instance and the virtual resource; The core resource arrangement component is further configured to manage the life cycle of the virtual instance and the virtual resource through the arrangement instance based on the association relationship and the mapping association relationship.
[0016] In a third aspect, the present application also provides an electronic device, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the arrangement method of computing resource of the present application when executing the computer program.
[0017] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method for arranging computing power resources.
[0018] Compared with the prior art, the present application has the following advantages: 1. The present application uniformly manages and defines the computing power configuration required by the service through the arrangement template, so that the allocation, planning and measurement of computing power resources are more intuitive and efficient, thereby improving the resource utilization efficiency.
[0019] 2. The present application directly manages virtual instances and indirectly manages underlying virtual resources by using arrangement instances, so that the management mode of computing power resources is standardized and unified. This design effectively reduces the dependence on different cloud computing platforms, realizes consistent management experience across platforms, and significantly reduces the operation and maintenance cost.
[0020] 3. The present application has good scalability, and can dynamically increase or decrease resources without destroying the original resource topology relationship, so as to easily realize the horizontal expansion or contraction of the service, and adapt to the changing business requirements.
[0021] 4. The present application abstracts complex relational data structures through virtual instances, providing stronger expression ability for resource management. At the same time, virtual instances can be connected to various virtualization platforms through plug-ins, realizing the loose coupling between the resource management layer and the actual resources. This design not only improves the flexibility of the system, but also makes the management layer and the resource layer of edge computing completely independent, thereby significantly improving the development and operation and maintenance efficiency.
[0022] Other features and advantages of the present application will be described in the following description, and some will become apparent from the description, or will be understood by those skilled in the art. The purpose and other advantages of the present application can be achieved and obtained by the structure indicated in the specification, claims and drawings. BRIEF DESCRIPTION OF DRAWINGS
[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiment or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative labor.
[0024] Figure 1 Fig. 1 shows a flow diagram of a method for arranging computing power resources according to an embodiment of the present application; Figure 2A flowchart for deleting computing power resources according to an embodiment of the present application is shown. Figure 3 A flowchart for modifying computing power resources according to an embodiment of the present application is shown. Figure 4 A flowchart for expanding computing power resources according to an embodiment of the present application is shown. Figure 5 An electronic device structure according to an embodiment of the present application is shown. DETAILED DESCRIPTION
[0025] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.
[0026] Figure 1 A flowchart of a computing power resource arrangement method according to an embodiment of the present application is shown. As shown in Figure 1 The computing power resource arrangement method according to an embodiment of the present application includes, obtaining a business job, and defining one or more arrangement templates through a core resource arrangement component; wherein the arrangement template represents the distribution and resource demand of computing power resources of the business job in a virtualization site; generating one or more arrangement instances based on the arrangement template, and creating an arrangement job corresponding to the arrangement instance through the core resource arrangement component; asynchronously executing the arrangement job through an edge resource arrangement component, and calling a virtual resource pool interface to create a virtual instance according to the arrangement job; establishing an association relationship between the virtual instance and the arrangement instance, and synchronizing the state information of the virtual instance to the element information of the arrangement instance; after the virtual instance is created, responding to the virtual instance through an edge virtualization platform, generating a virtual resource according to the virtual instance, and establishing a mapping relationship between the virtual instance and the virtual resource; based on the association relationship and the mapping association relationship, managing the life cycle of the virtual instance and the virtual resource through the arrangement instance.
[0027] In this embodiment, the core resource arrangement component records and manages the life cycle of the arrangement template and the arrangement instance.
[0028] In this embodiment, the orchestration template is a resource configuration model or scheme designed according to the demand of a business for computing power resources. It defines how to deploy and configure the required computing, storage, network and other resources on a specific virtualization site to meet the running requirements of a business application.
[0029] Each orchestration template is constructed based on a fixed virtualization site, and all resources (such as virtual hosts, network configurations, etc.) defined in the template will be allocated and deployed to this specific virtualization site. The virtualization site can be understood as a kind of infrastructure environment providing virtualization services, such as a certain independent area in the data center of a cloud service provider.
[0030] Further, the above also includes: When the orchestration instance is deleted or modified, the core resource orchestration component creates a deletion or modification orchestration job corresponding to the deletion or modification of the orchestration instance; The edge resource orchestration component asynchronously executes the deletion or modification orchestration job, and changes the state information of the corresponding virtual instance according to the deletion or modification orchestration job; The edge virtualization platform responds to the change of the state information of the virtual instance, deletes or modifies the virtual resources that exist in the mapping relationship, and feeds back to the virtual instance that exists in the mapping relationship after the deletion or modification; The virtual instance changes the state information according to the feedback information, and synchronously updates to the orchestration instance that exists in the association relationship after the change is completed, so that the element information of the orchestration instance is deleted or modified.
[0031] In this embodiment, as shown in Figure 2 When the orchestration instance needs to be deleted, the core resource orchestration component generates an orchestration job for deleting the orchestration instance, and asynchronously executes the job. The core resource orchestration component consumes the job, and notifies the edge resource orchestration component to delete the corresponding virtual instance. The edge resource orchestration component updates the state of the virtual instance to "deleting" by calling the virtual resource pool interface, and synchronously changes the state to the core resource orchestration component. The core resource orchestration component continuously listens until it confirms that the virtual instance and its associated virtual resources have been deleted, at which time the orchestration job is marked as successfully ended. After the state of the virtual instance is changed to "deleting", the orchestration plug-in module in the edge resource orchestration component triggers an asynchronous task, which is responsible for deleting the actual virtual resources in the underlying virtualization platform. After the virtual resources are successfully deleted, the state of the virtual instance is updated again to reflect that its resources have been completely cleared, and this state change is synchronized to the resource element information in the orchestration instance to ensure data consistency.
[0032] In this embodiment, as shown in Figure 3As shown, when it is necessary to delete the orchestration instance, the modification process is similar to the deletion process, which is not described here again. It should be noted that the modification action is only for configuration information and attribute information. For example, the specifications of the virtual host, i.e., the CPU and the memory size, and the expansion of the virtual hard disk. The original resource structure and the relationship in the orchestration template will not be changed.
[0033] Further, the orchestration template described above comprises element information, a correlation relationship and a constraint relationship. The constraint relationship is used to limit the virtual resource.
[0034] In the embodiment, the virtual instance is logically abstracted into three basic components, which are used to uniformly express the resource information in the orchestration template. The element information represents a collection of the minimum constituent units of various types of virtual instances. Each "element" represents a specific virtual resource type, such as a virtual host, a virtual hard disk, a virtual network and the like. They are the most basic component units in the resource model.
[0035] The correlation relationship describes the connection or use relationship between different virtual instances. For example, a virtual host binds a virtual network card, a virtual network card accesses a virtual network, a virtual hard disk is mounted to a virtual host and the like. This relationship expresses how resources cooperate with each other to complete the business function.
[0036] The constraint relationship expresses the dependency or limitation condition between virtual instances. For example, a certain virtual router must be deployed on a virtual host with specific computing capability; or a certain virtual network can only be accessed by a virtual machine of a specified type and the like. This kind of relationship ensures that the resource deployment meets the compliance and functionality requirements of the business operation.
[0037] In the embodiment, a logic based on 'computing capability' is introduced to distinguish resources, which expresses whether the resource has computing capability. The resources with computing capability include virtual hosts, NFVs (such as virtual routers, load balancers, NAT gateways and the like), and the resources without computing capability include virtual hard disks, virtual network cards, virtual networks, EIPs and the like. A logic to distinguish 'existing resources' is introduced, which expresses whether the resource is an existing resource.
[0038] Further, the element information described above comprises a type, a unique identifier, a configuration, metadata, a computing property and an existing property.
[0039] In the embodiment, when the element is constructed, the element information described above is used for construction. For example: # elements { { "Category":"instance", "Substance":true, "ID":"5fdaee7c-fb54-11e5-87f1-52540004757c", "Options":{}, "Metadata":{ "memory":2048, "cpu":2, "instance_name":"test_vm", "image_id": "img-test1234" } }, { "Category": "volume", "ID": "5fdafb06-fb54-11e5-87f1-52540004757c", "Options":{}, "Metadata":{ "volume_name":"test_vol", "volume_type":0, "size":50 } }, { "Category":"vxnet", "ID":"6c7cf630-462c-11ef-a9a7-4b4743343bf3", "Origin":true, "Metadata":{ "vxnet_id":"vxnet-0", "vxnet_type":2 } } } There are three resources: virtual host (instance), virtual hard disk (volume), and virtual network (vxnet), determined by Category; Substance is bool type, expressing whether this resource has computing power, and only virtual host has computing power in the example; ID is the unique identifier of each resource in the orchestration template, which can be uuid; Options is used for configuration information extension, and some advanced functions will be used, such as: virtual router port forwarding configuration, VPN configuration, tunnel configuration, etc.; Metadata saves the most basic attributes of virtual resources, such as the attributes of virtual host: cpu, memory, operating system image, host name, etc., the attributes of virtual hard disk: hard disk name, hard disk type, hard disk size, etc., and the attributes of virtual network: network type, network id, etc.; Origin is bool type, expressing whether this resource is an existing resource, and vxnet-0 is an existing virtual network resource in the example.
[0040] When building the association relationship, the resource with computing power is expanded, and the resource without computing power is associated with it, and the mapping table relationship is established by ID. This is an example corresponding to the above elements: # relations { "5fdaee7c-fb54-11e5-87f1-52540004757c": [ "5fdafb06-fb54-11e5-87f1-52540004757c", "6c7cf630-462c-11ef-a9a7-4b4743343bf3" ] } Among them, the virtual resource with computing power is virtual host, and its ID is "5fdaee7c-fb54-11e5-87f1-52540004757c"; virtual hard disk ("5fdafb06-fb54-11e5-87f1-52540004757c") and virtual network ("6c7cf630-462c-11ef-a9a7-4b4743343bf3") are associated with virtual host and used by virtual host.
[0041] Constraint relationship is a fixed logic that describes the restriction conditions and constraint conditions between resources, which usually does not need to be directly embodied in the template. This is an example: # constrains { "instance": { "vxnet": { "vxnet_type:2": { "count":1 } } }, "volume": { "instance": { "volume_type:0": { "count":1 } } } } The expression rule is a condition that resource category 1 is used for resource category 2. The condition that a virtual host is used for a virtual network is that when the vxnet_type (virtual network type) is 2, the virtual host can only use 1 virtual network of this type and cannot use multiple virtual networks of this type. The condition that a virtual hard disk is used for a virtual host is that when the volume_type (virtual hard disk type) is 0, the virtual hard disk can only be used by 1 virtual host and cannot be used by multiple virtual hosts.
[0042] Further, the above uses a common tag module to establish a tag of a unique identifier of the orchestration instance for the virtual instance, to realize the establishment of the association relationship between the virtual instance and the orchestration instance. A common tag module is used to establish a tag of a unique identifier of the virtual resource for the virtual instance, to realize the establishment of the mapping relationship between the virtual instance and the virtual resource.
[0043] Further, when the orchestration instance a has an expansion requirement, a new orchestration template b is created by using a core resource orchestration component, wherein the orchestration template a includes an existing virtual network. A new orchestration instance b is generated based on the orchestration template b, and a new virtual instance is created according to the orchestration instance b, the new virtual instance is automatically added to the virtual network, and the horizontal expansion of the computing resource of the orchestration instance a is realized. When there is a contraction requirement, the orchestration instance b generated by the orchestration template b is deleted, to recover the virtual instance b and the virtual resource associated therewith, and to release the computing resource.
[0044] Further, the above further includes: When the orchestration instance has a migration requirement, the original orchestration instance on the original virtualization site is deleted, and a new orchestration instance is created on a target virtualization site based on the original orchestration template, to realize the migration of the orchestration instance across virtualization sites.
[0045] In this embodiment, as Figure 4As shown, when the business needs to be expanded, the resource structure in the existing orchestration instance is not directly modified, but a new orchestration template (such as orchestration template B) is created based on the existing resource structure, which contains the required resource topology relationship (such as VPC, virtual network, etc.).
[0046] A new orchestration instance b is generated based on the orchestration template B, thereby creating a new virtual resource (such as virtual host VM2), and the new resource is automatically added to the existing resource environment (such as vxnet1 under VPC1), realizing the expansion of the computing resource of the business.
[0047] When the business load decreases and needs to be scaled down, the orchestration instance B generated by the orchestration template can be deleted, and the corresponding virtual resource (such as VM2) can be recycled to release the computing resource without affecting the original resource structure.
[0048] When the computing resource of a virtualization site where a certain orchestration instance A is located is insufficient, the system determines to migrate it to another virtualization site with sufficient resources through a scheduling strategy.
[0049] First, the original orchestration instance A is deleted, and the associated virtual instance and virtual resource are all recycled. Then, a new orchestration instance B is created based on the original orchestration template and deployed to the target virtualization site. The new instance inherits the original resource configuration, realizes the seamless migration of the business, and maintains the consistency and standardization of resource management.
[0050] Based on the same principle as the method shown in Figure 1 The embodiment of the application also provides an orchestration system of computing resource, which comprises: A core resource orchestration component is configured to define one or more orchestration templates according to a business job; wherein the orchestration template represents the distribution and resource requirement of the computing resource of the business job in a virtualization site; one or more orchestration instances are generated based on the orchestration template, and an orchestration job corresponding to the orchestration instance is created; An edge resource orchestration component is configured to asynchronously execute the orchestration job, create a virtual instance by calling a virtual resource pool interface according to the orchestration job; establish an association relationship between the virtual instance and the orchestration instance, and synchronize the state information of the virtual instance to the element information of the orchestration instance; An edge virtualization platform is configured to respond to the virtual instance after the virtual instance is created, generate a virtual resource according to the virtual instance, and establish a mapping relationship between the virtual instance and the virtual resource. The core resource orchestration component is further configured to manage the life cycle of the virtual instance and the virtual resource through the orchestration instance based on the association relationship and the mapping association relationship.
[0051] In this embodiment, The modules of the core resource orchestration component include: A metadata management module is configured to uniformly manage the related data of the orchestration template and the orchestration instance, and is responsible for the operation and maintenance of the whole life cycle, including the processing procedures such as creation, update, deletion, etc.
[0052] The modules of the edge resource orchestration component include: An orchestration engine module is configured to uniformly schedule and manage the virtual instances in the virtual resource pool according to the resource configuration information defined by the orchestration instance. The module is responsible for maintaining the mapping relationship between the orchestration instance and the virtual instance, and through the control and adjustment of the state and deployment of the virtual instance, the desired resource state of the orchestration instance is ensured.
[0053] An orchestration plug-in module is configured to respond to the changes (such as creation, modification or deletion) of the virtual instance, and accordingly perform the corresponding virtual resource operation in the underlying virtualization platform. The module is designed in a factory mode, has good expansibility and adaptation ability, and can interface with various cloud platforms and heterogeneous virtualization environments, and realize the unified management and operation of various virtualization resources.
[0054] The computing resource orchestration system of the embodiments of the present application can execute the computing resource orchestration method provided by the embodiments of the present application, and the implementation principles are similar. The actions performed by each module and unit in the computing resource orchestration system in each embodiment of the present application correspond to the steps in the computing resource orchestration method in each embodiment of the present application. For detailed function description of each module of the computing resource orchestration system, please refer to the description of the corresponding computing resource orchestration method in the foregoing description, which will not be described here.
[0055] The computing resource orchestration system can be a computer program (including program code) running in a computer device, for example, the computing resource orchestration system is an application software; the application software can be used to execute the corresponding steps in the method provided by the embodiments of the present application.
[0056] The modules described in the embodiments of the present application can be realized by software or hardware. In some cases, the name of the module does not constitute a limitation on the module itself.
[0057] Based on the same principle as the method shown in the embodiments of the present application, an electronic device is also provided in the embodiments of the present application, which can include but is not limited to: a processor and a memory; the memory is configured to store a computer program; the processor is configured to execute the method shown in any embodiment of the present application by calling the computer program.
[0058] In one optional embodiment, an electronic device is provided, which can include but is not limited to:Figure 5 The electronic device shown includes a processor and a memory. The processor and the memory are connected, such as through a bus. Optionally, the electronic device can also include a transceiver, which can be used for data interaction, such as data transmission and / or data reception, between the electronic device and other electronic devices. It should be noted that in actual applications, the transceiver is not limited to one, and the structure of the electronic device does not constitute a limitation on the embodiments of the present application. Figure 5 The electronic device shown includes a processor and a memory. The processor and the memory are connected, such as through a bus. Optionally, the electronic device can also include a transceiver, which can be used for data interaction, such as data transmission and / or data reception, between the electronic device and other electronic devices. It should be noted that in actual applications, the transceiver is not limited to one, and the structure of the electronic device does not constitute a limitation on the embodiments of the present application.
[0059] The memory is used to store the application program code (computer program) for executing the scheme of the present application, and is controlled by the processor for execution. The processor is used to execute the application program code stored in the memory to realize the content shown in the foregoing method embodiments.
[0060] The electronic device can also be a terminal device, Figure 5 The electronic device shown is only an example and should not limit the function and use range of the embodiments of the present application.
[0061] The computer readable storage medium provided by the embodiments of the present application stores a computer program. When the computer program runs on a computer, the computer can execute the corresponding content in the foregoing method embodiments.
[0062] According to another aspect of the present application, a computer program product or computer program is also provided, which includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to make the computer device execute the method provided in the various implementation manners of the above embodiments.
[0063] It should be understood that the flowcharts and block diagrams in the drawings illustrate the possible implementation architectures, functions and operations of the methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module, a program segment or a part of code containing one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different order from that noted in the drawings. For example, two blocks indicated in succession can actually be executed substantially in parallel, and sometimes in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and the combination of blocks in the block diagrams and / or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.
[0064] The computer readable storage medium described above bears one or more programs, which, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiments.
[0065] The above description is merely the preferred embodiments of the present application and the explanation of the applied technical principles. It should be understood by those skilled in the art that the disclosed scope of the present application is not limited to the technical solutions formed by the specific combinations of the above technical features, and should also cover other technical solutions formed by any combinations of the above technical features or their equivalent features without departing from the disclosed concept. For example, the technical solutions formed by the mutual replacement of the above features and the technical features disclosed in the present application (but not limited to) with similar functions.
Claims
1. A method for arranging computing power resources, characterized in that, The method comprises: acquiring a business job, defining one or more arrangement templates through a core resource arrangement component; wherein the arrangement template represents the distribution and resource requirements of the computing power resources of the business job in a virtualization site; generating one or more arrangement instances based on the arrangement template, and creating an arrangement job corresponding to the arrangement instance through the core resource arrangement component; asynchronously executing the arrangement job through an edge resource arrangement component, and calling a virtual resource pool interface to create a virtual instance according to the arrangement job; establishing an association relationship between the virtual instance and the arrangement instance, and synchronizing the state information of the virtual instance to the element information of the arrangement instance; after the virtual instance is created, responding to the virtual instance through an edge virtualization platform, generating a virtual resource according to the virtual instance, and establishing a mapping relationship between the virtual instance and the virtual resource; based on the association relationship and the mapping relationship, managing the life cycle of the virtual instance and the virtual resource through the arrangement instance.
2. The computing resource orchestration method of claim 1, wherein, Further comprising: when the arrangement instance is deleted or modified, creating a deletion or modification arrangement job corresponding to the deletion or modification arrangement instance through the core resource arrangement component; asynchronously executing the deletion or modification arrangement job through the edge resource arrangement component, and changing the state information of the corresponding virtual instance according to the deletion or modification arrangement job; responding to the change of the state information of the virtual instance through the edge virtualization platform, deleting or modifying the virtual resource that exists in the mapping relationship, and feeding back to the virtual instance that exists in the mapping relationship after deletion or modification; the virtual instance changes the state information according to the feedback information, and synchronously updates to the arrangement instance that exists in the association relationship after the change is completed, so that the element information of the arrangement instance is deleted or modified.
3. The computing resource orchestration method of claim 2, wherein, The arrangement template comprises: element information, association relationship and constraint relationship; the constraint relationship is used to limit the virtual resource.
4. The computing resource orchestration method of claim 3, wherein, The element information comprises: category, unique identifier, configuration, metadata, computational property and existing property.
5. The computing power resource arrangement method of claim 4, wherein a common tag module is used to establish a tag of a unique identifier of the arrangement instance for the virtual instance, so as to establish the association relationship between the virtual instance and the arrangement instance; a common tag module is used to establish a tag of a unique identifier of the virtual resource for the virtual instance, so as to establish the mapping relationship between the virtual instance and the virtual resource.
6. The computing resource orchestration method of claim 2, wherein, Further comprising: when the arrangement instance a has expansion demand, a new arrangement template b is created by using the core resource arrangement component, wherein the arrangement template a comprises an existing virtual network; a new arrangement instance b is generated based on the arrangement template b, and a new virtual instance is created according to the arrangement instance b, the new virtual instance is automatically added to the virtual network, and the horizontal expansion of the computing power resources of the arrangement instance a is realized; when there is a capacity reduction demand, the arrangement instance b generated by the arrangement template b is deleted, so as to recycle the virtual instance b and the virtual resource associated therewith, and release the computing power resources.
7. The computing resource orchestration method of claim 4, wherein, Further comprising: When the orchestration instance has a migration requirement, the original orchestration instance on the original virtualization site is deleted, and a new orchestration instance is created on the target virtualization site based on the original orchestration template, thereby realizing the migration of the orchestration instance across virtualization sites.
8. An arrangement system of computing resource, characterized in that, The method comprises the following steps: The core resource orchestration component is configured to define one or more orchestration templates according to a business job; wherein the orchestration template represents the distribution and resource requirement of the computing resource of the business job in a virtualization site; one or more orchestration instances are generated based on the orchestration template, and an orchestration job corresponding to the orchestration instance is created; The edge resource orchestration component is configured to asynchronously execute the orchestration job, and invoke a virtual resource pool interface to create a virtual instance according to the orchestration job; an association between the virtual instance and the orchestration instance is established, and the state information of the virtual instance is synchronized to the element information of the orchestration instance; The edge virtualization platform is configured to respond to the virtual instance after the virtual instance is created, and generate a virtual resource according to the virtual instance, and establish a mapping relationship between the virtual instance and the virtual resource. The core resource orchestration component is further configured to manage the life cycle of the virtual instance and the virtual resource through the orchestration instance based on the association and the mapping relationship.
9. An electronic device, comprising: The computer storage medium stores a computer program, and the computer program is executed by the processor to realize the method in any one of claims 1-7.
10. A computer storage medium, characterized in that The computer storage medium stores a computer program, and the computer program is executed by the processor to realize the method in any one of claims 1-7.