Hey KB,
It looks like Neil beat me to most of the meaty discussion, but I am happy to be the sacrificial lamb to hold the Storage SIG reins for now. Is there anything I could do in preparation for the proposal stuff that might make the road a bit smoother?
I see that most of the work is post devteam member involvement (new list, wiki section, etc) that I'm happy to start populating as soon as it makes sense. Just didn't know if there were specific proposal docs or other sundry that may help. Happy to run with whatever makes sense. Thanks.
Best Regards,
Patrick McGarry Director, Community || Inktank http://ceph.com || http://inktank.com @scuttlemonkey || @ceph || @inktank
On Tue, Feb 4, 2014 at 4:00 AM, Karanbir Singh mail-lists@karan.org wrote:
Hi Patrick,
On 02/03/2014 02:31 PM, Patrick McGarry wrote:
Just wanted to check on this and see if anyone had thoughts on the formation of a storage SIG? I'm also usually idling on freenode (and in #centos) as 'scuttlemonkey' if someone would like to discuss this further. Thanks.
What we need to do is get the proposal stuff done, in front of the board for the approval and then start working to import content.
I know that ceph easily seperates the cluster end from the client side, it might then be easier to consider one part of the equation before the other ?
At fosdem, I did manange to have a series of conversations with people around the idea of shared code across SIG's ( the sort of thing we might need to look into for the qemu config changes needed to make ceph work in the client side ), and its going to be a harder problem to solve.
How are you placed to consider the storage and client sides of ceph as independant components ?
Finally, I presume you are stepping up to the Storage SIG representative :)
- KB
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel