This will include e.g. credentials usage, performance, resiliency, testing requirements etc.
We have no well defined approach to fault tolerance neither on the component nor the system level. Should this be part of the OOM scope with help of the architecture sub committee?
How to scale ONAP? Should this be part of the OOM scope with help of the architecture sub committee?
Common logging formats and approaches need to be supported and automated cross components monitoring tools should be developed/provided
See: https://lists.onap.org/pipermail/onap-tsc/2017-September/001684.html
The architecture & security sub committee should define a common security architecture which the projects need to agree to adopt.
What are the detailed rules of API depreciation. We did commit at the NJ F2F that APIs can’t just change between releases but we never agreed on the actual process/timeline surrounding API changes etc.