Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TitleResponsible

Status

Status
colourGreen
titleOpen

Status
colourBlue
titleDone

Last DiscussedStartNotes

Dublin Scope Planning


Status
colourYellow
titleIn Progress

20190108

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-707

OPNFV/ONAP Paris



https://ddfplugfest19.sched.com/ Tue-Thu

Clover Gambia on prior https://zoom.us/j/115579117 - 7 hours ahead

https://ddfplugfest19.sched.com/event/K1Gy/opnfv-clover-utilizing-cloud-native-technologies-for-nfv

Security badging

Status
colourYellow
titleIn Progress




Security Vulnerabilities

Status
colourYellow
titleIn Progress




Secure https endpoints


Status
colourGreen
titleOpen




LOG Formats/Files

Status
colourYellow
titleIn Progress



Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-178

Format compliance - working with AAI team

Status
colourYellow
titleIn Progress

2019010820181101

(+) 20190109
from aai team
https://wiki.onap.org/display/DW/2019-01-17+AAI+Developers+Meeting+Open+Agenda
"hector has discovered that the stress test jar (liveness probe?) in aai-cassandra is hammering the cpu/ram/hd on the vm that aai is on - this breaks the etcd cluster (not the latency/network issues we suspected that may cause pod rescheduling) "


#6 on 2018-12-20 AAI Developers Meeting around

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-376

Discussion with @Sanjay Agraharam and [~pau2882] on checking how cassandra is running on the vm and if debug levels are on should be verified

use labelling to split aai-cs and ls - no DaemonSet

Michael O'Brien to reduce core count for ls to 1 from 3

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-915

edited 2019-01-10 AAI Developers Meeting

for the 10th

AAI team - 2 types of logging AOP/non-AOP


Status
colourGreen
titleOpen


20181101#22 on 2018-12-20 AAI Developers Meeting
Logging requests from Vendors

Status
colourGreen
titleOpen



Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-877

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-876

#15,19 and 37 on SP priorities for Dublin

LOG Streaming compliance

Status
colourYellow
titleIn Progress



Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-487

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-487

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-852





20190108

discuss tick/tock logging spec behaviour - cassablanca implemented in dublin, dublin implemented in elalto

Log Checker
20190109
MIke to review with Horace
Search Guard

Status
colourGreen
titleOpen

20180109

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-494

spec changes for Dublin
2019010920190111520190109

Dublin spec changes for Elalto

environment name

release name

check mail for reply Michael O'Brien

Prudence Au proposal of renaming the log file name itself for the release ie: 3.0.0-ONAP - will discuss later for next week


Cluster logging behaviour
20190115

server name in clustered environments - I will add the details and the Jira right after this meet

see details on serverFQDN in

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-666

Code Block
themeMidnight
No cluster failover use case yet - just verifying static cluster fields - most fields are from the cloudify controller which is out of band of the the kubernetes cluster


    "ServerFQDN": "10.42.156.239",
    "host": "deployment-handler",
    "componentName": "deployment-handler",
    "RemoteHost": "10.42.0.1",",
    "ServerIPAddress": "10.42.156.239",

filter out DCAE

Image Added

Image Added

LOG ELK stack indexing/dashboards

Status
colourGreen
titleOpen




Casablanca 3.0.1 work until 10th Jan


Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-913

LOG openlab tenant devops

cluster creation/testing




We have 2 clusters a 1+4 and 1+13 used for testing deployments and running the vFW

Logging DevOps Infrastructure

Wiki edits, RTD review

Status
colourGreen
titleOpen



Requiring Updates, Merges or Marked Deprecated
Metric Streaming and Prometheus

Status
colourYellow
titleIn Progress

20181207

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-911
- experimental chart on http://secure.solar:30000/graph

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-773

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-861

work with Vaibhav Chopra

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-1504

Finish SO filebeat additions

Status
colourYellow
titleIn Progress

20181207

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1110

Finish LOG common charts

Status
colourGreen
titleOpen

20181207

James MacNider - bring in Prianka's common eLK charts and use them in Clamp, LOG, SDC, POMBA

https://gerrit.onap.org/r/#/c/64767/

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOOM-1276

Team Members Thank you and review

Status
colourGreen
titleOpen



Review last 4 weeks since 

LOG Meeting Minutes 2018-12-05


Status
colourYellow
titleIn Progress



TSC/PTL meet actions

Status
colourYellow
titleIn Progress



OOM transfer chart ownership to teams
LOG is part of poc

Status
colourYellow
titleIn Progress

20190107

Starting - will have a training session - will send out any meetings to onap-discuss

We may have the same symlink repo folder like we do for doc

OOM Deployment priority
base platform includes LOG

Status
colourYellow
titleIn Progress

20181207

Q2) priority of system level containers like the ELK stack - OOM has a common services JIRA - DMaaP, AAF - TODO get JIRA - make sure log is in this!

There is a cd.sh retrofit that sequences the pods in order for deployment stability - this will be phased out when tiered deployment comes in

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-898

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-326

https://gerrit.onap.org/r/#/c/75422/ via ONAP Development#WorkingwithJSONPath

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1067


k8s manifest or oom values.yaml
for docker tags - truth

Status
colourYellow
titleIn Progress

20190107

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyTSC-86

Nexus3 routing slowdown

Status
colourBlue
titleDone

20181222

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyTSC-79

20181217-22

LOG compliance diagram/exercise

Michael O'Brien

@Sanjay Agraharam

Status
colourYellow
titleIn Progress

20181205

Log Streaming Compliance and API

Sanjay - diagram FB must be split between using AOP and AOP+spec compliant - only this one should be green







Ongoing




CI/CD pipeline TSC poc

Status
colourYellow
titleIn Progress

20180107

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyTSC-25

LOG is part of this poc

...