Re: Openstack-Swift

r you? > >-- >Andrew Gaul >http://gaul.org/ > On 4/14/17, 9:49 AM, "Paya, Ashkan" wrote: >Hi Andrew, > >Sure, please see the logs in this pastebin: https://pastebin.com/CPQtgVLW > >Ashkan > > > > >On 4/13/17, 7:3

Re: Openstack-Swift

Hi Andrew, Sure, please see the logs in this pastebin: https://pastebin.com/CPQtgVLW Ashkan On 4/13/17, 7:30 PM, "Andrew Phillips" wrote: >Hi Ashkan > >> * Failed in command: …., org.jclouds.http.HttpResponseException: >> command: POST https://identity.api.rackspacecloud.com/v2.0/token

Openstack-Swift

Hello, We want to verify access to our openstack-swift account under Rackspace via “apiAccessKeyCredential” keystone authentication type. Our credentials are valid and we can issue the following curl command successfully and receive tokenId, tenant name and Id and etc. * curl https://ident

Re: AWS us-standard region

ward to fix, do you want to try submitting a pull request with the patch? I'll be happy to help! I. On Apr 4, 2017 2:00 AM, "Paya, Ashkan" mailto:ashkan.p...@dell.com>> wrote: Hello, According to (http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region) “us-standar

AWS us-standard region

Hello, According to (http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region) “us-standard” got renamed to “us-east-1” some time back but in jclouds codebase[1] we still use the former name. This causes BlobStore.listAssignableLocations to return an invalid region when the user want

Swift in jclouds 2.0.0

Hi, According to JCLOUDS-786, the old swift api is no longer supported in jclouds 2.0.0. Does this mean that we should just change the provider’s name from swift to openstack-swift? In my case, solely changing the name does not seem to resolve

Re: HTTP Headers

in the provider >implementation. Specifically for User-Agent, we have an open feature >request: > >https://issues.apache.org/jira/browse/JCLOUDS-819 > >This is a well-scoped task and we would appreciate a pull request to >include it. Would you be willing to address this? > >On

Re: HTTP Headers

Hi Andrew, No there is no error or problem with the headers that jclouds sets. I just want to add a custom user-agent string to all put/get requests for some analysis/tracking purposes. Sincerely, Ashkan On 11/10/16, 1:30 PM, "Andrew Phillips" wrote: >Hi Ashkan > >> Can we use/overwrite HT

HTTP Headers

Hello, Can we use/overwrite HTTP headers such as USER_AGENT when invoking methods like BlobStore.putBlob() or we need to specify the BlobRequestSigner and use HttpClient instead? For example, if I want to include the HTTP headers in the following operation: ByteSource input = ByteSource.wrap(“

Re: Directory Name - 2.0.0-SNAPSHOT

ludes many >changes to align the former with the latter. > >For what it is worth, directories are a jclouds fiction and something we >deprecated in 2.0 and will remove in 2.1. The new prefix and delimiter >support in 2.0 matches how real providers work. > >On Wed, Oct 26, 2