11-01-2013, 04:56 PM
the two major issues with 1.22 are the devices randomly changing properties at runtime, and vcl thinking that devices are no longer available or are otherwise already busy.
there definitely is a point to acquiring hardware for a VirtuaCL cluster. just because this version is broken, as is the last version, doesn't mean the next version won't be broken
the point being, eventually a good solution will emerge. be it VirtualCL or something else. the other solution we are investigating will also require infiniband hardware. pretty much any cluster middleware will. so it's definitely worth the investment, even if it means having to hold off for a bit on a middleware solution. in the meantime you can manually distribute the load, and enjoy having a super fast interconnect for scp'ing wordlists back and forth
there definitely is a point to acquiring hardware for a VirtuaCL cluster. just because this version is broken, as is the last version, doesn't mean the next version won't be broken
the point being, eventually a good solution will emerge. be it VirtualCL or something else. the other solution we are investigating will also require infiniband hardware. pretty much any cluster middleware will. so it's definitely worth the investment, even if it means having to hold off for a bit on a middleware solution. in the meantime you can manually distribute the load, and enjoy having a super fast interconnect for scp'ing wordlists back and forth