...
| Title | Responsible | Status | Last discussed | Notes | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 2 Sonar Servers | William Reehil | Pending | 6/16 | What are we doing about the deprecated sonar server, should we redirect the old url to the new sonarcloud.io url? Ask this on PTL call | ||||||||||||||||
| 2 | Contributing+To+AAI+By+Assisting+with+Sonar+Reports | William Reehil | Completed | 6/16 | Update wiki page for sonar and contact information | ||||||||||||||||
| 3 | Self Repo creation | William Reehil | Pending | 6/16 | Link for self repo creation: https://wiki.onap.org/display/DW/Self+Repo+Creation+via+INFO.yaml William/Jimmy will look into this for creating the new sparky extensions repository | ||||||||||||||||
| 4 | Certificates (Who Owns Updating?) | 6/16 | Ideally when container starts certs should be generated and mounted. (Need to define the approach and how to get it implemented) Amdocs used to handle the certificates for their contributed microservices, which they no longer support. | ||||||||||||||||||
| 5 | Risks | William Reehil | Pending | 6/16 | Need to raise potential risks due to resource constraints on Guilin release on some non-functional requirements Guilin release - non-functional requirements proposed list Create tickets for G release off of
epics for A&AI impacted areas, assign resources if available, raise risks if not Open questions on
|