Date: Fri, 29 Mar 2024 00:06:43 +0000 (UTC) Message-ID: <556803684.7235.1711670803445@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7234_1574896900.1711670803444" ------=_Part_7234_1574896900.1711670803444 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Thursday, November 7, 2013
Attending:
Dan Schmiedt - willys@clemson.edu
Dale W. Carder - dwcarder@wisc.edukevin mayeshiro - kmayeshiro@ucdavis.edu=
span>
Kathy Benninger - benninger@psc=
.edu
Chris Small - chsmall@uw.=
edu
Deniz Gurkan - dgurkan@uh.=
edu
Rich Cropp - rac111@psu.ed=
u
Heidi Picher Dempsey hpd@bn.=
com
--
Agenda:
1) Agenda Bash
None.<=
br>2) Network management plane, control =
plane, data plane
Discus=
sion started on IRTF (Internet Research Task Force, focuses on research fra=
meworks). Discussions focused on how to 'manage this.' Now that=
SDN separates control and data plane, what about the management of this ne=
twork? Is this a separate from the control plane?
Deniz asked what thoughts were in this regard.&nb=
sp; What does management plane mean to you?
Dan: Command line interface: configure the devices
=
SNMP
Chris Smalls: think of a wireless network, where there is no real=
manageability of nodes.
Wirel=
ess networks - no CLI
Abstract=
ed by controllers
OpenStack mo=
del: generalized view with three elements: network, subnet, port
=
Grover: yes, but this is only one use ca=
se.Abstraction: application may n=
eed additional topology info?
=
Chris s: raw sockets has no =
place
Dan: pica8, no info from=
the switch - no manageability&nb=
sp;(in the traditional sense)
Automation is essential in abstra=
ction - wireless, RF, etc maybe possible no CLI
Heidi: multiple admin domains in GENI
Actual switch info is still important since imple=
mentations are not uniform yet
E.g.: HP switch capabilities, size of the forwarding table, Another e.g.: load balancer applicatio=
n's view of the switch may become important
PURE OpenFlow case: network management through ?Control plane: API for managementManagement plane: human interface?
Management plane: statistics?
Push simple config
Configuring app's=
?
For example: BGP as a northb=
ound app and may need to be configured by the management planeDale: programming experience is similar
Abstractions are not there yet t=
o manage effectively, more like taking responsibility for the actions
Dale: eg: we used to manage many AP=
s ... now, with centralized controllers, we only have a single management p=
oint. We no longer manage thousands of APs.
Similar to PC operating systems
Information gathering methods will change.Grover: layers of abstractions add the=
ability for a broader audience to do interesting things.
AL2S update: Forwarding is worki=
ng well on AL2S now.NDDI FlowViso=
r 1.4
I2 innovative apps progr=
am folks are doing demos now.
=
Working hard on a plan for virtualization. How to enable this in a pr=
oduction environment. Implementation plan for virtualization foirst d=
raft is now available.
Grover:=
this is a high priority but high risk item.
We will hopefully talk with Luke Fowler/ GRNoc team next cal=
l about FlowSpace Firewall, etc.