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-8687) Update prepare template api to seed/prepare a template only on a give primary storage
Date Wed, 19 Aug 2015 10:30:46 GMT

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

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

Commit fedef2e6caefd41ad10ac3d691a28271e101f171 in cloudstack's branch refs/heads/master from
[~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fedef2e ]

CLOUDSTACK-8687: Unit tests for validating the prepare template functionality.
These tests validate that the templates get scheduled for seeding. Additionally,
if a template is already seeded, we do not try and seed it again. Tests also
validate that templates are seeded to storage pools which are available.


> Update prepare template api to seed/prepare a template only on a give primary storage
> -------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8687
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8687
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Devdeep Singh
>            Assignee: Devdeep Singh
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Currently, the prepare template api will seed/prepare a given template on all the primary
storage pools in a zone. If however, a user wishes to prepare a template only a particular
storage pool, it isn't possible.
> The prepare template api should be updated to allow seedng/preparing a template only
on a given primary storage pool.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message