This is an issue to capture the comments and notes from the F2F in the Etherpad.
2) GAPS (Day 1):
IT and ML workloads -- Need to define the types of workloads and cover at least to a certain extent, IT as well as VNF (network functions). This needs to be spelled out in the section on what is not covered.
Terminology with respect to VNF profiling requirements. Need additional clarity around profiles. ch01
JB - Clarifications needed.
BFC - Lots of clean up on wording required overall, but Chapter 1 has the definitions, so important to get correct here.
Tenant is defined in Chapter 1 and in Chapter 3 are different. Which one should we consider here? Need to define the tenant in more detail and reconcile the differences.
JB - Clarifications needed. Slicing vs. Tenant, etc.
After the definition is done use the definition in a consistent way. BFC -- Agreed.
Release 1 MVP is only Infra and VNFs; CNF-s will be partially supported in Release 2
JB - clarify position and look at best way to support/define CNF articulated. (also impacts Ch. 3)+1 (high level only in CP1)
Can this be clearly stated in the document and can we remove the refernces ot CNF-s from the Release 1 branch to avoid confusion? Overall CP1 is missing the use cases, once these are added, much of the confusion should be resolved.
CNTT should collaborate very closely with the respective API workgroup of SDOs (ETSI, MEF, TM Forum). To collate the relevant APIs from these SDOs would require special permission since information might not be available to the public. eg. MEF LSO APIs & TM Forum OpenAPIs are accessible by members only.
JB Ch. 1 and 7. And also how CNTT community operates outside the document.
[G0]: ETSI NFV OpenAPI-s are accessible for everyone here: https://forge.etsi.org/gitlab/nfv.
OpenStack API-s: https://docs.openstack.org/stein/api/
This is an issue to capture the comments and notes from the F2F in the Etherpad.
2) GAPS (Day 1): IT and ML workloads -- Need to define the types of workloads and cover at least to a certain extent, IT as well as VNF (network functions). This needs to be spelled out in the section on what is not covered.
Terminology with respect to VNF profiling requirements. Need additional clarity around profiles. ch01 JB - Clarifications needed. BFC - Lots of clean up on wording required overall, but Chapter 1 has the definitions, so important to get correct here.
Tenant is defined in Chapter 1 and in Chapter 3 are different. Which one should we consider here? Need to define the tenant in more detail and reconcile the differences. JB - Clarifications needed. Slicing vs. Tenant, etc. After the definition is done use the definition in a consistent way. BFC -- Agreed.
Release 1 MVP is only Infra and VNFs; CNF-s will be partially supported in Release 2
JB - clarify position and look at best way to support/define CNF articulated. (also impacts Ch. 3)+1 (high level only in CP1) Can this be clearly stated in the document and can we remove the refernces ot CNF-s from the Release 1 branch to avoid confusion? Overall CP1 is missing the use cases, once these are added, much of the confusion should be resolved.
CNTT should collaborate very closely with the respective API workgroup of SDOs (ETSI, MEF, TM Forum). To collate the relevant APIs from these SDOs would require special permission since information might not be available to the public. eg. MEF LSO APIs & TM Forum OpenAPIs are accessible by members only. JB Ch. 1 and 7. And also how CNTT community operates outside the document. [G0]: ETSI NFV OpenAPI-s are accessible for everyone here: https://forge.etsi.org/gitlab/nfv. OpenStack API-s: https://docs.openstack.org/stein/api/