[Openstack] transfer of IP address between ports

Kevin Benton kevin at benton.pub
Wed Aug 23 14:30:16 UTC 2017


If re-using the port isn't feasible. You can update the allocation pools on
the subnet to exclude the IP address in question. It's hacky, but doing
that before removing it from the original port will ensure it's not
automatically allocated to another port.

On Wed, Aug 23, 2017 at 8:17 AM, 공용준 <sstrato.kong at gmail.com> wrote:

> Hi
>
> You can use fixed ip port for this.
> create neutron port and attach it to the one vm.
> or
> you can use floating ip for this purpose as well
>
> Regards,
> Andrew
>
>
> 2017. 8. 23. 오후 10:58, Volodymyr Litovka <doka.ua at gmx.com> 작성:
>
> Hi colleagues,
>
> imagine, somebody (e.g. me :-) ) needs to transfer IP address between two
> ports. The straight way is: release IP address and then assign it to
> another port.
>
> The possible problem with this way is time between release and assignment
> - during this time, this IP address is in DHCP pool and can be
> automatically assigned to some another port upon request.
>
> Any ideas how to prevent leasing this IP address during this time?
>
> Thank you.
>
> --
> Volodymyr Litovka
>   "Vision without Execution is Hallucination." -- Thomas Edison
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20170823/eb492192/attachment.html>


More information about the Openstack mailing list