Merge lp:~roadmr/charms/precise/storage/volume-label-option into lp:charms/storage
Status: | Merged |
---|---|
Merged at revision: | 42 |
Proposed branch: | lp:~roadmr/charms/precise/storage/volume-label-option |
Merge into: | lp:charms/storage |
Diff against target: |
32 lines (+10/-1) 2 files modified
config.yaml (+7/-0) hooks/storage-provider.d/block-storage-broker/block-storage-relation-changed (+3/-1) |
To merge this branch: | bzr merge lp:~roadmr/charms/precise/storage/volume-label-option |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Charles Butler (community) | Approve | ||
Review via email: mp+269931@code.launchpad.net |
Commit message
Add volume_label option.
If given, this is the name of the volume that will be requested from block_storage_
Otherwise, a default name will be chosen by the storage charm and requested from block_storage_
Description of the change
Add volume_label option.
If given, this is the name of the volume that will be requested from block_storage_
This is necessary in environments where two services may request conflicting volume names, and so is a workaround/indirect solution for https:/
I didn't add any unit tests since I couldn't figure out how, but I'd be happy to add them if someone can help me with ideas on how to test this (I did test it manually on a live environment, of course).
+1 LGTM
Thanks for the contribution Daniel