add bind-home options to local provider

Bug #1220816 reported by Mark Mims
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Low
Unassigned

Bug Description

lxc containers take a '--bind-home' and I think a more general '--bind' option.

Let's expose this as an option when deploying containers using local provider. The use case would be development/testing applications. Something along the lines of `juju deploy --bind-home --config myapp.yaml django myapp`... edit the app in your home directory, then touch the wsgi file and the containers redeploy.

There's a bit of a problem in the ambiguity of "home"... my laptop uses /home/mmm but the containers will use /home/ubuntu... but that can be solved.

I'm assuming it'd be better placed in `juju deploy --bind-home` instead of `juju bootstrap --bind-home` or environments.yaml as a 'bind-home' key... but whatever works.

Revision history for this message
Mark Mims (mark-mims) wrote :

perhaps a constraint on the local provider might be a better, provider-specific location for this? dunno

description: updated
Revision history for this message
Mark Mims (mark-mims) wrote :

`juju deploy --constraints "bind_map=/home/mmm:/home/ubuntu" django`?

Revision history for this message
Jorge Castro (jorge) wrote :

Thumper we talked about this a bit at the sprint, and we'd like to do this as part of our local development story as it's a powerful workflow.

Changed in juju-core:
status: New → Confirmed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Confirmed → Triaged
tags: added: feature lxc
Changed in juju-core:
importance: Undecided → High
Curtis Hovey (sinzui)
tags: added: local-provider
removed: lxc
Curtis Hovey (sinzui)
Changed in juju-core:
importance: High → Low
Changed in juju-core:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.