Ram,
Using the quantum APIs all the dashboard sees from the client is
'ACTIVE' and 'DOWN' in the port details.
I can show Administratively Down etc. if that info is provided to the
dashboard using the client or some other mechanism.
I can think of a couple of methods to deduce this to a certain extent by
the dashboard:
- Using a set of general rules like VIF connected but port down mean
operationally down, no vif plus down means administratively down etc..
- Store port history in the dashboard db, administratively down only
when the port has never been turned up since creation or the user
explicitly turns it down. This might lead to discrepancies when
switching between the dashboard, cli and other clients that won't have
this data available.
If the plugin can provide that info then it's just a matter of
displaying whatever the plugin/client returns. Thoughts on this?
Thanks
Arvind
On 08/09/2011 01:14 PM, Ram Durairaj (radurair) wrote:
Hi Arvind:
Are you also planning to show, in network speak, Administratively
UP/Down, Operationaly UP/Down.
We don't have to complicate this..but useful while debugging.
My $0.02
Ram
-----Original Message-----
From: netstack-bounces+radurair=cisco....@lists.launchpad.net
[mailto:netstack-bounces+radurair=cisco....@lists.launchpad.net] On
Behalf Of Arvind Somya (asomya)
Sent: Tuesday, August 09, 2011 10:09 AM
To: netstack@lists.launchpad.net
Subject: [Netstack] Port states
Hello Netstackers,
I'm trying to write this bit in the dashboard that allows users to
toggle port states, my problem is that while the FakePlugin defines two
states 'ACTIVE' and 'DOWN'.. the ovs plugin defines them as 'UP' and
'DOWN'.
Is there a way for the dashboard to find out what the supported states
are from the plugin? I couldn't find any methods in the client or the
plugin modules.
Thanks
Arvind
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
