Skip to end of metadata
Go to start of metadata

WIP  - Michael O'Brien (Amdocs 1705-1905)

see  TSC-25 - Getting issue details... STATUS

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

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

PTL (first and last name)
Jira Project NameContinuous Delivery
Jira KeyCD
Project IDCD
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



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

PTL



Committers


















Contributors













Meeting Minutes

20190124


zoom_0_20190124_tsc-25_meeting.mp4

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


20190131 - Orange CD demo from Sylvain Desbureaux

20190131_cd_tsc-25-meet_with_Orange_Sylvain_Desbureaux_demo.mp4


 20190131 agenda

Notes
 Use cases

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 

20190207_cd_tsc-25-meet.mp4

TSC-25 - Getting issue details... STATUS

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

Attendees



  • No labels

5 Comments

  1. new record for the aws system (only SO and vnfsdk)
    http://jenkins.onap.info/job/oom-cd-master/2971/consoleFull
    41/43
    ahead of tlab temporarily at 36/43 - but both systems still have intermittent failures

    https://jenkins.onap.org/view/External%20Labs/job/lab-tlab-beijing-oom-deploy/320/console

  2. I was thinking of how to do a verify job based test of code with an "instantiateVFW"  E2E test.

    Would simply replacing the docker container for a project with the verify job docker for the component to test be a faster verify.

    Build verify up through a docker image tagged projectA-container[A-Z]-verify-20181015T113454Z

    Use oom to do a image upgrade of projectA with the verify containers - the rest of ONAP stays on the staging/release containers as appropriate

    run health (must pass on old and new containers)

    run instantiateVFW (must pass - potential for openstack spurious issues)

    restore original docker images for ProjectA with staging/release  that were there before.


    I think  this would be faster than a complete re-install ?

  3. azure cd cluster

    ubuntu@a-cd-cd0:~$ kubectl top nodes
    NAME                                                            CPU(cores)   CPU%      MEMORY(bytes)   MEMORY%   
    a-cd-cd1.ol5omeerae0ujnzp3ubpalro4a.cx.internal.cloudapp.net    320m         4%        2492Mi          15%       
    a-cd-cd10.52jfcnvzqkhufliffwyqadavld.cx.internal.cloudapp.net   192m         2%        979Mi           6%        
    a-cd-cd11.zlm1p50qb14uxngou5vjncfi0e.cx.internal.cloudapp.net   174m         2%        982Mi           6%        
    a-cd-cd2.q4r3tj5k31vuphomrg3zdctgsa.cx.internal.cloudapp.net    212m         2%        1176Mi          7%       
    a-cd-cd3.wcz1aktttmouhanxc3og1uxi2h.cx.internal.cloudapp.net    212m         2%        1085Mi          6%        
    a-cd-cd4.untu0hxmuvbexjtmxyfgy3muah.cx.internal.cloudapp.net    162m         2%        991Mi           6%        
    a-cd-cd5.3twsgvxnopduhprvwokid2qtmg.cx.internal.cloudapp.net    174m         2%        978Mi           6%        
    a-cd-cd6.okbkwq3umygu5o1qxcktjtnwxa.cx.internal.cloudapp.net    203m         2%        992Mi           6%        
    a-cd-cd7.wnm41geqmccutbbmmmdhtxxidc.cx.internal.cloudapp.net    188m         2%        983Mi           6%        
    a-cd-cd8.uh0pm3u1svmedelb2jyr3h4lse.cx.internal.cloudapp.net    177m         2%        998Mi           6%        
    a-cd-cd9.5hdz0oogde4enpg5qj55lmmvgd.cx.internal.cloudapp.net    168m         2%        990Mi           6%        
    ubuntu@a-cd-cd0:~$ kubectl get nodes -o wide
    NAME                                                            STATUS    ROLES     AGE       VERSION            INTERNAL-IP       EXTERNAL-IP       OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
    a-cd-cd1.ol5omeerae0ujnzp3ubpalro4a.cx.internal.cloudapp.net    Ready     <none>    4d        v1.11.2-rancher1   40.84.2.199       40.84.2.199       Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd10.52jfcnvzqkhufliffwyqadavld.cx.internal.cloudapp.net   Ready     <none>    3m        v1.11.2-rancher1   104.210.0.25      104.210.0.25      Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd11.zlm1p50qb14uxngou5vjncfi0e.cx.internal.cloudapp.net   Ready     <none>    3m        v1.11.2-rancher1   104.46.97.97      104.46.97.97      Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd12.4rhao0uc1rvubmts0bppbfbq5b.cx.internal.cloudapp.net   Ready     <none>    1m        v1.11.2-rancher1   40.123.46.66      40.123.46.66      Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd13.1axxbdcbo31e3icq42v4itr0sc.cx.internal.cloudapp.net   Ready     <none>    1m        v1.11.2-rancher1   40.70.29.72       40.70.29.72       Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd2.q4r3tj5k31vuphomrg3zdctgsa.cx.internal.cloudapp.net    Ready     <none>    4d        v1.11.2-rancher1   104.209.185.151   104.209.185.151   Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd3.wcz1aktttmouhanxc3og1uxi2h.cx.internal.cloudapp.net    Ready     <none>    11m       v1.11.2-rancher1   104.46.106.27     104.46.106.27     Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd4.untu0hxmuvbexjtmxyfgy3muah.cx.internal.cloudapp.net    Ready     <none>    8m        v1.11.2-rancher1   104.208.216.200   104.208.216.200   Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd5.3twsgvxnopduhprvwokid2qtmg.cx.internal.cloudapp.net    Ready     <none>    8m        v1.11.2-rancher1   104.210.7.16      104.210.7.16      Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd6.okbkwq3umygu5o1qxcktjtnwxa.cx.internal.cloudapp.net    Ready     <none>    6m        v1.11.2-rancher1   104.210.5.24      104.210.5.24      Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd7.wnm41geqmccutbbmmmdhtxxidc.cx.internal.cloudapp.net    Ready     <none>    6m        v1.11.2-rancher1   104.46.110.23     104.46.110.23     Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd8.uh0pm3u1svmedelb2jyr3h4lse.cx.internal.cloudapp.net    Ready     <none>    4m        v1.11.2-rancher1   104.46.98.80      104.46.98.80      Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
    a-cd-cd9.5hdz0oogde4enpg5qj55lmmvgd.cx.internal.cloudapp.net    Ready     <none>    4m        v1.11.2-rancher1   104.210.2.46      104.210.2.46      Ubuntu 16.04.1 LTS   4.15.0-1021-azure   docker://17.3.2
  4. ubuntu@ip-172-31-29-61:~/oom/kubernetes$ sudo helm deploy onap local/onap --namespace onap -f ../../dev.yaml --verbose
    fetching local/onap
    Error: UPGRADE FAILED: "onap-dmaap" has no deployed releases
    Error: UPGRADE FAILED: "onap-log" has no deployed releases
    Error: UPGRADE FAILED: "onap-pomba" has no deployed releases
    Error: UPGRADE FAILED: "onap-robot" has no deployed releases
    onap-dmaap	1       	Thu Dec 27 00:46:47 2018	FAILED  	dmaap-3.0.0	onap     
    onap-log  	1       	Thu Dec 27 00:46:49 2018	FAILED  	log-3.0.0  	onap     
    onap-pomba	1       	Thu Dec 27 00:46:51 2018	FAILED  	pomba-3.0.0	onap     
    onap-robot	1       	Thu Dec 27 00:46:54 2018	FAILED  	robot-3.0.0	onap     

    fixed by an empty deploy first
    sudo helm deploy onap local/onap --namespace onap -f onap/resources/environments/disable-allcharts.yaml --verbose
    sudo helm deploy onap local/onap --namespace onap -f ../../dev.yaml --verbose
    ubuntu@ip-172-31-29-61:~/oom/kubernetes$ sudo helm list
    NAME      	REVISION	UPDATED                 	STATUS  	CHART      	NAMESPACE
    onap      	2       	Thu Dec 27 01:06:12 2018	DEPLOYED	onap-3.0.0 	onap     
    onap-dmaap	1       	Thu Dec 27 01:06:14 2018	DEPLOYED	dmaap-3.0.0	onap     
    onap-log  	1       	Thu Dec 27 01:06:18 2018	DEPLOYED	log-3.0.0  	onap     
    onap-pomba	1       	Thu Dec 27 01:06:26 2018	DEPLOYED	pomba-3.0.0	onap     
    onap-robot	1       	Thu Dec 27 01:06:38 2018	DEPLOYED	robot-3.0.0	onap