Late to the party, better than ever. https://github.com/openstack/neutron/blob/master/etc/policy.json#L90
On Sun, Aug 28, 2016 at 8:29 AM, William Josefsson <[email protected]> wrote: > yes thanks Kyle, I checked the neutron db and noticed there's a table called > ipallocations which seems to be link between port and the assigned VM IP > address. So even in the event I need to replace a crashed Neutron Networking > node, hopefully the IP addresses will be retrieved from the DB. thx will > > On Sun, Aug 28, 2016 at 12:26 AM, Kyle Greenwell <[email protected]> wrote: >> >> If I'm not mistaken, the ip is assigned to the neutron port, and that is >> assigned to the vm. As long as the instance doesn't get blown away and >> rebuilt with a different neutron port you won't be at risk of losing the ip. >> >> Sent from my iPhone >> >> On Aug 27, 2016, at 3:23 AM, William Josefsson >> <[email protected]> wrote: >> >> thanks Lubosz! I should explore further if floating IPs will help here. >> >> Can you also please clarify if VM IP is stored in the DB the IPs that have >> been assigned to a VM so there should be no risk of the dhcp giving it a new >> IP suddenly? That would cause a nightmare with real tenants soon coming >> onboard my deploy. I know there are some dnsmasq dhcp files in >> /var/lib/neutron/ on my Networking nodes, but what if I replace one of them >> with a fresh install, will the necessary vm details such as IP etc. be >> retrieved from the DB? thx will >> >> On Sat, Aug 27, 2016 at 12:17 AM, Kosnik, Lubosz <[email protected]> >> wrote: >>> >>> Lubosz is my first name not Kosnik :P >>> You can create a VM from Horizon and only specify the floating IP to be >>> exactly that one. With private networks it’s not available from Horizon. >>> About getting every time the next IP it’s normal thing. After getting the >>> roof for that specified IP range it will start looking for free IPs from the >>> beginning of the range. >>> >>> Cheers, >>> Lubosz Kosnik >>> Cloud Software Engineer OSIC >>> [email protected] >>> >>> On Aug 26, 2016, at 11:06 AM, William Josefsson >>> <[email protected]> wrote: >>> >>> Hi Kosnik. thanks. Is there any way in the GUI for the user to do that, >>> or they need to do cli 'neutron port-create ...' ? >>> Maybe I can pre-create the fixed IPs as admin, but how do a standard >>> tenant user select the Ports just created .. just as they select the >>> Networks/Subnets during 'Launch an instance'? >>> >>> I notice while provisioning that the IP number increments all the time, >>> even if previous instances with lower IPs are deleted. What will happen >>> eventually when I reach the last IP, will the lower number IPs be reused, or >>> what would the behavior be? thx will >>> >>> >>> >>> On Thu, Aug 25, 2016 at 10:58 PM, Kosnik, Lubosz >>> <[email protected]> wrote: >>>> >>>> VM always will get the same IP from DHCP server. To prepare the VM with >>>> fixed IP you need using neutron create a port in specified network with >>>> specified IP and after that to boot new VM you’re specifying not net-id but >>>> port-id and it’s gonna work. >>>> >>>> Cheers, >>>> Lubosz Kosnik >>>> Cloud Software Engineer OSIC >>>> [email protected] >>>> >>>> On Aug 25, 2016, at 9:01 AM, William Josefsson >>>> <[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> I wonder if there's any way of allowing my users to select fixed IPs for >>>> the VMs? I do shared Provider networks, VLAN on Liberty/CentOS. >>>> >>>> I know nova boot from the CLI or API has v4-fixed-ip=ip-addr option, >>>> however is there any way in the Dashboard where the User can select static >>>> IP? >>>> >>>> I would also appreciate if anyone can explain the default dnsmasq dhcpd >>>> lease. Will a VM always get the same IP during it's life time, or it may >>>> change? thx will >>>> _______________________________________________ >>>> OpenStack-operators mailing list >>>> [email protected] >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>>> >>>> >>> >>> >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
