IETF 94 - NMRG 38 meeting Intent Based Network Modeling (IBNEMO) Bert Wijnen 1
Ga between APP and Network APP wants A connection between two sites APP doesn t want Configurations of each device between two sites A service flow with SLA Flow entries in each device Tunnel, ACL, PBR configurations of different devices A customer network service chain 2
NEMO language for intent based network modeling NEMO APP Object Model Behavior Model NEMO Engine Node Connection Flow Oeration SDN Controller 15 simle statement for hundreds of comlex APIs Network alication/user use NEMO Language to rogramming their service NEMO Language is an Intent oriented network DSL (domain secific language), which is a language style network oen interface. Oerator/End-user or 3rd arty can use it to rogram network resource and behavior in their service alications. NEMO Engine is a network middleware, which translate high level service intent to real network instruction base on MDA(Model Driven Architecture). NEMO is now an OenDaylight roject coming with Beryllium release. htts://wiki.oendaylight.org/view/nemo:main 3
Use case : Virtual Private Cloud Oerator rovide virtual rivate cloud service for enterrises. Need to allocate two zones in the VPC for security issue. DMZ rovide htt/email/video services for access from internet. Interior rovide comute and storage resources for existing enterrise site. Provide BoD caability on the WAN connection. E.g, increase bandwidth when cloud bursting or backu internet BoD DMZ Enterrise site WAN interior Virtual Private Cloud 4
Use case: End to End Carrier Network The enterrise outsources their CPE business to the service rovider. The Branch site alies chained services in the vcpe before accessing WAN. The enterrise requests BoD in WAN between the branch and the headquarter for different bandwidth requirements, e.g., day/work and night/backu. The NEMO rogrammed logic runs on the Suer controller and instruct domain controller to accomlish network service rovisioning and olicy alying. Suer controller Domain controller Acc Core Domain controller Branch vcpe WAN Headquarter FW Cache BoD 5
An Examle: Bandwidth on Demand (B2B) DOCSIS There is a virtual link between the branch and headquarter offices. o The bandwidth of the vlink can be adjusted on demand o The adjustment can be triggered by "conditions" meet, e.g. The bandwidth will be adjusted when the timing meets. NEMO Scrit: Node branch; Node HQ; Connection tunnel Tye P2P Endnodes branch, HQ; Branch WAN Headquarter Condition: from 8am to 6m, Bandwidth: 10G Condition: from 6m to 8am, Bandwidth: 1G Constraint day AlyTo tunnel Condition time>8am & time <6m Oeration set:bandwidth=10g; Constraint night AlyTo tunnel Condition(time>0am & time<8am) (time>6m & time<0am) Oeration set:bandwidth=1g; 6
NEMO Editor in Eclise Program a Eclise lug-in that highlights the keywords Integrate with the IBNEMO roject Parse the NEMO language and comose the NEMO rest API. Call rest client/lib to send the request. Reference: Hackathon imlementation result: htts://github.com/aaguti-work/nemo-ietf 7
What could be the role of intent-based networking in situation where the system's goal "emerges" from the agents interactions? IBNEMO can dynamically udate the network behaviour. So if IBNEMO a gets alert that change is needed, it can do so Tianran Zhou can demo (see him. Possibly also demo at Bits&Bytes) Question: should IBNEMO also monitor network? Should that be art of IBNEMO? Can it rely on other network monitoring tools that trigger IBNEMO activity? Are there researchers that want to exeriment with that? Do we have ideas on how to do this? 8
What we are looking for: do you have exerience in oerating a network? How would you imlement the use cases? Feedback on the NEMO language definition, roosals for enhancements the OenDaylight roject? Hel us debug the current OenDaylight NEMO Engine rogramming lugins for Eclise? Program the interface(s) to drive the OenDaylight imlementation Integrate them with the NEMO Editor You know Xtext? Hel us to imrove the NEMO Editor lugin 9
Thank You 10