I have just realised that this isn't even on the Release Team's radar for a FFE.
GlusterFS 2.0.x has some serious issues such as maxing out CPU in certain (random yet reproducible) circumstances. The upgrade path from 2.0.x to 3.0.0 was a bit rough but it seems that most of the 3.0 issues were resolved in 3.0.2.
Upstream has mostly dropped support 2.0.x and encourage all users with bugs/issues to try 3.0.x. The referenced upstream bug report is one example of this.
I think it would be a shame for Ubuntu to ship a broken version of glusterfs in lucid, especially as it will be around for a long time.
As I noted in comment #11 the debs in Andres ppa worked ok when I tested them.
I have just realised that this isn't even on the Release Team's radar for a FFE.
GlusterFS 2.0.x has some serious issues such as maxing out CPU in certain (random yet reproducible) circumstances. The upgrade path from 2.0.x to 3.0.0 was a bit rough but it seems that most of the 3.0 issues were resolved in 3.0.2.
Upstream has mostly dropped support 2.0.x and encourage all users with bugs/issues to try 3.0.x. The referenced upstream bug report is one example of this.
I think it would be a shame for Ubuntu to ship a broken version of glusterfs in lucid, especially as it will be around for a long time.
As I noted in comment #11 the debs in Andres ppa worked ok when I tested them.