You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Ivan Efremov <eo...@yandex.ru> on 2014/06/18 05:25:58 UTC
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
Re: Managing individual ESXi instances
Posted by ilya musayev <il...@gmail.com>.
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 storage iSCSI, local datastore formatted as VMFS and NFS.
On 6/18/14, 8:53 AM, Tim Mackey wrote:
> 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 <
> mike.tutkowski@solidfire.com> wrote:
>
>> 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.tutkowski@solidfire.com> wrote:
>>
>>> 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 <eo...@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" <Al...@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>*™*
>>>
>>
>>
>> --
>> *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>*™*
>>
Re: Managing individual ESXi instances
Posted by Mike Tutkowski <mi...@solidfire.com>.
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 <tm...@gmail.com> wrote:
> 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 <
> mike.tutkowski@solidfire.com> wrote:
>
> > 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.tutkowski@solidfire.com> wrote:
> >
> > > 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 <eo...@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" <Al...@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>*™*
> > >
> >
> >
> >
> > --
> > *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>*™*
> >
>
--
*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>*™*
Re: Managing individual ESXi instances
Posted by Tim Mackey <tm...@gmail.com>.
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 <
mike.tutkowski@solidfire.com> wrote:
> 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.tutkowski@solidfire.com> wrote:
>
> > 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 <eo...@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" <Al...@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>*™*
> >
>
>
>
> --
> *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>*™*
>
Re: Managing individual ESXi instances
Posted by Mike Tutkowski <mi...@solidfire.com>.
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.tutkowski@solidfire.com> wrote:
> 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 <eo...@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" <Al...@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>*™*
>
--
*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>*™*
Re: Managing individual ESXi instances
Posted by Mike Tutkowski <mi...@solidfire.com>.
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 <eo...@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" <Al...@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>*™*
Re: Managing individual ESXi instances
Posted by Ivan Efremov <eo...@yandex.ru>.
Thanks for the reply!
Ivan
18.06.2014, 21:43, "Alex Huang" <Al...@citrix.com>:
> Hi Ivan,
>
> To introduce a new hypervisor, it's a matter of
> - Adding a new Discoverer implementation to tell CloudStack which Resource best works with the new Hypervisor.
> - Adding a new Resource implementation that deals with all of the hypervisor commands sent to it. This is the big part due to the large set of commands we send to it.
>
> For someone who understands CloudStack code and the hypervisor well, I think a prototype can be done in about two months or so. For ESX, you have to figure out a how to map functions that CS supports but is not with ESX. For example, I think migration and live storage migration. You can decide not to support them in the prototype and just support simple vm/volume/network life cycle for now.
>
> --Alex
>> -----Original Message-----
>> From: Ivan Efremov [mailto:eo2@yandex.ru]
>> Sent: Wednesday, June 18, 2014 8:31 AM
>> To: dev@cloudstack.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 major points that should be patched when adding a new
>> hypervisor type?
>>
>> Thanks,
>> Ivan
>>
>> 18.06.2014, 18:24, "Alex Huang" <Al...@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
RE: Managing individual ESXi instances
Posted by Alex Huang <Al...@citrix.com>.
Hi Ivan,
To introduce a new hypervisor, it's a matter of
- Adding a new Discoverer implementation to tell CloudStack which Resource best works with the new Hypervisor.
- Adding a new Resource implementation that deals with all of the hypervisor commands sent to it. This is the big part due to the large set of commands we send to it.
For someone who understands CloudStack code and the hypervisor well, I think a prototype can be done in about two months or so. For ESX, you have to figure out a how to map functions that CS supports but is not with ESX. For example, I think migration and live storage migration. You can decide not to support them in the prototype and just support simple vm/volume/network life cycle for now.
--Alex
> -----Original Message-----
> From: Ivan Efremov [mailto:eo2@yandex.ru]
> Sent: Wednesday, June 18, 2014 8:31 AM
> To: dev@cloudstack.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 major points that should be patched when adding a new
> hypervisor type?
>
>
> Thanks,
> Ivan
>
> 18.06.2014, 18:24, "Alex Huang" <Al...@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
Re: Managing individual ESXi instances
Posted by Ivan Efremov <eo...@yandex.ru>.
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" <Al...@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
RE: Managing individual ESXi instances
Posted by Alex Huang <Al...@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