| Peter Pentchev | 469dfea | 2022-06-27 12:48:18 +0300 | [diff] [blame] | 1 | options: |
| 2 | driver-source: |
| 3 | type: string |
| 4 | default: |
| 5 | description: | |
| 6 | Optional configuration to support use of additional sources such as: |
| 7 | - ppa:myteam/ppa |
| 8 | - cloud:trusty-proposed/kilo |
| 9 | - http://my.archive.com/ubuntu main |
| 10 | The last option should be used in conjunction with the key configuration |
| 11 | option. |
| 12 | driver-key: |
| 13 | type: string |
| 14 | default: |
| 15 | description: | |
| 16 | Key ID to import to the apt keyring to support use with arbitary source |
| 17 | configuration from outside of Launchpad archives or PPA's. |
| 18 | use-multipath: |
| 19 | type: boolean |
| 20 | default: True |
| 21 | description: | |
| 22 | Whether to use a multipath connection for iSCSI or FC in Cinder |
| 23 | volume service. Enabling multipath for VMs is managed by the |
| 24 | "use-multipath" option in the nova-compute charm. |
| 25 | protocol: |
| 26 | type: string |
| 27 | default: |
| 28 | description: | |
| 29 | SAN protocol to use. Choose between iscsi or fc. |
| 30 | volume-backend-name: |
| 31 | type: string |
| 32 | description: | |
| 33 | Volume backend name for the backend. The default value is the |
| 34 | application name in the Juju model, e.g. "cinder-mybackend" |
| 35 | if it's deployed as `juju deploy cinder-storpool cinder-mybackend`. |
| 36 | A common backend name can be set to multiple backends with the |
| 37 | same characters so that those can be treated as a single virtual |
| 38 | backend associated with a single volume type. |