...
- Status and Stucks
Current POMBA Dublin Stories (Logging Project) -
Current Code Inspections
- POMBA hourly healthcheck (CD deployment) - http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
- General Status
- Casablanca (Maintenance)
- POMBA 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 server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-778 Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-763
: For network resource only and should be split into Network Discovery and ND context builder.Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDNC-475
- Stories to be formally verified before closure:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-768 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-779 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-404
- Stories closed:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-765 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-762 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-938 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-937 Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-764
- 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 server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-852 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-916
(high)Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-917
- Bugs to be verified:
Jira showSummary true server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-807
(Verify in OOM fails, assigned back to design)Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-803 Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-808
- Bugs closed off since last meeting:
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-875 Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-897 Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-961 Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-935
- Casablanca (Maintenance)
- 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 server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-950 - 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 20Done
- 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
- J. Ram Balasubramanian will forecast demos as development progresses
- Should ping the automation team on POMBA usage
- Chesla to ping Brian.
- Note we need to be careful about breaking POMBA when in the middle of incremental updates, where OOM isn't yet done.
- 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://wiki.onap.org/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.
- Feature commitment Jan 17 → pushed one week. Jan 24th. (M1)
- Should look at milestones and ensure we are in good shape.
- Dublin