GitHub user devdeep opened a pull request:
https://github.com/apache/cloudstack/pull/635
CLOUDSTACK-8687: Prepare template only on a given storage pool
Update prepare template api to seed/prepare a template only on a given
primary storage. 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.
Updated the api to take storage pool id as an optional parameter. If the pool
id is provided then the template is prepared only on the given primary storage
pool.
Following scenarios were tested. 1) Prepared a template with out the
storage pool id. The template was seeded on all the available pools in the
given zone. 2) Prepared a template with storage pool id as a parameter in the
api. The template was seeded only on the given primary storage pool.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/devdeep/cloudstack-1 CLOUDSTACK-8687
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/635.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #635
----
commit 746dddd6054a3a1453c8347ce0640e8941b8a6a7
Author: Devdeep Singh <[email protected]>
Date: 2015-07-28T06:35:35Z
CLOUDSTACK-8687: Update prepare template api to seed/prepare a template
only on a given primary storage. 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. Updated the api to take
storage pool id as an optional parameter. If the pool id is provided
then the template is prepared only on the given primary storage pool
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
