Re: [Dev] Add Content-Encoding to Google Cloud Storage

You can reproduce the symptoms in JCLOUDS-885 by modifying addContentMetadata and checkContentMetadata in GoogleCloudStorageBlobIntegrationLiveTest.java. Note that jclouds has abstracted both its implementation and tests so crawling through this code might confuse you at first. You can run a curr

Re: [1.9.1] - CloudStack - userMetaData vs userData

I assume you refer to this userData [1]. I'm not a CloudStack user, so I don't know how that user data is expected to be used, but what you propose makes sense to me (taking into account the size limitation of that property). Adding this feature should be pretty straightforward. You just have to c

Re: Semantics of TemplateOptions.authorizePublicKey(...) -- esp wrt Google Compute

There are a couple things to consider here: how the "authorizePublicKey" behaves has never been formalised, and I agree we should do that. Let's use this thread to come to a consensus we are all happy with. I think the main point to discuss is whether jclouds should *always* create a (hidden) key

[Dev] Add Content-Encoding to Google Cloud Storage

Hi All, I'm contributing to the issue jclouds 885 [1].I am new to jclouds contribution and i am reading documentations and do all the things.Up to now I clone and setup jclouds labs google [2] project in IDEA developer environment.I am activated google cloud storage and going through their steps.