Abstract: A method and associated systems for a multi-tenant DNS mechanism. A multi-tenant computing environment hosts multiple private overlay networks, each of which comprises one tenant's domain. A multi-tenant DNS agent receives a DNS request to resolve a domain address located within the multi-tenant environment. The agent examines a special record within the request to determine whether the request requires resolving the domain address to an internal tenant-specific network identifier within a tenant's private network. The agent then forwards the request to a DNS server, notifying the server whether the requested address resolution is tenant-specific. If the request is not tenant-specific, the server performs a conventional DNS lookup. But if the request is tenant-specific, the DNS server instead performs a lookup into a tenant-specific local database that allows the domain address to be resolved to an internal address visible only within the multi-tenant computing environment.

Abstract: A method, computer system, and computer program product for selecting a next-hop component for a packet from a group in a service function chain (SFC) enabled domain. The method may include receiving a request for selecting a next-hop component for a packet from a group in an SFC-enabled domain. The method may include collecting a delay measurement for packets of each of the plurality of components from a measurement agent in the SFC-enabled domain. The method may include selecting at least one component from the plurality of components based on the delay measurement for packets of each of the plurality of components. The method may include returning an indicator indicating at least one component.

Abstract: A method, system, and computer program product for enabling communication between different overlay solutions. The method includes one or more processor obtaining an address resolution request from a first resource in a first domain for a second resource in a second domain. Both domains are in a shared computing environment and the second domain includes a control plane engine. The one or more processor obtains source information from the request, registers the information to the engine, and utilizes the request to query the engine to locate the second resource in the domain. The second resource matches the request. The processor receives a response from the engine identifying a first host and the first host is in the second domain and is the host of the second resource. The processor sends a notification request to the first host requesting that the first host reply to the request.

Abstract: A load-balancer instance is instantiated in a network virtualization edge (NVE) in a software defined network (SDN). A forwarding table in the NVE is modified to indicate that a next hop for a packet having a destination address of the load-balancer instance is to be resolved by the load-balancer instance. From a portion of the packet, and using the load-balancer instance, a value usable to select a singular next hop to a first real server in a pool of real servers managed by the load-balancer instance is determined. The packet is forwarded, using the modified forwarding table, the packet through an underlay of the SDN such that the packet tunnels from the NVE to a first NVE, the second NVE hosting the first real server.

Abstract: A method, computer system, and computer program product for selecting a next-hop component for a packet from a group in a service function chain (SFC) enabled domain. The method may include receiving a request for selecting a next-hop component for a packet from a group in an SFC-enabled domain. The method may include collecting a delay measurement for packets of each of the plurality of components from a measurement agent in the SFC-enabled domain. The method may include selecting at least one component from the plurality of components based on the delay measurement for packets of each of the plurality of components. The method may include returning an indicator indicating at least one component.

Abstract: In one embodiment, a system includes a processing circuit and logic integrated with and/or executable by the processing circuit that causes the processing circuit to receive a congestion notification message from a first virtual switch of a first server indicating that a first virtual machine (VM) hosted by the first server is overloaded. The logic also causes the processing circuit to advertise a congestion status of the first VM in a congestion status message to one or more virtual switches in a network in response to receiving the congestion notification message. Moreover, the logic causes the processing circuit to cause all virtual switches in the network except for the first virtual switch to stop sending traffic destined for the first VM while the first VM is overloaded without restricting sending traffic that is destined for other VMs hosted by the first server.

Abstract: A method and system for virtual networking is provided. The method includes receiving logical service chain data describing a source virtual network ID (VNID) for a source virtual network, a destination VNID for a destination virtual network, and a group of intermediate waypoints. The logical service chain data defines a logical service chain. A set of networked virtual environments (NVE) is selected to support the group of intermediate waypoints and the logical service chain is deployed and mapped to a physical service chain implemented on the set of NVEs. The logical service chain data is transmitted to a network virtual authority (NVA) and a packet forwarding mechanism is introduced when a packet is received from an overlay port or an underlay port. An associated IP address is requested and the first packet is analyzed.

Abstract: Methods, computer program products, and systems are presented. The methods include, for instance: obtaining, by one or more processor, metadata of at least one packet of a network stream; and determining, by the one or more processor, a shortcut rule for the network stream to bypass at least one waypoint network, the shortcut rule being determined using the metadata of the at least one packet of the network stream. In one embodiment, the obtaining includes obtaining the metadata from the at least one waypoint network. In another embodiment, the obtaining comprises obtaining the metadata from multiple packets of the network stream, and the determining comprises using the metadata of the multiple packets of the network stream to determine the shortcut rule. In a further embodiment, the determining includes analyzing a header of the at least one packet of the network stream.

Abstract: A method, system, and computer program product for enabling communication between different overlay solutions. The method includes one or more processor obtaining an address resolution request from a first resource in a first domain for a second resource in a second domain. Both domains are in a shared computing environment and the second domain includes a control plane engine. The one or more processor obtains source information from the request, registers the information to the engine, and utilizes the request to query the engine to locate the second resource in the domain. The second resource matches the request. The processor receives a response from the engine identifying a first host and the first host is in the second domain and is the host of the second resource. The processor sends a notification request to the first host requesting that the first host reply to the request.

Abstract: A method, system, and computer program product for enabling communication between different overlay solutions. The method includes one or more processor obtaining an address resolution request from a first resource in a first domain for a second resource in a second domain. Both domains are in a shared computing environment and the second domain includes a control plane engine. The one or more processor obtains source information from the request, registers the information to the engine, and utilizes the request to query the engine to locate the second resource in the domain. The second resource matches the request. The processor receives a response from the engine identifying a first host and the first host is in the second domain and is the host of the second resource. The processor sends a notification request to the first host requesting that the first host reply to the request.

Abstract: A method and associated systems for a multi-tenant DNS mechanism. A multi-tenant computing environment hosts multiple private overlay networks, each of which comprises one tenant's domain. A multi-tenant DNS agent receives a DNS request to resolve a domain address located within the multi-tenant environment. The agent examines a special record within the request to determine whether the request requires resolving the domain address to an internal tenant-specific network identifier within a tenant's private network. The agent then forwards the request to a DNS server, notifying the server whether the requested address resolution is tenant-specific. If the request is not tenant-specific, the server performs a conventional DNS lookup. But if the request is tenant-specific, the DNS server instead performs a lookup into a tenant-specific local database that allows the domain address to be resolved to an internal address visible only within the multi-tenant computing environment.

Abstract: A method and associated systems for a multi-tenant DNS mechanism. A multi-tenant computing environment hosts multiple private overlay networks, each of which comprises one tenant's domain. A multi-tenant DNS agent receives a DNS request to resolve a domain address located within the multi-tenant environment. The agent examines a special record within the request to determine whether the request requires resolving the domain address to an internal tenant-specific network identifier within a tenant's private network. The agent then forwards the request to a DNS server, notifying the server whether the requested address resolution is tenant-specific. If the request is not tenant-specific, the server performs a conventional DNS lookup. But if the request is tenant-specific, the DNS server instead performs a lookup into a tenant-specific local database that allows the domain address to be resolved to an internal address visible only within the multi-tenant computing environment.

Abstract: An approach is provided in which an information handling system establishes a resource reservation protocol (RSVP) session corresponding to a flow between a first entity and a second entity operating within a computer environment that implements a network virtualization overlay protocol. Once the RSVP session is established, the information handling system encapsulates data packets of the flow based on the network virtualization overlay protocol and, in turn, sends the encapsulated data packet over the computer network with a quality of service (QoS) assurance level that is based on the established RSVP session.

Abstract: A load-balancer instance is instantiated in a network virtualization edge (NVE) in a software defined network (SDN). A forwarding table in the NVE is modified to indicate that a next hop for a packet having a destination address of the load-balancer instance is to be resolved by the load-balancer instance. From a portion of the packet, and using the load-balancer instance, a value usable to select a singular next hop to a first real server in a pool of real servers managed by the load-balancer instance is determined. The packet is forwarded, using the modified forwarding table, the packet through an underlay of the SDN such that the packet tunnels from the NVE to a first NVE, the second NVE hosting the first real server.

Abstract: A load-balancer instance is instantiated in a network virtualization edge (NVE) in a software defined network (SDN). A forwarding table in the NVE is modified to indicate that a next hop for a packet having a destination address of the load-balancer instance is to be resolved by the load-balancer instance. From a portion of the packet, and using the load-balancer instance, a value usable to select a singular next hop to a first real server in a pool of real servers managed by the load-balancer instance is determined. The packet is forwarded, using the modified forwarding table, the packet through an underlay of the SDN such that the packet tunnels from the NVE to a first NVE, the second NVE hosting the first real server.

Abstract: A mechanism for multicast (M-VIM) is used to resolve address looking up problems for different types of VXLAN related overlay networks for multicast and broadcast traffics. A Multicast Overlay Ferry Proxy (MOFP) is introduced between a VXLAN domain and the CNI domain for ferrying control plane and data panel information. The M-VIM mechanism comprises three parts: a VXLAN Module; a CNI Module; and a proxy mechanism.

Abstract: A method, system, and computer program product for enabling communication between different overlay solutions. The method includes one or more processor obtaining an address resolution request from a first resource in a first domain for a second resource in a second domain. Both domains are in a shared computing environment and the second domain includes a control plane engine. The one or more processor obtains source information from the request, registers the information to the engine, and utilizes the request to query the engine to locate the second resource in the domain. The second resource matches the request. The processor receives a response from the engine identifying a first host and the first host is in the second domain and is the host of the second resource. The processor sends a notification request to the first host requesting that the first host reply to the request.

Abstract: A method, system, and computer program product for enabling communication between different overlay solutions. The method includes one or more processor obtaining an address resolution request from a first resource in a first domain for a second resource in a second domain. Both domains are in a shared computing environment and the second domain includes a control plane engine. The one or more processor obtains source information from the request, registers the information to the engine, and utilizes the request to query the engine to locate the second resource in the domain. The second resource matches the request. The processor receives a response from the engine identifying a first host and the first host is in the second domain and is the host of the second resource. The processor sends a notification request to the first host requesting that the first host reply to the request.

Abstract: A method and system for virtual networking is provided. The method includes receiving logical service chain data describing a source virtual network ID (VNID) for a source virtual network, a destination VNID for a destination virtual network, and a group of intermediate waypoints. The logical service chain data defines a logical service chain. A set of networked virtual environments (NVE) is selected to support the group of intermediate waypoints and the logical service chain is deployed and mapped to a physical service chain implemented on the set of NVEs. The logical service chain data is transmitted to a network virtual authority (NVA) and a packet forwarding mechanism is introduced when a packet is received from an overlay port or an underlay port. An associated IP address is requested and the first packet is analyzed.

Abstract: In one embodiment, a system includes a processing circuit and logic integrated with and/or executable by the processing circuit that causes the processing circuit to receive a congestion notification message from a first virtual switch of a first server indicating that a first virtual machine (VM) hosted by the first server is overloaded. The logic also causes the processing circuit to advertise a congestion status of the first VM in a congestion status message to one or more virtual switches in a network in response to receiving the congestion notification message. Moreover, the logic causes the processing circuit to cause all virtual switches in the network except for the first virtual switch to stop sending traffic destined for the first VM while the first VM is overloaded without restricting sending traffic that is destined for other VMs hosted by the first server.