[salv.orla...@gmail.com]
Sent: Wednesday, April 06, 2016 1:19 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Floating IPs and Public IPs are not equivalent
Hey! This sounds like bike-shedding & yak-shaving... totally my thing!
It is true that the Neu
Hey! This sounds like bike-shedding & yak-shaving... totally my thing!
It is true that the Neutron model currently kind of forces a two-level
topology, with the external network being a sort of special case.
Regardless, this does not mean you cannot assign directly public IPs to
your instances -
The main barrier to this is that we need to stop using the
'external_network_bridge = br-ex' option for the L3 agent and define a
bridge mapping on the L2 agent. Otherwise the external network is treated
as a special case and the VMs won't actually be able to get wired into the
external network.
*To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* [openstack-dev] Floating IPs and Public IPs are not equivalent
>>
>>
>> Just a friendly reminder to everyone - floating IPs are not synonymous
>> with Public IPs in OpenStack.
>>
mean.
>
> My face. It just fell off.
>
>
>> *From:* Monty Taylor
>> *Sent:* Thursday, March 31, 2016 10:23:22 AM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* [openstack-dev] Floating IPs and Public IPs are not equivalent
>>
10:23:22 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* [openstack-dev] Floating IPs and Public IPs are not equivalent
Just a friendly reminder to everyone - floating IPs are not synonymous
with Public IPs in OpenStack.
The most common (and growing, thank you
And with external rbac in mitaka, you can finally have private floating ip's. :)
Thanks,
Kevin
From: Monty Taylor
Sent: Thursday, March 31, 2016 10:23:22 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] Floating IPs
t; -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: Thursday, March 31, 2016 12:58 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] Floating IPs and Public IPs are not equivalent
>
> On 03/31/2016 01:23 PM, Monty Ta
, March 31, 2016 12:58 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Floating IPs and Public IPs are not equivalent
On 03/31/2016 01:23 PM, Monty Taylor wrote:
> Just a friendly reminder to everyone - floating IPs are not synonymous
> with Public IPs in Ope
On 03/31/2016 01:23 PM, Monty Taylor wrote:
> Just a friendly reminder to everyone - floating IPs are not synonymous
> with Public IPs in OpenStack.
>
> The most common (and growing, thank you to the beta of the new
> Dreamcompute cloud) configuration for Public Clouds is directly assign
> public
Just a friendly reminder to everyone - floating IPs are not synonymous
with Public IPs in OpenStack.
The most common (and growing, thank you to the beta of the new
Dreamcompute cloud) configuration for Public Clouds is directly assign
public IPs to VMs without requiring a user to create a
11 matches
Mail list logo
