Open Stack

On Mon, Jun 01, 2015 at 08:50:17PM EDT, Hirofumi Ichihara wrote:
> 
> > Thanks for the clarification. Do you think that there are cases where
> > the value for PHYSICAL_NETWORK and PUBLIC_PHYSICAL_NETWORK will be different? 
> No, I cannot find the cases. I think it’s traditional something.
> 
> > Perhaps we can change the default value for PUBLIC_PHYSICAL_NETWORK from
> > "public" to just pulling in what PHYSICAL_NETWORK is set to, if it is
> > set?
> 
> Do you expect anything like the following?
> 
> PUBLIC_PHYSICAL_NETWORK=${PUBLIC_PHYSICAL_NETWORK:-$PHYSICAL_NETWORK}

I'd expect the above, where we pull the setting from PHYSICAL_NETWORK.
Then perhaps in the lib/neutron-legacy define

PHYSICAL_NETWORK={$PHYSICAL_NETWORK:-public}

> change PHYSICAL_NETWORK into PUBLIC_PHYSICAL_NETWORK in all the code.

I'd actually prefer we not change PHYSICAL_NETWORK ->
PUBLIC_PHYSICAL_NETWORK since that may just confuse people more. What if
your machine is not on a public network? What if it's just an isolated
networking lab that you want your instances to just plug into? I think
the "PUBLIC" part of the variable name is not going to apply all the
time.


-- 
Sean M. Collins