Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Copied template from the AAI project - Thank James Forsyth

Delta from R1

Started the library (for cassablanca)

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-118

Deliver python library 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-151
 in the logging repo via the Multicloud team (Ramki KrishnanShankaranarayanan Puzhavakath Narayanan, and Sastry Isukapalli interested). Note: Sastry Isukapalli has an implementation based on ECOMP's EELF for Python and can share notes and code from that.

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
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-95

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-118


  3. The Multicloud team has committed a python RI under
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-161
  4. The Multicloud team is retrofitting our repo for python
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyMULTICLOUD-151
  5. We are looking at alternatives to the sidecar for the filebeat container
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-169
  6. we are looking at out of the box transaction tracing libraries like opentrace
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-104
  7. we are looking to investigate logging in DCAEGEN2 - first step was to bring up the full DCAE stack

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-167

...

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-154

  1. Security
    1. Logging RI:  
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyOOM-877
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyLOG-186

      98% for 

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

       Badge level for project 1578 is in_progress

    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
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyLOG-169
    2. ELK stack can be instantiated in < 1hr - around 5-10 min as part of overall OOM deployment
  5. Usability

...