WO2017035738A1

WO2017035738A1 - Resource management method and device

Info

Publication number: WO2017035738A1
Application number: PCT/CN2015/088608
Authority: WO
Inventors: 杨旭; 夏海涛; 余芳; 刘建宁
Original assignee: 华为技术有限公司
Priority date: 2015-08-31
Filing date: 2015-08-31
Publication date: 2017-03-09
Also published as: JP6555676B2; US20180191637A1; JP2018526916A; EP3337095A1; EP3337095A4; CN107005427A; BR112018003775A2

Abstract

Provided are a resource management method and device, comprising: determining, by a master orchestrator, a resource management in a management domain of a slave orchestrator needing to be performed by the slave orchestrator (S101); and transmitting a resource management instruction to the slave orchestrator (S102), wherein the resource management instruction is configured to instruct the slave orchestrator to execute the resource management in the management domain of the slave orchestrator needing to be performed by the slave orchestrator. The master orchestrator and the slave orchestrator respectively have different management domains. The invention can be applied to a resource management across NFVO management domains.

Description

Resource management method and device

Technical field

The present invention relates to the field of network communication technologies, and in particular, to a resource management method and apparatus.

Background technique

NFV (Network Function Virtualization) is a technology that telecom network operators implement some telecommunications network functions in general-purpose high-performance servers, switches, and storage by drawing on virtualization technologies in the IT field. This technology requires telecom network functions to be implemented in software, and can be run on general-purpose servers, switches, and storage hardware, while automating instantiation, elastic scaling, and migration operations as needed. At present, many dedicated network element devices in the telecommunication network, such as firewalls, routers, CG-NAT (Carrier Grade NAT, carrier-grade network address translation), can be virtualized by NFV technology.

Figure 1 shows the NFV end-to-end architecture, which mainly includes the following three parts:

First, VNF (Virtualized Network Function):

VNF refers to virtualized network functions, such as EPC (Evolved Packet Core) nodes (MME), SGW (Serving GateWay), PGW (Packet Data) Network GateWay (packet data network gateway), etc., corresponds to PNF (Physical Network Function) in the traditional network. NFV hopes that similar VNFs and PNFs will have the same functionality, performance and external interfaces. The VNF can be composed of multiple VNFCs (VNF Components, virtual network function components). Generally, a VNFC runs in a VM (Virtualized Machine). Therefore, in deployment, a VNF can contain one or more VMs.

EMS (Element Management System): Performs traditional FCAPS (Fault Management, Configuration Management, Account Management, Performance Management, Security Management, Fault Management, Accounting, Performance, Security Management) functions for the VNF.

Second, NFVI (NFV Infrastructure):

NFVI provides hardware and virtual resources for the entire system, consisting of hardware resources (including: computing, networking, storage), virtualization layer (virtualizing hardware resources into resource pools), and virtual resources (also including: computing, networking, storage) three parts).

MANO (Management and Orchestration, Management and Orchestration):

MANO consists mainly of three entities:

VIM (Virtualized Infrastructure Manager): The management unit of NFVI, which includes hardware resource management and virtual resource management.

NFVO (NFV Orchestrator, NFV Orchestrator): Responsible for lifecycle management of NS (Network Service, service unit composed of multiple VNFs, such as EPC), and resources of the entire NFV system (including hardware resources and software) Resources) for orchestration and management.

VNFM (VNF Manager): responsible for lifecycle management of VNF.

The OSS/BSS (Operation Support System/Business Support System) shown in FIG. 1 refers to the operator's OSS/BSS, which is not included in the NFV system component and belongs to the related external entity.

At present, the standardization work of NFV is focused on MANO. As shown in Figure 2, the detailed architecture of MANO is basically the same as in the previous section, but four new entities have emerged: NS Catalog (Network Service Catalog). , VNF Catalog (directory), NFV Instances (instance), NFVI Resources (resources), which are functional modules for storing NS, VNF information, software packages, and running status in MANO, where:

NS Catalog: Stores all NSD (NS Descriptor) information that is already on-board.

VNF Catalog: Stores all existing VNF Packages (packages, including VNFD (VNF Descriptor), virtual machine images, etc.).

NFV Instances: Stores status information of all running NS, VNF, and other instances, such as assigned network addresses, operation records, and so on.

NFVI Resources: Stores the status of all NFVI resources, including available/reserved/allocated NFVI resources.

In the actual NFV MANO application, the NFVO management domain and the carrier network domain are certain. Mapping relationship. For example, for operators in small and medium-sized countries, an NFVO management domain can be mapped to the carrier's national network; for operators in China, the United States, such as a superpower, an NFVO management domain may only be mapped to a provincial company. network of.

The inventors have found through research that in some application scenarios, for example, NFV technology is used in the enterprise network of a global enterprise, or VNF of the inactive band is selected for the VNF in the tsunami seismic activity zone area. When the band and the inactive band usually span different countries or span different provinces, the NS needs to be deployed in different NFVO management domains. As shown in FIG. 3, NFVO (NFVO1 and NFVO2) of two different management domains complete the deployment of NS across the NFVO domain through a horizontal interface (a thick line between NFVO1 and NFVO2 in FIG. 3). In the figure, VNF1, VNF2, VNF3, and VNF4 together form an NS, where VNFs 1-3 are deployed in the NFVO1 management domain, and VNF4 is deployed in the NFVO2 management domain.

Resource management in the NFV standard in the prior art involves only one NFVO management domain, and is not applicable to resource management across the NFVO management domain.

Summary of the invention

In view of this, the present invention provides a resource management method and apparatus for resource management across an NFVO management domain. The specific plan is as follows:

According to the first possible implementation manner of the first aspect of the present application, the application provides a resource management method, where the method includes:

The main choreographer determines resource management within the administrative domain of the slave scheduler that is required to be performed from the orchestrator;

Transmitting, to the slave scheduler, a resource management instruction, the resource management instruction, configured to instruct the slave orchestrator to perform resource management in an administrative domain of the slave orchestrator required to be performed by the slave orchestrator;

The main arranger and the slave arranger respectively have different management domains.

In conjunction with the second possible implementation of the first aspect, the resource management instruction is sent to the slave orchestrator, specifically:

An instruction to query the availability of resources within the administrative domain of the orchestrator from the orchestrator.

In conjunction with the third possible implementation of the first aspect, the resource management instruction is sent to the slave orchestrator, specifically:

An instruction to reserve resources from the orchestrator's administrative domain is sent to the slave scheduler.

In conjunction with the fourth possible implementation of the first aspect, the resource management instruction is sent to the slave orchestrator, specifically:

An application resource quota request is sent to the slave scheduler.

In conjunction with the fifth possible implementation of the first aspect, the resource management instruction is sent to the slave orchestrator, specifically:

Sending an adjustment resource quota request to the slave scheduler.

In conjunction with the sixth possible implementation of the first aspect, after the resource management instruction is sent to the slave orchestrator, the method further includes:

Receiving the resource management result fed back from the arranger.

According to the first possible implementation manner of the second aspect of the present application, the application provides another resource management method, where the method includes:

Receiving, from the orchestration, a resource management instruction sent by the main arranger, the resource management instruction is used to instruct the slave orchestrator to perform resource management in an administrative domain of the slave orchestrator that needs to be performed by the slave orchestrator;

Performing resource management within the administrative domain of the slave scheduler that is required by the slave orchestrator;

With reference to the second possible implementation of the second aspect, the receiving, by the orchestrator, the resource management instruction sent by the main arranger includes:

An instruction sent from the orchestrator to query the availability of the resources within the administrative domain of the orchestrator is received from the orchestrator.

With the third possible implementation of the second aspect, the performing resource management in the management domain of the slave orchestrator required by the slave orchestrator specifically includes:

Initiating an instruction from the orchestrator to a VIM (Virtualization Infrastructure Manager) within the administrative domain of the slave orchestrator to query for availability of resources within the administrative domain of the orchestrator;

Receiving the result of the query returned from the VIM in the administrative domain of the orchestrator.

With the fourth possible implementation of the second aspect, after the receiving the query result returned by the VIM in the domain to which the orchestrator belongs, the method further includes:

The query result is fed back to the main arranger.

With reference to the fifth possible implementation manner of the second aspect, the receiving, by the orchestrator, the resource management instruction sent by the main arranger includes:

An instruction sent from the orchestrator to reserve resources from the manager domain of the orchestrator is received from the orchestrator.

With reference to the sixth possible implementation of the second aspect, the performing source management in the management domain of the slave orchestrator required by the slave orchestrator specifically includes:

Initiating, from the orchestration, an instruction to reserve the resources in the administrative domain of the orchestrator from a VIM (Virtualization Infrastructure Manager) within the management domain of the slave orchestrator;

Receiving the reserved resource information returned by the VIM in the administrative domain of the orchestrator.

With the seventh possible implementation of the second aspect, after the receiving the reserved resource information returned by the VIM in the management domain of the orchestrator, the method further includes:

And feeding back the reserved resource information to the main orchestrator.

With reference to the eighth possible implementation manner of the second aspect, the receiving, by the orchestrator, the resource management instruction sent by the main arranger includes:

The slave scheduler receives an application resource quota request sent by the primary organizer.

With reference to the ninth possible implementation manner of the second aspect, the performing, by the slave orchestrator, the resource management in the management domain of the slave orchestrator specifically includes:

The slave scheduler sends the request resource quota request to the VIM in the management domain of the slave scheduler;

Receiving, from the orchestrator, a quota allocation size returned by the VIM in the management domain of the orchestrator;

The slave scheduler feeds back the quota allocation size to the primary orchestrator, and the primary orchestrator performs resource management on the management domain from the orchestrator after receiving the lifecycle management request according to the quota allocation size.

In conjunction with the tenth possible implementation of the second aspect, the slave arranger receives the primary organizer and sends The resource management instructions specifically include:

The slave scheduler receives an adjusted resource quota request sent by the primary organizer.

With reference to the eleventh possible implementation manner of the second aspect, the performing resource management in the management domain of the slave orchestrator by the slave orchestrator specifically includes:

The slave scheduler sends the adjusted resource quota request to a VIM in the management domain of the slave scheduler;

The slave arranger receives an adjustment result returned by the VIM in the management domain of the arranger.

According to a first possible implementation manner of the third aspect of the present application, the application provides a resource management apparatus, where the apparatus includes:

Determining a unit for the primary orchestrator to determine resource management within the administrative domain of the slave scheduler that is required to be performed from the orchestrator;

a sending unit, configured to send, to the slave orchestrator, a resource management instruction, where the resource management instruction is used to instruct the slave orchestrator to perform resource management in an administrative domain of the slave orchestrator that needs to be performed by the slave orchestrator ;

In conjunction with the second possible implementation of the third aspect, the sending unit is specifically configured to:

In conjunction with the third possible implementation of the third aspect, the sending unit is specifically configured to:

In conjunction with the fourth possible implementation of the third aspect, the sending unit is specifically configured to:

An application resource quota request is sent to the slave scheduler.

In conjunction with the fifth possible implementation of the third aspect, the sending unit is specifically configured to:

Sending an adjustment resource quota request to the slave scheduler.

In conjunction with the sixth possible implementation of the third aspect, the device further includes:

And a receiving unit, configured to receive the resource management result fed back from the orchestrator.

According to a first possible implementation manner of the fourth aspect of the present application, the application provides a resource management apparatus, where the apparatus includes:

a receiving unit, configured to receive, from the orchestrator, a resource management instruction sent by the main orchestrator, where the resource management instruction is used to instruct the slave orchestrator to perform an administrative domain within the management domain of the slave orchestrator that needs to be performed by the slave orchestrator Resource management;

An execution unit, configured to perform resource management within an administrative domain of the slave orchestrator required to be performed by the slave orchestrator;

In conjunction with the second possible implementation of the fourth aspect, the receiving unit is specifically configured to:

In conjunction with the third possible implementation of the fourth aspect, the execution unit is specifically configured to:

In conjunction with the fourth possible implementation of the fourth aspect, the apparatus further includes:

a first feedback unit, configured to feed back the query result to the main orchestrator.

In conjunction with the fifth possible implementation of the fourth aspect, the receiving unit is specifically configured to:

In conjunction with the sixth possible implementation of the fourth aspect, the execution unit is specifically configured to:

In conjunction with the seventh possible implementation of the fourth aspect, the apparatus further includes:

a second feedback unit, configured to feed back the reserved resource information to the primary orchestrator.

In conjunction with the eighth possible implementation of the fourth aspect, the receiving unit is specifically configured to:

In conjunction with the ninth possible implementation of the fourth aspect, the execution unit is specifically configured to:

Sending, by the scheduler, the application resource quota request to the management domain of the slave scheduler VIM;

With reference to the tenth possible implementation manner of the fourth aspect, the receiving unit is specifically configured to:

With reference to the eleventh possible implementation manner of the fourth aspect, the executing unit is specifically configured to: send, by the orchestrator, the adjustment resource quota request to a VIM in an administrative domain of the slave orchestrator;

It can be seen from the above technical solution that the resource management method and apparatus of the present application determines, by the main orchestration device, that resource management in the management domain from the orchestrator by the orchestrator is required, and the resource management instruction is sent to the slave orchestrator. The resource management instruction is used to instruct the slave orchestrator to perform resource management in an administrative domain of the slave orchestrator that needs to be performed by the slave orchestrator, wherein the master orchestrator and the slave orchestrator respectively have different management Domain, which can be applied to resource management across NFVO management domains.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

Figure 1 is a schematic diagram of an NFV end-to-end architecture;

2 is a schematic diagram of a detailed structure of a MANO;

FIG. 3 is a schematic diagram of an architecture of an NS deployed in different NFVO management domains;

4 is a flowchart of Embodiment 1 of a resource management method according to the present disclosure;

FIG. 5 is a flowchart of Embodiment 2 of a resource management method according to the present disclosure;

FIG. 6 is a schematic diagram of signaling interaction of Embodiment 1 of a resource management method according to the present disclosure;

FIG. 7 is a schematic diagram of signaling interaction of Embodiment 2 of a resource management method according to the present disclosure;

FIG. 8 is a schematic diagram of signaling interaction of Embodiment 3 of a resource management method according to the present disclosure;

FIG. 9 is a structural diagram of Embodiment 1 of a resource management apparatus according to the present disclosure;

FIG. 10 is a structural diagram of Embodiment 2 of a resource management apparatus according to the present disclosure;

11 is a structural diagram of a computing node of the present application.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The terms "comprising" and "having", and any variations thereof, are intended to cover a non-exclusive inclusion to include a series of units of processes, methods, systems, or products. The devices are not necessarily limited to those units, but may include other units not explicitly listed or inherent to such processes, methods, products, or devices.

For the convenience of description, the embodiment of the present invention takes a master arranger and a slave arranger as an example. However, based on the solution of the present application, an application scenario of a master arranger and a plurality of slave arrangers is also within the protection scope of the present application. It should be noted that the main arranger and the slave arranger have different management domains respectively. In addition, the main arranger and the slave arranger can be specifically NFVO. Of course, the main arranger and the slave arranger can also be other entities with resource management and orchestration functions, such as NSO (Network Service Orchestrator). ), RO (Resource Orchestrator), where NSO and RO are sub-arrangers obtained by splitting NFVO entities, NSO is responsible for management and orchestration of network services, and RO is responsible for management and orchestration of virtual resources. This application is not limited. The main arranger can be any one of NFVO, NSO, and RO, and the arranger can also be any one of NFVO, NSO, and RO.

Taking the main arranger and the slave arranger as NFVO as an example, as shown in Fig. 3, NFVO (NFVO1 and NFVO2) of two different management domains are connected through the horizontal direction (NFVO1 and NFVO2 in Fig. 3). Between the thick lines) the deployment of NS across the NFVO domain is completed. It should be noted that the master-slave relationship of the orchestrator is determined by the creator/leader of the NS across the NFVO domain. The same orchestrator may be the primary or the orchestrator for the different NSs it manages. Assuming that the OSS (or manager) in Figure 3 performs the NS1 instantiation process through NFVO1, NFVO1 is set as the master arranger, and NFVO2 is the slave arranger. In the figure, VNF1, VNF2, VNF3, and VNF4 form a common NS1, where VNF1~3 are deployed in the management domain of NFVO1, and VNF4 is deployed in the management domain of NFVO2.

The technical solutions of the present application will be described in detail by way of embodiments.

FIG. 4 is a flowchart of Embodiment 1 of a resource management method according to the present disclosure. The method is applied to a main arranger, and specifically includes the following steps:

S101. The main arranger determines resource management in the management domain of the slave arranger that needs to be performed from the orchestrator.

Taking Figure 3 as an example, NFV1 belongs to the management domain of NFVO1. It is assumed that NFV1 needs to be extended, but the resources in NFVO1 are insufficient. If the policy allows, NFVO1 may try to apply for resource expansion to NFVO2. The extended part, NFVO1, needs to be determined by NFVO2. Resource management within the NFVO2 management domain.

S102. Send a resource management instruction to the slave scheduler, where the resource management instruction is used to instruct the slave orchestrator to perform resource management in an administrative domain of the slave scheduler that needs to be performed by the slave orchestrator.

It should be noted that the resource management instruction sent to the slave scheduler may specifically be an instruction for querying the availability of resources in the management domain from the orchestrator, or reserved resources in the management domain from the orchestrator. Command, or, request a resource quota request, or adjust a resource quota request.

It should be further noted that after the execution of the slave scheduler requires resource management in the management domain of the slave arranger by the slave orchestrator, the resource management result is fed back from the orchestrator to the master orchestrator, editor-in-chief The queuer receives the above resource management result, so that the main arranger coordinates the resource usage when the NS is instantiated.

The resource management method of this embodiment determines, by the main orchestration device, resource management in the management domain of the slave orchestrator that is required to be performed from the orchestrator, and sends a resource management instruction to the slave orchestrator, where the resource management The instruction instruction is used to instruct the slave orchestrator to perform resource management in an administrative domain of the slave orchestrator that needs to be performed by the slave orchestrator, wherein the master orchestrator and the slave orchestrator respectively have different management Domain, which can be applied to resource management across NFVO management domains.

FIG. 5 is a flowchart of Embodiment 2 of a resource management method according to the present disclosure. The method is applied to a slave arranger, and specifically includes the following steps:

S201. Receive a resource management instruction sent by the main arranger from the orchestrator.

The resource management instruction is used to instruct the slave orchestrator to perform resource management within an administrative domain of the slave orchestrator that needs to be performed by the slave orchestrator.

Specifically, when the resource management is a resource query, the resource management instruction is an instruction for querying the availability of the resource in the management domain from the orchestrator. When the resource management is reserved for a resource, the resource management instruction is an instruction to reserve resources from an administrative domain of the orchestrator. Or, when the resource management is a management resource quota, the resource management instruction is an application resource quota request or an adjustment resource quota request.

S202. Perform resource management in an administrative domain of the slave scheduler that needs to be performed by the slave orchestrator;

When the resource management instruction is an instruction to query the availability of resources in the management domain from the orchestrator, the performing resource management in the management domain of the slave orchestrator required by the slave orchestrator includes the following steps :

Initiating an instruction from the orchestrator to query the VIM within the administrative domain of the orchestrator from the availability of resources within the administrative domain of the orchestrator;

Receiving the query result returned by the VIM in the management domain of the orchestrator;

The query result is fed back to the main arranger.

When the resource management instruction is an instruction to reserve the resource in the management domain from the orchestrator, the performing resource management in the management domain of the slave orchestrator required by the slave orchestrator includes the following steps:

Initiating, from the orchestration, an instruction to reserve the resources in the administrative domain of the orchestrator from the VIM in the management domain of the slave orchestrator;

Receiving the reserved resource information returned by the VIM in the management domain of the orchestrator;

Specifically, the reserved resource information may include a reserved resource ID, a resource type, a resource size, and the like.

And feeding back the reserved resource information to the main orchestrator.

When the resource management instruction is an application resource quota request, the performing resource management in the management domain of the slave orchestrator required by the slave orchestrator includes the following steps:

Among them, lifecycle management includes: instantiation, elastic scaling, termination, update, and the like. It can be VNF lifecycle management or NS lifecycle management.

When the resource management instruction is to adjust the resource quota request, the performing resource management in the management domain of the slave orchestrator required by the slave orchestrator includes the following steps:

The slave tuner receives an adjustment result returned by the VIM in the management domain of the orchestrator, such as an adjusted resource quota size or a changed resource quota size.

The slave scheduler feeds back the adjustment result to the master orchestrator, and the master arranger performs resource management on the management domain from the arranger after receiving the lifecycle management request according to the adjustment result.

The resource management method of the embodiment, by receiving, from the orchestrator, a resource management instruction sent by the main arranger, the resource management instruction is used to instruct the slave orchestrator to execute the slave scheduler that needs to be performed by the slave orchestrator Resource management within an administrative domain; wherein the primary orchestrator is divided into the slave orchestrator Do not have different management domains, can be applied to resource management across NFVO management domains.

Based on the above-disclosed embodiments of the present invention, the resource management method disclosed in the present invention will be described in detail below through the signaling interaction between the main arranger and the slave arranger.

FIG. 6 is a schematic diagram of signaling interaction in Embodiment 1 of a resource management method according to the present disclosure. In this embodiment, a main arranger is represented by P-NFVO, and is represented by an S-NFVO from an orchestrator. The VIM in the management domain is represented by VIM-1, and the VIM in the management domain of the orchestrator is represented by VIM-2. The VNFM in the management domain of the main arranger is represented by VNFM-1, and the VNFM in the management domain of the orchestrator uses VNFM-2. After the method is applied to receive the NS instantiation request, the method includes the following steps:

A0, P-NFVO receives the NS instantiation request.

A1, P-NFVO verifies the NS instantiation request.

A2, P-NFVO sends an instruction to VNFM-1 to check if the VNF exists.

A3, VNFM-1 sends the query result to P-NFVO.

A4, P-NFVO sends an instruction to VIM-1 to query the availability of resources within the administrative domain of P-NFVO or to reserve resources within the administrative domain of P-NFVO.

A5, VIM-1 queries the availability of resources within the administrative domain of the P-NFVO or reserves resources within the administrative domain of the P-NFVO.

A6, VIM-1 returns query results or reserved resource information to P-NFVO.

A7, P-NFVO sends an instruction to the S-NFVO to query the availability of resources within the administrative domain of the S-NFVO or to reserve resources within the administrative domain of the S-NFVO.

A8, S-NFVO sends an instruction to VNFM-2 to check whether the VNF exists.

A9, VNFM-2 sends the query result to S-NFVO.

It should be noted that A8 and A9 are optional processes in the whole process.

A10. The S-NFVO sends an instruction to the VIM-2 to query the availability of resources in the management domain of the S-NFVO or to reserve resources in the management domain of the S-NFVO.

S-NFVO receives the availability of resources within the administrative domain of the S-NFVO transmitted by the P-NFVO or After the instruction of the resources in the management domain of the S-NFVO is reserved, the instruction can be verified. The verification here includes the authentication of the P-NFVO and the verification of the correctness of the content of the instruction.

A11, VIM-2 queries the availability of resources within the administrative domain of the S-NFVO or reserves resources within the administrative domain of the S-NFVO.

A12, VIM-2 returns query result or reserved resource information to S-NFVO.

A13, S-NFVO returns query result or reserved resource information to P-NFVO.

The P-NFVO continues to perform the NS instantiation process according to the query result or the reserved resource information. Specifically, the local instantiation request may be sent to the VIM-1, and the cross-domain instantiation request is sent to the S-NFVO. It is not within the scope of the present application, so its specific implementation is not limited in this embodiment.

It should be noted that the P-NFVO may modify the reserved resource information returned by the S-NFVO to indicate that the resource described by the NFVO management domain belongs to another NFVO management domain. When resource allocation is performed based on this reserved resource information, P-NFVO needs to convert it back to the original value for S-NFVO domain identification.

FIG. 7 is a schematic diagram of signaling interaction of a resource management method according to Embodiment 2 of the present disclosure. In this embodiment, a main arranger is represented by P-NFVO, and is represented by an S-NFVO from an orchestrator. The VIM in the management domain is represented by VIM-1, and the VIM in the management domain of the orchestrator is represented by VIM-2. The VNFM in the management domain of the main arranger is represented by VNFM-1, and the VNFM in the management domain of the orchestrator uses VNFM-2. The method includes the following steps: Before the method is used to receive the NS instantiation request, such as when the P-NFVO establishes a connection with the S-NFVO, or during the last resource query/reservation process, the method includes the following steps:

B0, P-NFVO sends an application resource quota request to S-NFVO.

B1, S-NFVO sends a request for resource quota to VIM-2.

Before S-NFVO sends a request for resource quota request to VIM-2, S-NFVO verifies the application resource quota request, including the authentication of P-NFVO and the verification of the correctness of the requested content.

B2, VIM-2 allocates the corresponding quota.

VIM-2 assigns corresponding quotas based on policies or prior agreements.

B3, VIM-2 sends the quota allocation size to S-NFVO.

B4, S-NFVO sends a quota allocation size to P-NFVO.

Optionally, P-NFVO stores the quota allocation size on VIM-1, so that VIM-1 obtains global available resource information.

It should be noted that the use of resources in the subsequent NS instantiation process can directly obtain the information of available resources by querying the information of P-NFVO or VIM-1 without initiating related requests to the S-NFVO.

Further, it should be noted that when the quota demand changes (for example, if the quota is insufficient), the P-NFVO may initiate an adjustment resource quota request to the S-NFVO to change the quota size. FIG. 8 is a schematic diagram of signaling interaction in Embodiment 3 of a resource management method according to the present disclosure. In this embodiment, a main arranger is represented by P-NFVO, and is represented by an S-NFVO from an orchestrator. The VIM in the management domain is represented by VIM-1, and the VIM in the management domain of the orchestrator is represented by VIM-2. The VNFM in the management domain of the main arranger is represented by VNFM-1, and the VNFM in the management domain of the orchestrator uses VNFM-2. The method includes the following steps: Before the method is used to receive the NS instantiation request, such as when the P-NFVO establishes a connection with the S-NFVO, or during the last resource query/reservation process, the method includes the following steps:

C0, P-NFVO sends an adjustment resource quota request to the S-NFVO.

C1, S-NFVO sends an adjustment resource quota request to VIM-2.

Before the S-NFVO sends an adjustment resource quota request to the VIM-2, the S-NFVO verifies the adjustment resource quota request, including the authentication of the P-NFVO and the verification of the correctness of the requested content.

C2, VIM-2 adjusts resource quotas.

C3, VIM-2 sends the adjustment result to S-NFVO.

The modulation result is specifically an adjusted resource quota size or a changed resource quota size.

C4, S-NFVO sends the adjustment result to P-NFVO.

In this embodiment, the resource management is implemented through the quota mode, so that the cross-domain resource management is localized, and the repeated query is avoided every time the resource is used, which brings additional processing delay. In addition, the introduction of the quota also helps the S-NFVO to P. - The resource usage of the NFVO domain is clearly limited.

The method is described in detail in the above-disclosed embodiments of the present invention, and the method of the present invention can be used in many ways. Various forms of apparatus are implemented, and thus the present invention also discloses an apparatus, which will be described in detail below with reference to specific embodiments.

FIG. 9 is a structural diagram of Embodiment 1 of a resource management apparatus according to the present disclosure. The apparatus is applied to a main arranger, and specifically includes the following units:

A determining unit 11 for the primary orchestrator determines resource management within the administrative domain of the slave scheduler that is required to be performed from the orchestrator.

a sending unit 12, configured to send, to the slave orchestrator, a resource management instruction, where the resource management instruction is used to instruct the slave orchestrator to execute resources in an administrative domain of the slave orchestrator that needs to be performed by the slave orchestrator management.

The sending unit is specifically configured to:

Alternatively, an instruction to reserve resources from the manager domain of the orchestrator is sent to the slave scheduler.

Alternatively, send an application or adjust a resource quota request to the slave scheduler.

Alternatively, an adjustment resource quota request is sent to the slave scheduler.

It should be noted that the device further includes:

FIG. 10 is a structural diagram of Embodiment 2 of a resource management apparatus according to the present disclosure. The apparatus is applied to a slave arranger, and specifically includes the following units:

The receiving unit 21 is configured to receive, from the orchestrator, a resource management instruction sent by the main arranger, where the resource management instruction is used to instruct the slave orchestrator to perform an administrative domain of the slave orchestrator that needs to be performed by the slave orchestrator Resource management;

An execution unit 22, configured to perform resource management in an administrative domain of the slave scheduler that needs to be performed by the slave orchestrator;

The receiving unit is specifically configured to:

The execution unit is specifically configured to, from the orchestrator, an instruction to query a VIM (Virtualization Infrastructure Manager) in the management domain of the slave orchestrator for querying availability of resources in the management domain from the orchestrator;

Then the device further comprises:

Alternatively, the receiving unit is specifically configured to:

Then, the execution unit is specifically configured to:

Then, the device further includes:

Alternatively, the receiving unit is specifically configured to:

Then, the execution unit is specifically configured to:

The receiving unit is specifically configured to:

The execution unit is specifically configured to: send, by the orchestrator, the adjusted resource quota request to a VIM in an administrative domain of the slave orchestrator;

It should be noted that the specific function implementation of each unit is described in detail in the method embodiment, and is not described in detail in this embodiment. For details, refer to the related description of the method embodiment.

In addition, the embodiment of the present application further provides a computing node, which may be a host server including computing power, or a personal computer PC, or a portable computer or terminal, etc., and the specific embodiment of the present application is not correct. The specific implementation of the compute node is limited.

11 is a structural diagram of a computing node of the present application. As shown in FIG. 11, the computing node 1100 includes:

A processor 1110, a communication interface 1120, a memory 1130, and a bus 1140.

The processor 1110, the communication interface 1120, and the memory 1130 complete communication with each other through the bus 1140.

The processor 1110 is configured to execute the program 1132.

In particular, program 1132 can include program code, the program code including computer operating instructions.

The processor 1110 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

The memory 1130 is configured to store the program 1132. The memory 1130 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory. The program 1132 may specifically include:

The related method steps described in the corresponding embodiments of Figures 4-10.

For the specific implementation of each module in the program 1132, refer to the corresponding unit in the embodiment shown in FIG. 9-10. I will not go into details here.

The various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments may be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

A person skilled in the art will further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in a combination of electronic hardware or electronic hardware and computer software. To clearly illustrate the interchangeability of some of the hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the above description. Whether these functions are performed in hardware or a combination of hardware and software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented directly in hardware, a software module executed by a processor, or a combination of both. The software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but the scope of the invention is to be accorded

Claims

A resource management method, the method comprising:

The main choreographer determines resource management within the administrative domain of the slave scheduler that is required to be performed from the orchestrator;

Transmitting, to the slave scheduler, a resource management instruction, the resource management instruction, configured to instruct the slave orchestrator to perform resource management in an administrative domain of the slave orchestrator required to be performed by the slave orchestrator;

The main arranger and the slave arranger respectively have different management domains.
The method according to claim 1, wherein the sending the resource management instruction to the slave orchestrator comprises:

An instruction to query the availability of resources within the administrative domain of the orchestrator from the orchestrator.
The method according to claim 1, wherein the sending the resource management instruction to the slave orchestrator comprises:

An instruction to reserve resources from the orchestrator's administrative domain is sent to the slave scheduler.
The method according to claim 1, wherein the sending the resource management instruction to the slave orchestrator comprises:

An application resource quota request is sent to the slave scheduler.
The method according to claim 1, wherein the sending the resource management instruction to the slave orchestrator comprises:

Sending an adjustment resource quota request to the slave scheduler.
The method according to any one of claims 1 to 5, wherein after the resource management instruction is sent to the slave orchestrator, the method further comprises:

Receiving the resource management result fed back from the arranger.
A resource management method, the method comprising:

Receiving, from the orchestration, a resource management instruction sent by the main arranger, the resource management instruction is used to instruct the slave orchestrator to perform resource management in an administrative domain of the slave orchestrator that needs to be performed by the slave orchestrator;

Performing resource management within the administrative domain of the slave scheduler that is required by the slave orchestrator;

The main arranger and the slave arranger respectively have different management domains.
The method according to claim 7, wherein the receiving the resource management instruction sent by the main arranger from the orchestrator comprises:

An instruction sent from the orchestrator to query the availability of the resources within the administrative domain of the orchestrator is received from the orchestrator.
The method according to claim 8, wherein the performing resource management in the management domain of the slave orchestrator required by the slave orchestrator comprises:

Initiating an instruction from the orchestrator to a VIM (Virtualization Infrastructure Manager) within the administrative domain of the slave orchestrator to query for availability of resources within the administrative domain of the orchestrator;

Receiving the result of the query returned from the VIM in the administrative domain of the orchestrator.
The method according to claim 9, wherein after the receiving the query result returned by the VIM in the domain to which the orchestrator belongs, the method further includes:

The query result is fed back to the main arranger.
The method according to claim 7, wherein the receiving the resource management instruction sent by the main arranger from the orchestrator comprises:

An instruction sent from the orchestrator to reserve resources from the manager domain of the orchestrator is received from the orchestrator.
The method according to claim 11, wherein the performing source management in the management domain of the slave orchestrator required by the slave orchestrator comprises:

Initiating, from the orchestration, an instruction to reserve the resources in the administrative domain of the orchestrator from a VIM (Virtualization Infrastructure Manager) within the management domain of the slave orchestrator;

Receiving the reserved resource information returned by the VIM in the administrative domain of the orchestrator.
The method according to claim 12, wherein after the receiving the reserved resource information returned by the VIM in the management domain of the orchestrator, the method further comprises:

And feeding back the reserved resource information to the main orchestrator.
The method according to claim 7, wherein the receiving the resource management instruction sent by the main arranger from the orchestrator comprises:

The slave scheduler receives an application resource quota request sent by the primary organizer.
The method according to claim 14, wherein the performing resource management in the management domain of the slave scheduler required by the slave orchestrator comprises:

The slave scheduler sends the request resource quota request to the VIM in the management domain of the slave scheduler;

Receiving, from the orchestrator, a quota allocation size returned by the VIM in the management domain of the orchestrator;

The slave scheduler feeds back the quota allocation size to the primary orchestrator, and the primary orchestrator performs resource management on the management domain from the orchestrator after receiving the lifecycle management request according to the quota allocation size.
The method according to claim 7, wherein the receiving the resource management instruction sent by the main arranger from the orchestrator comprises:

The slave scheduler receives an adjusted resource quota request sent by the primary organizer.
The method according to claim 16, wherein the performing resource management in the management domain of the slave scheduler required by the slave orchestrator comprises:

The slave scheduler sends the adjusted resource quota request to a VIM in the management domain of the slave scheduler;

The slave arranger receives an adjustment result returned by the VIM in the management domain of the arranger.
A resource management device, characterized in that the device comprises:

Determining a unit for the primary orchestrator to determine resource management within the administrative domain of the slave scheduler that is required to be performed from the orchestrator;

a sending unit, configured to send, to the slave orchestrator, a resource management instruction, where the resource management instruction is used to instruct the slave orchestrator to perform resource management in an administrative domain of the slave orchestrator that needs to be performed by the slave orchestrator ;

The main arranger and the slave arranger respectively have different management domains.
The device according to claim 18, wherein the sending unit is specifically configured to:

An instruction to query the availability of resources within the administrative domain of the orchestrator from the orchestrator.
The device according to claim 18, wherein the sending unit is specifically configured to:

An instruction to reserve resources from the orchestrator's administrative domain is sent to the slave scheduler.
The device according to claim 18, wherein the sending unit is specifically configured to:

An application resource quota request is sent to the slave scheduler.
The device according to claim 18, wherein the sending unit is specifically configured to:

Sending an adjustment resource quota request to the slave scheduler.
The device according to any one of claims 18 to 22, further comprising:

And a receiving unit, configured to receive the resource management result fed back from the orchestrator.
A resource management device, characterized in that the device comprises:

a receiving unit, configured to receive, from the orchestrator, a resource management instruction sent by the main orchestrator, where the resource management instruction is used to instruct the slave orchestrator to perform an administrative domain within the management domain of the slave orchestrator that needs to be performed by the slave orchestrator Resource management;

An execution unit, configured to perform resource management within an administrative domain of the slave orchestrator required to be performed by the slave orchestrator;

The main arranger and the slave arranger respectively have different management domains.
The device according to claim 24, wherein the receiving unit is specifically configured to:

An instruction sent from the orchestrator to query the availability of the resources within the administrative domain of the orchestrator is received from the orchestrator.
The device according to claim 25, wherein the execution unit is specifically configured to:

Initiating an instruction from the orchestrator to a VIM (Virtualization Infrastructure Manager) within the administrative domain of the slave orchestrator to query for availability of resources within the administrative domain of the orchestrator;

Receiving the result of the query returned from the VIM in the administrative domain of the orchestrator.
The device of claim 26, wherein the device further comprises:

a first feedback unit, configured to feed back the query result to the main orchestrator.
The device according to claim 24, wherein the receiving unit is specifically configured to:

An instruction sent from the orchestrator to reserve resources from the manager domain of the orchestrator is received from the orchestrator.
The device according to claim 28, wherein the execution unit is specifically configured to:

Initiating, from the orchestration, an instruction to reserve the resources in the administrative domain of the orchestrator from a VIM (Virtualization Infrastructure Manager) within the management domain of the slave orchestrator;

Receiving the reserved resource information returned by the VIM in the administrative domain of the orchestrator.
The method of claim 29, wherein the apparatus further comprises:

a second feedback unit, configured to feed back the reserved resource information to the primary orchestrator.
The device according to claim 24, wherein the receiving unit is specifically configured to:

The slave scheduler receives an application resource quota request sent by the primary organizer.
The device according to claim 31, wherein the execution unit is specifically configured to:

The slave scheduler sends the request resource quota request to the VIM in the management domain of the slave scheduler;

Receiving, from the orchestrator, a quota allocation size returned by the VIM in the management domain of the orchestrator;

The slave scheduler feeds back the quota allocation size to the primary orchestrator, and the primary orchestrator performs resource management on the management domain from the orchestrator after receiving the lifecycle management request according to the quota allocation size.
The device according to claim 24, wherein the receiving unit is specifically configured to:

The slave scheduler receives an adjusted resource quota request sent by the primary organizer.
The method according to claim 33, wherein the execution unit is specifically configured to: the slave scheduler sends the adjusted resource quota request to a VIM in a management domain of the slave scheduler;

The slave arranger receives an adjustment result returned by the VIM in the management domain of the arranger.