There were around 40 new bpmns in Casablanca behind that API, if you want a 
review please setup a discussion.

Thanks

-Steve


From: "rene.rob...@orange.com" <rene.rob...@orange.com>
Date: Wednesday, September 19, 2018 at 8:31 AM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, "SMOKOWSKI, 
STEVEN" <ss8...@att.com>, OSIŃSKI Tomasz O-PL <tomasz.osins...@orange.com>, 
"viswanath.kumarskandpr...@verizon.com" <viswanath.kumarskandpr...@verizon.com>
Cc: RAJEWSKI Lukasz O-PL <lukasz.rajew...@orange.com>
Subject: RE: [E] [onap-discuss] Why we need manual SDN-C preloading?

A new BPMN behind that API ?

René

De : onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] De la 
part de Steve Smokowski
Envoyé : mercredi 19 septembre 2018 14:23
À : OSIŃSKI Tomasz O-PL; onap-discuss@lists.onap.org; 
viswanath.kumarskandpr...@verizon.com
Cc : RAJEWSKI Lukasz O-PL
Objet : Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

It should allow it on the newer GR-API Flow,  I do believe VID has a toggle 
mechanism to perform this.  The older VNF API flow does not support not using 
pre-load.  Be aware the GR-API flow is still under test in Casablanca, and is 
yet to reach full stability.

Here is a sample macro request with the input params supplied on the SO api.  
The data that was in preload can be placed under the instance-params section.


Thanks

-Steve


From: Osiński Tomasz 2 - Korpo <tomasz.osins...@orange.com>
Date: Wednesday, September 19, 2018 at 8:16 AM
To: "SMOKOWSKI, STEVEN" <ss8...@att.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>, "viswanath.kumarskandpr...@verizon.com" 
<viswanath.kumarskandpr...@verizon.com>
Cc: Rajewski Łukasz - Korpo <lukasz.rajew...@orange.com>
Subject: RE: [E] [onap-discuss] Why we need manual SDN-C preloading?

How I can pass these param sinto SO?

Thanks,
Tomek

[Logo Orange]

Tomasz Osiński, Główny Specjalista R&D
Orange Labs Polska, Wydział Rozwoju Zaawansowanych Systemów Sieciowych
Tel.: +48 50 130 06 88,
Orange Polska, Obrzeżna 7, 02-691 Warszawa
www.orange.pl<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.orange.pl&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=shs6nPzThSiGJml9VXN0Eg&m=O7F_jQT8orpjfVJpPVeFOJ4Xo-77ijtk-kTf09CMpnc&s=dtqtvgbpaGnogiUdcwMKIrRmg1Wm-13CgcxFuOcNSvg&e=>


From: SMOKOWSKI, STEVEN [mailto:ss8...@att.com]
Sent: Wednesday, September 19, 2018 2:14 PM
To: onap-discuss@lists.onap.org; viswanath.kumarskandpr...@verizon.com; Osiński 
Tomasz 2 - Korpo
Cc: Rajewski Łukasz - Korpo
Subject: Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

You don’t need preload, you can simply pass the params into SO.  It will still 
make a call to SDNC, but the data will just be sourced from the input.  This 
flow is being tested in Casablanca now.

Thanks

-Steve


From: <onap-discuss@lists.onap.org> on behalf of "Viswanath Kumar Skand Priya 
via Lists.Onap.Org" <viswanath.kumarskandpriya=verizon....@lists.onap.org>
Reply-To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, 
"viswanath.kumarskandpr...@verizon.com" <viswanath.kumarskandpr...@verizon.com>
Date: Wednesday, September 19, 2018 at 8:09 AM
To: onap-discuss <onap-discuss@lists.onap.org>, "tomasz.osins...@orange.com" 
<tomasz.osins...@orange.com>
Cc: "lukasz.rajew...@orange.com" <lukasz.rajew...@orange.com>
Subject: Re: [E] [onap-discuss] Why we need manual SDN-C preloading?

I second this comment. We are also having same question and infact we even 
tried to bypass this SDN-C preload check but not successful so far. We modified 
BPMN file to skip the SDN-C interaction altogether, however SO's state is still 
stuck in "In Progess" state.

IMHO SDN-C preload is optional step, shouldn't be introduced as a mandatory 
step in BPMN. There were lots of usecase specific work done in R1, primarily to 
just demo a particular usecase. However this is not changed even after moving 
to 2 releases.

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.verizon.com&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=shs6nPzThSiGJml9VXN0Eg&m=dUB_kX68vFzpvR-YUpwCeWLHd1rlZAr7VX-YKykgtME&s=rs7t5sFkU74Dq0ZtMV6KvmYtJSQg_Io9BreoC4sNoWI&e=>

Viswanath Kumar Skand Priya
Senior Architect
Technology, Architecture & Planning



On Wed, Sep 19, 2018 at 12:57 PM Tomek 
<tomasz.osins...@orange.com<mailto:tomasz.osins...@orange.com>> wrote:
Hello,

As in title, why we need manual SDN-C preloading in ONAP? We use and work with 
ONAP from Amsterdam release. It was surprising for us that there are some 
additional, manual steps needed to perform orchestration for any single VNF. We 
have currently ongoing development of Casablanca release and I don’t see the 
feature requests to automate SDN-C preloading in ONAP. In my opinion it’s just 
a matter of information exchange between SDC/SO/AAI/SDN-C.

Could you explain me why this manual step is still needed for ONAP? Is there 
any plan to automate it?

Regards,
Tomek

[Logo Orange]

Tomasz Osiński, Main R&D Specialist
Orange Labs R&D Center
Tel.: +48 50 130 06 88,
Orange Poland, Obrzeżna 7, 02-691 Warsaw
www.orange.pl<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.orange.pl_&d=DwMFBA&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ&m=ZTWnaPHZdfQOlWsKSFwliTGQt3zngjz-rz9zfV6rB9k&s=jLIhE0aOej3rXZ2aVPy9YwQPmpzYcnhbHriFWbo-H3o&e=>






_________________________________________________________________________________________________________________________



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.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12509): https://lists.onap.org/g/onap-discuss/message/12509
Mute This Topic: https://lists.onap.org/mt/25754741/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to