cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3913) private templates and volume are copied to additional secondary storage
Date Mon, 05 Aug 2013 12:15:47 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729448#comment-13729448
] 

ASF subversion and git services commented on CLOUDSTACK-3913:
-------------------------------------------------------------

Commit f28a28dc779bd6c7f6598b6944056249eb677904 in branch refs/heads/master from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f28a28d ]

CLOUDSTACK-3913
Private templates would now get copied to only one of image  storage chosen randamly as was
the case earlier. Dont throw an exception for uploading volumes when there are multiple image
stores, instead choose one of them randomly
Signed off by : nitin mehta<nitin.mehta@citrix.com>

                
> private templates and volume are copied to additional secondary storage
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3913
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3913
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.1.0, 4.2.0
>            Reporter: Ahmad Emneina
>            Assignee: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> I believe the expected behavior, after adding an additional secondary storage server
was to copy only public templates for redundancy. Whats happening is everything (all templates,
volumes..) are being copied over whole sale.

--
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

Mime
View raw message