All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alphe Salas Michels <asalas@kepler.cl>
To: ceph-devel@vger.kernel.org
Subject: writing a ceph cliente for MS windows
Date: Mon, 04 Nov 2013 17:19:12 -0300	[thread overview]
Message-ID: <52780140.6090409@kepler.cl> (raw)

Good day developers!

I would like to propose to the one interested  work with me to develop a 
ceph cliente for MS windows world, Basing us on dokanFS.

My company is a ceph enthousiast that use on a dayly basis ceph and that 
need both transfer speed and big expendable and cheap storage.
My company is specialised in data recovery and we want to participate to 
ceph effort by bringing a ceph cliente for windows.
Our experience shows us that the best gateway is each clientes being its 
own gateway, instead of having a bottle neck server or a cluster of 
bottle neck servers as gateway (FTP, samba, SFTP,webdav, s3, etc..).

We already did some research in that domain.

Dokan FS is an intent  to write an opensource fuse like cliente for MS 
windows.

More information on DOKANFS can be triggered here
http://dokan-dev.net/en/download/

Positive points of using DOKANFS.

- its opensourced and well licenced mit licence, gpl licence and lgpl 
licence.

Negative point of using DOKAN FS.
- unreachable author
- Poor documentation . Dev comments in japanese.
- Work in progress so it is unstable and needs to be updated, debugged 
and maintained by a MS Windows file system expert developper.

I try past year to do a merge from ceph-fuse to dokanfs
here are what I learnt.
- Ceph-fuse and related source code is around 60 000 lines of code.
- Ceph protocol isn t documented so it is like trying to draw a map of 
america using only a sextan and a compass.

Those led me to those conclusions:
- I can t do it alone.
- It is easier to draw down the ceph protocol way to work from 
kernel/fs/ceph sources and mount.ceph
- Ceph depending libraries may be unexistant or not up to date in their 
port on MS Windows (cygwin)
- MS file system specialist are hard do find in the "open source libre 
world" so I will try in the commercial world.

The commercial world has some problems too. They need ceph protocol 
draft to implemente it to their own product They will have licencing 
/commercial politics that infringe lgpl, and hide that most of the work 
is done by people other than them. They will not participate in a 
financial way to ceph enhancement and growth.

As for the modalities of the work if we come to work togather on that 
topic, it up to you. We can / should use the most possible libre tools 
for that work (eclipse, mingwin/cygwin etc...) Sharpening the dev tools 
in libre can already be a big problem. But my way to see this is the 
more libre are our tools on MS Windows the most people can easyly join us.


Best Regards,


Alphe Salas

asalas@kepler.cl
I.T ingeneer.
*<http://www.kepler.cl>*


             reply	other threads:[~2013-11-04 20:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 20:19 Alphe Salas Michels [this message]
2013-11-05 14:23 ` writing a ceph cliente for MS windows Sage Weil
2013-11-05 17:40   ` Alphe Salas Michels
2013-11-05 21:49     ` Alphe Salas Michels
2013-11-05 21:59       ` Yehuda Sadeh
2013-11-05 22:31         ` Alphe Salas Michels
2013-11-06  0:00     ` Sage Weil
2013-11-06 14:37       ` Alphe Salas Michels
2013-11-06 21:47       ` Alphe Salas Michels
2013-11-05 23:33 ` James Harper
     [not found] <CAME-gASugOE=-ZoY3-sAa4vCzOd+TXBiEavjoUH3gDLG+1K38w@mail.gmail.com>
2013-11-07 12:13 ` Alphe Salas Michels
2013-11-07 14:29   ` Ketor D
2013-11-07 14:50     ` Matt W. Benjamin
2013-11-07 18:02       ` Alphe Salas Michels
2013-11-07 20:47         ` Alphe Salas Michels
2013-11-08  0:11           ` Malcolm Haak
2013-11-08  0:31             ` Matt W. Benjamin
     [not found]             ` <CAME-gARbjR++qXsx9Sx4KbuggthONrscHToxCTUKrci_MLMDzw@mail.gmail.com>
2013-11-08 14:15               ` Alphe Salas Michels
2014-12-26 17:10                 ` Ketor D
2014-12-27  5:14                   ` Dong Yuan
2014-12-27  5:14                     ` Dong Yuan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52780140.6090409@kepler.cl \
    --to=asalas@kepler.cl \
    --cc=ceph-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.