@tntteam Thanks for the encouragement, much appreciated.
As per the more exciting features such as you mention I’m personally quite looking forward to getting around to the more ‘exotic’ stuff and have in mind implementing a nice friendly and simple integration for CTDB so we can gain pCIFS and some HA stuff such as IP takeover. We already have the basics of the inter-Rockstor appliance communication in place that the replication feature uses, which is based on zeromq, and I’m imagining leveraging that to allow non technical users to be able to bootstrap their way up into hosting a simple GlusterFS arrangement, potentially even within a single node but across multiple pools via brick/pool say (obviously lacking some redundancy elements here of course). The Glusterfs + CTDB combo looks to be a well tested and very importantly well documented option. However as previously mentioned:
My personal preference for HA is more in the direction of a clustered fs than a master slave type arrangement as it’s more expandable and seems like it addresses the issue at a lower level rather than trying to bend older technologies to fit newer paradigms. I.e I want to get to the stage where one could deploy / destroy Rockstor instances in a Cluster trivially.
Looks like we have a message cross-over here so I’ll address your more recent post here:
Agreed, hence the need for our documentation improvements referenced earlier. If you fancy you could take a look at our Community Contributions and more specifically the Contributing to Rockstor documentation doc sections.
Make sure you are running the latest stable release as per:
Prior to that for a while all releases showed the failure you seem to be having which was down to some major API refactoring for shares and pools that we unfortunately had to do but will in the end benefit the project going forward.
Also note that there are still some fragile elements to the replication code as it stands, and looking at the first reported failure in the replication history should help, and make sure to look at both the sender and the receiver’s reports as sometimes one is more informative than the other. I’ll get around to some more maintenance/improvements soon in that area but I’m currently occupied elsewhere in the project, for better or worse 
Do feel free to open a dedicated thread to track down / help debug any issues you find as Rockstor is fully open source and so greatly benefits from contributions of all sorts. Most notably in constructive forum participation, plus we seem to have quite a knowledge among our members.
Hope that helps.