I have attempted to use the fixed_ip for our internal use.
I found too many issues with the existing feature, and would propose to rewrite
it as new feature.
The problem I experienced are:
1. ) I have to repeatedly enter the option --fixed_ip for as many IPs as I need
to apply. This will not scale if I wanted many IPs.2). The operation does not
guarantee you get your original IP assigned, the VM instance become
non-reachable.3). I can not requested seperate MAC addresses to go with the IP
address.4.) The command acces privilage is controlled by policy. It would be
more appropriate to use quota to control how many IPs a user can request
instead of granting a privilage to the user.
To use the mulitple IP,you can use OVS, mac-vlan etc. But that requires
seperate MAC address to go with IPs.
== Aihua Edward Li ==
On Friday, October 30, 2015 12:00 PM, Shraddha Pandhe
<spandhe.openst...@gmail.com> wrote:
Hi folks,
James Penick from Yahoo! presented a talk on Thursday about how Yahoo uses
Neutron for Ironic. I would like to follow up on one particular use case that
was discussed: Multi-IP support.
Here's our use-case for Multi-ip:
For Ironic, we want user to specify the number of IPs on boot. Now, we want
scheduler to find a network with sufficient IPs and then pick a host in that
subnet (Note: static IPs for baremetal). Now, when allocating network, we want
to assign all requested IPs from the same subnet as the host's static IP. Also,
we don't want to configure those IPs on the host. We only want to display them
on "nova show".
So basically we will only create one port for the host, and append all
fixed_ips in the ports fixed_ip list field.
Questions:1. Hows do most people use the fixed_ips field in the port? What are
different ways you can populate multiple IPs in fixed_ips? One way I know is,
using neutron-client to create port, you can specify --fixed-ip as many times
as you want, and that will append fixed_ips to the port. Any other way?
2. Is anybody else using multi-ip?
__________________________________________________________________________
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
