deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronelle Landy (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DTACLOUD-206) Distinguising public and private addresses for instances launched through Deltacloud to Openstack provider
Date Mon, 27 Aug 2012 12:56:07 GMT

     [ https://issues.apache.org/jira/browse/DTACLOUD-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ronelle Landy closed DTACLOUD-206.
----------------------------------


Closing JIRA as fixed in openstack gem 1.0.3 ... see test output in comments above

Additional issues mention in this JIRA are tracked in the openstack gem as per marios's comments.
                
> 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: Ronelle Landy
>
> 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

Mime
View raw message