Decoupling scheme for hypervisor from SDN architecture
draft-gu-sdnrg-decoupling-scheme-hypervisor-sdn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rong Gu , Chen Li | ||
| Last updated | 2016-09-17 (Latest revision 2016-03-16) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Different hypervisors are used in SDN network in cloud datacenters, such as KVM, VMware ESXi and Xen. However, different hypervisors are not well supported by SDN network to some degrees. In order to solve the problems with hypervisor VMware ESXi and Xen, decoupling schemes for hypervisor from SDN architecture are presented. Through different decoupling schemes, we want to find a better way in order to get the overall view by the SDN network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)