MOVIE usecase info Guide¶
Contents:
1. MOVIE VPC usecase info¶
1.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
1.2. VPC usecase image¶
<<<<<<< HEAD .. figure:: images/vpc.png
name: virtual-private-cloud width: 50%
1.3. VPC usecase description¶
Create a Virtual Private Cloud to process email traffic through firewall and spam filter before processing.
- Description
- Pull up Model Template with all VPC nodes Link Endnodes (access-node, email server) Properties flows: customer-email gothrough (router, firewall, DMZ, email-spam-filter, protected zone router)
- What Intent Processor creates
- Virtual router to link virtual Private Cloude (vPC) vPC structure, whic here consists of a firewall, DMZ, email-spam filer a protected zone, and several nework services (E.g. hosted email)
1.4. VPC usecase description¶
>>>>>>> 1a87f87... MOVIE-9 usecase documentation with ODL NEMO upstream
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.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.
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
3. MOVIE SFC usecase info¶
<<<<<<< HEAD
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
3.1. SFC usecase image¶
<<<<<<< HEAD .. figure:: images/sfc.png
name: service-function-chaining width: 50%
3.2. SFC usecase description¶
<<<<<<< HEAD Create Service Chaining Function path
Netwrok function in path: firewall, load balancer, WAN optimization between virtual private cloud and Internet.
- Description
- Link sf1 Endpoints (VPC, Internet) Properties flow1 inbound flow2 outbound Flow 1 match Internet-Traffic Policy ID1 Policy ID1 gothorugh (firewall, WoC)
- Intent Based Process
- Allocate VNFs linked to vRouter for firewall & WoC Set of Filters to vRouter for firewall & WoC Apply policies to steer flow to gothrough different service paths
>>>>>>> 1a87f87... MOVIE-9 usecase documentation with ODL NEMO upstream
