...
Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
The following Presentations Apply to all the below non-functional requirements
View file name SecLog-TO-PTLs-v9.pptx height 250 View file name 2021-NOV-08_JakartaSECCOM-BestPrac-GlobalReqtsProposal_v3.pptx height 250
LOGS MANAGEMENT - PHASE 1: COMMON PLACE FOR DATA (REQ-441 ->REQ-1070)
R10 PRESENTATION:
| ITEM | DETAILS |
|---|---|
| Presentation | |
| Recording mp4 | |
| Audio only |
Key Contacts - Robert Heinemann fabian rouzaut Amy Zwarico Pawel Pawlak
Executive Summary - All ONAP applications should generate logs that can be collected by Kubernetes.
Business Impact - Improves the security posture of ONAP by enabling platform wide log collection to support downstream security analytics.
Business Markets - All operators, service providers and entities using ONAP.
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
LOG GENERATION: STANDARDIZED LOG FIELDS (REQ-1072)
R10 PRESENTATION:
| ITEM | DETAILS | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Presentation |
Jakarta Best Practice Proposal for Standardized Logging Fields - v2 | ||||||||||||
| Recording mp4 | |||||||||||||
| Audio only |
Key Contacts - Robert Heinemann fabian rouzaut Amy Zwarico Pawel Pawlak Byung-Woo Jun
Executive Summary - Standardize the fields that are logged across all ONAP applications.
Business Impact - Enhance ONAP’s security posture by positioning the platform to support advanced security analytics
Business Markets - All operators, service providers and entities using ONAP.
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Use Integration Standard Image (REQ-1073)
R10 PRESENTATION:
| ITEM | DETAILS | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Presentation |
| ||||||||||||
| Recording mp4 | |||||||||||||
| Audio only |
Key Contacts - Amy Zwarico Pawel Pawlak Sylvain Desbureaux Michał Jagiełło
Executive Summary - All ONAP applications must use an OOM standard image.
Business Impact - Improves the security posture of ONAP by providing more uniform ONAP deployments and automatically providing Java 11/Python 3 and eliminating unused versions of Java 8 and Python 2 in containers
Business Markets - All operators, service providers and entities using ONAP.
Funding/Financial Impacts - N/A
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.