ot;Is it too late in the game to
>>>>>>>>> interrogate the template to discover its virtual size if we're just
>>>>>>>>> about
>>>>>>>>> to copy the template to primary storage?"
>>>>>>>
t;>>>>>> about
>>>>>>>> to copy the template to primary storage?"
>>>>>>>>
>>>>>>>> If it's not, this might be the place to run the logic to figure out
>>>>>&
>>>
>>>>>>> Really, there are three big possibilities:
>>>>>>>
>>>>>>> 1) Just ask the end user to provide the virtual size (not commenting
>>>>>>> here on what happens for already-uploaded templates)
>>>
gt;>>> here on what happens for already-uploaded templates)
>>>>>>
>>>>>> or
>>>>>>
>>>>>> 2) Figure out the virtual size when the template is copied from
>>>>>> object storage to secondary storage an
e the DB with this info (not sure
>>>>> what happens if the template has already been copied to
>>>>> (secondary-storage)
>>>>> NFS because it was used before)
>>>>>
>>>>> or
>>>>>
>>>>> 3)
>>>>
>>>> or
>>>>
>>>> 3) Figure out the virtual size when the template is about to be copied
>>>> from secondary storage to primary storage
>>>>
>>>> On Mon, Sep 8, 2014 at 11:35 PM, Sanjeev Neelarapu &l
t;>> On Mon, Sep 8, 2014 at 11:35 PM, Sanjeev Neelarapu <
>>> sanjeev.neelar...@citrix.com> wrote:
>>>
>>>> Mike,
>>>>
>>>> You are right. Template gets copied to (secondary-storage) NFS before
>>>> being copied to primar
elar...@citrix.com> wrote:
>>
>>> Mike,
>>>
>>> You are right. Template gets copied to (secondary-storage) NFS before
>>> being copied to primary storage
>>>
>>> -Sanjeev
>>>
>>> -Original Message-
>>> From: Mike Tu
sage-
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: Tuesday, September 09, 2014 10:55 AM
>> To: dev@cloudstack.apache.org
>> Cc: Punith S; Francois Gaudreault
>> Subject: Re: S3/Swift Problem around Virtual Size
>>
>> Hi W
gt; Sent: Tuesday, September 09, 2014 10:55 AM
> To: dev@cloudstack.apache.org
> Cc: Punith S; Francois Gaudreault
> Subject: Re: S3/Swift Problem around Virtual Size
>
> Hi Will,
>
> Thanks for the input!
>
> I like the idea of storing the virtual size as metadata in S3 or Swift
> although
; Francois Gaudreault
Subject: Re: S3/Swift Problem around Virtual Size
Hi Will,
Thanks for the input!
I like the idea of storing the virtual size as metadata in S3 or Swift although
this could require that the end user provide this value when uploading the
template.
However, if we have the ability
Hi Will,
Thanks for the input!
I like the idea of storing the virtual size as metadata in S3 or Swift
although this could require that the end user provide this value when
uploading the template.
However, if we have the ability to determine the virtual size of the
template after it gets download
My two cents on the topic.
Ideally we would save the size in the object store metadata and retrieve it
from the metadata if it is set. If it is not set in the object store
metadata, then when it is fetched, we have to put it on NFS and determine
the size (then ideally save the metadata back to th
Hi Punith,
Thanks for putting in time on this!
So, option 1 occurs after we download the template to S3 or Swift. We then
have to copy it to NFS so that we can determine the virtual size?
Relatively slow, but it would work.
If we went this route, would we then delete that template from the NFS
s
hi mike,
i have figured out the issue, in NFS secondary storage the virtual size is
been calculated by the VHD Processor by accessing the vhd template.
but in case of S3, cloudstack is not able to access the template but it
only gets to know the physical size of the template!
in order to solve t
Hi Punith,
Have you been able to make any progress with regards to this Swift/S3 issue?
Thanks!
Mike
On Wed, Aug 27, 2014 at 7:43 AM, Punith S wrote:
> hi
>
> think i had a timeout problem!
> on the second try the template has been downloaded to the S3 bucket and
> the management server shows
That's a good question, Marcus.
I've CCed Edison to bring this to his attention.
Edison - What do you think?
Thanks
On Tue, Aug 26, 2014 at 9:48 PM, Marcus wrote:
> Per Edisons comments about not knowing the image size, can't we just set
> some headers and store metadata with the template in
hi
think i had a timeout problem!
on the second try the template has been downloaded to the S3 bucket and the
management server shows the status as download complete with template size
as 1.6G instead of its virtual size 20G.
and i see the template's status as Download Complete but it seems it is
Per Edisons comments about not knowing the image size, can't we just set
some headers and store metadata with the template in S3 to save the virtual
size when the template is registered? I'm assuming here that the SSVM does
the work of pulling the template in and uploading to S3. Or it could be
sto
Looks like your SSVM cannot reach Internet properly?
FG
On 2014-08-26, 11:14 AM, Punith S wrote:
hi francois,
since i'm not having a swift setup, i'm using the s3 bucket.
and as you recommended i got the SSVM up with seeded nfs storage,
post that i removed the nfs secondary storage and added
hi francois,
since i'm not having a swift setup, i'm using the s3 bucket.
and as you recommended i got the SSVM up with seeded nfs storage,
post that i removed the nfs secondary storage and added the S3 with staging
nfs store as the new sec storage, since you cannot have any nfs secondary
storag
Punith,
We ran into the same problem. The only way we found to get around that,
is to start from a standard NFS, get the SSVMs up, and then move to Swift.
If you find a way to avoid such manipulation, let me know!
FG
On 2014-08-26, 9:58 AM, Punith S wrote:
hi,
i'm trying to deploy a zo
hi,
i'm trying to deploy a zone with S3 alongside an empty staging nfs store as
the secondary storage,
does anyone have idea about how to seed the s3 secondary storage with ssvm
templates to bring up the secondary storage VM ?
like in nfs we seed nfs sec store by running this script
/usr/share/
I mean we are populating the template just like we would do with normal NFS
using the UI.
ACS takes care of pushing to swift.
FG
On Aug 26, 2014 6:02 AM, "Francois Gaudreault"
wrote:
> Punith,
>
> We are using Swift. We have a tmpauth proxy.
>
> FG
> On Aug 26, 2014 2:48 AM, "Punith S" wrote:
Punith,
We are using Swift. We have a tmpauth proxy.
FG
On Aug 26, 2014 2:48 AM, "Punith S" wrote:
> sure mike,
>
> since i don't have a S3 account, i'm getting one today.
>
> francois, can you brief me how you seeded your templates into S3.
>
> thanks!
>
>
> On Mon, Aug 25, 2014 at 11:16 PM, M
sure mike,
since i don't have a S3 account, i'm getting one today.
francois, can you brief me how you seeded your templates into S3.
thanks!
On Mon, Aug 25, 2014 at 11:16 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Yes, I expect we'll see the same issue with S3, as well.
>
> P
Yes, I expect we'll see the same issue with S3, as well.
Punith - Is this something you might have time to investigate? Perhaps
Edison can point us in the right direction here.
On Mon, Aug 25, 2014 at 5:17 AM, Francois Gaudreault <
fgaudrea...@cloudops.com> wrote:
> Punith,
>
> I highly anticip
Punith,
I highly anticipate the same issue with S3... it shares a lot of code with
swift.
My focus would be swift, but we should fix for both :)
FG
On Aug 25, 2014 6:33 AM, "Punith S" wrote:
> thanks for opening this thread mike,
>
> since i only use nfs as my secondary storage provider, i did
thanks for opening this thread mike,
since i only use nfs as my secondary storage provider, i didn't see this
issue till date.
is this issue occurring even using a S3 secondary storage with staging nfs
store ?
if so like edison pointed we need to fetch the virtual size from the nfs
store instead
Hey Edison,
Do you know how difficult/easy of a fix this is, who might be available to
put this fix in, and for what release (hopefully 4.4.1) this fix could find
its way in?
Thanks!
Mike
On Fri, Aug 22, 2014 at 3:37 PM, Francois Gaudreault <
fgaudrea...@cloudops.com> wrote:
> Min,
>
> Ok, but
Min,
Ok, but this is not the behavior I see. Even without requesting a VM
create, the template is pushed to the staging NFS at least once. Is it
downloaded there or pushed after download, that I am not sure. I was
assuming the swift upload bash script was executed after the template is on
the stag
No. For S3/Swift, register template will directly upload templates to S3
without going through staging NFS. It will only be copied to staging NFS
when we first use that template to provision a VM.
Thanks
-min
On 8/22/14 2:25 PM, "Francois Gaudreault" wrote:
>Edison,
>
>Isnt the templates downlo
Edison,
Isnt the templates downloaded to the Staging NFS first?
FG
On Aug 22, 2014 5:20 PM, "Edison Su" wrote:
> I know the reason why the size of template doesn’t have correct virtual
> size if it’s registered in S3/Swift:
> In case of s3/swift, the template is directly stored into s3/swift th
I know the reason why the size of template doesn’t have correct virtual size if
it’s registered in S3/Swift:
In case of s3/swift, the template is directly stored into s3/swift through
swift/s3 api, there is no place for cloudstack to look into template, to find
out the virtual size during templa
I forgot to say that this was noticed with 4.4 (but is probably an earlier
issue).
On Fri, Aug 22, 2014 at 2:38 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Hi,
>
> This was brought up in a different e-mail thread, but I wanted to make it
> more clear that it's related to CloudSta
35 matches
Mail list logo
