Re: [openstack-dev] [neutron] Backup port info to restore the flow rules

On Mon, Feb 22, 2016 at 7:03 PM, Ihar Hrachyshka wrote: > Agent could probably try to restore the state from its internal state. If > that’s the missing bit you want to have, I think that could stand for a > proper RFE. > Good point. Thanks. -- Best, Jian

Re: [openstack-dev] [neutron] Backup port info to restore the flow rules

Jian Wen wrote: I don't think it's enough for a large scale cloud. When the neutron server is not available and the flow rules are gone, we need the backup to restore the flow rules. Flows should not be reset when neutron-server is down. If that’s the case,

Re: [openstack-dev] [neutron] Backup port info to restore the flow rules

I don't think it's enough for a large scale cloud. When the neutron server is not available and the flow rules are gone, we need the backup to restore the flow rules. We have more than a thousand physical servers in our production environment. Rare events will occur where combined

Re: [openstack-dev] [neutron] Backup port info to restore the flow rules

Jian Wen wrote: Hello, If we restart OvS/ovs-agent when one or more of Neutron, MySQL and RabbitMQ is not available, the flow rules in OvS will be gone. If Neutron/MySQL/RabbitMQ doesn't become available in time, the VMs will lose their network connections. It's not easy

[openstack-dev] [neutron] Backup port info to restore the flow rules

Hello, If we restart OvS/ovs-agent when one or more of Neutron, MySQL and RabbitMQ is not available, the flow rules in OvS will be gone. If Neutron/MySQL/RabbitMQ doesn't become available in time, the VMs will lose their network connections. It's not easy for an operations engineer to manually