Hello
Agree to the update of P9,P10,P11. And also agree to remove D2 term.
But I don’t think the update to P7 is more suitable, the original
version seems better.
Best regards
发件人: [email protected] [mailto:[email protected]]
代表 [email protected]
发送时间: 2017年11月24日 4:04
收件人: [email protected]; [email protected]
主题: [onap-tsc] [arch] Corrections for the architecture document.
Hello
Please find some corrections for the Architecture document
https://www.onap.org/wp-content/uploads/sites/20/2017/11/ONAP_CaseSolution_Architecture_FNL.pdf
As noticed by Nermin, the D2 term should be removed from Figure 1
P7. Controllers
I think the VF-C definition is not exact according to existing R1 code.
“Also, the Virtual Function Controller (VF-C) provides an ETSI NFV compliant
NFV-O function, and is responsible for lifecycle management of virtual services
and the associated physical COTS server infrastructure. VF-C provides a generic
VNFM capability but also integrates with external VNFMS and VIMs as part of a
NFV MANO stack.”
We propose to replace by “The Virtual Function Controller (VF-C) is responsible
for managing the lifecycle of VNF when this cannot be achieved by other
components of the ONAP architecture and for managing the lifecycle of network
services that comprise at least one of such VNF. It can also processes fault
and performance management events to trigger the ONAP closed loops.“
P9 vCPE use-case
“Similarly, ONAP uses the APP -C component to manage the virtualization
infrastructure.”
ð “Similarly, ONAP uses the APP -C component to manage the VNF lifecycle“
P10&11 References/Links to the use case white papers are missing
“Read the Residential vCPE Use Case with ONAP whitepaper to learn more.”
“Read the VoLTE Use Case with ONAP whitepaper to learn more.”
Best Regards
Eric
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc
