Notes

• Merge https://gerrit.onap.org/r/#/c/41939/ for https://gerrit.onap.org/r/#/c/41491/ to prep for test coverage work

• go over next milestone 19 April RC0 Release Planning#BeijngReleaseCalendar

• https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning.nodetail&selectedIssue=LOG-177&epics=visible&selectedEpic=LOG-169

• Future epic -  LOG-221: log compliance to support requestID/invocationID tracking - depends on finished java/python logging library first ClosedPreview

• Discussion with Shishir, Sanjay, Luke, Vitaly, Neal

  • external systems passing in a requestID (correlated to their BSS/OrderID) should be OK and not treated as a separate "outside of onap" usecase - as the incoming rest call will have the uuid header and be treated as any other onap component.

  • Report the entrypoint/exit (not necessarily carry/propagate) - need to discuss exactly how to do this in the spec (in the context of real OPS call graphs) - correlation id

  • Review MSB as a driver of this? Review DMaaP as well - in prep of C* arch subcommittee review - and security subcommittee

  • External systems need to conform to push/pull of requestID's in order to participate in ELK operations

• Shishir: Q: allow the ELK stack to be in its own namespace

  • and address resiliency/scaling of the current ELK stack - for production deployment - raise epic 

• Neal: if values.yaml log is set to false - does filebeat sidecars still come up - raise story on parameterizing this.

• Discuss filebeat changes? LOG-169: Document alternatives to the filebeat agent as etherial PV sidecar container for the ELK stackClosedPreview also in context of global config epic?

• Close out changes in Cass* changes for RC0 in ONAP Application Logging Specification v1.2 (Casablanca)

  • Try for 24th May - or RC0 19th 

• Retired attributes: see derived fields in ONAP Application Logging Specification v1.2 (Casablanca)#Deprecation

  • possibly audit on usage beyond core fields (partner, service, entity)

  • Review in the context of OPS production

  • Support operators with commercial stacks (Splunk) - in the context of deriving fields that will be removed above - the spec is independent but should be complete in the context of any ELK tech used

  • Sanjay: OPS requirements reflected in the spec - need early feedback from use of this spec in actual production - external systems above

• Need minimal scenario to exercise the spec - for arch subcommittee review

• Michael send out meeting for thu to below and onap-discuss - https://lists.onap.org/pipermail/onap-discuss/2018-April/009020.html

Attendees

Open