Versions Compared

Key

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

 

  1. PNF presentation by Eliezio Oliveira(Ebo)
    1. Model-based, modular simulator 
    2. The simulator is composed by two modules: i) a Netopeer core Netconf server, and ii) a DB that hosts Yang models
    3. User provides configuration:
      1. Yang model that describes a Netconf end point
      2. initial configuration of the simulator (e.g. a JSON file that contains initial values of parameters defined in the Yang model)
      3. one or more Python scripts that include the operations that the PNF simulator executes when a change (i.e. API call) is made
    4. The simulator code is hosted by github (https://github.com/blue-onap/netconf-pnp-simulator.git) and runs as docker container
    5. The simulator can simulate different PNFs (modules) at the same time
    6. If one has to simulate multiple instances of the same PNF (module), the recommended way is to deploy multiple instances of the simulator docker container
    7. Current usage in ONAP:
      1. PNF subscription handler use case
      2. PNF software upgrade use case
    8. Possible approaches to hosting the code in ONAP repository
      1. Demo repository
      2. Integration repository
      3. Sub-repository within the Integration repository
  2. Lab status
    1. Integration-SB-01 (master branch) is almost a month old and not stable
    2. A new lab (master branch) will be created soon and information about VM access will be socialized via onap-discuss mailing list


 

  1. Feedback from the Syncho with Seccom
    1. priorities
    2. port scanning tests
      1. White list
      2. consequence on integration related pod
    3. root_pods
      1. consequence on integration related pod
      2. java docker? any jenkins expert to move that to official ONAP repo...
    4. introduction of kube-hunter (vulnerability checkers)
  2. Admin
    1. Specific Integration milestones to be defined and reported to David McBride: Integration M4 milestone possible evolution
    2. Update on Integration verification job
      1. python verification job added in Integration repo (for vCPE)
    3. alias team.onap.eu created
    4. reinsourcing of oom/robot in robot: https://gerrit.onap.org/r/c/oom/+/101605
  3. Lab Status
  4. Frankfurt status
    1. Use case update
      1. roundtable from use case owner
      2. Portal Selenium tests
        1. Is there any test plan already available in Portal
        2. If so is there any associated tests, shall we cretae on, leverage on healthportall?
      3. DCAE application deployment
      4. pnf_registrate status
      5. anyone working on and End to End "basic" CDS
    2. JIRA: https://jira.onap.org/secure/RapidBoard.jspa?rapidView=207&quickFilter=630
      1. Review Blocking JIRA review: 1: Frankfurt Release Integration Test Blocking Issues
      2. New A&AI regression detected (no more tenant id leading to failure of the end to end VNF tests)
    3. CI status
      1. Master status
      2. Parallelization of the VNF and security tests (to save CI time) in progress
      3. windriver CI still pending - runner is working well but clean/server creation seems to request parameters that do not fit well together
  5. AoB

...