Re: [jclouds/jclouds-labs] Pb compute api (#292)
@devcsrj I removed all the formatting changes, i agree lets focus on the compute changes, all the changes in the commit are related to the Compute API . -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/292#issuecomment-247569116
Re: [jclouds/jclouds-labs] Pb compute api (#292)
@alibazlamit pushed 1 commit. 25ab6d0 minor fix -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/jclouds/jclouds-labs/pull/292/files/23c285072ed22918cbdc374429e49ed60cfb5e91..25ab6d02d2f493b2488a32c21625f9f82586f6e9
Re: [jclouds/jclouds-labs] Pb compute api (#292)
@alibazlamit pushed 1 commit. 2707084 commit -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/jclouds/jclouds-labs/pull/292/files/aaeb697c0e5d81667841e3f626a5ae15bb56dda9..27070843b4bd7b1932a423d6a692d0edf4064717
[jclouds/jclouds-labs] Fix package export for OSGi (#318)
You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-labs/pull/318 -- Commit Summary -- * Fix package export -- File Changes -- M azurecompute-arm/pom.xml (2) -- Patch Links -- https://github.com/jclouds/jclouds-labs/pull/318.patch https://github.com/jclouds/jclouds-labs/pull/318.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/318
Re: [jclouds/jclouds-karaf] Fix OSGiScriptEngineManager package (#83)
@nacx pushed 1 commit. a36ede1 Fix log message -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/83/files/5eeb5cfbfacaf8c05e7057727638f3bf2297717b..a36ede13de7f7ea873827b985607ffb61425354d
[jclouds/jclouds-karaf] Fix OSGiScriptEngineManager package (#83)
Minor issue after moving the classes that caused the jclouds commands not to be installed. /cc @demobox You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-karaf/pull/83 -- Commit Summary -- * Fix OSGiScriptEngineManager package -- File Changes -- M commands/src/main/resources/OSGI-INF/blueprint/jclouds-commands.xml (2) -- Patch Links -- https://github.com/jclouds/jclouds-karaf/pull/83.patch https://github.com/jclouds/jclouds-karaf/pull/83.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/83
[jira] [Commented] (JCLOUDS-1179) putBlob doesn't handle 401s
[ https://issues.apache.org/jira/browse/JCLOUDS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15497270#comment-15497270 ] Zack Shoylev commented on JCLOUDS-1179: --- I won't get to this until after Wednesday next week. > putBlob doesn't handle 401s > > > Key: JCLOUDS-1179 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1179 > Project: jclouds > Issue Type: Bug > Components: jclouds-blobstore >Affects Versions: 1.9.2, 2.0.0 > Environment: Devstack on Ubuntu 14.04 >Reporter: Nick Howes >Assignee: Zack Shoylev > Labels: openstack-swift > > After the token used by jclouds expires, subsequent `putBlob` requests to > swift fail with 401. > Unlike other operations, the `putBlob` command does not resolve this by > `POST`ing to keystone, but instead tries a few times to `PUT` the blob to > swift. Each request fails with a 401 and then it gives up. > Other operations such as a get _will_ handle a retry by refreshing the auth > token, after which subsequent puts work (until the next expiry) > Project to reproduce can be found here > https://github.com/UniversityofWarwick/jclouds-bug > It should be noted that when running this script I have altered [token] > expiration in /etc/keystone/keystone.conf to be 2 seconds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
