Versions Compared

Old Version 22

changes.mady.by.user Gildas Lanilis

Saved on

compared with

New Version 23

changes.mady.by.user Gildas Lanilis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add process improvement day 2

...

  1. CI-CD: tools and processes
    1. Self-commit:
      1. automate Docker release version
      2. When time is critical (after RC0), allow PTLs to merge their change. This should allow be applicable to LF IT (CI-Management). 
    2. Increase CI-Management committers list
    3. CD: use of OPNFV Clover. Helen/Integration
    4. Packaging: Improve Docker images build: incremental versus rebuild everything, optimize docker package (size, time to download) (LF+Gary-Michael). Fact: 13 docker templates in Beijing. Focus first on the most downloaded docker images (sdc, so aai,...)
    5. Standardize the build jobs (benefit: ease to add dependency): LF.
    6. Daily Build: get back to daily build. Build only image on code changes. (once a week one full build).
    7. Partner with OPNFV: Clover project.
  2. Testing
    1. Improve time to get the full ONAP installed and started (currently 12 hours to debug): 1 hour for HC + 1 another hour for instantiate => 3 hours. Every project team effort. Better knowledge (training) of OOM + K8S + Helm
    2. Look at how to architect for testability, and debugability : Brian
    3. Love to plug a vFW-vDNS automated testing in the verify jobs: Not realistic for Casablanca. ( Gary to try)
    4. Manual way to build docker off on Verify job
  3. Release milestones
    1. Enforcement (respect and act upon automated results): (naming and shaming if criteria not met) on TLabs starting at M2 for Casablanca.(increase lab coverage over time, over release)
      1. HealthCheck: must not be broken for more than 48 hours
      2. Use case (VFW vDNS are automated): must not be broken for more than 48 hours
      3. CSIT: must not be broken for more than 48 hours
      4. Daily Build: must not be broken for more than 48 hours
      5. What for new projects?: HealthCheck after M4
      6. Perform testing Staging and Prod env: Gary.
  4. Labs and Infrastructure
    1. Resource (hardware): 96 GB ram * 10 (add to stop some daily test in Beijing)  (wind: 1.8 TB of ram total): Get data Stephen Gosh : Michael
    2. Increase uplink speed on windriver network (slicing 10 GB): 
    3. jenkins + nexus (currently 8GB is minimum): make it faster: LF. Jenkins fails cost minimum 1/2 days (for US). To bring this to the TSC→G Board.
  5. Packaging
    1. : 
    Packaging 
  6. Code Coverage and License scan
  7. Security
  8. SLA with LF: Idea Use JIRA to prioritize tasks.

...