#onap-int: Integration Weekly Meeting

Meeting started by helenychen at 14:03:20 UTC (full logs).

Meeting summary

    1. a few new docker images from sdc, and new images from SO and multicloud is not accepted (Guest16632, 14:05:55)
    2. clarify SDC new images are accepted, but SO and multicloud images are not accepted yet (Guest16632, 14:06:51)
    3. OOM has not branched yet (Guest16632, 14:08:20)
    4. After OOM branches for casablanca, integration team will run a final round of automated testing (Guest16632, 14:10:58)
    5. gary reported oom-daily fails last a few builds (Guest16632, 14:18:47)
    6. oom-daily build failure is on windriver (Guest16632, 14:19:35)
    7. marco reported when onap starts, you would see containers in error state in new version of kubectl (Guest16632, 14:22:40)
    8. kubectl version changed from 1.10 to 1.11 (Guest16632, 14:25:09)
    9. OOM will provide H/A cluster guide, it should be need (Guest16632, 14:27:42)
    10. brian suggest to add more regions in demo init (Guest16632, 14:30:06)
    11. helen: should automate vcpe TOSCA use case (Guest16632, 14:31:28)
    12. helen: tata communication will be willing to contribute resource for testing (Guest16632, 14:32:06)
    13. brian: suggest to split sdc robot in dublin, it grows big (Guest16632, 14:32:58)
    14. brian: robot need to run in k8s cluster because it uses internal port (Guest16632, 14:34:44)
    15. Gary will provide his instruction on updating docker image version in wiki (Guest16632, 14:39:01)
    16. ACTION: review readthedocs in integration repo docs directory (Guest16632, 14:45:13)
    17. helen: add readthedocs stuff like how to install OOM ONAP by integration, override file (Guest16632, 14:46:28)
    18. ACTION: : gary add into readthedocs how to upgrade docker image version (Guest16632, 14:49:03)
    19. ACTION: : helen will add a section for each use case and let use case owner add their use case specific release notes (Guest16632, 14:49:59)
    20. ACTION: helen will contact doc team lead (rich or sophie?) on how to add use case specific info (Guest16632, 14:51:41)
    21. https://gerrit.onap.org/r/gitweb?p=integration.git;a=tree;f=docs;h=ff115c44b523a6b986771000e3060c2a20c50fb2;hb=refs/heads/casablanca (Guest16632, 14:59:28)
    22. use case should provide a readthedocs in the above link directory (Guest16632, 14:59:53)
    23. use case can provide a link back to wiki if they have (Guest16632, 15:02:05)
    24. use case team should provide short version of their use case issues and workaround in the above directory (Casablanca) with their own .rst by Friday (Guest16632, 15:05:08)
    25. ACTION: Yang will reach out to Yan Yang to provide the use case doc (Guest16632, 15:11:55)
    26. put in the rst file: 1. a brief of your use case and its link to its proposal 2. Test status link 3. Known issues/bugs and workaround (a. scripts including link in git to the script files b. manual steps) (Guest16632, 15:30:34)
    27. the above is the content suggested going into each use case readthedocs (Guest16632, 15:32:30)


Meeting ended at 15:34:14 UTC (full logs).

Action items

  1. review readthedocs in integration repo docs directory
  2. : gary add into readthedocs how to upgrade docker image version
  3. : helen will add a section for each use case and let use case owner add their use case specific release notes
  4. helen will contact doc team lead (rich or sophie?) on how to add use case specific info
  5. Yang will reach out to Yan Yang to provide the use case doc


People present (lines said)

  1. Guest16632 (30)
  2. collabot` (3)
  3. helenychen (1)


Generated by MeetBot 0.1.4.