[
https://issues.apache.org/jira/browse/DTACLOUD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-399.
----------------------------------
Resolution: Fixed
Fixed with patch in: http://tracker.deltacloud.org/patch/8786328f
[root@qe-blade-02 server]# API_PROVIDER=http://10.16.120.241/api
./bin/deltacloudd -i vsphere -r <host> -f cimi,deltacloud
Starting Deltacloud API :: vsphere :: http://10.16.120.241/api ::
<host>:3001/api
>> Thin web server (v1.5.0 codename Knife)
>> Debugging ON
>> Maximum connections set to 1024
>> Listening on <host>:3001, CTRL+C to stop
10.10.51.90 - - [02/Jan/2013 09:47:53] "POST /cimi/machines?format=xml
HTTP/1.1" 201 829 4.5753
> Make VSphere API_PROVIDER format consistent with other drivers
> --------------------------------------------------------------
>
> Key: DTACLOUD-399
> URL: https://issues.apache.org/jira/browse/DTACLOUD-399
> Project: DeltaCloud
> Issue Type: Bug
> Reporter: Michal Fojtik
>
> In RHEV-M the API_PROVIDER is a full URL (https, /api), same for OpenStack,
> but for VSphere we use hostname. We should be consistent and offer the same
> schema to VSphere.
> Example:
> $ ./bin/deltacloudd -i vsphere -P 'https://vsphere.host/api' # -> this should
> work as well as giving 'vsphere.host' parameter.
> Note: This should be done without breaking backward compatibility :-)
--
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
