#opnfv-meeting: dovetai weekly meeting

Meeting started by hongbo123 at 14:03:36 UTC (full logs).

Meeting summary

    1. roll (hongbo123, 14:04:08)
    2. hongbo (hongbo123, 14:04:12)
    3. leo_wnag (leo_wang, 14:04:19)
    4. leo_wang (leo_wang, 14:04:26)
    5. dneary (dneary, 14:07:45)
    6. we have about four people in this dovetail meeting, we will start the discussion of dovetail release. this topic will be discussed next week (hongbo123, 14:08:32)

  2. dovetail release plan (hongbo123, 14:08:47)
    1. Larry Lamers (ljlamers, 14:11:50)

  3. Dovetail test tool requirements (dneary, 14:24:35)
    1. Leo gives a current status - takes a test case, and runs test cases from upstream test projects (dneary, 14:24:57)
    2. Most functionality is ready. Jira tasks created for the tool already (dneary, 14:25:16)
    3. Most important is to add new tests (dneary, 14:25:45)
    4. Dave says that 2 potential requirements have been raised in recent weeks: (dneary, 14:27:19)
    5. 1. Ability to run test tool independent of OPNFV infrastructure (dneary, 14:27:37)
    6. 2. Cryptographic verification of test results (dneary, 14:29:47)
    7. Leo says for 1st, we are not ready today to support commercial vendors in this way (dneary, 14:30:07)
    8. For the 2nd, verifying test results has not been a priority for now. Hongbo believes that we can do this quickly, potentially for the first release (dneary, 14:32:50)
    9. Leo asks if this is a requirement for the first release. Dave says that if we award marks based on test results, that there will be resistance if there is no verification trail (dneary, 14:34:23)
    10. Leo asks if it is really a requirement, Chris agrees that we need to list requirements and ask for feedback from other groups like CVP on the priorities (dneary, 14:35:02)
    11. Dave says it's about expectation management about what we can and cannot do for 1st release, and if we don't do result verification, then it probably will not be used to award trademark usage. (dneary, 14:35:48)
    12. Leo says that outside of these, there are no major features which could be required for a first release (dneary, 14:38:44)
    13. (bearing in mind that these could also be optional) (dneary, 14:38:58)

  4. Dovetail test case release criteria (dneary, 14:39:30)
    1. Hongbo points out there are many candidate tests for consideration, and we should add more to the compliance test suite (dneary, 14:46:26)
    2. Dave points out that we have finalised a proposal for test case criteria this week (dneary, 14:47:05)
    3. Chris points out that there is some political context we need to consider when adding tests, and it is important that we work closely with the other test projects (dneary, 14:47:38)
    4. Hongbo proposes that we engage with the community on test cases to add so that we can add more (dneary, 14:49:35)
    5. Dave asks whether an arbitrary number of tests makes sense, and proposed that we focus instead on what functional areas we require test coverage for in the C release (dneary, 14:50:40)
    6. We discussed which functional areas made sense for the first release (dneary, 14:51:28)
    7. Target functional areas from C&C: (dneary, 14:53:51)
    8. Basic VIM operations (dneary, 14:54:36)
    9. NFV services (VPN, SFC, ...) (dneary, 14:54:46)
    10. Fault management/Localization, Audit (dneary, 14:55:01)
    11. Create scenarios/stacks (IPv6, FDS, ...) (dneary, 14:55:21)
    12. System testing (Functest, Yardstick) (dneary, 14:55:40)
    13. start email to continue discussion (hongbo123, 15:02:43)


Meeting ended at 15:03:15 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. dneary (33)
  2. hongbo123 (10)
  3. collabot` (5)
  4. leo_wang (2)
  5. ljlamers (1)
  6. ChrisPriceAB (0)


Generated by MeetBot 0.1.4.