Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Agenda

  • address backlog of LOG Meeting Minutes 2018-11-13
  • Resource commitments
    • Architecture/requirements - covered
    • Implementation
    • project overhead (builds/deploy/jobs/security)
  • Overall Dublin plan - Logging Dublin Scope
    • Infrastructure
      • Log streaming adjustments (see Log Streaming Compliance and API)
        • with
        • partial
        • without
      • Security
        • Security (REST and HTTPS transport)
          • Definitely need to use search guard  LOG-494 - Getting issue details... STATUS
        • Vulnerability/PEN testing
    • Log format/schema adherence
      • We have a good spec from Casablanca - we will be implementing this in Dublin - see Active Logging Specifications
      • ecomp to onap
      • openo to onap
      • new components
    • Use cases
      • ops
      • transaction tracing (passing, failure of VNF deployment for example)
    • Log library use (optional)
      • As we know - each pod will need to deliver logs in one of at least 3 ways, manually, non-AOP library (like AAI), AOP library (like portal/sdk, or our reference)
      • retrofit/augment our example to use portal, adjust the library if required, support adoption onap wide

  • TODO



Notes

  • No labels