James,
>From a configuration standpoint, option one only requires adding the public
network to each compute node and some bridge/interface mapping changes.
However, the diagrams and traffic flows become more complex. I could split
the latter into two categories depending on whether a VM attaches
Hi Matt,
Commentary in-line.
On 05/12/15 14:03, Matt Kassawara wrote:
> The networking guide [1] contains deployment scenarios [2] that describe
> the operation of several common OpenStack Networking (neutron)
> architectures including functional configuration examples.
>
> Currently, the
Could you maybe go with option 1 and have the part allowing tenants to
attach directly to the external network at the bottom as a separate section?
"If you want to allow tenants to attach directly to these networks as well,
continue reading."
Then it has one step where you mark the network as
I wish it was that easy... the external network currently only attaches to
the network node.
On Sat, Dec 5, 2015 at 12:15 PM, Kevin Benton wrote:
> Could you maybe go with option 1 and have the part allowing tenants to
> attach directly to the external network at the bottom