That's true. But if you have more physical interfaces, you can get the
installation without tagged ports. BTW, we had limitation before in FuelWeb
- we didn't have an ability to not to use tags.


On Tue, Oct 15, 2013 at 12:52 PM, mattymo <notifications@github.com> wrote:

> In pages/install-guide/networks.rst:
>
> > @@ -58,24 +58,24 @@ FlatDHCPManager (single-interface scheme)
> >  .. image:: /_images/flatdhcpmanager-sh_scheme.jpg
> >    :align: center
> >
> > -Therefore all switch ports where Compute nodes are connected must be
> > -configured as tagged (trunk) ports with required VLANs allowed (enabled,
> > -tagged). Virtual machines will communicate with each other on L2 even if
> > -they are on different Compute nodes. If the virtual machine sends IP packets
> > -to a different network, they will be routed on the host machine according to
> > -the routing table. The default route will point to the gateway specified on
> > -the networks tab in the UI as the gateway for the Public network.
> > +In order for FlatDHCPManager to work, all switch ports where Compute nodes are
> > +connected must be configured as tagged (trunk) ports with the required VLANs
>
> This is when you have a single network port for your compute, instead of 3
> like we usually do. Is this scenario supported still? You can't make this
> work without vlan tagging afaict.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/Mirantis/fuel-docs/pull/26/files#r6965472>
> .
>



-- 
Mike Scherbakov