summaryrefslogtreecommitdiff
path: root/troveclient/v1/modules.py
Commit message (Collapse)AuthorAgeFilesLines
* Add support for module-reapply commandPeter Stachowski2017-01-051-0/+21
| | | | | | | | | | | | | | | | To facilitate the concept of live-update, a new command 'reapply' has been added to reapply a given module to all instances that it had previously been applied to. Originally, a module designated live-update would automatically be re-applied whenever it was updated. Adding a specific command however, allows operators/users more control over how the new payload would be distributed. Old 'modules' could be left if desired, or updated with the new command. Change-Id: Ic4cc9e9085cb40f1afbec05caeb04886137027a4 Partial-Bug: #1554903 Depends-On: I4caf4a57226dd711575cde766076fa25d16792e2
* Add module-instance-count commandPeter Stachowski2017-01-051-1/+3
| | | | | | | | | | | | | | | | | | | | Added a --count_only flag to the call for module instances to return a summary of the applied instances based on the MD5 of the module (this is most useful for live_update modules, to see which ones haven't been updated). Added a new module-instance-count command. This was done to facilitate getting the summary, since it returns a different result set. It basically calls the same python interface as module-instances, but adds the --count_only flag. Also added some missing tests. Change-Id: Iea661166bf3a4f3520a590da5954aedcd0036243 Partial-Bug: #1554900 Depends-On: I4caf4a57226dd711575cde766076fa25d16792e2
* Add support for module ordering on applyPeter Stachowski2016-08-251-2/+18
| | | | | | | | | | | | Client side of being able to specify 'priority' modules plus a way to rank the order in which modules are applied. Two new attributes 'priority_apply' and 'apply_order' have been added to the python API and are supported in the CLI by means of the module-create and module-update commands. Partially Implements: blueprint module-management-ordering Change-Id: I2b871c7d1eab634174396bd0905329f3a66755f6
* module-update with --all_datastores doesn't workPeter Stachowski2016-08-111-7/+11
| | | | | | | | | | | In writing the scenario tests for the fix for https://launchpad.net/bugs/1611525 (see https://review.openstack.org/#/c/353118/ ) it became evident that the --all_datastores and --all_datastore_versions options weren't functioning correctly. These options are now handled in the right way. Change-Id: I0f226f09db08f635c542b27d8d2f898050d327fa Partial-Bug: #1612430
* Client support for instance module feature2.2.0Peter Stachowski2016-03-111-9/+24
| | | | | | | | | | | | | | | | | This adds support in the python API and Trove CLI for instance module commands. These commands include: - module-apply - module-remove - module-query - module-retrieve - module-list-instance The parsing of --instance was modified to allow multiple modules to be specified. This was extended to 'nics' as well. Partially Implements: blueprint module-management Change-Id: If62f5e51d4628cc6a8b10303d5c3893b3bd5057e
* Add suport for module maintenance commandsPeter Stachowski2016-02-241-0/+132
This adds support in the python API and Trove CLI for module maintenance commands. These commands include: - module-list - module-show - module-create - module-update - module-delete Partially Implements: blueprint module-management Change-Id: I54d37025275dee4731ad49ebbd21612c4464e4c4