- 1.1 Project Name:
  - 1.1.1 Project description:
  - 1.1.2 Scope:
  - 1.1.3 Architecture Alignment:
  - 1.1.4 Other Information:
  - 1.1.5 Key Project Facts:
  - 1.1.6 Release Components Name:
  - 1.1.7 Resources committed to the Release:
2 Meeting Minutes
- 2.1 20190124
- 2.2 20190131 - Orange CD demo from Sylvain Desbureaux
- 2.3 20190207
  - 2.3.1 Attendees

WIP - @Michael O'Brien

see https://lf-onap.atlassian.net/browse/TSC-25

This is a potential draft of a project proposal template. It is not final or to be used until the TSC approves it.

Link to Project Proposal training materials

Project Name:

Proposed name for the project: cd

Project description:

Provide high level description of intended project and intended use case(s) and benefit, if needed.
Requirements
- Deployment run on every or batch of commits
- Access to failed healtcheck results
- Access to failed container results "kubectl get pods --all-namespaces | grep -E '0/|1/2' - like http://jenkins.onap.info/job/oom-cd-master/3496/console

Scope:

Describe the functionality to be provided by the project. Please provide the full intended scope of the project; not just what is intended for the project's first release.
Specify any interface/API specification proposed,
Identity a list of features and functionality will be developed.
Identify what is in or out of scope. During the development phase, it helps reduce discussion.

Architecture Alignment:

How does this project fit into the rest of the ONAP Architecture?
- Please Include architecture diagram if possible
- What other ONAP projects does this project depend on?
How does this align with external standards/specifications?
- APIs/Interfaces
- Information/data models
Are there dependencies with other open source projects?
- APIs/Interfaces
- Integration Testing
- etc.

Other Information:

link to seed code (if applicable)
Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts:

Facts	Info

Facts	Info
PTL (first and last name)	@Michael O'Brien
Jira Project Name	Continuous Delivery
Jira Key	CD
Project ID	CD
Link to Wiki Space

Release Components Name:

Note: refer to existing project for details on how to fill out this table

Components Name	Components Repository name	Maven Group ID	Components Description

Components Name	Components Repository name	Maven Group ID	Components Description
		org.onap.cd

Resources committed to the Release:

Note 1: No more than 5 committers per project. Balance the committers list and avoid members representing only one company. Ensure there is at least 3 companies supporting your proposal.

Note 2: It is critical to complete all the information requested, that will help to fast forward the onboarding process.

Role	First Name Last Name	Linux Foundation ID	Email Address	Location

Role	First Name Last Name	Linux Foundation ID	Email Address	Location
PTL
Committers



Contributors

Meeting Minutes

20190124

20190124

20190124

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

Attendees/Participants

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

Meeting Minutes: 20190124

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

20190131 - Orange CD demo from Sylvain Desbureaux

20190131 agenda

demo on gitlab by Orange
discuss trigger work in Linux Foundation
and trigger work at Orange
quickly discuss 2 use cases we are solving for Dublin
recording at 1431
excellent demo and discussion of the working system Sylvain Desbureaux has setup for Orange as a CD poc that integrates with LF Gerrit posted to the wiki
https://lf-onap.atlassian.net/wiki/display/DW/CD+-+Continuous+Deployment#CD-ContinuousDeployment-20190131-OrangeCDdemofromSylvainDesbureaux
example from Orange in https://gerrit.onap.org/r/#/c/77660/
using -1, 0, 1 - currently 0 as the callback

Notes

Use cases

OOM docker image tag update
https://gerrit.onap.org/r/#/c/75910/
OOM chart configuration change
https://gerrit.onap.org/r/#/c/75479/
gitlab OOM repo mirroring for CD pocs
https://gitlab.com/obriensystems/oom
https://gitlab.com/Orange-OpenSource/lfn

Currently Manual
(essentially at a minimum the CD deploy does)

kubectl get pods --all-namespaces and oom/kubernetes/robot$ sudo ./ete-k8s.sh onap health

20190207

https://lf-onap.atlassian.net/browse/TSC-25

20190207 Agenda

propose reduce meets to every 2 weeks as Orange/LF collaboration is already done daily
send out vote on meetings every 2 weeks to LF
update video from last week
also open discussion on goals of this task force as it has been on since Mid Oct - RC0
Review status of Phases for this CD task force
phase 1: is essentially met - pending details on -1/0/+1 known issues with branch deployment/stability general to ONAP
Review running Orange gerritt bot for OOM repo merges
example https://gerrit.onap.org/r/#/c/78009/
review manifest vs oom docker tag truth - discussions/mails here and TSC-86
review LF infrastructure changes

q) on timing - work on profiles of dependencies
q) chart ownership - in queue - empty repos only for now J
example
https://git.onap.org/aaf/oom/tree/
optional for this release

mechanism is symlink just like the docs directory in each project -
discuss with Mike Elliott

CD - Continuous Deployment