-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] fixed ip info shown for port even when
dhcp is disabled
Hi John,
Sure, this may not be in the scope of IPAM as originally proposed in [1]. Am
just trying to see if there can be a solution for this scenario using IPAM.
What I had
(not for usage questions) openstack-dev@lists.openstack.org
Date: Wednesday, December 17, 2014 at 6:06 PM
To: openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] fixed ip info shown for port even
when dhcp is disabled
This means whatever
)
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] fixed ip info shown for port even when
dhcp is disabled
I have the feeling that the discussion is diverging a bit.
John is correctly stating that with pluggable IPAM it should be possible, in
theory to write a driver which
: Wednesday, January 28, 2015 at 4:58 PM
To: John Belamaric jbelama...@infoblox.com, OpenStack Development Mailing
List (not for usage questions) 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
...@infoblox.com,
OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto: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
kpr...@yahoo.commailto:kpr...@yahoo.com
Subject: Re: [openstack-dev] [Neutron] fixed ip info shown for port even when
dhcp is disabled
If we have ports without IPs, I don't think we need a placeholder, do we?
Wouldn't a port without an IP address be the same thing as a port with a
placeholder
) 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, there's provisions to
query the external source by Pluggable IPAM
@lists.openstack.org 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
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
openstack-dev@lists.openstack.orgmailto: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
@lists.openstack.org
Date: Wednesday, December 17, 2014 at 6:06 PM
To: openstack-dev@lists.openstack.org 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
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
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
12 matches
Mail list logo
