<div><div dir="auto">Good morning,</div><div dir="auto"><br></div><div dir="auto">Maybe external network without dhcp will do a work? It requires additional interface, like rackspace did initially in their cloud, but customer can maintain vrrp then in l2 network.</div><div dir="auto"><br></div><div dir="auto">--</div><div dir="auto">Misha</div><br><div class="gmail_quote"><div>пн, 28 серп. 2017 о 11:24 Volodymyr Litovka <<a href="mailto:doka.ua@gmx.com">doka.ua@gmx.com</a>> пише:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi Andrew,<br>
<br>
sorry for delay in responding, there were Ukrainian Independence Day
and we were on holidays, spending time with family and friends :)</div><div text="#000000" bgcolor="#FFFFFF"><br>
<br>
<div class="m_1964442808582161174moz-cite-prefix">On 8/24/17 6:36 PM, 공용준 wrote:<br>
</div>
<blockquote type="cite">
<div>
<blockquote type="cite">
<div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);float:none;display:inline!important">There is another scenario. It's going to be
public cloud and there can be few reasons to allow
customer to move pubic IP address between his VMs, e.g. he
built another VM using another OS for same role and need
to move this role from old VM to new VM, do not changing
other infrastructure's configurations. Five or ten seconds
of cool down time isn't a problem itself, since it's not
for high availability</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
</div>
</blockquote>
<div>Did you consider the lbaas for this purpose? I think
floating IP’s concept is good, but the implementation I think
we need to rethink about this. </div>
<div>and I thinks opentack’s octavia also do the job.<br>
</div>
</div>
</blockquote></div><div text="#000000" bgcolor="#FFFFFF">
Yes, I'm considering LBaaS, but as another service in my public
cloud :) So, don't want to provide it as part of base set of
services.<br>
<br>
I will check what you did in order to solve this issue, but
preliminary I think that you're right and floating IP is the best
solution for this (since don't require Openstack modification). The
only concern I have regarding floating IP is performance since NAT
is involved and this can lead to performance degradation. I think I
will provide two kinds of IP addresses - fixed and transferable. And
if somebody needs to preserve IP address between two different
instance, he will choose transferable IP for additional cost - this
will prevent massive NAT, on the one hand and will compensate
additional resources exhaustion, on the other.<br>
<br>
Thank you!</div><div text="#000000" bgcolor="#FFFFFF"><br>
<br>
<pre class="m_1964442808582161174moz-signature" cols="72">--
Volodymyr Litovka
"Vision without Execution is Hallucination." -- Thomas Edison
</pre>
</div>
_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</blockquote></div></div>