Team, We decided to keep the logging meeting for now at the same 11EDT GMT-4 timeslot. If there is a problem with the original bridge we can use my zoom as an alternate
Tomorrow’s meet https://wiki.onap.org/display/DW/LOG+Meeting+Minutes+2019-03-19 https://zoom.us/j/519971638 alternate : https://zoom.us/j/7939937123 Note: there is a scheduled POMBA demo for the 26th March timeslot Last 2nd week’s meet https://wiki.onap.org/display/DW/LOG+Meeting+Minutes+2019-03-05 Attendees Luke Parker<https://wiki.onap.org/display/~lparker> , Prudence Au<https://wiki.onap.org/display/~pau2882> , Michael O'Brien<https://wiki.onap.org/display/~michaelobrien> , Sanjay, Lorraine Welch<https://wiki.onap.org/display/~lorraineawelch> Agenda § Meetings every 2 weeks now - next meeting the 19th § Need to accomidate Luke Parker<https://wiki.onap.org/display/~lparker> - who is up at 3 am right now in Australia - will be 1 in the morning until April - then 2am § ideas: Better to be up at 1-3 than 8am - keep at 11 for now § For NA - stays at 11 - but I will verify if we are on UTC § DST is coming this weekend - we should agree on the meeting time - Luke does not go DST for 3 more weeks § Michael: status no progress on logging related jiras involving dublin scope (code/tech) last week § Passed M2 § Discussed in TSC and PTL meets - issue related to manifest vs k8s values.yaml overrides for casablanca and CMR releases - § <https://jira.onap.org/browse/TSC-86> [https://jira.onap.org/secure/viewavatar?size=xsmall&avatarId=10303&avatarType=issuetype] <https://jira.onap.org/browse/TSC-86> TSC-86 - Lock down docker image tag name source of truth - oom values.yaml or integration repo manifest - A: both but manifest is the source SUBMITTED § TSC 2019-02-28<https://wiki.onap.org/display/DW/TSC+2019-02-28> § <https://jira.onap.org/browse/OOM-1560> [https://jira.onap.org/secure/viewavatar?size=xsmall&avatarId=10303&avatarType=issuetype] <https://jira.onap.org/browse/OOM-1560> OOM-1560 - dmaap-dr-node deployment is failing - casablanca SUBMITTED § In architecture review for M3 - (Addressed comments) Logging Dublin M3 Architecture Review<https://wiki.onap.org/display/DW/Logging+Dublin+M3+Architecture+Review> § Working more for OOM lately - Created RKE script to replace rancher - pending work is to test HA - https://gerrit.onap.org/r/#/c/79067/ for <https://jira.onap.org/browse/OOM-1670> [https://jira.onap.org/secure/viewavatar?size=xsmall&avatarId=10316&avatarType=issuetype] <https://jira.onap.org/browse/OOM-1670> OOM-1670 - RKE installation script and reference HEAT yaml/env/sh SUBMITTED § Assisting with ONS April demo prep - 2 or more ONAP installations working together - one as an edge cloud § Focused on onap devops - primarily for 2 customers deploying ONAP § 5G training next week § April 3-5 ONS work § k8s infrastructure and § Logging will be a part of the demo - we will show the kibana logs during a vFW operation in an i-frame for the master and edge ONAP deploys § PTL position is open - let me know if anyone would like to take it. § Also quickly discussed idea of rolling LOG into OOM - should revisit § Pending committer for pomba - Committer Request for Trevor Tait<https://wiki.onap.org/display/DW/Committer+Request+for+Trevor+Tait> and Committer Request for Pierre Rioux<https://wiki.onap.org/display/DW/Committer+Request+for+Pierre+Rioux> - will send out reviews once stats are completed - TSC review will be needed § TODO I need to check MSB issues on onap-discuss - § Spondon - import the dashboard - fix the one on the wiki - Lorraine Welch<https://wiki.onap.org/display/~lorraineawelch> export to json first ONAP Culprit Locator<https://wiki.onap.org/display/DW/ONAP+Culprit+Locator> § Lorraine Welch<https://wiki.onap.org/display/~lorraineawelch> question about changing the index for the db (Grafana for example) - @Timestamp timestamp for example - TODO - merge the 2 indexes - § Q) Sanjay: (opentracking related - picking up errors on stdout (err, out) § how: § (also review from 2 weeks ago - Lorraine Welch<https://wiki.onap.org/display/~lorraineawelch> System.out standardout - review in terms of not using a hardcoded file appender - in terms of syslogs · see https://12factor.net/logs) · log retention on pod failure - those not mapped to PVs - including the current EmptyDir link between the sidecar - etherial PV - logs only end up in the elk stack · Look into PV/PVC structure for log retention instead of the default emptydir · https://git.onap.org/logging-analytics/tree/reference/logging-kubernetes/logdemonode/charts/logdemonode/templates/deployment.yaml#n114 · see PV/PVC example . logs can go to the /dockerdatanfs) · https://git.onap.org/oom/tree/kubernetes/portal/charts/portal-mariadb/templates/deployment.yaml#n84 · Topic: File retention · Q: rotation schedule, size of retention - what role does the PV on the ELK stack play compared to the individual source pod PVs · @Luke's example - discuss with Mike Elliott<https://wiki.onap.org/display/~melliott> - review a pending upstream contribution · https://git.onap.org/logging-analytics/tree/reference/provider/helm/logback/chart/resources/logback.xml#n10 · variables set in · https://git.onap.org/logging-analytics/tree/reference/provider/helm/logback/chart/values.yaml#n14' · Review any issues with multiple providers in SDNC and APPC · Lorraine Welch<https://wiki.onap.org/display/~lorraineawelch> check https://www.loomsystems.com/blog/single-post/2017/01/30/a-comparison-of-fluentd-vs-logstash-log-collector /michael This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16193): https://lists.onap.org/g/onap-discuss/message/16193 Mute This Topic: https://lists.onap.org/mt/30503768/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
