Recording:
Attendees:
Tony Noori
Chandra Cinthala
START RECORDING
1 | Casablanca Maintenance Release Status | James Forsyth | Look at Jira, talk about open issues
| |||||||||||
2 | Dublin Use Cases | BBS Broadband Service Use Case (Dublin) Change Management Dublin Extensions Fine Grain Placement Service (F-GPS) Edge Automation Functional Requirements for (Dublin) OpenSource Access Manager (OSAM) Use Case K8S based Cloud Region Support Tony Noori from AT&T will identify the ONAP POC for system engineering for AAI modelling. This person will coordinate schema changes, watch the use case wiki, jira, perform gerrit reviews, etc. | ||||||||||||
3 | Tomcat-embed license policy | org.apache.tomcat.embed in springboot 1.5.18 has a strong copyleft license. Can we exclude this from the package since we don't use the embedded tomcat? James Forsyth has shown that this mitigates the issue in the resources project | ||||||||||||
4 | Helm Chart Ownership | James Forsyth | OOM is planning to make a new repo for our OOM helm charts and give us the ability to commit changes. The community is still working out process of how these updates will be merged into the public repos that all teams use. We need to look at our team's ability to support this, including having a test process internally to validate changes before we merge them. | |||||||||||
5 | Virtual F2F Dec 10-12 | ONAP Project Developers Event, Dec 10 - 12, 2018, (Virtual Webinars) - Wednesday's call (12 Dec) will be superceded by the Dublin Architecture Review at the VF2F. The weekly dev call will be as scheduled on 13 Dec. | ||||||||||||
6 | Casablanca Maintenance Release | The casablanca branch is open for CMR code reviews. Discuss what will be included in the CMR. Release artifacts need to be available 10 Jan 2019 James Forsyth send note to OOM team to see which branch they are accepting changes for CMR - Update: according to Mike Elliot CMR changes go to the OOM 'casablanca' branch and master is open for Dublin updates. | ||||||||||||
7 | Documentation | Suggestion from today's meeting: Installation and Developer Setup page - linking the latest out to the wiki and then copy at release time. | ||||||||||||
8 | ESR Nexus IQ Vulnerabilities | Since we can't be sure about the status of the ESR vulnerabilities, we will publish that the application is vulnerable to all of them. | ||||||||||||
9 | MSB Configs | |||||||||||||
10 | CSIT Test Cases | Need to maintain these for Dublin, and expand to include things like MSB integration. Establish a working group to develop CSIT test cases for Dublin and document them on the wiki. James Forsyth will create the page and solicit ideas. | ||||||||||||
11 | Container sizing | AAI-1940 - Correct resources requirements in Helm Charts Open | ||||||||||||
12 | CCVPN schema changes | |||||||||||||
13 | Spike | Identify component owner and disposition for casablanca Component owner: Amdocs. Spike takes messages from Champ and populates in topics. James Forsyth to release Spike. | ||||||||||||
14 | Casablanca Release Status | Casablanca Release Integration Testing Status - if you submit documentation between now and RC2 on 27 Nov please include Sofia Wallin in the list of reviewers on the gerrit review. | ||||||||||||
15 | Lab support | To assist with monitoring JIRA, suggest subscribing to this filter: https://jira.onap.org/issues/?filter=11532, which does pick up - AAI-1913AAI queries not working in SB-06 Open as discussed. Also sent a message to onap-discuss to ask if JIRA Notification Scheme and new email list could be setup as well. | ||||||||||||
16 | Status of History Backend | There is a document which shows us as delivering the history backend in Casablanca - need to discuss if we are providing an accurate picture of what's available in Casablanca. | ||||||||||||
17 | Hbase to Cassandra migration | Bell Canada has a requirement to migrate their A&AI Graph DB backend from HBase to Cassandra. We are enabling this effort. We have been investigating GraphAdmin code in ONAP, which seems to support the framework. We would like to make enhancements to this framework and contribute to ONAP. The initial enhancements we would like to accomplish are:
Our goals:
Recording 13th November DBmigration.mp4 | ||||||||||||
18 | AAI GraphGraph | Discussion A&AI GraphGraph moved to 2018-11-15 AAI Developers Meeting. | ||||||||||||
19 | 5min | AAI UI documentation or user guide | Recently updated AAI Graphical User Interface due to colleagues wanting to use the AAI UI. Is there a more comprehensive and authoritative documentation or user guide for AAI UI? The main issue is that it is not clear how to get started - Francis Paquette will look at what's on the readthedocs site, I think we need to port what Keong has put in the wiki to the main docs repo at a minimum. - AAI-1268[sparky] Platform Maturity - Usability In Progress | |||||||||||
20 | CII Badging | Fill out CII Silver Badging Template. We have not committed to a silver badge, but the community wants us to fill it out to the best of our ability. | ||||||||||||
21 | Dublin 5G Use Case | Dublin AAI changes in support of 5g use cases. Link for presentation: 5G - PNF Plug and Play (Casablanca carry-over items) 29 Nov: https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Release+4+%28Dublin%29+Use+Cases+and+functional+requirements | ||||||||||||
22 | Schema Service | |||||||||||||
23 | Support for 2 OOM deployment types | Motivation: Decrease the resource footprint for A&AI (ONAP) deployments Idea: we could support 2 different deployments 1. full (normal) deployment and 2. barebones deployment. The point of the "barebone" deployment would be to deploy only the essential services necessary for proper functioning of A&AI (leaving out services like cacher, sparky, graphadmin, having 1 cassandra node instead of 3 or 5 etc). In order to reduce hardware/cloud costs (mainly the memory footprint) it could be beneficial to support a minimalistic A&AI deployment. | ||||||||||||
24 | 5G PNF Software upgrade | We have a 5G related functionality in Change management, 5G PNF Software upgrade. https://wiki.onap.org/display/DW/5G+-+PNF+Software+Upgrade. Right now, PNF software version is modeled and accepted in SDC, and also approved in Modeling subcommittee and TSC.https://wiki.onap.org/display/DW/TSC+2018-07-26+Meeting+Agenda. (Modeling report) We are not familiar with A&AI. The target of this functionality is to update PNF Sw version when upgrade completion with specified pnfid. Could you and your team give us some help on this? 1) Is there any available APIs provided by AAI for this? 2) If yes, can you give me some details on it. If not, could you and AAI team provide support in Casablanca? We would like to provide contributions if needed. wangyaoguang to follow-up with SDC team and send conclusion results to James Forsyth |
...