I've CCed Edison on this. I think he has a bunch of experience with S3 and
Swift integration into CloudStack.
On Fri, Aug 22, 2014 at 11:46 AM, Francois Gaudreault <
fgaudrea...@cloudops.com> wrote:
> Ok. I digged a little more, and now I know why it fails, but don't know
> how to fix this :) I
Ok. I digged a little more, and now I know why it fails, but don't know
how to fix this :) I opened a defect:
https://issues.apache.org/jira/browse/CLOUDSTACK-7406
To me this is a fairly important one since is does have impacts on other
features (e.g SF storage plugin, and maybe usage reporting
As an FYI, the reason this still works for "traditional" (so-called
non-managed) primary storage in CloudStack on XenServer is that those
environments put many CloudStack root and data disks on the same backend
SAN volume (or NFS share).
Even if the size of the root disk is incorrectly specified,
Just to clarify: "Mark" is really me: "Mike" :)
I give Daan a hard time about this. :) He called me Mark at CCCEU in Denver
a few times during a presentation and it seems like that's been like a
second name for me.
On Fri, Aug 22, 2014 at 10:27 AM, Francois Gaudreault <
fgaudrea...@cloudops.com>
Mark and I worked on that off-list, and it looks like it's a Swift
provider issue. See, in ACS, when you use NFS, the reported template
size is the ROOT volume size. While using swift, it's the VHD file size,
which is not the ROOT volume size.
SolidFire will rely on this metric to create the L
I would also add that the ROOT volume created stayed on the SF cluster,
even if the VM creation failed. That's also a problem, although I
believe the "storage garbage collector" would delete it?
FG
On 2014-08-22, 11:39 AM, Francois Gaudreault wrote:
Hi Mike,
I tryed the SolidFire plugin on 4
Hi Francois,
Interesting...all of my tests on XS 6.1 and 6.2 check out just fine (but
that is with CS 4.4).
I'll contact you off list and we can work this out.
Thanks,
Mike
On Fri, Aug 22, 2014 at 9:44 AM, Francois Gaudreault <
fgaudrea...@cloudops.com> wrote:
> I would also add that the ROOT
Hi Mike,
I tryed the SolidFire plugin on 4.4.1, and I don't think the behavior is
right for the ROOT volume. Tried on XenServer 6.2.
First, I am using a template with technically a 20GB space, but the
storage plugin will create the volume only according to the size of the
vhd (which is 3GB).
