Hello

I have found the “custom” BPMN that handle the TunnelXCon instantiation via SO.

Then, I wonder if it is always necessary to create such kind of “custom” BPMN 
when having to instantiate an allotted resource ?

Also, I do not understand how SO is able to find the related service/VNF 
instance on which the allotted resource will have to be configured by SDN-C ?

Best regards

René


De : ROBERT René TGI/OLN
Envoyé : mercredi 15 mai 2019 13:50
À : 'Gil Bullard'; onap-discuss@lists.onap.org
Objet : RE: [onap-discuss] [AAI] vnf instance relationship with service instance

Hello Gil,

I have read again the vCPE use-case to better understand allotted resources.

I think I understand well the idea : a way to model a “resource” that is 
provided by a VNF.

But I do not see anywhere how to proceed to instantiate that allotted resource.

At one point, it will be necessary to send a SO request in order to instantiate 
a TunnelXCon on a vGMux.

Can someone share that SO request ?

Best regards



De : Gil Bullard [mailto:gil.bull...@att.com]
Envoyé : jeudi 9 mai 2019 18:45
À : ROBERT René TGI/OLN; onap-discuss@lists.onap.org
Objet : Re: [onap-discuss] [AAI] vnf instance relationship with service instance

Rene, there are two use patterns that I can envision in this case:
a) The VNF is providing some "shared service" to the various service instances 
which are implemented via another VNF(s), and the "shared VNF" is not aware of 
the "other VNF".  E.g., the "shared VNF" is providing DNS service to a set of 
VNF instances of type VNF x.  In this case we would want to wrap the DNS VNF in 
its own separate "service", because we want the VNF x instances to just see the 
DNS VNF as a "service" to be accessed, and we don't want the DNS VNF to know 
too much about its clients.  So I would model the DNS VNF as part of an SDC 
"DNS Service", and model VNF x as part of a different SDC "Service x".  Thus, 
the service instance to which the DNS VNF instance belongs is different than 
the service instance to which a VNF x instance belongs.  If this is what you 
are trying to model, I am not aware of how to model such a service type to 
service type relationship in SDC, or a service instance to service instance 
relationship in A&AI.
b) The "shared VNF" is directly involved in the various service instances and 
is in fact aware of the service instances.  E.g., the VNF is a "shared 
firewall" infrastructure VNF in which one can create instances of "firewall 
experience" for various customers through configuration.  There is current 
support in A&AI for modeling this, which we demonstrated in the Amsterdam 
release "Residential Broadband" use case via the "vCpeResCust" SDC Service, 
particularly the "TunnelXConn" Allotted Resource which has an A&AI association 
with the "vGMUX" shared VNF.  See 
https://wiki.onap.org/pages/viewpage.action?pageId=3246168.  Note however that 
we are proposing a change to the SDC modeling and A&AI support for Allotted 
Resources, a proposal that I presented at the F2F and which will be discussed 
on an upcoming Architecture team call.  See email thread between myself and 
Ciaran Johnston on onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> for 
more information.

_________________________________________________________________________________________________________________________

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 (#17037): https://lists.onap.org/g/onap-discuss/message/17037
Mute This Topic: https://lists.onap.org/mt/31553090/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