Page History

Common Items

1. Secure communication  
   1. CBS
      1. Need AAF cert and deployment to be secure
      2. Consul interface will remain unsecure (dependent on OOM)
      3. CBS expose both secure/insecure to allow ServiceComponent transition
      4. SDK impact (client- java/python)
   2. DeploymentHandler->InventoryAPI
   3. Cloudify Interfaces  (Jack to assess impact
2. SEC-COM  Open items
3. Secure communication
   1. Topic/feed
   2. CBS (dependency on Consul)
   3. Non-root container
      1. Cloudify -  To be checked with DeWayne
      2. PolicyHandler, Deployment-Handler, CBS, Inventory
   4. Security Vulnerability (review Dublin exception list and close)
      1. Need to be assessed for all Service components  
4. CIA
   1. Cloudify - CentOS (post E release)
   2. Deployment-handler, CBS, Inventory, Policy-Handler
   3. Service components
      1. VES +   
5. 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)
      1. Platform - InventoryAPI , rest may be complaint (to be verified)  
   4. API Standardization (Usability)
6. Jenkins job alignment (moving to common template) across all services
7. CSIT alignment across all services
8. CSIT improvement
9. 1. Moving toward global-jjb for all platform components
   2. Moving toward global-jjb for all service components
10. CSIT alignment
    1. Platform CSIT (add blueprint into inventory, kick-off deployment through DH
    Platform components (security/csit/jjb
    1. )
11. Blueprint generator/Dmaap plugin integration (Topic standardization – pre-requisite)
    1. Enhance blueprint generator tool from Dublin to use Dmaap plugin and generated blueprint with associated properties by default
    2. Deploy components using new blueprint and validate dynamic topic/feed provisioning and configuration into services
       1. Depends on role (or identify setup in AAF - will need pre-configuration)
12. AAF integration
    1. Dynamic certificate generation
       1. Dependent on Dublin AAF work; to be checked with Jonathan  
13. SDK library integration (Except PRH/HV-VES)
    1. For service components
14. Policy Integration for dynamic components
    1. For service components to go through policy model/SDC onboarding
15. CBS Look up change CBS library (remove consul dependency in lookup)
    1. Library update required (python and java)
    2. Non SDK utilized components to be updated (VESCollector/RESTConf)
    3. Platform components to be verified  
16. Docker build and tagging consistency
17. dcae plugin DCAE plugin (k8splugin) compatibility in nexus
    1. Helm plugin in CCSDK address fixed this in R4.
18. Helm chart migration (platform componentsDashboard)
19. Python 3.x support (Cloudify, plugins + other dcae platform component; relates to DOC-419)
    1. Convert our code to be compatible with Python 3.x. (For example, using “import future” and making certain that loops work on iterators instead of lists when the API calls return iterators in 3.x.)
    2. Set up our plugin tox tests so that they are executed with both Python 2.7 AND Python 3.x.
       1. Upgrade all plugins (k8splugin/dmaap/policyplugin/relationship/postgres/helm) to support both 2.x and 3.x
       2. Verfiy all other platform components (CBS, PH, SNMP trap, Heartbeat)
20. Upgrade to new Cloudify version expected in June (compatible Cloudify upgrade to 5.0)
    1. Migrate if single base image   if multiple containers - will be assessed later.

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

...