Seeking Feedback on Gluster Development Priorities/Roadmap

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Ben,

Thanks for asking!

Documentation for sure lacks some important details. I have serveral
questions like:

1) How to effectively replicate on the other data center asynchronuously.
2) Support for async replication in addition to sync replication. This
might be helpful and self heal may not be required in that case.
2) More info on Data center replication setup
3) It will be good to get some performance information /experience
from those people who are already using it and post it on the gluster
site.
4) Some info on how to make gluster run as a web service. For eg: I
currently don't know how to effectively create a web service to serve
browser clients.
5) Best practices info

Mostly it's around getting more information out that we can read and understand!

Thanks!

> Following that, our internal priorities are:
>>
>> -Continuous Data Replication (over WAN)
>> -Improved User Interface
>> -CIFS/Active Directory Support
>> -Object storage ?(unified file and object)
>> -Geo-replication to Amazon S3 (unify public and private cloud)
>> -Continuous Data Protection
>> -REST management API's
>> -Enhanced support for ISCSi SANs
>>
>> Are these the right priorities? How would you prioritize?
>>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>
>


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux