Hello everyone! I am on the Bell team working with ONAP, and we have a use case where SO must configure a set of switches, and that configuration must be done as a single transaction. In other words, it has to seem like all of the switches were configured at the same time. The result is that we have to lock the switches. The problem that we run in to is that because we will have an error if two different SO requests try to lock the same ToR, we have to send requests to SO one at a time. This is unnecessarily inefficient.
Is there already a way of dealing with this sort of problem upstream? I have put together a proof of concept for a microservice that would choose which SO requests can go and which have to wait, allowing as much parallelism as possible given the resource dependencies. But I was wondering whether something along these lines exists already. Let me know! Jonathan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15149): https://lists.onap.org/g/onap-discuss/message/15149 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]] -=-=-=-=-=-=-=-=-=-=-=-
