Page Comparison

Casablanca Maintenance Release

• Remaining Open Issues
• Integration Status
• Release Note

Dublin Release - M1 preparation

S3P Requirements

Security pNF/xNF

TSC Dublin Release Prioritization (v11): Dublin Release Requirements

Feedback/Action items: https://lists.onap.org/g/onap-tsc/message/4460

Remaining Open Issues: https://lists.onap.org/g/onap-release/message/934

Platform Maturity Requirements (S3P)

docker_version:
type: string
default: "17.03.2"

rancher_version:
type: string
default: "1.6.25"

rancher_agent_version:
type: string
default: "1.2.11"

kubectl_version:
type: string
default: "1.11.5"

helm_version:
type: string
default: "2.9.1"

Oom values.yaml or integration repo manifest ( Image RemovedTSC-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

<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

DEV reduced deployment footprint

through ReplicaSet: 1

Discussion on state of enforced dependencies - SDNC and AAI are good examples - for SDNC it will not deploy unless dmaap, consul and sdc are pre-deployed, however other projects that have compile-time/injection-time pom.xml dependencies are not reflected.

Some projects have explicit deployments set in their init containers - others do not yet.

Issues:

Enforced dependencies block a module for dev testing unless dependencies are up

For example - everyone needs AAI up - but there are no init containers referencing AAI so any module can deploy without AAI - but functionality will be limited.

Proposal:

Follow - as usual - AAI example - where they put in a conditional on the --set enabled flag - and don't enforce the dependency - not blocking bringing up just a single module. However if the dependency is enabled in dev/values.yaml then the dependency is checked.

https://git.onap.org/oom/tree/kubernetes/aai/charts/aai-traversal/templates/job.yaml#n42

    spec:      initContainers:
        {{ if eq .Values.global.aafEnabled true }}
        - --container-name
        - aaf-locate
        {{ end }}

The deployment profile is useful for module-level deployments, consistent sequential deployments, CD and dev environments

current state

https://lists.onap.org/g/onap-discuss/topic/oom_sdnc_just_deploy_sdnc/28989874?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,28989874

Image Removed

or higher level

Image Removed

Committer, Calendar, etc?

#1 DmaaP zoom bridge issue

#2 AAF - Add Sai committer's rights

#3 Remove inactive Modeling committers - https://lists.onap.org/g/onap-tsc/message/4450

I've been trying to change meeting time for VNFRQTS call since Nov last year. Process on website says to create ticket on helpdesk. I've have no response on this. If that's not the process can we get the instructions updated.

Helpdesk #'s

#66481

#65633

#64787