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 F2109D320 for ; Wed, 6 Feb 2013 14:11:15 +0000 (UTC) Received: (qmail 55247 invoked by uid 500); 6 Feb 2013 14:11:15 -0000 Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org Received: (qmail 55115 invoked by uid 500); 6 Feb 2013 14:11:15 -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 54897 invoked by uid 99); 6 Feb 2013 14:11:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2013 14:11:14 +0000 Date: Wed, 6 Feb 2013 14:11:14 +0000 (UTC) From: "Christian Karnath (JIRA)" To: dev@deltacloud.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DTACLOUD-443) Openstack Provider 'Availability Zones' MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DTACLOUD-443?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13= 572427#comment-13572427 ]=20 Christian Karnath commented on DTACLOUD-443: -------------------------------------------- OK, I did the test drive and here are my notes: - requesting /api/realms against openstack returns all regions which are av= ailable. I comply with this solution. - requesting /api/instances is only working when I specify a region within = API_PROVIDER. Would it be possible to loop through all realms when omitting= a specific region? It would be very helpful if both ways are possible. - the realm attribute is not set correctly for a single instance and always= pointing to the =E2=80=98default=E2=80=99 realm: [=E2=80=A6] <= /realm> [=E2=80=A6] =20 > Openstack Provider 'Availability Zones' > --------------------------------------- > > Key: DTACLOUD-443 > URL: https://issues.apache.org/jira/browse/DTACLOUD-443 > Project: DeltaCloud > Issue Type: Improvement > Reporter: Marios Andreou > Assignee: Marios Andreou > Attachments: 0001-Deltacloud-adds-maps-openstack-regions-to-delta= cloud.patch > > > (from Christian Karnath, via e-mail): > Hey Marios, > HPCloud provides three different compute clouds (availability zones) at t= he moment. How can I specify which compute cloud is used with the openstack= driver, because the API credentials and the URL endpoint of the identity s= ervice (keystone) are the same. Connecting and authenticating directly to t= he nova-api of a specific compute cloud is not possible, because HPCloud is= using keystone as a centralized identity management solution. > I guess when authentication against the identity service all three comput= e clouds are returned, but only the first cloud is manageable with deltaclo= ud? Would it make sense to re-implement /api/realms for this case? The curr= ent /api/realms implementation could be retained for users who are connecti= on directly to a specific nova api endpoint (i. e. an openstack environment= s without keystone). > Best > Christian -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira