Return-Path: X-Original-To: apmail-deltacloud-dev-archive@www.apache.org Delivered-To: apmail-deltacloud-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 25225D202 for ; Thu, 23 Aug 2012 15:10:43 +0000 (UTC) Received: (qmail 58679 invoked by uid 500); 23 Aug 2012 15:10:43 -0000 Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org Received: (qmail 58667 invoked by uid 500); 23 Aug 2012 15:10:43 -0000 Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@deltacloud.apache.org Delivered-To: mailing list dev@deltacloud.apache.org Received: (qmail 58657 invoked by uid 99); 23 Aug 2012 15:10:42 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Aug 2012 15:10:42 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9BE442C0A54 for ; Thu, 23 Aug 2012 15:10:42 +0000 (UTC) Date: Fri, 24 Aug 2012 02:10:42 +1100 (NCT) From: "Christian Karnath (JIRA)" To: dev@deltacloud.apache.org Message-ID: <1200418748.5815.1345734642639.JavaMail.jiratomcat@arcas> In-Reply-To: <1910843043.23484.1336075009411.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (DTACLOUD-206) Distinguising public and private addresses for instances launched through Deltacloud to Openstack provider MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DTACLOUD-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440365#comment-13440365 ] Christian Karnath commented on DTACLOUD-206: -------------------------------------------- any news regarding this issue? it is possible to implement this like the rubygem does? > 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 -------------- > > > >
10.4.108.65
>
15.185.113.54
> > > root > ------------------------------------------------------ > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira