Hi, > How did you do this? Did you map all Walrus objects 1:1 to RADOS? If so, > that should give you pretty large RADOS objects. That is not a problem, > RADOS can handle that, but performance-wise it isn't the best way to go. > > Or does Walrus split it's internal objects into smaller ones? I didn't know there's performance penalty, so currently it's just 1:1. I think eucalyptus administration tool split up a VM image to multiple objects when store it into Walrus, but that's only for VM image. Normal S3 put go directly 1:1. What is the best size when split it up anyway? Maybe I should refer rbd code? >> So these are different services, which can work together. >> I think if both services could integrated into Eucalyptus(or the >> another IaaS platform such as OpenStack) that will be exciting. >> >> Ceph already has radosgw for S3 compatible service anyway, but it >> looks much easier to use RADOS API from Walrus, so I implemented that >> way. > > Yes, the radosgw from Ceph is proof-of-concept, what RADOS/Ceph is > capable of. Do you have your Walrus integration online somewhere? Well, currently my testing environment is on the internal network. If you want to test it I can setup. >> >> > But great work! I think a lot of people don't see the full potential of >> > RADOS, hope your bindings and phprados will make more people use RADOS. >> > >> > If you ask Sage, he might want to setup a new GIT repo for you and a >> > project in the tracker, so we can keep track of bugs and features. >> > >> > Thanks, >> > >> > Wido > > About the Wiki, you are free to create a page :-) Okay, thanks. syuu -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
