Content Comparison

Copied template from the AAI project - filling out today 20180309Thank James Forsyth

Delta from R1

Started the library (for cassablanca)

Deliver python library 

Sonar must be above 50%, and address CLM

Future Cassablanca

1. We retrofitted the project as a Java project (jenkins, sonar)
2. We are developing a Java RI - planning completion for Cassablanca
   

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-95

   
   

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-118

   
   
   
3. The Multicloud team has committed a python RI under
   

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-161

4. The Multicloud team is retrofitting our repo for python
   

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-151

5. We are looking at alternatives to the sidecar for the filebeat container
   

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-169

6. we are looking at out of the box transaction tracing libraries like opentrace
   

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-104

7. we are looking to investigate logging in DCAEGEN2 - first step was to bring up the full DCAE stack
   
   

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-167

...

1. Security
   1. Logging RI:  
      

      Jira Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-877

      Jira Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-186

      98% for 

      https://bestpractices.coreinfrastructure.org/projects/1578

       

   2. SONAR code coverage.  Plan is to get to >50% on all repos.
   3. TODO: communicate with security team
   4. Nexus IQ scans: 
2. Scalability and Resiliency
   
   1. Working closely with OOM team (all Logging developers are also OOM contributors)
   2. Relying on kubernetes to manage Logging ELK stack resilience
3. Performance and stability
   
   1. Focus to this point has been security and scalability/resiliency.  We will participate in the integration team's performance testing
   2. ELK stack can meet soak test requirements
4. Manageablility
   1. Logging Filebeat sidecar refactor
      Possible sidecar refactor to use a deamonset in 

      Jira Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-169

   2. ELK stack can be instantiated in < 1hr - around 5-10 min as part of overall OOM deployment
5. Usability

...

1. We are aligning with the centralized configuration work in OOM
   
   

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-740

2. we are
3. 
   
   

API UpdatesAPI Updates

We currently have no logging library for Beijing - the stub work is in