2018-11-01 AAI Developers Meeting
Recording
Agenda Items
Title | Responsible | Status | Notes | Last discussed |
---|---|---|---|---|
Agenda Suggestion | @Keong Lim | Done | Since there are more topics than can fit into any single meeting, suggest that after discussing one topic in depth, we rotate the agenda items to bring different issues to the top. | |
Jackson Replacement | Team @Keong Lim @Tian Lee | On Hold
| Security subcommittee has recommended teams move away from jackson, and will be presenting alternatives and asking for an assessment from each project. Our team will need to do an analysis - this would not be trivial, especially given how many of our repos are impacted. As of now, this would be a very high LOE for the team, we need to understand what the recommendation from the SECCOM is before we can provide better details on what the LOE would be. Updated: Using Google gson vs FasterXML Jackson 10th Oct: Present to Seccom meeting 15th Oct: Present to PTL meeting 31st Oct: Debatable whether the cost of swapping Cassandra and changing code is worth the benefit of removing Jackson from the vulnerabilities list | 1st Nov 2018 |
AAI too slow for Holmes | @Keong Lim @CT Paterson | In Progress | @Guangrong Fu mentioned AAI in Baseline Measurements based on Testing Results:
The problem for caching is how to know when to update the cached data. Even though the access time may be fast for Holmes, the risk is using out-of-date data, so the correlations will be wrong anyway. Also, duplicating the AAI data outside of AAI is probably a bad architectural decision. Making AAI faster for these use cases would be better. Has there been a performance analysis of where the time is spent? Could it help to use ElasticSearch (e.g. as in sparky)? Should Holmes have a batch interface to get more AAI data in fewer calls? Or a better correlation API that results in fewer calls? 31st Oct: https://lists.onap.org/g/onap-discuss/topic/27805753 1st Nov:
| 1st Nov 2018 |
HAproxy in OOM | @Former user (Deleted) | In Progress | Why is the pod for HAproxy not named (hard to figure out that there is a proxy), unsure how it is logging and where @James Forsyth creates JIRA tasks to 1. to have the pod named 2. add logging to the proxy AAI-1807: Change the aai pod name to aai-haproxyClosedAAI-1810: Add option to enable logging for haproxy dockerClosed | 1st Nov 2018 |
Rocket.Chat AAI channel | @Former user (Deleted) | Done | Would it make sense to create a AAI channel in rocket chat? @Former user (Deleted) will create a rocket chat channel AAI @James Forsyth created private group aai-dev in the integration rocketchat server - if you need access (@Keong Lim, @William Reehil, @William LaMont, @Manisha Aggarwal, @Tian Lee, @Steve Blimkie, @Arul Nambi, @Francis Paquette, @CT Paterson, @Giulio Graziani , @Mark Leonard, @Edward Dening, @Bo Lv anybody else?) please contact Jimmy and I'll add your rocketchat ID. | 1st Nov 2018 |
2 Types of logging in A&AI WS | @Former user (Deleted) | On Hold | There are 2 types of logging in the services
Is that correct? Shouldn't there be just 1 type? 1st Nov: After Casaclanca release investigate logging guidelines and figure out what library to use in order to unify logging within A&AI | 1st Nov 2018 |
Disable unused web services | @Former user (Deleted) | In Progress | Could we disable unused (i.e. not integrated) A&AI web services, so that the deployment is faster and the resource footprint is smaller? e.g. Champ (any other ws?) 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. @Venkata Harish Kajur @Former user (Deleted) - investigate how to disable/enable charts in A&AI so we can create a core group of pods which handle the use-cases and than extended group will all the services. Consider a group of unused/unintegrated services (like Champ) | 1st Nov 2018 |
AAI HAProxy and 2-way-TLS | @Former user (Deleted) | Open | Technical solution to either decommission the proxy or make design changes to AAF to enable client side certificates. | |
AAI Traversal queries | @Former user (Deleted) | Open | The AAI Traversal API is fairly complex, are there examples and descriptions of what the inputs and outputs of the rest api are, or alternative way to gain know-how? Code is quite difficult to read. | |
AAI Champ | @Former user (Deleted) | In Progress |
| 1st Nov 2018 |
Spring profiles | @Former user (Deleted) | Open | Do we need the “production” profile? | |
OOM Artifacts | @Former user (Deleted) | Open | Some of our top level OOM deployment artifacts are not unique (i.e. don’t take namespace into account as all other deployables), is that intentional? | |
Return codes and messages for WS | @Former user (Deleted) | Open | Is there a guide for the description of the error message and the error codes? How are new error states (message + code) added? | |
Rocket.Chat support | @Former user (Deleted) | Open | In order to use rocket chat with native client (and have notifications for example) it needs a TLS cert. Support for integration team? | |
Copyright license header restricted to 1 company | @Former user (Deleted) | Open | In the copyright /** * ============LICENSE_START======================================================= * org.onap.aai * ================================================================================ * Copyright © 2017-2018 AT&T Intellectual Property. All rights reserved. If there is a company other than AT&T the build fails saying the license header is wrong | |
Dublin 5G Use Case | @Benjamin Cheung | In Progress Last discussion: 24th Oct 2018 | Dublin AAI changes in support of 5g use cases. Link for presentation: 5G - PNF Plug and Play (Casablanca carry-over items)
| 25th Oct 2018 |
Schema Service | @Manisha Aggarwal | In Progress Last discussion: 25th Oct 2018 | Discuss about the Schema Microservice | 1st Nov 2018 |