So you reckon that using Shared disk for AlwaysOn availability groups would be a challenge?
No, just not worth doing in my opinion. If the storage is shared why double your storage requirement so that you can use Always On. Also if you're looking to have a readable secondary to offload reporting from the primary database surely you'd want that on seperate storage? Otherwise you'll more than likely have the same bottlenecks as before.
The design here is to have an active secondaries that will accept only read only queries.
Great!, exactly what always on can be used for.
In the case of shared storage can a specific disk be presented to only a node only and the other in WSFC won't have access to it?
Yes that is possible. What do you mean by shared storage? Are we talking about a SAN here? or a shared disk array?
MCSE: Data Platform
MCSE: Business Intelligence
Follow me on Twitter: @WazzTheBadger
LinkedIn Profile: Simon Osborne