Hi Brian / Rene / Steven, Thanks for the pointers. I understand the need for preload during deployment and that's exactly what VID is trying to achieve . My only comment is about the mandatory flow that exists between SO and SDN-C, inspite of ignoring SDN-C for a deployment.
Runtime values could be supplied by N ways to VNFs and SDN-C is just one of them. If I don't depend on SDN-C for a network service ( both network & ip address assignment ) and I should be able to just talk to SO and VIM without the need to have additional flows. If SDN-C preload is unchecked, then why SO should talk to SDN-C ? BR, Viswa <http://www.verizon.com> Viswanath Kumar Skand Priya Senior Architect Technology, Architecture & Planning On Wed, Sep 19, 2018 at 6:10 PM Brian <bf1...@att.com> wrote: > Not sure. I usually test with the SDNC preload option. > > I suspect its only the .env parameters since the data is added to the > parameter line in the stack create when they match .env parameters and > ignored if not. > > SO might do other things with that data though. > > > > Brian > > > > > > *From:* Rajewski Łukasz - Korpo <lukasz.rajew...@orange.com> > *Sent:* Wednesday, September 19, 2018 8:38 AM > *To:* FREEMAN, BRIAN D <bf1...@att.com>; onap-discuss@lists.onap.org; > Osiński Tomasz 2 - Korpo <tomasz.osins...@orange.com> > *Subject:* RE: Why we need manual SDN-C preloading? > > > > Thanks Brian, it explains a lot. > > > > regarding the option 2, this file contains only values of parameters > specified in .env file for heat or there are some other ones required? > > > > Regards, > > > > [image: Logo Orange] > > *Łukasz Rajewski*, R&D Expert > Orange Labs Polska, Advancend Networking Systems Agency, Warsaw > *Mobile: +48 519 310 854* > Orange Polska, Obrzeżna 7, 02-691 Warszawa > www.orange.pl > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.orange.pl_&d=DwMFBA&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=fWJOo710tN2kqhd7qJ2uN_1a6ehkRcTodkyZv4qtlw8&s=GIHauSayjqdpsddFNx9pbkEVO8pYh7RcTrlOVw6hiEE&e=> > > > > > > *From:* FREEMAN, BRIAN D [mailto:bf1...@att.com <bf1...@att.com>] > *Sent:* Wednesday, September 19, 2018 2:31 PM > *To:* onap-discuss@lists.onap.org; Osiński Tomasz 2 - Korpo > *Cc:* Rajewski Łukasz - Korpo > *Subject:* RE: Why we need manual SDN-C preloading? > > > > Tomek, > > > > The issue is how to assign the per instance data that can not part of the > model that is used multiple times for instantiation. > > > > There are 3 mechanisms for setting that per instance data. > > > > 1. Preload to SDN-C where the instance specific hostnames , network > information needed for the VNF to do its function , ssh key etc can be set. > 1. VID users selects the “use sdnc preload” option and SO queries > for that data to SDNC at the VF Module instantiation > 2. As a json file uploaded to VID so that the same information is > provided to SO > > > 1. VID users selects the upload json file option instead of “use sdnc > preload” > 1. Automated SDN-C assignment where there is a controller design > studio template used to do “resource resolution” > > > 1. VID user doesnt select the use sdnc preload option > 2. As part of the process of VNF design – the network/service > designer creates the template for resource resolution and the > corresponding > policies for thing slike hostnames, query IP Address Management > subsystem > for assignments and any manually resolved data that came in from VID > > > > It is not a simple problem because the .env file’s that are provided with > the VNF heat template’s are not instance specific at model onboarding and > each service provider is likely to have unique naming conventions and > configuration policies they want to implement. > > > > > > Casablanca will see the initial availability of the Controller Design > Studio so you can see more of how the model/policy driven resource > resolution will work. > > > > Brian > > > > > > *From:* onap-discuss@lists.onap.org <onap-discuss@lists.onap.org> *On > Behalf Of *Tomek > *Sent:* Wednesday, September 19, 2018 3:27 AM > *To:* onap-discuss@lists.onap.org > *Cc:* Rajewski Łukasz - Korpo <lukasz.rajew...@orange.com> > *Subject:* [onap-discuss] Why we need manual SDN-C preloading? > > > > 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 > > > > [image: 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=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=83ShlKLJYHsQ8x6q-X8YL24wHFwZI4uTMmfo-m9Y1JA&s=KuxxUC2YWgnewrJqjRv6IFzS3UqpGd9L87qn88jUstc&e=> > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12511): https://lists.onap.org/g/onap-discuss/message/12511 Mute This Topic: https://lists.onap.org/mt/25755049/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
