...
| Jira No | Summary | Description | Status | Solution | Filebeat containers and potential to be used for log aggregation | A lot of Filebeat containers as part of infrastructure healhchecks. Filebeat is a side container for logs aggregation and potentially could be used for prototype or implement logs aggregation for stdout and stderr. It looks there is broad coverage accross ONAP project that has this Filebeat container already. OOM team do not want to manage sidecars that would be used to collect logs. There are at least 30 Filebeat containers with old java or python versions. | ongoing | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
To figure it out how many Filebeat containers are in ONAP projects. Bob to synch with Byung. Bob to join Integration team meeting on WednesdayONAP Logging Architecture & design | Byung presented ONAP logging architecture:
In there (page 5), presented an old view of ONAP logging architecture (leveraging filebeat, logstash, others) Option A preferred. There are some reasons we don't want to use the architecture (filebeat not necessary): 1) Since the log sidecar is no longer favored by OOM and others after the global requirement REQ-441 - all ONAP applications generate log events to STDOUT/STDERR; so logging side car is no longer desired 2) LogStash has some license issue that is why Fluentbit (on each node) and FluentD as aggregator proposed 3) new architecture simplifies ONAP logging Diagrams are editable in Gliffy. Sylvain shared info on Orange docuementation: https://gitlab.com/Orange-OpenSource/lfn/infra/kubernetes_cofor gating llection | ongoing | Resources supporting this project are welcome. To elaborate how to assure security for Fluenbit and FluenntD communication - maybe service mesh proxy could be used. Byung will be back from PTO in January. | |||||||||||||||||||||||
| Synch of versions with OOM and Integration teams | We have a policy to recommend latest stable version. Apparently some difficulty raised by Sylvain to implement 1.20+ Kubernetes. From process perspective we should agree on versions with Integration and OOM per each release and collect feedback. Versions synchronization started with Java and Python versions synch. Impact analysis is important to run but it takes time and it is easier to do the upgrade. Respnsibility should be on OOM or Integration team. The goal is to have everyone aware of the versions that should be used per release. Issue with using 1.19 K8s is that it is not supported by the community. Centos 8 will be deprecated in December'21. for the support 7.x is better to use as it will be available until 2024. Huge code change in IPv6 in K8s between 1.19 and 1.20 in K8s. | ongoing | Muddasar to check the link: Database, Java, Python, Docker, Kubernetes, and Image Versions Sylvain to be contacted for 1.19 version end of support. | PTL meeting update |
| ongoing | Topics proposals to be reviewed at the next SECCOM - automation for Release Notes could be a topic to propose. | ONAP code quality improvement | E-mail exchanges with Toine by e-mail. Meeting done with Thierry, Kevin and Jess - new job created in gerrit CPS sonar verify, not for the quality can be added. | ongoing | Test with CPS to be organized with Toine and Kevin. Voting by TSC to change quality gate value. | Software BOMs: | SBOMs to be discussed on Thursday. Ongoing follow-up with Krzysztof. | ongoing | Ticket to be opened and work with LFN IT, build BOM and present it to PTLs. | TSC meeting this Thursday | We present non functional requirements for Jakarta release. | ongoing | Sonarcloud dashboard has gone and no longer supported! | Tony is checking alternatives. Poor documentation of APIs. | ongoing | SonarCloud representatives in France could be contacted (via Jessica) if neededteams |
| ongoing | Sylvain to get a monthly e-mail on possible move towards 1.22 and we would start on 1.21.2 | |
| SECCOM presentations for incoming DDF (January). |
| ongoing | Proposals to be reviewed next SECCOM (last minute) | |||||||||||||||||||||||
| TSC voting process for submitted requirements | Deadline is on 2nd of December. | ongoing | No action required on our side. | |||||||||||||||||||||||
OUR NEXT SECCOM MEETING CALL WILL BE HELD ON 23rd30th OF NOVEMBER'21. Part 1 | Synch with OOM (Sylvain) ONAP Logging Architecture & design by Byung. SECCOM proposal for DDF:
Interproject proposals:
| |||||||||||||||||||||||||
SECCOM MEETING CALL WILL BE HELD ON 30th OF NOVEMBER'21. Part 2 | Request from the Policy project group (Ramesh and Liam) for the ‘cluster-admin’ permission on one of their helm charts in OOM for automate helm chart installation for microservice. |
...