deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-206) Distinguising public and private addresses for instances launched through Deltacloud to Openstack provider
Date Fri, 18 May 2012 12:56:07 GMT


Marios Andreou commented on DTACLOUD-206:

Not too sure what to do about this. The problem is that Openstack actually calls both of these
addresses 'private'. This is somewhat explained here
and leaves the hope that this functionality may be improved in future releases.

So for example, taking to the HP cloud: 

res = @connection.req("GET", "/servers/127883/ips")
(rdb:1) res.body
"{\"addresses\": {\"private\": [{\"version\": 4, \"addr\": \"\"}, {\"version\":
4, \"addr\": \"\"}]}}"

So both addresses are 'private'. I *think* you need to put your Instance into the 'public'
network in order for the IP address to be labelled as 'public' - so e.g. as explained in
I tried:

(rdb:1) res = @connection.req("GET", "/servers/127883/ips/public")
OpenStack::Compute::Exception::ItemNotFound Exception: Instance is not a member of specified

The 'hack' explained in the post above only works if you've associated a floating
IP. So for example, after association of a floating IP:

(rdb:1) res = @connection.req("GET", "/os-floating-ips")
#<Net::HTTPOK 200 OK readbody=true>
(rdb:1) res.body
"{\"floating_ips\": [{\"instance_id\": 127883, \"ip\": \"\", \"fixed_ip\": \"\",
\"id\": 1913}]}"

and you could use this info to determine which of the two server addresses was the public

One way we *could* go is to use some kind of pattern matching on, - it would work for now. But I'm not sure this is the right approach. Needs


> Distinguising public and private addresses for instances launched through Deltacloud
to Openstack provider 
> -----------------------------------------------------------------------------------------------------------
>                 Key: DTACLOUD-206
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: Deltacloud git commit version: c13da7b50bbbbdc529b42207f58dbe5099006ad1
> RHEL 6.2, Fedora 16
> Openstack V2.0
>            Reporter: Ronelle Landy
>            Assignee: Marios Andreou
> Looking at an instance launched through Deltacloud to the Openstack provider, there does
not seems to be a public IP address reported by Deltacloud. What HP shows as a 'fixed public
address', Deltacloud shows as a second 'private address':
> ------- Copying from HP interface ----------
> Server Details 
>  Status:  Active 
>  Flavor:  standard.xsmall - 1 vCPU / 1 GB RAM / 30 GB HD  
>  Image:  1361 - Debian Squeeze 6.0.3 Server 64-bit 20120123 
> Key Pair: 
> Fixed Public IP: 
>  Floating Public IPs: 
> Private IP:  
> Started:  2012-04-30 09:43:02 -0700  
> Age:  2 minutes 
> --------- Copying from deltacloud --------------
>  <link href=';instance_id=115785'
method='post' rel='create_image' />
>   </actions>
>   <public_addresses></public_addresses>
>   <private_addresses><address type='ipv4'></address>
> <address type='ipv4'></address></private_addresses>
>   <authentication type='password'>
>     <login>
>       <username>root</username>
> ------------------------------------------------------
> Note from Marios:
> see and

> I revisited those threads now to see if it was fixed and came across
... so it seems it's ultimately an openstack issue. JIRA please.. we need to figure out how
we can capture this reliably in deltacloud.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message