Comment 8 for bug 1575146

We're considering whether solution to bug 1598081 may come handy to address this issue. We are partially reluctant to add deployment/topology complexity into Neutron right now and it might be easier to allow third parties to trigger a status change on the port based on their own logic and orchestration. However, depending on the level of pluggability of [1], it might be possible to address this type of need by means of the diagnostics API/framework (still in the works). Please review the logs and provide further feedback.

I'll let Ihar chime in with further comments.

[1] https://blueprints.launchpad.net/neutron/+spec/troubleshooting