Difference between revisions of "Project Proposals/DMM"

From fd.io
Jump to: navigation, search
(Scope)
(Description)
Line 20: Line 20:
 
== Description ==
 
== Description ==
 
<!-- Description of the work that will take place in this project -->
 
<!-- Description of the work that will take place in this project -->
This  project aims to provides an extendable framework following the “Dual mode, Multiple protocols & Multiple instances (DMM)” principle, i.e. it hosts different types of networking stack instances operating on different domain (kernel/user-space) or even with different protocol suits (TCP/IP, RDMA, or others)
+
DMM (Dual Mode, Multi-protocol, Multi-instance) is a concept to provide a transport agnostic framework for the applications where applications can
 +
* Work with both user and kernel mode network stack.
 +
* Use different network protocol stack based on their functional and performance requirement (QOS).
 +
* Work with multiple instance of transport protocol stack.
 +
* Engage or adopt new protocol stack dynamically.
 +
 
 +
[[File:Dmm-framework.JPG|center|600px]]
 +
 
 +
* Existing applications or new applications use Posix compatible and uniform socket API library (via system hijacking or LD_PRELOAD).
 +
* Neuro Resource Discovery learn the set of protocol policies to route the packet. It can be like controller continuously monitor the network state and can update the policy rules dynamically on need basis.
 +
* Local protocol policy orchestrator regularly sync with nRD.
 +
* Session layer of DMM (nSocket) lookup this protocol orchestrator for any new session request and manages the session mapping and other info’s.
 +
* Based on protocol lookup the corresponding protocol stack is chosen.
  
 
== Scope ==
 
== Scope ==

Revision as of 06:58, 9 January 2018


Name

Dual-Mode Multi-protocol Multi-instance (DMM)

Project Contact Name and Email

Wangyalei <wangyalei2@huawei.com>

Repository Name

DMM

Description

DMM (Dual Mode, Multi-protocol, Multi-instance) is a concept to provide a transport agnostic framework for the applications where applications can

  • Work with both user and kernel mode network stack.
  • Use different network protocol stack based on their functional and performance requirement (QOS).
  • Work with multiple instance of transport protocol stack.
  • Engage or adopt new protocol stack dynamically.
Dmm-framework.JPG
  • Existing applications or new applications use Posix compatible and uniform socket API library (via system hijacking or LD_PRELOAD).
  • Neuro Resource Discovery learn the set of protocol policies to route the packet. It can be like controller continuously monitor the network state and can update the policy rules dynamically on need basis.
  • Local protocol policy orchestrator regularly sync with nRD.
  • Session layer of DMM (nSocket) lookup this protocol orchestrator for any new session request and manages the session mapping and other info’s.
  • Based on protocol lookup the corresponding protocol stack is chosen.

Scope

  • DMM supports different protocols on both kernel and user space
  • With the DMM framework, system operators can plug-in dedicated types of networking stack instances according to performance and/or functional requirements from user applications

Initial Committers

Vendor Neutral

No current or expected issues with vendor neutrality

Meets Board Policy (including IPR, being within Board defined Scope etc)

Meets board policy as expressed in Technical Community Charter and IP Policy

Administrata

  • Request for Project proposal consideration
    • Email: (place link to email to TSC proposing project, this can be obtained from TSC Archives
    • Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on)