<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>As I have seen very large deployments still on nova networks <br><br>Inviato da iPhone</div><div><br>Il giorno 07/mag/2015, alle ore 12:56, BYEONG-GI KIM <<a href="mailto:kimbyeonggi@gmail.com">kimbyeonggi@gmail.com</a>> ha scritto:<br><br></div><blockquote type="cite"><div><div dir="ltr">Dear Joe<div><br></div><div>Thank you very much for the reply!</div><div><br></div><div>The answer is very helpful for me to understand what multi-host mode of nova-network exactly provides. By the way, in aspect of reliability, robustness and fault-tolerance for networking service on OpenStack, nova-network still seems better than neutron, the neutron provides lots of useful networking features though. I'd like to hear comments about this. </div><div><br></div><div>I'm now mainly focusing on analyzing how much high-availability can be guaranteed by each networking service type. I know the latest neutron provides distributed L3 service, i.e., DVR (Distributed Virtual Router) and can give high-availability via Pacemaker or something like that, but I'm not sure this can be said that the neutron is obviously better than nova-network in terms of the service continuity. </div><div><br></div><div>Regards</div><div><br></div><div>Byeong-Gi</div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-05-08 0:56 GMT+09:00 Joe Topjian <span dir="ltr"><<a href="mailto:joe@topjian.net" target="_blank">joe@topjian.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>If the nova-network service is down, then only actions that would involve nova-network (creating and terminating instances for example) won't work. Instances that are already running will still be able to communicate with both the outside network and other instances in the cloud.</div><div><br></div><div>You can easily test this by just stopping the nova-network service on the compute node (assuming you have a window where no one will be launching instances).</div><div><br></div><div>multi-host provides continuity in that each compute node becomes a network gateway for the instances hosted on that node. If that compute node is physically down, instances on all other compute nodes can still have external network access.</div><div><br></div><div>Contrast this with single-host networking where all traffic is routed through the single host. (Again, nova-network does not need to be running on that single host for traffic to still get out.) But if that single host is physically down, then *no* instances in your cloud have external network access.</div><div><br></div><div>Hope that helps,</div><div>Joe<br><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Thu, May 7, 2015 at 1:08 AM, BYEONG-GI KIM <span dir="ltr"><<a href="mailto:kimbyeonggi@gmail.com" target="_blank">kimbyeonggi@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hello.<div><br></div><div>It seems that this question would be quite outdated question, because this is a question about nova-network instead of neutron.</div><div><br></div><div>I wonder whether VMs located in a Compute Node, e.g., Compute A, are accessible while its nova-network service is down if the other nova-network is running on the other Compute Nodes, such as Compute B, Compute C, etc.</div><div><br></div><div>Or, does the multi-host just provide continuity of the networking service via avoiding single point failure?</div><div><br></div><div>Thanks in advance!</div><div><br></div><div>Regards,</div><div>Byeong-gi</div></div>
<br></div></div>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div>
</blockquote></div><br></div>
!DSPAM:1,554bc4d313714275170572!
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a></span><br><span>Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a></span><br><span>Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a></span><br><span></span><br><span></span><br><span>!DSPAM:1,554bc4d313714275170572!</span><br></div></blockquote></body></html>