[
https://issues.apache.org/jira/browse/CLOUDSTACK-8687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14655133#comment-14655133
]
ASF GitHub Bot commented on CLOUDSTACK-8687:
--------------------------------------------
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/635#issuecomment-127946635
@devdeep the test you added seems fine and passes (the assert messages look
like they can be better formulated to describe what went wrong)
I do not understand the relevance to these test with respect to the changed
code though.
Don't get me wrong, you wrote a fine set of additional tests and cloudstack
is not an easy book to read so I might be misreading your test. I would like it
to be clear and obvious that the added tests test what has been changed in this
PR.
> 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)
