This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
meetings:enfv [2015/11/25 16:28] Kevin Luehrs [November 25, 2015] |
meetings:enfv [2016/01/05 16:08] (current) Andrew Sergeev added 10-Dec-2015 minutes |
||
---|---|---|---|
Line 18: | Line 18: | ||
=====Meeting Agendas and Minutes===== | =====Meeting Agendas and Minutes===== | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ====December 10, 2015==== | ||
+ | |||
+ | ===Attendes: James, Michael, Jesse, Taiyun=== | ||
+ | |||
+ | ===Minutes=== | ||
+ | __Item 1: Scope of Group__ \\ | ||
+ | MK: In tunneling section, broaden the question to allow for segment routing \\ | ||
+ | MK: In Monitoring … propose we use Assurance as a slightly broader term \\ | ||
+ | MK: Noted that MANO is now in scope for OPNFV \\ | ||
+ | MK: Propose that “edge” gets defined a little more explicitely (E.g. Home, business service and mobile) \\ | ||
+ | MK: Should add an item listing out the gaps/challenges associated with pushing the NFV location from the | ||
+ | “ISP POP” (or similar) to the true network edge (e.g. Scaling, security … ) \\ | ||
+ | Taiyun: Ensure that a distributed base station use case is in scope. (Agreed!) \\ | ||
+ | JH: Worried about too many use cases, propose focusing on Mobile and Enterprise \\ | ||
+ | JB: Let’s start with three and include Residential \\ | ||
+ | JH: Would we cover MANO? \\ | ||
+ | All: Agreed that we would identify the needs we place on MANO from eNFV, but we wouldn’t spec MANO itself. \\ | ||
+ | MK: Will publish a link to the ETSI MANO definition document (with crib notes!) \\ | ||
+ | JH: Wondering if MPLS is out of scope. \\ | ||
+ | All: Its borderline … simply of interest when we talk of options for forwarding user and management traffic \\ | ||
+ | |||
+ | __Item 2: Who is working on what__ \\ | ||
+ | MK: Looking at Home Gateway and ISP Edge from the forwarding point of view … has something to contribute \\ | ||
+ | MK: In the middle of containers vs VM’s … Would also like to work there \\ | ||
+ | MK: Not a security guy, but is in possession of a report \\ | ||
+ | MK: List of gaps \\ | ||
+ | JB: Squaring bare metal with remote survivability \\ | ||
+ | JB: Multi DC management/orchestration \\ | ||
+ | JB: Securing the link \\ | ||
+ | JB: List of gaps \\ | ||
+ | JH: Containers vs VM \\ | ||
+ | JH: Mano \\ | ||
+ | |||
+ | __Next Steps__ \\ | ||
+ | * Those that stepped forward should work on capturing lead ideas/thoughts in as much detail as possible for | ||
+ | the next meeting \\ | ||
+ | * Comments invited from everyone on all topics under development, especially including the list of gaps. \\ | ||
+ | * James to solicit input on times for next meetings initial target is week of Jan 11. \\ | ||
+ | * At next meeting, we will present initial notes | ||
---- | ---- |