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.
* 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
* VID users selects the upload json file option instead of "use sdnc
preload"
3. Automated SDN-C assignment where there is a controller design studio
template used to do "resource resolution"
* VID user doesnt select the use sdnc preload option
* 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
[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 (#12518): https://lists.onap.org/g/onap-discuss/message/12518
Mute This Topic: https://lists.onap.org/mt/25753419/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
