Hi, I updated my pull request and looking forward #5416, and asked for more information on the tracker. Nowadays, i'm iterating on the tracker to find issues i can fix. I currently proposed fixes for #1779, #5228 and #5324. I'm not very familiar with tests, and it might be a little too big for me to start with. Btw, I was also in contact with Joe Buck to properly setup a fake cluster suitable to make tests, as i was having trouble in doing that. To get started, i'm looking for things a bit smaller, that could fit in a day. I would be glad if you could point me to some specific tasks, even if they are not specially related to the geo-replication blueprint, the best for me remaining rgw related tasks as it's what i am trying to learn. Best regards. On Thu, Jun 27, 2013 at 5:25 PM, christophe courtaut <christophe.courtaut@xxxxxxxxx> wrote: > ---------- Forwarded message ---------- > From: Yehuda Sadeh <yehuda@xxxxxxxxxxx> > Date: Thu, Jun 27, 2013 at 5:21 PM > Subject: Re: Contribution > To: christophe courtaut <christophe.courtaut@xxxxxxxxx> > > > On Thu, Jun 27, 2013 at 7:30 AM, christophe courtaut > <christophe.courtaut@xxxxxxxxx> wrote: >> Hi Yehuda, >> >> I went thru http://tracker.ceph.com/projects/rgw/issues today ( all 22 >> of them ;-) and contributed a patch to >> http://tracker.ceph.com/issues/5324 ( that was an easy one ). I'd be >> happy to either fix more bugs on the current development branch or >> contribute to the geo-replication >> https://github.com/ceph/ceph/commits/wip-rgw-geo-2 >> >> The amount of work going on with wip-rgw-geo is impressive and I'm not >> sure what I could do to help. It would be most convenient for me to >> pick from a list of self contained tasks in the tracker. I would be >> happy to spend a few days on each of them, one at a time. Since I'm >> still new to the code base, working on a tasks that would require >> weeks of work is probably too ambitious at this point. However, I very >> much understand that the definition of such tasks requires a fair >> amount of work on your part. And if noone works on these tasks, this >> would be a waste of your time. If that helps, I promise to diligently >> work on them, full time :-) >> > > Hi, > > I saw your pull request, and also commented on the commit. There's > a similar easy issue (#5416) that you can take a look at now if you'd > like. > I think that at the moment with regard to the geo-replication, the > most helpful thing would be to test the different APIs, make sure they > work as expected as we're on a tight schedule, and planning a feature > freeze by the end of next week. > The API specifications are in the wiki > (http://wiki.ceph.com/RESTful_API_for_DR_%2F%2F_Geo-Replication). > Specifically I'm interested in data sync, as it's the path less > tested. If you could simulate (even manually) a scenario, where you > put an object in a bucket, check to see whether bucket is listed in > the data log, then go to the bucket index log, see the change entry in > the bucket index log, then generate a copy of that object from the > master zone to the secondary zone. Look at the operation state log to > see whether this operation is marked as completed. > Check to see whether the object appears in the secondary zone, check > its attributes. > That tests a wide range of the new APIs, and it'll be really helpful. > If you could somewhat automate it and create a script that does it, > it'll be extra helpful. > > Most of the other DR/geo-replication tasks are either done (waiting > for review and merge) or being implemented now. There are other > non-geo-replication issues that I can assign to you if you want to get > your feet dipped in the rgw code. Even if these are not a direct > geo-replication issues it may help us getting geo-replication out the > door faster as it'll free me to work on geo-replication. Let me know > if you're interested. > > Thanks! > Yehuda > > > -- > Christophe Courtaut -- Christophe Courtaut -- 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
