+1
De : Kanagaraj Manickam [mailto:[email protected]]
Envoyé : mercredi 15 novembre 2017 06:00
À : TALASILA, MANOOP (MANOOP); Kenny Paul; Lisa Caywood
Cc : Sabater, Susana, Vodafone Spain; CHAWKI Jamil IMT/OLN; onap-discuss;
onap-tsc
Objet : RE: [onap-tsc] Official ONAP Architecture Slide
Dear Kenny,
I would like share my point of view :
As Manoop mentioned below, It would be better, if we could bring Portal, ONAP
CLI span across Design Time and Run-Time services similar to OOM reported now.
May be something as follows:
[cid:[email protected]]
ONAP service (design time & Run time)
Regards
Kanagaraj M
***************************************************************************************
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**************************************************************************************
***************************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email immediately
and delete it!
***************************************************************************************
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of TALASILA, MANOOP
(MANOOP)
Sent: Wednesday, November 15, 2017 8:27 AM
To: Kenny Paul; Lisa Caywood
Cc: Sabater, Susana, Vodafone Spain;
[email protected]<mailto:[email protected]>; onap-discuss; onap-tsc
Subject: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide
Also, the Portal platform should be represented across the architecture on the
top of the diagram similar to OOM, as the operators/users access both
“design-time” and “run-time” applications through Portal platform (for example
VID, AAI, SDC and Policy apps).
Manoop
From: "TALASILA, MANOOP (MANOOP)"
<[email protected]<mailto:[email protected]>>
Date: Tuesday, November 14, 2017 at 9:42 PM
To: Kenny Paul <[email protected]<mailto:[email protected]>>,
Lisa Caywood <[email protected]<mailto:[email protected]>>
Cc: onap-discuss
<[email protected]<mailto:[email protected]>>, onap-tsc
<[email protected]<mailto:[email protected]>>,
"[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>, "Sabater, Susana,
Vodafone Spain"
<[email protected]<mailto:[email protected]>>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide
Hi Kenny,
In the Architecture slide, can we please rename “Portal Framework - UI” ->
“ONAP Portal Platform”? as it is not just UI (I hear this misconception most of
the time), it provides many backend application integration services along with
a runtime dashboard. Thanks.
Manoop
From: <[email protected]<mailto:[email protected]>>
on behalf of "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Date: Tuesday, November 14, 2017 at 10:29 AM
To: "Sabater, Susana, Vodafone Spain"
<[email protected]<mailto:[email protected]>>, Lisa Caywood
<[email protected]<mailto:[email protected]>>
Cc: onap-discuss
<[email protected]<mailto:[email protected]>>, onap-tsc
<[email protected]<mailto:[email protected]>>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide
Hi Susana
Ok in this case we have to remove this from VFC.
Regards
jamil
De : Sabater, Susana, Vodafone Spain [mailto:[email protected]]
Envoyé : mardi 14 novembre 2017 16:26
À : Lisa Caywood; CHAWKI Jamil IMT/OLN
Cc : onap-discuss; onap-tsc
Objet : RE: [onap-tsc] Official ONAP Architecture Slide
And maybe it is wise to avoid making any statement that “ONAP is functionally
aligned with ETSI NFV architecture”, since it will deeply confuse the audience
trying to see the alignment.
Cheers
/Susana
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Lisa Caywood
Sent: Tuesday, November 14, 2017 4:19 PM
To: CHAWKI Jamil IMT/OLN
<[email protected]<mailto:[email protected]>>
Cc: onap-discuss
<[email protected]<mailto:[email protected]>>; onap-tsc
<[email protected]<mailto:[email protected]>>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide
Jamil, we can not spell out the names of all of the components on the slide;
there isn't room. It must be legible, including from a distance (eg in a public
presentation).
Chris can answer #2.
Thanks, Lisa
On Tue, Nov 14, 2017 at 7:14 AM,
<[email protected]<mailto:[email protected]>> wrote:
Hello Kenny
Additional comments and proposals on this figure:
1- Remove ETSI NFV alignment from VFC and to replace it by a general note
that ‘ONAP is functionally aligned with ETSI NFV architecture’
2- We need to remove AWS, Rackspace and Azure. Why Rackspace is listed and
not WindRiver ?
3- MultiCloud Infrastructure Adaptation Layer => it is not an adaptation
layer today. Replace it by Multi VIM/Cloud (official project name).
4- Replace SDN-C by SDN Controller, similar to Application Controller
5- VVP, VNF Requirements, Modelling, Testing & integration are not
mentioned in the architecture
a. Proposals:
i. To add Requirements and
Validation with VNF SDK.
ii. To add Modelling with CLAMP
iii. To add Test and Integration
with OOM
6- We need to avoid the abbreviations like AAF, OOF …
a. Proposal to replace:
i. SDC by Service Design Creation
ii. Clamp by Closed Loop Design
iii. DMaaP by Data Movement
iv. A&AI by Active & Available
Inventory
v. Holmes by Fault Correction
vi. DCAE by Data Collection
Analytics and Events
vii. AAF by Application Authorization
Framework
viii. CC SDK Common Controller SDK
ix. OOF by Optimization Framework
Regards
jamil
De : [email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide
As was pointed out in Paris there are too many variations of the Amsterdam
architecture which is bad to say the least.
The officially approved image for the Amsterdam Architecture and be found here:
https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_download_attachments_1015842_ONAP-2520Amsterdam-2520arch.png-3Fapi-3Dv2&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=jAJ95dk3e1UHkL1cYqAbaaAXHSHJ4dLCutxks9qN9hk&s=dM-Lut2Wm8s10yOB1USwcWV1OZArlmYba0b_ddZg3wU&e=>
In preparation for the release announcement here is what we are asking in order
of priority:
-If an archecture image is referecned in your official readthedocs
documentation, please use this image
-If an archecture image is referenced in your wiki pages, please add the URL
above to reference the the image.
-If an archecture image is referecned in a presentation slide deck, please
ensure you use this image.
I am intentionally NOT distributing it because that is how we ended up with so
many versions in the first place. :-)
Thanks!
Best Regards,
-kenny
Kenny Paul, Technical Program Manager
[email protected]<mailto:[email protected]>
510.766.5945<tel:(510)%20766-5945>
_________________________________________________________________________________________________________________________
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.
--
______________
Lisa Caywood
Director of Ecosystem Development
OpenDaylight<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opendaylight.org_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=jAJ95dk3e1UHkL1cYqAbaaAXHSHJ4dLCutxks9qN9hk&s=cM18DDpCOBha6jyO4Ae7-LG5EZvhLHTasm8pT6xPkEg&e=>
and
ONAP<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.onap.org_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=jAJ95dk3e1UHkL1cYqAbaaAXHSHJ4dLCutxks9qN9hk&s=shsZhD4ktnED9LAS9xeIpY56X3cMIuWeNOmsHhk2-FE&e=>
Projects
[email protected]<mailto:[email protected]>
+1 (408) 857-3642
Skype: RealLisaC
Twitter: @RealLisaC
_________________________________________________________________________________________________________________________
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.
_________________________________________________________________________________________________________________________
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-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
