WO2024066625A1 - 租户管理方法、设备和存储介质 - Google Patents

租户管理方法、设备和存储介质 Download PDF

Info

Publication number
WO2024066625A1
WO2024066625A1 PCT/CN2023/105153 CN2023105153W WO2024066625A1 WO 2024066625 A1 WO2024066625 A1 WO 2024066625A1 CN 2023105153 W CN2023105153 W CN 2023105153W WO 2024066625 A1 WO2024066625 A1 WO 2024066625A1
Authority
WO
WIPO (PCT)
Prior art keywords
tenant
type
routing
target
users
Prior art date
Application number
PCT/CN2023/105153
Other languages
English (en)
French (fr)
Inventor
方超
修文飞
张琪
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2024066625A1 publication Critical patent/WO2024066625A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0645—Rental transactions; Leasing transactions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular to a tenant management method, device, and storage medium.
  • Cloud computing service platforms can provide relatively independent resource management capabilities for different tenants.
  • cloud computing service platforms can deploy a set of routing devices and firewalls within each tenant to provide routing services to tenants and achieve network isolation between different tenants.
  • Embodiments of the present application provide a tenant management method, device, and storage medium to provide a solution for improving routing utilization when the number of virtual machines in a tenant is uneven.
  • a tenant management method comprising: obtaining a tenant creation request, the tenant creation request carrying the number of users corresponding to a target tenant to be created; in response to the tenant creation request, when the number of users corresponding to the target tenant is less than a preset number of users, determining the type of the target tenant as a first type; when the type of the target tenant is the first type, creating the target tenant and associating the target tenant to a public routing tenant, the public routing tenant being used to provide routing services for tenants of the first type, and realizing network isolation between tenants of the first type through preset firewall rules.
  • a tenant management method comprising: obtaining a public routing tenant creation request; creating the public routing tenant in response to the public routing tenant creation request, and deploying routing equipment and a firewall for the public routing tenant; upon receiving a first type of tenant association request, establishing an association relationship between the public routing tenant and the first type of tenant, so as to provide routing services for the first type of tenant through the public routing tenant, and realizing network isolation between the first type of tenants through preset firewall rules, wherein the number of users corresponding to the first type of tenant is less than the preset number of users, and no routing equipment is deployed inside the first tenant.
  • a tenant management device which terminal includes a processor and a memory, the memory storing programs or instructions that can be run on the processor, and the program or instructions, when executed by the processor, implement the steps of the tenant management method described in the first aspect, or implement the steps of the tenant management method described in or the second aspect.
  • a readable storage medium on which a program or instruction is stored.
  • the steps of the tenant management method as described in the first aspect are implemented, or the steps of the tenant management method as described in or the second aspect are implemented.
  • a tenant creation request is obtained, where the tenant creation request carries the number of users corresponding to a target tenant to be created.
  • the type of the target tenant is determined to be a first type.
  • the target tenant is created and associated with a public routing tenant, where the public routing tenant is used to provide routing services for tenants of the first type, and network isolation between tenants of the first type is achieved through preset firewall rules.
  • FIG1 is a schematic flow chart of a tenant management method according to an embodiment of the present application.
  • FIG2 is a schematic diagram of a tenant management method according to an embodiment of the present application.
  • FIG3 is a schematic diagram of another tenant management method according to an embodiment of the present application.
  • FIG4 is a schematic flow chart of another tenant management method according to an embodiment of the present application.
  • FIG5 is a schematic flow chart of another tenant management method according to an embodiment of the present application.
  • FIG6 is a schematic flow chart of another tenant management method according to an embodiment of the present application.
  • FIG7 is a schematic diagram of another tenant management method according to an embodiment of the present application.
  • FIG8 is a schematic diagram of the structure of a tenant management device according to an embodiment of the present application.
  • FIG9 is a schematic diagram of the structure of another tenant management device according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of the structure of a tenant management device according to an embodiment of the present application.
  • the embodiments of this specification provide a tenant management method, device and storage medium.
  • the inventive concept of the present application is as follows: With the rapid development of computer technology, cloud computing service platforms have been deployed on a large scale, and cloud computing service platforms can provide relatively independent resource management capabilities for different tenants. For example, the cloud computing service platform can deploy a set of routing devices and firewalls inside each tenant to provide routing services for the tenants and achieve network isolation between different tenants.
  • the service provision capability of the routing device is usually large, and the number of virtual machines in different tenants is uneven, deploying a set of routing devices and firewalls for each tenant will cause a waste of routing resources. Therefore, a solution is needed to improve routing utilization when the number of virtual machines in the tenants is uneven.
  • the embodiments of this specification provide a technical solution that can solve the above-mentioned problems. For details, please refer to the following content.
  • an embodiment of the present specification provides a tenant management method
  • the execution subject of the method may be a server
  • the server may be a server of a cloud computing service platform
  • the server may be an independent server
  • a server cluster composed of multiple servers.
  • the method may specifically include the following steps:
  • the tenant creation request may carry the number of users corresponding to the target tenant to be created, and the number of users may be the number of virtual machines corresponding to the target tenant.
  • the server may obtain one or more tenant creation requests, and each tenant creation request may carry a corresponding number of virtual machines (ie, number of users).
  • the preset number of users can be determined by the server based on factors such as the preset business scenario and the service provision of the routing device. For example, the preset number of users can be determined according to the network response speed of the current business scenario. Specifically, the higher the network response speed of the business scenario, the smaller the corresponding preset number of users can be. Alternatively, the preset number of users can be determined according to the service provision of the routing device. Specifically, if the service provision of the routing device is 100, the preset number of users can be 50, 80, etc., which is less than the service provision of the routing device. In addition, there are many different ways to determine the preset number of users. Different preset numbers of users can be determined according to different actual application scenarios. The embodiments of this specification do not specifically limit this.
  • the server can also determine different preset numbers of users according to different business scenarios corresponding to the tenants, and determine the type of corresponding target tenant based on the preset number of users corresponding to the business scenario.
  • the tenant creation request may include a tenant creation request for target tenant 1 and a tenant creation request for target tenant 2.
  • the business scenario corresponding to target tenant 1 is the resource transfer business
  • the business scenario corresponding to target tenant 2 is the instant messaging business. Since the requirement of the instant messaging business on the network response speed is higher than that of the resource transfer business, the preset number of users 1 corresponding to the resource transfer business may be greater than the preset number of users 2 corresponding to the instant messaging business.
  • the type of target tenant 1 may be determined by the preset number of users 1, and the type of target tenant 2 may be determined by the preset number of users 2, that is, if the number of users of target tenant 1 is greater than the preset number of users 1, then the type of target tenant 1 may be determined to be the first type, and if the number of users of target tenant 2 is greater than the preset number of users 2, then the type of target tenant 2 may be determined to be the first type.
  • the tenant creation request can be sent to the corresponding staff for processing, and the tenant creation can be processed according to the processing result.
  • User creation processing and other operations can be sent to the corresponding staff for processing, and the tenant creation can be processed according to the processing result.
  • the target tenant is created and associated with the public routing tenant.
  • the public routing tenant can be used to provide routing services for the first type of tenants, and realize network isolation between the first type of tenants through preset firewall rules.
  • Routing devices and firewalls can be deployed in the public routing tenant to provide routing services for the first type of tenants whose number of users is less than the preset number of users through the routing devices in the public routing tenant, and realize network isolation between the first type of tenants through the firewall in the public routing tenant.
  • the preset firewall rules can be access control rules, which are composed of source address, destination address, source port, destination port, protocol, etc.
  • the firewall rules can realize blocking between subnets through source address, destination address, etc., that is, the public routing tenant can perform access control on the first type of tenants through preset firewall rules to realize network isolation between the subnets of the first type of tenants.
  • the public routing tenant does not provide advanced network functions.
  • the target tenant can be associated with the public routing tenant to provide routing services to the target tenant through the routing device in the public routing tenant. Since a firewall is deployed in the public routing, when the public routing tenant managed by the target tenant is also associated with other first type tenants, network isolation between the target tenant and other first type tenants can be achieved through preset firewall rules.
  • this method may cause a waste of routing device resources. For example, if a routing device can provide network services for 1,000 virtual machines, and the number of users corresponding to tenant 1 is 100 virtual machines, and the number of users corresponding to tenant 2 is 200 virtual machines, then this will cause the routing device corresponding to tenant 1 to be wasted. 90% of the resources of the device are wasted, and 80% of the resources of the routing device corresponding to tenant 2 are wasted.
  • routing services can be provided to multiple first-type tenants through the public routing tenant, thereby reducing the waste of routing resources. For example, as shown in FIG3 , assuming that both Tenant 1 and Tenant 2 are first-type tenants, and the number of users of Tenant 1 and Tenant 2 are both 500 virtual machines, the routing equipment deployed in the public routing tenant can also provide network services for 1,000 virtual machines. Obviously, providing routing services to multiple first-type tenants through public routing can reduce the resource waste rate of routing equipment and improve the utilization rate of routing resources.
  • the embodiment of the present specification provides a tenant management method, which obtains a tenant creation request, the tenant creation request carries the number of users corresponding to the target tenant to be created, responds to the tenant creation request, and determines the type of the target tenant as the first type when the number of users corresponding to the target tenant is less than the preset number of users, creates the target tenant when the type of the target tenant is the first type, and associates the target tenant with a public routing tenant, which is used to provide routing services for tenants of the first type, and implements network isolation between tenants of the first type through preset firewall rules.
  • routing services are provided for tenants of the first type whose number of users is less than the preset number of users through the public routing tenant, and the public routing tenant can implement network isolation between tenants of the first type through preset firewall rules, which can avoid the problem of routing resource waste caused by deploying a routing device for each tenant, save resource costs, and improve routing utilization.
  • an embodiment of the present specification provides a tenant management method
  • the execution subject of the method may be a server
  • the server may be a server of a cloud computing service platform
  • the server may be an independent server
  • a server cluster composed of multiple servers.
  • the method may specifically include the following steps:
  • the tenant creation request carries the number of users corresponding to the target tenant to be created.
  • the type of the target tenant may be determined according to the number of users corresponding to the target tenant. That is, as shown in FIG. 4 , after S102 , S104 to S408 may be continued to be executed, or S410 to S412 may be continued to be executed.
  • the type of the target tenant is determined to be the first type.
  • the internal network of the first type of tenant is a shared network
  • the same network address prefix can be used to make the internal network of the first type of tenant a shared network.
  • the network address prefix in the network subnet configuration of the first type of tenant can be set to network segment 192, etc., so that the network within the tenant is a shared network.
  • the virtual machines within the first type of tenant can access the external network through the shared network, and the addresses of each shared network need to be planned.
  • the shared networks of different tenants cannot overlap, that is, each first type of tenant uses its own subnet, and the subnet prefix of each first type of tenant is fixed.
  • the public routing tenant corresponding to the target tenant is determined among multiple public routing tenants to be associated, and the target tenant is associated to the public routing tenant corresponding to the target tenant.
  • the remaining service provision of each public routing tenant to be associated can be determined by the service provision of each public routing tenant to be associated and the number of users corresponding to the associated first type tenants of each public routing tenant to be associated, and then the public routing tenant corresponding to the target tenant is determined according to the number of users of the target tenant and the remaining service provision of each public routing tenant to be associated, and the target tenant is associated with the target tenant.
  • the public routing tenant corresponding to the user can be determined by the service provision of each public routing tenant to be associated and the number of users corresponding to the associated first type tenants of each public routing tenant to be associated, and then the public routing tenant corresponding to the target tenant is determined according to the number of users of the target tenant and the remaining service provision of each public routing tenant to be associated, and the target tenant is associated with the target tenant.
  • the public routing tenant corresponding to the user can be determined by the service provision of each public routing tenant to be associated and the number of users corresponding to the associated first type tenants of each public routing tenant to be associated, and then the public routing tenant corresponding to the target
  • the public routing tenants to be associated are public routing tenant 1 and public routing tenant 2
  • the remaining service provision of public routing tenant 1 is 300 virtual machines (that is, the service provision of public routing tenant 1 can be 1000, and the number of users corresponding to the associated first type of tenants is 700 virtual machines)
  • the remaining service provision of public routing tenant 2 is 400 virtual machines. Since the remaining service provision of public routing tenant 2 is greater than the remaining service provision of public routing tenant 1, it can be determined that public routing tenant 2 is the public routing tenant corresponding to the target tenant, and the target tenant can be associated with public routing tenant 2.
  • the above-mentioned method for determining the public routing tenant corresponding to the target tenant is an optional and feasible determination method.
  • the maximum service provision amount of each public routing tenant to be associated within a preset detection period (such as the maximum service provision amount of routing services provided by the public routing tenant to the associated first type of tenants in the past week) can also be obtained, and the public routing tenant corresponding to the target tenant can be determined based on the maximum service provision amount and the service provision amount of the public routing tenant.
  • Different determination methods can be selected according to different actual application scenarios, and the embodiments of this specification do not specifically limit this.
  • the number of users of the target tenant changes from 100 virtual machines to 500 virtual machines
  • the number of users corresponding to the changed target tenant that is, 500 virtual machines
  • the type of the target tenant is determined to be the second type.
  • the type of the target tenant and the association relationship with the public routing tenant can be kept unchanged. If the number of users corresponding to the changed target tenant is not less than the preset number of users, the type of the target tenant can be determined as the second type.
  • the type of the target tenant can be changed to the second type. If the preset number of users is 500 virtual machines, the type of the target tenant and the association relationship with the public routing tenant can be kept unchanged, that is, the type of the target tenant is still the first type.
  • the preset number of users corresponding to the changed business scenario can be obtained, and then the type of the target tenant can be determined based on the preset number of users corresponding to the changed business scenario and the number of users corresponding to the changed target tenant. For example, if the business scenario corresponding to the target tenant changes from resource transfer business to instant messaging business, the corresponding number of users can change from 600 virtual machines to 400 virtual machines. If the number of users corresponding to the changed target tenant is 500 virtual machines, it can be determined that the type of the target tenant is the second type.
  • routing services can be provided to users within the target tenant through the routing equipment deployed within the target tenant, and network isolation between users within the target tenant can be provided through a firewall, wherein the internal network of the second type of tenant is a non-shared network, and the network segments of the subnets can overlap.
  • the type of the target tenant is determined to be the second type.
  • the second type of tenant can provide routing for users through the routing equipment deployed within the tenant.
  • the network isolation between users within the second type of tenants is achieved by the service and preset firewall rules.
  • whether the number of users corresponding to the target tenant is less than the preset number of users can be used to determine whether the type of the target tenant is the first type or the second type, so as to provide different routing services for different types of tenants to save routing resources and improve routing resource utilization.
  • the embodiment of the present specification provides a tenant management method
  • the embodiment of the present specification provides a tenant management method
  • obtains a tenant creation request the tenant creation request carries the number of users corresponding to the target tenant to be created, responds to the tenant creation request, and when the number of users corresponding to the target tenant is less than the preset number of users, determines the type of the target tenant as the first type, creates the target tenant when the type of the target tenant is the first type, and associates the target tenant with a public routing tenant, the public routing tenant is used to provide routing services for the first type of tenants, and implements network isolation between the first type of tenants through preset firewall rules.
  • routing services are provided for the first type of tenants whose number of users is less than the preset number of users through the public routing tenant, and the public routing tenant can implement network isolation between the first type of tenants through the preset firewall rules, which can avoid the problem of routing resource waste caused by deploying a routing device for each tenant, save resource costs, and improve routing utilization.
  • an embodiment of the present specification provides a tenant management method
  • the execution subject of the method may be a server
  • the server may be a server of a cloud computing service platform
  • the server may be an independent server
  • a server cluster composed of multiple servers.
  • the method may specifically include the following steps:
  • a public routing tenant is created, and routing devices and firewalls are deployed for the public routing tenant.
  • the public routing tenant can only provide routing services, the public routing tenant may not provide advanced network functions, and corresponding routing devices and firewalls can be deployed for the public routing tenant according to the needs of actual business scenarios.
  • the number of users corresponding to the first type of tenant is less than the preset number of users, and no routing device is deployed inside the first tenant.
  • a public routing tenant may establish an association relationship with one or more first-type tenants. Upon receiving a first-type tenant association request, it may determine whether to establish an association relationship with the first-type tenant to be associated based on the amount of service provided by the routing devices deployed in the public routing tenant, the number of users of the associated first-type tenants, and the number of users of the first-type tenants to be associated.
  • the service capacity of the routing device deployed in the public routing tenant is 1,000 virtual machines
  • the number of users of the associated first type of tenants is 700 virtual machines
  • the number of users of the first type of tenants to be associated is not greater than 300 virtual machines
  • an association relationship can be established between the announced routing tenant and the first type of tenant to be associated. Since no routing device is deployed in the first type of tenant, routing services can be provided to multiple associated first type tenants through the routing device deployed in the public routing tenant, and network isolation between first type tenants can be achieved through preset firewall rules.
  • the embodiments of the present specification provide a tenant management method, which obtains a public routing tenant creation request, creates a public routing tenant in response to the public routing tenant creation request, and deploys routing devices and firewalls for the public routing tenant.
  • a first-type tenant association request is received, an association relationship is established between the public routing tenant and the first-type tenant, so as to provide routing services for the first-type tenant through the public routing tenant, and implement network isolation between the first-type tenants through preset firewall rules.
  • the number of users corresponding to the first-type tenant is less than the preset number of users, and no routing devices are deployed inside the first tenant.
  • routing services can be provided for the first-type tenant whose number of users is less than the preset number of users through the public routing tenant, and the public routing tenant can implement network isolation between the first-type tenants through the preset firewall rules, which can avoid the problem of routing resource waste caused by deploying a routing device for each tenant, save resource costs, and improve routing utilization.
  • an embodiment of the present specification provides a tenant management method
  • the execution subject of the method may be a server
  • the server may be a server of a cloud computing service platform
  • the server may be an independent server
  • a server cluster composed of multiple servers.
  • the method may specifically include the following steps:
  • a public routing tenant is created, and routing devices and firewalls are deployed for the public routing tenant.
  • the number of users corresponding to the first type of tenant is less than the preset number of users, and no routing device is deployed inside the first tenant.
  • a blocking rule with the source address as other intranets and the destination address as the network segment needs to be added on the firewall to achieve the function of network isolation between the first type of tenants.
  • firewall rules can be set to ensure network communication isolation between different first-type tenants and intercommunication between subnets within the same tenant.
  • the routing devices deployed in the public routing tenant are adjusted based on the changed number of users corresponding to the associated first type of tenant, so that the service provision of the adjusted public routing tenant is not less than the changed number of users corresponding to the associated first type of tenant.
  • the number of users corresponding to a tenant is not fixed. Therefore, in order to ensure the routing service quality of the tenant, it is possible to detect whether the public routing tenant can meet the routing service requirements of the associated first type of tenants, and when the public routing tenant cannot meet the routing service requirements of the associated first type of tenants, the routing devices deployed in the public routing tenant are adjusted, such as increasing the deployment of routing devices in the public routing tenant, or replacing the routing devices deployed in the public routing tenant with routing devices with a larger service provision, etc., so that the adjusted public routing tenant can meet the routing service requirements of the associated first type of tenants. Specifically, it is possible to determine whether the public routing tenant can meet the associated first type of tenant based on whether the number of users corresponding to the associated first type of tenant is greater than the service provision of the public routing tenant. The routing service requirements of tenants.
  • tenant 1 and tenant 2 are tenants of the first type, and tenant 1 and tenant 2 respectively establish association relationships with the public routing tenant, that is, the public routing tenant can provide routing functions for users of tenant 1 and tenant 2.
  • the routing device deployed in the public routing tenant can provide network services for 1,000 virtual machines. If the number of users of tenant 1 changes from 500 virtual machines to 600 virtual machines, the service provision of the routing device deployed in the public routing tenant is less than the number of users of tenant 1 and tenant 2, that is, the public routing tenant cannot meet the routing service requirements of tenant 1 and tenant 2.
  • the routing device deployed in the public routing tenant can be adjusted, such as deploying another routing device in the public routing tenant, that is, the service provision of the public routing tenant can be increased by adding routing devices, so that the service provision of the routing device deployed in the public routing tenant is not less than the number of users of tenant 1 and tenant 2.
  • the type of tenant may also change. Therefore, if there is a tenant whose tenant type has changed among the associated first-type tenants, the association between the tenant whose tenant type has changed and the public routing tenant can be disconnected, and the intranet interface corresponding to the tenant whose tenant type has changed and the blocking rules corresponding to the tenant whose tenant type has changed on the firewall can be deleted.
  • the association between the canceled tenant and the public routing tenant may be disconnected, and the corresponding public routing tenant may be deleted.
  • the embodiments of the present specification provide a tenant management method, which obtains a public routing tenant creation request, creates a public routing tenant in response to the public routing tenant creation request, and deploys routing devices and firewalls for the public routing tenant.
  • a first-type tenant association request is received, an association relationship is established between the public routing tenant and the first-type tenant, so as to provide routing services for the first-type tenant through the public routing tenant, and implement network isolation between the first-type tenants through preset firewall rules.
  • the number of users corresponding to the first-type tenant is less than the preset number of users, and no routing devices are deployed inside the first tenant.
  • routing services can be provided for the first-type tenant whose number of users is less than the preset number of users through the public routing tenant, and the public routing tenant can implement network isolation between the first-type tenants through the preset firewall rules, which can avoid the problem of routing resource waste caused by deploying a routing device for each tenant, save resource costs, and improve routing utilization.
  • the embodiments of the present specification provide a tenant management method
  • the execution subject of the method may be a server
  • the server may be a server of a cloud computing service platform
  • the server may be an independent server
  • a server cluster composed of multiple servers.
  • the server can receive a tenant creation request, which can be used to create a first type of tenant, a second type of tenant, or a public routing tenant, wherein if the tenant creation request can include a first type or type of tenant creation request, the tenant creation request can carry the number of users corresponding to the target tenant to be created.
  • the server may, when the number of users corresponding to the target tenant is less than the preset number of users, The type of the target tenant is determined to be the first type, and when the number of users corresponding to the target tenant is not less than the preset number of users, the type of the target tenant is determined to be the second type.
  • the tenant creation request is a request for creating a public routing tenant
  • a public routing tenant may be created, and routing devices and firewalls may be deployed for the public routing tenant.
  • the server can create corresponding first-type tenants, second-type tenants and public routing tenants according to different tenant creation requests, and establish an association relationship between the first-type tenants and the public routing tenants.
  • the specific tenant creation method and the method for establishing the association relationship between tenants can refer to the specific contents of the above-mentioned embodiments 1 to 4, which will not be repeated here.
  • tenant 1 and tenant 2 can be first-type tenants.
  • Tenant 1 and tenant 2 can access the external network through the routing device deployed in the public routing tenant, and the internal network of tenant 1 is a shared network, and the internal network of tenant 2 is also a shared network.
  • Tenant 3 and tenant 4 can be second-type tenants. Routing devices and firewalls can be deployed inside tenant 3 and tenant 4.
  • Tenant 3 and tenant 4 can directly access the external network through the internally deployed routing devices.
  • the internal networks of tenant 3 and tenant 4 are non-shared networks, and the network segments of subnets can overlap.
  • the tenants can be flexibly adjusted according to the specific changes to meet the actual usage needs of the tenants.
  • the type of tenant or the service volume of public routing tenants can be flexibly adjusted according to the changes in the number of users to ensure the stability of service provision of the entire cloud service system.
  • tenants can be divided into first-type tenants, second-type tenants, and public routing tenants.
  • Routing devices can be deployed in second-type tenants and public routing tenants, and network function management can be set for second-type tenants and public routing tenants, such as floating IP allocation function, firewall management function, etc., while public routing tenants can only be first-type tenants. It provides routing functions for tenants of the first type. It is not allowed to create resources such as virtual machine disks in public routing tenants, and it is not allowed to add security groups and rules in public routing tenants.
  • the first type of tenant does not need to deploy its own routing equipment, which can improve the resource utilization rate of the entire cloud computing service system and reduce system consumption costs.
  • the embodiments of the present specification provide a tenant management method, which can provide routing services for first-type tenants whose number of users is less than a preset number of users through a public routing tenant, and the public routing tenant can achieve network isolation between first-type tenants through preset firewall rules, thereby avoiding the problem of routing resource waste caused by deploying a routing device for each tenant, saving resource costs, and improving routing utilization.
  • the embodiment of this specification also provides a tenant management device, as shown in FIG8 .
  • the tenant management device includes: a request acquisition module 801, a first determination module 802 and a first creation module 803, wherein:
  • the request acquisition module 801 is used to acquire a tenant creation request, where the tenant creation request carries the number of users corresponding to the target tenant to be created;
  • a first determination module 802 is configured to, in response to the tenant creation request, determine the type of the target tenant as a first type when the number of users corresponding to the target tenant is less than a preset number of users;
  • the first creation module 803 is configured to, when the type of the target tenant is the first type, The target tenant is created and associated with a public routing tenant, where the public routing tenant is used to provide routing services for the first type of tenants and to achieve network isolation between the first type of tenants through preset firewall rules.
  • the device further includes:
  • a second determining module configured to determine the type of the target tenant as a second type when the number of users corresponding to the target tenant is not less than the preset number of users;
  • the second creation module is used to create the target tenant and deploy routing equipment and firewalls for the target tenant when the type of the target tenant is the second type.
  • the second type of tenant provides routing services to users through the routing equipment deployed inside the tenant, and realizes network isolation between users inside the second type of tenant through preset firewall rules.
  • the first creation module 803 is used to:
  • a public routing tenant corresponding to the target tenant is determined among multiple public routing tenants to be associated, and the target tenant is associated to the public routing tenant corresponding to the target tenant.
  • the device further includes:
  • a quantity acquisition module used for acquiring the number of users corresponding to the changed target tenant when the number of users of the target tenant changes
  • a third determining module configured to determine the type of the target tenant as the second type when the number of users corresponding to the changed target tenant is not less than the preset number of users;
  • the device deployment module is used to disconnect the association between the target tenant and the public routing tenant when the type of the target tenant is the second type, and to deploy routing equipment and a firewall for the target tenant.
  • the first type of tenant internal network is a shared network.
  • the embodiment of the present specification provides a tenant management device, which obtains a tenant creation request, the tenant creation request carries the number of users corresponding to the target tenant to be created, responds to the tenant creation request, and determines the type of the target tenant as the first type when the number of users corresponding to the target tenant is less than the preset number of users, creates the target tenant when the type of the target tenant is the first type, and associates the target tenant with a public routing tenant, which is used to provide routing services for tenants of the first type, and implements network isolation between tenants of the first type through preset firewall rules.
  • routing services are provided for tenants of the first type whose number of users is less than the preset number of users through the public routing tenant, and the public routing tenant can implement network isolation between tenants of the first type through preset firewall rules, which can avoid the problem of routing resource waste caused by deploying a routing device for each tenant, save resource costs, and improve routing utilization.
  • the embodiment of this specification also provides a tenant management device, as shown in FIG. 9 .
  • the tenant management device includes: a request acquisition module 901, a tenant creation module 902 and a relationship establishment module 903, wherein:
  • the request acquisition module 901 is used to acquire a public routing tenant creation request
  • a tenant creation module 902 configured to create the public routing tenant in response to the public routing tenant creation request, and deploy routing devices and firewalls for the public routing tenant;
  • the relationship establishment module 903 is used to establish an association relationship between the public routing tenant and the first type of tenant when receiving a first type of tenant association request, so as to provide routing services for the first type of tenant through the public routing tenant and establish an association relationship between the public routing tenant and the first type of tenant through the preset firewall rules.
  • Network isolation is achieved between tenants of the first type, the number of users corresponding to the tenants of the first type is less than the preset number of users, and no routing device is deployed inside the first tenants.
  • the device further includes:
  • a device adjustment module is used to adjust the routing devices deployed in the public routing tenant based on the changed number of users corresponding to the associated first type of tenants when the number of users corresponding to the associated first type of tenants is greater than the service provision of the public routing tenant, so that the service provision of the adjusted public routing tenant is not less than the changed number of users corresponding to the associated first type of tenants.
  • the relationship establishment module 903 is used to:
  • an intranet interface corresponding to the first type of tenants is added to the public routing tenant, and a blocking rule corresponding to the intranet interface is added to the firewall to achieve network isolation between the first type of tenants through the blocking rule.
  • the device further includes:
  • a relationship disconnection module is used to disconnect the association between the tenant whose tenant type has changed and the public routing tenant when there is a tenant whose tenant type has changed among the associated first type tenants, and to delete the intranet interface corresponding to the tenant whose tenant type has changed, as well as the blocking rules on the firewall corresponding to the tenant whose tenant type has changed.
  • the data type of the business data determines the disturbance data used to attack the business data.
  • the embodiment of the present specification provides a tenant management device, which obtains a public routing tenant creation request, creates a public routing tenant in response to the public routing tenant creation request, and deploys routing devices and firewalls for the public routing tenant.
  • a tenant management device which obtains a public routing tenant creation request, creates a public routing tenant in response to the public routing tenant creation request, and deploys routing devices and firewalls for the public routing tenant.
  • An association relationship is established between the tenant and the first type of tenant, so that routing services are provided to the first type of tenant through the public routing tenant, and network isolation between the first type of tenants is achieved through preset firewall rules.
  • the number of users corresponding to the first type of tenant is less than the preset number of users, and no routing equipment is deployed inside the first tenant.
  • routing services can be provided to the first type of tenant whose number of users is less than the preset number of users through the public routing tenant, and the public routing tenant can achieve network isolation between the first type of tenants through preset firewall rules, which can avoid the problem of routing resource waste caused by deploying a routing device for each tenant, save resource costs, and improve routing utilization.
  • the embodiment of this specification also provides a tenant management device, as shown in FIG10 .
  • the tenant management device may have relatively large differences due to different configurations or performances, and may include one or more processors 1001 and memory 1002, and the memory 1002 may store one or more storage applications or data.
  • the memory 1002 can be a short-term storage or a persistent storage.
  • the application stored in the memory 1002 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the tenant management device.
  • the processor 1001 can be configured to communicate with the memory 1002 and execute a series of computer executable instructions in the memory 1002 on the tenant management device.
  • the tenant management device may also include one or more power supplies 1003, one or more wired or wireless network interfaces 1004, one or more input and output interfaces 1005, and one or more keyboards 1006.
  • the tenant management device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more
  • the program may include one or more modules, and each module may include a series of computer executable instructions for the tenant management device, and the one or more programs configured to be executed by one or more processors include computer executable instructions for performing the following:
  • tenant creation request carries the number of users corresponding to the target tenant to be created
  • the target tenant is created and associated with a public routing tenant
  • the public routing tenant is used to provide routing services for the first type of tenants
  • network isolation between the first type of tenants is achieved through preset firewall rules.
  • the method further comprises:
  • the target tenant is created, and a routing device and a firewall are deployed for the target tenant.
  • the second type of tenant provides routing services to users through the routing device deployed within the tenant, and network isolation between users within the second type of tenant is achieved through preset firewall rules.
  • associating the target tenant with a public routing tenant includes:
  • a public routing tenant corresponding to the target tenant is determined among multiple public routing tenants to be associated, and the target tenant is associated to the public routing tenant corresponding to the target tenant.
  • the method further comprises:
  • the association between the target tenant and the public routing tenant is disconnected, and a routing device and a firewall are deployed for the target tenant.
  • the first type of tenant internal network is a shared network.
  • the one or more programs configured to be executed by one or more processors also include computer executable instructions for performing the following:
  • an association relationship is established between the public routing tenant and the tenant of the first type, so that routing services are provided to the tenant of the first type through the public routing tenant, and network isolation between tenants of the first type is achieved through preset firewall rules.
  • the number of users corresponding to the tenant of the first type is less than the preset number of users, and no routing equipment is deployed inside the first tenant.
  • the method further comprises:
  • the routing device deployed in the public routing tenant is adjusted so that the service provision of the adjusted public routing tenant is not less than the changed number of users corresponding to the associated first type of tenant. quantity.
  • establishing an association relationship between the public routing tenant and the tenant of the first type includes:
  • an intranet interface corresponding to the first type of tenants is added to the public routing tenant, and a blocking rule corresponding to the intranet interface is added to the firewall to achieve network isolation between the first type of tenants through the blocking rule.
  • the method further comprises:
  • the embodiment of the present specification provides a tenant management device, which obtains a tenant creation request, the tenant creation request carries the number of users corresponding to the target tenant to be created, and responds to the tenant creation request.
  • the type of the target tenant is determined to be the first type.
  • the target tenant is created, and the target tenant is associated with a public routing tenant, which is used to provide routing services for tenants of the first type, and to achieve network isolation between tenants of the first type through preset firewall rules.
  • routing services are provided for tenants of the first type whose number of users is less than the preset number of users through the public routing tenant, and the public routing tenant can achieve network isolation between tenants of the first type through preset firewall rules, which can avoid the problem of routing resource waste caused by deploying a routing device for each tenant, save resource costs, and improve routing utilization.
  • the embodiments of this specification also provide a computer-readable storage medium, on which a computer program is stored.
  • a computer program is stored.
  • the computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
  • the embodiment of the present specification provides a computer-readable storage medium, which obtains a tenant creation request, the tenant creation request carries the number of users corresponding to the target tenant to be created, responds to the tenant creation request, and determines the type of the target tenant as the first type when the number of users corresponding to the target tenant is less than the preset number of users, creates the target tenant when the type of the target tenant is the first type, and associates the target tenant with a public routing tenant, which is used to provide routing services for tenants of the first type, and implements network isolation between tenants of the first type through preset firewall rules.
  • routing services are provided for tenants of the first type whose number of users is less than the preset number of users through the public routing tenant, and the public routing tenant can implement network isolation between tenants of the first type through preset firewall rules, which can avoid the problem of routing resource waste caused by deploying a routing device for each tenant, save resource costs, and improve routing utilization.
  • a programmable logic device such as a field programmable gate array (FPGA)
  • FPGA field programmable gate array
  • HDL There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc.
  • ABEL Advanced Boolean Expression Language
  • AHDL Altera Hardware Description Language
  • HDCal JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc.
  • VHDL Very-High-Speed Integrated Circuit Hardware Description Language
  • Verilog Verilog
  • the controller may be implemented in any suitable manner.
  • the controller may be implemented as a microprocessor or a processor and may store computer readable program codes (e.g.,
  • the memory controller may be implemented in the form of a computer-readable medium (software or firmware), a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller.
  • controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320.
  • the memory controller may also be implemented as part of the control logic of the memory.
  • the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices included therein for implementing various functions may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.
  • a typical implementation device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
  • one or more embodiments of the present specification may be provided as methods, systems, or computer program products. Therefore, one or more embodiments of the present specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present specification may take the form of a computer program product having one or more computer programs including computer program code.
  • the present invention is in the form of a computer program product implemented on a computer-usable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.).
  • These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable tenant management device to produce a machine, so that the instructions executed by the processor of the computer or other programmable tenant management device produce a device for implementing the functions specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable tenant management device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable tenant management device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in a flowchart and/or one or more boxes in a block diagram.
  • a computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • processors CPU
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash RAM.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash random access memory
  • Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase-change RAM (PRAM), static RAM (SRAM), dynamic RAM (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
  • PRAM phase-change RAM
  • SRAM static RAM
  • DRAM dynamic RAM
  • RAM random access memory
  • ROM read-only memory
  • embodiments of the present specification may be provided as methods, systems or computer program products. Therefore, one or more embodiments of the present specification may be implemented in the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Furthermore, one or more embodiments of the present specification may be implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. in the form of a computer program product for implementation.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • One or more embodiments of the present specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules.
  • program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types.
  • One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network.
  • program modules may be located in local and remote computer storage media, including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Computer Security & Cryptography (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种租户管理方法、设备和存储介质，属于通信领域。本申请实施例的租户管理方法包括：获取租户创建请求，所述租户创建请求携带有待创建的目标租户对应的用户数量；响应于所述租户创建请求，在所述目标租户对应的用户数量小于预设用户数量的情况下，将所述目标租户的类型确定为第一类型；在所述目标租户的类型为第一类型的情况下，创建所述目标租户，并将所述目标租户关联到公共路由租户，所述公共路由租户用于为所述第一类型的租户提供路由服务，并通过预设防火墙规则实现所述第一类型的租户之间的网络隔离。

Description

租户管理方法、设备和存储介质
交叉引用
本申请要求在2022年09月29日提交中国专利局、申请号为202211201994.4、名称为“租户管理方法、设备和存储介质”的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，尤其涉及一种租户管理方法、设备和存储介质。
背景技术
随着计算机技术的迅速发展，云计算服务平台得到大规模部署，云计算服务平台可以为不同的租户提供相对独立的资源管理能力。例如，云计算服务平台可以在每个租户内部部署一套路由设备和防火墙，以为租户提供路由服务，并实现不同租户间的网络隔离。
但是，由于路由设备的服务提供能力通常较大，而不同的租户内的虚拟机的数量是参差不齐的，因而，为每个租户部署一套路由设备和防火墙，就会造成路由资源的浪费，因此，需要一种在租户内虚拟机数量参齐不齐的情况下，提高路由利用率的解决方案。
发明内容
本申请实施例提供一种租户管理方法、设备和存储介质，以提供一种在租户内虚拟机数量参齐不齐的情况下，提高路由利用率的解决方案。
第一方面，提供了一种租户管理方法，所述方法包括：获取租户创建请求，所述租户创建请求携带有待创建的目标租户对应的用户数量；响应于所述租户创建请求，在所述目标租户对应的用户数量小于预设用户数量的情况下，将所述目标租户的类型确定为第一类型；在所述目标租户的类型为第一类型的情况下，创建所述目标租户，并将所述目标租户关联到公共路由租户，所述公共路由租户用于为所述第一类型的租户提供路由服务，并通过预设防火墙规则实现所述第一类型的租户之间的网络隔离。
第二方面，提供了一种租户管理方法，所述方法包括：获取公共路由租户创建请求；响应于所述公共路由租户创建请求，创建所述公共路由租户，并为所述公共路由租户部署路由设备和防火墙；在接收到第一类型的租户关联请求的情况下，在所述公共路由租户与所述第一类型的租户之间建立关联关系，以通过所述公共路由租户为所述第一类型的租户提供路由服务，并通过预设防火墙规则实现所述第一类型的租户之间的网络隔离，所述第一类型的租户对应的用户数量小于预设用户数量，且所述第一租户内部未部署路由设备。
第三方面，提供了一种租户管理设备，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的租户管理方法的步骤，或者实现如或第二方面所述的租户管理方法的步骤。
第四方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的租户管理方法的步骤，或者实现如或第二方面所述的租户管理方法的步骤。
本申请实施例采用下述技术方案：
获取租户创建请求，租户创建请求携带有待创建的目标租户对应的用户数量，响应于租户创建请求，在目标租户对应的用户数量小于预设用户数量的情况下，将目标租户的类型确定为第一类型，在目标租户的类型为第一类型的情况下，创建目标租户，并将目标租户关联到公共路由租户，公共路由租户用于为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离。
附图说明
图1是根据本申请的一个实施例的租户管理方法的示意性流程图；
图2是根据本申请的一个实施例的租户管理方法的示意图；
图3是根据本申请的一个实施例的另一种租户管理方法的示意图；
图4是根据本申请的一个实施例的另一种租户管理方法的示意性流程图；
图5是根据本申请的一个实施例的另一种租户管理方法的示意性流程图；
图6是根据本申请的一个实施例的另一种租户管理方法的示意性流程图；
图7是根据本申请的一个实施例的另一种租户管理方法的示意图；
图8是根据本申请的一个实施例的一种租户管理装置的结构示意图；
图9是根据本申请的一个实施例的另一种租户管理装置的结构示意图；
图10是根据本申请的一个实施例的租户管理设备的结构示意图。
具体实施方式
本说明书实施例提供一种租户管理方法、设备和存储介质。
为了使本技术领域的人员更好地理解本说明书中的技术方案，下面将结合本说明书实施例中的附图，对本说明书实施例中的技术方案进行清楚、完 整地描述，显然，所描述的实施例仅仅是本说明书一部分实施例，而不是全部的实施例。基于本说明书中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本说明书保护的范围。
本申请的发明构思如下：随着计算机技术的迅速发展，云计算服务平台得到大规模部署，云计算服务平台可以为不同的租户提供相对独立的资源管理能力。例如，云计算服务平台可以在每个租户内部部署一套路由设备和防火墙，以为租户提供路由服务，并实现不同租户间的网络隔离。但是，由于路由设备的服务提供能力通常较大，而不同的租户内的虚拟机的数量是参差不齐的，因而，为每个租户部署一套路由设备和防火墙，就会造成路由资源的浪费，因此，需要一种在租户内虚拟机数量参齐不齐的情况下，提高路由利用率的解决方案。为此，本说明书实施例提供一种可以解决上述问题的技术方案，具体可以参见下述内容。
实施例一
如图1所示，本说明书实施例提供一种租户管理方法，该方法的执行主体可以为服务器，该服务器可以是云计算服务平台的服务器，该服务器可以是独立的服务器，也可以是由多个服务器组成的服务器集群。该方法具体可以包括以下步骤：
在S102中，获取租户创建请求。
其中，租户创建请求可以携带有待创建的目标租户对应的用户数量，用户数量可以是与目标租户对应的虚拟机数量。
在实施中，服务器可以获取一个或多个租户创建请求，每个租户创建请求都可以携带有对应的虚拟机数量(即用户数量)。
在S104中，响应于租户创建请求，在目标租户对应的用户数量小于预设 用户数量的情况下，将目标租户的类型确定为第一类型。
其中，预设用户数量可以是服务器基于预设业务场景、路由设备的服务提供量等因素确定的，例如，可以根据当前业务场景的网络响应速度，确定预设用户数量，具体如业务场景对网络响应速度越高，则对应的预设用户数量可以越小，或者，还可以根据路由设备的服务提供量，确定预设用户数量，具体如路由设备的服务提供量为100，则预设用户数量可以为50、80等小于路由设备的服务提供量的数量，除此之外，预设用户数量还可以有多种不同的确定方法，可以根据实际应用场景的不同，确定不同的预设用户数量，本说明书实施例对此不作具体限定。
在实施中，在租户创建请求有多个的情况下，服务器还可以根据租户对应的业务场景的不同，确定不同的预设用户数量，在通过业务场景对应的预设用户数量，确定对应的目标租户的类型。
例如，租户创建请求可以有针对目标租户1的租户创建请求和针对目标租户2的租户创建请求，假设目标租户1对应的业务场景为资源转移业务，目标租户2对应的业务场景为即时通讯业务，其中，由于即时通讯业务对网络响应速度的要求高于资源转移业务对网络响应速度的要求，因此，资源转移业务对应的预设用户数量1可以大于即时通讯业务对应的预设用户数量2。可以通过预设用户数量1确定目标租户1的类型，通过预设用户数量2确定目标租户2的类型，即若目标租户1的用户数量大于预设用户数量1，则可以确定目标租户1的类型为第一类型，若目标租户2的用户数量大于预设用户数量2，则可以确定目标租户2的类型为第一类型。
此外，在目标租户对应的用户数量不小于预设用户数量的情况下，可以将该租户创建请求发送给对应的工作人员进行处理，并根据处理结果进行租 户创建处理等操作。
在S106中，在目标租户的类型为第一类型的情况下，创建目标租户，并将目标租户关联到公共路由租户。
其中，公共路由租户可以用于为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离，公关路由租户内可以部署路由设备和防火墙，以通过公关路由租户内的路由设备为用户数量小于预设用户数量的第一类型的租户提供路由服务，并通过公关路由租户内的防火墙实现第一类型的租户之间的网络隔离，预设防火墙规则可以是访问控制规则，由源地址、目的地址、源端口、目的端口、协议等组成，防火墙规则可以通过源地址、目的地址等实现子网之间的阻断，即公共路由租户可以通过预设防火墙规则对第一类型的租户进行访问控制，以使第一类型的租户的子网之间实现网络隔离，此外，公关路由租户不提供高级网络功能。
在实施中，第一类型的租户内由于未部署路由设备，因而，第一类型的租户无法为用户提供网络功能，所以，可以将目标租户关联到公共路由租户，以通过公共路由租户内的路由设备，为目标租户提供路由服务，且由于公共路由内部署有防火墙，因而在目标租户管理的公共路由租户还关联有其他第一类型的租户的情况下，还可以通过预设防火墙规则实现目标租户与其他第一类型的租户之间的网络隔离。
如图2所示，若针对每个第一类型的租户(即租户1、租户2)部署一套路由设备和防火墙，由于第一类型的租户对应的用户数量小于预设用户数量，因而，该方法可能造成路由设备的资源浪费，例如，若一个路由设备可以为1000台虚拟机提供网络服务，而租户1对应的用户数量为100台虚拟机，租户2对应的用户数量为200台虚拟机，那么，这就会造成租户1对应的路由 设备的90％的资源浪费，租户2对应的路由设备的80％的资源浪费。
若将多个第一类型的租户关联到公共路由租户，则可以通过公共路由租户为多个第一类型的租户提供路由服务，降低路由资源的浪费，例如，如图3所示，假设租户1和租户2都为第一类型的租户，且租户1和租户2的用户数量都为500台虚拟机，公共路由租户内部署的路由设备也可以为1000台虚拟机提供网络服务，显然，通过公共路由为多个第一类型的租户提供路由服务，可以降低对路由设备的资源浪费率，提高路由资源的利用率。
本说明书实施例提供一种租户管理方法，获取租户创建请求，租户创建请求携带有待创建的目标租户对应的用户数量，响应于租户创建请求，在目标租户对应的用户数量小于预设用户数量的情况下，将目标租户的类型确定为第一类型，在目标租户的类型为第一类型的情况下，创建目标租户，并将目标租户关联到公共路由租户，公共路由租户用于为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离。这样，通过公共路由租户为用户数量小于预设用户数量的第一类型的租户提供路由服务，且公共路由租户可以通过预设防火墙规则实现第一类型的租户之间的网络隔离，可以避免针对每个租户部署一个路由设备导致的路由资源浪费的问题，节省了资源成本，提高了路由利用率。
实施例二
如图4所示，本说明书实施例提供一种租户管理方法，该方法的执行主体可以为服务器，该服务器可以是云计算服务平台的服务器，该服务器可以是独立的服务器，也可以是由多个服务器组成的服务器集群。该方法具体可以包括以下步骤：
在S102中，获取租户创建请求。
其中，租户创建请求携带有待创建的目标租户对应的用户数量。
可以根据目标租户对应的用户数量，确定目标租户的类型，即如图4所示，在S102后，可以继续执行S104～S408，或者，还可以继续执行S410～S412。
在S104中，响应于租户创建请求，在目标租户对应的用户数量小于预设用户数量的情况下，将目标租户的类型确定为第一类型。
其中，第一类型的租户内部网络为共享网络，可以通过相同的网络地址的前缀，使第一类型的租户的内部网络为共享网络，例如，可以将第一类型的租户的网络子网配置中的网络地址前缀设定为192网段等，以使该租户内的网络为共享网络，第一类型的租户内的虚拟机可以通过该共享网络访问外部网络，且各共享网络的地址需进行规划，不同的租户的共享网络之间不可重叠，即每个第一类型的租户使用自己的子网，且每个第一类型的租户子网前缀固定。
在S106中，在目标租户的类型为第一类型的情况下，创建目标租户。
在S402中，基于待关联的公共路由租户的服务提供量、待关联的公共路由租户的已关联第一类型的租户对应的用户数量，以及目标租户对应的用户数量，在多个待关联的公共路由租户中确定与目标租户对应的公共路由租户，并将目标租户关联到与目标租户对应的公共路由租户。
在实施中，若存在多个待关联的公共路由租户，则可以通过每个待关联的公共路由租户的服务提供量，每个待关联的公共路由租户的已关联第一类型的租户对应的用户数量，确定每个待关联的公共路由租户的剩余服务提供量，再根据目标租户的用户数量和每个待关联的公共路由租户的剩余服务提供量，确定与目标租户对应的公共路由租户，并将目标租户关联到与目标租 户对应的公共路由租户。
例如，假设待关联的公共路由租户有公共路由租户1和公共路由租户2，若公共路由租户1的剩余服务提供量为300台虚拟机(即公共路由租户1的服务提供量可以为1000，已关联的第一类型的租户对应的用户数量为700台虚拟机)，公共路由租户2的剩余服务提供量为400台虚拟机，由于公共路由租户2的剩余服务提供量大于公共路由租户1的剩余服务提供量，因此，可以确定公共路由租户2为与目标租户对应的公共路由租户，可以将目标租户关联到公共路由租户2。
此外，上述与目标租户对应的公共路由租户的确定方法是一种可选地、可实现的确定方法，在实际应用场景中，还可以有多种不同的确定方法，例如，还可以获取每个待关联的公共路由租户在预设检测周期内的最大服务提供量(如公共路由租户在近一周内的为已关联的第一类型的租户提供路由服务的最大服务提供量)，并根据最大服务提供量和公共路由租户的服务提供量，确定与目标租户对应的公共路由租户等，可以根据实际应用场景的不同，选取不同的确定方法，本说明书实施例对此不作具体限定。
在S404中，在目标租户的用户数量发生变化的情况下，获取变化后的目标租户对应的用户数量。
在实施中，例如，若目标租户的用户数量由100台虚拟机变化为500台虚拟机，则可以获取变化后的目标租户对应的用户数量，即500台虚拟机。
在S406中，在变化后的目标租户对应的用户数量不小于预设用户数量的情况下，将目标租户的类型确定为第二类型。
在实施中，若变化后的目标租户对应的用户数量仍小于预设用户数量的情况下，则可以保持目标租户的类型以及与公共路由租户之间的关联关系不 变，若变化后的目标租户对应的用户数量不小于预设用户数量的情况下，则可以将目标租户的类型确定为第二类型。
例如，假设变化后的目标租户对应的用户数量500台虚拟机，若预设用户数量为600台虚拟机，则可以将目标租户的类型变更为第二类型，若预设用户数量为500台虚拟机，则可以保持目标租户的类型以及与公共路由租户之间的关联关系不变，即目标租户的类型仍为第一类型。
此外，若目标租户对应的业务场景发生变化，则可以获取变化后的业务场景对应的预设用户数量，再基于变化后的业务场景对应的预设用户数量以及变化后的目标租户对应的用户数量，确定目标租户的类型，例如，若目标租户对应的业务场景从资源转移业务变化为即时通讯业务，对应的用户数量可以从600台虚拟机变化为400台虚拟机，若变化后的目标租户对应的用户数量500台虚拟机，则可以确定目标租户的类型为第二类型。
在S408中，在目标租户的类型为第二类型的情况下，断开目标租户与公共路由租户的关联关系，并为目标租户部署路由设备和防火墙。
在实施中，在目标租户的类型为第二类型的情况下，可以通过目标租户内部署的路由设备为目标租户内的用户提供路由服务，并通过防火墙提供目标租户内用户之间的网络隔离，其中，第二类型的租户内部网络为非共享网络，子网的网段可以重叠。
在S410中，在目标租户对应的用户数量不小于预设用户数量的情况下，将目标租户的类型确定为第二类型。
在S412中，在目标租户的类型为第二类型的情况下，创建目标租户，并为目标租户部署路由设备和防火墙。
其中，第二类型的租户可以通过租户内部部署的路由设备为用户提供路 由服务，并通过预设防火墙规则实现第二类型的租户内部的用户之间的网络隔离。
在实施中，通过目标租户对应的用户数量是否小于预设用户数量，可以确定目标租户的类型是第一类型还是第二类型，以为不同类型的租户提供不同的路由服务，以节省路由资源，提高路由资源利用率。
本说明书实施例提供一种租户管理方法，本说明书实施例提供一种租户管理方法，获取租户创建请求，租户创建请求携带有待创建的目标租户对应的用户数量，响应于租户创建请求，在目标租户对应的用户数量小于预设用户数量的情况下，将目标租户的类型确定为第一类型，在目标租户的类型为第一类型的情况下，创建目标租户，并将目标租户关联到公共路由租户，公共路由租户用于为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离。这样，通过公共路由租户为用户数量小于预设用户数量的第一类型的租户提供路由服务，且公共路由租户可以通过预设防火墙规则实现第一类型的租户之间的网络隔离，可以避免针对每个租户部署一个路由设备导致的路由资源浪费的问题，节省了资源成本，提高了路由利用率。
实施例三
如图5所示，本说明书实施例提供一种租户管理方法，该方法的执行主体可以为服务器，该服务器可以是云计算服务平台的服务器，该服务器可以是独立的服务器，也可以是由多个服务器组成的服务器集群。该方法具体可以包括以下步骤：
在S502中，获取公共路由租户创建请求。
在S504中，响应于公共路由租户创建请求，创建公共路由租户，并为公共路由租户部署路由设备和防火墙。
在实施中，由于公共路由租户可以仅提供路由服务，因此，公共路由租户可以不提供高级网络功能，可以根据实际业务场景的需求，为公共路由租户部署相应的路由设备和防火墙。
在S506中，在接收到第一类型的租户关联请求的情况下，在公共路由租户与第一类型的租户之间建立关联关系，以通过公共路由租户为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离。
其中，第一类型的租户对应的用户数量小于预设用户数量，且第一租户内部未部署路由设备。
在实施中，公共路由租户可以与一个或多个第一类型的租户之间建立关联关系，在接收到第一类型的租户关联请求的情况下，可以根据公共路由租户内部署的路由设备的服务提供量、已关联的第一类型的租户的用户数量和待关联的第一类型的租户的用户数量，确定是否与待关联的第一类型的租户之间建立关联关系。
例如，若公共路由租户内部署的路由设备的服务提供量为1000台虚拟机，已关联的第一类型的租户的用户数量为700台虚拟机，若待关联的第一类型的租户的用户数量不大于300台虚拟机，则可以在公告路由租户与待关联的第一类型的租户之间建立关联关系，由于第一类型的租户内未部署路由设备，因此，可以通过该公共路由租户内部署的路由设备为已关联的多个第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离。
本说明书实施例提供一种租户管理方法，获取公共路由租户创建请求，响应于公共路由租户创建请求，创建公共路由租户，并为公共路由租户部署路由设备和防火墙，在接收到第一类型的租户关联请求的情况下，在公共路由租户与第一类型的租户之间建立关联关系，以通过公共路由租户为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离，第一类型的租户对应的用户数量小于预设用户数量，且第一租户内部未部署路由设备，这样，可以通过公共路由租户为用户数量小于预设用户数量的第一类型的租户提供路由服务，且公共路由租户可以通过预设防火墙规则实现第一类型的租户之间的网络隔离，可以避免针对每个租户部署一个路由设备导致的路由资源浪费的问题，节省了资源成本，提高了路由利用率。
实施例四
如图6所示，本说明书实施例提供一种租户管理方法，该方法的执行主体可以为服务器，该服务器可以是云计算服务平台的服务器，该服务器可以是独立的服务器，也可以是由多个服务器组成的服务器集群。该方法具体可以包括以下步骤：
在S502中，获取公共路由租户创建请求。
在S504中，响应于公共路由租户创建请求，创建公共路由租户，并为公共路由租户部署路由设备和防火墙。
在S602中，在接收到第一类型的租户关联请求的情况下，基于第一类型的租户的网络信息，对公共路由租户添加与第一类型的租户对应的内网接口，并在防火墙上添加与内网接口对应的阻断规则，以通过阻断规则实现第一类 型的租户之间的网络隔离。
其中，第一类型的租户对应的用户数量小于预设用户数量，且第一租户内部未部署路由设备。
在实施中，公共路由租户内部署的路由设备每添加一个接口时，需要在防火墙上添加源地址为其他内网、目的地址为该网段的阻断规则，以实现第一类型的租户之间的网络隔离的功能。
这样，在多个第一类型的租户使用的同一个公共路由租户下的路由设备时，可以在新增与第一类型的租户对应的内网接口时，通过设置相应的防火墙规则，确保不同的第一类型的租户之间网络的通讯隔离以及同一租户内部的子网互通。
在S604中，在已关联的第一类型的租户对应的用户数量大于公共路由租户的服务提供量的情况下，基于已关联的第一类型的租户对应的变化后用户数量，对公共路由租户内部署的路由设备进行调整，以使调整后的公共路由租户的服务提供量不小于已关联的第一类型的租户对应的变化后用户数量。
在实施中，在实际应用场景中，租户对应的用户数量不是一成不变的，因此，为保证租户的路由服务质量，可以对公共路由租户是否能满足已关联的第一类型的租户的路由服务需求进行检测，并在公共路由租户无法满足已关联的第一类型的租户的路由服务需求时，对公共路由租户内部署的路由设备进行调整，如可以在公共路由租户内增加路由设备的部署量，或者，可以将公共路由租户内部署的路由设备更换为服务提供量更大的路由设备等，以使调整后的公共路由租户能够满足已关联的第一类型的租户的路由服务需求，具体的，可以根据已关联的第一类型的租户对应的用户数量是否大于公共路由租户的服务提供量的情况，确定公共路由租户能够满足已关联的第一类型 的租户的路由服务需求。
例如，如图3所示，租户1和租户2为第一类型的租户，租户1与租户2分别与公共路由租户之间建立关联关系，即公共路由租户可以为租户1和租户2的用户提供路由功能，假设租户1和租户2的用户数量都为500台虚拟机，公共路由租户内部署的路由设备可以为1000台虚拟机提供网络服务，若租户1的用户数量从500台虚拟机变化为600台虚拟机，则公共路由租户内部署的路由设备的服务提供量小于租户1和租户2的用户数量，即该公共路由租户无法满足租户1和租户2的路由服务需求，此时，可以对公共路由租户内部署的路由设备进行调整，如在公共路由租户内再部署一个路由设备，即可以通过增加路由设备的方式提高公共路由租户的服务提供量，以使该公共路由租户内部署的路由设备的服务提供量不小于租户1和租户2的用户数量。
在S606中，在已关联的第一类型的租户中存在租户类型变动的租户的情况下，断开租户类型发生变动的租户与公共路由租户之间的关联关系，并删除与租户类型发生变动的租户对应的内网接口，以及防火墙上与租户类型发生变动的租户对应的阻断规则。
在实施中，由于租户对应的用户数量不是一成不变的，因而，租户的类型也可以发生变动，所以，在已关联的第一类型的租户中存在租户类型变动的租户的情况下，可以断开租户类型发生变动的租户与公共路由租户之间的关联关系，并删除与租户类型发生变动的租户对应的内网接口，以及防火墙上与租户类型发生变动的租户对应的阻断规则。
此外，在已关联的第一类型的租户中存在租户销户等情况下，也可以断开销户的租户与公共路由租户之间的关联关系，并删除与销户的租户对应的 内网接口，以及防火墙上与销户的租户对应的阻断规则。
本说明书实施例提供一种租户管理方法，获取公共路由租户创建请求，响应于公共路由租户创建请求，创建公共路由租户，并为公共路由租户部署路由设备和防火墙，在接收到第一类型的租户关联请求的情况下，在公共路由租户与第一类型的租户之间建立关联关系，以通过公共路由租户为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离，第一类型的租户对应的用户数量小于预设用户数量，且第一租户内部未部署路由设备，这样，可以通过公共路由租户为用户数量小于预设用户数量的第一类型的租户提供路由服务，且公共路由租户可以通过预设防火墙规则实现第一类型的租户之间的网络隔离，可以避免针对每个租户部署一个路由设备导致的路由资源浪费的问题，节省了资源成本，提高了路由利用率。
实施例五
本说明书实施例提供一种租户管理方法，该方法的执行主体可以为服务器，该服务器可以是云计算服务平台的服务器，该服务器可以是独立的服务器，也可以是由多个服务器组成的服务器集群。
服务器可以接收租户创建请求，租户创建请求可以用于创建第一类型的租户、第二类型的租户或公共路由租户，其中，若租户创建请求可以包括第一类型或类型的租户创建请求，则该租户创建请求可以携带有待创建的目标租户对应的用户数量。
若租户创建请求为用于创建第一类型的租户或第二类型的租户的请求，则服务器可以在目标租户对应的用户数量小于预设用户数量的情况下，将目 标租户的类型确定为第一类型，在目标租户对应的用户数量不小于预设用户数量的情况下，将目标租户的类型确定为第二类型。
若租户创建请求为用于创建公共路由租户的请求，则响应于该租户创建请求，可以创建公共路由租户，并为公共路由租户部署路由设备和防火墙。
服务器可以根据不同的租户创建请求，分别创建对应的第一类型的租户、第二类型的租户以公共路由租户，并为第一类型的租户和公共路由租户之间建立关联关系，具体的租户创建方法以及租户之间的关联关系的建立方法可以参见上述实施例一～实施例四的具体内容，此处不再赘述。如图7所示，租户1和租户2可以为第一类型的租户，租户1和租户2可以通过公关路由租户内部署的路由设备访问外部网络，且租户1内部网络为共享网络，租户2内部网络也为共享网络，而租户3和租户4可以是第二类型的租户，租户3以及租户4内部可以部署路由设备和防火墙，租户3以及租户4就可以通过内部部署的路由设备直接访问外部网络，租户3以及租户4内部网络为非共享网络，子网的网段可以重叠。
且在租户的用户数量、公共路由租户的服务提供量、租户的类型等发生变化的情况下，可以灵活的根据具体的变化情况，对租户进行调整，以适应租户的实际使用需求。例如，在租户的用户数量发生变化的情况下，可以灵活针对用户数量的变化情况，调整租户的类型或公共路由租户的服务提供量等，以保证整个云服务系统的服务提供稳定性。
通过对租户进行类型的划分，可以将租户分为第一类型的租户、第二类型的租户以及公共路由租户，可以在第二类型的租户以及公共路由租户内部署路由设备，且可以针对第二类型的租户以及公共路由租户设置网络功能管理，如浮动IP分配功能、防火墙管理功能等，而公共路由租户仅可以为第一 类型的租户提供路由功能，不允许在公共路由租户内创建虚机磁盘等资源，不允许在公共路由租户内添加安全组及规则，在创建第一类型的租户时需要关联将第一类型的租户关联到公共路由租户，以通过公共路由租户的路由设备为第一类型的租户提供实现高级网络功能，同时，第一类型的租户内不需要部署属于自己的路由设备，可以提高整个云计算服务系统的资源使用率，减少系统消耗成本。
本说明书实施例提供一种租户管理方法，可以通过公共路由租户为用户数量小于预设用户数量的第一类型的租户提供路由服务，且公共路由租户可以通过预设防火墙规则实现第一类型的租户之间的网络隔离，可以避免针对每个租户部署一个路由设备导致的路由资源浪费的问题，节省了资源成本，提高了路由利用率。
实施例六
以上为本说明书实施例提供的租户管理方法，基于同样的思路，本说明书实施例还提供一种租户管理装置，如图8所示。
该租户管理装置包括：请求获取模块801、第一确定模块802和第一创建模块803，其中：
请求获取模块801，用于获取租户创建请求，所述租户创建请求携带有待创建的目标租户对应的用户数量；
第一确定模块802，用于响应于所述租户创建请求，在所述目标租户对应的用户数量小于预设用户数量的情况下，将所述目标租户的类型确定为第一类型；
第一创建模块803，用于在所述目标租户的类型为第一类型的情况下， 创建所述目标租户，并将所述目标租户关联到公共路由租户，所述公共路由租户用于为所述第一类型的租户提供路由服务，并通过预设防火墙规则实现所述第一类型的租户之间的网络隔离。
本说明书实施例中，所述装置还包括：
第二确定模块，用于在所述目标租户对应的用户数量不小于所述预设用户数量的情况下，将所述目标租户的类型确定为第二类型；
第二创建模块，用于在所述目标租户的类型为第二类型的情况下，创建所述目标租户，并为所述目标租户部署路由设备和防火墙，所述第二类型的租户通过租户内部部署的路由设备为用户提供路由服务，并通过预设防火墙规则实现所述第二类型的租户内部的用户之间的网络隔离。
本说明书实施例中，所述第一创建模块803，用于：
基于待关联的公共路由租户的服务提供量、所述待关联的公共路由租户的已关联第一类型的租户对应的用户数量，以及所述目标租户对应的用户数量，在多个所述待关联的公共路由租户中确定与所述目标租户对应的公共路由租户，并将所述目标租户关联到所述与所述目标租户对应的公共路由租户。
本说明书实施例中，所述装置还包括：
数量获取模块，用于在所述目标租户的用户数量发生变化的情况下，获取变化后的目标租户对应的用户数量；
第三确定模块，用于在所述变化后的目标租户对应的用户数量不小于所述预设用户数量的情况下，将所述目标租户的类型确定为第二类型；
设备部署模块，用于在所述目标租户的类型为第二类型的情况下，断开所述目标租户与所述公共路由租户的关联关系，并为所述目标租户部署路由设备和防火墙。
本说明书实施例中，所述第一类型的租户内部网络为共享网络。
本说明书实施例提供一种租户管理装置，获取租户创建请求，租户创建请求携带有待创建的目标租户对应的用户数量，响应于租户创建请求，在目标租户对应的用户数量小于预设用户数量的情况下，将目标租户的类型确定为第一类型，在目标租户的类型为第一类型的情况下，创建目标租户，并将目标租户关联到公共路由租户，公共路由租户用于为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离。这样，通过公共路由租户为用户数量小于预设用户数量的第一类型的租户提供路由服务，且公共路由租户可以通过预设防火墙规则实现第一类型的租户之间的网络隔离，可以避免针对每个租户部署一个路由设备导致的路由资源浪费的问题，节省了资源成本，提高了路由利用率。
实施例七
以上为本说明书实施例提供的租户管理方法，基于同样的思路，本说明书实施例还提供一种租户管理装置，如图9所示。
该租户管理装置包括：请求获取模块901、租户创建模块902和关系建立模块903，其中：
请求获取模块901，用于获取公共路由租户创建请求；
租户创建模块902，用于响应于所述公共路由租户创建请求，创建所述公共路由租户，并为所述公共路由租户部署路由设备和防火墙；
关系建立模块903，用于在接收到第一类型的租户关联请求的情况下，在所述公共路由租户与所述第一类型的租户之间建立关联关系，以通过所述公共路由租户为所述第一类型的租户提供路由服务，并通过预设防火墙规则 实现所述第一类型的租户之间的网络隔离，所述第一类型的租户对应的用户数量小于预设用户数量，且所述第一租户内部未部署路由设备。
本说明书实施例中，所述装置还包括：
设备调整模块，用于在已关联的第一类型的租户对应的用户数量大于所述公共路由租户的服务提供量的情况下，基于所述已关联的第一类型的租户对应的变化后用户数量，对所述公共路由租户内部署的路由设备进行调整，以使调整后的公共路由租户的服务提供量不小于所述已关联的第一类型的租户对应的变化后用户数量。
本说明书实施例中，所述关系建立模块903，用于：
基于所述第一类型的租户的网络信息，对所述公共路由租户添加与所述第一类型的租户对应的内网接口，并在所述防火墙上添加与所述内网接口对应的阻断规则，以通过所述阻断规则实现所述第一类型的租户之间的网络隔离。
本说明书实施例中，所述装置还包括：
关系断开模块，用于在所述已关联的第一类型的租户中存在租户类型变动的租户的情况下，断开所述租户类型发生变动的租户与所述公共路由租户之间的关联关系，并删除与所述租户类型发生变动的租户对应的内网接口，以及所述防火墙上与所述租户类型发生变动的租户对应的阻断规则。
业务数据的数据类型，确定用于对所述业务数据进行攻击的所述扰动数据。
本说明书实施例提供一种租户管理装置，获取公共路由租户创建请求，响应于公共路由租户创建请求，创建公共路由租户，并为公共路由租户部署路由设备和防火墙，在接收到第一类型的租户关联请求的情况下，在公共路 由租户与第一类型的租户之间建立关联关系，以通过公共路由租户为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离，第一类型的租户对应的用户数量小于预设用户数量，且第一租户内部未部署路由设备，这样，可以通过公共路由租户为用户数量小于预设用户数量的第一类型的租户提供路由服务，且公共路由租户可以通过预设防火墙规则实现第一类型的租户之间的网络隔离，可以避免针对每个租户部署一个路由设备导致的路由资源浪费的问题，节省了资源成本，提高了路由利用率。
实施例八
基于同样的思路，本说明书实施例还提供一种租户管理设备，如图10所示。
租户管理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器1001和存储器1002，存储器1002中可以存储有一个或一个以上存储应用程序或数据。其中，存储器1002可以是短暂存储或持久存储。存储在存储器1002的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括对租户管理设备中的一系列计算机可执行指令。更进一步地，处理器1001可以设置为与存储器1002通信，在租户管理设备上执行存储器1002中的一系列计算机可执行指令。租户管理设备还可以包括一个或一个以上电源1003，一个或一个以上有线或无线网络接口1004，一个或一个以上输入输出接口1005，一个或一个以上键盘1006。
具体在本实施例中，租户管理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上 程序可以包括一个或一个以上模块，且每个模块可以包括对租户管理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：
获取租户创建请求，所述租户创建请求携带有待创建的目标租户对应的用户数量；
响应于所述租户创建请求，在所述目标租户对应的用户数量小于预设用户数量的情况下，将所述目标租户的类型确定为第一类型；
在所述目标租户的类型为第一类型的情况下，创建所述目标租户，并将所述目标租户关联到公共路由租户，所述公共路由租户用于为所述第一类型的租户提供路由服务，并通过预设防火墙规则实现所述第一类型的租户之间的网络隔离。
可选地，所述方法还包括：
在所述目标租户对应的用户数量不小于所述预设用户数量的情况下，将所述目标租户的类型确定为第二类型；
在所述目标租户的类型为第二类型的情况下，创建所述目标租户，并为所述目标租户部署路由设备和防火墙，所述第二类型的租户通过租户内部部署的路由设备为用户提供路由服务，并通过预设防火墙规则实现所述第二类型的租户内部的用户之间的网络隔离。
可选地，所述将所述目标租户关联到公共路由租户，包括：
基于待关联的公共路由租户的服务提供量、所述待关联的公共路由租户的已关联第一类型的租户对应的用户数量，以及所述目标租户对应的用户数量，在多个所述待关联的公共路由租户中确定与所述目标租户对应的公共路由租户，并将所述目标租户关联到所述与所述目标租户对应的公共路由租户。
可选地，所述方法还包括：
在所述目标租户的用户数量发生变化的情况下，获取变化后的目标租户对应的用户数量；
在所述变化后的目标租户对应的用户数量不小于所述预设用户数量的情况下，将所述目标租户的类型确定为第二类型；
在所述目标租户的类型为第二类型的情况下，断开所述目标租户与所述公共路由租户的关联关系，并为所述目标租户部署路由设备和防火墙。
可选地，所述第一类型的租户内部网络为共享网络。
此外，经配置以由一个或者一个以上处理器执行该一个或者一个以上程序还包含用于进行以下计算机可执行指令：
获取公共路由租户创建请求；
响应于所述公共路由租户创建请求，创建所述公共路由租户，并为所述公共路由租户部署路由设备和防火墙；
在接收到第一类型的租户关联请求的情况下，在所述公共路由租户与所述第一类型的租户之间建立关联关系，以通过所述公共路由租户为所述第一类型的租户提供路由服务，并通过预设防火墙规则实现所述第一类型的租户之间的网络隔离，所述第一类型的租户对应的用户数量小于预设用户数量，且所述第一租户内部未部署路由设备。
可选地，所述方法还包括：
在已关联的第一类型的租户对应的用户数量大于所述公共路由租户的服务提供量的情况下，基于所述已关联的第一类型的租户对应的变化后用户数量，对所述公共路由租户内部署的路由设备进行调整，以使调整后的公共路由租户的服务提供量不小于所述已关联的第一类型的租户对应的变化后用户 数量。
可选地，所述在所述公共路由租户与所述第一类型的租户之间建立关联关系，包括：
基于所述第一类型的租户的网络信息，对所述公共路由租户添加与所述第一类型的租户对应的内网接口，并在所述防火墙上添加与所述内网接口对应的阻断规则，以通过所述阻断规则实现所述第一类型的租户之间的网络隔离。
可选地，所述方法还包括：
在所述已关联的第一类型的租户中存在租户类型变动的租户的情况下，断开所述租户类型发生变动的租户与所述公共路由租户之间的关联关系，并删除与所述租户类型发生变动的租户对应的内网接口，以及所述防火墙上与所述租户类型发生变动的租户对应的阻断规则。
本说明书实施例提供一种租户管理设备，获取租户创建请求，租户创建请求携带有待创建的目标租户对应的用户数量，响应于租户创建请求，在目标租户对应的用户数量小于预设用户数量的情况下，将目标租户的类型确定为第一类型，在目标租户的类型为第一类型的情况下，创建目标租户，并将目标租户关联到公共路由租户，公共路由租户用于为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离。这样，通过公共路由租户为用户数量小于预设用户数量的第一类型的租户提供路由服务，且公共路由租户可以通过预设防火墙规则实现第一类型的租户之间的网络隔离，可以避免针对每个租户部署一个路由设备导致的路由资源浪费的问题，节省了资源成本，提高了路由利用率。
实施例九
本说明书实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述租户管理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
本说明书实施例提供一种计算机可读存储介质，获取租户创建请求，租户创建请求携带有待创建的目标租户对应的用户数量，响应于租户创建请求，在目标租户对应的用户数量小于预设用户数量的情况下，将目标租户的类型确定为第一类型，在目标租户的类型为第一类型的情况下，创建目标租户，并将目标租户关联到公共路由租户，公共路由租户用于为第一类型的租户提供路由服务，并通过预设防火墙规则实现第一类型的租户之间的网络隔离。这样，通过公共路由租户为用户数量小于预设用户数量的第一类型的租户提供路由服务，且公共路由租户可以通过预设防火墙规则实现第一类型的租户之间的网络隔离，可以避免针对每个租户部署一个路由设备导致的路由资源浪费的问题，节省了资源成本，提高了路由利用率。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪90年代，对于一个技术的改进可以很明显地区分是硬件上的 改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device，PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如 软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书一个或多个实施例时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本说明书的实施例可提供为方法、系统、或计算机程序产品。因此，本说明书一个或多个实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本说明书一个或多个实施例可采用在一个或多个其中包含有计算机可用程序代码 的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书的实施例是参照根据本说明书实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程租户管理设备的处理器以产生一个机器，使得通过计算机或其他可编程租户管理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程租户管理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程租户管理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(Phase-change RAM，PRAM)、静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本说明书的实施例可提供为方法、系统或计算机程序产品。因此，本说明书一个或多个实施例可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本说明书一个或多个实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实 施的计算机程序产品的形式。
本说明书一个或多个实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书一个或多个实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本说明书的实施例而已，并不用于限制本说明书。对于本领域技术人员来说，本说明书可以有各种更改和变化。凡在本说明书的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本说明书的权利要求范围之内。

Claims (11)

  1. 一种租户管理方法，包括：
    获取租户创建请求，所述租户创建请求携带有待创建的目标租户对应的用户数量；
    响应于所述租户创建请求，在所述目标租户对应的用户数量小于预设用户数量的情况下，将所述目标租户的类型确定为第一类型；
    在所述目标租户的类型为第一类型的情况下，创建所述目标租户，并将所述目标租户关联到公共路由租户，所述公共路由租户用于为所述第一类型的租户提供路由服务，并通过预设防火墙规则实现所述第一类型的租户之间的网络隔离。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    在所述目标租户对应的用户数量不小于所述预设用户数量的情况下，将所述目标租户的类型确定为第二类型；
    在所述目标租户的类型为第二类型的情况下，创建所述目标租户，并为所述目标租户部署路由设备和防火墙，所述第二类型的租户通过租户内部部署的路由设备为用户提供路由服务，并通过预设防火墙规则实现所述第二类型的租户内部的用户之间的网络隔离。
  3. 根据权利要求1所述的方法，其中，所述将所述目标租户关联到公共路由租户，包括：
    基于待关联的公共路由租户的服务提供量、所述待关联的公共路由租户的已关联第一类型的租户对应的用户数量，以及所述目标租户对应的用户数量，在多个所述待关联的公共路由租户中确定与所述目标租户对应的公共路由租户，并将所述目标租户关联到所述与所述目标租户对应的公共路由租户。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    在所述目标租户的用户数量发生变化的情况下，获取变化后的目标租户对应的用户数量；
    在所述变化后的目标租户对应的用户数量不小于所述预设用户数量的情况下，将所述目标租户的类型确定为第二类型；
    在所述目标租户的类型为第二类型的情况下，断开所述目标租户与所述公共路由租户的关联关系，并为所述目标租户部署路由设备和防火墙。
  5. 根据权利要求2所述的方法，其中，所述第一类型的租户内部网络为共享网络。
  6. 一种租户管理方法，包括：
    获取公共路由租户创建请求；
    响应于所述公共路由租户创建请求，创建所述公共路由租户，并为所述公共路由租户部署路由设备和防火墙；
    在接收到第一类型的租户关联请求的情况下，在所述公共路由租户与所述第一类型的租户之间建立关联关系，以通过所述公共路由租户为所述第一类型的租户提供路由服务，并通过预设防火墙规则实现所述第一类型的租户之间的网络隔离，所述第一类型的租户对应的用户数量小于预设用户数量，且所述第一租户内部未部署路由设备。
  7. 根据权利要求6所述的方法，其中，所述方法还包括：
    在已关联的第一类型的租户对应的用户数量大于所述公共路由租户的服务提供量的情况下，基于所述已关联的第一类型的租户对应的变化后用户数量，对所述公共路由租户内部署的路由设备进行调整，以使调整后的公共路由租户的服务提供量不小于所述已关联的第一类型的租户对应 的变化后用户数量。
  8. 根据权利要求6所述的方法，其中，所述在所述公共路由租户与所述第一类型的租户之间建立关联关系，包括：
    基于所述第一类型的租户的网络信息，对所述公共路由租户添加与所述第一类型的租户对应的内网接口，并在所述防火墙上添加与所述内网接口对应的阻断规则，以通过所述阻断规则实现所述第一类型的租户之间的网络隔离。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    在所述已关联的第一类型的租户中存在租户类型变动的租户的情况下，断开所述租户类型发生变动的租户与所述公共路由租户之间的关联关系，并删除与所述租户类型发生变动的租户对应的内网接口，以及所述防火墙上与所述租户类型发生变动的租户对应的阻断规则。
  10. 一种租户管理设备，包括处理器和存储器，其中，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至9任一项所述的租户管理方法的步骤。
  11. 一种可读存储介质，其中，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1-9中任一项所述的租户管理方法的步骤。
PCT/CN2023/105153 2022-09-29 2023-06-30 租户管理方法、设备和存储介质 WO2024066625A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211201994.4 2022-09-29
CN202211201994.4A CN117857062A (zh) 2022-09-29 2022-09-29 租户管理方法、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2024066625A1 true WO2024066625A1 (zh) 2024-04-04

Family

ID=90475886

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/105153 WO2024066625A1 (zh) 2022-09-29 2023-06-30 租户管理方法、设备和存储介质

Country Status (2)

Country Link
CN (1) CN117857062A (zh)
WO (1) WO2024066625A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160323183A1 (en) * 2015-04-30 2016-11-03 Cisco Technology, Inc. Cloud Provider, Service, and Tenant Classification in Cloud Computing
CN107342895A (zh) * 2017-06-26 2017-11-10 网宿科技股份有限公司 一种多租户的网络优化方法、系统、计算设备及存储介质
US20190042322A1 (en) * 2017-08-04 2019-02-07 Espressive, Inc. Elastic multi-tenant container architecture
CN111404951A (zh) * 2020-03-23 2020-07-10 星环信息科技（上海）有限公司 一种云网络的租户创建方法、计算机设备及存储介质
CN114640554A (zh) * 2022-02-15 2022-06-17 阿里云计算有限公司 多租户通信隔离方法和混合组网方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160323183A1 (en) * 2015-04-30 2016-11-03 Cisco Technology, Inc. Cloud Provider, Service, and Tenant Classification in Cloud Computing
CN107342895A (zh) * 2017-06-26 2017-11-10 网宿科技股份有限公司 一种多租户的网络优化方法、系统、计算设备及存储介质
US20190042322A1 (en) * 2017-08-04 2019-02-07 Espressive, Inc. Elastic multi-tenant container architecture
CN111404951A (zh) * 2020-03-23 2020-07-10 星环信息科技（上海）有限公司 一种云网络的租户创建方法、计算机设备及存储介质
CN114640554A (zh) * 2022-02-15 2022-06-17 阿里云计算有限公司 多租户通信隔离方法和混合组网方法

Also Published As

Publication number Publication date
CN117857062A (zh) 2024-04-09

Similar Documents

Publication Publication Date Title
US11055159B2 (en) System and method for self-healing of application centric infrastructure fabric memory
TWI694700B (zh) 資料處理方法和裝置、用戶端
CN105573604A (zh) 应用程序的分类方法及装置
CN112104499B (zh) 一种容器网络模型构建方法、装置、设备及介质
US11563805B2 (en) Method, apparatus, client terminal, and server for data processing
TW201935362A (zh) 資訊推送方法、裝置及設備
US20230028837A1 (en) Scaling for split-networking datapath
US10812606B2 (en) Supporting communications in a stream processing platform
WO2024103912A1 (zh) 一种请求处理方法、装置、设备及非易失性可读存储介质
US11838206B2 (en) Edge node with datapath split between pods
US20190044871A1 (en) Technologies for managing single-producer and single consumer rings
WO2024066625A1 (zh) 租户管理方法、设备和存储介质
US20210092050A1 (en) Enhanced dynamic encryption packet segmentation
CN111614694B (zh) 通信方法、装置及电子设备和计算机可读存储介质
WO2023169271A1 (zh) 一种数据存储方法及数据处理设备
CN102609293B (zh) 对c/c++进行动态实例化的方法
EP3857826B1 (en) Flexible unnumbered destination tunnels for virtual networks
KR20230038100A (ko) 클러스터화 게이트웨이의 분배 방법, 장치, 저장 매체 및 전자 기기
CN108681492A (zh) 数据处理方法及装置
CN114363254A (zh) 租户隔离方法、装置及电子设备
WO2024114157A1 (zh) 报文发送方法、设备、存储介质和承载网设备
CN117440444B (zh) 一种基于多模态网元的流量管控方法、装置及电子设备
CN110659105A (zh) 虚拟化资源处理方法、装置、设备及存储介质
CN110300068A (zh) Arp资源管理方法、装置、电子设备
TW202008153A (zh) 資料處理方法和裝置、伺服器

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23869873

Country of ref document: EP

Kind code of ref document: A1