allow specifying docker_volume_size on cluster-create
Bug #1697648 reported by
Ricardo Rocha
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Undecided
|
Ricardo Rocha |
Bug Description
The docker_volume_size field can only be set on the cluster template. This is a value that users often want to override when using predefined and public cluster templates.
Blueprint https:/
In the meantime we should add this parameter explicitly on the cluster-create command so that users can already benefit from this.
Changed in magnum: | |
assignee: | nobody → Ricardo Rocha (rocha-porto) |
Changed in magnum: | |
status: | New → In Progress |
Changed in magnum: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/471766 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=79039bb4198 b08500f5d5738b4 64d187f494a73a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 79039bb4198b085 00f5d5738b464d1 87f494a73a
Author: Ricardo Rocha <email address hidden>
Date: Wed Jun 7 13:10:33 2017 +0000
Allow docker_volume_size on cluster create
Add docker_volume_size as an option during cluster create. If not given,
the default is taken from the cluster template.
Add docker_volume_size in the Cluster object and use that instead
of the one from ClusterTemplate.
Update both magnum and magnum cli documentation to reflect the above changes.
Partial-Bug: #1697648 8fa5319b238f4fd 98b4d499be4
Implements: blueprint flatten-attributes
Change-Id: Ic6d77e6fdf5b06