AW: Workflow for extracting a snapshot

2015-04-02 Thread S . Brüseke - proIO GmbH
Hi,

it looks like the link will not be deleted.
As far as I understand CS creates a symlink on secondary storage VM in 
/var/www/html/userdata/ to the volume itself.
Is there any kind of garbage collection which deletes the symlink? I consider 
this as a security risk, because the volume will be downloadable forever.

Mit freundlichen Grüßen / With kind regards,

Swen Brüseke

-Ursprüngliche Nachricht-
Von: Ahmad Emneina [mailto:aemne...@gmail.com] 
Gesendet: Mittwoch, 1. April 2015 17:05
An: Cloudstack users mailing list; S. Brüseke - proIO GmbH
Betreff: Re: Workflow for extracting a snapshot

That looks like the correct flow, snaps cant be downloaded. The download URL 
expires in about 30 minutes ( I could be wrong here).

On Wed, Apr 1, 2015 at 5:02 AM, S. Brüseke - proIO GmbH  s.brues...@proio.com 
wrote:

 Hi,

 can somebody tell me what the best workflow is to extract snapshots? 
 As far as I know a direct extraction of a snapshot is not possible.
 The VM needs to run all the time during the extraction!

 Here is my workflow:
 1. create snapshot of volume
 2. create new volume via snapshot
 3. download new volume
 4. delete new volume

 Another question is for how long will the download link be valid and 
 will the link deleted after a while?
 Thank you for help!

 Mit freundlichen Grüßen / With kind regards,

 Swen Brüseke



 - proIO GmbH -
 Geschäftsführer: Swen Brüseke
 Sitz der Gesellschaft: Frankfurt am Main

 USt-IdNr. DE 267 075 918
 Registergericht: Frankfurt am Main - HRB 86239

 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
 Informationen.
 Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
 erhalten haben, informieren Sie bitte sofort den Absender und 
 vernichten Sie diese Mail.
 Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail 
 sind nicht gestattet.

 This e-mail may contain confidential and/or privileged information.
 If you are not the intended recipient (or have received this e-mail in
 error) please notify
 the sender immediately and destroy this e-mail.
 Any unauthorized copying, disclosure or distribution of the material 
 in this e-mail is strictly forbidden.






- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 




AW: Workflow for extracting a snapshot

2015-04-02 Thread S . Brüseke - proIO GmbH
Hi,

it took some time, but here are some infos I do not want to keep back:

The life of a URL generated when we click on download template depends on two 
parameters in global settings in CCP. They are extract.url.cleanup.interval and 
extract.url.expiration.interval. 

Once the value in seconds is met after the creation of the URL it is expired, 
say the value of 'extract.url.expiration.interval' is 4 hours and we are 
generating a URL by clicking the download template now, then the URL is valid 
till 4 hours from now, once it is reaching the 4 hours from now it is cleaned 
up once the cleanup thread is run. Since the cleanup thread is run as per the 
'extract.url.cleanup.interval' say 2 hours, This could run immediately after 
the URL is expired or even it could go upto 2 hours from the time of URL 
expiry. 

So that minimum life of URL is = extract.url.expiration.interval 
Maximum life of URL = extract.url.expiration.interval + 
extract.url.cleanup.interval

I will confirm this info after some testing.

Mit freundlichen Grüßen / With kind regards,

Swen Brüseke

 
proIO GmbH   
Kleyerstr. 79 - 89 / Tor 13   
D-60326 Frankfurt am Main 
 
Mail: s.brues...@proio.com
Tel:  +(49) (0) 69 739049-15
Fax:  +(49) (0) 69 739049-25  
Web:  www.proio.com
 
- Support -
Mail: supp...@proio.com
24h:  +(49) (0) 1805 522 855


-Ursprüngliche Nachricht-
Von: S. Brüseke - proIO GmbH [mailto:s.brues...@proio.com] 
Gesendet: Donnerstag, 2. April 2015 10:33
An: users@cloudstack.apache.org; aemne...@gmail.com
Betreff: AW: Workflow for extracting a snapshot

Hi,

it looks like the link will not be deleted.
As far as I understand CS creates a symlink on secondary storage VM in 
/var/www/html/userdata/ to the volume itself.
Is there any kind of garbage collection which deletes the symlink? I consider 
this as a security risk, because the volume will be downloadable forever.

Mit freundlichen Grüßen / With kind regards,

Swen Brüseke

-Ursprüngliche Nachricht-
Von: Ahmad Emneina [mailto:aemne...@gmail.com]
Gesendet: Mittwoch, 1. April 2015 17:05
An: Cloudstack users mailing list; S. Brüseke - proIO GmbH
Betreff: Re: Workflow for extracting a snapshot

That looks like the correct flow, snaps cant be downloaded. The download URL 
expires in about 30 minutes ( I could be wrong here).

On Wed, Apr 1, 2015 at 5:02 AM, S. Brüseke - proIO GmbH  s.brues...@proio.com 
wrote:

 Hi,

 can somebody tell me what the best workflow is to extract snapshots? 
 As far as I know a direct extraction of a snapshot is not possible.
 The VM needs to run all the time during the extraction!

 Here is my workflow:
 1. create snapshot of volume
 2. create new volume via snapshot
 3. download new volume
 4. delete new volume

 Another question is for how long will the download link be valid and 
 will the link deleted after a while?
 Thank you for help!

 Mit freundlichen Grüßen / With kind regards,

 Swen Brüseke



 - proIO GmbH -
 Geschäftsführer: Swen Brüseke
 Sitz der Gesellschaft: Frankfurt am Main

 USt-IdNr. DE 267 075 918
 Registergericht: Frankfurt am Main - HRB 86239

 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
 Informationen.
 Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
 erhalten haben, informieren Sie bitte sofort den Absender und 
 vernichten Sie diese Mail.
 Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail 
 sind nicht gestattet.

 This e-mail may contain confidential and/or privileged information.
 If you are not the intended recipient (or have received this e-mail in
 error) please notify
 the sender immediately and destroy this e-mail.
 Any unauthorized copying, disclosure or distribution of the material 
 in this e-mail is strictly forbidden.






- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 





- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese