Currently we have limitations for our network verification architecture.
It is ok from the point of orchestration, but pretty ugly in terms of reporting and UI.
Some time ago i was proposing approach where we will have separate tab (or same as HealthCheck)
with all kinds of pre-deployment verifications enabled. It requires significant amount of work todo, and i am not sure
when i will have that free time.
If you want just prepare package and run it manually - it is very simple..
But speaking of automation and integration it with our orchestrator/nailgun - it will require development and
testing, so i prefere to track this activity as BP.
Currently we have limitations for our network verification architecture.
It is ok from the point of orchestration, but pretty ugly in terms of reporting and UI.
Some time ago i was proposing approach where we will have separate tab (or same as HealthCheck)
with all kinds of pre-deployment verifications enabled. It requires significant amount of work todo, and i am not sure
when i will have that free time.
If you want just prepare package and run it manually - it is very simple.. nailgun - it will require development and
But speaking of automation and integration it with our orchestrator/
testing, so i prefere to track this activity as BP.
https:/ /blueprints. launchpad. net/fuel/ +spec/ovs- test-part- network- verification