Unless I missed it, Ian neglected to ACK the patch for Image Factory, but he did push it
into github with 'vsphere'.
On 07/07/2011 07:44 PM, David Lutterkort wrote:
> On Thu, 2011-07-07 at 14:13 +0200, Tomas Von Veschler wrote:
>> On 07/07/2011 10:42 AM, Mark McLoughlin wrote:
>>> Hey,
>>>
>>> We have an inconsistency where the Deltacloud 'rhevm' and
'vsphere'
>>> driver names differ from the 'rhev-m' and 'vmware' names we
use for
>>> Image Factory targets and Conductor provider types.
>>
>> Maybe dumb question, shouldn't it be "vcenter" instead of
"vsphere"?
>
> From browsing Wikipedia and vmware.com[1], it seems vSphere is the
> product we are targetting with the driver, and vCenter the umbrella name
> for a bunch of related products - so I'd stick with vSphere. But by all
> means, if somebody with VMWare experience can give an authoritative
> answer to what this beast is called, we'll change it.
>
> For all I care, we can call it Barney as long as (1) it doesn't sing and
> (2) people don't confuse it with a driver for vCloud
>
> David
>
> [1] Sidebar at
http://www.vmware.com/support/pubs/sdk_pubs.html
Ahm okey. If naming the driver as the API then vsphere looks right to
me. From
http://www.vmware.com/support/developer/vc-sdk/ :
"ESX/ESXi 4.1 and vCenter Server 4.1 systems provide a Web service that
you can access by using the vSphere API."
Tomas
_______________________________________________
aeolus-devel mailing list
aeolus-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/aeolus-devel