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

Christian Karnath commented on DTACLOUD-446:
--------------------------------------------

Hey Marios,

I'm using the separate driver for hpcloud.com in my own environment as a quick 
and functional solution to address the region issue in particular and to 
simplify the connection parameters without breaking any openstack driver stuff. 
In the long term I also think it's better to have a more generalized solution 
within the openstack driver which cleanly implements the realms collection and 
which statically includes public cloud parameters as described by you in 
DTACLOUD-443. 
BTW: Thanks for the info about the CLA. This is the first apache project I'm 
involved in and that’s why I haven't signed any CLA yet. I will catch up asap.

Christian

                
> Openstack - make it easier to connect to 'public' openstack providers (like 
> HP)
> -------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-446
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-446
>             Project: DeltaCloud
>          Issue Type: Wish
>            Reporter: Marios Andreou
>            Assignee: Marios Andreou
>         Attachments: 
> 0001-Driver-for-hp-to-simplify-the-connection-parameters-.patch
>
>
> (from irc discussion with Christian Karnath)
> (12:36:20) Christian_: marios: in general - does a speciazlized hp driver 
> makes sense? i mean hp is a public cloud provider like amazon and for ec2 for 
> example you dont need to supply a api_url
> (12:36:57) marios: Christian_: hmm.. not sure about that - kinda defeats the 
> object/goes against the spirit  of openstack
> (12:37:22) pblaho [pblaho@nat/redhat/x-tdojjupsuwxxrqjs] entered the room.
> (12:37:24) marios: Christian_: i mean - unless there's some wild deviation in 
> the hp implementation from vanilla openstack - but afaik there isn't
> (12:37:41) marios: Christian_: it would mean we'd need a new driver for every 
> openstack provider out there
> (12:39:35) marios: Christian_: do you think we need a specialised hp driver?
> (12:40:36) marios: Christian_: if the only reason for it is the 'provider 
> url' - we could consider another solution.. like an additional parameter .... 
> deltacloudd -i openstack -api_url 'hp'
> (12:40:43) marios: Christian_: and we define that somewhere
> (12:40:49) marios: Christian_: or are you thinking about more that this?
> (12:41:04) Christian_: marios: i know... hmm good question. the benefit will 
> be a longer list of supported providers (not every users know that hp runs 
> openstack) 
> (12:41:16) Christian_: marios: well and the setup is muck easier
> (12:41:28) Christian_: marios: only username, password and region is required 
> as an input parameter
> (12:42:01) Christian_: marios: it would be as easy as connecting to ec2
> (12:42:43) marios: Christian_: right - then how about what i suggest above 
> then:
> (12:42:51) marios: (12:40:36) marios: Christian_: if the only reason for it 
> is the 'provider url' - we could consider another solution.. like an 
> additional parameter .... deltacloudd -i openstack -api_url 'hp'
> (12:43:14) marios: Christian_: (just an example - we can think/discuss the 
> syntax etc)
> (12:43:38) Christian_: marios: additional parameter is fine too (if 
> /api/realms is implemented for the realm stuff...)
> (12:44:06) marios: Christian_: ok - lets put this on ice for now - i'll file 
> a jira for it now so we don't forget... sec

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

Reply via email to