Former user (Deleted)

cl664y@att.com

Yang Xu

Amy Zwarico

Rich Bennett

Casablanca Maintenance Release Dashboard: https://jira.onap.org/secure/Dashboard.jspa?selectPageId=11102

Integration Blocker(s): Casablanca Maintenance Release Integration Test Blocking Issues

Integration Status: Casablanca Maintenance Release Integration Testing Status

One integration issue to discuss is external repo usage (dockerhub) and potential problem of image tag "latest"

Release note to be updated no later than January 30th, 2019 EOD; Sign-Off/TSC Review on 1/31

cl664y@att.com

Former user (Deleted)

Rich Bennett

• Review your final commitments on the centralized Dublin wiki page by 1/30 11am CET/5pm EST: https://lists.onap.org/g/onap-tsc/message/4520
• Provide your inputs on remaining items identified during the review and send a note to Jim/myself when it is done
• Assessment on CSIT moving to OOM
• Migrate Docker image releases from Nexus3 into DockerHub (Architecture Independence) by Dublin M4 (To be confirmed based on impact assessment)
  Presentation to PTLs is required on 2/4 then impact assessment to be performed with the PTLs.
  Part of CIA project - Adolfo
  
• oParent Integration - still part of your commitments
• Document as you Code:
  
  • Send feedback to Sofia about Documentation Plan Proposal prior the TSC call (1/31)
    
  • 46 items already committed out of 107
    

    type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due

    Loading...

    Refresh

          + Videos for the use cases/functional requirements

• Please update any risk/issue (if any):  Dublin Risks
• TSC Sponsor?

cl664y@att.com

Former user (Deleted)

• Helm Chart Transfer: 4 projects have been identified for trial: A&AI, Log, Policy, APPC and Clamp. Mike Elliott will work with PTL to gather/transfer knowledge and create training materials. Training to be done the week of Jan 14 and PTL to provide their commitment or not by M1 on Jan 24.
  <1-7/2019>: Work in progress. Schedule might shift to another week. Michael will follow-up with Mike. Training will be open to everybody. The objective is that each team will take over the management of their Helm Charts.
  <1-28/2019>: Meeting is organized on 1/29 with LF. Training will be organized early in February. Additional information on the next PTL call (2/4)
  
  
• Oom values.yaml or integration repo manifest ( TSC-86 - Lock down docker image tag name source of truth - oom values.yaml or integration repo manifest - A: both but manifest is the source Submitted )

  if not covered - see TSC 2019-01-10

  Quick discussion on nailing down whether we need a yaml override of the deployable

  docker image tags in the oom repo (understanding is no) - with the integration docker manifest

  (manifest is currently a copy of the oom values.yaml tags - not the reverse)

  If not - then we need a documented procedure wiki/RTD on running a derived values.yaml override for the entire system before deployment

  AAF is only an example here

  https://git.onap.org/oom/tree/kubernetes/aaf/charts/aaf-service/values.yaml?h=casablanca#n28

  image: onap/aaf/aaf_service:2.1.8

  drives

  https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv?h=casablanca#n11

  onap/aaf/aaf_service,2.1.8
  
  

  <1-7/2019> Integration team to document the procedure.<01/13/2019> Answer from Integration team: docker manifest under integration repo is the source of truth, and is used by Integration team to override OOM values.yaml when deploying ONAP in Openlab. See the instructions at the bottom of page https://onap.readthedocs.io/en/casablanca/submodules/integration.git/docs/onap-oom-heat.html#onap-oom-heat-template
  <1-21/2019> Procedure should include Timers, dependencies, etc.
  just need to define all the --set and -f overrides like the following
  
  sudo helm deploy onap local/onap --namespace $ENVIRON -f $DISABLE_CHARTS_YAML  -f $DEV0_YAML $APPENDABLE_ENABLED_FLAGS --verbose

  <1-28-2019>: Document how to handle the latest 3rd party image from github.
  
  

• WindRiver Lab Management - Please provide feedback to Stephen Goochno later than January 31st, 2019 if you need to keep your tenant space, VMs: user-usage.txt
  
  
• (Catherine by 1/28): Need to follow-up with LF Legal concerning "Spring Boot" vs "JAX-RS"- any licensing preference? Spring Boot is under the Apache-2.0 license
  
  
• (PTLs): Review ONAP codebase license scan, Jan. 2019 sent by Steve Winslow on 1/18.

In Dublin, we are encouraging all projects that use named-queries to convert to custom-queries. In El Alto, the plan is to remove the named-query API.

AAI-1989 - Getting issue details... STATUS

<1-28/2019>:  Identify projects that are impacted; contact James Forsyth.

Want to get a sense of what efforts are underway in the community on service monitoring for long running instances of ONAP; when disaster strikes across pods or across dependent systems, what is being doing to detect/recover from such disasters?

AAI-2082 - Getting issue details... STATUS

<1-28/2019>: Any tool, other open community working on it - in addition to what K8S monitoring tools?

Prometheus tool:

https://jira.onap.org/browse/ONAPARC-352
https://jira.onap.org/browse/LOG-911
https://jira.onap.org/browse/OOM-1555
https://jira.onap.org/browse/OOM-1504
James Forsyth will setup a dedicated session - please include Stephen Gooch, djhunt

Michael O'Brien

Attendees:

Kenny Paul
Michael O'Brien
Mike Elliott
Sylvain Desbureaux
Habib Torab
Jun (Nicolas) Hu
@Paul Ionut Vaduva
Alain Soleil
Gary Wu
Jessica Wagantall
Jim Baker
John Lotoski

TSC-25 - Getting issue details... STATUS

By request of Dublin Scorecard - https://lists.onap.org/g/onap-tsc/topic/dublin_m1_scorecard_tsc/29536574?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,29536574

Alexis de Talhouët is welcome as TSC management - his deep technical "hands-on" approach will be appreciated

Meeting Minutes: 20190124

Video on CD - Continuous Deployment

• recording - except during sensitive pw screens -
• Bengt Thuree needs another slot - moved to Thu 2030
• 1830 in france not good - 2030 is good - will move meet to 1430EDT
• LF is the level of testing their own deployment
• Orange/OOM discussion in the past - working on pulling the release tag for a gerrit review poc -

around

sudo helm deploy local/onap --namespace onap -f onap/resources/environments/disable-allcharts.yaml --set so.enabled=true

server
https://gitlab.com/Orange-OpenSource/lfn/onap/onap_oom_automatic_installation/pipelines/44398686

• orange oom deploy step: validation steps are kubectl get pods, healthcheck, and some TBD subset of a use case (4 use case VNFs, (IMS,,,,) - SO issue being worked on by Sylvain Desbureaux and Morgan Richomme
• source above on https://gitlab.com/Orange-OpenSource/lfn/onap/onap_oom_automatic_installation
• Orange higher level source for all LF projects in https://gitlab.com/Orange-OpenSource/lfn
• Bengt Thuree working with IT/infra team for for VM's -
• next meeting next thu 31st Jan - demo from Orange next thu - 2030 GMT+1 (france time)
• how to work - keep it in the main jira as notes... - LF will work out integration with the infrastructure they are bringing up - a status mid week would be beneficial from the LF (you can work in the jira or subtask or via comments on the jira)
• key is getting the magic word working from an oom review - Orange Sylvain Desbureaux can work with Bengt.

• Ultimate Main Goal: prevent to merge code that has not been tested in a CD environment.

•   POCs
  Integration team: 2018
  Gary Wu - full onap system 13 vms - freq: master once a day
  http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?orgId=1
  https://github.com/garyiwu/onap-lab-ci

  Logging/OOM Team: 201710
  Michael O'Brien - partial onap system 1 vm - freq: hourly for 3 pod - 6 hours for full onap deploy 256G vm
  http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
  http://jenkins.onap.info/job/oom-cd-master2-aws/
  https://git.onap.org/logging-analytics/tree/deploy

  Orange Labs 201901
  https://gitlab.com/Orange-OpenSource/lfn/onap/onap_oom_automatic_installation/pipelines/44398686
  https://gitlab.com/Orange-OpenSource/lfn

• 
  

• Proposed flow 1 should be doable for Dublin - fully automated CI/CD - ElAlto due to VM resources
  - gerrit commit on the oom repo for a particular component like so, aai 
  - keyed by Issue-ID Jira
  - helm-verify jjb jenkins job currently runs - reports +1/-1
  - manual magic word "run-helm-deploy" will kick in a helm-deploy jjb job 
  that deploys robot and the particular pod to a 16-32g VM (preconfigured with 
  rancher as a single node) - how? jenkins will run a remote ssh shell to a 
  server using a cached key - a cd.sh script will need to be written - see the 
  2 pocs below already running 
  - reports +1/-1 if healthcheck for that component passes after 20 min - parse 
  the logs from jenkins
  - scripts to bring up k8s/helm/docker - see links in comments