<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi Volodymyr</div><div class=""><br class=""></div><div class="">From my understanding, Do you need to maintain same IP address between port(and Mac will be changed)?</div><div class="">If that, it will be hard because there’s some cool down time(something like reuse ip timeout) in the neutron IPAM db. If my memory is right, it was ten or five sec. </div><div class=""><br class=""></div><div class="">Actually, I’m using the same kind of scenario here( same ip address to different neutron port)</div><div class="">I changed neutron db schema so it can assign same ip address to different port ( I also changed the neutron policy. only admin can use this function)</div><div class="">In this scenario, </div><div class="">If i need to have a new port with the previous IP, </div><div class="">I just create new port with the same IP. and I use this function to achieve the ECMP in our cloud. </div><div class=""><br class=""></div><div class="">Regards, </div><div class="">Andrew</div><br class=""><div><blockquote type="cite" class=""><div class="">2017. 8. 23. 오후 11:30, Volodymyr Litovka <<a href="mailto:doka.ua@gmx.com" class="">doka.ua@gmx.com</a>> 작성:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class=""><font face="SFNS Display" class="">Hi Andrew,</font></p><p class=""><font face="SFNS Display" class="">thanks for the prompt reply.</font></p><p class=""><font face="SFNS Display" class="">I'm using fixed ip addresses, not
floating IPs. In terms of Heat it looks like there:</font></p><p class=""><font face="SFNS Display" class="">n1-wan:<br class="">
type: OS::Neutron::Port<br class="">
properties:<br class="">
name: n1-wan<br class="">
network: e-net<br class="">
fixed_ips: [ { subnet: e-subnet, ip_address: X.X.X.X } ]</font></p><p class=""><font face="SFNS Display" class="">n1:<br class="">
type: OS::Nova::Server<br class="">
properties:<br class="">
name: n1<br class="">
networks:<br class="">
- port: { get_resource: n1-wan }<br class="">
</font></p><p class=""><font face="SFNS Display" class="">and there are some constraints in my
installation:</font></p>
<ol class="">
<li class=""><font face="SFNS Display" class="">I can't move ports between VMs (in
order to support predictable naming according to port roles,
their MAC addresses are stored in udev rules inside VM and if
I will change port, rules/roles will fail)</font></li>
<li class=""><font face="SFNS Display" class="">I don't want to use floating ip due
to possible performance degradation when using massive NAT</font></li>
</ol>
Another idea I have is to move ports between VMs, changing their
MACs accordingly and will try it if no other ways will be found :)<br class="">
<br class="">
Thanks again.<br class="">
<br class="">
<div class="moz-cite-prefix">On 8/23/17 5:17 PM, 공용준 wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:85E5345E-8C59-4E53-8193-54779CAC8DB0@gmail.com" class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
Hi
<div class=""><br class="">
</div>
<div class="">You can use fixed ip port for this. </div>
<div class="">create neutron port and attach it to the one vm. </div>
<div class="">or </div>
<div class="">you can use floating ip for this purpose as well </div>
<div class=""><br class="">
</div>
<div class="">Regards, </div>
<div class="">Andrew</div>
<div class=""> </div>
<div class="">
<div class="">
<blockquote type="cite" class="">
<div class="">2017. 8. 23. 오후 10:58, Volodymyr Litovka <<a href="mailto:doka.ua@gmx.com" class="" moz-do-not-send="true">doka.ua@gmx.com</a>> 작성:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="content-type" content="text/html;
charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class=""><font class="" face="SFNS Display">Hi
colleagues,</font></p><p class=""><font class="" face="SFNS Display">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.</font></p><p class=""><font class="" face="SFNS Display">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.<br class="">
</font></p><p class=""><font class="" face="SFNS Display">Any ideas
how to prevent leasing this IP address during this
time?</font></p><p class=""><font class="" face="SFNS Display">Thank
you.</font><br class="">
</p>
<pre class="moz-signature" cols="72">--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison
</pre>
</div>
_______________________________________________<br class="">
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="" moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class="">
Post to : <a href="mailto:openstack@lists.openstack.org" class="" moz-do-not-send="true">openstack@lists.openstack.org</a><br class="">
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="" moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison
</pre>
</div>
</div></blockquote></div><br class=""></body></html>