provide --storage flag on add-unit
Bug #1742615 reported by
Stuart Bishop
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
I can add a new unit and reuse existing storage with 'juju add-unit --attach-storage foo/1'. However, there seems to be no way to add a new unit with fresh, attached storage. There is no 'juju add-unit --storage=1G' or similar, or easy way to create a clean, unattached storage.
Use case is adding a second unit to a production-sized PostgreSQL deployment:
juju deploy cs:postgresql --storage=250G
If I need to add a second unit with 'juju add-unit postgresql', there will be no attached storage and setup will fail; an attempt will be made to replicate the database, and it will fail due to lack of space.
tags: | added: canonical-is |
tags: | added: docteam |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
summary: |
- Unable to add a unit with fresh, attached storage + provide --storage flag on add-unit |
To post a comment you must log in.
> juju deploy cs:postgresql --storage=250G
>
> If I need to add a second unit with 'juju add-unit postgresql', there will be no attached storage > and setup will fail; an attempt will be made to replicate the database, and it will fail due to lack of space.
If you deploy with --storage, then every unit added with add-unit will get the same storage. I've just tested this with 2.3 and verified that it works.
It might still be useful to have a --storage flag on add-unit, though, to override whatever was specified to "juju deploy".