> 3.1.4 move-vnic: Will the command fail if the vnic is busy ? That could > be the easy route. Trying to move it while it is busy i.e. with clients > having it open may be more difficult from an implementation perspective. > > 3.1.6, 3.1.7 - up-vnic and down-vnic is the same as creation and > deletion of vnics except that it is done based on information from the > repository instead of from the command line ? Somehow up and down > conjure up vision of just a flag change (similar to ifconfig up/down) > instead of creation / deletion, may be just the nomenclature ?
Maybe init-vnic would be more clear? It has precedent (e.g., init-linkprop; init-secobj). -- meem
