summaryrefslogtreecommitdiffstats
path: root/nova/openstack
diff options
context:
space:
mode:
authorDavid McNally <dave.mcnally@hp.com>2012-08-08 16:20:23 +0100
committerDavid McNally <dave.mcnally@hp.com>2012-08-10 09:41:26 +0100
commit8f1c54ce98fed9cb7384be9cbb9f28eba2f12c2d (patch)
treed37724bc663d1a12afad1ae95cadf876d5d919a5 /nova/openstack
parent043e3f5981d89d35aa8bb8f1c42561c38451dfc4 (diff)
downloadnova-8f1c54ce98fed9cb7384be9cbb9f28eba2f12c2d.tar.gz
nova-8f1c54ce98fed9cb7384be9cbb9f28eba2f12c2d.tar.xz
nova-8f1c54ce98fed9cb7384be9cbb9f28eba2f12c2d.zip
Compute restart causes period of network 'blackout'
Fixes bug 1034401 When a compute service is restarted each instance running on the host has its iptables rules built and applied sequentially during the host init stage. The impact of this, especially on a host running many instances, can be observed as a period where some instances are not accessible as the existing iptables rules have been torn down and not yet re-applied. The presented work-around for this is a configurable/flagged deferred mode that prevents the application of the iptables rules until all instances on the host had been initialised then the rules for all instances are applied all at once preventing a 'blackout' period. Change-Id: I0da90d07e54225fb63f3884897fb00a6027cd537
Diffstat (limited to 'nova/openstack')
0 files changed, 0 insertions, 0 deletions