...
- Thanks to all the Logging committers for releasing 1.4.0 of logging-analytics project to support the Global JJB migration andPrudence Auis still working with LF on the Global JJB migration
- El Alto timeline
- Development started on July 14, images for early drop needs to be available by August 5 to ensure the delivery of early drop on August 19
- Early drop commitment
Jira server ONAP JIRA columns key,summary,type,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery Project = LOG and fixVersion = "El Alto Release" and status != Closed and type != Epic and labels = El_Alto_Early_Drop serverId 425b2b0a-557c-3c0c-b515-579789cceedb
- Early drop commitment
- Committed contents
Jira server ONAP JIRA columns key,summary,type,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery Project = LOG and fixVersion = "El Alto Release" and status != Closed and type != Epic serverId 425b2b0a-557c-3c0c-b515-579789cceedb
- Development started on July 14, images for early drop needs to be available by August 5 to ensure the delivery of early drop on August 19
- future of POMBA
Attendees
Notes
- Reviewed questions from Dave Williamsonon the Casablanca logging spec ONAP Application Logging Specification v1.2 (Casablanca)
- InvocationID - for asynchronous response should contain the InvocationID of the original request
- Prudence Auto document this at the meaningful spot on the spec page
- What should be the content for ServiceInstanceID?
- Team to come back with suggestions at the next meeting
- VirtualServerName to be deprecated in Frankfurt
- ContextName to be deprecated in Frankfurt
- InvocationID - for asynchronous response should contain the InvocationID of the original request
- Next meeting: August 6, 2019