penstack/neutron-specs/specs/kilo/neutron-ipam.html
From: Padmanabhan Krishnan
Reply-To: Padmanabhan Krishnan
Date: Thursday, February 5, 2015 at 1:47 AM
To: John Belamaric , "OpenStack Development Mailing
List (not for usage questions)"
Subject: Re: [openstack-dev] [Neutron] fixed ip in
pecs.openstack.org/openstack/neutron-specs/specs/kilo/neutron-ipam.html
>
>
>
> From: Padmanabhan Krishnan
> Reply-To: Padmanabhan Krishnan
> Date: Thursday, February 5, 2015 at 1:47 AM
> To: John Belamaric , "OpenStack Development
> Mailing List (not for usage question
Padmanabhan Krishnan mailto:kpr...@yahoo.com>>
Reply-To: Padmanabhan Krishnan mailto:kpr...@yahoo.com>>,
"OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, December 17, 2014 at 6:06 PM
To:
"openstack-dev
c , "OpenStack Development Mailing
List (not for usage questions)"
Subject: Re: [openstack-dev] [Neutron] fixed ip info shown for port even when
dhcp is disabled
Some follow up questions on this.
In the specs, i see that during a "create_port", there's provisions to quer
gt;
Date: Wednesday, January 28, 2015 at 4:58 PM
To: John Belamaric mailto:jbelama...@infoblox.com>>,
"OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] fixed ip info shown for port even w
P relay so we can utilize external
> DHCP more easily.
>
> [1] https://blueprints.launchpad.net/neutron/+spec/neutron-ipam
> [2] https://etherpad.openstack.org/p/neutron-dhcp-org
> [3] https://blueprints.launchpad.net/neutron/+spec/dhcp-relay
>
> John
>
> From: Padmanabhan Kri
penStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] fixed ip info shown for port even when
dhcp is disabled
Some follow up questions on this.
In the specs, i see that during a "create_port&
-org[3]
https://blueprints.launchpad.net/neutron/+spec/dhcp-relay
John
From: Padmanabhan Krishnan
Reply-To: Padmanabhan Krishnan , "OpenStack Development
Mailing List (not for usage questions)"
Date: Wednesday, December 17, 2014 at 6:06 PM
To: "openstack-dev@lists.openstack.org"
t;openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [Neutron] fixed ip info shown for port even when
dhcp is disabled
This means whatever tools the operators are using, it need to make sure the IP
address assigned inside the VM matches with Openstack has assigned to the
port.Bringing
to:openstack-dev@lists.openstack.org>"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] fixed ip info shown for port even when
dhcp is disabled
This means whatever tools the operators are using, it need to make sure the IP
address assigned inside the
This means whatever tools the operators are using, it need to make sure the IP
address assigned inside the VM matches with Openstack has assigned to the
port.Bringing the question that i had in another thread on the same topic:
If one wants to use the provider DHCP server and not have Openstack's
I understood and I agree that assigning the ip address to the port is
not a bug, however showing it to the user, at least in Horizon dashboard
where it pops up in the main instance screen without a specific search,
can be very confusing.
On 12/16/14 12:25, Salvatore Orlando wrote:
> In Neutron IP
In Neutron IP address management and distribution are separated concepts.
IP addresses are assigned to ports even when DHCP is disabled. That IP
address is indeed used to configure anti-spoofing rules and security groups.
It is however understandable that one wonders why an IP address is assigned
Is there a specific reason for which a fixed ip is bound to a port on a
subnet where dhcp is disabled? it is confusing to have this info shown
when the instance doesn't have actually an ip on that port.
Should I fill a bug report, or is this a wanted behavior?
--
Pasquale Porreca
DEK Technologie
14 matches
Mail list logo
