Agenda

  • Status and Stucks
  • Technical Discussion
  • Making the PTL Happy

Notes

  • Status and Stucks
  • Technical Discussion
    • While the code is in, we are experiencing several issues with components starting correctly at the moment. Need to defer the demo.
      • containers not starting correct
      • Actively working; will demo next week.
    • Lobby integration team to get Pomba turned on.
      • Want them to run POMBA
        • Even if we are the only ones to look at initially.
        • Sharon will follow up once container issue is fixed.
        • Config maps are large, so they would need to use the workaround helm charts in order to deploy.
          • Install might work.  Upgrade won't.
    • Start talking Dublin next week.
      • Sharon to present.
      • Create a scope page with list of Epics
      • Should not need to go back to Architecture Committee for incremental improvements.
    • Gildas shut down something so jobs are not running in Dublin yet
    • When cut branch? 
      • Early would be good. Need to cut release
      • Give image stuff to Brian's team for manifest.
      • Will need to double merge, so wait until ready.
  • Making the PTL Happy
    • Today is M4
    • In good shape with with a couple caveats
      • Some open bugs
      • Vulnerability should be looked at
      • Can take an action to resolve anything they find.
    • RC0 is the next milestone.

1 Comment

  1. JIRA board todo: 

    LOG-678 - Getting issue details... STATUS

    LOG-224 - Getting issue details... STATUS

    vulnerability JIRA

    license jira


    left out workarounds/progress for pomba in R3 Logging Security/Vulnerability Threat Template

    see stories closed in C and pushed to D for pomba in Logging Casablanca M4 Deliverable for Code Freeze Milestone Checklist Template

    pod status - as healthcheck in windriver does not yet list failed pods  - but my CD system does

    this is from a system only running pomba

    update: mvn 33/35 is most likely the issue here - Prudence Au has iterated

    NAMESPACE     NAME                                                    READY     STATUS             RESTARTS   AGE
    kube-system   heapster-6cfb49f776-nnd2l                               1/1       Running            5          84d
    kube-system   kube-dns-75c8cb4ccb-84tw5                               3/3       Running            16         84d
    kube-system   kubernetes-dashboard-6f4c8b9cd5-qq94f                   1/1       Running            5          84d
    kube-system   monitoring-grafana-76f5b489d5-7r5vb                     1/1       Running            5          84d
    kube-system   monitoring-influxdb-6fc88bd58d-w424h                    1/1       Running            5          84d
    kube-system   tiller-deploy-8b6c5d4fb-sgkqd                           1/1       Running            1          22h
    onap          onap-pomba-aaictxbuilder-56d98d7649-ljqqh               1/2       CrashLoopBackOff   4          11m
    onap          onap-pomba-contextaggregator-765844bbc9-2slnt           1/1       Running            0          11m
    onap          onap-pomba-data-router-97fcf9597-jctxl                  1/1       Running            5          11m
    onap          onap-pomba-elasticsearch-6c8d7bb4f9-98t2p               1/1       Running            0          11m
    onap          onap-pomba-kibana-d76b6dd4c-vcvm6                       0/1       PodInitializing    0          11m
    onap          onap-pomba-networkdiscovery-85d76975b7-rv24v            1/2       CrashLoopBackOff   4          11m
    onap          onap-pomba-networkdiscoveryctxbuilder-c89786dfc-qzk6c   1/2       CrashLoopBackOff   4          11m
    onap          onap-pomba-sdcctxbuilder-5bc9cdcd77-vb9wh               0/1       CrashLoopBackOff   5          11m
    onap          onap-pomba-search-data-65c86fbcf9-vkq2b                 2/2       Running            1          11m
    onap          onap-pomba-servicedecomposition-557dd9d669-7rrz5        1/2       CrashLoopBackOff   4          11m
    onap          onap-pomba-validation-service-5cf47bcbf-cgxx2           1/1       Running            0          11m
    
    
    later
    onap          onap-pomba-aaictxbuilder-56d98d7649-ljqqh               1/2       CrashLoopBackOff   8          27m
    onap          onap-pomba-contextaggregator-765844bbc9-2slnt           1/1       Running            0          27m
    onap          onap-pomba-data-router-97fcf9597-jctxl                  1/1       Running            5          27m
    onap          onap-pomba-elasticsearch-6c8d7bb4f9-98t2p               1/1       Running            0          27m
    onap          onap-pomba-kibana-d76b6dd4c-vcvm6                       1/1       Running            0          27m
    onap          onap-pomba-networkdiscovery-85d76975b7-rv24v            1/2       CrashLoopBackOff   8          27m
    onap          onap-pomba-networkdiscoveryctxbuilder-c89786dfc-qzk6c   1/2       CrashLoopBackOff   8          27m
    onap          onap-pomba-sdcctxbuilder-5bc9cdcd77-vb9wh               0/1       CrashLoopBackOff   10         27m
    onap          onap-pomba-search-data-65c86fbcf9-vkq2b                 2/2       Running            1          27m
    onap          onap-pomba-servicedecomposition-557dd9d669-7rrz5        1/2       CrashLoopBackOff   8          27m
    onap          onap-pomba-validation-service-5cf47bcbf-cgxx2           1/1       Running            0          27m


    this is from a 244g single vm with a 42/44 healtcheck

    http://jenkins.onap.info/job/oom-cd-master/3497/console