Locking Mechanism.

Priority

4

Summary

Support of locking mechanism that can prevent different parts of ONAP from accessing

Use Cases

Change Management

R1 Status

Not supported

R2 Status



In order to allow for coordination between different parts of the platform, mechanisms that provide that the same resources is not being modified by more than one source at a time is needed.

It is unclear if locking is something that should be in A&AI or is part of the Policy Engine (Perhaps this can be posed as a question to Arc Subcommittee?)