Geneve: Generic Network Virtualization Encapsulation

Earlier this year, VMware, Microsoft, Red Hat and Intel published an IETF draft on Generic Network Virtualization Encapsulation (Geneve). This draft (first published on Valentine’s Day no less) includes authors from the each of the first generation encapsulation protocols — VXLAN, NVGRE, and STT. However, beyond the obvious appeal of unification across hypervisor platforms, the salient feature of Geneve is that it was designed from the ground up to be flexible. Nobody wants an endless cycle of new encapsulation formats as network virtualization designs and controllers mature, certainly not the vendors that have to support the ever growing list of acronyms and RFCs.

Of course press releases, standards bodies and predictions about the future mean little without actual implementations, which is why it is important to consider the “ecosystem” from the beginning of the process. This includes software and silicon implementations in both commercial and open source varieties. This always takes time but since Geneve was designed to accommodate a wide variety of use cases it has seen a relatively quick uptake. Unsurprisingly, the first implementations that landed were open source software — including switches such as Open vSwitch and networking troubleshooting tools like Wireshark. Today the first hardware implementation has arrived, in the form of the 40 Gbps Intel XL710 NIC, previously known as Fortville.

Why is hardware support important? Performance. Everyone likes flexibility, of course, but most of the time that comes with a cost. In the case of a NIC, hardware acceleration enables us to have our cake and eat it too by offloading expensive operations while retaining software control in the CPU. These NICs add encapsulation awareness for classic operations like checksum and TCP segmentation offload to bring Geneve tunnels to performance parity with traditional traffic. For good measure, they also add in support for a few additional Geneve-specific features as well.

Of course, this is just the beginning — it is still only six months after publication of the Geneve specification and much more is still to come. Expect to see further announcements coming soon for both NIC and switch silicon and of course new software to take advantage of the advanced capabilities. Until then, a discussion session as well as a live demo will be at Intel Developer Forum this week to provide a first glimpse of Geneve in action.

转自http://networkheresy.com/2014/09/08/geneve-ecosystem-support-has-arrived/

时间: 2024-08-29 04:38:03

Geneve: Generic Network Virtualization Encapsulation的相关文章

Is VXLAN the Answer to the Network Virtualization Question?

Network virtualization is a growing topic of interest and for some good reasons as networks scale to meet the challenges of cloud computing they are running up against VLAN scaling limitations. There have been several network overlay technologies rel

Connecting Docker for Cloud Services using SDN and Network Virtualization

 Abstract The explosive scale of container CPUs needs highly efficient network virtualization Challenge The number of container-based CPUs will be 10-100 multiples up over that of hypervisor-based virtual machines; cloud networking needs upgrade to

网络虚拟化基础协议之Geneve

网络虚拟化最基础的技术莫过于分层(Overlay.Underlay),要实现分层有两种手段,一个是映射(Mapping),一个是封装(Encapsulation). 映射,主要思路是转发时替换报文语义,如何替换将需要设备进行查询. 封装,则是把需要的报文语义添加到网包中,处理的时候一层层的解封装即可,尽量对设备透明. 不少协议都实现了封装的部分或完整功能,包括IP-in-IP.Vlan.MPLS.VXLAN.NVGRE.STT等.这些协议各有各的特点,不少都是为了简单地隔离或者通过隧道连通不同网

Network Function Virtualization for a Network Device

An apparatus for performing network function virtualization (NFV), comprising: a memory, a processor coupled to the memory, wherein the memory includes instructions that when executed by the processor cause the apparatus to perform the following: rec

微软职位内部推荐-SW Engineer II for Azure Network

微软近期Open的职位: Software Engineer II The world is moving to cloud computing. Microsoft is betting Windows Azure as our cloud computing platform. Important steps have already been taken to virtualize storage and computing through software, increasing agi

Chapel 2.Network interfaces

Note: Copy from TCP/IP Tutorial and Technical Overview (IBM Redbook GG24-3376-07)[000] 2.1 Ethernet and IEEE 802 local area networks (LANs) 2.1.1 Gigabit Ethernet 2.2 Fiber Distributed Data Interface (FDDI) 2.3 Serial Line IP (SLIP) 2.4 Point-to-Poin

[转]Network flow monitoring with Open vSwitch

With network virtualization, the software switches (such as Open vSwitch) on the servers act like the edge switches. So, to gain insights into the network flow behavior, it becomes important to have some sort of flow monitoring technique to analyze t

[转]数据中心网络虚拟化 隧道技术

http://www.sdnlab.com/12077.html SDNLAB 如何实现不同租户和应用间的地址空间和数据流量的隔离是实现数据中心网络虚拟化首先需要解决的几个问题之一.所谓地址空间的隔离是指不同租户和应用之间的网络(ip)地址之间不会产生相互干扰.换句话说,两个租户完全可以使用相同的网络地址.所谓数据流量的隔离是指任何一个租户和应用都不会感知或捕获到其他虚拟网络内部的流量.为了实现上述目的,我们可以在物理网络上面为租户构建各自的覆盖(overlay)网络,而隧道封装技术则是实现覆盖

Windows Server 2012 虚拟化实战:网络(一)

虚拟化对于计算的抽象,大家可能相对熟悉,也许都有在单机使用诸如Virtual PC或者Virtual Box的经验.使用的这些虚拟化软件的第一印象就是我们的CPU可以同时运行多套不同的操作系统,并且其上应用程序并行不悖.计算的抽象使得同一套硬件设备上的操作系统之间得以相互隔离,犹如一个身体拥有两个甚至更多灵魂,这是什么鬼?那么接下来很自然的一件事就是,这些灵魂之间该如何沟通呢?依然只有一个身体,如何相互握手和交流,如何对外联系和提供服务.因而对于虚拟化而言,最重要的基础设施除了存储外,再就是网络