Hi Preload is about providing some Heat parameters value at instantiation time. Without preload, your Heat stack will use default values from your Heat templates coming from SDC (after distribution). For example, “image name” or “flavor name” are not the same from one VIM to another VIM.
You are right, the way it works today in Beijing is not satisfying. My proposal would be to replace that SDNC preload by the possibility to provide parameters/values via SO API and to use a BPMN that would use those parameters/values. That means to be able to define and add a new BPMN (I do not know how to do that) If anyone can share the procedure to add a new BPMN, we could try work on it. Regards René [Logo Orange]<http://www.orange.com/> René Robert «Open and Smart solutions for autOmating Network Services» ORANGE/IMT/OLN/CNC/NARA/OSONS Fixe : +33 2 96 07 39 29 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2096%2007%2039%2029> Mobile : +33 6 74 78 68 43 <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2074%2078%2068%2043> rene.rob...@orange.com<mailto:rene.rob...@orange.com> De : onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] De la part de Viswanath Kumar Skand Priya via Lists.Onap.Org Envoyé : mercredi 19 septembre 2018 14:07 À : onap-discuss; OSIŃSKI Tomasz O-PL Cc : RAJEWSKI Lukasz O-PL Objet : 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$]<http://www.verizon.com> 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 (#12501): https://lists.onap.org/g/onap-discuss/message/12501 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] -=-=-=-=-=-=-=-=-=-=-=-
