rg, "Ryan Wilson 76511"
> *Sent: *Tuesday, April 22, 2014 6:52:27 PM
> *Subject: *Re: [ovs-dev] [PATCH] netdev: Add random tag to struct netdev.
>
> It would make a lot more sense to have a global indication whether OVS was
> restarted. This is a property of OVS, not of
ev@openvswitch.org, "Ryan Wilson 76511"
Sent: Tuesday, April 22, 2014 6:52:27 PM
Subject: Re: [ovs-dev] [PATCH] netdev: Add random tag to struct netdev.
It would make a lot more sense to have a global indication whether OVS was
restarted. This is a property of OVS, not of a netd
It would make a lot more sense to have a global indication whether OVS was
restarted. This is a property of OVS, not of a netdev. Otherwise we'll get
subsequent requests to add such a random tag to every single table in the
database.
You can already tell if a port is deleted and readded by noticin
> I don't understand why, if you need to know when vswitchd restarts (why do
> you?), it should be tied to netdevs.
So if you're monitoring a netdev for packet stats, you need to know if
vswitchd restarted so that you can take account of the fact the stats
were reset. I suppose it needs to be tie
I don't understand why, if you need to know when vswitchd restarts (why do
you?), it should be tied to netdevs.
On Apr 22, 2014 4:09 PM, "Ryan Wilson 76511" wrote:
> netdev: Add random tag to struct netdev.
>
>
> Before, there would be no way to tell if ovs-vswitchd had
> been restarted or killed
netdev: Add random tag to struct netdev.
Before, there would be no way to tell if ovs-vswitchd had
been restarted or killed via ovsdb logging. Now, a random
tag will be generated upon initialization of the netdev
struct which happens when ovs-vswitchd is restarted. A
change in tag value in
