Agenda

• Status and Stucks
• Technical Discussion
• Making the PTL Happy

...

• 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
    • Status: RED – Michael O'Brien will need to address what looks like some outages in the tool
  • 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.
  • General Status
    • Casablanca
      • Casablanca OOM branch available!
      • Have AAI containers (data-router/validation-service) been released since last meeting?
        • Not sure; will ask.
      • Bugs in progress:

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-857

          • OOM work – I guess we'll have to merge it into casablanca and then create a clone bug for master now?
      • Bugs to be verified:

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-805

          
          
          • Pinged Brian for closure
      • Bugs closed off in last week:

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-833

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-834

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-835

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-845

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-855

    • Dublin
      • OOM master branch is Dublin!
      • Stories in progress:

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-517

        • Jira Legacy
          server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-426

          • Was waiting for OOM branch...this will be completed probably next week.
      • Bugs in progress:

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-807

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-808

          
          
          • Both were awaiting OOM...that work will proceed next week.

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-852

      • Bugs to be verified:

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-803

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-814

• Technical Discussion
  
  • TOSCA task force plan updates?
    • Chelsa off until new year.
  • 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
    • David Stangl hasn't had time to look at that yet.
• Making the PTL Happy
  
  • ONAP Casablanca RC2 Milestone
    • Logging Casablanca RC2 Deliverables for RC2 Milestone Checklist Template
    • Should be voted on today.
  • Dublin
    
    • CSIT needs to get done
      • Automated integration test that integration team can run. Need to get them.
      • Still open
    • Don't think we need 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.