Comment 3 for bug 1755414

Hi Miguel,

thanks for the responce.

Use case is the ability to easily switch VM between two subnets with
different address spaces, using same port on VM.

In the diagram, at different times VM can be connected:
- EITHER to Subnet1 (e.g. RFC1918 address space) and, thus, be NATed
using VR
- OR to Subnet2, and, thus, be globally accessible without VR

using single port, thus, having at the every one moment of time, just
one address on the port (either Subnet1's or Subnet2's), not two
addresses simultaneously.

This simplifies configuration on the VM (simple MAC-port binding (as
there is always one port), clear configuration as one port is, e.g.
single point of firewall rules), simplifies management and operations of
Openstack (one port per VM instead two ones per VM for such topologies)
and makes overall configuration is more clear.

Thank you.

On 6/15/18 4:43 PM, Miguel Lavalle wrote:
> I don't think I understand the use case behind this proposal. From a
> user point of view, what is it that you are trying to accomplish? Would
> you provide more details?
>

--
Volodymyr Litovka
   "Vision without Execution is Hallucination." -- Thomas Edison