Page History

Copied from the AAI project - filling out today 20180309

Delta from R1

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

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-95

   
   

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-118

   
   
   
3. The Multicloud team has committed a python RI under
   

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-161

4. The Multicloud team is retrofitting our repo for python
   

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key MULTICLOUD-151

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

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-169

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

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-104

7. we are

S3P Updates

1. Security
   1. Logging RI:

      Image Removed99% for 

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

   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 Filebeat sidecar refactor
      Possible sidecar refactor to use a deamonset in 

      Jira
      server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-169

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

...