deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Karnath (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DTACLOUD-443) Openstack Provider 'Availability Zones'
Date Wed, 06 Feb 2013 14:21:13 GMT

    [ https://issues.apache.org/jira/browse/DTACLOUD-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572427#comment-13572427
] 

Christian Karnath edited comment on DTACLOUD-443 at 2/6/13 2:19 PM:
--------------------------------------------------------------------

OK, I did a first test drive and here are my notes:

- requesting /api/realms against openstack returns all regions which are available. 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 and requesting a
collection of instances? It would be very helpful if both ways are possible. Every single
instance could be flagged with the specific realm-id 

- the realm-id is always pointing to the ‘default’ realm:
<instance href='http://127.0.0.1:3001/api/instances/1047655' id='1047655'>
[…]
  <realm href='http://127.0.0.1:3001/api/realms/default' id='default'></realm>
[…]
</instance>

- launching a new instance and setting the realm_id is a good solution to specify the region
-> I comply with this solution too
                
      was (Author: karnath):
    OK, I did a first test drive and here are my notes:

- requesting /api/realms against openstack returns all regions which are available. 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 and requesting a
collection of instances? It would be very helpful if both ways are possible. Every single
instance could be flagged with the specific realm-id 

- the realm-id is always pointing to the ‘default’ realm:
<instance href='http://127.0.0.1:3001/api/instances/1047655' id='1047655'>
[…]
  <realm href='http://127.0.0.1:3001/api/realms/default' id='default'></realm>
[…]
</instance>

- launching a new instance and setting the realm_id is a good solution to specific the region
                  
> 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-deltacloud.patch
>
>
> (from Christian Karnath, via e-mail):
> Hey Marios,
> HPCloud provides three different compute clouds (availability zones) at the 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 service (keystone) are the same. Connecting and authenticating
directly to the 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 compute clouds are
returned, but only the first cloud is manageable with deltacloud? Would it make sense to re-implement
/api/realms for this case? The current /api/realms implementation could be retained for users
who are connection directly to a specific nova api endpoint (i. e. an openstack environments
without keystone).
> Best
> Christian

--
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