El-ALTO DISCUSSION ITEMS

1. SEC-COM  Open items
2. Secure communication
   1. Topic/feed
   2. CBS (dependency on Consul)
   3. Non-root container
   4. Security Vulnerability (review Dublin exception list and close)
3. CIA
4. S3P
   1. Documentation/Usability
   2. Performance test/bench-marking (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)
   3. Application logging consistency (Manageability)
   4. API Standardization (Usability)
5. Jenkins job alignment (moving to common template)
6. CSIT improvement
7. Platform components (security/csit/jjb)
8. Blueprint generator/Dmaap plugin integration
   1. (Topic standardization – pre-requisite)
9. SDK library integration (Except PRH/HV-VES)
10. Policy Integration for dynamic components
11. CBS library (remove consul dependency in lookup)
12. Docker tagging consistency
13. dcae Plugin compatibility in nexus

PM-Mapper

1. Control Loop flow onboarding/integration – SDC/CLAMP/Policy
2. VES Onboarding yaml registration binding with PM-Mapper configuration
3. VES o/p from PM-Mapper feeding into analytics services

BBS-EventProcessor

1. AAI interaction to use new DCAE SDK (1.1.5)
2. Control Loop flow onboarding/integration – SDC/CLAMP/Policy
3. PNF re-registration event handling should not involve BBS-ep (update of AAI service status) to be moved into SO
4. Move PRH -> BBS-EP notification structure to VES (This will not be required if #3 is accomplished)
5. Switch to AAF based topic
6. Stress testing with replicas
7. Support event filtering from generic topic (currently using cpe_authentication topic instead of statechange)
8. ci job change to use version.properties override

VES-Mapper

1. Tool translate/simplify smooks mapping from SDC model
2. Control Loop flow onboarding/integration – SDC/CLAMP/Policy
3. Consul update (via SDK library) to support periodic polling

SON-Handler

1. Support MS scaling
2. CBS SDK integration for periodic polling