SDN network management consideration
draft-gu-sdnrg-network-management-consideration-01
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 , Yan Zhuang | ||
| Last updated | 2016-06-28 | ||
| 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-01
SDNRG R. Gu, Ed.
Internet-Draft C. Li
Intended status: Informational China Mobile
Expires: December 30, 2016 Y. Zhuang
Huawei
June 28, 2016
SDN network management consideration
draft-gu-sdnrg-network-management-consideration-01
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 30, 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, et al. Expires December 30, 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. Overlaps of management between tenants and network
administrator . . . . . . . . . . . . . . . . . . . . . . 6
4.4. Alarm and log of new SDN devices and network . . . . . . 6
4.5. High availability of software-based devices and networks 7
5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 7
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 in the network. Openstack K version, SDN controller, open
virtual switch, SDN ToR (top of rack) switches and SDN gateways are
used.In this cloud-based deployment, Openstack manages computing,
storage and network of the entire network system by its modules
including neutron, nova, ironic, swift and so on.SDN controller is
responsible for the network provision and management. It receives
messages of network operations from applications or Openstack neutron
and translates them into commands/operations for forwarding
devices.Open virtual switch, SDN ToR switch and SDN gateway are
forwarding devices in this senario.
With this deployment, we now face some problems in managing such SDN
network with all these added heterogeneous devices.The management can
be devided into several parts: network monitoring, network detection,
and alarm and log for devices, services and tenants.
Difficulties lie in that:
(1) Two network layers including overlay and underlay increases the
difficulty in troubleshooting.
(2) Software-based devices such as open virtual swith, openstack and
others face the problem of high availability as well as the link
availability.
Gu, et al. Expires December 30, 2016 [Page 2]
Internet-Draft SDN network management consideration June 2016
(3) Logical network can be operated by tenants. Thus there are
overlaps between the management of tenants and network administrator
(4) Openstack server, controller, open virtual switch and SDN tor are
new devices which should be covered by network manager system as well
as large numbers of virtual machines.
(5) Operations can be at anytime and anywhere with the requirement of
real-time requirement.
This draft presents several use cases in management of SDN
datacenters.
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
ovs: open virtual switch
4. SDN management usecases
4.1. Network monitoring
Network monitoring includes monitoring configurations of network
devices, 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
VMs 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 also monitored.
Gu, et al. Expires December 30, 2016 [Page 3]
Internet-Draft SDN network management consideration June 2016
Tenants can get the information of their own logical network
including configuration, topology, and performance in order to own
network self-management.
Network administrator can get the information of network resources
and system resources.The network resources includes virtual network
resources such as subnet and traffic path and physical network
resources such as vxlan gateway, ovs, ToR and so on. System resource
includes controller, IT resources, devices of firewall and load
balancer.
------------------------------------------------------------
| ------------------ ---------------- |
| 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 technologies
can be used as usual.In SDN network, detection should also be
provided in the overlay network.With the collected information of
Gu, et al. Expires December 30, 2016 [Page 4]
Internet-Draft SDN network management consideration June 2016
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 can detect the time delay and packet-
loss between each two vteps in a SDN network. The point where packet
lost should be detected again with two vteps.Thus the fault point can
be found.
- -----------------------------------------------------------
| 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 verifies the service availability such as VPC
or service function chain. Controller simulates the traffic of the
virtual private cloud of one tenant with virtual routers and virtual
bridges. With the collected information of traffic, the availability
of tenants' service are detected.
Gu, et al. Expires December 30, 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. Overlaps of management between tenants and network administrator
Tenants can manage their own network by network configuration in VPC.
Performance of tenants' VPC can be observed by tenants themself.
Network administrator can not only get the information of each
tenant, but also has the overall view. As a result, there are
overlaps between tenants and network administrator.
The contents of difference and relationship between tenants
management and network administrator management are TBD.
4.4. Alarm and log of new SDN devices and network
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.
Gu, et al. Expires December 30, 2016 [Page 6]
Internet-Draft SDN network management consideration June 2016
4.5. High availability of software-based devices and networks
As openstack server, ovs and VMs are brought in,availability should
be considered. Besides, availability of virtual and physical link
should be covered.
The contents of availability of devices and networks are TBD.
5. Conclusion
In SDN network deployment,new challenages are brought in such as two
layers of networks, SDN devices, large scales of virtual machines,
real-time management requirements,and so on.Under these challenages,
SDN network management should be considered throughly..
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
Gu, et al. Expires December 30, 2016 [Page 7]
Internet-Draft SDN network management consideration June 2016
Chen Li
China Mobile
32 Xuanwumen West Ave, Xicheng District
Beijing 100053
China
Email: lichenyj@chinamobile.com
Yan Zhuang
Huawei
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Email: zhuangyan.zhuang@huawei.com
Gu, et al. Expires December 30, 2016 [Page 8]