| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-341 |
|---|
|
We will proceed with what we have in Frankfurt, a VNFM model that exists in AAI today. We have to think of how to proceed further.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-394 |
|---|
|
Project tickets for modeling effort:
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | AAI-2929 |
|---|
|
Information Elements
We need to understand which are the key elements ONAP needs to be aware of. Those should be driven from the use case flows.
Next week (19 Jun) Fernando Oliveira will present on IFA 11 changes
Eric Multanen (Deactivated) will upload current helm packages to the workspace