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 |