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 the changes for an ESX-only solution are, it may
or may not work "out of the box" for managed storage.
On Wed, Jun 18, 2014 at 9:30 AM, Ivan Efremov <eo2@yandex.ru> wrote:
> 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:24, "Alex Huang" <Alex.Huang@citrix.com>:
> > 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 [mailto:eo2@yandex.ru]
> >> Sent: Tuesday, June 17, 2014 8:26 PM
> >> To: dev@cloudstack.apache.org
> >> Subject: Managing individual ESXi instances
> >>
> >> Hi all,
> >>
> >> I've sent this mail to the users list but this one looks as the better
> destination.
> >>
> >> I'm new to the CloudStack platform and I'm wondering why the platform
> >> does need the vCenter API and can not use ESXi directly,
> >>
> >> Can anyone elaborate on this?
> >> Are there any proposals for adding ESXi integration to CloudStack?
> >>
> >> Thanks,
> >> Ivan
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*
|