Copied from the AAI project - filling out today 20180309

Delta from R1

1. 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

   
   
   
2. The Multicloud team has committed a python RI under
3. 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

4. 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

5. we are

S3P Updates

1. Security
   1. AAI coreLogging RI:

      

      
      

   2. SONAR code coverage.  Plan is to get to >50% on all repos.
   3. 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 /EELFFilebeat 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

Deployment Configuration Alignment

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

API Updates