On Thu, Oct 20, 2011 at 2:48 AM, Salvatore Orlando < salvatore.orla...@eu.citrix.com> wrote: > > ** ** > > - The question of what enums to expose is interesting. At the most simple > level, all the user cares about is "UP" or "DOWN". I can think of two > reasons we may want to do more: **** > > 1) The system believes the current state to be transient, and thus wants to > let the user know that a change without user action is expect. This seems > to be the goal with something like "PROVISIONING". **** > > 2) The system believes the user may be able to do something to fix the > problem. For example, the attachment-id is not found, so perhaps the user > needs to correct the attachment-id, or make sure the VM with that > attachment-id is actually running. **** > > I'm not sure I understand difference between "DOWN" and "FAILED". Thinking > through various plugin scenarios, I think in practice it could be hard to > know when to use one versus the other as a developer. Similarly, I'm not > sure how the user interprets either field differently. One might try to > have both a general "error" state and more specific error states like > "attachment-id" not found, but even that can get tricky as it may be that an > attachment-id is not found because the plugin's connection to the switch is > down, not because the attachment-id actually doesn't exist. **** > > ** ** > > In my opinion a case for “DOWN” would be a port without an attachment (or > with a wrong attachment); on the other hand, a case for FAILED would be the > failure of a physical switch in the network or an hypervisor. **** > > I don’t have very strong opinion on the set of possible operational states. > IMHO, having just UP and DOWN is fine for a start. We can probably start > with them and then see in course of action if we might want something more. >
Awesome, sounds like we're very much on the same page. And just to be clear, I'm fine with there being more states than UP and DOWN if people want. My goal is just to make sure that they have very clear meanings for both the user. The example of distinguishing between a port that has no attachment and one that has an attachment that was unable to be wired is one such example. Dan **** > > Regards,**** > > Salvatore**** > > > -- > Mailing list: https://launchpad.net/~netstack > Post to : netstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~netstack > More help : https://help.launchpad.net/ListHelp**** > > > > **** > > ** ** > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dan Wendlandt > Nicira Networks, Inc. > www.nicira.com | www.openvswitch.org > Sr. Product Manager > cell: 650-906-2650 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~**** > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks, Inc. www.nicira.com | www.openvswitch.org Sr. Product Manager cell: 650-906-2650 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
