Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
exclude1

WIP  - Michael O'Brien

see 

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyTSC-25

...

Link to Project Proposal training materials

Project Name:

  • Proposed name for the project: projectnamecd

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.

...

Role

First Name Last Name

Linux Foundation ID

Email Address

Location

PTL



Committers


















Contributors













Meeting Minutes

20190124


View file
namezoom_0_20190124_tsc-25_meeting.mp4
height250

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

View file
name20190131_cd_tsc-25-meet_with_Orange_Sylvain_Desbureaux_demo.mp4
height250


 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 

View file
name20190207_cd_tsc-25-meet.mp4
height250

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyTSC-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

Attendees


Image Added