Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DD3A511802 for ; Wed, 18 Jun 2014 15:54:05 +0000 (UTC) Received: (qmail 62010 invoked by uid 500); 18 Jun 2014 15:54:05 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 61965 invoked by uid 500); 18 Jun 2014 15:54:05 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 61953 invoked by uid 99); 18 Jun 2014 15:54:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 15:54:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tmackey@gmail.com designates 209.85.213.49 as permitted sender) Received: from [209.85.213.49] (HELO mail-yh0-f49.google.com) (209.85.213.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 15:54:01 +0000 Received: by mail-yh0-f49.google.com with SMTP id f73so754654yha.8 for ; Wed, 18 Jun 2014 08:53:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=kyyv19LEpzExbKZy96zIXc3D6M2qCuWXTBl45QVIgDw=; b=Vu1dXTe+PTght3xXYy0Zkf76DiSV7Hn0aR7j+hwrLMfF7I9LeNGb6xPTGj3XiPcWVd 0x+YGJ6U8OOwST5QPFkLxlV7V5fYrZlCuC2yVprnplbzdll2lN2Iz/CI1KULPlvT9ZAc 3OIA2WwrMNP3dHTeKwyc7kIcWzsLIAosweXULFUZBom4573lhuEtHFuG1lKmoUetfzha HKxvCy/CHhx0aWeB5DZxaFTGAkzCYbBfzXheMjOACTwu446X1w0hF5VcHNwu+nJH+Ovy Yl6CuPIhuU/FCrX3gU3Gthhlt+fuccMtWPCVQ/hUY66mFwEXi+FXPp2gzo/7IavY8LhW aWlA== X-Received: by 10.236.160.67 with SMTP id t43mr56360400yhk.11.1403106820773; Wed, 18 Jun 2014 08:53:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.166.86 with HTTP; Wed, 18 Jun 2014 08:53:20 -0700 (PDT) In-Reply-To: References: <2294901403061958@web5h.yandex.ru> <20CF38CB4385CE4D9D1558D52A0FC058757EF7@SJCPEX01CL03.citrite.net> <1449801403105446@web11g.yandex.ru> From: Tim Mackey Date: Wed, 18 Jun 2014 11:53:20 -0400 Message-ID: Subject: Re: Managing individual ESXi instances To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=20cf304353a8a25c1b04fc1e437a X-Virus-Checked: Checked by ClamAV on apache.org --20cf304353a8a25c1b04fc1e437a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 wor= ks > > with it. > > > > I've added support for managed storage to XenServer, ESX/vCenter, and K= VM > > for CloudStack. > > > > Another hypervisor type - to me personally - means I'd to verify manage= d > > storage works with it. > > > > Depending on how radical the changes for an ESX-only solution are, it m= ay > > or may not work "out of the box" for managed storage. > > > > > > On Wed, Jun 18, 2014 at 9:30 AM, Ivan Efremov wrote: > > > >> Hi Alex, > >> > >> How do you think, what is the rough estimation of adding ESX API suppo= rt > >> 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" : > >> > IIRC, the reason is because the vCenter API is more powerful than th= e > >> 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 > > *=E2=84=A2* > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkowski@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > *=E2=84=A2* > --20cf304353a8a25c1b04fc1e437a--