This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
meetings:movie [2015/09/21 09:56] Tianran Zhou [Logistics] |
meetings:movie [2016/03/02 06:15] (current) Tianran Zhou [Meeting on March 2th, 2016] |
||
---|---|---|---|
Line 4: | Line 4: | ||
When: | When: | ||
- | ***Wednesday 01:00-02:00 AM UTC** | + | ***Wednesday 03:00-04:00 AM UTC** |
- | * [[http://www.timeanddate.com/worldclock/fixedtime.html?hour=1&min=0&sec=0|Your Local Time]] (Tuesday 18:00 US Pacific Time) | + | * [[http://www.timeanddate.com/worldclock/fixedtime.html?hour=1&min=0&sec=0|Your Local Time]] (Tuesday 19:00 US Pacific Time) |
To join the meeting: | To join the meeting: | ||
***Web Conferencing**: ''https://global.gotomeeting.com/join/900108805'' | ***Web Conferencing**: ''https://global.gotomeeting.com/join/900108805'' | ||
Line 14: | Line 14: | ||
* [[http://webchat.freenode.net/?channels=opnfv-meeting|Web Chat]]; or | * [[http://webchat.freenode.net/?channels=opnfv-meeting|Web Chat]]; or | ||
* [[https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23opnfv-meeting|IRC Cloud]] | * [[https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23opnfv-meeting|IRC Cloud]] | ||
+ | |||
+ | ==== Meeting on March 2th, 2016 ==== | ||
+ | |||
+ | **Agenda:** | ||
+ | |||
+ | - Release B status | ||
+ | - ODL NEMO Review | ||
+ | - MOVIE and NEMO | ||
+ | - NEMO demo on MWC2016 | ||
+ | |||
+ | **Minute:** | ||
+ | |||
+ | 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. | ||
+ | |||
+ | 2. ODL NEMO Review | ||
+ | |||
+ | 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. | ||
+ | |||
+ | Thus with Nemo language the MOVIE model can be implemented for the 3-node use case. | ||
+ | |||
+ | 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. | ||
+ | |||
+ | 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. | ||
+ | |||
+ | 5. The use case demo of 2 will be called Cloud VPN and we will try add that to Release C of OPNFV. | ||
+ | |||
+ | |||
+ | ==== Meeting on October 14th, 2015 ==== | ||
+ | |||
+ | [[http://www.timeanddate.com/worldclock/fixedtime.html?msg=OPNFV-movie&iso=20151014T01&ah=1|Your local time]] | ||
+ | |||
+ | **Agenda:** | ||
+ | |||
+ | - Roll call | ||
+ | - Discussion on the Jira tickets. | ||
+ | - Discussion on the policy integration with RS team. | ||
+ | - AOB | ||
+ | |||
+ | JIRA reference: | ||
+ | |||
+ | [[https://jira.opnfv.org/browse/MOVIE-9?jql=project%20%3D%20MOVIE]] | ||
+ | |||
+ | **Minute:** | ||
+ | |||
+ | ==== Meeting on September 23th, 2015 ==== | ||
+ | |||
+ | [[http://www.timeanddate.com/worldclock/fixedtime.html?msg=OPNFV-movie&iso=20150923T01&ah=1|Your local time]] | ||
+ | |||
+ | **Agenda:** | ||
+ | |||
+ | - Roll call | ||
+ | - Prakash will lead the discussion on the IFA 005 contribution. | ||
+ | - Discussion on the policy integration with RS team. | ||
+ | - AOB | ||
+ | |||
+ | JIRA reference: | ||
+ | |||
+ | [[https://jira.opnfv.org/browse/MOVIE-4]] | ||
+ | |||
+ | [[https://jira.opnfv.org/browse/MOVIE-5]] | ||
+ | |||
+ | **Minute:** | ||
+ | |||
+ | We talked about the NEMO intent project in ODL, and the proposed language. We found NEMO language is a new style for intent NBI. And very easy to use just like talking with the controller. | ||
+ | |||
+ | 1. Reviewed NFV IFA005 Interfaces and actions supported and we will need to MAP Intents to these APIs and compare with OpenStack to see if we are missing any attributes or actions. For we will try map use cases and Intents to conclude drawing use case flows for BOD, VN and SFC. This will take about 4-5 weeks. | ||
+ | |||
+ | 2. How is NEMO different from other languages like Frenetic. | ||
+ | * http://www.cs.cornell.edu/~jnfoster/papers/frenetic-icfp.pdf | ||
+ | * The difference is that NEMO can import any VNF and switch them , chain them together, so NEMO is more focused on Integrating. NEMO is more alike to SQL or a variant of that. | ||
+ | |||
+ | 3. How does it compare with Data-log? | ||
+ | * Its domain independent where as the NEMO is based on Domains like Network, Compute & Storage. Data-log cannot describe the use cases like BOD, NV, SFC etc. | ||
+ | |||
+ | 4. Likely dates for NEMO release with ODL is 12/17/2015 which we can target for one or more use cases as we decide, and ONOS will need more need investigation. This will be ODL release date for compass to take it further into Brahmaputra OPNFV release. | ||
+ | |||
+ | 5. Review Akanda's rug (https://github.com/stackforge/akanda-rug) on stackforge for Service VM to apply MOVIE use cases. | ||
+ | |||
+ | 6. Discussion about the MOVIE API Specification -Based on support for Intent based on NEMO API in ODL we need to compare the same with ONOS / XoS. | ||
+ | |||
+ | https://wiki.opendaylight.org/view/NEMO:Main | ||
+ | |||
+ | http://d3s9ug42bq7kbi.cloudfront.net/webinars/onos-dec/ONOS-NorthBound.pdf | ||
+ | |||
+ | * Intent Expression & Compilation | ||
+ | * Looks like BOD is still at Network level service and we may have to look at other uses cases to see if they are service level intent. So the BOD scenario is provision based for customer like cost or QoS we can condition it as intent. | ||
+ | |||
+ | ---------------------------- | ||
==== Meeting on September 16th, 2015 ==== | ==== Meeting on September 16th, 2015 ==== | ||
Line 33: | Line 129: | ||
**Minute:** | **Minute:** | ||
+ | |||
+ | MOVIE had a meeting earlier and decided to provie the 3 use cases of BOD, VN and SFC each with API at two weeks intervals. Also there was discussions to separate Service Abstraction , Service Policy and Intent and call it "Intent Based Policy". The debate was on how it's different from GBP. There was dicussion on Info Model as how Object Node is actually Nodes (type can be host, layer 2 group, layer 3 group, service function pool etc.) and Connection can contain flow. This is to compare how GBP can be built from IBP objects. Plus noted that Flow is contained in Connection objetcs.The native modeling was agreed will be based on Yand Model for both Instances and operations where Action is mandatory, constraints and conditions are optional. | ||
+ | The Jira Movie-2 was API creation with there use cases was estaimted toal of 6-weeks so at to complete API work by November 30th. However OPNFV APIs will be implemented by Dec 30th, 2015 for it to be ready in time for OPNFV B Release. The biggest concern was dependence on Liberty completions and start of Miataka November beginning to align with Mitaka M1. | ||
+ | |||
+ | ---------------------------- | ||
==== Meeting on August 5th, 2015 ==== | ==== Meeting on August 5th, 2015 ==== | ||
Line 63: | Line 164: | ||
- Hopefully that MOVIE could use this tool in the generic VIM NBI layer. | - Hopefully that MOVIE could use this tool in the generic VIM NBI layer. | ||
- Will send more questions to Peter offline. | - Will send more questions to Peter offline. | ||
+ | |||
+ | ---------------------------- | ||
+ | |||
==== Meeting on July 8th, 2015 ==== | ==== Meeting on July 8th, 2015 ==== | ||
Line 80: | Line 184: | ||
- The intent based network modeling (IBNEMO) bar bof on IETF is going to happen on monday and thursday to meeting time slot of various people. Sue also introduced the agenda and the initial presentation. | - The intent based network modeling (IBNEMO) bar bof on IETF is going to happen on monday and thursday to meeting time slot of various people. Sue also introduced the agenda and the initial presentation. | ||
- Kevin presented the new project. We have a good discussion and conclude that this kind of NBI is technique specific for metro ethernet. The movie project will provide a higher level abstraction and will provide a generic NBI platform so that many technique specific interfaces can be plugged in as well as their corresponding adaptions. | - Kevin presented the new project. We have a good discussion and conclude that this kind of NBI is technique specific for metro ethernet. The movie project will provide a higher level abstraction and will provide a generic NBI platform so that many technique specific interfaces can be plugged in as well as their corresponding adaptions. | ||
+ | |||
+ | ---------------------------- | ||
==== Meeting on June 10th, 2015 ==== | ==== Meeting on June 10th, 2015 ==== | ||
Line 112: | Line 218: | ||
Based on the feedback Sue Hares received, for our next meeting. she will write-up the uses cases and indicate what problems these show. Movie members suggested these cases case be presented in write-up and in power-point. In another document, she will summarize and expand on the problems these use cases show. | Based on the feedback Sue Hares received, for our next meeting. she will write-up the uses cases and indicate what problems these show. Movie members suggested these cases case be presented in write-up and in power-point. In another document, she will summarize and expand on the problems these use cases show. | ||
+ | |||
+ | ---------------------------- | ||
==== Meeting on May 13th, 2015 ==== | ==== Meeting on May 13th, 2015 ==== | ||
Line 128: | Line 236: | ||
* {{:meetings:congress_blueprint.pptx|}} | * {{:meetings:congress_blueprint.pptx|}} | ||
* As we have discussed the gap of congress, this contribution might be part of the movie project. | * As we have discussed the gap of congress, this contribution might be part of the movie project. | ||
+ | |||
+ | ---------------------------- | ||
+ | |||
==== Meeting on April 30th, 2015 ==== | ==== Meeting on April 30th, 2015 ==== | ||
Line 151: | Line 262: | ||
* It's not written in python, so it's hard to contribute to OpenStack. | * It's not written in python, so it's hard to contribute to OpenStack. | ||
- Adjourned | - Adjourned | ||
+ | |||
+ | ---------------------------- | ||
+ | |||
==== Meeting on April 22th, 2015 ==== | ==== Meeting on April 22th, 2015 ==== | ||