Urwashi, Hi, the Amsterdam repo is essentially deprecated and has an elk stack under the log pod – all deployment code is in the oom repo as usual. https://git.onap.org/oom/tree/kubernetes/log?h=amsterdam use the following script to bring up the system old or new. https://git.onap.org/logging-analytics/tree/deploy/cd.sh
I would advise using Beijing or master as a lot of changes/fixes have went in since Amsterdam – including the full containerization of DCAE from the hybrid deployment of amsterdam. An example of a recent project that implemented the current filebeat (the filebeat/logstash architecture will likely be modified in Casablanca) config is CLAMP https://git.onap.org/oom/tree/kubernetes/clamp https://jira.onap.org/browse/CLAMP-170 https://gerrit.onap.org/r/#/c/48961/ https://wiki.onap.org/display/DW/Logging+User+Guide /michael From: Urwashi Saraswat Sent: Tuesday, June 12, 2018 2:12 PM To: Michael O'Brien <[email protected]> Cc: [email protected] Subject: ELK stack deployment for onap Amsterdam HI Michael, Do you have deployment for ELK stack in onap Amsterdam which has new filebeat configuration. ? This is regarding the onap logging project Thanks Urwashi This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
