Difference between revisions of "IETF 102 Hackathon"
From Yuma123 Wiki
Jump to navigationJump to search| Line 1: | Line 1: | ||
| + | ==Alternative southbound interface to flow enabled network bridges== |
||
| − | ==Objectives== |
||
| − | Below are the 3 main objectives. Updates will be published below. |
||
| − | ===Alternative southbound interface to flow enabled network bridges=== |
||
This is a new project originally defined in the following post on hackathon@ietf.org https://mailarchive.ietf.org/arch/msg/hackathon/vb27RmJivbwy8UURV_KXh2IzZd0 |
This is a new project originally defined in the following post on hackathon@ietf.org https://mailarchive.ietf.org/arch/msg/hackathon/vb27RmJivbwy8UURV_KXh2IzZd0 |
||
| Line 8: | Line 6: | ||
#Design and publish draft with YANG model of a flow enabled network bridge. |
#Design and publish draft with YANG model of a flow enabled network bridge. |
||
#Device (server) side model implementation - loadable module for some of the available opensource NETCONF servers implementing the model for a OpenFlow device as a proxy controller with a single node. |
#Device (server) side model implementation - loadable module for some of the available opensource NETCONF servers implementing the model for a OpenFlow device as a proxy controller with a single node. |
||
| − | #Controller (client) side plug-in implementation - |
+ | #Controller (client) side plug-in implementation - ncflowplugin for |
ODL interacting with NETCONF mounted nodes implementing the YANG model |
ODL interacting with NETCONF mounted nodes implementing the YANG model |
||
that ideally can coexist with openflowplugin. |
that ideally can coexist with openflowplugin. |
||
| − | + | ==Progress:== |
|
| + | ===Design and publish draft with YANG model of a flow enabled network bridge.=== |
||
| − | * Checked https://github.com/opencomputeproject/SAI for references. |
||
| + | Done - https://datatracker.ietf.org/doc/draft-vassilev-netmod-network-bridge/ |
||
| − | |||
| + | ===Device (server) side model implementation=== |
||
| + | Done - https://github.com/vlvassilev/yuma123/tree/master/example-modules/ietf-network-bridge |
||
| + | ===Controller (client) side plug-in implementation - ncflowplugin for ODL=== |
||
| + | Incomplete. |
||
====Walkthrough==== |
====Walkthrough==== |
||
Revision as of 17:48, 15 July 2018
Contents
- 1 Alternative southbound interface to flow enabled network bridges
- 2 Progress:
Alternative southbound interface to flow enabled network bridges
This is a new project originally defined in the following post on hackathon@ietf.org https://mailarchive.ietf.org/arch/msg/hackathon/vb27RmJivbwy8UURV_KXh2IzZd0
The project consists of 3 tasks:
- Design and publish draft with YANG model of a flow enabled network bridge.
- Device (server) side model implementation - loadable module for some of the available opensource NETCONF servers implementing the model for a OpenFlow device as a proxy controller with a single node.
- Controller (client) side plug-in implementation - ncflowplugin for
ODL interacting with NETCONF mounted nodes implementing the YANG model that ideally can coexist with openflowplugin.
Progress:
Design and publish draft with YANG model of a flow enabled network bridge.
Done - https://datatracker.ietf.org/doc/draft-vassilev-netmod-network-bridge/
Device (server) side model implementation
Done - https://github.com/vlvassilev/yuma123/tree/master/example-modules/ietf-network-bridge
Controller (client) side plug-in implementation - ncflowplugin for ODL
Incomplete.
Walkthrough
Mount the netconf device:
yangcli admin@localhost> merge /modules/module[name='netconfflow-0'][type='sal-netconf-connector'] -- address=localhost sal-netconf:port=830 tcp-only=false username=tester password=tester sal-netconf:event-executor/type=netty-event-executor sal-netconf:event-executor/name=global-event-executor sal-netconf:binding-registry/type=binding-broker-osgi-registry sal-netconf:binding-registry/name=binding-osgi-broker sal-netconf:dom-registry/type=dom-broker-osgi-registry sal-netconf:dom-registry/name=dom-broker sal-netconf:client-dispatcher/type=netconf-client-dispatcher sal-netconf:client-dispatcher/name=global-netconf-dispatcher sal-netconf:processing-executor/type=threadpool sal-netconf:processing-executor/name=global-netconf-processing-executor sal-netconf:keepalive-executor/type=scheduled-threadpool sal-netconf:keepalive-executor/name=global-netconf-ssh-scheduled-executor
