Hi, How about moving L3 & dhcp agents as well as other networking services to other node? Multiple nodes having L3 and dhcp agents are supported since Grizzly. So you don't need to have dedicated network node for these agents. You'll probably need to recreate (or reschedule) routers if you have any, but it seems like your VMs should continue working and have connectivity (within tenant private network)
Thanks, Eugene. On Thu, Sep 12, 2013 at 10:44 AM, Geraint Jones <[email protected]> wrote: > As far as I am aware you are in for an outage no matter how you do it. > However I am very interested in the answer to this as I am going to have to > do the same very soon to upgrade our network node. > > Sent from my iPhone > > On 12/09/2013, at 6:36 PM, Jitendra Kumar Bhaskar <[email protected]> > wrote: > > Hi All, > > Openstack setup is running on test environment with three nodes( 4 compute > , 1 network and 1 cloud). Every thing is working fine but I need to change > network node due to some hardware issue. Already more than 10 vms are > running. I am not getting any way ? So without interrupting of existing > VM's how can I replace network node ? > > Regards* > Jitendra Bhaskar* > > > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
