+1. Also, if you just need an additional IP for the instance that isn't used by other instances, you can do a port update and add additional IPs to the fixed_ips field.
On Tue, Dec 6, 2016 at 1:09 AM, Neil Jerram <n...@tigera.io> wrote: > Hi Vincent, > > Your initial observation is correct: each port is associated with a > Neutron network, and will get one IPv4 and one IPv6 address from the > subnets associated with that network. > > To add additional IPs to a port, you can use the allowed-address-pairs > extension. > > Regards, > Neil > > > *From: *Vincent.Chao > *Sent: *Tuesday, 6 December 2016 06:43 > *To: *OpenStack Development Mailing List (not for usage questions) > *Reply To: *OpenStack Development Mailing List (not for usage questions) > *Subject: *[openstack-dev] [neutron] Is it possible that creating a port > and binding it with 2 IPs > > Hi Neutrons, > > As my observation from the flow table, every created port seems bound with > only one IP address. > I was wondering is neutron support this function which can bind a port > with two IPs? > > For example, a VNF load balancer, which has a VIP and a real IP. > And this VNF receives packets with the destination of a VIP or a real IP > through one port. > > Any corrections or suggestions are welcome. > Thanks in advance. > > Vincent > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev