#opnfv-testperf: Test & Performance weekly meeting December 12th

Meeting started by morgan_orange at 15:00:50 UTC (full logs).

Meeting summary

    1. Jose Lausuch (jose_lausuch, 15:01:30)
    2. Fatih Degirmenci (fdegir, 15:02:25)
    3. Frank Brockners (frankbrockners, 15:02:48)
    4. Morgan Richomme (morgan_orange, 15:03:22)

  2. Functest status (jose_lausuch, 15:04:36)
    1. making progress to run functest on the 4 installers (jose_lausuch, 15:04:55)
    2. almost successful running Functest from Jenkins on all of them, some environment issues to be fixed (jose_lausuch, 15:05:39)
    3. vPing working everywhere (jose_lausuch, 15:05:55)
    4. tempest runs everywhere but gives different kindof errors (jose_lausuch, 15:06:22)
    5. rally and vIMS not fully stable: some issues on some installers (jose_lausuch, 15:06:44)
    6. integration started of bgpvpn project (jose_lausuch, 15:07:27)
    7. no installer running opencontrail yet (jose_lausuch, 15:08:08)

  3. Yardstick status (jose_lausuch, 15:08:49)
    1. defined 11 test that MUST run on any installer (jose_lausuch, 15:09:01)
    2. they will continue developing some test cases after the code freeze (jose_lausuch, 15:10:01)
    3. the deadline is to freeze de feature projects code (tests cases) but not integration in yardstick/functest/.. (jose_lausuch, 15:10:32)
    4. minimum 4 times in a row from the CI passing the criteria defined by functest and yardstick (jose_lausuch, 15:11:52)

  4. Qtip status (jose_lausuch, 15:12:19)
    1. identify which test are acceptable if they don´t pass due to installed features in place that prevent them to pass (jose_lausuch, 15:21:47)
    2. making sure that the tests run on different labs. Soon run from jenkins (jose_lausuch, 15:22:28)
    3. qtip to run within a docker container too (jose_lausuch, 15:22:40)
    4. make sure that qtip runs also in fuel and apex (jose_lausuch, 15:27:38)
    5. New test projects will be taken into CI once the development work is done and validated against the existing installers (fdegir, 15:29:00)

  5. VSperf (jose_lausuch, 15:29:18)
    1. The order of CI runs will be: build (if valid), deploy, functest, yardstick (fdegir, 15:29:26)
    2. Jobs of other test frameworks will be added accordingly once they're confirmed to be ready (fdegir, 15:29:53)
    3. no particular concerns to raise so far (jose_lausuch, 15:29:54)
    4. https://build.opnfv.org/ci/job/installer-controller-pod-daily-master/ (fdegir, 15:35:32)
    5. there won´t be a jjob for each scenario, jjob will be "dumb", the test projects have to read the parameters of the scenario and proceed accordingly (jose_lausuch, 15:38:28)
    6. generic jobs for scenarios (jose_lausuch, 15:39:15)
    7. https://build.opnfv.org/ci/job/installer-controller-pod-daily-master/ (jose_lausuch, 15:39:27)
    8. Patch under review https://gerrit.opnfv.org/gerrit/#/c/4781/ (fdegir, 15:40:34)

  6. Release stability (jose_lausuch, 15:42:12)
    1. Chris and Debra propose lab ready: deploy without problems. run the basic tests without problem, but the features themselves don't need to be as stable as the infrastructure (jose_lausuch, 15:43:54)
    2. Debra asks what happens is some tests work on all installers but 1 (for example) (jose_lausuch, 15:47:41)
    3. Morgan points out that those minimum set of tests must work on all installers (Openstack infra verification, …) (jose_lausuch, 15:48:08)

  7. Demo (jose_lausuch, 15:52:50)
    1. https://wiki.opnfv.org/opnfv_test_dashboard/opnfv_kibana_dashboards (jose_lausuch, 15:53:43)


Meeting ended at 16:06:23 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. jose_lausuch (37)
  2. fdegir (9)
  3. collabot` (4)
  4. morgan_orange (4)
  5. frankbrockners (1)


Generated by MeetBot 0.1.4.