Versions Compared

Old Version 268

changes.mady.by.user Morgan Richomme

Saved on

compared with

New Version 269

changes.mady.by.user Morgan Richomme

Saved on

Key

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

...

  1. Action point follow-up

    •  Lukasz Rajewski prepare a demo on test automation managed by Lukasz..why it could not be integrated in CI for the moment (reflexion for Istanbul)
    •  Morgan Richomme sent a mail to PTL on good practice. Reminder that no patch in gate oldes than x months is a criteria for milestones..it is clearly not respected.
    •  Lasse Kaihlavirta plan a 20' section for a full session 
  2. Admin
    1. committers
    2. baseline images
    3. repo cleanup
  3. Status on CSIT Lasse Kaihlavirta : CSIT status after Honolulu.pptx
    1. CPS = Showcase example, everything is fine
    2. CCSDK previous showcase, still requires distributtion of docker builds, not possible to rebuild locally
    3. DMaaP (dmaap/buscontroller moved), OPTF (optf/odf and optf/has already moved), SDNC (almost finished but still some failures) transition in progress
    4. AAI mumtitenancy done outside ONAP planned to be incoprorated into aai/resources and aai/traversal => use of scala+gatling (examples based on robot so far)
    5. Policy: CSIT moved to reir repositories but tests do not follow reco (test after merge, not project specific, jjb fully specific
    6. Still some active projects with old design (DCAEGEN2, Modeling, Multicloud, OOM-platform-cert-service, SO)
    7. Usecase #action Morgan Richomme dig a little bit to understand if it corresponds to active use cases
    8. VFC and VID do not seem really maintained
    9. VNFSDK: only images for frankfurt => not maintained
    10. CSIT tests disabled (aaf, appc, clamp, music)
    11. clamp moved to SDC => what does it mean from a CSIT perspective
  4. Demo vFW CNF Lukasz Rajewski
    1. slide deck: #action Lukasz Rajewski put the slide deck here
    2. use case partially automated but would require a KUD (test cannot use a ns of the existing k8s hosting ONAP)
    3. As the use case is maintained and includes regularly feature changes, it woudl be interesting to include it in CI..to show that it is red/green as part of the use cases (more than smoke tests)
    4. #action Morgan Richomme Konrad Bańka Lukasz Rajewski estimate what is missing for integration in CI
    5. Open question and where the status of the xNF shall be available for ONAP admin..not clear status of the service/vnf/module was available in VID, some test status was available in SDC but not sure to know where the info on the status of the xNF would be the more accurate #action Morgan Richomme send a mail to the community to get feedback on this xNF status page
  5. AoB

  1. Action point follow-up
    1. AP1: Morgan Richomme review Integration simu and release versions if possible + update doc accordingly
      1. not done yet wait for release of the xtesting dockers
    2. AP2: all move or closed the JIRA in honolulu
      1. done
    3. AP3: report your feedback on honolulu lesson learned
      1. to be done
    4. AP4: participants indicate their top 3 priorities for honolulu (https://etherpad.anuket.io/p/onap_integration_istanbul)
      1. done
  2. Admin
    1. Admin status (PTL, election, INFO.yaml)
      1. congratulations Bartosz Gardziejewski elected as integration committer

...