Purpose
- Deep-dive discussions that take more time than is available in a single AAI Weekly Status and Coordination Meeting
- Review related wiki pages, e.g. under AAI Design Documentation
Meeting Time Poll
| Title | Responsible | Notes |
|---|---|---|
| Weekly Developer's Call | James Forsyth will create a new poll and send link to new poll to the onap-discuss list |
Proposed Agenda Items
| Title | Responsible | Status | Notes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dublin 5G Use Case | IN PROGRESS | Dublin AAI changes in support of 5g use cases. Link for presentation: 5G - PNF Plug and Play (Casablanca carry-over items)
| |||||||||||
| Schema Service | IN PROGRESS | Discuss about the Schema Microservice 11th Oct: Use Cases for Dynamic AAI Schema Changes | |||||||||||
| Jackson Replacement | IN PROGRESS | 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 | |||||||||||
| AAI HAProxy and 2-way-TLS | Pavel Paroulek | OPEN | Technical solution to either decommission the proxy or make design changes to AAF to enable client side certificates. | ||||||||||
| AAI Traversal queries | Pavel Paroulek | 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 | Pavel Paroulek | OPEN |
| ||||||||||
| Spring profiles | Pavel Paroulek | OPEN | Do we need the “production” profile? | ||||||||||
| OOM Artifacts | Pavel Paroulek | 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? | ||||||||||
| New column | Pavel Paroulek | IN PROGRESS | Proposing new column Status, where: OPEN - topic not yet discussed IN PROGRESS - being worked on ON HOLD - not being worked on and not finished DONE - 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:
|