deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (JIRA)" <>
Subject [jira] [Closed] (DTACLOUD-443) Openstack Provider 'Availability Zones'
Date Thu, 07 Feb 2013 16:01:14 GMT


Marios Andreou closed DTACLOUD-443.

> Openstack Provider 'Availability Zones'
> ---------------------------------------
>                 Key: DTACLOUD-443
>                 URL:
>             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:

View raw message