2f3703bb34
The module feature of Trove has been designed to be idempotent, in that a module should be able to be applied more than once with no ill side effects. Unfortunately a new instance_modules record is written for each apply, potentially leaving records behind on module-remove that make it impossible to delete the module. This has been fixed and code put in place on module-apply and module-delete to remove any extraneous records. Depends-On: Ia4fc545a10c7c16532aefd73818dd7d90c9c271b Change-Id: I09b301c1fb8311f9c5bee07d0af398071da3dd24 Closes-Bug: #1640010 |
||
---|---|---|
.. | ||
backup | ||
cluster | ||
cmd | ||
common | ||
conductor | ||
configuration | ||
datastore | ||
db | ||
dns | ||
extensions | ||
flavor | ||
guestagent | ||
instance | ||
limits | ||
locale/fr/LC_MESSAGES | ||
module | ||
network | ||
quota | ||
taskmanager | ||
templates | ||
tests | ||
README | ||
__init__.py | ||
rpc.py | ||
version.py | ||
versions.py |
README
This is the trove code itself