[
https://issues.apache.org/jira/browse/DTACLOUD-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442345#comment-13442345
]
Marios Andreou commented on DTACLOUD-206:
-----------------------------------------
OK - Christian thank you very much for your extensive testing - much
appreciated! Indeed from a quick poke at the API docs it seems the issues are
Openstack API version related. For example see
http://wiki.openstack.org/ReleaseNotes/Diablo#OpenStack_API_1.1_issues - e.g.
"Instances still show both ids and UUIDs in responses" for Diablo.
I think since this JIRA ticket is specifically about public/private addresses
and that is now fixed, I'm going to close this issue. I have moved your
comments to a new issue against the ruby-openstack gem here
https://github.com/ruby-openstack/ruby-openstack/issues/9 - the issues you
report aren't to do with deltacloud but with the gem itself. I've have to spend
some time on other issues over the next few days but will get round to fixing
those asap. Thanks again for your help.
Ronelle - do you agree we should close this issue (since its about
public/private addresses)? I'll mark as resolved and assign to you - you can
close it if you think its ok.
thanks, marios
> Distinguising public and private addresses for instances launched through
> Deltacloud to Openstack provider
> -----------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-206
> URL: https://issues.apache.org/jira/browse/DTACLOUD-206
> Project: DeltaCloud
> Issue Type: Improvement
> 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: 15.185.113.54
> Floating Public IPs:
> Private IP: 10.4.108.65
> Started: 2012-04-30 09:43:02 -0700
> Age: 2 minutes
> --------- Copying from deltacloud --------------
> <link
> href='http://qe-blade-14.idm.lab.bos.redhat.com:3008/api/images;instance_id=115785'
> method='post' rel='create_image' />
> </actions>
> <public_addresses></public_addresses>
> <private_addresses><address type='ipv4'>10.4.108.65</address>
> <address type='ipv4'>15.185.113.54</address></private_addresses>
> <authentication type='password'>
> <login>
> <username>root</username>
> ------------------------------------------------------
> Note from Marios:
> see https://connect.hpcloud.com/article/api-serversdetail and
> https://connect.hpcloud.com/question/276/public-addresses-fog.
> I revisited those threads now to see if it was fixed and came across
> https://answers.launchpad.net/nova/+question/185110 ... 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
