Agenda
- Reviewing EPIC list and priority in OOM for Production-Grade Deployments
Some Discussion Topics
- JIRA board https://jira.onap.org/secure/RapidBoard.jspa?rapidView=41&useStoredSettings=true
- Integration team question about OOM status - https://lists.onap.org/pipermail/onap-discuss/2018-January/007085.html
- TSC 20171221 meeting details:
- TSC new project proposals - discuss CHAP/MUSIC with OOM - bharathb
- TSC new project proposals - Image Manager - Former user (Deleted)
- TSC item - need decision on whether to remove HEAT from Beijing
- TSC item - upgrade path for Beijing to Casablanca - OOM to provide framework that other projects submit their DB and API upgrade scripts - raise root epic like
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-5 - TSC 20180104 readiness:
- release-1.1.0 to Amsterdam switch
- review of all release-1.1.0 doc/content -
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-529 - partially related to CI/CD readiness
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-373 - Discuss Victor Morales
patch to support OOM in VagrantJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-370
Victor has been a very good supporter of development environments in ONAP with the toolset he originated - please look over and the deployment system that provides another way to bootstrap ONAP
https://lists.onap.org/pipermail/onap-discuss/2017-December/007041.html - OOM Contribution recognition list (committers, contributors, documentation, testing, architecture ...)
- Kubernetes 1.9.0 RC release last week
- TSC new project proposals - discuss CHAP with OOM - bharathb
- TSC new project proposals - Image Manager - Former user (Deleted)
- TSC item - need decision on whether to remove HEAT from Beijing
- TSC item - upgrade path for Beijing to Casablanca - OOM to provide framework that other projects submit their DB and API upgrade scripts - raise root epic like released last week - staying on 1.8.6 for now until we solve the secrets issue -
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-522
look atJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-530 - Assist SDC with any Kubernetes deployment issues during
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SDC-828 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SDC-647 - requests for
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INTOOM-5511