Welcome to Network Intent Composition

1 Welcome to Network Intent Composition
2 Introduction
- 2.1 NIC basics
  - 2.1.1 Config dev environment
  - 2.1.2 Tips
  - 2.1.3 Basic guide using Intents for QoS
  - 2.1.4 Basic guide to create Intents to ALLOW or BLOCK
- 2.2 List of available commands
- 2.3 How to install
- 2.4 List of commands
  - 2.4.1 intent:add
  - 2.4.2 intent:remove
  - 2.4.3 intent:show
  - 2.4.4 intent:list
  - 2.4.5 intent:compile (EXPERIMENTAL)
- 2.5 Compilation process demo
- 2.6 Project Information
3 Feel free to edit this section as necessary
4 Documentation
- 4.1 Proposed Community Goals for NIC project
  - 4.1.1 Documents
- 4.2 Weekly Meetings
  - 4.2.1 Schedule and Logistics
  - 4.2.2 Meeting Topics
  - 4.2.3 Past Meetings
5 Release Planning
6 Release Notes

Introduction

This Network Intent Composition project will enable the controller to manage and direct network services and network resources based on describing the “Intent” for network behaviors and network policies. Intents are described to the controller through a new NorthBound Interface, which provides generalized and abstracted policy semantics instead of specific configuration commands. The Intent based NBI allows for a descriptive way to get what is desired from the infrastructure, unlike the current SDN interfaces which are based on describing how to provide different services. This NBI will accommodate orchestration services and network and business oriented SDN applications. The Network Intent Composition function will use existing OpenDaylight Network Service Functions and Southbound Plugins to control both virtual and physical network devices. The Network Intent Composer will be designed to be protocol agnostic such that any control protocol can be used such as Openflow, OVSDB, I2RS, Netconf, BGP etc.

This project provides a structure capable to support different Intent definitions and work with multiple southbound plugins at the same time, also contains its own implementation for Intent Lifecycle Management.

NIC basics

Config dev environment

Tips

Debugging: ./karaf debug

It will listen to 5005 port

Basic guide using Intents for QoS

QoS attribute mapping

1. Create a basic topology using mininet

^{sudo mn --topo single --mac --controller=remote,ip=127.0.0.1,port=6633 --switch ovsk,protocols=OpenFlow13}

2. Run karaf distribution and install odl-nic-core-mdsal, odl-nic-console,