I don't have the bandwidth right now, but I might be able to fit it in among other work over the next while. Plus this would be a good reason to actually get into the Neutron code base a bit as it isn't one I've dug through before much.
Let's say yes for now, and any direction as to where to start looking would be good. To save me some time, even just some ideas of where in the current code base I should be looking, and where to start about with adding a new API. Chances are I can mostly reuse a large amount of the existing RBAC code, but what I'm curious of is how much of the existing models can be reused.
If possible using the existing models with some minor changes to them so the old API and the new can both use them would be ideal. Then the API itself is simply a different path/workflow to sharing a network. The old uses the old method and goes straight to the shared state, while the new handles the in between stage (pending), and the acceptance step action. Hopefully that is possible, otherwise we may have to duplicate some functionality.
I don't have the bandwidth right now, but I might be able to fit it in among other work over the next while. Plus this would be a good reason to actually get into the Neutron code base a bit as it isn't one I've dug through before much.
Let's say yes for now, and any direction as to where to start looking would be good. To save me some time, even just some ideas of where in the current code base I should be looking, and where to start about with adding a new API. Chances are I can mostly reuse a large amount of the existing RBAC code, but what I'm curious of is how much of the existing models can be reused.
If possible using the existing models with some minor changes to them so the old API and the new can both use them would be ideal. Then the API itself is simply a different path/workflow to sharing a network. The old uses the old method and goes straight to the shared state, while the new handles the in between stage (pending), and the acceptance step action. Hopefully that is possible, otherwise we may have to duplicate some functionality.