Oh, I was going to ask, though, on a related note...don't we duplicate
certain hypervisor features in CS today...like HA for some platforms?
On Wed, Mar 20, 2013 at 8:01 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Thanks for that info, Kelven!
>
>
> On Wed, Mar 20, 2013 at 7:47 P
Thanks for that info, Kelven!
On Wed, Mar 20, 2013 at 7:47 PM, Kelven Yang wrote:
> VMware is a very different animal in CloudStack, the reason lies on the
> integration point, in XS/KVM case, CloudStack manages hypervisor host
> directly, while in VMware case, the integration point is at vCent
VMware is a very different animal in CloudStack, the reason lies on the
integration point, in XS/KVM case, CloudStack manages hypervisor host
directly, while in VMware case, the integration point is at vCenter
instead of ESX/ESXi hosts, therefore, ESX/ESXi hosts are actually
indirectly managed by C
Hey Kelven,
Can you clarify for me something?
In your view, is creating a XenServer storage repository in the way I
described earlier different (easier) than creating a VMware datastore?
If Edison's storage plug-in framework is not going to do this, then I'm
confused what value it brings to the
Interesting...well, hopefully Edison can comment and clear this up.
Thanks, Kelven!
On Wed, Mar 20, 2013 at 7:22 PM, Kelven Yang wrote:
> If this is the case, the storage plug-in framework needs to be adaptive to
> that a datastore may be preset from external source. Creating VMFS
> datastore
If this is the case, the storage plug-in framework needs to be adaptive to
that a datastore may be preset from external source. Creating VMFS
datastore involves with complex interactive flow, for example, it requires
administrator to enable iScsi adapter on every ESX host under a cluster.
It does n
Thanks, Kevlen
That makes sense that in pre 4.2 we don't use VI SDK to create a datastore
as we require the datastore to be set up ahead of creating Primary Storage.
However, as far as I understand Edison's 4.2 storage plug-in framework,
which creates the necessary storage when a VM is spun up or
We don't use VI SDK in CloudStack for VMware integration.
For VMFS datastore, CloudStack will not create it and will rely on vCenter
to do it. To enable a VMFS datastore involves a series of steps, the flow
is provided by vCenter.
Kelven
On 3/20/13 1:26 PM, "Mike Tutkowski" wrote:
>Hi everyone
If I'm not mistaken, Edison had to accomplish this for his storage
framework in CS 4.2, so maybe he'll be able to shed some light on this
question. :)
On Wed, Mar 20, 2013 at 2:26 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Hi everyone,
>
> Has anyone every used the VI SDK or th
Hi everyone,
Has anyone every used the VI SDK or the VI Java API to create a VMFS
datastore that makes use of an iSCSI target?
I've been searching all over Google for some decent sample code. I've
found bits and pieces (more about NFS than iSCSI), but nothing that brings
it all together.
This w
10 matches
Mail list logo
