Hi, In “K8S based Cloud region support” feature too, there is similar problem statement where a given VNF (we call it as resource bundle) can have many workloads, networks and volumes. These workloads are dependent on each other and hence there is a need for relationship bindings. For example, say if there are 4 workloads, A, B, C and D. The requirement could be that C has to be brought up only when A is completed and B is ready. D can come up in parallel. We are thinking of using DAG approach to provide these relationships and criteria to move to next stage in the pipeline. We are still in design phase of this sub-feature.
I am guessing that you require similar DAG for your micro-service too. Thanks Srini From: [email protected] [mailto:[email protected]] On Behalf Of Eidelman, Jonathan Sent: Thursday, January 24, 2019 10:39 AM To: Shankar Narayanan <[email protected]>; [email protected] Subject: Re: [onap-discuss] [SO] Queuing SO requests for resources Hi Shankar, Yes, in fact that is more or less what I had in mind. The idea is that if SO requires exclusive use of some resources (lets say locks for switches, but could be something else), SO sends a call to this microservice asking for those resources. Then the microservice keeps queues for each resource and puts this SO request in the relevant queues. Whenever an SO request is able to run (because it is first in line in some queue and all resources are available), the microservice communicates that to the SO request, which then goes forward knowing that it has exclusive access to the resources. The advantage of this is that if two requests do not need the same resources, they can go in parallel. I'm very open to other ways of achieving this too so please feel free to suggest things! Best, Jonathan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15158): https://lists.onap.org/g/onap-discuss/message/15158 Mute This Topic: https://lists.onap.org/mt/29526109/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
