SDN network management consideration
draft-gu-sdnrg-network-management-consideration-00
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Authors | Rong Gu , Chen Li | ||
| Last updated | 2016-06-27 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-gu-sdnrg-network-management-consideration-00
SDNRG R. Gu, Ed.
Internet-Draft C. Li
Intended status: Informational China Mobile
Expires: December 29, 2016 June 27, 2016
SDN network management consideration
draft-gu-sdnrg-network-management-consideration-00
Abstract
This draft introduces consideration about SDN network management
after the deployment of SDN and NFV in cloud datacenters.
Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 29, 2016.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Gu & Li Expires December 29, 2016 [Page 1]
Internet-Draft SDN network management consideration June 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Definition of terms . . . . . . . . . . . . . . . . . . . . . 3
4. SDN management usecases . . . . . . . . . . . . . . . . . . . 3
4.1. Network monitoring . . . . . . . . . . . . . . . . . . . 3
4.2. Network detection . . . . . . . . . . . . . . . . . . . . 4
4.3. Alarm and log . . . . . . . . . . . . . . . . . . . . . . 6
5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Normative References . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
In cloud datacenter deployment,virtualized infrastructure of virtual
machines and physcial infrastructure of bare-metal servers are both
deployed. Openstack K version, SDN controller, open virtual switch,
SDN ToR (top of rack) switch and SDN gateway are chosen.Openstack
manages computing, storage and the network by neutron, nova, ironic
module and so on.SDN controller receives the messages of network
operation and translates it into forwarding devices.Open virtual
switch, SDN ToR switch and SDN gateway are forwarding devices.
After the deployment, we have faced the problems in management of SDN
network with all these added devices.The management are devided into
three parts: network monitoring, network detection, and alarm and log
aiming at devices, services and tenants.Difficulties lie in that:
(1) There are two network layers including overlay and underlay
increasing the difficulty of troubleshooting.
(2) Devices such as open virtual swith, openstack and others are
software based.High reliability can be a problem.
(3) Logical network can be operated by tenants which increases risks.
(4) Openstack, controller, open virtual switch and SDN tor are new
devices added in the network which should be covered by manager as
long as large numbers of virtual machines.
(5) Operations can be at anytime and anywhere with the requirement of
real time management.
This draft presents several considerations in management of SDN
datacenters.
Gu & Li Expires December 29, 2016 [Page 2]
Internet-Draft SDN network management consideration June 2016
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. Definition of terms
EP: end point
NFV: network function virtualization
SDN: software defined network
SFC: service function chaining
ToR: top of rack
VM: virtual machine
VPC: virtual private cloud
VSW: virtual switch
4. SDN management usecases
4.1. Network monitoring
Network monitoring includes network devices, configurations, physical
topology and logical topology.Network monitoring should be based on
underlay and overlay network.Virtualized network elements correspond
to physical network devices.Virtual networks of vm correspond to vsw
with its interface as well as the ToR.Real-time monitoring is
required.Status of devices and topologies should be updated
automately.Performance of devices are monitored.
Tenants can get the information of their own logical network
including configuration, topology, and performance in order to own
network self-management.
Manager of network can get the information of network resources and
system resources.The network resources includes virtual network
resource such as subnetwork and traffic path and physical network
resources such as vxlan gateway, vsw, ToR and so on. System resource
includes controller, IT resources, devices of firewall and load
balancer.
Gu & Li Expires December 29, 2016 [Page 3]
Internet-Draft SDN network management consideration June 2016
------------------------------------------------------------
| ------------------ ---------------- |
| application | tenants mgnt | | manager mgnt | |
| ---------------+-- ----+----------- |
----------------------------+------|----------|-------------
| --------- |
---------+------------- | |
| openstack | | |
---------+------------- | |
| | |
---------------+--------------+--+-
| SDN controller |
---------------+-----------+-------
| | |
| | |
------------ | --------------
| | |
| +-----+----+ |
| | SDN ToR | |
------------ +-----+----+ ------+-----
| ------- | | | Physical |
| | OVS | | ------------ | devices |
| +-----+ | | | | |
| | | | |bare-metal| | NAT/ |
|--+- --+-| | Server | | FW/ |
||VM| |VM|| | | | LB/ |
|---- ----| | | | VPN |
------------ ------------ ------------
Figure 1: Network monitoring
4.2. Network detection
Network detection aims at trouble-shooting automatically and fault
prediction.In underlay network, traditional detection technology can
be adopted as usual.In SDN network, the overlay network should be
added in detection.Besides the device diagnosis and network diagnosis
should be taken action.With the collected data of packet-loss and
time delay as well as the logical and physical topology,we can
undergo the trouble-shooting and prediction.
For example, the vtep detection detects the time delay and packet-
loss through each two vtep in SDN network.The point where packet loss
comes out is detected again with two vteps.Thus the fault point can
be located.
Gu & Li Expires December 29, 2016 [Page 4]
Internet-Draft SDN network management consideration June 2016
- -----------------------------------------------------------
| Core switch |
-----+--------------------+-----------------------+--------
| ...(detection)... | |
| . . | |
-----+--.-- ---.-+----- |
| ToR . | | . ToR | |
-----+--.-- ---.-+----- |
| . . | |
| . .| |
------+-.--- --- .+------ ------+-----
| -----V- | | -V----- | | Physical |
| | vtep| | | | vtep| | | devices |
| +-----+ | | +-----+ | | |
| | | | | | | | | NAT/ |
|--+- --+-| |--+- --+-| | FW/ |
||VM| |VM|| ||VM| |VM|| | LB/ |
|---- ----| |---- ----| | VPN |
------------ ------------ ------------
Figure 2: vtep detection
The service detection varifies service such as VPC or service
function chain.Controller simulates the traffic about the virtual
private cloud of one tenants with virtual routers and virtual
bridges.With the collected information of traffic, tenants service
are detected.
Gu & Li Expires December 29, 2016 [Page 5]
Internet-Draft SDN network management consideration June 2016
----------------------------------------------------------
| Controller |
-----------------------------V----------------------------
| |
|traffic |information
|simulation |collection
------------V---------------------------------------------
| VPC -------------- |
| | vRouter1 | |
| --V.--------V- |
| . | | . (detection) |
| ......... | | ........... |
| . ----------- ----------- . |
| . | | . |
| ---V-+----- -----+-V--- |
| | vBridge1| | vBridge1| |
| -----+----- -----+----- |
-----------------/-\----------------------/-\------------
------ ------ ----- ---------
| | | |
----+--- ----+--- ---+---- ----+---
| EP1 | | EP2 | | EP3 | | EP4 |
-------- -------- -------- --------
Figure 3: service detection
4.3. Alarm and log
It's easy of design alarm and log in devices monitoring. While in
overlay networks related with tenants, alarm and log needs to be
taken overall consideration.
The contents of alarm and log are TBD.
5. Conclusion
SDN and NFV technology has been planned to be co-deployed in the
cloud datacenters in providing services such as VPC and VAS of
layer4-layer7.Through the resolution test, we have found out that key
problems on network architecture, virtualized platform, standard
interfaces, high availability, practice guidance and many others
exist.More tests, trails and standardization work need to be
conducted in preparing the large-scale commercial deployment of SDN
and NFV technology in cloud datacenters.
Gu & Li Expires December 29, 2016 [Page 6]
Internet-Draft SDN network management consideration June 2016
6. Security Considerations
None.
7. IANA Considerations
None.
8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, DOI 10.17487/RFC2234,
November 1997, <http://www.rfc-editor.org/info/rfc2234>.
Authors' Addresses
Rong Gu (editor)
China Mobile
32 Xuanwumen West Ave, Xicheng District
Beijing 100053
China
Email: gurong_cmcc@outlook.com
Chen Li
China Mobile
32 Xuanwumen West Ave, Xicheng District
Beijing 100053
China
Email: lichenyj@chinamobile.com
Gu & Li Expires December 29, 2016 [Page 7]