LXC driven local development story
Bug #859180 reported by
Benjamin Saller
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
High
|
Benjamin Saller | ||
Bug Description
This branch includes the merge of many preceding branches related to the lxc local dev story. In its current state it can be used to do local lxc deployemnt and testing.
Add the following to your ~/.juju/
juju: environments
default: laptop
laptop
type: lxc
admin-secret: whoknows
data-dir: /tmp
I recommend adding dmsmasq to your /etc/resolv.conf with:
nameserver 192.168.122.1
However a subsequent branch makes status and ssh find the proper VM for you.
Machines are named via a pattern <username>-<env name>-<
So for me a wordpress deployment from the local repo would result in a machine at
Related branches
lp:~bcsaller/pyjuju/lxc-omega
- Gustavo Niemeyer: Approve
- Kapil Thangavelu (community): Approve
-
Diff: 643 lines (+152/-115)16 files modifiedexamples/oneiric/mysql/hooks/db-relation-joined (+1/-5)
examples/oneiric/wordpress/hooks/config-changed (+1/-1)
examples/oneiric/wordpress/hooks/db-relation-changed (+1/-1)
examples/oneiric/wordpress/hooks/install (+1/-1)
juju/agents/machine.py (+2/-1)
juju/control/add_unit.py (+1/-0)
juju/lib/lxc/data/juju-create (+1/-0)
juju/machine/tests/test_unit_deployment.py (+54/-31)
juju/machine/unit.py (+49/-23)
juju/providers/lxc/__init__.py (+13/-4)
juju/providers/lxc/agent.py (+11/-1)
juju/providers/lxc/container.py (+0/-31)
juju/providers/lxc/tests/test_container.py (+7/-7)
juju/providers/lxc/tests/test_provider.py (+7/-7)
misc/bash_completion.d/juju (+2/-2)
setup.py (+1/-0)
| Changed in juju: | |
| assignee: | nobody → Benjamin Saller (bcsaller) |
| milestone: | none → eureka |
| status: | New → In Progress |
| importance: | Undecided → High |
| description: | updated |
| Changed in juju: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
