.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0

.. image:: ../etc/opnfv-logo.png
  :height: 40
  :width: 200
  :alt: OPNFV
  :align: left
.. these two pipes are to seperate the logo from the first title
|
|
MOVIE BOD usecase info
======================

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

BOD usecase image
-----------------
<<<<<<< HEAD
.. figure:: images/bod.png
    :name: bandwith-on-demand
    :width: 50%

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.

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
=======


BOD usecase description
----------------------

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


..
    Revision: 70db10647da026ac5617f1b585ab3013cc445e17
    Build date: 2016-07-22