...
- 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):
Move to Dublin since this is where the work was actually doneJira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-456 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-470 - Move to Dublin since this is where the work was actually done
- Stories in progress:
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-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
- Stories to be formally verified before closure:
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 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
- 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:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-935 - This is having a big impact
- Have found and fixed some issues, but not resolved
- Prudence will help resolve, along with those already working it
- high priority item
- Bugs in progress:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-852
(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 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 server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-807 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 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-875
- Bugs closed off since last meeting:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-857
- Tasks to be closed off (just a technicality):
- 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.
- Did we miss these in Casablanca?
- Pomba data router missed this yes, resulting in a last minute change
- Gary from Integration had to do it.
- History: A&AI team updated data router version, but did not update all uses. This is not a normal thing then.
- Pomba data router missed this yes, resulting in a last minute change
- We will have to do this for Dublin in two months.
- Create task to track J. Ram Balasubramanian
- Not sure if done yet.
- 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
- Create task to track J. Ram Balasubramanian
- Did we miss these in Casablanca?
- 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
- Integration Team discussion
- When we know the Openstack/network discovery info will work in ONAP, we shall reach out to Brian and the Integration team again.
- Logs now fixed, finding some additional bugs, but now easier to address. When resolved, can communicate.
- Sent an email to Brian to let him know that embedded openstack support is now available for use
- 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.
- When we know the Openstack/network discovery info will work in ONAP, we shall reach out to Brian and the Integration team again.
- 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
- Network Audit and/or additional enhancement - end of Feb/mid March?
- Data Dictionary & Network Discovery- Dec 20
- J. Ram Balasubramanian will forecast demos as development progresses
- 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
- ONAP Casablanca Maintenance? Michael O'Brien as of now Logging and Pomba are not in 3.0.1-ONAP - only critical fixes should go in if we have any
- Done from our perspective
- Consider porting bugs into maintenance (add label for candidates)
- Only high and highest ones. Ones that impact other components, prevent POMBA from launching or the audit to even start.
- Note the following date to submit bug fixes into Casablanca - Dec 10 (M1), Jan 10 (Docker Release Image), Jan 24 (Release Notes)
- Supposed to go out today, but Michael doesn't think we are not ready. There are 5 OOM patches, including one for POMBA.ensure you paste results of a CD deploy when creating code inspection. Don't rely on integration team.
- kubectl get pods -n onap health check
- ONAP Casablanca Maintenance? Michael O'Brien as of now Logging and Pomba are not in 3.0.1-ONAP - only critical fixes should go in if we have any
- Ensure that the ONAP wiki is complete and accurate for deployment instructions
- including undercloud instructions for the cluster
- single VM targeting for developers versus ONAP official instructions
- Will continue to update wiki as best information is available
- Dublin
- Should look at milestones and ensure we are in good shape.
- Feature commitment Jan 17 → pushed one week. Jan 24th.
- 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.
- Should look at milestones and ensure we are in good shape.