Status column
| Status | Description | ||||||
|---|---|---|---|---|---|---|---|
| Agenda item not yet discussed | ||||||
| Agenda item being worked on | ||||||
| Agenda item not being worked on and not finished | ||||||
| Agenda item finished, item can be removed | ||||||
| Agenda item finished, any in-progress work was abandoned, item can be removed |
Attendees
Recording
Agenda Items
| Title | Responsible | Status | Notes | Weekly Developer's Call | James Forsyth|||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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)
| |||||||||||||||||||||||||||||||||||
| Schema Service |
| Discuss about the Schema Microservice 11th Oct: Use Cases for Dynamic AAI Schema Changes | |||||||||||||||||||||||||||||||||||
| Jackson Replacement |
| 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 | |||||||||||||||||||||||||||||||||||
| Disable unused web services |
| 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?) | |||||||||||||||||||||||||||||||||||
| AAI HAProxy and 2-way-TLS | Former user (Deleted) |
| Technical solution to either decommission the proxy or make design changes to AAF to enable client side certificates. | ||||||||||||||||||||||||||||||||||
| AAI Traversal queries | Former user (Deleted) |
| 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) |
|
| ||||||||||||||||||||||||||||||||||
| Spring profiles | Former user (Deleted) |
| Do we need the “production” profile? | ||||||||||||||||||||||||||||||||||
| OOM Artifacts | Former user (Deleted) |
| 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? | ||||||||||||||||||||||||||||||||||
| New column | Former user (Deleted) |
| Proposing new column Status, where:
James Forsyth will create a new poll and send link to new poll to the onap-discuss list https://doodle.com/poll/t2c7md2kv9x7cdzx- topic finished, can be closed and removed Keong: The "status" mirrors a JIRA case workflow. Should we open JIRA cases to track progress and link them here? They can also be linked/searched from the Meeting Notes pages. Keong: Also just to use up the available colours from Confluence macro, suggest:
Pavel: Keong Lim - I think some agenda items don't justify opening and managing a JIRA ticket, but if the agenda item leads to a real task that someone should perform then we definately should create a JIRA for that. The "Cancelled" status is a marvelous idea! | ||||||||||||||||||||||||||||||||||
| Return codes and messages for WS |
| 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 |
| In order to use rocket chat with native client (and have notifications for example) it needs a TLS cert. Support for integration team? | |||||||||||||||||||||||||||||||||||
| 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. |