Merge lp:~matsubara/auto-package-testing/custom-meta-data-prepare-testbed into lp:auto-package-testing
Proposed by
Diogo Matsubara
Status: | Merged |
---|---|
Merged at revision: | 327 |
Proposed branch: | lp:~matsubara/auto-package-testing/custom-meta-data-prepare-testbed |
Merge into: | lp:auto-package-testing |
Diff against target: |
36 lines (+10/-2) 1 file modified
bin/prepare-testbed (+10/-2) |
To merge this branch: | bzr merge lp:~matsubara/auto-package-testing/custom-meta-data-prepare-testbed |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Martin Pitt | Approve | ||
Review via email: mp+213922@code.launchpad.net |
Commit message
add option to allow custom metadata file to prepare-testbed script
Description of the change
This allows one to prepare a testebed using a custom meta-data file rather than using the hard coded one in the prepare-testbed. My use case for this is to prepare a testbed with multiple network-interfaces (e.g. https:/
To post a comment you must log in.
Just two little nitpicks:
+ METADATAFILE=$2
Should be quoted.
+ cat $METADATAFILE > $METADATA
Should be quoted and use cp.
Otherwise this LGTM.
Out of interest, what do you need this for? I'm asking because this whole lp:auto-package-testing thing will go away in the next cycle in favor of running adt-run directly (with adt-virt- {lxc,qemu} ), so we need to fit your use case there, too.
Thanks!