NX users may confuse between connected to vm or connected to the switch (despite of <plugged>), as they used to <link>=up|down<link/>
Yap, no convergence on terminology yet, right?
I think we need to keep the plugged/unplugged not to confuse libvirt users
Yes, with real iron nics (and hard drives), the term "hotplug" is widely understood as "shove a new device into a running machine". So I see no reason to change anything. But I do not see how this is related to libvirt (which does not have an API call named *plug*).
however let's do wired/un-wired = link-up / link-down it's understood by everyone and Michael pointed out
I'm fine with that. I"ve updated the wiki with the term "link state" instead of "wired/unwired".
What about allowing a nic with the no-network? Did not see discussion on this.
It is useful as an interim state when changing networks or if the nic is there to be use by a hook. This may also be useful when allowing to purge a network while it is connected to VMs: Link-Down on all nics and connect to the empty/no network. (Yes I know, it's not par of the feature, but you know someone will ask for it soon :))
It should not be hard to implement; In http://wiki.ovirt.org/wiki/Feature/DetailedNetworkWiring#New_API I suggest passing no 'network' element to mean "connected to nothing".
I don't really understand why changing the link state to down is not enough? What is the added value of connecting "unwired" nic to a none network?
The coupling between vNIC and LN should break - for this feature (that I hate to call it wired) and for future to come.
Simon.
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel