jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Custine (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-645) Incorrect endpoint url chosen for default region of HPCloud Object Storage
Date Fri, 01 Aug 2014 01:50:39 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081805#comment-14081805
] 

Chris Custine commented on JCLOUDS-645:
---------------------------------------

Oh believe me, I am painfully aware of this version mismatch between the two endpoints as
is [~jdaggett]. That is why it is now passing null, because before you would only match on
region-a.geo-1, or none if you actually specified jclouds.region=region-b.geo-1 (the endpoint
matching defaults to serviceType + version).  However, this isn't really the cause of this
behavior where the last endpoint is selected.  The cause is that the fix I wrote for that
issue happens to specifically select the last match, based on the precedent in other areas
as you mentioned above.

So I understand why all of this is happening, and I can change it to select the first endpoint
instead.  My question is whether this is the right thing to do, since we are basically changing
behavior to match arbitrary expectations of downstream code.  I think it should be required
to specify region just like the new swift provider (which we will hopefully be migrating HP
Cloud to soon), but doing that would have been a much larger incompatibility issue with downstream
code written for the current swift impl.

> Incorrect endpoint url chosen for default region of HPCloud Object Storage
> --------------------------------------------------------------------------
>
>                 Key: JCLOUDS-645
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-645
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.8.0
>            Reporter: Shri Javadekar
>            Assignee: Chris Custine
>             Fix For: 1.8.0
>
>
> JClouds seems to be choosing the wrong endpoint from the service catalog returned by
HPCloud Object Storage.
> From what I see there are two endpoints returned in the Object Storage part of the service
catalog.
> D 07-31 13:21:22.122 pool-1-thread-1 jclouds.wire:59 |::] << "          "publicURL":
"https:\/\/region-a.geo-1.objects.hpcloudsvc.com\/v1\/53176293441764",[\n]"
> D 07-31 13:21:22.124 pool-1-thread-1 jclouds.wire:59 |::] << "          "publicURL":
"https:\/\/region-b.geo-1.objects.hpcloudsvc.com\/v1\/53176293441764",[\n]"
> I do not have any region configured.
> With 1.7.3, the first url was getting used and my tests were succeeding. However, with
1.8.0 the second url get's chosen and my tests failed with a "404 Not Found" error.
> See this for more details: http://pastie.org/private/yzxbnvxwidajalcucwflwa



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message