2. MOVIE BOD usecase info

2.1. MOVIE is using ODL NEMO Project

Since the first SDN controller we chose was ODL all codes for now are upstream in ODL. Pleas refer latest info on link https://wiki.opendaylight.org/view/NEMO:main Installation details: https://wiki.opendaylight.org/view/NEMO:Installation_Guide System Test details: https://wiki.opendaylight.org/view/NEMO:Beryllium:System_Test The code repo: https://git.opendaylight.org/gerrit/gitweb?p=nemo.git;a=shortlog;h=refs%2Fheads%2Fstable%2Fberyllium

2.2. BOD usecase image

<<<<<<< HEAD .. figure:: images/bod.png


2.3. BOD usecase description

Bandwith on Demand can be described for an Enterprise customer with head quarter (HQ) and a Branch office (branch) needing a virtual link between them. This can be varied based on time of day and here is the description.


Link Endnodes(branch,HQ) Properties Flow: Day 10G

Link Endpoint(branch, HQ) Properties Flow: Night 1G

Flow: Day match...time (8am,6pm)

Flow: Night match....time (6pm,8am)

What Intent processor sets up

Adjust Virtual Link Bandwidth on demand for link between branch and HQ.

Trigger by “conditions” met by time change

Condition: From 8am to 6pm Bandwidth: 10G

Condition : From 6pm to 8am Bandwidth: 1G =======

2.4. BOD usecase description

>>>>>>> 1a87f87... MOVIE-9 usecase documentation with ODL NEMO upstream