LOG Meeting Minutes 2019-11-19

Owned by Prudence Au
Nov 19, 2019
1 min read

Agenda

  • Kevin Smokowski committer promotion request has been submitted to the TSC on Nov 17, 2019 

  • ONAP considered the logging project not participated in the Frankfurt release as we didn't meet the M1 requirements

  • Draft Frankfurt spec ONAP Application Logging Specification v1.3 (Frankfurt) - Continuation

    • We owe Steve Smokowski an answer for his question on August 30, 2018 (Response Code and Response Description) and September 4, 2018 (Invoke and Invoke-return).
      - Oct 29, 2019 Sanjay and @Dave Williamson to talk with the AT&T Ops team for the use of Response Code and Response description.
      - Nov 5, 2019 AT&T Ops team is good with Response Code and Response Description are must for error case only and since these are mandatory fields, a default value will be suggested to indicate no issue found.
      - Nov 5, 2019 Action: Prudence to update the description for these 2 fields

    • Still need to address the issue with 2 test environments and only 1 log instance?  @Dave Williamson reported it on December 6, 2018
      - Oct 29, 2019 Sanjay and @Dave Williamsonto investigate.  This might be resolved by the tenant isolation feature.
      - Nov 5, 2019 it was confirmed that the metadata field (environment) in the header resolved the issue 
      ----------------------------------------------------------------------------------------

    • Any feedback on Kevin Smokowski's comment on August 6, 2019 regarding the use of User-Agent as PartnerName?

    • Any feedback on Kevin Smokowski's comment on August 5, 2019 regarding the value of ServerIPAddress in the case of docker & kubernetes deployment?

    • Any updates needed for TargetEntity and PartnerName?  Mentioned on August 15, 2019 (a conversation between Dave and Kevin)

    • Any feedback on composite RequestID or NOT composite RequestID (from October 2, 2019)?

  • This will be the last meeting hosted by Prudence

Attendees

Notes