bindmounts have to be optional

Bug #1493213 reported by Michał Jastrzębski on 2015-09-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sam Yaple

Bug Description

We have several bindmounts in our project, and not all of them are required for container to run. Some of them are just for comfort of use. We should make these optional and configurable in default.yml.

Steven Dake (sdake) on 2015-09-08
Changed in kolla:
status: New → Triaged
importance: Undecided → High
milestone: none → liberty-rc1
Sam Yaple (s8m) on 2015-09-28
Changed in kolla:
assignee: nobody → Sam Yaple (s8m)
Steven Dake (sdake) on 2015-09-28
Changed in kolla:
milestone: liberty-rc1 → liberty-rc2
Steven Dake (sdake) on 2015-10-11
Changed in kolla:
milestone: liberty-rc2 → liberty-rc3
Steven Dake (sdake) on 2015-10-12
Changed in kolla:
milestone: liberty-rc3 → mitaka-1
Steven Dake (sdake) on 2016-01-06
Changed in kolla:
milestone: mitaka-1 → mitaka-2
Steven Dake (sdake) on 2016-01-22
Changed in kolla:
milestone: mitaka-2 → mitaka-3
Steven Dake (sdake) wrote :

Pretty sure this is all resolved with the named volume work. Marking as invalid.

Changed in kolla:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers