#opnfv-functest: sync Auto/Functest /Orange

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

Meeting summary

  1. Presentation of Auto (morgan_orange, 15:02:41)
    1. https://wiki.opnfv.org/display/AUTO (morgan_orange, 15:03:27)
    2. working on CI (morgan_orange, 15:03:33)
    3. 3 use case: edge, entreprise vCPE, resiliency improvement (linked to DCAE) (morgan_orange, 15:04:35)
    4. auto part of Fraser and planned for Gambia (morgan_orange, 15:05:01)
    5. x86 and arm architecture both supported (onap + VNFs) (morgan_orange, 15:08:35)

  2. Functest (morgan_orange, 15:09:19)
    1. presentation of Functest project, xtesting and how xtesting has been used fro ONAP (morgan_orange, 15:50:29)
    2. yardstick is providing lots of tooling which can provide perf info (orchestrator = heat) (morgan_orange, 15:54:32)
    3. power consumption API available, integrated in Functest (morgan_orange, 16:06:16)
    4. not sure it is very active (morgan_orange, 16:06:26)
    5. http://testresults.opnfv.org/functest/xtesting/ (morgan_orange, 16:06:46)
    6. http://testresults.opnfv.org/functest/framework/ (morgan_orange, 16:06:52)
    7. http://testresults.opnfv.org/test/api/v1/results?case_name=cloudify_ims&last=1&criteria=PASS (morgan_orange, 16:08:10)
    8. https://build.opnfv.org/ci/view/functest/ (morgan_orange, 16:08:22)
    9. functest is run (like yardstick) after a scenario deployment (morgan_orange, 16:08:36)
    10. it integrates several tiers dockerized in alpine dockers (morgan_orange, 16:09:25)
    11. feature may be integrated in feature docker or even get their own docker if needed (morgan_orange, 16:09:25)
    12. being integrated in xtesting (providing bash/python/robot/unittest/vnbf abstraction) can be helpfule to be de facto integrated in scenario Ci and get results (morgan_orange, 16:09:49)
    13. contact for Functest is Functest PTL => Cedric Ollivier (usually reachable on this opnfv-functest IRC chan) (morgan_orange, 16:10:41)
    14. xtesting framework has been used for ONAP to integrate ONAP robot tests => 3 files needed to create a dedicated docker runnable trough an ONAP system (slice of the traditionnal robot healtcheck upstream tests) (morgan_orange, 16:11:37)
    15. Orange is planning to use xtesting for VNF (chain SO / SDNC API call) (morgan_orange, 16:12:06)

  3. XCI (morgan_orange, 16:12:15)
    1. XCI is an OPNFV project aiming to provide quick feedback to upstream community by integrating upstream versions e.g. Openstack + ODL (morgan_orange, 16:12:46)
    2. discussions to add ONAP on Kubenernets scenario (morgan_orange, 16:12:59)
    3. https://etherpad.opnfv.org/p/xci-oom (morgan_orange, 16:13:11)
    4. contact Jack Morgan (K8S+ONAP) / Fatih (XCI) (morgan_orange, 16:13:28)
    5. Orange is currently pipelining k8 / ONAP (oom) and Openstack / ONAP (heat) (morgan_orange, 16:13:57)
    6. but still not 100% OK with both installers (morgan_orange, 16:14:08)
    7. results on official ONAP CI looks better (morgan_orange, 16:14:19)
    8. http://12.234.32.117/jenkins/ (morgan_orange, 16:14:58)
    9. contact Gary Wu (morgan_orange, 16:15:12)

  4. open dicsussion (morgan_orange, 16:15:23)
    1. considering fuel + heat based installation makes sense for a first installation especially if you want to test installation on arm and x86 (morgan_orange, 16:15:49)
    2. XCI could be eventually levergaed for OOM installation (morgan_orange, 16:16:04)


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

Action items

  1. (none)


People present (lines said)

  1. morgan_orange (37)
  2. collabot_ (3)


Generated by MeetBot 0.1.4.