Page Comparison

...

Status and Stucks

Current POMBA Dublin 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

General Status

Casablanca (Maintenance)

NothingPOMBA bug in the email chain - 915, 932, 950

Task	LOG-915	Reduce Logstash core limit to 1 from 3 until LOG-LS and AAI-CS perf issue on the same VM is determined	High	In Progress	Not POMBA
Bug	LOG-932	pomba-data-router pod does not come up in Casablanca MR	High	Closed	Closed in Dublin or Casablanca?
Bug	LOG-950	periodic pomba-pomba-networkdiscoveryctxbuilder pod in CrashLoopBackoff due to timing	Medium	Submitted	Assigned to Jmac, to look at

Note we said we were only fixing absolutely critical issues in Casablanca, are these them?
- Action Yong. Will reply later today

Dublin
- Tasks to be closed off (just a technicality):
- Stories in progress: All 3 of them will be delivered by Feb-08.
  - 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-778
  - 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-763
  - Jira Legacy
    server System Jira
    columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key SDNC-475
    : For network resource only and should be split into Network Discovery and ND context builder.
- Stories to be formally verified before closure:
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-768
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-765779
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-762404
- Stories closed:
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-938765
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-937762
  - 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-764938
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-779937
  - 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-404764
- Bugs to enter:
  - Latest security scan results show ~9 medium issues that should be recorded (but aren't severe enough to merit immediate work).
- Bugs entered in last week:
  - none
- Bugs in progress:
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-852
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-803
    (Verify in OOM fails, assigned back to design)
    Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-916
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-917
    (high)
- Bugs to be verified:
  - Jira Legacy
    showSummary true
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-935
    (high)
  Bugs to be verified:
  - 807
  - Jira Legacy
    showSummary true
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-807803
    (Verify in OOM fails, assigned back to design)
  - 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-808
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-875
- Bugs closed off since last meeting:
  - 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-821875
  - 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-804897
  - 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-713961
  - 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-714935

Technical Discussion
- Note we need to be careful about breaking POMBA when in the middle of incremental updates, where OOM isn't yet done.
  - Pulling OOM back into the project will fix this. This is currently not planned, and requires resources from OOM project to do this, so defer.
  - both master and any MR
  - Jira Legacy
    server System Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key LOG-
    809
Technical Discussion
- Note OOM changes should be done when manifest changes are done. Should not wait for integration team to do this work for us.
  - We will have to do this for Dublin in two months.
  - Create task to track J. Ram Balasubramanian
    - Done.
  - Docker version update
  - Moving from snapshot to proper release is part of workflow.
    - If POMBA thinks they will have no more changes, they can do this earlier
  - Sharon to create task for this for El Alto backlog.
- Organizing Models and Swaggers between releases
  - Basic navigation should take us to current
  - It should also be possible to get Casablanca information
  - Wiki needs some reorganization
- Consider demo schedules
  - J. Ram Balasubramanian will forecast demos as development progresses
    - ~~Data Dictionary & Network Discovery- Dec 20~~
      - ~~Done~~
    - L2 Network data - beginning of Feb?
      - Set a more specific date in January
      - Let's demo with some rules. So probably Feb 14th or 21st.
      - If we want validation run on new data, then Feb 21st makes more sense
    - Additional enhancement - March 21st
- Should ping the automation team on POMBA usage
  - Chesla to ping Brian.
Making the PTL Happy
- Dublin
  - Should look at milestones and ensure we are in good shape.
    - Feature commitment Jan 17 → pushed one week. Jan 24th. (M1)
      - Prudence is supporting Michael for this activity.
      - https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Logging+Dublin+Deliverables+for+Planning+Milestone+Checklist+Template
      - https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Logging+Dublin+M1+Release+Planning
    - Functionality freeze Feb 14
      - Not sure if this was impacted by M1 slip .- nope - still the 14th
    - API freeze is March 14th.

Versions Compared

Old Version 1

New Version Current

Key