<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 7/29/15 6:06 AM, Vijaya Bhaskar
wrote:<br>
</div>
<blockquote
cite="mid:CAMaq5FEOAiFSOSEa0F0MdrJ5bPO31hMVYXkVGFQah1V_jCy5_w@mail.gmail.com"
type="cite">
<div dir="ltr">If you can add additional compute nodes, then
create networks in neutron with the same network range as
nova-network and then migrate the VMs from old compute node to
new compute nodes with neutron support.<br>
</div>
</blockquote>
That is an inventive but Extremely Complex suggestion :) Neutron
doesn't support my current network topology so I'm not really
interested in switching... I just want want to move from one
nova-network node to another. (It doesn't help that block migration
is sort of broken in Icehouse.)<br>
<br>
-A<br>
<br>
<br>
<blockquote
cite="mid:CAMaq5FEOAiFSOSEa0F0MdrJ5bPO31hMVYXkVGFQah1V_jCy5_w@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jul 29, 2015 at 12:02 AM,
Andrew Bogott <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:abogott@wikimedia.org" target="_blank">abogott@wikimedia.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I'm
running Icehouse with the 'legacy' nova-network service and
a single network node.<br>
<br>
Everything in my cluster is running Ubuntu Trusty and ready
for an upgrade to Juno, except for my network node, which is
still running Precise. How do I upgrade it without causing
cloud-wide downtime? I can think of a few approaches, none
of which I feel confident about undertaking:<br>
<br>
1: Build a new network node running Trusty, and then nudge
existing VMs off of the old node and onto the new one. I've
gotten fairly far down this path, but just realized that I
don't have any idea how to do the 'nudge' step.<br>
<br>
2: Switch my network to multi-node mode, add a new network
node, somehow inform VMs about the new secondary node, then
upgrade and reboot network nodes one at a time and rely on
the instances to fail over to the running node during
upgrade.<br>
<br>
3: Stop having special-purpose network nodes altogether and
adopt the (more-modern, as I understand it) approach of
running nova-network on each compute node. This seems ideal
in the long run, but also maximize the amount of tinkering
and potential disaster.<br>
<br>
Has anyone done this? #2 seems like the obvious approach
since it gets me some redundancy in the long run, but I'm
not at all clear on what the steps are given an
already-running-and-useful network. I have the feeling that
I've read a guide about upgrade-via-migration which would
closely resemble #1 but I can no longer find that document.<br>
<br>
Thank you!<br>
<br>
-Andrew<br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:openstack@lists.openstack.org"
target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a moz-do-not-send="true"
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>
<br>
</div>
</blockquote>
<br>
</body>
</html>