Yup, this is expected. It happens for both single-host and multi-host. With the former, we have an older environment where it takes around 10 minutes for all network access to resume. That's with a few hundred tenants, a few hundred vlans, and a few hundred floating IPs all on one host, though.
>From your list of reasons for restarting, we only need to restart nova-network for config changes. If you're running into odd issues that you think nova-network might be causing, definitely feel free to describe some symptoms :) Joe On Nov 26, 2015 8:49 AM, "Gustavo Randich" <[email protected]> wrote: > Hi everybody, (still using nova-network in production... :) > > Using nova-network (icehouse), multi-host, FlatDHCPManager > > Is it expectable to experience an interruption of various seconds in > instances' floating IP reachability when nova-network is restarted and > repopulates iptables' NAT output/prerouting/float-snat tables? (IP packets > are not delivered to VMs until iptables forwarding rules are setup) > > We don't restart nova-network often, but we have certain cases when we > need(ed) to: > > * nova-network not reconnecting to RabbitMQ (latest oslo messaging patch > mitigates this) > * configuration changes in nova.conf from time to time > * sanitary periodic (weekly or monthly) restarts to prevent poorly > understood problems of the past (resource leaks?); will stop doing this due > to NAT downtime > > Thanks! > > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > >
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
