Ronelle Landy created DTACLOUD-200:
--------------------------------------

             Summary: 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 clone: 
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 = restClient.post( path: '/api/load_balancers', 
contentType: ContentType.XML,
                                headers: [Accept: 'application/xml'], 
requestContentType : ContentType.URLENC,
                                body: ['name=webTrafficBalancer' + 
                                        '&realm_id=us-east-1b' +
                                        '&listener_protocol=HTTP' +
                                        '&listener_balancer_port=80' +
                                        '&listener_instance_port=3001'])

Delatcloud returns 'us-east-1a' as the realm:

curl -X GET --user "username:password" 
"http://qe-blade-14.idm.lab.bos.redhat.com:3005/api/load_balancers?format=json";
{"load_balancers":[{"realms":[{"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/webTrafficBalancer","instances":[],"listeners":[{"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]# 

The same is true if the load_balancer was created through the GUI selecting 
'us-east-1b' as the realm. Snippet from deltacloud server output is copied 
below:

 INFO -- : Opening new HTTPS connection to 
elasticloadbalancing.us-east-1.amazonaws.com:443
{:availability_zones=>["us-east-1b"], :created=>Wed Apr 25 20:48:39 UTC 2012, 
:instances=>[], 
:dns_name=>"loadBalancerFromGUI-1426417834.us-east-1.elb.amazonaws.com", 
:created_time=>Wed Apr 25 20:48:39 UTC 2012, 
:health_check=>{:healthy_threshold=>10, :unhealthy_threshold=>2, :timeout=>5, 
:interval=>30, :target=>"TCP:3001"}, :listeners=>[{:load_balancer_port=>80, 
:instance_port=>3001, :protocol=>"TCP"}], :name=>"loadBalancerFromGUI", 
:load_balancer_name=>"loadBalancerFromGUI"}

Deltacloud still returns 'us-east-1a' as the realm:

curl -X GET --user "<username>:<password>" 
"http://qe-blade-14.idm.lab.bos.redhat.com:3005/api/load_balancers?format=json"{"load_balancers":[{"realms":[{"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":["loadBalancerFromGUI-1426417834.us-east-1.elb.amazonaws.com"],"id":"loadBalancerFromGUI","created_at":"Wed
 Apr 25 20:48:39 UTC 
2012"},{"realms":[{"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/webTrafficBalancer","instances":[],"listeners":[{"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]# 


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


Reply via email to