GitHub user devdeep opened a pull request:
https://github.com/apache/cloudstack/pull/715
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. Also added unit tests to validate the functionality
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/715.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 #715
----
commit adf6b588ddb2d61bc4aa8ed4c02edaf292fa825e
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
commit fedef2e6caefd41ad10ac3d691a28271e101f171
Author: Devdeep Singh <[email protected]>
Date: 2015-08-04T11:47:10Z
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.
----
---
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.
---
