#opnfv-meeting: OPNFV TSC

Meeting started by ChrisPriceAB at 15:00:51 UTC (full logs).

Meeting summary

  1. TSC roll call (ChrisPriceAB, 15:00:59)
    1. Gerald Kunzmann (DOCOMO) (GeraldK, 15:01:08)
    2. Chris Price (ChrisPriceAB, 15:01:09)
    3. Dirk Kutscher (NEC) (dku, 15:01:19)
    4. Frank Brockners (frankbrockners, 15:01:21)
    5. Frank Zdarsky (Red Hat) (fzdarsky, 15:02:01)
    6. Julien (rpaik, 15:02:10)
    7. Parviz Yegani (Parviz, 15:02:12)
    8. Uli Kleber (uli__, 15:02:25)
    9. dlenrow (dlenrow, 15:02:49)
    10. Prakash (rprakash__, 15:02:51)
    11. Bryan Sullivan (bryan_att, 15:03:02)

  2. Approval of minutes (ChrisPriceAB, 15:03:33)
    1. Pranav Mehta (Pranav, 15:04:02)
    2. AGREED: minutes approved. (ChrisPriceAB, 15:04:26)
    3. Wenjing Chu (Wenjing, 15:04:28)

  3. Agenda Bashing (ChrisPriceAB, 15:04:35)
    1. HELP: minutes link? (rprakash__, 15:05:21)
    2. frankbrockners indicates meeting can finish earlier. (ChrisPriceAB, 15:08:09)
    3. discussed and agreed two hour TSC still necessary by default (dlenrow, 15:09:02)
    4. depending on topics we have can keep to 2 hrs or less (rprakash__, 15:09:35)

  4. OpenStack community discussion (ChrisPriceAB, 15:09:46)
    1. telcowg in openstack has not met as per my intercations may be some one has beter info (rprakash__, 15:10:41)
    2. Introductions: Russell Bryant, OpenStack techncal committee member, looking into NFV as part of his OpenStack work (dneary, 15:10:59)
    3. I mean 2015 (rprakash__, 15:11:02)
    4. palani (palani, 15:11:16)
    5. Ok I missed it was to get the use case for MNO/MVNO added and will ersue next week (rprakash__, 15:11:44)
    6. Introductions: Jay Pipes, OpenStack TC member, working for Mirantis, former PTL, interested in avoiding duplication of effort & ensuring OpenStack and OPNFV work well together (dneary, 15:12:17)
    7. any updates on yesterday meetings any links to share on summary? (rprakash__, 15:12:24)
    8. Introductions: Kyle Mestery, future Neutron PTL (dneary, 15:12:43)
    9. Introductions: Thierry Carrez, release manager for OpenStack, OpenStack TC chair (dneary, 15:13:16)
    10. any action items taken up in yesterdays telcowg? (rprakash__, 15:13:49)
    11. I don't see yet any 2015 meeting logs in telcowg (rprakash__, 15:15:27)
    12. link: evesdrop.openstack.org/meetings/nfv/ (rprakash__, 15:16:12)
    13. thanks its telcowg and not nfv I see details on zones etc - appreciate and any summay from attendees? (rprakash__, 15:18:26)
    14. so the focus on telcowg was on Security Seggregation (Placement Zones) (rprakash__, 15:21:02)
    15. I will submit the MNO/MVNO use case by email to one of you from A&T who can update that on site? (rprakash__, 15:22:27)
    16. reason I may not be able to join next week but if there is a way to add and start debating will help in telcowg for as OPNFV will will need to bind Policys, users/tenant sructure etc. have several BPs impacting for k2/l.. in upstream (rprakash__, 15:24:24)
    17. going back on Security Seggregation why only L2 (VLAN) seggeration between MZ & DMZ , most designs or IPV6 L3 based any specific reason for that in use case presentaion (rprakash__, 15:28:13)
    18. will add my inpus to DaSchad is he here? (rprakash__, 15:31:00)
    19. HELP: is there a goto meeting along with this or just IRC for today? (rprakash__, 15:33:18)
    20. https://global.gotomeeting.com/join/798898261 (frankbrockners, 15:33:37)
    21. this is GTM meeting #798898261 (dlenrow, 15:34:12)
    22. nobody presenting thus far on GTM (dlenrow, 15:34:42)
    23. Mike B asks how we can best manage end to end test/use cases when significant portions of these are built in upstream communities. If the validation schema's are distributed it can be difficult to understand and troubleshoot these and manage the lifecycle of them. (I think) (ChrisPriceAB, 15:34:59)
    24. Jay asks for a process overview of OpenStack methodologies in this area to help provide clarity around upstream processes in OpenStack for the OPNFV community. (which will help answer the above question) (ChrisPriceAB, 15:37:37)
    25. Overview on release and planning: design summits every 6 months. It's a working event, usually 5 days, where specifications of proposed feature implementations are discussed/debated, and priorities for the next release cycle are agreed upon. (jaypipes, 15:39:16)
    26. Next design summit is in Vancouver in May (jaypipes, 15:39:27)
    27. Specifications targeted for Kilo that are approved for Nova: http://specs.openstack.org/openstack/nova-specs/specs/kilo/index.html (jaypipes, 15:40:06)
    28. Example NFV-related spec: http://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/input-output-based-numa-scheduling.html (jaypipes, 15:40:21)
    29. OPNFV plans a technical event to coincide with the Vancouver OpenStack event to maximize collaborative dialogs across communities. (ChrisPriceAB, 15:40:41)
    30. OpenStack uses a time-based release cycle. Current one is named Kilo -- https://wiki.openstack.org/wiki/Kilo_Release_Schedule (ttx, 15:40:49)
    31. *Unapproved* specifications currently under review: https://review.openstack.org/#/q/status:open+project:openstack/nova-specs,n,z (jaypipes, 15:41:02)
    32. anyone can vote and comment on any spec (and we encourage lots of feedback) (jaypipes, 15:41:16)
    33. We are available on mailing list and #openstack-[nova|neutron|dev] IRC channels if you have any questions on our processes (jaypipes, 15:42:13)
    34. the prefix [NFV] is used in OpenStack to identify e-mail traffic intended to discuss NFV related topics (topic filtering is possible) (ChrisPriceAB, 15:43:06)
    35. HELP: do we mainatain logs of these meetings in opnfv? (rprakash__, 15:43:36)
    36. HELP: where can I fiind that? (rprakash__, 15:44:07)
    37. http://meetbot.opnfv.org/meetings/opnfv-meeting/ (rpaik, 15:44:19)
    38. thanks Chris (rprakash__, 15:44:22)
    39. https://wiki.opnfv.org/wiki/tsc (ChrisPriceAB, 15:44:28)
    40. Telco Working Group IRC meeting information: https://wiki.openstack.org/wiki/Meetings#Telco_Working_Group_Meeting (jaypipes, 15:46:42)

  5. Update on Bootstrap project (ChrisPriceAB, 15:49:02)
    1. https://wiki.opnfv.org/get_started (ChrisPriceAB, 15:49:24)
    2. Frank provides an update of the bgs project: (ChrisPriceAB, 15:52:06)
    3. many participants doing private investigative work and experimentation (ChrisPriceAB, 15:52:22)
    4. unable to run collaborative activites due to a lack of sufficient hardware resources (ChrisPriceAB, 15:52:43)
    5. hardware is now available for developmental work, with restrictions on security access to the equipment (ChrisPriceAB, 15:53:29)
    6. it has been identified that our own hardware is needed to overcome the various issues we have found trying to get the bgs project off the ground (ChrisPriceAB, 15:54:03)
    7. the topic of installers is an item pending concensus on the best approach for OPNFV release 1, attempts ongoing with Fuel found to be difficult to extend for OPNFV work (ChrisPriceAB, 15:55:05)
    8. daily meetings are being run over IRC, at 06:00 PST and 17:00 PST which have not been attended as much as would have been hoped for. IRC chanel is irc.freenode.net:6697/opnfv-bgs (ChrisPriceAB, 15:56:30)
    9. Frank identifies the hardware need is the blocking issue currently, and that an installer needs to be selected. (ChrisPriceAB, 15:58:03)
    10. Gerard asks if there is an estimate for a timeline for key decisions. (installer and hardware for instance) (ChrisPriceAB, 15:59:14)
    11. Frank answers that some of these issues are ready for decision now however a clear plan is not easily defined right now. (ChrisPriceAB, 16:00:12)
    12. Palani mentions he is interested to continue with Fuel based on his experiences so far working with it, including the possibility to include OpenDaylight. (ChrisPriceAB, 16:01:59)
    13. Trevor indicates that the Intel testbed may be able to provide the needed hardware for bgs and CI until the build and integration infrastructure is available. (ChrisPriceAB, 16:05:45)

  6. Octopus project update (ChrisPriceAB, 16:28:25)
    1. Uli provides and update on the CI project process. (ChrisPriceAB, 16:28:41)
    2. the team is wrking on the detailed task list for the project to establish a framework for collaboration. (ChrisPriceAB, 16:29:03)
    3. Uli indicates there are issues with the timing of next weeks meeting. (ChrisPriceAB, 16:29:57)
    4. dlenrow asks is octopus is suspended until bgs has reached a certain point and then would start working form that base point. (ChrisPriceAB, 16:30:42)
    5. Uli describes that the planning phase needs to be mature and actionable when bgs has reached such a point. This work needs to be done first in anticipation of the bgs baseline output. (ChrisPriceAB, 16:31:32)

  7. OPNFV HW infrastructure requirements (ChrisPriceAB, 16:35:41)
    1. https://wiki.opnfv.org/get_started/get_started_work_environment (ChrisPriceAB, 16:36:36)
    2. Frank describes that a selection of POD's would be required to enable parallel development of platform types as a wish list for the hardware. (ChrisPriceAB, 16:37:36)
    3. The basic POD set-up would include a master-node, 3 control nodes, and 2 compute nodes (ChrisPriceAB, 16:38:22)
    4. servers require to be able to be pixie booted, a 40g NIC is required to work toward our target capabilities for OPNFV. (ChrisPriceAB, 16:39:06)
    5. any purchase should be relatively future proof. (ChrisPriceAB, 16:39:40)
    6. dedicated storage does not seem to be a high priority requirement for NFV functions. (ChrisPriceAB, 16:39:54)
    7. 2 40g NICs are prefered, nor necessary (julien_ZTE, 16:40:37)
    8. question: does the NIC support SR-IOV ? (julien_ZTE, 16:50:27)
    9. AGREED: the hardware needs for the CI/CD and bgd projects need to be concluded by the upcoming TSC meeting on Tuesday the 13th of January. (ChrisPriceAB, 16:51:21)
    10. ACTION: tuesday deadline for opnfv hardware upgrade on get started web page (rprakash, 16:51:44)
    11. ACTION: frankbrockners to present options for hardware aquisition/leasing on Tuesdays TSC meeting. (ChrisPriceAB, 16:52:33)
    12. ACTION: All: identify needed, networking, connectivity, networking, storage, power needs for the hardware. (ChrisPriceAB, 16:53:29)
    13. frankbrokners, yes in our test, currently no other sulotions for the the traffic (julien_ZTE, 16:53:41)
    14. frankbrockners, yes in our test, currently no other sulotions for the the traffic (julien_ZTE, 16:54:23)

  8. AoB (ChrisPriceAB, 16:58:13)
    1. the OPNFV WiKi is not up to date and seems stale at times. Actions needed on the guidelines for the WiKi shoudl be addressed next week. (ChrisPriceAB, 17:00:28)
    2. project leads should keep project wiki pages up tp date (rpaik, 17:00:52)


Meeting ended at 17:01:08 UTC (full logs).

Action items

  1. tuesday deadline for opnfv hardware upgrade on get started web page
  2. frankbrockners to present options for hardware aquisition/leasing on Tuesdays TSC meeting.
  3. All: identify needed, networking, connectivity, networking, storage, power needs for the hardware.


Action items, by person

  1. frankbrockners
    1. frankbrockners to present options for hardware aquisition/leasing on Tuesdays TSC meeting.
  2. UNASSIGNED
    1. tuesday deadline for opnfv hardware upgrade on get started web page
    2. All: identify needed, networking, connectivity, networking, storage, power needs for the hardware.


People present (lines said)

  1. ChrisPriceAB (56)
  2. rprakash__ (22)
  3. dneary (13)
  4. jaypipes (10)
  5. collabot` (8)
  6. dlenrow (6)
  7. ttx (5)
  8. julien_ZTE (4)
  9. rpaik (4)
  10. frankbrockners (3)
  11. GeraldK (2)
  12. uli__ (2)
  13. palani (1)
  14. russellb (1)
  15. Pranav (1)
  16. TapioT (1)
  17. bryan_att (1)
  18. mestery (1)
  19. Parviz (1)
  20. Wenjing (1)
  21. dku (1)
  22. rprakash (1)
  23. fzdarsky (1)
  24. frankbrckners (0)


Generated by MeetBot 0.1.4.