There are two models for NFVO, VNFM and VIM interfacing.
One is direct model, where VNFM calls VIM directly.
The other is indirect model, where NFVO acting as the proxy between the two and calls VIM for the VNFM.
In either case, the VNFM could be a third party SVNFM or the
Hi Alok, Thanks for sharing this document. It is great to see it is evolving. I am curious about the maturity and applicability of these requirements/metrics. Are all the specifications aligned with ONAP Beijing implementation? Will it be
I believe we are using the composite pattern currently.
Why the decorator pattern would be better?
Lingli
发自网易邮箱大师
On 11/23/2017 05:03, John Strassner wrote: While I agree with the requirements that Andy said (e.g., a ServiceComponent should support multiple Services, and a ServiceComponent
not sure how the same word can be misspelled 3 times in an email and
not flagged as an error until I reply.
Best Regards,
-kenny
Kenny Paul, Technical Program Manager
kp...@linuxfoundation.org
510.766.5945
On Nov 13, 2017, at 4:14 PM, 邓灵莉/Lingli Deng <denglin...@chinamobile.com> wrote:
Hi
Hi Kenny
I am a raid that the link returns a error as Page not found.
Lingli
发送自 Windows 10 版邮件应用
发件人: Kenny Paul
发送时间: 2017年11月14日 8:04
收件人: onap-discuss; onap-tsc
抄送: Lisa Caywood
主题: [onap-tsc] Official ONAP Architecture Slide
As was pointed out in Paris there are too many variations of
