Page History

...

• Status and Stucks
  

  • Current POMBA Casablanca Stories (Logging Project) -

    • Dublin Pomba Stories

  • Current Code Inspections

    • https://gerrit.onap.org/r/#/q/status:open+pomba

  • POMBA hourly healthcheck (CD deployment) - http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
  • Note we are currently just barely meeting our line coverage rates with the addition of SDNC Context builder into Dublin, which impacts Casablanca since they are measuring main
    • Also CLM issues need to be addressed in SDNC Context Builder.
  • We have created all our Casablanca branches in POMBA project. Thanks James and Michael. SDNC ones have also been created.
    
    • Note that we are still waiting on sure about dependent A&AI and SDNC release containers.
  • General Status
    • Casablanca
      • Note that only committers can see nexus iq results so folks submitting code can't see what issues they are introducing. This is an issue for us.
      • Our code coverage currently lists us as passed.
      • Security related bugs being worked on:

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-830

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-832

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-831

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-826

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-835

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-833

      • Stability related issues being worked on:

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-845

          • can close off

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-844

          • move to Dublin
      • Integration team still to close off a bug:

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-805

          • ping Brian
    • Dublin
      • SSL support necessary for AAI communications still in a holding pattern:

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-807

        • Jira
          server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-808

        • Note: Dublin OOM branch necessary to finalize bug fixes
          • They need to wait for the thumbs up from the integration team, so this may get impacted by the ONAP release delay
      • Still waiting on OOM branch for SDNC Context Builder deployment. (~November/December)

        • Jira
          server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-426

• Technical Discussion
  
  • Chesla should provide an update on the TOSCA task force plan if there's anything new
    • No update
  • Integration Team discussion
    • Need schedule
    • How to test L2 Fabric
      • Some of that information may be not be available in ONAP
      • But the resources will be, even if for other reason.
  • Consider demo schedules
• Making the PTL Happy
  
  • ONAP Casablanca RC2 Milestone
    • Logging Casablanca RC2 Deliverables for RC2 Milestone Checklist Template
    • Slipped to Nov 30th, but this just to allow more time for integration testing, not new work.
      • Anything new issues after the 15th does not need to be fixed
  • Dublin
    
    • CSIT needs to get done
      • Automated integration test that integration team can run. Need to get them.
      • Still open
    • Don't think we nee to present to architecture team this release as we are focused incremental improvements.
    • Consolidated monitoring
      • end to end monitoring - logging, kuberntets, etc
      • Improved logging.
        • Note we have not tested transaction ids in logs.
      • During operations.
      • They want single dashboard.
      • Can discuss in more details later.