US9887961B2 - Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking - Google Patents

Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking Download PDF

Info

Publication number
US9887961B2
US9887961B2 US14/719,723 US201514719723A US9887961B2 US 9887961 B2 US9887961 B2 US 9887961B2 US 201514719723 A US201514719723 A US 201514719723A US 9887961 B2 US9887961 B2 US 9887961B2
Authority
US
United States
Prior art keywords
dhcp
tenant
address
specific
packet
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US14/719,723
Other languages
English (en)
Other versions
US20160344687A1 (en
Inventor
Liang Rong
Gang Tang
Zi J. TAO
Ming S. XIAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kyndryl Inc
Original Assignee
International Business Machines Corp
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 International Business Machines Corp filed Critical International Business Machines Corp
Assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION reassignment INTERNATIONAL BUSINESS MACHINES CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: RONG, Liang, TANG, Gang, TAO, ZI J., XIAN, MING S.
Priority to US14/719,723 priority Critical patent/US9887961B2/en
Priority to CN201680027661.0A priority patent/CN107615716B/zh
Priority to JP2017552848A priority patent/JP6670025B2/ja
Priority to GB1720489.2A priority patent/GB2555740C/en
Priority to PCT/CN2016/082833 priority patent/WO2016188375A1/en
Priority to DE112016001657.3T priority patent/DE112016001657T5/de
Publication of US20160344687A1 publication Critical patent/US20160344687A1/en
Priority to US15/809,146 priority patent/US10425381B2/en
Publication of US9887961B2 publication Critical patent/US9887961B2/en
Application granted granted Critical
Priority to US16/526,477 priority patent/US10904206B2/en
Priority to US17/144,316 priority patent/US11546293B2/en
Assigned to KYNDRYL, INC. reassignment KYNDRYL, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INTERNATIONAL BUSINESS MACHINES CORPORATION
Priority to US18/073,787 priority patent/US11956207B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5061—Pools of addresses
    • H04L61/2015—
    • 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
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L61/2061—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • 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
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L2012/4629—LAN interconnection over a backbone network, e.g. Internet, Frame Relay using multilayer switching, e.g. layer 3 switching

Definitions

  • the technical character of the present invention generally relates to a Dynamic Host Configuration Protocol (DHCP) mechanism for a cloud networking, and more particularly, to a DHCP mechanism for multi-tenant cloud networking.
  • DHCP Dynamic Host Configuration Protocol
  • Multi-tenant support is a basic demand for cloud data center networks, which requires service isolations between different tenants.
  • One type of service isolation is address isolation which provides overlapping addresses to different tenants.
  • IETF NVO3 Internet Engineering Task Force Network Virtualization Overlays
  • VNID virtual network identifier
  • Addressing and host configuration can be provided through Dynamic Host Configuration Protocol (DHCP), which provides configuration parameters to hosts.
  • DHCP Dynamic Host Configuration Protocol
  • DHCP has two components, including a protocol for delivering host-specific configuration parameters from a DHCP server to a host and a mechanism for allocation of network addresses to hosts.
  • the protocol only supports a configuration in a single address space. Therefore, each DHCP server can only be configured with configuration parameters of a single address space (i.e., the protocol cannot support overlapped address spaces). Thus, the client of the DHCP server can only obtain an address from this single address space.
  • DHCP servers In order to provide overlapping addresses to different tenants in cloud data center networks, separate DHCP servers must be set up for each tenant. This is usually implemented by setting up a unique DHCP server in a separate LINUX namespace (i.e., operating system level virtualization) or running multiple DHCP servers in different hosts. In these implementations, there is one DHCP server for a tenant, and the addresses provided to different tenants can be overlapped.
  • LINUX namespace i.e., operating system level virtualization
  • multiple Linux namespaces are complex and resource/computation intensive since there is usually only one physical network interface card used to connect to the data network.
  • multiple Linux namespaces requires multiple virtual network interfaces to be created and connected to an Ethernet bridge to serve those namespaces and multiple DHCP server instances to be run in which each one of them only serves a single tenant or even a single network segment.
  • legacy operating systems e.g., WINDOWS SERVER and legacy LINUX kernels before 2.6.32.xx) do not support LINUX namespaces.
  • a method for that includes receiving a dynamic host configuration protocol (DHCP) packet.
  • the method further includes inserting a tenant-specific option information within the DHCP packet.
  • the method further includes transmitting the DHCP packet with the tenant-specific option information.
  • DHCP dynamic host configuration protocol
  • a computer program product that includes a computer readable storage medium having program code embodied in the storage medium.
  • the program code is not a transitory signal per se, and the program instructions are readable by a computing device to cause the computing device to perform a method that includes receiving a dynamic host configuration protocol (DHCP) packet.
  • the method further includes determining that the DHCP packet comprises tenant-specific option information.
  • the method further includes selecting an address space based on the tenant-specific option information.
  • DHCP dynamic host configuration protocol
  • a computer program that includes a computer readable storage medium having program code embodied in the storage medium.
  • the program code is not a transitory signal per se, and the program instructions are readable by a computing device to cause the computing device to perform a method that includes receiving a dynamic host configuration protocol (DHCP) packet which comprises a tenant-specific option information.
  • the method further includes locating a tenant address space based on the tenant-specific option information.
  • the method further includes obtaining a virtual network identifier from a virtual access point (VAP).
  • VAP virtual access point
  • the method further includes obtaining a subnet configuration corresponding to the obtained virtual network identifier.
  • the method further includes allocating an internet protocol (IP) address which corresponds to the obtained subnet configuration.
  • IP internet protocol
  • a system in another aspect of the invention, includes a CPU, a computer readable memory, and a computer readable storage medium. Additionally, the system includes one or more program instructions. The system includes program instructions to insert multi-tenancy information within a dynamic host configuration protocol (DHCP) packet. The system further includes program instructions to transmit the DHCP packet with the multi-tenancy information. The program instructions are stored on the computer readable storage medium for execution by the CPU via the computer readable memory.
  • DHCP dynamic host configuration protocol
  • a method for configuring a tenant-specific DHCP option frame format that includes configuring a first field of the tenant-specific DHCP option frame format to denote an overlay protocol type that is used for tenant isolation.
  • the method further includes configuring a second field of the tenant-specific DHCP option frame format to uniquely identify a tenant.
  • the method further includes configuring a third field of the tenant-specific DHCP option frame format to denote a virtual network.
  • Embodiments of the present invention provide systems and methods that implement technical features such as a novel DHCP mechanism for multi-tenant cloud networking, which addresses the issue of address isolation for different tenants in a more efficient manner than current systems.
  • tenant-specific information is included in a DHCP packet for a scoping of address space.
  • the advantage of the aforementioned technical solution for embodiments of the DHCP mechanism is that it is backwards-compatible, and does not adversely affect currently implemented systems of DHCP processing. Further, if the tenant-specific information is not provided in the DHCP packet, DHCP processing can occur in a manner as current systems.
  • the address range in the DHCP packet is scoped locally to a tenant's address space when using the DHCP tenant-specific information.
  • a single DHCP server is capable of providing DHCP services for multiple tenants, even though their address range may overlap with each other.
  • OS operating system
  • embodiments of the DHCP mechanism simplify the DHCP service provisioning in multi-tenant cloud data centers.
  • the technical features of embodiments of the DHCP mechanism also address the interoperability issue when a data center network comprises heterogeneous virtual environments offered by different vendors.
  • FIG. 1 depicts a cloud computing node according to an embodiment of the present invention.
  • FIG. 2 depicts a cloud computing environment according to embodiments of the present invention.
  • FIG. 3 depicts abstraction model layers according to embodiments of the present invention.
  • FIG. 4 depicts a cloud computing note according to another embodiment of the present invention.
  • FIG. 5 is a frame format for a tenant-specific DHCP option in accordance with aspects of the present invention.
  • FIG. 6 depicts an exemplary flow (swim diagram) for a DHCP packet processing in accordance with aspects of the present invention.
  • FIG. 7 depicts an exemplary flow for an address allocation processing in accordance with aspects of the present invention.
  • FIG. 8 depicts an exemplary flow for a DHCP subnet selection support in accordance with aspects of the present invention.
  • the technical character of the present invention generally relates to a Dynamic Host Configuration Protocol (DHCP) mechanism for a cloud networking, and more particularly, to a DHCP mechanism for multi-tenant cloud networking. More specifically, embodiments of the present invention provide systems and methods that implement technical features such as a novel DHCP mechanism for multi-tenant cloud networking, which addresses the issue of address isolation for different tenants in a more efficient manner than current systems. For example, in embodiments of the DHCP mechanism, tenant-specific information is included in a DHCP packet for a scoping of address space.
  • DHCP Dynamic Host Configuration Protocol
  • the advantage of the aforementioned technical solution for embodiments of the DHCP mechanism is that it is backwards-compatible, and does not adversely affect currently implemented systems of DHCP processing. Further, if the tenant-specific information is not provided in the DHCP packet, DHCP processing can occur in a manner as current systems. Moreover, in comparison to an address range in the DHCP packet which has a global scope, in the technical features of embodiments of the DHCP mechanism, the address range in the DHCP packet is scoped locally to a tenant's address space when using the DHCP tenant-specific information.
  • a single DHCP server is capable of providing DHCP services for multiple tenants, even though their address range may overlap with each other.
  • OS operating system
  • embodiments of the DHCP mechanism simplify the DHCP service provisioning in multi-tenant cloud data centers.
  • the technical features of embodiments of the DHCP mechanism also address the interoperability issue when a data center network comprises heterogeneous virtual environments offered by different vendors.
  • a single DHCP server providing addressing service is used for multiple tenants in a cloud data center based on overlay networks.
  • Embodiments of the DHCP mechanism help to solve the following technical issues in DHCP systems:
  • embodiments of the DHCP mechanism do not disrupt current DHCP interactions between clients and a server, such as DHCP DISCOVER, OFFER, REQUEST, ACKNOWLEDGMENT, RELEASE, etc.
  • the DHCP interactions also work in embodiments of the DHCP mechanism of the present invention.
  • the tenant-specific option is used as an indicator for a DHCP server to allocate an internet protocol (IP) address on an associated address space specific to that tenant.
  • IP internet protocol
  • a single DHCP server can serve a plurality of tenants, and each tenant can have its own IP address pool for allocation.
  • each pool in a tenant is totally independent and can be overlapped (i.e., same IP address pool) with another pool for a different tenant.
  • the tenant-specific option is added to a DHCP header by a DHCP relay agent.
  • the tenant-specific option comprises the following fields:
  • transport agent encoding value to denote the overlay protocol type that is used for tenant isolation (e.g., VLAN, VXLAN, DOVE, NVGRE, STT, etc.);
  • tenant ID a universally unique identifier (UUID) used to identify a tenant
  • VNID virtual network ID
  • the tenant specific option is implemented as a sub-option in a DHCP relay agent information option (option 82, RFC 3046).
  • the implementation adds a sub-option in the option 82 standard to include the proposed tenant-specific option.
  • the tenant-specific option is added to the DHCP header by a DHCP relay agent, which runs on a network virtualization edge (NVE). Since the NVE is on an edge of the overlay network, it is easy to derive the encoding value of a transport agent in the tenant specific option.
  • the VNID can be derived from a virtual access point (VAP) on which the DHCP client connects.
  • VAP virtual access point
  • the DHCP server supports two types of address spaces: global address space and tenant address space.
  • the global address space is compatible with a known DHCP mechanism in which a tenant-specific option is not present in the DHCP packet.
  • the IP address ranges cannot be overlapped; whereas, in the technical solution using embodiments of the DHCP mechanism of the present invention, each tenant has a specific address pool in the tenant address space, and the address range in the DHCP mechanism can be overlapped across different tenant's address pool.
  • a DHCP server performs a known DHCP processing. Otherwise, if the DHCP_DISCOVER message includes the tenant specific option, the tenant specific option is used to locate the tenant address space and IP range. The DHCP server locates the address space corresponding to the tenant ID in the tenant-specific option. If the DHCP_DISCOVER message has a subnet selection option (option 118) or a link selection sub-option (sub-option 5 in option 82), the DHCP server will allocate an address from that subnet.
  • DHCP_DISCOVER message does not have a subnet selection option or a link selection sub-option, an IP range is associated to a VNID, and the DHCP server will find the IP range according to the VNID in the tenant specific option.
  • embodiments of the DHCP mechanism of the present invention can include a DHCP server which uses a matching criteria or access control list (ACL) rules on the tenant-specific option in the configuration to locate the tenant address space.
  • ACL access control list
  • a cloud service provider may employ various overlay network solutions from different vendors to achieve a multi-tenant cloud data center. Therefore, embodiments of the DHCP mechanism can be utilized when the network size is expanded.
  • the CSP may have two overlay networks, and these overlay networks may be built on top of a common physical network.
  • a tenant may have virtual machines in both overlay networks. Therefore, in embodiments of the novel DHCP mechanism, there is a convenient way to provision the DHCP server in the physical network in case of a tenant having virtual machines spanning across heterogeneous overlay networks.
  • the transport agent field in a tenant specific option is used to provision the DHCP server.
  • the DHCP server in embodiments of the DHCP mechanism can use the transport agent, together with VNID, in the tenant specific option, as the classification fields to derive the IP range from which IP addresses are allocated.
  • a transport agent may be added as a dimension in the classification criteria to locate the IP address range in the tenant address space.
  • Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service.
  • This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
  • On-demand self-service a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.
  • Resource pooling the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).
  • Rapid elasticity capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
  • Measured service cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.
  • level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts).
  • SaaS Software as a Service: the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure.
  • the applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail).
  • a web browser e.g., web-based e-mail
  • the consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
  • PaaS Platform as a Service
  • the consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
  • IaaS Infrastructure as a Service
  • the consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
  • Private cloud the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
  • Public cloud the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
  • Hybrid cloud the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
  • a cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability.
  • An infrastructure comprising a network of interconnected nodes.
  • Cloud computing node 10 is only one example of a suitable cloud computing node and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention described herein. Regardless, cloud computing node 10 is capable of being implemented and/or performing any of the functionality set forth hereinabove.
  • cloud computing node 10 there is a computer system/server 12 , which is operational with numerous other general purpose or special purpose computing system environments or configurations.
  • Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.
  • Computer system/server 12 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system.
  • program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types.
  • Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computer system storage media including memory storage devices.
  • computer system/server 12 in cloud computing node 10 is shown in the form of a general-purpose computing device.
  • the components of computer system/server 12 may include, but are not limited to, one or more processors or processing units 16 , a system memory 28 , and a bus 18 that couples various system components including system memory 28 to processor 16 .
  • Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.
  • bus architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.
  • Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12 , and it includes both volatile and non-volatile media, removable and non-removable media.
  • System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32 .
  • Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media.
  • storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”).
  • a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”).
  • an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided.
  • memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
  • Program/utility 40 having a set (at least one) of program modules 42 , may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment.
  • Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.
  • a DHCP client 80 can be implemented as one or more of the program modules 42 .
  • the DHCP client 80 may be implemented as separate dedicated processors or a single or several processors to provide the functionality described herein.
  • the DHCP client 80 performs one or more of the processes described herein.
  • Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24 , etc.; one or more devices that enable a user to interact with computer system/server 12 ; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via I/O interfaces 22 . Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20 . As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18 .
  • LAN local area network
  • WAN wide area network
  • public network e.g., the Internet
  • cloud computing environment 50 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54 A, desktop computer 54 B, laptop computer 54 C, and/or automobile computer system 54 N may communicate.
  • Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof.
  • This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device.
  • computing devices 54 A-N shown in FIG. 2 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).
  • FIG. 3 a set of functional abstraction layers provided by cloud computing environment 50 ( FIG. 2 ) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 3 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:
  • Hardware and software layer 60 includes hardware and software components.
  • hardware components include mainframes 61 ; RISC (Reduced Instruction Set Computer) architecture based servers 62 ; servers 63 ; blade servers 64 ; storage device 65 ; and networks and networking components 66 .
  • software components include network application server software 67 and database software 68 .
  • Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71 ; virtual storage 72 ; virtual networks 73 , including virtual private networks; virtual applications and operating systems 74 ; and virtual clients 75 .
  • management layer 80 may provide the functions described below.
  • Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment.
  • Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses.
  • Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources.
  • User portal 83 provides access to the cloud computing environment for consumers and system administrators.
  • Service level management 84 provides cloud computing resource allocation and management such that required service levels are met.
  • Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.
  • SLA Service Level Agreement
  • Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91 ; software development and lifecycle management 92 ; virtual classroom education delivery 93 ; data analytics processing 94 ; transaction processing 95 ; and DHCP processes 96 described herein. In accordance with aspects of the invention, the DHCP processes 96 workload/function operates to perform one or more of the processes described herein.
  • FIG. 4 depicts a cloud computing node according to another embodiment of the present invention.
  • FIG. 4 is another cloud computing node which comprises a same cloud computing node 10 as FIG. 1 .
  • the computer system/server 12 also comprises or communicates with a DHCP client 170 , a DHCP server 160 , and a DHCP relay agent 180 , as described in greater detail herein.
  • the DHCP client 170 , the DHCP server 160 , and the DHCP relay agent 180 can be implemented as one or more program code in program modules 42 stored in memory as separate or combined modules. Additionally, the DHCP client 170 , the DHCP server 160 , and the DHCP relay agent 180 may be implemented as separate dedicated processors or a single or several processors to provide the function of these tools. While executing the computer program code, the processing unit 16 can read and/or write data to/from memory, storage system, and/or I/O interface 22 . The program code executes the processes of the invention.
  • DHCP client 170 may be configured to send a DHCP request packet to a DHCP server 160 via a cloud computing environment 50 .
  • cloud computing environment 50 may be the Internet, a local area network, a wide area network, and/or a wireless network.
  • the DHCP server 160 allocates an IP address for the DHCP client 170 .
  • DHCP server 160 may provide direct support for multi-tenancy on the DHCP protocol using a tenant-specific DHCP option to carry tenant information.
  • the DHCP server 160 can support overlapped IP address spaces.
  • the DHCP server 160 provides numerous advantages and technical solutions over known OS virtualization for multi-tenancy, including addressing inter-operability between different encapsulation protocols for multi-tenant isolation, high scalability (e.g., not as computationally intensive), and seamlessly supports the software defined networking (SDN) address allocation requirement.
  • a DHCP relay agent 180 may be used as an intermediary to relay messages between DHCP client 170 and DHCP server 160 via the cloud computing environment 50 .
  • DHCP client 170 and DHCP server 160 may communicate directly with each other without use of the DHCP relay agent 180 .
  • the present invention may be a system, a method, and/or a computer program product.
  • the computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
  • the computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device.
  • the computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
  • a non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • SRAM static random access memory
  • CD-ROM compact disc read-only memory
  • DVD digital versatile disk
  • memory stick a floppy disk
  • a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon
  • a computer readable storage medium is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
  • Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
  • the network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.
  • a network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
  • Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages.
  • the computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
  • These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the functions noted in the block may occur out of the order noted in the figures.
  • two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • FIG. 5 is a frame format for a tenant-specific DHCP option in accordance with aspects of the present invention. More specifically, FIG. 5 depicts a tenant-specific DHCP option frame format 100 for carrying tenant information.
  • the tenant-specific DHCP option frame format 100 includes a variety of fields, including, but not limited to option 110 , length 120 , transport agent 130 , tenant ID 140 , and virtual network ID 150 .
  • Option 110 is a unique value in DHCP options.
  • Length 120 is a total number of bytes of remaining fields.
  • Transport agent 130 is an encoding value used to denote the overlay protocol type that is used for tenant isolation, e.g., VLAN, VXLAN, DOVE, NVGRE, STT, etc.
  • Tenant ID 140 is a universally unique identifier (UUID) used to identify a tenant.
  • virtual network ID 150 denotes a virtual network, which is an abstract of a L2 segment or broadcast domain.
  • the tenant-specific DHCP option frame format 100 is an indicator for a DHCP server to allocate an IP address on associated address space to that tenant. Therefore, a single DHCP server can serve a plurality of tenants, and each tenant can have its own IP address pool for allocation. The pools in different tenants are totally independent, and can be overlapped.
  • the tenant-specific option frame format 100 can be added to a DHCP header by a DHCP relay agent.
  • the tenant-specific option is a sub-option in DHCP relay agent information option (option 82, RFC 3046). Therefore, implementation will add a sub-option in the option 82 to include the tenant-specific option frame format 100 .
  • FIGS. 6-8 show exemplary flows (or swim lane diagrams) for performing aspects of the present invention.
  • the steps of FIGS. 6-8 may be implemented in the environment of FIGS. 1 and 4 , for example.
  • the flowchart(s) illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products as already described herein in accordance with the various embodiments of the present invention.
  • the flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
  • FIG. 6 depicts an exemplary flow (swim diagram) for a DHCP packet processing in accordance with aspects of the present invention. More specifically, FIG. 6 shows a tenant-specific option added to the DHCP header by a DHCP relay agent.
  • NVE network virtualization edge
  • a virtual network identifier (VNID) can be derived from a virtual access point (VAP) to which the DHCP client connects.
  • VAP virtual access point
  • the VAP is a logical connection point on the NVE for connecting a tenant system to a virtual network.
  • VAPs can be physical ports or virtual ports identified through logical interface identifiers, such as VLAN ID or internal vSwitch Interface ID connected to a virtual machine (VM).
  • the tenant ID in the tenant-specific option can be derived through the VNID by consulting the local cache or remote database in NVA that consists of the mapping between VNID and tenant ID.
  • a gateway IP interface is needed, on which DHCP client packets on that L2 segment will be received. Therefore, in current DHCP systems, upon receiving a DHCP message from a DHCP client, the IP address of the IP interface will be filled in the GIADDR field of the DHCP packet if it is zero, and the DHCP message is sent to the DHCP server. In other words, the GIADDR is added by the first DHCP relay agent. The DHCP server will use the GIADDR to allocate the IP address and other network parameter to the DHCP client. The DHCP server will send a corresponding DHCP relay message to a DHCP relay agent identified by the GIADDR. The DHCP relay agent is designed to send the DHCP reply message to the directly connected DHCP clients—the clients in the same L2 segment as the IP interface of the DHCP relay agent identified by the GIADDR.
  • DHCP clients are running in the overlay network, and the overlay networks of different tenants are isolated.
  • the DHCP server is designed to serve all the DHCP clients in different tenant overlay networks.
  • the DHCP server and DHCP relay agents will communicate through the underlay network.
  • the GIADDR added by the DHCP relay agent will be an underlay IP address of the relay agent.
  • the DHCP server will not use the GIADDR to allocate the IP address and other network parameters to DHCP client.
  • the DHCP server will use the tenant-specific option and other options to allocate the IP address and other network parameters to the DHCP client.
  • the DHCP server will send a corresponding DHCP reply message to a DHCP relay agent identified by the GIADDR.
  • the relay agent will use the VNID in tenant-specific option to deliver the DHCP reply message to the DHCP client accordingly.
  • FIG. 6 depicts an exemplary flow or swim lane diagram for a DHCP packet processing in accordance with aspects of the present invention.
  • FIG. 5 includes the following actors: DHCP client 210 (an example of DHCP client 170 described with regard to FIG. 4 ), DHCP relay agent 220 (an example of DHCP relay agent 180 with regard to FIG. 4 ), and DHCP server 230 (an example of DHCP server 160 described with regard of FIG. 4 ).
  • a DHCP client 210 sends a DHCP_DISCOVER message to a DHCP relay agent 220 .
  • the DHCP relay agent 220 sends a DHCP_DISCOVER with tenant specific option message to DHCP server 230 .
  • the DCHP server 230 then sends a DHCP_OFFER with tenant specific option message to DHCP relay agent 220 .
  • DHCP relay agent 220 sends a DHCP_OFFER message to DHCP client 210 .
  • DHCP client 210 sends a DHCP_REQUEST message to the DHCP relay agent 220 .
  • the DHCP relay agent 220 sends a DHCP_REQUEST with tenant specific option message to DHCP server 230 , at step 236 .
  • DHCP server 230 sends a DHCP_ACK with tenant specific option message to DHCP relay agent 220 .
  • DHCP relay agent 220 sends a DHCP_ACK message to DHCP client 210 .
  • FIG. 7 depicts an exemplary flow for an address allocation processing in accordance with aspects of the present invention.
  • the DHCP server supports two types of address spaces: global address space and tenant address space.
  • the global address space is compatible with current DHCP methods in which a tenant-specific option is not present in the DHCP packet.
  • the IP address ranges cannot be overlapped; whereas, in contrast, in the technical solutions of the DHCP mechanism of the depicted embodiment of the present invention, each tenant has a specific address pool in the tenant address space.
  • the address range in the DHCP mechanism of the depicted embodiment can be overlapped across different tenant's address pool.
  • the DHCP server performs a known DHCP processing. Otherwise, if the DHCP_DISCOVER message includes the tenant specific option, the tenant specific option is used to locate the tenant address space and IP range. The DHCP server locates the address space corresponding to the tenant ID in the tenant-specific option. Also, in FIG. 7 , if the DHCP_DISCOVER message has a subnet selection option (option 118) or a link selection sub-option (sub-option 5 in option 82), the DHCP server will allocate an address from that subnet.
  • the novel DHCP mechanism of the depicted embodiment can include a DHCP server which uses a matching criteria or access control list (ACL) rules on the tenant-specific option in the configuration to locate the tenant address space.
  • ACL access control list
  • a DHCP server receives a DHCP request packet.
  • the processes and systems of the DHCP server determine whether the DHCP request (e.g., DHCP_DISCOVER) has a specific option. If the DHCP request does not have a tenant specific option (i.e., NO), at step 315 , the DHCP server uses a global address space. Then, at step 320 , known DHCP protocol processing is performed by the DHCP server and the DHCP client, since there is no tenant specific option.
  • DHCP_DISCOVER a tenant specific option
  • an address space is chosen by the DHCP server according to the tenant specific option field.
  • a determination is made by the DHCP server as to whether there is either a link selection (option 118) or a subnet selection option (opt 82 subopt 5) in the DHCP request. If there is no link (i.e., NO) at step 345 , an address is allocated for VNID by the DHCP server.
  • step 330 if there is either a link selection (option 118) or a subnet selection option (opt 82 subopt 5) in the DHCP request (i.e., YES), then at step 335 , there is a check by the DHCP server whether an available address in a requesting subnet.
  • step 335 if there is an available address in the requesting subnet (i.e., YES), at step 340 , an address is allocated in the subnet by the DHCP server.
  • step 335 if there is not an available address in the requesting subnet (i.e., NO), at step 345 , an address is allocated for VNID by the DHCP server.
  • FIG. 8 depicts an exemplary flow for a DHCP subnet selection support in accordance with aspects of the present invention.
  • a DHCP client 410 sends a DHCP_DISCOVER message to a DHCP relay agent 420 in step 441 .
  • DHCP relay agent 420 locates the tenant address space according to the tenant ID in the tenant specific option and allocates an IP address in the intended subnet.
  • the DHCP relay agent 420 derives its VNID from an associated VAP. Then, in FIG.
  • the DHCP relay agent 420 sends a query subnet of VNIDx message to a network virtualization authority (NVA) 440 to inquire of the subnet configuration of that VNID.
  • NVA network virtualization authority
  • a reply for the subnet of VNIDx is sent by the NVA 440 to the DHCP relay agent in step 443 .
  • the DHCP_DISCOVER with tenant specific option and subnet selection option 118 or option 82 with subopt 5 is sent to DHCP server 430 .
  • a DHCP subnet selection option (option 118, RFC3011) and a link selection in relay agent information option (option 82, suboption 5, RFC3527) are used to communicate to a DHCP server on a desired subnet from which the DHCP clients expect to obtain their IP address. Therefore, the novel DHCP mechanism of the depicted embodiment can be easily extended to these situations through NVA.
  • a NVA can maintain the subnet configuration for each VNID.
  • the DHCP relay agent 420 derives its VNID from the associated VAP. After that, the DHCP relay agent 420 sends a query to NVA 440 to inquire of the subnet configuration of that VNID.
  • the subnet configuration which is replied by NVA 440 , is then filled in the DHCP option 118 or option 82—suboption 5.
  • the subnet information is then communicated to DHCP server 430 together with the tenant-specification option.
  • DHCP server 430 When DHCP server 430 receives the DHCP_DISCOVER packet, DHCP server 430 locates the tenant address space according to tenant ID in the tenant specific option and allocates an IP address in the intended subnet which is carried in the DHCP option 118 or option 82—suboption 5.
  • a service provider such as a Solution Integrator, could offer to perform the processes described herein.
  • the service provider can create, maintain, deploy, support, etc., the computer infrastructure that performs the process steps of the invention for one or more customers. These customers may be, for example, any business that uses technology.
  • the service provider can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
  • the DHCP mechanism provides numerous advantages over current systems. These advantages include, but are not limited to, providing direct support for multi-tenancy on DHCP protocol and removing the need of LINUX namespace OS-level virtualization to support multi-tenancy.
  • this technical solution is accomplished by formulating a tenant-specific DHCP option to carry tenant information and improving an address allocation scheme on a DHCP server to prioritize IP address allocation on the tenant address space once tenant-specific option is detected in the DHCP packet.
  • both the DHCP client and the DHCP relay agent can add tenant-specific option.
  • an interoperability issue between different encapsulation protocols for multi-tenant isolation e.g., VLAN, VXLAN, DOVE, NVGRE, STT, etc. is alleviated.
  • embodiments of the DHCP mechanism provide high scalability as the number of tenants grows. For example, in current systems, OS-virtualization to support multi-tenancy increases computational burden because each instance of a LINUX namespace requires additional resources; whereas, in embodiments of the DHCP mechanism of the present invention, computational burden is reduced in comparison to OS-level virtualization. Further, in embodiments of the DHCP mechanism, a SDN address allocation requirement is seamlessly supported because each DHCP client gets correct addresses belonging to its tenant and its connected virtual network.
  • the systems and processes described herein provide a computer-implemented method for multi-tenancy support on a DHCP protocol, on a network.
  • a computer infrastructure such as the computer system shown in FIGS. 1 and 4 or the cloud environment shown in FIG. 2 can be provided and one or more systems for performing the processes of the invention can be obtained (e.g., created, purchased, used, modified, etc.) and deployed to the computer infrastructure.
  • the deployment of a system can comprise one or more of:
US14/719,723 2015-05-22 2015-05-22 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking Active 2035-12-22 US9887961B2 (en)

Priority Applications (10)

Application Number Priority Date Filing Date Title
US14/719,723 US9887961B2 (en) 2015-05-22 2015-05-22 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
CN201680027661.0A CN107615716B (zh) 2015-05-22 2016-05-20 用于云联网的多租户感知动态主机配置协议(dhcp)机制
JP2017552848A JP6670025B2 (ja) 2015-05-22 2016-05-20 クラウド・ネットワーキングのためのマルチテナント認識型動的ホスト構成プロトコル（ｄｈｃｐ）機構
GB1720489.2A GB2555740C (en) 2015-05-22 2016-05-20 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
PCT/CN2016/082833 WO2016188375A1 (en) 2015-05-22 2016-05-20 Multi-tenant aware dynamic host configuration protocol (dhcp) mechanism for cloud networking
DE112016001657.3T DE112016001657T5 (de) 2015-05-22 2016-05-20 Multi-Tenant-Sensitiver DHCP-Mechanismus für Cloud-Netzwerke
US15/809,146 US10425381B2 (en) 2015-05-22 2017-11-10 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US16/526,477 US10904206B2 (en) 2015-05-22 2019-07-30 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US17/144,316 US11546293B2 (en) 2015-05-22 2021-01-08 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US18/073,787 US11956207B2 (en) 2015-05-22 2022-12-02 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/719,723 US9887961B2 (en) 2015-05-22 2015-05-22 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/809,146 Continuation US10425381B2 (en) 2015-05-22 2017-11-10 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking

Publications (2)

Publication Number Publication Date
US20160344687A1 US20160344687A1 (en) 2016-11-24
US9887961B2 true US9887961B2 (en) 2018-02-06

Family

ID=57325828

Family Applications (5)

Application Number Title Priority Date Filing Date
US14/719,723 Active 2035-12-22 US9887961B2 (en) 2015-05-22 2015-05-22 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US15/809,146 Active US10425381B2 (en) 2015-05-22 2017-11-10 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US16/526,477 Active US10904206B2 (en) 2015-05-22 2019-07-30 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US17/144,316 Active 2035-06-03 US11546293B2 (en) 2015-05-22 2021-01-08 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US18/073,787 Active US11956207B2 (en) 2015-05-22 2022-12-02 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking

Family Applications After (4)

Application Number Title Priority Date Filing Date
US15/809,146 Active US10425381B2 (en) 2015-05-22 2017-11-10 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US16/526,477 Active US10904206B2 (en) 2015-05-22 2019-07-30 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US17/144,316 Active 2035-06-03 US11546293B2 (en) 2015-05-22 2021-01-08 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US18/073,787 Active US11956207B2 (en) 2015-05-22 2022-12-02 Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking

Country Status (6)

Country Link
US (5) US9887961B2 (de)
JP (1) JP6670025B2 (de)
CN (1) CN107615716B (de)
DE (1) DE112016001657T5 (de)
GB (1) GB2555740C (de)
WO (1) WO2016188375A1 (de)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10812446B1 (en) 2019-07-22 2020-10-20 Cisco Technology, Inc. Dynamic host configuration across multiple sites in software defined access networks
US10904206B2 (en) 2015-05-22 2021-01-26 International Business Machines Corporation Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10142284B2 (en) * 2015-09-30 2018-11-27 Vmware, Inc. Faster IP address allocation in a hybrid cloud environment using subnet selective randomization
US10931629B2 (en) * 2016-05-27 2021-02-23 Cisco Technology, Inc. Techniques for managing software defined networking controller in-band communications in a data center network
CN108667886B (zh) * 2017-04-01 2020-07-28 华为技术有限公司 提供PaaS服务的方法、管理系统和云计算服务架构
US10715597B2 (en) 2017-06-16 2020-07-14 At&T Intellectual Property I, L.P. Methods and systems to create a network-agnostic SDN-based cloud gateway for connectivity to multiple cloud service providers
CN110324248B (zh) * 2018-03-30 2021-07-30 中移(苏州)软件技术有限公司 一种裸金属服务器路由更新方法、装置、电子设备及介质
US11165634B2 (en) * 2018-04-02 2021-11-02 Oracle International Corporation Data replication conflict detection and resolution for a multi-tenant identity cloud service
CN110855599B (zh) * 2018-08-20 2022-10-21 中兴通讯股份有限公司 一种多租户访问控制方法及装置、计算机可读存储介质
US10826916B2 (en) * 2018-09-17 2020-11-03 ShieldX Networks, Inc. Agent-less network traffic inspection using an overlay network
US10848423B1 (en) * 2018-09-26 2020-11-24 Amazon Technologies, Inc. Multi-account gateway
CN111294319B (zh) * 2018-12-07 2022-05-27 网宿科技股份有限公司 网络隔离的方法、装置，网络设备和可读存储介质
EP3694173B1 (de) 2019-02-08 2022-09-21 Palantir Technologies Inc. Isolieren von anwendungen, die mehreren mandanten innerhalb einer computerplattform zugeordnet sind
CN111614790B (zh) * 2019-02-26 2022-08-05 杭州海康威视系统技术有限公司 虚拟机地址配置系统、方法及装置
US11146634B2 (en) 2019-04-25 2021-10-12 International Business Machines Corporation Storage pool isolation
CN113055500B (zh) * 2019-12-26 2022-08-30 中国电信股份有限公司 地址请求方法、装置及计算机可读存储介质
CN111200644A (zh) * 2019-12-27 2020-05-26 福建升腾资讯有限公司 一种基于中继服务器在互联网环境下镜像缓存方法及系统
US11502993B2 (en) * 2020-08-10 2022-11-15 Perimeter 81 Ltd Scalable and on-demand multi-tenant and multi region secure network
US11425044B2 (en) * 2020-10-15 2022-08-23 Cisco Technology, Inc. DHCP layer 2 relay in VXLAN overlay fabric
US11463312B2 (en) 2021-01-21 2022-10-04 Cisco Technology, Inc. Secure onboarding of network devices
CN113259500A (zh) * 2021-03-30 2021-08-13 紫光云技术有限公司 一种ovs网络dhcp地址池方法
CN113726738B (zh) * 2021-07-26 2023-08-18 新华三技术有限公司合肥分公司 获取被测设备物理位置信息方法及网络设备、存储介质
CN114244842B (zh) * 2021-12-23 2023-07-25 绿盟科技集团股份有限公司 一种安全资源调度方法、装置、电子设备及存储介质

Citations (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7051089B1 (en) * 2001-10-24 2006-05-23 Cisco Technology, Inc. Techniques for automatically delegating address spaces among dynamic host configuration servers
US7152117B1 (en) 2001-10-04 2006-12-19 Cisco Technology, Inc. Techniques for dynamic host configuration using overlapping network
US7586912B2 (en) 2006-07-28 2009-09-08 Cisco Technology, Inc. Techniques for exchanging DHCP information among DHCP relay agents and DHCP servers
US20090279454A1 (en) * 2007-08-04 2009-11-12 Michael Wacker Method for configuring a dhcp server using dhcp option 82
US7707277B2 (en) 2007-04-27 2010-04-27 Alcatel Lucent Method and system for configuring pseudowires using dynamic host configuration protocol (DHCP) messages
US20100274924A1 (en) * 2009-04-24 2010-10-28 Nortel Networks Limited Method and Apparatus for Accommodating Duplicate MAC Addresses
US20100275248A1 (en) * 2008-01-03 2010-10-28 Huawei Technologies Co., Ltd. Method, apparatus and system for selecting service network
US20110213870A1 (en) 2010-02-26 2011-09-01 International Business Machines Corporation Providing services to multiple tenants of an application
US20120269091A1 (en) * 2011-04-19 2012-10-25 Janus Ahrensbach Auto-configuration of network devices
US20130086236A1 (en) * 2011-09-30 2013-04-04 Stephan Baucke Using mpls for virtual private cloud network isolation in openflow-enabled cloud computing
US20130125124A1 (en) * 2011-09-30 2013-05-16 Telefonaktiebolaget L M Ericsson (Publ) Apparatus and method for segregating tenant specific data when using mpls in openflow-enabled cloud computing
US20130297752A1 (en) * 2012-05-02 2013-11-07 Cisco Technology, Inc. Provisioning network segments based on tenant identity
US20130332577A1 (en) 2012-06-06 2013-12-12 Juniper Networks, Inc. Multitenant server for virtual networks within datacenter
US20140006585A1 (en) 2012-06-29 2014-01-02 Futurewei Technologies, Inc. Providing Mobility in Overlay Networks
WO2014083449A1 (en) 2012-11-27 2014-06-05 Telefonaktiebolaget L M Ericsson (Publ) Apparatus and method for segregating tenant specific data when using mpls in openflow-enabled cloud computing
US8825839B2 (en) 2010-11-24 2014-09-02 Unisys Corporation Snooping DNS messages in a server hosting system providing overlapping address and name spaces
EP2866389A1 (de) 2012-07-24 2015-04-29 ZTE Corporation Verfahren und vorrichtung zum automatischen auffinden und konfigurieren eines virtuellen netzwerkes
US20150120962A1 (en) 2013-10-25 2015-04-30 International Business Machines Corporation Sharing a java virtual machine
US20150124823A1 (en) * 2013-11-05 2015-05-07 Cisco Technology, Inc. Tenant dhcp in an overlay network
US20160330120A1 (en) * 2015-05-08 2016-11-10 Cisco Technology, Inc. Dynamic host configuration protocol relay in a multipod fabric

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2348598A1 (en) * 2001-06-05 2002-12-05 Mediatrix Telecom Inc. Generic method for customization of dhcp options
JP2010193051A (ja) 2009-02-17 2010-09-02 Fujitsu Telecom Networks Ltd ネットワーク管理方法、ｄｈｃｐリレーエージェントおよびｄｈｃｐサーバ
EP2480045B1 (de) 2011-01-13 2015-04-08 Alcatel Lucent Anordnung zur Bereitstellung von Funktionen eines mobilen IP-CAN-Gateways und Verwendung solch einer Anordnung zur Verkehrsentlastung von besagtem mobilen IP-CAN
CN103813288A (zh) * 2012-11-06 2014-05-21 中兴通讯股份有限公司 基于移动网络的租户网络业务实现方法、系统及网元
WO2015021629A1 (zh) * 2013-08-15 2015-02-19 华为技术有限公司 一种资源发放方法
US10439988B2 (en) * 2013-08-21 2019-10-08 Vmware, Inc. On premises, remotely managed, host computers for virtual desktops
US9979602B1 (en) * 2014-08-25 2018-05-22 Cisco Technology, Inc. Network function virtualization infrastructure pod in a network environment
CN104253878B (zh) * 2014-09-09 2018-04-17 烽火通信科技股份有限公司 Dhcp relay终结子接口的vlan信息管理系统及方法
CN104468775B (zh) * 2014-12-05 2017-10-10 国云科技股份有限公司 一种适用于云计算的分布式路由器实现方法
CN105991435B (zh) * 2015-02-05 2019-08-27 华为技术有限公司 用于获取端口路径的方法及装置
US9742726B2 (en) * 2015-02-26 2017-08-22 Red Hat Israel, Ltd. Distributed dynamic host configuration protocol
US9887961B2 (en) 2015-05-22 2018-02-06 International Business Machines Corporation Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking

Patent Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7152117B1 (en) 2001-10-04 2006-12-19 Cisco Technology, Inc. Techniques for dynamic host configuration using overlapping network
US7051089B1 (en) * 2001-10-24 2006-05-23 Cisco Technology, Inc. Techniques for automatically delegating address spaces among dynamic host configuration servers
US7586912B2 (en) 2006-07-28 2009-09-08 Cisco Technology, Inc. Techniques for exchanging DHCP information among DHCP relay agents and DHCP servers
US7707277B2 (en) 2007-04-27 2010-04-27 Alcatel Lucent Method and system for configuring pseudowires using dynamic host configuration protocol (DHCP) messages
US20090279454A1 (en) * 2007-08-04 2009-11-12 Michael Wacker Method for configuring a dhcp server using dhcp option 82
US20100275248A1 (en) * 2008-01-03 2010-10-28 Huawei Technologies Co., Ltd. Method, apparatus and system for selecting service network
US20100274924A1 (en) * 2009-04-24 2010-10-28 Nortel Networks Limited Method and Apparatus for Accommodating Duplicate MAC Addresses
US20110213870A1 (en) 2010-02-26 2011-09-01 International Business Machines Corporation Providing services to multiple tenants of an application
US8825839B2 (en) 2010-11-24 2014-09-02 Unisys Corporation Snooping DNS messages in a server hosting system providing overlapping address and name spaces
US20120269091A1 (en) * 2011-04-19 2012-10-25 Janus Ahrensbach Auto-configuration of network devices
US20130125124A1 (en) * 2011-09-30 2013-05-16 Telefonaktiebolaget L M Ericsson (Publ) Apparatus and method for segregating tenant specific data when using mpls in openflow-enabled cloud computing
US20130086236A1 (en) * 2011-09-30 2013-04-04 Stephan Baucke Using mpls for virtual private cloud network isolation in openflow-enabled cloud computing
US20130297752A1 (en) * 2012-05-02 2013-11-07 Cisco Technology, Inc. Provisioning network segments based on tenant identity
US20130332577A1 (en) 2012-06-06 2013-12-12 Juniper Networks, Inc. Multitenant server for virtual networks within datacenter
US20140006585A1 (en) 2012-06-29 2014-01-02 Futurewei Technologies, Inc. Providing Mobility in Overlay Networks
EP2866389A1 (de) 2012-07-24 2015-04-29 ZTE Corporation Verfahren und vorrichtung zum automatischen auffinden und konfigurieren eines virtuellen netzwerkes
US20150188769A1 (en) * 2012-07-24 2015-07-02 Zte Corporation Method and device thereof for automatically finding and configuring virtual network
WO2014083449A1 (en) 2012-11-27 2014-06-05 Telefonaktiebolaget L M Ericsson (Publ) Apparatus and method for segregating tenant specific data when using mpls in openflow-enabled cloud computing
US20150120962A1 (en) 2013-10-25 2015-04-30 International Business Machines Corporation Sharing a java virtual machine
US20150124823A1 (en) * 2013-11-05 2015-05-07 Cisco Technology, Inc. Tenant dhcp in an overlay network
US20160330120A1 (en) * 2015-05-08 2016-11-10 Cisco Technology, Inc. Dynamic host configuration protocol relay in a multipod fabric
US9634934B2 (en) * 2015-05-08 2017-04-25 Cisco Technology, Inc. Dynamic host configuration protocol relay in a multipod fabric

Non-Patent Citations (8)

* Cited by examiner, † Cited by third party
Title
"List of IBM Patents or Patent Applications Treated as Related," 1 page.
Durairaj et al., "Multi-Tenancy Isolation in Datacenter Networks", Cisco Systems, Inc., IPCOM000212015D, Oct. 25, 2011, 14 pages.
International Search Report for PCT Application No. PCT/CN2016/082833, 4 pages.
Jain, "Multi-Tenant Isolation and Network Virtualization in Cloud Data Centers", Washington University in Saint Louis, http://www.cse.wustl.edu/˜jain/cse570-13/, 2013, 32 pages.
Koichi Onoue, Naoki Matsuoka, Jun Tanaka; "Host-based multi-tenant technology for scalable data center networks"; 2012; ACM/IEEE Symposium on Architectures for Networking and Communications Systems (ANCS); pp. 87-98. *
Narten et al., "Overlays for Network Virtualization Draft-IETF-NVO3-Overlay-Problem Statement", Internet Engineering Task Force, Apr. 26, 2013, 26 pages.
Nritten Opinion of the International Searching Authority for PCT Application No. PCT/CN2016/082833, dated Jul. 26, 2016, 4 pages.
Specification "Multi-Tenant Aware Dynamic Host Configuration Protocol (DHCP) Mechanism For Cloud Networking" and drawings in related U.S. Appl. No. 15/809,146, filed Nov. 10, 2017, 47 pages.

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10904206B2 (en) 2015-05-22 2021-01-26 International Business Machines Corporation Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US11546293B2 (en) 2015-05-22 2023-01-03 Kyndryl, Inc. Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US11956207B2 (en) 2015-05-22 2024-04-09 Kyndryl, Inc. Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US10812446B1 (en) 2019-07-22 2020-10-20 Cisco Technology, Inc. Dynamic host configuration across multiple sites in software defined access networks

Also Published As

Publication number Publication date
US20160344687A1 (en) 2016-11-24
US10425381B2 (en) 2019-09-24
US20180077114A1 (en) 2018-03-15
GB201720489D0 (en) 2018-01-24
GB2555740C (en) 2021-11-24
US20210136031A1 (en) 2021-05-06
CN107615716B (zh) 2020-07-03
CN107615716A (zh) 2018-01-19
JP2018519687A (ja) 2018-07-19
WO2016188375A1 (en) 2016-12-01
US11956207B2 (en) 2024-04-09
JP6670025B2 (ja) 2020-03-18
GB2555740A (en) 2018-05-09
US20230108856A1 (en) 2023-04-06
DE112016001657T5 (de) 2017-12-21
US10904206B2 (en) 2021-01-26
US20190356630A1 (en) 2019-11-21
US11546293B2 (en) 2023-01-03
GB2555740B (en) 2021-10-20

Similar Documents

Publication Publication Date Title
US11956207B2 (en) Multi-tenant aware dynamic host configuration protocol (DHCP) mechanism for cloud networking
US10320674B2 (en) Independent network interfaces for virtual network environments
US9628290B2 (en) Traffic migration acceleration for overlay virtual environments
US9374316B2 (en) Interoperability for distributed overlay virtual environment
US10972549B2 (en) Software-defined networking proxy gateway
US10038665B2 (en) Reducing broadcast flooding in a software defined network of a cloud
US11283649B2 (en) Multicast traffic across virtual networks (VNs)
US10917379B2 (en) Domain intercommunication in shared computing environments
US11177974B2 (en) Consistent provision of member node group information on virtual overlay network
US20150381385A1 (en) Packet encapsulation with redirected dma for software defined networks
US9559910B2 (en) Locating virtual machine(s) within virtual networks

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RONG, LIANG;TANG, GANG;TAO, ZI J.;AND OTHERS;REEL/FRAME:035699/0676

Effective date: 20150327

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

AS Assignment

Owner name: KYNDRYL, INC., NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:057885/0644

Effective date: 20210930