Agenda
- Status and Stucks
- Technical Discussion
- Making the PTL Happy
...
- 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
Status: RED – Michael O'Brien will need to address what looks like some outages in the tool- 20181219: The kibana image I am using saturates after a couple months - reverted to a Sept 2018 image - running OK now - from my AWS account
- I lost my spot 64G vm last night to the market pricing - raised a new one this morning - results should be in in 2 hours
see
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key TSC-79 Code Block theme Midnight Issues with a couple pomba pods - are due to the fact that nexus3.onap.org has a 80x routing slowdown since the 17th - I have raised a proxy nexus3.onap.cloud for casablanca images and nexus4.onap.cloud for master images - but due to the speed - the pomba images won't be on the server until late friday (35 hour download of 40G) 19:43:27 onap onap-pomba-pomba-contextaggregator-d9f888c4-thtkn 0/1 Init:0/1 4 45m 10.42.41.97 ip-172-31-23-144.us-east-2.compute.internal <none> 19:43:27 onap onap-pomba-pomba-networkdiscovery-555f4cff77-m6s6t 1/2 CrashLoopBackOff 13 45m 10.42.10.178 ip-172-31-23-144.us-east-2.compute.internal <none>
- Something broken? Not giving update updates. Still broken as of last night.
- General Status
- Casablanca
- Bugs to be verified/closed:
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-805 - Still no luck in getting Brian to close this off
- Bugs to be verified/closed:
- Dublin
- Stories in progress (to be delivered this week):
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-404 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-517
- Stories to be formally verified before closure:
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 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-779
- Bugs in progress:
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-852 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-904
- 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-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-857 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-875 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-879
- Bugs closed off since last meeting:
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-814
- We are a little behind in our verification efforts and are hoping to make this up over the holidays while there's not so much other stuff going on!
- Stories in progress (to be delivered this week):
- Casablanca
- Technical Discussion
- 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.
- Logs now fixed, finding some additional bugs, but now easier to address. When resolved, can communicate.
- 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
- David Stangl has identified some timeframes where demos would probably make sense based on current forecast
- Data Dictionary & Network Discovery- Dec 20
- Technically that would be Dec 20.
- Also demo network Network discovery of VM info using native code as part of end to end flow.
- Note that admin credentials are needed in order to get all supported parameters.
- If non-admin privalenges, then fewer parameters shall be returned
- We should update the wiki to indicate which parameters require which credentials
- Data dictionary
- We should base error messages on what we know in the rules (resource and attribute name), instead of relying on meaningful text from the data dictionary
- 200/202 - attribute found and value valid
- 404 - attribute not found
- 4?? - attribute found but value not valid
- The type field is a good one to use in the data dictionary mock up. Name or uuid are unique so not great candidates for a data dictionary.
- We should base error messages on what we know in the rules (resource and attribute name), instead of relying on meaningful text from the data dictionary
- L2 Network data - beginning of Feb?
- Set a more specific date in January
- Network Audit - end of Feb?
- Data Dictionary & Network Discovery- Dec 20
- David Stangl has identified some timeframes where demos would probably make sense based on current forecast
- Added process page for new (or current) contributors:
- Integration Team discussion
- 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
- 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)
- Consider porting bugs into maintenance (add label for candidates)
- Dublin
- Should look at milestones and ensure we are in good shape.
- Feature commitment Jan 17
- Functionality freeze Feb 14
- API freeze is March 14th.
- Should look at milestones and ensure we are in good shape.
- 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