#opnfv-meeting: OPNFV TSC

Meeting summary

1. roll call (ChrisPriceAB, 14:59:10)
   1. Uli Kleber (uli-k_, 14:59:14)
   2. Chris Price (ChrisPriceAB, 14:59:15)
   3. Frank Brockners (frankbrockners, 15:00:06)
   4. Edgar StPierre (edgarstp, 15:00:31)
   5. Dave Neary (dneary, 15:00:45)
   6. Brian Skerry (bjskerry, 15:00:46)
   7. Gerald Kunzmann (DOCOMO) (GeraldK, 15:01:00)
   
   
2. approval of previous minutes of meeting (ChrisPriceAB, 15:01:05)
   1. https://wiki.opnfv.org/wiki/tsc#december_8_2015 previous minutes (ChrisPriceAB, 15:01:10)
   2. minutes approved, no comments (ChrisPriceAB, 15:01:23)
   
   
3. Agenda Bashing (ChrisPriceAB, 15:01:29)
   1. https://wiki.opnfv.org/wiki/tsc#december_15_2015 todays agenda (ChrisPriceAB, 15:01:42)
   2. Bryan Sullivan (bryan_att, 15:02:13)
   3. Dirk Kutscher (dku, 15:02:18)
   4. no additions to the Agenda (ChrisPriceAB, 15:02:45)
   5. Julien (Julien-zte, 15:02:56)
   
   
4. OPNFV internship program proposal (ChrisPriceAB, 15:02:57)
   1. https://wiki.opnfv.org/developer/internship-program main internship program page (rpaik, 15:03:06)
   2. https://wiki.opnfv.org/developer/intern-projects-page project proposal page (rpaik, 15:03:27)
   3. dlenrow (dlenrow, 15:03:33)
   4. rpaik outlines the proposed structure for the internship program (ChrisPriceAB, 15:04:13)
   5. we have allocated a budget for around 10 interns for 2016 (ChrisPriceAB, 15:04:25)
   6. any community member can propose an "internship project proposal" targetting graduate or undergraduate students (ChrisPriceAB, 15:04:51)
   7. The goal of the program is to advertise the project proposals to the student community (ChrisPriceAB, 15:05:22)
   8. the mentor who proposed the project will be responsible for selecting and mentoring the candidates (ChrisPriceAB, 15:05:44)
   9. rpaik has proposed a program that will be able to run all year to accomodate our global community. (ChrisPriceAB, 15:06:11)
   10. internships may run as a three month program, or optionally as a six month program for students who will be studying while doing the internship. (ChrisPriceAB, 15:06:56)
   11. the internship program pages can be improved by the community or by providing feedback directly to rpaik (ChrisPriceAB, 15:08:18)
   12. dneary outlines the constraining factor may be a limit to the number of mentors, is there a process for identifying mentors. (ChrisPriceAB, 15:08:57)
   13. there will be effort required from the mentor during the project. (ChrisPriceAB, 15:10:03)
   14. dku states that a result or summary of the work would be valuable to provide at the end of the project for visibility and awareness of the results. (ChrisPriceAB, 15:11:47)
   15. chrispriceab asks if we are constrained to 10 projects (ChrisPriceAB, 15:13:48)
   16. rpaik says we can increase the available budget if we have more mentors available for projects (ChrisPriceAB, 15:14:07)
   17. We could make suggestions that the mentors post progress (e.g. on the wiki) toward the goals on a regular basis or at key progress points, without getting too specific on the timing. (bryan_att, 15:14:30)
   18. HKirksey describes that the quality of the mentor will be critical for the success of the program. The interns are dependant on the mentor for their success which reflects on our community. (ChrisPriceAB, 15:15:08)
   19. dneary asks if there is an expectation that the project be OPNFV focused, or also be able to wrk in upstream projects? (ChrisPriceAB, 15:15:59)
   20. rpaik states that both would be viable, as long as the work relates to OPNFV developmental efforts. (ChrisPriceAB, 15:16:22)
   21. Parviz Yegani (Parviz, 15:16:59)
   22. dneary adds that upstream mentoring requires competent mentors form the upstream community. and to keep the projects simple. (ChrisPriceAB, 15:17:21)
   
   
5. Brahmaputra update (ChrisPriceAB, 15:19:54)
   1. debra has been working with the community on CI/Genesis/test infrastructure focus activities. (ChrisPriceAB, 15:20:29)
   2. a community call was held for plugin development as it was identified as a gap in our Brahmaputra development (ChrisPriceAB, 15:20:57)
   3. more discussion will be needed for test case writing and upcoming milestone E in January (ChrisPriceAB, 15:21:36)
   4. https://wiki.opnfv.org/releases/brahmaputra#overview brahmaputra release page (ChrisPriceAB, 15:22:06)
   5. It would be good to clarify that if a use case turns out not to be verifiable, that use case needs to be removed from the release docs, or clearly put into a non-released backlog. (bryan_att, 15:24:08)
   6. GeraldK asks if we have a summary of the features available for all installer in Brahmaputra (ChrisPriceAB, 15:24:09)
   7. https://git.opnfv.org/cgit/genesisreq/tree/docs/sources/system-requirements.rst (frankbrockners, 15:24:30)
   8. https://git.opnfv.org/cgit/genesisreq/tree/docs/sources/ux-requirements.rst (frankbrockners, 15:24:41)
   9. uli-k describes that we do not yet have a stable base for our testing projects to further develop stability in the test suites. (ChrisPriceAB, 15:27:14)
   
   
6. Review and comments on the API workshop material (ChrisPriceAB, 15:33:27)
   1. https://wiki.opnfv.org/_media/community/opnfv_infomodels.pptx proposed material for the API modelling meeting on behalf of OPNFV (ChrisPriceAB, 15:34:23)
   2. the intention of this material is to communicate our desire to collaborate with SDO' performing interface modelling and specification (ChrisPriceAB, 15:35:03)
   3. bryan_att is still looking for input from the community on some technical areas. (ChrisPriceAB, 15:35:34)
   4. #info bryan_att will outline the way in which open source project adopt standards and implement them as they are made available (ChrisPriceAB, 15:36:39)
   5. working quickly and iteratively is the best way of SDO's interacting with open source projects on emerging standards. (ChrisPriceAB, 15:37:19)
   6. GeraldK adds that we may not need to model every interface in Yang/TOSCA but should be open to adopt existing interfaces where it makes sense. (ChrisPriceAB, 15:42:05)
   
   
7. Methods of publishing requirements work with our release (ChrisPriceAB, 15:42:43)
   1. bryan_att adds that ETSI pre-workshop meeting on Dec. 17th (rpaik, 15:42:59)
   2. uli-k adds that if requirements are added to the documentation tree, it may not require a lot of effort (rpaik, 15:45:55)
   3. Uli points out that the documents we release should receive a proper review before publication (GeraldK, 15:46:09)
   4. there is a view that requirements projects are living documents that are not fixed in time. (ChrisPriceAB, 15:49:54)
   
   
8. creation review for OVN for NFV (ChrisPriceAB, 15:50:47)
   1. https://wiki.opnfv.org/ovn4nfv ovn for nfv project proposal (ChrisPriceAB, 15:51:23)
   2. the goal of this project is to align on NFV requirements and contribute upstream to OVN to address them (ChrisPriceAB, 15:52:33)
   3. parviz asks what additional capability OVN provides (ChrisPriceAB, 15:55:10)
   4. vikramdham answers that OVN provides an alternative method of implementing existing features, but distributes network control elements. (ChrisPriceAB, 15:55:55)
   5. bjskerry asks if this project will work with the ovsnfv project (ChrisPriceAB, 15:57:22)
   6. vikram answers that the project intends to align (ChrisPriceAB, 15:57:37)
   7. chrispriceab asks if the project could be implemented within the scope of the ovsnfv project (ChrisPriceAB, 15:58:31)
   8. vikram answers that the objectives of the projects area quite different (ChrisPriceAB, 15:58:51)
   9. agree with VikramDham (Julien-zte, 15:59:31)
   10. Brian Skerry (bjskerry2, 16:00:59)

Action items

1. (none)

People present (lines said)

1. ChrisPriceAB (63)
2. bryan_att (13)
3. TomNadeau (12)
4. collabot` (10)
5. ildikov (10)
6. edgarstp (7)
7. fdegir (5)
8. dlenrow (4)
9. anac1 (4)
10. rpaik (4)
11. frankbrockners (3)
12. Julien-zte (3)
13. dneary (3)
14. GeraldK (3)
15. bjskerry2 (2)
16. dku (2)
17. uli-k_ (2)
18. Parviz (2)
19. Wenjing (1)
20. bjskerry (1)
21. Ritch (1)