Hi Jason,
Thank you so much for all of the information. This really provides some
good insight on the integration of iSCSI with LIO. Lets hope that kernel
folks can work fast ahah
Sam
On Wed, Aug 9, 2017 at 12:48 PM, Jason Dillaman wrote:
> Yeah -- the issue is that if nodeA is the active pa
Hi Sam,
Pacemaker will take care of HA failover but you will need to progagate
the PR data yourself.
If you are interested in a solution that works out of the box with
Windows, have a look at PetaSAN
www.petasan.org
It works well with MS hyper-v/storage spaces/Scale Out File Server.
Cheers
/Ma
Yeah -- the issue is that if nodeA is the active path and Windows
issues some PRs, then if nodeA fails and nodeB is promoted to the
active path, those PRs won't exist and Windows will balk and fail the
device. I've seen some posts online w/ folks writing custom pacemaker
resource scripts to try to
Hmm :( Even for an Active/Passive configuration? I'm guessing we will
need to do something with Pacemaker in the meantime?
On Wed, Aug 9, 2017 at 12:37 PM, Jason Dillaman wrote:
> I can probably say that it won't work out-of-the-gate for Hyper-V
> since it most likely will require iSCSI persis
We are working hard to formalize active/passive iSCSI configuration
across Linux/Windows/ESX via LIO. We have integrated librbd into LIO's
tcmu-runner and have developed a set of support applications to
managing the clustered configuration of your iSCSI targets. There is
some preliminary documentat
Hi Sam,
We use SCST for iSCSI with Ceph, and a pacemaker cluster to orchestrate the
management of active/passive presentation using ALUA though SCST device groups.
In our case we ended up writing our own pacemaker resources to support our
particular model and preferences, but I believe there
