Gateway management method and device, computer equipment, storage medium and program product

Abstract

The invention relates to a gateway management method and device, computer equipment, a storage medium and a program product. The method comprises the following steps: for each service element in a cloud network platform, determining a target resource bearing value of the service element according to a resource bearing value of the service element and the number of servers in the cloud network platform; determining at least one target service element from the service elements according to the target resource bearing value and the resource consumption value of each service element; and constructing an association relationship between the to-be-allocated tenant and the gateway corresponding to the at least one target service element. By adopting the method, the target service element of which the tenant bearing capacity is higher than the preset capacity threshold can be accurately determined from the service elements, so that only the to-be-allocated tenants can be allocated to the target service element of which the tenant bearing capacity is higher than the preset capacity threshold, and the tenants can be allocated to the target service element according to the tenant bearing capacity of each service element. And the tenant gateway distribution is flexibly carried out.

Description

Technical Field

[0001] The present application relates to the field of cloud computing technology, and in particular to a gateway management method, apparatus, computer equipment, storage medium and program product. Background Art

[0002] With the development of cloud computing technology, CNP (Cloud Network Platform) has emerged. CNP includes tenant gateways, general servers, and virtual network element servers. Among them, tenant gateways can be directly deployed using general servers, or tenant gateways can be deployed using virtual network element servers built on general servers. Usually, tenant gateways can be assigned to corresponding tenants so that tenants can access the cloud network platform through the tenant gateways.

[0003] In the conventional technology, when allocating tenants to tenant gateways, a polling sharing method is used to allocate and manage tenants. However, when allocating tenant gateways in the conventional technology, there is a problem that the allocation method is not flexible enough. Summary of the invention

[0004] Based on this, it is necessary to provide a gateway management method, apparatus, computer equipment, storage medium and program product that can improve the flexibility of tenant gateway allocation methods in response to the above technical problems.

[0005] In a first aspect, the present application provides a gateway management method, which is applied to a cloud network platform; the method comprises:

[0006] For each service element in the cloud network platform, determine a target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform;

[0007] Determining at least one target service element from each of the service elements according to the target resource carrying value and the resource consumption value of each of the service elements;

[0008] An association relationship is established between the tenant to be assigned and the gateway corresponding to the at least one target service element.

[0009] In one embodiment, determining the target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform includes:

[0010] Acquire an initial resource carrying value of the service element according to the resource carrying value of the service element and a preset first weight adjustment value;

[0011] The target resource carrying value is determined according to the initial resource carrying value and the number of the servers.

[0012] In one embodiment, the server includes a general server and a virtual network element server, and determining the target resource carrying value according to the initial resource carrying value and the number of the servers includes:

[0013] Acquire a resource carrying value of the general-purpose server according to the number of the general-purpose servers and a preset second weight adjustment value;

[0014] According to the number of the virtual network element servers and a preset third weight adjustment value, obtaining a resource carrying value of the virtual network element server;

[0015] The sum of the initial resource carrying value, the resource carrying value of the general server and the resource carrying value of the virtual network element server is determined as the target resource carrying value.

[0016] In one of the embodiments, determining at least one target service element from each of the service elements according to the target resource carrying value and the resource consumption value of each of the service elements includes:

[0017] Determining the resource surplus value of each of the service elements according to the target resource carrying value and the resource consumption value of each of the service elements;

[0018] The target service element is determined from the service elements according to the remaining value of the resources of the service elements.

[0019] In one embodiment, the method further comprises:

[0020] Obtaining version information of each of the service elements;

[0021] When it is determined that the version information is updated, the target resource carrying value of each of the service elements is updated according to the updated version information.

[0022] In one embodiment, the method further comprises:

[0023] If the remaining resource value of the virtual network element server in the cloud network platform is not greater than the preset resource threshold, and the remaining resource value of the general server corresponding to the virtual network element server is greater than the preset resource threshold, the virtual network element server is expanded and label information of the expanded virtual network element server is generated; the label information is used to indicate that the expanded virtual network element server has not been tested;

[0024] Testing the expanded virtual network element server to obtain a test result of the expanded virtual network element server; the test result is used to indicate whether the test of the expanded virtual network element server has passed;

[0025] The resource carrying value of each of the service elements is updated according to the capacity value of the virtual network element server after the capacity expansion that has passed the test.

[0026] In a second aspect, the present application also provides a gateway management device, including:

[0027] A first determination module is used to determine, for each service element in the cloud network platform, a target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform;

[0028] A second determining module, configured to determine at least one target service element from each of the service elements according to a target resource carrying value and a resource consumption value of each of the service elements;

[0029] A construction module is used to construct an association relationship between the tenant to be assigned and the gateway corresponding to the at least one target service element.

[0030] In a third aspect, the present application further provides a computer device, wherein the computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the method in any one of the embodiments of the first aspect are implemented.

[0031] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method in any one of the embodiments of the first aspect are implemented.

[0032] In a fifth aspect, the present application further provides a computer program product, wherein the computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the method in any one of the embodiments of the first aspect are implemented.

[0033] The above-mentioned gateway management method, device, computer equipment, storage medium and program product, for each service element in the cloud network platform, determines the target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform; determines at least one target service element from each service element according to the target resource carrying value and resource consumption value of each service element; and establishes an association relationship between the tenant to be assigned and the gateway corresponding to at least one target service element. The embodiment of the present application can perform index processing on each service element in the cloud network platform, that is, accurately determine the target resource carrying value of the service element, thereby, according to the accurate target resource carrying value and resource consumption value of each service element, accurately determine the target service element whose capacity to carry the tenant is higher than the preset capacity threshold from the service element, so that the tenant to be assigned can be assigned only to the target service element whose capacity to carry the tenant is higher than the preset capacity threshold, so that the tenant gateway allocation can be flexibly performed according to the capacity of each service element to carry the tenant. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0035] Figure 1 An application environment diagram of a gateway management method in an embodiment;

[0036] Figure 2 A schematic diagram of a flow chart of a gateway management method in an embodiment;

[0037] Figure 3 A schematic diagram of a flow chart of a target resource carrying value determination step in one embodiment;

[0038] Figure 4 is a schematic diagram of a capability view in one embodiment;

[0039] Figure 5 A schematic diagram of a flow chart of a gateway management method in another embodiment;

[0040] Figure 6 is a structural block diagram of a gateway management device in an embodiment;

[0041] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0043] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by technicians in the technical field to which this application belongs; the terms used herein are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" in the specification and claims of this application and the above-mentioned figure descriptions and any variations thereof are intended to cover non-exclusive inclusions.

[0044] In the description of the embodiments of the present application, the technical terms "first", "second", etc. are only used to distinguish different objects, and cannot be understood as indicating or implying relative importance or implicitly indicating the number, specific order or primary and secondary relationship of the indicated technical features. In the description of the embodiments of the present application, the meaning of "multiple" is more than two, unless otherwise clearly and specifically defined.

[0045] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0046] With the development of cloud computing technology, CNP (Cloud Network Platform) has emerged. CNP includes tenant gateway (TGW), general server and virtual network element server, among which tenant gateway can be directly deployed using general server, or tenant gateway can be deployed using virtual network element server built on general server. Usually, tenant gateway can be assigned corresponding tenants so that tenants can access cloud network platform through the tenant gateway.

[0047] In traditional technology, when allocating tenants to tenant gateways, a polling sharing method is used to allocate and manage tenants. However, when allocating tenant gateways in traditional technology, the size of tenants and the actual load of TGW are not taken into consideration, which leads to the possibility that tenants may still be allocated to TGWs that already carry many tenants. Therefore, when allocating tenant gateways in traditional technology, there is a problem that the allocation method is not flexible enough.

[0048] After introducing the background technology of the gateway management method provided by the embodiment of the present application, the following briefly describes the implementation environment involved in the gateway management method provided by the embodiment of the present application. The gateway management method provided by the embodiment of the present application can be applied to Figure 1 In the cloud network platform shown. The cloud network platform includes an SDN (Software Defined Network) controller 11, a tenant gateway (TGW) 12, a general server 13, and a virtual network element server 14, etc., wherein the tenant gateway 12 can be directly deployed using the general server 13, or the tenant gateway 12 can also be deployed using a virtual network element server 14 built on the general server 13. The SDN controller 11, the tenant gateway 12, the general server 13, and the virtual network element server 14 can communicate with each other, transmit data, and interact with information. Among them, each server in the cloud network platform can be an independent general server, or a server cluster or distributed system composed of multiple general servers, or a cloud server that provides cloud computing services. Exemplarily, each general server can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices, and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The head mounted device may be a virtual reality (VR) device, an augmented reality (AR) device, smart glasses, etc.

[0049] Those skilled in the art will understand that Figure 1 The structure shown in the figure is only a block diagram of a part of the structure related to the scheme of the present application, and does not constitute a limitation on the distributed storage system to which the scheme of the present application is applied. The specific distributed storage system may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0050] In one embodiment, Figure 2 As shown, a gateway management method is provided, which is applied to Figure 1 The cloud network platform in the example is used to illustrate, including the following steps:

[0051] S201, for each service element in the cloud network platform, determine a target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform.

[0052] Among them, service elements refer to the basic elements used by cloud computing resource pools to provide cloud network services. Service elements may include but are not limited to resource pools, general servers, physical network devices, virtual network element servers built on physical network element servers, etc. The resource pool is a collection of various software and hardware in the cloud network platform. General servers refer to general physical network element servers. Virtual network element servers refer to virtual TGWs built on general servers. Tenant Gateway (TGW) refers to the gateway corresponding to each tenant in the cloud network. The tenant gateway is used to realize the function of tenants accessing the network. Tenants refer to customer terminals in the cloud network platform. Of course, service elements can be formulated according to the actual cloud network implementation plan of a specific cloud service provider, the internal and external conditions of the resource pool, marketing strategies, operation and maintenance criteria, etc. The embodiments of this application do not limit service elements. For example, Table 1 is an example of each service element, the element index corresponding to each service element, and the quantitative basis for quantifying each element index in an exemplary embodiment.

[0053] Table 1

[0054]

[0055]

[0056] Based on the above Table 1, it can be seen that, by way of example, the factor indicators may include but are not limited to important capability indicators of the physical server itself (such as CPU, memory, network card, local storage, GPU, etc.), network-related resources (such as export bandwidth, internal business network bandwidth, remote storage resources, etc.), resource pool size, physical network equipment (such as underlying physical switches, routing equipment, etc.), the number of public network addresses of the configured resource pool, geographical distribution, main service objects, enterprise positioning of the resource pool, etc., virtualization strategy (such as deployment method, resource over-allocation ratio, different activation specifications, etc.), deployed operating system, network element version and other factor indicators.

[0057] Among them, the resource carrying value refers to the quantitative value of the indicator obtained after the preliminary index processing of the total capacity of the service element to carry tenants. The resource carrying value is used to represent the physical hard power of each service element. The target resource carrying value is used to represent the overall service capacity and health of the service element, that is, the target resource carrying value reflects the total capacity of the service element to carry tenants.

[0058] In the embodiment of the present application, in combination with the above-mentioned Table 1, for each service element in the cloud network platform, the cloud network platform can determine at least one element index corresponding to the service element, and the quantitative basis for quantifying each element index, and can index the service element according to at least one element index corresponding to the service element, and the quantitative basis corresponding to each element index, to obtain the resource carrying value of the service element. In addition, the cloud network platform can also obtain the number of servers in the cloud network platform. Thus, optionally, the cloud network platform can directly determine the target resource carrying value of the service element based on the resource carrying value of the service element and the number of servers in the cloud network platform; or, the cloud network platform can also comprehensively determine the target resource carrying value of the service element based on the resource carrying value of the service element and the number of servers in the cloud network platform, combined with the weight set by the administrator device in the cloud network platform. Of course, the embodiment of the present application does not limit the specific implementation method for determining the target resource carrying value of the service element.

[0059] S202: Determine at least one target service element from each service element according to the target resource carrying value and resource consumption value of each service element.

[0060] In the embodiment of the present application, optionally, the cloud network platform can sort each service element according to the target resource carrying value and resource consumption value of each service element to obtain the sorting result of each service element, so that at least one target service element can be determined from each service element according to the sorting result of each service element; or, the cloud network platform can also determine the resource surplus value of each service element according to the target resource carrying value and resource consumption value of each service element, so that at least one target service element can be determined from each service element according to the resource surplus value of each service element. Of course, the embodiment of the present application does not limit the specific implementation method for determining the target service element. Among them, the resource consumption value refers to the quantitative value of the resources consumed by the tenants in the service element, and the target service element refers to the service element in the service element whose capacity to carry tenants is higher than the preset capacity threshold.

[0061] S203: Establish an association relationship between the tenant to be assigned and the gateway corresponding to at least one target service element.

[0062] In the embodiment of the present application, the cloud network platform can use at least one target service element to deploy a tenant gateway, and can establish an association relationship between the tenant to be assigned and the tenant gateway corresponding to at least one target service element, so that the corresponding tenant can be assigned to the tenant gateway, so that the tenant can access the cloud network platform through the corresponding tenant gateway. Among them, the tenant to be assigned refers to a tenant who needs to access the cloud network platform through a tenant gateway, and the association relationship can be understood as a communication connection relationship between the tenant to be assigned and the tenant gateway corresponding to the target service element.

[0063] In the above-mentioned gateway management method, for each service element in the cloud network platform, the target resource carrying value of the service element is determined according to the resource carrying value of the service element and the number of servers in the cloud network platform; at least one target service element is determined from each service element according to the target resource carrying value and resource consumption value of each service element; and an association relationship between the tenant to be assigned and the gateway corresponding to at least one target service element is established. The embodiment of the present application can perform index processing on each service element in the cloud network platform, that is, the target resource carrying value of the service element can be accurately determined, thereby, according to the accurate target resource carrying value and resource consumption value of each service element, the target service element whose capacity to carry the tenant is higher than the preset capacity threshold can be accurately determined from the service element, so that the tenant to be assigned can be assigned only to the target service element whose capacity to carry the tenant is higher than the preset capacity threshold, so that the tenant gateway allocation can be flexibly performed according to the capacity of each service element to carry the tenant.

[0064] In one embodiment, a method for determining the target resource carrying value of a service element is provided, namely, "determining the target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform" in the above S201, such as Figure 3 As shown, including:

[0065] S301: Acquire an initial resource carrying value of a service element according to the resource carrying value of the service element and a preset first weight adjustment value.

[0066] In the embodiment of the present application, the cloud network platform can determine at least one element index corresponding to the service element, and the quantitative basis for quantifying each element index, and can perform index processing on the service element according to at least one element index corresponding to the service element, and the quantitative basis corresponding to each element index, to obtain the resource carrying value of the service element. In addition, the cloud network platform can also obtain the preset first weight adjustment value set by the administrator device in the cloud network platform. Thus, the cloud network platform can use the preset first weight adjustment value to adjust the resource carrying value of the service element and obtain the initial resource carrying value of the service element.

[0067] S302: Determine a target resource carrying value according to the initial resource carrying value and the number of servers.

[0068] In the embodiment of the present application, optionally, the cloud network platform can directly determine the target resource carrying value of the service element according to the initial resource carrying value of the service element and the number of servers in the cloud network platform; or, the cloud network platform can also comprehensively determine the target resource carrying value of the service element according to the initial resource carrying value of the service element and the number of servers in the cloud network platform, combined with the weight set by the administrator device in the cloud network platform. Of course, the embodiment of the present application does not limit the specific implementation method for determining the target resource carrying value of the service element.

[0069] In this embodiment, the initial resource carrying value of the service element can be accurately obtained based on the resource carrying value of the service element and the preset first weight adjustment value. Thus, the target resource carrying value used to characterize the total capacity of the service element to carry tenants can be accurately determined based on the initial resource carrying value and the number of servers.

[0070] In one embodiment, the server may include a general server and a virtual network element server. Based on this, an implementation method for determining the target resource carrying value is provided, that is, "determining the target resource carrying value according to the initial resource carrying value and the number of servers" in S302, including:

[0071] The resource carrying value of the general-purpose servers is obtained according to the number of general-purpose servers and a preset second weight adjustment value.

[0072] According to the number of virtual network element servers and a preset third weight adjustment value, a resource carrying value of the virtual network element server is obtained.

[0073] The sum of the initial resource carrying value, the resource carrying value of the general server and the resource carrying value of the virtual network element server is determined as the target resource carrying value.

[0074] In the embodiment of the present application, the above-mentioned servers may include but are not limited to general servers and virtual network element servers, and the cloud network platform may also obtain the preset second weight adjustment value and the preset third weight adjustment value set by the administrator device in the cloud network platform. Based on this, the cloud network platform can use the preset second weight adjustment value to adjust the number of general servers to obtain the resource carrying value of the general servers, and the cloud network platform can use the preset third weight adjustment value to adjust the number of virtual network element servers to obtain the resource carrying value of the virtual network element server. Of course, the embodiment of the present application does not limit the order of obtaining the resource carrying value of the general server and obtaining the resource carrying value of the virtual network element server. Thus, the cloud network platform can sum the initial resource carrying value, the resource carrying value of the general server, and the resource carrying value of the virtual network element server, and determine the sum of the initial resource carrying value, the resource carrying value of the general server, and the resource carrying value of the virtual network element server as the target resource carrying value.

[0075] For example, assuming that the service elements include a resource pool, a general server, and a virtual network element server, then the resource pool level capacity value Pr (i.e., the target resource carrying value) can be calculated based on all element indicators of the service elements, the capacity value Pp of the general server can be calculated based on the relevant element indicators of the general server, and the capacity value Pv of the virtual network element server can be calculated based on the relevant element indicators of the virtual network element server. The specific formula for determining the target resource carrying value is shown in the following formula (1).

[0076] Pr = ∑ fn(En) + w(HR) +∑ Cpn×wn(HPn) + ∑ Cvn×wn(HVn) (1)

[0077] Among them, Pr represents the overall capacity value of the resource pool (i.e., the target resource carrying value), fn(En) represents the service element capacity value obtained after the element index of the nth resource pool is indexed according to the corresponding quantitative basis (i.e., the resource carrying value of the nth service element), and the accumulation of each service element capacity value (i.e., ∑ fn(En)) constitutes the main part of the overall capacity of the resource pool, which is also the embodiment of the materialized capacity of the resource pool. Among them, the service elements corresponding to the resource pool include the resource pool, general server, virtual network element server (such as TGW virtual machine), controller and other system software and middleware types of service elements in Table 1. w(HR) represents the first weight adjustment value of the administrator device to adjust the weight of the overall capacity value of the resource pool. Cpn represents the number of general servers of the nth class, wn(HPn) represents the second weight adjustment value of the administrator device for weighted adjustment of the capacity value of the nth general server element, ∑ Cpn×wn(HPn) refers to the product of Cpn and wn(HPn) and the cumulative sum, representing the weighted adjustment of the capacity values ​​of all general physical servers by the administrator device, that is, the resource carrying value of the general server represents the adjusted capacity value of the general physical server. Cvn represents the number of virtual network element servers of the nth class, wn(HVn) represents the third weight adjustment value of the administrator device for weighted adjustment of the capacity value of the nth virtual network element server element, ∑ Cvn×wn(HVn) refers to the product of Cvn and wn(HVn) and the cumulative sum, representing the weighted adjustment of the capacity values ​​of all virtual network element servers by the administrator device, that is, the resource carrying value of the virtual network element server represents the adjusted capacity value of the virtual network element server. In addition, considering that the network element server (whether in physical or virtual form) may be used in a master-slave mode, the relevant capability values ​​can also be defined as a pair of physical or virtual network element servers according to business needs. Of course, the embodiments of the present application do not limit this.

[0078] In this embodiment, the resource carrying value of the general server is obtained according to the number of general servers and the preset second weight adjustment value; the resource carrying value of the virtual network element server is obtained according to the number of virtual network element servers and the preset third weight adjustment value; the sum of the initial resource carrying value, the resource carrying value of the general server and the resource carrying value of the virtual network element server is determined as the target resource carrying value. By indexing the service elements through the above method, it is possible to identify and quantify the important factors closely related to the cloud network among the complex internal and external related factors of the cloud resource pool, and form an intuitive quantitative view. The quantitative view is used to characterize the overall service capacity and health of the resource pool, and can provide insight into the efficient and continuous operation of the resource pool, and can automatically generate resource pool operation and maintenance suggestions and execution plans for reference and execution by operation and maintenance personnel.

[0079] In one embodiment, a method for implementing determining a target service element is provided, namely, the step of “determining at least one target service element from each service element according to the target resource carrying value and resource consumption value of each service element” in S202 above, including:

[0080] The resource surplus value of each service element is determined based on the target resource carrying value and resource consumption value of each service element.

[0081] According to the resource surplus value of each service element, a target service element is determined from among the service elements.

[0082] Among them, the resource consumption value refers to the quantitative value of the resources consumed by the tenants in the service elements. In the embodiment of the present application, the tenants can also be referred to as service objects, that is, it can be understood that the service objects are the profit source of the cloud service provider and the object that generates cloud service resource consumption. Of course, the service objects can be formulated according to the marketing strategies, operation and maintenance criteria, etc. of the specific cloud service provider, and the embodiments of the present application do not limit the service elements. For example, Table 2 is an example of each service object, the element index corresponding to each service object, and the quantitative basis for quantifying each element index in an exemplary embodiment.

[0083] Table 2

[0084]

[0085] In an embodiment of the present application, in combination with the above Table 2, the cloud network platform can determine at least one factor indicator corresponding to the service object, and a quantitative basis for quantifying each factor indicator, and can perform indicator processing on the service element according to at least one factor indicator corresponding to the service object and the quantitative basis corresponding to each factor indicator, so as to quantify the resources required to provide services that meet the agreed SLA (Service Level Agreement) requirements for specific users (ie, tenants), thereby obtaining the resource consumption value of each service object in the service element.

[0086] Exemplarily, the specific formula for determining the resource consumption value of the service object is shown in the following formula (2).

[0087] Ct = ∑gn(Tn) + w(HT) (2)

[0088] Among them, Ct represents the quantitative value of resources consumed to provide services that meet SLA requirements for a certain tenant. gn(Tn) represents the element resource consumption value obtained after the element indicator of the nth service object is indexed according to the corresponding quantitative basis. The accumulation of these element resource consumption values ​​constitutes the main part of the tenant's expected overall resource consumption, and objectively represents the importance of the tenant. w(HT) represents the administrator's device making differentiated adjustments to the tenant's resource consumption value based on the tenant's importance and volume.

[0089] Therefore, the cloud network platform can determine the resource surplus value of each service element according to the target resource carrying value and resource consumption value of each service element. The resource surplus value refers to the amount of resources that the service element can still carry tenants when it has already carried tenants. Exemplarily, the specific formula for determining the resource surplus value is shown in the following formula (3).

[0090] H(r,p,v) = P(r,p,v) - ∑Ct (3)

[0091] Among them, H(r,p,v) represents the health of the service element (i.e., the remaining value of resources), which can be at the resource pool level (Hr), the general server level (Hp), the virtual network element server level (Hv), or a combination of various service elements. P(r,p,v) represents the capacity value of the service element, which can be at the resource pool level (Pr), the general server level (Pp), the virtual network element server level (Pv), or a combination of various service elements. ∑Ct represents the resource consumption sum of all tenants carried in the service element (i.e., the resource consumption value), which can be at the resource pool level, the general server level, the virtual network element server level, or a combination of various service elements. It should be noted that the health of the service element needs to correspond to the capacity value of the service element and the resource consumption value of the service element.

[0092] Afterwards, the cloud network platform can determine the target service element whose resource surplus value is higher than the preset capacity threshold from each service element in real time according to the resource surplus value of each service element. In this way, the target service element can be dynamically adjusted when the tenant bearer is unbalanced (for example, the configuration of the tenant carried and the forwarding service increase sharply, the tenant service carried by other TGWs is vacated or the customer withdraws from the pool). Among them, the preset capacity threshold can be set according to the actual situation, and the embodiment of the present application does not limit the specific value of the preset capacity threshold.

[0093] Based on this, as the SDN system where the SDN controller is located runs for a long time, the tenants it carries are constantly changing, the tenant configuration needs to occupy the memory resources of the network element, and the tenant's traffic forwarding will occupy the CPU resources and internal and external bandwidth resources of the network element. Therefore, it is necessary to understand the actual load status of the current resource pool, general server and virtual network element server, and reasonably allocate the newly added tenants to the network element with lower load, or allocate the tenants to specific network elements according to the customer type of the tenant to meet specific SLA requirements. The embodiment of the present application can determine the health (Hr, Hp and Hv) of the resource pool, general server and virtual network element server by measuring their physical resource occupancy and software version capabilities. For example, for general servers and virtual network element servers, if the physical resources (such as CPU, memory, disk, network card bandwidth) of the general server or virtual network element server are occupied, the load of the general server or virtual network element server is higher, the health is lower, and the load of the newly added tenant is less likely to be carried; for TGWs with the same or similar loads, if the SDN-related software version capability corresponding to the TGW is lower, it means that the TGW does not give priority to carrying tenants. In this way, the embodiment of the present application adds the above-mentioned target resource carrying value, resource consumption value, resource remaining value and other indicators in the design of the SDN system. The SDN controller will decide which general-purpose servers and virtual network element servers will take on the new tenants according to the health of the general-purpose servers and virtual network element servers, thereby determining the target service elements, which is helpful to build an SDN system that meets the requirements of autonomy, dynamically improve the rationality of tenant resource allocation, reduce unnecessary tenant migration operations in the operation and maintenance stage, and enable higher operation and maintenance efficiency and quality, and reduce potential operation risks.

[0094] In this embodiment, the resource surplus value of each service element can be determined according to the target resource carrying value and resource consumption value of each service element. Thus, the target service element can be determined from among the service elements according to the resource surplus value of each service element. In this way, the appropriate network element resources can be better allocated to tenants in combination with the service capabilities and health of each service, and corresponding operation and maintenance suggestions can be provided regularly or on demand according to the dynamic operation of the resource pool.

[0095] In one embodiment, a method for updating the target resource carrying value of each service element is also provided, that is, the above-mentioned gateway management method further includes:

[0096] Get the version information of each service element.

[0097] When it is determined that the version information is updated, the target resource carrying value of each service element is updated according to the updated version information.

[0098] In the related art, due to the large number of online resource pool version combinations, some resource pools have temporary non-standard operation configurations, and the operation and upgrade are difficult. Therefore, R&D and operation and maintenance personnel cannot quickly predict the resource pool capabilities and potential problems. For problems that have occurred in historical time periods, R&D personnel need to review the relevant documents released by the version and query the known issues of the version in order to plan upgrade strategies and modify upgrade scripts. However, the document recording methods are diverse and scattered, and information integration is time-consuming and labor-intensive, easy to miss and forget, resulting in the online resource pool upgrade. Due to ignoring the existing non-standard operation configuration, the relevant configuration is lost after the upgrade. Among them, non-standard operation configuration refers to some non-standard settings and operations temporarily customized by tenants, which can be understood as temporary and informal implementations of customer needs or temporary fixes for known problems. Non-standard operation configuration will modify the current version information of service elements.

[0099] Based on this, it can be seen that the carrying and forwarding capabilities of the SDN system not only rely on the overall physical hardware capabilities of the resource pool, but also greatly rely on the software system architecture, operating system, middleware and other soft capabilities that implement software-defined network functions. Among them, the implementation of the control plane and data plane related components of the SDN system itself is the aspect with the greatest changes in the above soft capabilities, and is also an important output of cloud network service provider software development, and also a reflection of the market competitiveness of cloud network service providers. In the actual resource pool deployment and operation process, there are often different versions of the control plane and data plane. In the large number of resource pools and a large number of physical and virtual network elements in the resource pool, it is difficult for administrators to fully understand the software capabilities and known defects of the relevant SDN.

[0100] Therefore, when designing an SDN system, the embodiments of the present application may consider associating the versions of each component of the SDN system with the confirmed defects (BUGs) of the version, as a basis for calculating the capabilities of resource elements such as the controller and other system software and middleware, and network element software versions. For example, if there are more unresolved issues in the currently deployed version confirmation, the capacity values ​​of the relevant resource pools and network elements will be lower; under the same tenant resources and forwarding load, the health of the resource pools and network elements will also be lower. Based on this, a preferred strategy for carrying tenant network elements can be implemented, that is, avoiding allocating tenants to service elements with more problems.

[0101] In the embodiments of the present application, for example, Figure 4 As shown, Figure 4The figure is a schematic diagram of a capability view in an embodiment. After the new version is released, the SDN system can compare the deployed version in the current system with the latest stable version, form upgrade suggestions and dry run (DryRun) steps, and record the defects and their solutions and result verifications that occur during the development of the SDN system in the defect management system, and add updated version information and resource pool information in the defect management system for reference and evaluation by operation and maintenance personnel. It can also quickly decide which resource pools can meet the relevant requirements after the customer proposes the use requirements of relevant features. Among them, the defect management system can include but is not limited to the defect description, affected version, repair version, severity of the problem, quick recovery method, etc. in the defect record information. The defect management system is of great significance for operation and maintenance personnel to understand the capabilities of the software version, known defects and their recovery methods.

[0102] Thus, combined Figure 4 As shown, the information in the defect management system and the configuration management system can also be used to confirm problems and clean data to form a knowledge base, and the knowledge base can be used to measure the indicators of the SDN system itself for the software system architecture and functions, operating system, middleware and other soft capabilities. In this way, the cloud network platform can obtain the version information of each service element from the knowledge base and determine whether the version information is updated. In the case of determining that the version information is updated, the cloud network platform can update the target resource carrying value of each service element according to the updated version information. Furthermore, a comprehensive analysis can be conducted in combination with the overall physical hard capabilities and soft capabilities of the aforementioned resource pool to obtain the health of the resource pool and the capacity view of the resource pool, and it can be seen that the health of the resource pool changes with the service capabilities of each service element and the resource consumption of the carrying tenants.

[0103] In this embodiment, the version information of each service element can be obtained, and when it is determined that the version information is updated, the target resource carrying value of each service element is updated according to the updated version information. In this way, a knowledge base can be formed based on the defect management system and the configuration management system, and the target resource carrying value of each service element can be updated to obtain the health of the resource pool and the capacity view of the resource pool, so that the operation and maintenance team can understand the non-standard operations and their processing methods in a resource pool, and prevent upgrade operation problems caused by ignoring the existence of non-standard operations.

[0104] In one embodiment, there is also provided a method for implementing capacity expansion processing on a virtual network element server, that is, the above-mentioned gateway management method, further comprising:

[0105] If the remaining resource value of the virtual network element server in the cloud network platform is not greater than the preset resource threshold, and the remaining resource value of the general server corresponding to the virtual network element server is greater than the preset resource threshold, the virtual network element server is expanded and label information of the expanded virtual network element server is generated; the label information is used to indicate that the expanded virtual network element server has not been tested.

[0106] The virtual network element server after the capacity expansion is tested to obtain a test result of the virtual network element server after the capacity expansion; the test result is used to indicate whether the test of the virtual network element server after the capacity expansion is passed.

[0107] According to the capacity value of the virtual network element server after expansion that has passed the test, the resource carrying value of each service element is updated.

[0108] In the related technology, after the network element server is expanded, the tenant can establish an association with the network element server. However, the network element server may not have been tested at this time, which may lead to the risk of mutual influence between the test operation and the tenant's use operation. In addition, the expansion verification scenario of the network element server or TGW virtual machine is currently mainly carried out during the night upgrade cutover window, so the operation and maintenance and testing personnel need to stay up all night for verification, which not only affects the work efficiency of the relevant personnel during the day, but also affects the speed of expansion and grid connection to increase the service capacity of the resource pool.

[0109] Based on this, the cloud network platform in the embodiment of the present application can monitor in real time whether the remaining resource value of the virtual network element server in the cloud network platform is not greater than the preset resource threshold, and whether the remaining resource value of the general server corresponding to the virtual network element server is greater than the preset resource threshold. Among them, the embodiment of the present application does not limit the specific numerical value of the preset resource threshold. If it is determined that the remaining resource value of the virtual network element server in the cloud network platform is not greater than the preset resource threshold, and the remaining resource value of the general server corresponding to the virtual network element server is greater than the preset resource threshold, the cloud network platform can expand the capacity of the virtual network element server to obtain the expanded virtual network element server, and perform network element initialization operation on the expanded virtual network element server, and set the network connection state of the initialized network element to "f", so as to generate the label information of the expanded virtual network element server. Among them, the tag information is used to indicate that the virtual network element server after expansion has not been tested. The tag information may include but is not limited to the grid-connected flag field, that is, the grid-connected flag field can be added to the library table related to the general server or virtual network element server. At this time, the flag of the grid-connected flag field can be set to "f" (that is, not connected to the grid), and the default grid-connected flag of the existing network element can be set to empty. In addition, the logic of the controller to allocate tenant network elements can also be modified so that tenants can only be allocated or migrated to network elements with a grid-connected flag of empty or "t" (that is, connected to the grid). In this way, it can be ensured that only the expanded network elements that have passed the test, that is, connected to the grid, will be allocated to tenants.

[0110] In addition, a test tenant type can be added to the SDN controller. The tenant type can include but is not limited to a combination of shared or exclusive, virtual or physical tenant types, and a test flag can be added to the tenant to be tested corresponding to each tenant type. Thus, the cloud network platform can call the asynchronous check mechanism after NFV (Network Functions Virtualization) to obtain the running status of the expanded virtual network element server from NFV, so that the tenant to be tested carrying the test flag can be used to test the virtual network element server with the grid connection flag "f" in the expanded virtual network element server, thereby obtaining the test result of the expanded virtual network element server. Among them, the test process can include but is not limited to network element basic function verification, tenant migration verification, performance testing, etc., and the test result is used to indicate whether the test of the expanded virtual network element server has passed. Thus, the cloud network platform can determine the virtual network element server after the expansion that has passed the test, and update the grid connection flag in the tag information of the virtual network element server after the expansion that has passed the test to "t". In addition, the resource carrying value of each service element can be updated according to the capacity value of the virtual network element server after the expansion that has passed the test, so as to calculate and update the health of the virtual network element server itself and the health of the general physical server where the virtual network element server after the expansion is located. If it is determined that the test of the virtual network element server after the expansion has not passed, the cloud network platform can determine the subsequent processing strategy according to the error information fed back by the NFV side. For example, the processing strategy may include but is not limited to retrying, or generating an operation and maintenance alarm due to insufficient resources and inability to expand. In this way, the problem of only performing expansion operations but not performing feedback checks in the related technology, resulting in continuous expansion operations when there are no resources on the NFV side, thereby generating a large number of invalid operations and invalid data, can be avoided, and the burden of nighttime operation and verification of operation and maintenance personnel can be alleviated.

[0111] In this embodiment, a grid-connected flag field can be added to the library table related to the general server or virtual network element server, and the default grid-connected flag of the existing network elements can be set to empty. In addition, the logic of the controller to allocate tenant network elements can be modified so that tenants can only be allocated or migrated to network elements whose grid-connected flag is empty or "t" (i.e., indicating grid connection). In this way, it can be ensured that only the expanded network elements that have passed the test, i.e., after grid connection, will be allocated to tenants. And according to the capacity value of the expanded virtual network element server that has passed the test, the resource carrying value of each service element can be updated, so as to calculate and update the health of the virtual network element server itself and the health of the general physical server where the expanded virtual network element server is located in real time. By testing the expanded virtual network element server, not only can the problems caused by only performing expansion operations but not performing feedback checks in the related technology be avoided, but also the burden of nighttime operation and verification of operation and maintenance personnel can be alleviated.

[0112] Based on all the above embodiments, the present application also provides a complete gateway management method, which is applied to a cloud network platform, such as Figure 5 As shown, the method includes:

[0113] S501, for each service element in the cloud network platform, obtaining an initial resource carrying value of the service element according to the resource carrying value of the service element and a preset first weight adjustment value;

[0114] S502, obtaining a resource carrying value of the general-purpose server according to the number of general-purpose servers and a preset second weight adjustment value;

[0115] S503, acquiring a resource carrying value of the virtual network element server according to the number of virtual network element servers and a preset third weight adjustment value;

[0116] S504, determining the sum of the initial resource carrying value, the resource carrying value of the general server and the resource carrying value of the virtual network element server as the target resource carrying value;

[0117] S505, determining the resource surplus value of each service element according to the target resource carrying value and resource consumption value of each service element;

[0118] S506, determining a target service element from among the service elements according to the resource surplus value of each service element;

[0119] S507, building an association relationship between the tenant to be assigned and the gateway corresponding to at least one target service element;

[0120] S508, obtaining version information of each service element;

[0121] S509, when it is determined that the version information is updated, updating the target resource carrying value of each service element according to the updated version information;

[0122] S510, if the remaining resource value of the virtual network element server in the cloud network platform is not greater than the preset resource threshold, and the remaining resource value of the general server corresponding to the virtual network element server is greater than the preset resource threshold, the virtual network element server is expanded, and label information of the expanded virtual network element server is generated; the label information is used to indicate that the expanded virtual network element server has not been tested;

[0123] S511, testing the virtual network element server after the capacity expansion to obtain a test result of the virtual network element server after the capacity expansion; the test result is used to indicate whether the test of the virtual network element server after the capacity expansion has passed;

[0124] S512: Update the resource carrying value of each service element according to the capacity value of the virtual network element server after the capacity expansion that has passed the test.

[0125] In the above-mentioned gateway management method, for each service element in the cloud network platform, the target resource carrying value of the service element is determined according to the resource carrying value of the service element and the number of servers in the cloud network platform; at least one target service element is determined from each service element according to the target resource carrying value and resource consumption value of each service element; and an association relationship between the tenant to be assigned and the gateway corresponding to at least one target service element is established. The embodiment of the present application can perform index processing on each service element in the cloud network platform, that is, the target resource carrying value of the service element can be accurately determined, thereby, according to the accurate target resource carrying value and resource consumption value of each service element, the target service element whose capacity to carry the tenant is higher than the preset capacity threshold can be accurately determined from the service element, so that the tenant to be assigned can be assigned only to the target service element whose capacity to carry the tenant is higher than the preset capacity threshold, so that the tenant gateway allocation can be flexibly performed according to the capacity of each service element to carry the tenant.

[0126] In summary, the embodiment of the present application proposes an autonomous software-defined network design and operation and maintenance improvement method, which is used to make the operation mode of the cloud network platform more flexible and autonomous, improve the utilization efficiency of network resources in the cloud, reduce the daily workload of operation and maintenance personnel, and improve the efficiency and quality of operation and maintenance execution. Specifically, by defining and calculating the service capability indicators corresponding to the physical, geographical, social and enterprise-specific related attributes of the network element general server and TGW virtual machine, and dynamically calculating the health of each server after carrying tenant resources, the operation and maintenance personnel can timely understand the service capabilities, load conditions, and operation and maintenance strategies recommended by the system of the resource pool, so that the operation and maintenance personnel can achieve "one pool, one policy" operation and maintenance in the scenario of differentiated deployment methods and deployment versions. In addition, by combining the version information deployed in the resource pool, special configuration information, and the knowledge base formed based on the existing defect management system, a service capability and potential problem view at the resource pool level is formed, so that the operation and maintenance personnel can have a clear understanding of the capabilities of the resource pool before upgrading the resource pool, and will not miss certain specific non-standard configurations, thereby not affecting the customer's upgrade experience, improving the reliability of the upgrade operation, and reducing the probability of negative impact on users. In addition, by improving the design of the automatic expansion mechanism of network elements, the problem of no feedback on creation and deployment and inability to independently verify after creation, which affects the timing of grid connection and damages the automatic expansion capability, is solved.

[0127] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0128] Based on the same inventive concept, the embodiment of the present application also provides a gateway management device for implementing the gateway management method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more gateway management device embodiments provided below can refer to the limitations on the gateway management method above, and will not be repeated here.

[0129] In an exemplary embodiment, Figure 6 As shown, a gateway management device is provided, including: a first determination module 31, a second determination module 32 and a construction module 33, wherein:

[0130] The first determination module 31 is used to determine, for each service element in the cloud network platform, a target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform.

[0131] The second determining module 32 is configured to determine at least one target service element from among the service elements according to the target resource carrying value and the resource consumption value of each service element.

[0132] The construction module 33 is used to construct an association relationship between the tenant to be assigned and the gateway corresponding to at least one target service element.

[0133] In one embodiment, the first determining module 31 includes:

[0134] An initial resource carrying value acquiring unit, configured to acquire an initial resource carrying value of a service element according to the resource carrying value of the service element and a preset first weight adjustment value;

[0135] The first determining unit is used to determine a target resource carrying value according to the initial resource carrying value and the number of servers.

[0136] In one embodiment, the server includes a general server and a virtual network element server, and the first determining unit includes:

[0137] A first quantity acquisition subunit, configured to acquire a resource carrying value of the general-purpose server according to the number of the general-purpose servers and a preset second weight adjustment value;

[0138] The second quantity subunit is used to obtain the resource carrying value of the virtual network element server according to the number of virtual network element servers and a preset third weight adjustment value;

[0139] The first determining subunit is used to determine the sum of the initial resource carrying value, the resource carrying value of the general server and the resource carrying value of the virtual network element server as the target resource carrying value.

[0140] In one embodiment, the second determination module 32 includes:

[0141] A resource remaining value determining unit, configured to determine the resource remaining value of each service element according to the target resource carrying value and resource consumption value of each service element;

[0142] The second determining unit is used to determine a target service element from among the service elements according to the resource surplus value of each service element.

[0143] In one embodiment, the gateway management device further includes:

[0144] A version information acquisition module is used to obtain the version information of each service element;

[0145] The first updating module is used to update the target resource carrying value of each service element according to the updated version information when it is determined that the version information is updated.

[0146] In one embodiment, the gateway management device further includes:

[0147] The capacity expansion module is used to expand the capacity of the virtual network element server if the remaining resource value of the virtual network element server in the cloud network platform is not greater than the preset resource threshold, and the remaining resource value of the general server corresponding to the virtual network element server is greater than the preset resource threshold, and generate label information of the expanded virtual network element server; the label information is used to indicate that the expanded virtual network element server has not been tested;

[0148] The test module is used to test the virtual network element server after the capacity expansion to obtain the test result of the virtual network element server after the capacity expansion; the test result is used to indicate whether the test of the virtual network element server after the capacity expansion has passed;

[0149] The second updating module is used to update the resource carrying value of each service element according to the capacity value of the virtual network element server after the capacity expansion that has passed the test.

[0150] Each module in the above-mentioned gateway management device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.

[0151] In an exemplary embodiment, a computer device is provided. The computer device may be a server, or the computer device may be a terminal. The internal structure diagram thereof may be as follows: Figure 7As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a gateway management method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0152] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0153] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0154] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0155] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0156] It should be noted that the user information (including but not limited to relevant information of any of the tenants, tenants, or administrator devices, user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0157] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0158] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0159] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A gateway management method, characterized in that: The method is applied to a cloud network platform; the method comprises: For each service element in the cloud network platform, determine a target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform; Determining at least one target service element from each of the service elements according to the target resource carrying value and the resource consumption value of each of the service elements; An association relationship is established between the tenant to be assigned and the gateway corresponding to the at least one target service element.

2. The method according to claim 1, characterized in that Determining the target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform includes: Acquire an initial resource carrying value of the service element according to the resource carrying value of the service element and a preset first weight adjustment value; The target resource carrying value is determined according to the initial resource carrying value and the number of the servers.

3. The method according to claim 2, characterized in that The server includes a general server and a virtual network element server, and determining the target resource carrying value according to the initial resource carrying value and the number of the servers includes: Acquire a resource carrying value of the general-purpose server according to the number of the general-purpose servers and a preset second weight adjustment value; According to the number of the virtual network element servers and a preset third weight adjustment value, obtaining a resource carrying value of the virtual network element server; The sum of the initial resource carrying value, the resource carrying value of the general server and the resource carrying value of the virtual network element server is determined as the target resource carrying value.

4. The method according to any one of claims 1 to 3, characterized in that: The determining at least one target service element from each of the service elements according to the target resource carrying value and the resource consumption value of each of the service elements comprises: Determining the resource surplus value of each of the service elements according to the target resource carrying value and the resource consumption value of each of the service elements; The target service element is determined from the service elements according to the remaining value of the resources of the service elements.

5. The method according to claim 4, characterized in that The method further comprises: If the remaining resource value of the virtual network element server in the cloud network platform is not greater than the preset resource threshold, and the remaining resource value of the general server corresponding to the virtual network element server is greater than the preset resource threshold, the virtual network element server is expanded and label information of the expanded virtual network element server is generated; the label information is used to indicate that the expanded virtual network element server has not been tested; Testing the expanded virtual network element server to obtain a test result of the expanded virtual network element server; the test result is used to indicate whether the test of the expanded virtual network element server has passed; The resource carrying value of each of the service elements is updated according to the capacity value of the virtual network element server after the capacity expansion that has passed the test.

6. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Obtaining version information of each of the service elements; When it is determined that the version information is updated, the target resource carrying value of each of the service elements is updated according to the updated version information.

7. A gateway management device, characterized in that: The device comprises: A first determination module is used to determine, for each service element in the cloud network platform, a target resource carrying value of the service element according to the resource carrying value of the service element and the number of servers in the cloud network platform; A second determining module, configured to determine at least one target service element from each of the service elements according to a target resource carrying value and a resource consumption value of each of the service elements; A construction module is used to construct an association relationship between the tenant to be assigned and the gateway corresponding to the at least one target service element.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images