deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-443) Openstack Provider 'Availability Zones'
Date Thu, 07 Feb 2013 15:59:13 GMT

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

Marios Andreou commented on DTACLOUD-443:
-----------------------------------------

OK - Christian thanks for all you help and feedback here:

I pushed the patches above with commit 3d318d252f5289322b0798a65ff81c6604aef946  - including
a minor modification:

* as we spoke about briefly on irc, I changed the way region is specified within the api_provider.
Instead of using "::" I used ";" as delimiter - because this complies with what other similar
drivers do in such cases (see rhevm) and also as David Lutterkort pointed out - using ';'
means the API_PROVIDER string is a valid URI

WRT the functionality for instances and creation etc you mentioned above:

* when you create an instance, if no realm specified (via api_provider) a random one is chosen
and realm_id is correctly populated on the create_instance response

The case of getting all instances from all realms is problematic for me. It diverges from
the behaviour in other drivers (where you specify a 'provider' and see the instances in that
'provider'). Also, I don't know what to do with the case of a single instance being requested
- servers themselves (returned from openstack) don't know which region they're in. So what
do we do in this case? I think for now I'm going to push these patches with the realms functionality
and we should open a new issue to discuss and work out what to do with the instances. 

thanks marios

                
> 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