...
- 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)
- Nothing
- 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
: For network resource only and should be split into Network Discovery and ND context builder.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
- 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-765 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-762 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-938 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-937 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-764 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-779 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-404
- 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
(Verify in OOM fails, assigned back to design)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-916
(high)Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-917
(high)Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-935
- Bugs to be verified:
Jira Legacy showSummary true server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-807 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-821
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-804 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-713 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-714 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-809
- Casablanca (Maintenance)
- 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
- This is covered. We can stop tracking this here.
- Create task to track J. Ram Balasubramanian
- We will have to do this for Dublin in two months.
- 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.
- Additional enhancement - March 21st
- Data Dictionary & Network Discovery- Dec 20
- J. Ram Balasubramanian will forecast demos as development progresses
- Should ping the automation team on POMBA usage
- Chesla to ping Brian.
- Note OOM changes should be done when manifest changes are done. Should not wait for integration team to do this work for us.
- 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.
- 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