You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Marcus Sorensen (JIRA)" <ji...@apache.org> on 2012/11/18 07:42:12 UTC

[jira] [Created] (CLOUDSTACK-508) CLVM copies template to primary storage unnecessarily

Marcus Sorensen created CLOUDSTACK-508:
------------------------------------------

             Summary: CLVM copies template to primary storage unnecessarily
                 Key: CLOUDSTACK-508
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-508
             Project: CloudStack
          Issue Type: Bug
          Components: Template
    Affects Versions: 4.0.0
         Environment: KVM/CLVM
            Reporter: Marcus Sorensen
            Priority: Minor
             Fix For: 4.1.0


Because of the way most other primary storage types work with cloudstack
(i.e. backing stores) CLVM actually copies the template to a local logical
volume on primary storage, then uses that. This causes all of your primary
storage to be littered with a copy of every template used. Since we're not
using these, dump the template direct to the newly created logical volume.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-508) CLVM copies template to primary storage unnecessarily

Posted by "Marcus Sorensen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CLOUDSTACK-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Sorensen resolved CLOUDSTACK-508.
----------------------------------------

    Resolution: Fixed

new deployments from template copy from template on secondary storage direct to primary storage.

88180fc139ad905bb51db6aa0287bd9471194aea
                
> CLVM copies template to primary storage unnecessarily
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-508
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-508
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Template
>    Affects Versions: 4.0.0
>         Environment: KVM/CLVM
>            Reporter: Marcus Sorensen
>            Priority: Minor
>             Fix For: 4.1.0
>
>
> Because of the way most other primary storage types work with cloudstack
> (i.e. backing stores) CLVM actually copies the template to a local logical
> volume on primary storage, then uses that. This causes all of your primary
> storage to be littered with a copy of every template used. Since we're not
> using these, dump the template direct to the newly created logical volume.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-508) CLVM copies template to primary storage unnecessarily

Posted by "Marcus Sorensen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLOUDSTACK-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499631#comment-13499631 ] 

Marcus Sorensen commented on CLOUDSTACK-508:
--------------------------------------------

88180fc139ad905bb51db6aa0287bd9471194aea
                
> CLVM copies template to primary storage unnecessarily
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-508
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-508
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Template
>    Affects Versions: 4.0.0
>         Environment: KVM/CLVM
>            Reporter: Marcus Sorensen
>            Priority: Minor
>             Fix For: 4.1.0
>
>
> Because of the way most other primary storage types work with cloudstack
> (i.e. backing stores) CLVM actually copies the template to a local logical
> volume on primary storage, then uses that. This causes all of your primary
> storage to be littered with a copy of every template used. Since we're not
> using these, dump the template direct to the newly created logical volume.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CLOUDSTACK-508) CLVM copies template to primary storage unnecessarily

Posted by "Marcus Sorensen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CLOUDSTACK-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Sorensen closed CLOUDSTACK-508.
--------------------------------------

    
> CLVM copies template to primary storage unnecessarily
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-508
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-508
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Template
>    Affects Versions: 4.0.0
>         Environment: KVM/CLVM
>            Reporter: Marcus Sorensen
>            Priority: Minor
>             Fix For: 4.1.0
>
>
> Because of the way most other primary storage types work with cloudstack
> (i.e. backing stores) CLVM actually copies the template to a local logical
> volume on primary storage, then uses that. This causes all of your primary
> storage to be littered with a copy of every template used. Since we're not
> using these, dump the template direct to the newly created logical volume.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira