meetings:movie
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
meetings:movie [2016/03/02 06:14] Tianran Zhou [Meeting on October 14th, 2015] |
meetings:movie [2016/03/02 06:15] (current) Tianran Zhou [Meeting on March 2th, 2016] |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| **Minute:** | **Minute:** | ||
| + | |||
| 1. Release B status | 1. Release B status | ||
| + | |||
| We discussed the inability to deliver on Release B in parallel with Beryllium ODL release as NEMO code which is the modeling was not ready. | We discussed the inability to deliver on Release B in parallel with Beryllium ODL release as NEMO code which is the modeling was not ready. | ||
| + | |||
| 2. ODL NEMO Review | 2. ODL NEMO Review | ||
| + | |||
| We reviewed the CloudVPN (BGP VPN) use case that has been built for MWC Demo. | We reviewed the CloudVPN (BGP VPN) use case that has been built for MWC Demo. | ||
| + | |||
| In this demo 3-node, 1 Beijing, 1 Shanghai bank tenants access the Data Center node with two Applications A1 and A2 services, providing both http and video services. The chain1 is used by both site users which passed through Firewall and Load Balancer in that order. The traffic from Beijing is allowed both Http and Video traffic for priority 1 but for Shanghai site only http traffic is allowed based on priority 1. All priority 0 traffic are denied by Firewall. | In this demo 3-node, 1 Beijing, 1 Shanghai bank tenants access the Data Center node with two Applications A1 and A2 services, providing both http and video services. The chain1 is used by both site users which passed through Firewall and Load Balancer in that order. The traffic from Beijing is allowed both Http and Video traffic for priority 1 but for Shanghai site only http traffic is allowed based on priority 1. All priority 0 traffic are denied by Firewall. | ||
| + | |||
| Thus with Nemo language the MOVIE model can be implemented for the 3-node use case. | Thus with Nemo language the MOVIE model can be implemented for the 3-node use case. | ||
| + | |||
| 3. MOVIE and NEMO | 3. MOVIE and NEMO | ||
| + | |||
| It was decides to try NEMO OSGi bundle on ODL site that will be built in Santa Clara Lab to test and see if this can be done for one use case. | It was decides to try NEMO OSGi bundle on ODL site that will be built in Santa Clara Lab to test and see if this can be done for one use case. | ||
| + | |||
| This will be sued as part of Release-C depending on resource available. | This will be sued as part of Release-C depending on resource available. | ||
| + | |||
| 4. The MOVIE project will try complete the Release B documentation borrowing from ODL or linking to ODL for BOD and SFC use cases. | 4. The MOVIE project will try complete the Release B documentation borrowing from ODL or linking to ODL for BOD and SFC use cases. | ||
| + | |||
| 5. The use case demo of 2 will be called Cloud VPN and we will try add that to Release C of OPNFV. | 5. The use case demo of 2 will be called Cloud VPN and we will try add that to Release C of OPNFV. | ||
meetings/movie.1456899269.txt.gz ยท Last modified: 2016/03/02 06:14 by Tianran Zhou
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
