“…if an application moves from an environment where disks/volumes are mounted using WWNNs/WWPNs as end-point IDs (fibre channel) to an environment with IQNs as end-point IDs (iSCSI) we often have to re-validate and re-engineer. If the application were to list its own requirements it would actually just be something like ‘xGB block storage, isolated, with <performance guarantee 1> and <performance guarantee 2>’. There would be no mention of WWPNs or IQNs, fibre channel or iSCSI. The list above is the type of [automated/attached] description needed that would help make the application portable. It fits into a trust-based model (aka Promise Theory)…”
The above is an excerpt from my recent post on our Cisco UK & Ireland blog. You can read the full post here: http://gblogs.cisco.com/uki/it-service-brokerage-technical-mindset-infrastructure/