You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Michal Fojtik (JIRA)" <ji...@apache.org> on 2012/12/13 14:22:12 UTC
[jira] [Updated] (DTACLOUD-399) Make VSphere API_PROVIDER format
consistent with other drivers
[ https://issues.apache.org/jira/browse/DTACLOUD-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik updated DTACLOUD-399:
-----------------------------------
Description:
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 :-)
was:
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.
Note: This should be done without breaking backward compatibility :-)
> 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