Re: [Netstack] Port states

Sorry, false alarm.. my tree was out of date :) Thanks Arvind On 08/09/2011 04:03 PM, Dan Wendlandt wrote: Is this code the latest from trunk? I believe that is one of the lines that was changed in the recently merged patch-set. Dan On Tue, Aug 9, 2011 at 1:03 PM, Arvind Somya

Re: [Netstack] Port states

Is this code the latest from trunk? I believe that is one of the lines that was changed in the recently merged patch-set. Dan On Tue, Aug 9, 2011 at 1:03 PM, Arvind Somya wrote: > ** > Thanks Dan, > > Also noticed something weird in the ovs plugin, might be already fixed: > > def get_port_det

Re: [Netstack] Port states

Hi Arvind, These are good questions. This is all part of what we've been trying to sort out in another thread on the email list. I believe we're approaching consensus on these issues, but we may end up deciding to bump all notions of 'state' (both administrative and operational) out of the v1.0

Re: [Netstack] Port states

Thanks Dan, Also noticed something weird in the ovs plugin, might be already fixed: def get_port_details(self, tenant_id, net_id, port_id): port = db.port_get(port_id) rv = {"port-id": port.uuid, "attachment": port.interface_id, "net-id": port.network_id, "port-state":

Re: [Netstack] Port states

On Tue, Aug 9, 2011 at 10:20 AM, Arvind Somya wrote: > ** > Somik, > Thanks for the info.. i'll file a bug. > I actually fixed that a while back, but the fix had been stuck waiting reviews. It just merged in the past day or so (though grep reveals a python comment that is still wrong) Dan >

Re: [Netstack] Port states

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 certa

Re: [Netstack] Port states

Somik, Thanks for the info.. i'll file a bug. -Arvind On 08/09/2011 01:16 PM, Somik Behera wrote: The active states from API definition perspective should be "ACTIVE" and "DOWN" If the OVS plugin has 'UP' thats a bug, please file one and we will bring it inline to API spec. Quantum currently j

Re: [Netstack] Port states

The active states from API definition perspective should be "ACTIVE" and "DOWN" If the OVS plugin has 'UP' thats a bug, please file one and we will bring it inline to API spec. Quantum currently just has 2 supported port-state "ACTIVE" and "DOWN" which map to admin up/down on a port. Thanks, Somik

Re: [Netstack] Port states

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-bounc