Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

  • Lab status
    • Orange lab tests results are not stored/tests are not execute for a couple of days Morgan Richomme
    • DT lab also (smile) but the lastest results looks promisingImage Added  Looks healthchecks and pnf issues are resolved
    • DT tests results are not visble on https://logs.onap.org/ Andreas Geissler Michał Jagiełło
      Jira
      serverONAP Jira
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyINT-1956
  • Acceptance criterias for Istanbul (TSC Objectives)
    • Infrastructure healthcheck: 100%
    • Healthcheck: 100%
    • Smoke use-cases: 100%
    • Security: 100%
      • Some errors may be considered as exceptions:
        • PODs used for tests - we agree that all tests resources should be created in separate namespace
          Jira
          serverONAP Jira
          serverId425b2b0a-557c-3c0c-b515-579789cceedb
          keyTEST-356
        • PODs which are no more maintained (e.g. ESR)
      • For all other cases JIRA tickets should be created
    • Stability: 85%
  • Istanbul integration blocking points
    • Two more open tickets:
      • Jira
        serverONAP Jira
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyINT-1925
      • Jira
        serverONAP Jira
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyOOM-2285
  • More advanced SO instantiation test use cases


 

  • Labs status
    • pnf_macro and pnf-register failing but after the debugging of pnf_macro the possible source of the problem was found and reported. The fix is ready PRH change https://gerrit.onap.org/r/c/oom/+/122864. Gating results look very promising: https://logs.onap.org/onap-integration/gating/122864-5/index.html
    • cleanup issues: looks like the tests cleanup not works as we expected :) The MSB K8S instance created in pnf_macro test (pnf_simulator) is not deleted if test fails on any further steps (but before the cleanup) because we aggreed that the cleanup is a part of the test execution. Possible solutions:
      Jira
      serverONAP Jira
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyTEST-355

      • we should run cleanup for steps which were already executed and passed
      • we should create additional K8S resources on separate namespaces and delete them after test exection
    • OOF deployment issue 
      Jira
      serverONAP Jira
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyOPTFRA-981
      - not resolved yet, krishna moorthy is working on that. Dong (China Telekom) will be a contact point
  • Slicing usecase issue:
    Jira
    serverONAP Jira
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyINT-1951

    • reproduction is not possible
    • documentation is outdated
    • there are some steps in description which looks "hacky" (image recreation, restart pods manually)
    • What we can do:
      • find anyone who can help to reproduce that use case and prepare a nice documentation
      • prepare a doc/wiki page with the clear use case acceptance process to avoid that kind of issues in the future

...