TSC 2019-06-13 DDF El Alto Priority notes

Date

Goals

Discussion items

  • PTLs have asked for a pause to do some clean-up tech debt
    • ~4K epics, stories, bugs, tasks in JIRA need to be reviewed/aligned
  • Pentest results highlighted a great number of issues 
    • OJSI tickets #1
    • updates to environment to commonly agreed upon versions
    • Known vulneabarilities bu upgrading / replacing librarities
    • CII badging alignment
  • Documentyation
    • clean-up and standarzation
    • tutorial videos/recordings - EUAG will be providing feedback
  • CI/CD test automation
    • Eric Debeau CSIT - 61 healthchecks for 244 pods - unclear what we are really testing
    • can something really be part of a release if there are no health-checks, no e2e usecase testing, etc.
    • Kenny Paul need to revisit the infrastructure budget to assess what we can do. $$ were set aside
    • @Ahmad - we need to look not only at what needs to be tested but how we are testing - 
    • Seshu Kumar Mudiganti SO test cases are admittedly insufficient.  Most testing is robot based and we don't have much experience. We know what to do, but not how to do it. request a taskforce w/ SMEs on robot to work with PTLs on more robust testing. need help writing testcases. tests should be run before merge.
    • Pamela Dragosh The CSIT environment is a very complicated environment to build tests in. Very time consuming to build CSIT tests and get them to run. The design of it needs to be re-visited. Integrating Dmaap into CSIT is a must and very complicated. Policy Team built a Dmaap simulator for this.
    • FREEMAN, BRIAN D would like to see a mandate on how to test. SO at verify - but non SO need CSIT. Need to just start opening JIRAs. 
    • Keong Lim every ONAP project should release a pod for robot testing, that can be deployed into any system with OOM to run tests on that system
    • Resource alignment for taskforce needed
    • Summary: security, doc as uyou code, don't break the build