zoom bridge: https://zoom.us/j/283628617
Duration 60 minutes
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| NO RECORDING FOR THIS SESSION | |||
| 5min | Open Issues Review | ||
| 5min | Emergency Maintenance Release - Tag: 3.0.2
| TSC-120 - Getting issue details... STATUS Timeline:
Current status: Partial testing complete and use cases, focused testing on basic functionality. Document updates required for all the changed components and use case docs. Need update at top level of RTD. | |
| 5min | M4 Preparation
Please update M4 checklist by April 10th, 2019 noon - thank you | Former user (Deleted) | Code Freeze. Mark the end of the Features coding. Jira issues are either fixed in the current release or assigned to next release. 100% of Functional Test Case are automated. End 2 End Release Test Cases are implemented (Integration Team). All new VNF Requirements planned for the release reviewed and implemented in VNF Requirements project. |
| 10min | CII Badging Grant/Right Access | Provide the procedure to add CII badging Grant/Access Add Former user (Deleted) as an editor <CII_badging_id:3607> | |
| 10min | OOM/Integration process | Process review of integration process from2019-04-04. Primary goal to use OOM as the primary source for the docker image tags. This will require some changes to the process - RC0 - will add process to the wiki Brian Freeman | |
| 10min | One LDAP group per repo - a proposal | Switching to 1:1 repos:LDAP group in April. Should be completely transparent to the team - helpdesk ticket on any noticed issues. | |
| 5min | grafana (http://onapci.org/grafana/login) External Labs Jenkins Jobs: https://jenkins.onap.org/view/External%20Labs/ | cl664y@att.com | Access to the grafana now requires login/PW seems to have changed 2019 Integration uses log files - not grafan Yang Xu to followup Follow up from Yang: Grafana was restarted lately and anonymous access was not enabled. Now everyone can access without password http://onapci.org/grafana/ and click on Daily Summary link. Is there another way to see if the containers are passing on ext. labs? M4 checklist references grafana - should change to not reference LF ext resources Former user (Deleted) |
AAF calling conventions With Dublin, AAF needs the Namespace in the URL. If your URL has "https://aaf-locate:8095/locate/org.osaaf.aaf.service:2.1", it needs to be WHERE NS=onap https://aaf-locate.onap:8095/locate/onap.org.osaaf.aaf.service:2.1 If you go direct: https://aaf-service.onap:8100/.... | AAF Team does not know how teams are currently deploying their Configs. Please contact Jonathan for help here, and/or with new Cert Volume method... Need to have this deployed before we change these others. ?move to El Alto? Follow up 2019-04-15 | ||
OOM commits process When contributors modify OOM configuration values it may impact runtime environment. Need to understand the OOM process if the changes to OOM can potentially get merged by OOM team without knowledge of the ONAP component team's committers/PTL. | Mandar Sawant | Hardcoded IPaddrs and ports - multiple reviewers should agree on the change. OOM uses only the healthcheck to verify "correctness". Team is expected to already have given a +1 before OOM merge. Mike Elliott to refresh process in OOM team. Automated testing of runtime would help eliminate this problem. | |
Chat log
07:02:18 From Pamela Dragosh : Can LF check Jenkins? Looks like a lot of jobs are sitting around waiting to get onto the queue. Seems stuck.
07:10:16 From Jimmy Forsythg : AAI AAF configs are in OOM: oom/kubernetes/aai/charts/aai-resources/resources/config/aaf and oom/kubernetes/aai/charts/aai-traversal/resources/config/aaf
07:10:51 From Martial Ngueko (AT&T) : does Jonathan modification implies an update of the AAF certificates ?
07:22:43 From Jonathan Gathman : AAF URL change should not affect Certificates. Auto generation of Certificates (which will be noted later) does not.
07:22:45 From Pamela Dragosh : Policy release notes are done already.
07:23:43 From Jonathan Gathman : I have not actually changed OOM for AAF yet (I am testing my changes for OOM, though it works well in K8S)
07:47:59 From Brian : kubernetes/aaf/charts/aaf-locate/values.yaml:aaf_register_as: "aaf-locate.onap" kubernetes/aaf/charts/aaf-locate/values.yaml: name: aaf-locate kubernetes/aaf/charts/aaf-locate/values.yaml: portName: aaf-locate kubernetes/aaf/charts/aaf-locate/Chart.yaml:name: aaf-locate kubernetes/aaf/charts/aaf-oauth/templates/deployment.yaml: - aaf-locate kubernetes/aaf/charts/aaf-fs/templates/deployment.yaml: - aaf-locate kubernetes/aaf/charts/aaf-cm/templates/deployment.yaml: - aaf-locate kubernetes/aaf/charts/aaf-hello/templates/deployment.yaml: - aaf-locate kubernetes/aaf/values.yaml: cadi_locator_as: "aaf-locate.onap" kubernetes/policy/charts/drools/resources/config/opt/policy/config/drools/base.conf:AAF_HOST=aaf-locate.{{.Release.Namespace}} kubernetes/policy/charts/policy-common/resources/config/pe/base.conf:AAF_HOST=aaf-locate.{{.Release.Namespace}} kubernetes/aai/charts/aai-traversal/templates/job.yaml: - aaf-locate kubernetes/aai/charts/aai-traversal/resources/config/aaf/org
07:48:42 From Brian : kubernetes/aai/charts/aai-traversal/resources/config/aaf/org.osaaf.location.props:aaf_locate_url=https://aaf-locate.{{.Release.Namespace}}:8095 kubernetes/aai/charts/aai-champ/resources/rproxy/config/cadi.properties:aaf_locate_url=https://aaf-locate.{{.Release.Namespace}}:8095 kubernetes/aai/charts/aai-resources/resources/config/aaf/org.osaaf.location.props:aaf_locate_url=https://aaf-locate.{{.Release.Namespace}}:8095 kubernetes/aai/charts/aai-resources/resources/rproxy/config/cadi.properties:aaf_locate_url=https://aaf-locate.{{.Release.Namespace}}:8095 kubernetes/aai/charts/aai-gizmo/resources/rproxy/config/cadi.properties:aaf_locate_url=https://aaf-locate.{{.Release.Namespace}}:8095 kubernetes/aai/charts/aai-sparky-be/resources/config/portal/cadi.properties:aaf_locate_url=https://aaf-locate.{{.Release.Namespace}}:8095 kubernetes/clamp/values.yaml: "clamp.config.cadi.aafLocateUrl": "https://aaf-locate.{{ include "common.namespace" . }}:8095", kubernetes/appc/resources/config/appc/opt/onap/appc/data/pr
07:57:05 From Brian : root@njcdtl01bf1936:/home2/bf1936/ONAP/oom# grep -R org.osaaf * kubernetes/aai/charts/aai-traversal/templates/configmap.yaml:{{ tpl (.Files.Glob "resources/config/aaf/org.osaaf.location.props").AsConfig . | indent 2 }} kubernetes/aai/charts/aai-traversal/templates/deployment.yaml: - mountPath: /opt/app/aai-traversal/resources/aaf/org.osaaf.location.props kubernetes/aai/charts/aai-traversal/templates/deployment.yaml: subPath: org.osaaf.location.props kubernetes/aai/charts/aai-traversal/resources/config/aaf/org.osaaf.location.props:## org.osaaf.location.props kubernetes/aai/charts/aai-traversal/resources/config/aaf/cadi.properties:cadi_prop_files=/opt/app/aai-traversal/resources/aaf/org.osaaf.location.props:/opt/app/aai-traversal/resources/aaf/org.onap.aai.props kubernetes/aai/charts/aai-resources/templates/configmap.yaml:{{ tpl (.Files.Glob "resources/config/aaf/org.osaaf.location.props").AsConfig . | indent 2 }} kubernetes/aai/charts/aai-resources/templates/deployment.yaml: - mountPath:
Action Items
- 2/11: Migrate Docker image releases from Nexus3 into Docker Hub (Architecture Independence) by Dublin M4.
<2-15-2019> Preparing a preso for review of all known infrastructure change requests for review at PTL meeting 2-25-2019
<2019-04-08: global-jjb progress report: start on DCAE soon - focus on El Alto delivery (precursor to Dockerhub) - Oom values.yaml or integration repo manifest (
TSC-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 ) Michael O'Brien
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
onap/aaf/aaf_service,2.1.8
20190318: discussed discrepancy with Orange in OOM call last week - manifest is still in use to manage versions until merges come into OOM from the teams and we finish the architecture of the merged manifest in oomOOM Meeting Notes - 2019-03-13
- Review Sylvain Desbureaux's detailed docker version/size/state status page at Reduction effort between Casablanca and Dublin
<1-7/2019> Integration team to document the procedure.<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
<1-21/2019> Procedure should include Timers, dependencies, etc.
just need to define all the --set and -f overrides like the following
sudo helm deploy onap local/onap --namespace $ENVIRON -f $DISABLE_CHARTS_YAML -f $DEV0_YAML $APPENDABLE_ENABLED_FLAGS --verbose
<1-28-2019>: Document how to handle the latest 3rd party image from github.
<2019-02-19>: One over-ride that will be shared, parent over-ride for docker versions, Michael O'Brien to modify TSC-86 to reflect process. Still looking at tool to institute changes for all projects (single commit). Mike Elliott FREEMAN, BRIAN D Gary Wu Sylvain Desbureaux to follow up offline.
It should also consider the problem identified with the Casablanca Maintenance Release:https://lists.onap.org/g/onap-tsc/message/4641
<2019-03-01 - Need a date for the delivery of the procedure ><2019-04-08 New process defined - needs to be documented on the wiki Brian Freeman>
- Tlab persistent storage IO architecture cl664y@att.com
- How to consume Alpine? Adolfo Perez-Duran (Deactivated)
- Modify code freeze checklist to include a certificate expiry check Former user (Deleted)
- What is the plan for the June ONAP Developers Forum - dates/location/etc Kenny Paul<includes outreach to education - looking at universities><Virtual meeting? - still under investigation>
- Helm Chart Transfer: 4 projects have been identified for trial: A&AI, Log, Policy, APPC, CLAMP and ONAP CLI. Mike Elliott will work with PTL to gather/transfer knowledge and create training materials. Training to be done the week of Jan 14 and PTL to provide their commitment or not by M1 on Jan 24.<1-7/2019>: Work in progress. Schedule might shift to another week. Michael will follow-up with Mike. Training will be open to everybody. The objective is that each team will take over the management of their Helm Charts.
<1-28/2019>: Meeting is organized on 1/29 with LF. Training will be organized early in February. Additional information on the next PTL call (2/4)<2019-2-19: Meeting on this topic today - review the process - develop training material. OOM subcharts complete - A&AI this week><2019-03-04: Ready to do the first project A&AI; after testing on the first project make video on process flow, several others will follow Jessica Gonzalez Mike Elliott><still working out the A&AI details - in progress; once the POC is complete the other repos will follow><2019-04-08: LF releng - Pushed a patch to a code transfer (test) branch to test out an approach and testing verify job. Once proved out need to work with down stream CI/CD before wholesale push. > - AAF calling conventions - followup Jonathan Gathman