No way to express Juju Storage Relations
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-deployer |
Fix Released
|
High
|
Tim Kuhlman | ||
Bug Description
I can't find a way to express Juju storage constraints.
Given a charm that makes use of storage relations (in metadata.yaml)
[...]
data-block:
type: block
description: storage needed for deployed service
minimum-size: 200G
multiple:
range: 1-
it can be deployed using command-line argument (e.g.)
[...] --storage data-block=ebs
to switch the storage provider from loop to ebs volumes (on aws).
In addition to this, juju provides at the command line the possibility to add storage to an unit (e.g.)
juju storage add <unit> data-block=
this must be expressible using juju-deployer as well.
This bug report is downstream from a feature request for amulet (Juju Testing Framework). Since amulet is build on juju-deployer, amulet cannot be used for charms that use Juju storage.
Related branches
- Tim Van Steenburgh (community): Approve
-
Diff: 226 lines (+66/-8)10 files modifieddeployer/action/importer.py (+1/-0)
deployer/env/base.py (+8/-1)
deployer/service.py (+4/-0)
deployer/tests/test_charm.py (+2/-2)
deployer/tests/test_data/wiki-storage.yaml (+13/-0)
deployer/tests/test_goenv.py (+2/-1)
deployer/tests/test_guiserver.py (+2/-2)
deployer/tests/test_importer.py (+19/-1)
deployer/tests/test_service.py (+4/-1)
doc/config.rst (+11/-0)
| Changed in juju-deployer: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Gui Bot (rick-harding+guibot) wrote | #1 |
| Changed in juju-deployer: | |
| assignee: | nobody → Tim Kuhlman (timkuhlman) |
| Changed in juju-deployer: | |
| status: | Confirmed → In Progress |
| Changed in juju-deployer: | |
| status: | In Progress → Fix Committed |
| Changed in juju-deployer: | |
| status: | Fix Committed → Fix Released |
The native juju deploy of bundles added support for this and it's in 2.0. We should mirror support from that as required.
https:/