Hi Srini, I agree with point 2 . However I want to emphaize on the fact that, this is still an issue and SO should be evolved to support dependency management and sequencing. W.r.t Point 1, I will equate K8S as VNFM for CNFs. So we can generalize the statement as, the dependency mgmt & sequencing within a VNF ( i.e between VF Modules ) is the responsibility of VNF-M . I don't think we can bring in Openstack / MC here within this paradigm. To me they are Infrastructure controllers, which does what has been told for. It is the VNFM / SO which does "orchestration" role.
BR, Viswa On Thu, Jan 3, 2019 at 2:39 AM Addepalli, Srinivasa R < [email protected]> wrote: > Can we say following: > > > > - Any dependency management among the workloads of a VF & VNF is > responsibility of VNFM, Multi-Cloud or the site orchestrator (such as > Openstack or K8S) > > - Any dependency management across VNFs in services is > responsibility of SO (This is not an issue today as each VNF/VF is brought > up independently from VID, as you said) > > > > Thanks > > Srini > > > > > > *From:* Kumar Skand Priya, Viswanath V [mailto: > [email protected]] > *Sent:* Wednesday, January 2, 2019 11:12 AM > *To:* Addepalli, Srinivasa R <[email protected]> > *Cc:* [email protected]; [email protected] > *Subject:* Re: [E] [Onap-arc] Dependency management across workloads > within VNF and across VNFs of a service > > > > Hi Srini, > > > > My 2 cents: > > > > I have raised this question much earlier during Amsterdam & Beijing DDF. > The answer I got from SDC & SO PTL is "Not yet". As of now today, latest > SDC is having a capability to specify dependency between VF-Module as part > of Network Service Design. SO doesn't regard dependency & sequencing at > all. As a matter of fact, when you instantiate via VID, the admin has to > manually add Vf-Modules as part of service instantiation, which makes is > completely manual and throw the burden of dependency management to human > actors. > > > > This is exactly the motivation behind model driven orchestration. On the > SO-BPMN side, similar functionality could be achieved by using techniques > like "Orchestration Hooks", like Pre & Post instantiation hooks. From my > enquiry with SO and CDS folks, this is what I learnt : There is a WIP item > that is targeting to develop these hooks inside SO, with the combination of > CDS controller plugins. Perhaps SO and CDS folks can comment on the same. > > > > BR, > > Viswa > > > > On Wed, Jan 2, 2019 at 10:01 PM Srini <[email protected]> > wrote: > > Hi, > > > > I came across a requirement where an application contains multiple > workloads, say A, B, C and D. > > Say that B and C depend on A to be ready and hence should be brought up > only after A is up and running. > > Say that D depends on B and C and hence should be brought up only after B > and C are up and running. > > > > I understand that in TOSCA, there is a way to create relationships and > have a way to insert scripts to check for readiness. So, I guess this is > taken care in use cases that are described using TOSCA. > > > > My question is with respect to SDC+SO+MC kind of orchestration. Is that > possible in this combination? If so, any pointers are appreciated. > > > > Thanks > > Srini > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14765): https://lists.onap.org/g/onap-discuss/message/14765 Mute This Topic: https://lists.onap.org/mt/28916725/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
