#opnfv-meeting: OPNFV TSC Meeting

Meeting started by ChrisPriceAB at 13:59:22 UTC (full logs).

Meeting summary

  1. roll call (ChrisPriceAB, 13:59:27)
    1. Chris Price (ChrisPriceAB, 13:59:37)
    2. Uli (uli-k_, 13:59:39)
    3. Gerald Kunzmann (GeraldK, 13:59:39)
    4. Frank Brockners (frankbrockners, 13:59:49)
    5. Tapio Tallgren (Tapio_T, 14:01:26)

  2. Previous Minutes of meeting (ChrisPriceAB, 14:01:44)
    1. no feedback on previous minutes, approved. (ChrisPriceAB, 14:01:53)

  3. Agenda Bashing (ChrisPriceAB, 14:02:00)
    1. https://wiki.opnfv.org/wiki/tsc Todays Agenda (ChrisPriceAB, 14:02:09)
    2. Wenjing (Wenjing, 14:02:14)
    3. Morgan Richomme (morgan_orange, 14:02:16)
    4. Narinder Gupta (narindergupta, 14:02:43)
    5. Bryan Sullivan (bryan_att, 14:02:45)
    6. Dirk Kutscher (dku, 14:02:58)

  4. Strategic Planning Committee discussion (ChrisPriceAB, 14:04:55)
    1. Chris outlines the identified need to address OPNFV consumers in the Brahmaputra timeline with a theme of "lab ready" (ChrisPriceAB, 14:06:31)
    2. Chris (Donley) outlines the focus areas the Strategic planning committee has identified for Brahmaputra (ChrisPriceAB, 14:06:49)
    3. Parviz Yegani (Parviz, 14:07:11)
    4. multi-site while important is seen to be heavily dependant on MANO components to realise in a meaningful way in the Brahmaputra time-frame. (ChrisPriceAB, 14:07:39)
    5. Chris presents a mapping of the identifies capabilities/themes with projects participating in the Brahmaputra release (ChrisPriceAB, 14:08:20)
    6. Chris outlines that cadence of release and iterative development is more important that completeness. Some capabilities may not be ready until the C-Release which is acceptable. (ChrisPriceAB, 14:09:48)
    7. he asks that the user stories be prioritized rather than completeness of features (ChrisPriceAB, 14:10:03)
    8. Chris indicates he will facilitate community support for resource shortages with the board in his capacity as SPC chair (ChrisPriceAB, 14:10:44)
    9. Ray Nugent asks if there are preferences on installer tools for the features (ChrisPriceAB, 14:11:19)
    10. Chris answers that the installers need to work, but the focus from the committee is on the features in the platform. (ChrisPriceAB, 14:11:49)
    11. Ray Nugent asks if the SPC has any views on the release artifacts to be delivered. (ChrisPriceAB, 14:13:37)
    12. ChrisPriceAB to post the slides on the wiki (rpaik, 14:13:45)
    13. Chris responds that the SPC does not have any specific opinions on the form of release. (ChrisPriceAB, 14:14:03)
    14. Brian asks if the intention is for targetted testing to focus on these use cases. (ChrisPriceAB, 14:14:36)
    15. Chris responds that test cases would be valuable for lab activities and an important component of the activity. (ChrisPriceAB, 14:15:00)
    16. Chris adds that the goal is to provide similar feedback earlier for future releases (e.g. prior to milestone C) (rpaik, 14:17:56)
    17. Chris outlines the committee will focus around 2 releases in the future moving forward. (ChrisPriceAB, 14:18:13)

  5. TSC update to the board (ChrisPriceAB, 14:18:48)
    1. topics presented were technical community elections/project lifecycle updates/Brahmaputra milestone C update (rpaik, 14:20:28)
    2. also discussed Pharos status (rpaik, 14:23:31)

  6. Community lab readiness for Brahmaputra (ChrisPriceAB, 14:26:08)
    1. Parviz asks if we can quantify risks of not having sufficient HW in the LF lab? (rpaik, 14:26:44)
    2. there is a discussion on establishing more infrastructure in the LF lab. (ChrisPriceAB, 14:26:58)
    3. uli-k outlines the risk of not bringing more hardware into the CI infrastructure on the project with combinatorial deployments (ChrisPriceAB, 14:27:39)
    4. Julien (julien_ZTE, 14:29:21)
    5. feedback form the community is that adding the additional capacilty in the existing lab would be highly beneficial for the project. (ChrisPriceAB, 14:29:36)
    6. Tapio raises the point that including ARM servers in the lab would be beneficial for the community. (ChrisPriceAB, 14:31:49)
    7. AGREED: Ths TSC would like to request additional funding for filling the existsing LF infra rack with servers to enable more deployment PODs in the LF lab. (ChrisPriceAB, 14:33:21)
    8. uli-k outlines the need for more lab infrastructures to be made available for the community in the Pharos context. (ChrisPriceAB, 14:33:56)
    9. uli-k describes the need to activate the community labs and make them available to the community. (ChrisPriceAB, 14:34:27)
    10. ACTION: Pharos project to identify labs that intend to participate in Brahmaputra and be part of the CI pipeline. (ChrisPriceAB, 14:35:20)
    11. https://wiki.opnfv.org/pharos/hw_resource_allocation (morgan_orange, 14:36:41)

  7. OPNFV community election process - proposal (ChrisPriceAB, 14:37:09)
    1. https://wiki.opnfv.org/community_election_procedure latest proposal (rpaik, 14:37:49)

  8. Committer removal processes (ChrisPriceAB, 14:39:34)
    1. https://wiki.opnfv.org/developer/committer_removal link to the proposed process (ChrisPriceAB, 14:39:54)

  9. OPNFV release artifacts decision (ChrisPriceAB, 14:43:31)
    1. https://wiki.opnfv.org/releases/brahmaputra/release_artifacts_discussion#optionsrelease_artifacts options for release artifacts (rpaik, 14:44:25)
    2. VOTE: Voted on "Preference on minimum requirements on release artifacts?" Results are, abstain: 1, 2b: 1 (ChrisPriceAB, 14:48:32)
    3. VOTE: Voted on "Preference on minimum requirements on release artifacts?" Results are, A2b: 7, abstain: 1, A1b: 1 (ChrisPriceAB, 14:49:18)
    4. https://wiki.opnfv.org/releases/brahmaputra/release_artifacts_discussion#optionsrelease_maintenance release maintenance options (rpaik, 14:49:48)
    5. VOTE: Voted on "Preference on release maintenance?" Results are, abstain: 2, M2a: 4, M2b: 2, M3b: 1 (ChrisPriceAB, 14:51:14)

  10. WiKi tool decision (ChrisPriceAB, 14:51:40)
    1. rpaik outlines that the preference for voters seems to be to move to confluence. (ChrisPriceAB, 14:52:26)
    2. VOTE: Voted on "Shall the TSC determine to migrate our WiKi to confluence?" Results are, 0: 5, +1: 6 (ChrisPriceAB, 14:54:37)
    3. vote count migration to confluence: 7/abstain:5 (rpaik, 14:57:14)
    4. AGREED: The TSC agrees to migrate our wiki to Confluence. (ChrisPriceAB, 14:57:18)

  11. TSC Meeting during OpenStack Summit (ChrisPriceAB, 14:57:34)
    1. https://etherpad.opnfv.org/p/OpenStackTokyo sign-up for OPNFV booth (rpaik, 14:57:53)
    2. rpaik describes the activities at the OpenStack summit are listed in the link above (ChrisPriceAB, 14:58:44)
    3. rpaik proposes we move the TSC call to 17:00 Tokyo time on Monday to reduce conflict with the OpenStack summit (ChrisPriceAB, 14:59:17)


Meeting ended at 15:01:38 UTC (full logs).

Action items

  1. Pharos project to identify labs that intend to participate in Brahmaputra and be part of the CI pipeline.


People present (lines said)

  1. ChrisPriceAB (63)
  2. collabot (35)
  3. rpaik (11)
  4. ThomasNadeau (10)
  5. uli-k (7)
  6. GeraldK (7)
  7. bryan_att (7)
  8. tapio_ (6)
  9. julien_ZTE (5)
  10. frankbrockners (5)
  11. Parviz (5)
  12. dku (5)
  13. bjskerry (4)
  14. morgan_orange (4)
  15. narindergupta (3)
  16. mbeierl (3)
  17. fdegir (2)
  18. uli-k_ (2)
  19. Tapio_T (1)
  20. Wenjing (1)
  21. debrascott (1)
  22. ilu-k (0)


Generated by MeetBot 0.1.4.