Agenda
- address backlog of LOG Meeting Minutes 2018-11-13
- Committer/PTL votes
- PTL role is up for election - any committer can run - details on last election - I will post a page for Dublin for next week
- Committer list review
- Lee (LOG)
- Avdhut (LOG)
- Luke (LOG)
- Michael (LOG/POMBA)
- Prudence (LOG/POMBA)
- Geora (POMBA)
- Shane has left ONAP (pomba)
- room for 2-4 more committers (Logging - Lorraine, Dave, Sanjay? and Pomba - Pierre?)
- PTL role is up for election - any committer can run - details on last election - I will post a page for Dublin for next week
- Resource commitments
- Architecture/requirements - covered
- Devops (build, jobs, s3p - R3 Logging Security/Vulnerability Threat Template and https://jenkins.onap.org/view/logging-analytics/job/logging-analytics-maven-clm-master/)
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-666
- Implementation
- project overhead (builds/deploy/jobs/security)
- create 6+ new repos for python and java reference implementations
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-871 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-860
- Overall Dublin plan - Logging Dublin Scope
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-870 - 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
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-494
- Definitely need to use search guard
- Vulnerability/PEN testing
- Security (REST and HTTPS transport)
- Log streaming adjustments (see Log Streaming Compliance and API)
- 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