IIRC, the reason is because the vCenter API is more powerful than the ESX API.
At the time (before Apache), the features that requested needed vCenter.
There's currently no proposal to use plain ESXi. Would love to see one though.
--Alex
> -Original Message-
> From: Ivan Efremov [mail
I know, for example, that I'd like to test out that managed storage works
with it.
I've added support for managed storage to XenServer, ESX/vCenter, and KVM
for CloudStack.
Another hypervisor type - to me personally - means I'd to verify managed
storage works with it.
Depending on how radical th
Or I'd like to know if it doesn't work (as is the case for Hyper-V until I
get time to add that kind of support for it).
On Wed, Jun 18, 2014 at 9:37 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> I know, for example, that I'd like to test out that managed storage works
> with it.
>
Hi Alex,
How do you think, what is the rough estimation of adding ESX API support to
CloudStack?
AFAIU the main point of integration of the new API is plugins/hypervisors. Are
there any other major points that should be patched when adding a new
hypervisor type?
Thanks,
Ivan
18.06.2014, 18:2
Mike,
I wouldn't expect things with the VMware Hypervisor (what they refer to
standalone ESXi) to work out of the box. Since you can't cluster things,
I'd expect only raw iSCSI to work, but it's been years since I've worked
with raw ESXi.
-tim
On Wed, Jun 18, 2014 at 11:40 AM, Mike Tutkowski <
Well, as long as the API to standalone ESX is similar to vCenter's API
(which much of it is, I think), it might not be a ton of work to get the
managed storage part to work, but it's hard to say.
On Wed, Jun 18, 2014 at 9:53 AM, Tim Mackey wrote:
> Mike,
>
> I wouldn't expect things with the VM
dstack.apache.org
> Subject: Re: Managing individual ESXi instances
>
> Hi Alex,
>
> How do you think, what is the rough estimation of adding ESX API support to
> CloudStack?
> AFAIU the main point of integration of the new API is plugins/hypervisors.
> Are there any other
ow.
>
> --Alex
>> -Original Message-
>> From: Ivan Efremov [mailto:e...@yandex.ru]
>> Sent: Wednesday, June 18, 2014 8:31 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: Managing individual ESXi instances
>>
>> Hi Alex,
>>
>>
The WSDL is still available on ESXi port 443, you are loosing the
vCenter fanciness - which maybe big for some folks, but other than that
- it works fine.
The API calls will have to be altered as they will no longer be bound to
vCenter, but most of the calls can be re-used.
You can use local
