Hi, Doron, Cross-posting and inline.
On Mar 25, 2012 7:22 AM, "Doron Tsur" <[email protected]> wrote: > > Hi, > > I've researching BlobStore API, went over the guide and some examples. I > would send send some of this to jcloud user-list but there is a membership > pending issue. I approved your membership, noting from sound of your note, you likely want jclouds-dev > > Questions. > > Limitation - I wonder if there is a way to probe the limitation. Sometimes > users might want to perform operation which are restricted like upload to > Azure a file which is more than 64MB. Is there away to prob the limitation There's currently a partially implemented Capabilities system on BlobStore. This was done years ago, and we can discuss why it didn't work. Current approach is to expose anything not LCD using Optional<X> interface, which can be derived at runtime or from static metadata about a service. This is first implemented in our hpcloud-objectstore where a non OpenStack Swift entension is present. There's more work to be done on this including discovery of non-standard features. > in the BlobStore and make sure that an operation is possible. Other example > is trying to redirect a blob from one blobstore to another. Objects should or do have reference to their geographic location (ex. Iso3166) and also the provider they are in. There is currently no copyBlob op, but you could imagine copying using server apis on those who support it, or employing a strategy for intercloud copies. > > Development - How do you guys develop and test your code when you need a > cloud? I will probably revamp my old laptop to run the necessary platform, > it would be a pain if at all possible (machine issues). Best practice here? Transient and filesystem providers. You can also use devstack.org to install openstack swift on your laptop in a vm, or even implement a blobstore binding for something more lightweight and already in whirr. > > IRC: When is jclouds, Whirr most active in the IRC?. I'm from GMT+2. > Irc and jclouds-dev google groups are pretty active in your timezone towards the end of the day. We have equal activity in europe and PST > Proposal- Would you like me to share my proposal with you guys before > submitting? What kind of inrormation you expect besides of: deliverable, > Timeline other commitments. What is the level of details the design should > have? I'll have to punt this Q to someone more familiar with the process. > > Sorry for bombarding with questions but Whirr just became my top choice for > GSoC project and I want to get things rolling. Rock on > > Good Day, > qballer > > > > On Thu, Mar 22, 2012 at 6:35 AM, Adrian Cole <[email protected]> wrote: > > > Hi, Doran > > > > A blob is indeed a blob :) > > > > I would start by going to github jclouds-examples and making a few blobs of > > your own. > > > > You can play with these and also look at jclouds.org/documentation where > > there's a BlobStore guide, to help you understand what it is like, being a > > blob. > > > > Finally, you can hop on irc freenode #jclouds to meet others coping with > > life in a blobby world. > > > > -A > > On Mar 21, 2012 5:30 PM, "Doron Tsur" <[email protected]> wrote: > > > > > Setting up a simple Whirr cluster would be my next step. I'm trying to > > get > > > a good feel of the project so I've been going over some documentation. I > > > don't come with a lot of background in cloud computing so I'm figuring it > > > out as I go. This step also requires me to setup an Ubuntu Server 10.04, > > I > > > will do that and run Whirr on it. > > > > > > It took me a while to understand that a blob is just that, a blob. I'm > > > assuming that the entire Blob Store concept was created in order to > > > transfer and store big binary files efficiently. I'm not sure how this is > > > achieved yet but a client doesn't need to understand the server just how > > to > > > interface with it. > > > > > > Things I want to do: > > > > > > 1. Support create, delete and setMetaData (I understand Blobs have that, > > > right?) in the basics. > > > > > > 2. Support functions with out occupying the Whirr terminal. meaning that > > as > > > soon as a request is made, the CLI can be free to do other things while > > the > > > job is done in the background. I'm guessing that create can be time > > > consuming. As soon as the function is done it should print the > > result/stats > > > to the screen. blocking the CLI if required should be easy if needed. > > > > > > 3. It came to mind that on a cloud you can have several Blob Stores and > > if > > > Blobs could bounce from one to another it could be useful. If this is > > > possible, Blob Store wise, I would like to support move and copy between > > > blobs. This will less constrain the users bandwidth and could be useful > > for > > > scripting on top of this client . > > > > > > It would be great if you could share any quality links regarding Whirr, > > > Jclouds, cloud computing and interfacing with a BlobStores. Google is my > > > friend but all of you have been researching the topic for some time now. > > > > > > > > > > > > > > > > > > On Wed, Mar 21, 2012 at 12:50 AM, Andrei Savu <[email protected]> > > > wrote: > > > > > > > Good to hear that you find the project interesting. > > > > > > > > #286 sounds like a great fit for you. Have you tried to setup a simple > > > > cluster with Whirr? How do you think the blob store client should look > > > > like? > > > > > > > > Cheers, > > > > > > > > -- Andrei Savu / andreisavu.ro > > > > > > > > On Wed, Mar 21, 2012 at 12:21 AM, Doron Tsur <[email protected]> > > wrote: > > > > > > > > > HI all, > > > > > > > > > > This is the second ASF project that caught my eye. I guess Apache > > must > > > be > > > > > doing something right. I looked in to some JIRA issues which are > > > mentored > > > > > candidate and this interested me > > > > > > > > > > https://issues.apache.org/jira/browse/WHIRR-286 > > > > > > > > > > I've been taking interest in several open source project, after > > > speaking > > > > > with several committers on a bunch of projects I figured out the > > style > > > of > > > > > project I would like to do. I would like to own one feature, it > > doesn't > > > > > really matter which, though there some which are more appealing than > > > > > others. This would be my main project, during that time I would also > > > like > > > > > to perform general purpose bug fixing. This will allow me to produce > > > two > > > > > forms of deliverable code. The bug fixes should be on a weekly or > > > > bi-weekly > > > > > basis depending on main projects constrains and other factors. I will > > > > work > > > > > out the details with the mentor. I wonder if this approach sounds > > > > > reasonable for you? > > > > > > > > > > I'm guessing some of you or going to be mentors in the upcoming GSoC, > > > do > > > > > you have a specific notion in mind? > > > > > What kind of details would you like to see in the application? > > > > > Any Whirr specific documents you would like me to go in to while > > > writing > > > > up > > > > > a proposal? > > > > > > > > > > Please, feel free to share your thoughts! > > > > > > > > > > Good Day, > > > > > qballer > > > > > > > > > > > > > >
