OpenStack Development Mailing List (not for usage
> questions)"
> *Date: *Thursday, 21 September 2017 at 4:59
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [vitrage] Extending
.
From: Muhammad Usman
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Thursday, 21 September 2017 at 4:59
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [vitrage] Extending Topology
Dear
Dear Ifat,
Usman is here. Previously, I contacted you for contributing to OpenStack
Vitrage project but could not follow up with you for sometime due to
various reasons.
However, to get actively involved in OpenStack project, I have decided to
join OpenStack Summit in Sydney.
Also, based on my
Hi,
Let me try and explain the more general use case.
You can query OVS for the switches information, and understand how they are
mapped to one another. This is not enough for knowing the exact route of the
network traffic for a certain VM.
A certain switch can be connected to more than one ot
Hello Ifat,
I tried to see more in depth about the issues you mentioned regarding
the extension of vSwitches. Due to a lot of complexity involved in
generating this topology and associated effects, I believe we need to
setup some baseline (e.g. adding a configuration file for specifying
bridges in
