Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Date: Wed, 9 May 2012 13:03:50 +0000 (UTC)
From: "Michal Fojtik (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: 
 <919336325.44144.1336568630957.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1185943532.2403.1335387858147.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DTACLOUD-200) Deltacloud returns 'us-east-1a'
 as the realm for a load_balancer created in 'us-east-1b' availability zone
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DTACLOUD-200?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13=
271389#comment-13271389 ]=20

Michal Fojtik commented on DTACLOUD-200:
----------------------------------------

Seems like an upstream bug in the 'aws' gem. I'll investigate and drop a co=
mment here later.
               =20
> Deltacloud returns 'us-east-1a' as the realm for a load_balancer created =
in 'us-east-1b' availability zone
> -------------------------------------------------------------------------=
---------------------------------
>
>                 Key: DTACLOUD-200
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-200
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: Fedora 16
> Rhel 6.2
> deltacloud git commit version: c13da7b50bbbbdc529b42207f58dbe5099006ad1 c=
lone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
>            Reporter: Ronelle Landy
>            Assignee: David Lutterkort
>
> Copying test code to create load_balancer in 'us-east-1b' realm:
> HttpResponseDecorator respLB =3D restClient.post( path: '/api/load_balanc=
ers', contentType: ContentType.XML,
> =09=09=09=09headers: [Accept: 'application/xml'], requestContentType : Co=
ntentType.URLENC,
> =09=09=09=09body: ['name=3DwebTrafficBalancer' +=20
> =09=09=09=09=09'&realm_id=3Dus-east-1b' +
> =09=09=09=09=09'&listener_protocol=3DHTTP' +
> =09=09=09=09=09'&listener_balancer_port=3D80' +
> =09=09=09=09=09'&listener_instance_port=3D3001'])
> Delatcloud returns 'us-east-1a' as the realm:
> curl -X GET --user "username:password" "http://qe-blade-14.idm.lab.bos.re=
dhat.com:3005/api/load_balancers?format=3Djson"
> {"load_balancers":[{"realms":[{"limit":"unlimited","state":"available","n=
ame":"us-east-1a","id":"us-east-1a"}],"href":"http://qe-blade-14.idm.lab.bo=
s.redhat.com:3005/api/load_balancers/webTrafficBalancer","instances":[],"li=
steners":[{"load_balancer_port":80,"instance_port":3001,"protocol":"HTTP"}]=
,"public_addresses":["webTrafficBalancer-1078254100.us-east-1.elb.amazonaws=
.com"],"id":"webTrafficBalancer","created_at":"Wed Apr 25 19:36:25 UTC 2012=
"}]}[root@qe-blade-14 logs]#=20
> The same is true if the load_balancer was created through the GUI selecti=
ng 'us-east-1b' as the realm. Snippet from deltacloud server output is copi=
ed below:
>  INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1=
.amazonaws.com:443
> {:availability_zones=3D>["us-east-1b"], :created=3D>Wed Apr 25 20:48:39 U=
TC 2012, :instances=3D>[], :dns_name=3D>"loadBalancerFromGUI-1426417834.us-=
east-1.elb.amazonaws.com", :created_time=3D>Wed Apr 25 20:48:39 UTC 2012, :=
health_check=3D>{:healthy_threshold=3D>10, :unhealthy_threshold=3D>2, :time=
out=3D>5, :interval=3D>30, :target=3D>"TCP:3001"}, :listeners=3D>[{:load_ba=
lancer_port=3D>80, :instance_port=3D>3001, :protocol=3D>"TCP"}], :name=3D>"=
loadBalancerFromGUI", :load_balancer_name=3D>"loadBalancerFromGUI"}
> Deltacloud still returns 'us-east-1a' as the realm:
> curl -X GET --user "<username>:<password>" "http://qe-blade-14.idm.lab.bo=
s.redhat.com:3005/api/load_balancers?format=3Djson"{"load_balancers":[{"rea=
lms":[{"limit":"unlimited","state":"available","name":"us-east-1a","id":"us=
-east-1a"}],"href":"http://qe-blade-14.idm.lab.bos.redhat.com:3005/api/load=
_balancers/loadBalancerFromGUI","instances":[],"listeners":[{"load_balancer=
_port":80,"instance_port":3001,"protocol":"TCP"}],"public_addresses":["load=
BalancerFromGUI-1426417834.us-east-1.elb.amazonaws.com"],"id":"loadBalancer=
FromGUI","created_at":"Wed Apr 25 20:48:39 UTC 2012"},{"realms":[{"limit":"=
unlimited","state":"available","name":"us-east-1a","id":"us-east-1a"}],"hre=
f":"http://qe-blade-14.idm.lab.bos.redhat.com:3005/api/load_balancers/webTr=
afficBalancer","instances":[],"listeners":[{"load_balancer_port":80,"instan=
ce_port":3001,"protocol":"HTTP"}],"public_addresses":["webTrafficBalancer-1=
078254100.us-east-1.elb.amazonaws.com"],"id":"webTrafficBalancer","created_=
at":"Wed Apr 25 19:36:25 UTC 2012"}]}[root@qe-blade-14 logs]#=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira