vmbuilder should provide an option to choose which libvirt virtual network
Bug #351509 reported by
Jack Coulter
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| VMBuilder |
Fix Released
|
Undecided
|
Unassigned | ||
| vm-builder (Ubuntu) |
Fix Released
|
Wishlist
|
Mackenzie Morgan | ||
Bug Description
It is possible to have more than on virtual network with libvirt, currently vmbuilder assumes that created VMs are connected to the 'default' virtual network.
The user should be able to specify which virtual network they want the newly created VM to be connected to, if this option is not specified, it will fall back to the 'default' virtual network.
Attached is a patch which I believe fixes this bug.
Related branches
lp:~lool/vmbuilder/libvirt-network-flag
- VMBuilder: Pending requested
-
Diff: 26 lines (+4/-1)2 files modifiedVMBuilder/plugins/libvirt/__init__.py (+1/-0)
VMBuilder/plugins/libvirt/templates/libvirtxml.tmpl (+3/-1)
Revision history for this message
| Jack Coulter (jscinoz) wrote | #1 |
Revision history for this message
| Soren Hansen (soren) wrote | #2 |
| Changed in vm-builder (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| Jack Coulter (jscinoz) wrote | #3 |
| Changed in vm-builder (Ubuntu): | |
| status: | Incomplete → Confirmed |
| importance: | Undecided → Low |
| importance: | Low → Wishlist |
Revision history for this message
| Nigel Babu (nigelbabu) wrote | #4 |
| Changed in vm-builder (Ubuntu): | |
| assignee: | nobody → Mackenzie Morgan (maco.m) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in vm-builder (Ubuntu): | |
| status: | Confirmed → Fix Released |
Revision history for this message
| Loïc Minier (lool) wrote | #6 |
Revision history for this message
| Loïc Minier (lool) wrote | #7 |
| Changed in vmbuilder: | |
| status: | New → Fix Released |
To post a comment you must log in.
The --network option should be given a default value of "default" so that we don't have to put conditionals in the template. Can you make that change and perhaps put it in a bzr branch? Thanks!