Merge lp:~gmb/maas-test/import-images into lp:maas-test
Proposed by
Graham Binns
Status: | Merged |
---|---|
Merged at revision: | 39 |
Proposed branch: | lp:~gmb/maas-test/import-images |
Merge into: | lp:maas-test |
Diff against target: |
104 lines (+35/-3) 4 files modified
maastest/kvmfixture.py (+7/-0) maastest/maasfixture.py (+13/-3) maastest/tests/test_maasfixture.py (+14/-0) packages.txt (+1/-0) |
To merge this branch: | bzr merge lp:~gmb/maas-test/import-images |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Raphaël Badin (community) | Approve | ||
Gavin Panella (community) | Approve | ||
Review via email: mp+195550@code.launchpad.net |
Description of the change
This branch makes importing PXE files a setup step for the MAAS fixture. It updates the import_pxe_files config directly rather than using `export` because the latter didn't persist across SSH sessions.
To post a comment you must log in.
Nice. A few very minor comments.
[1]
+ # latter doesn't seem to work stick across SSH sessions. I don't
I assume "work stick" is a northern expression? :)
[2]
+ # know whether that's because # we're doing it over SSH and not
Extra #
[3]
+ expected_ pxe_config_ snippet = ( "precise" \n' "amd64/ generic i386/generic"\n'
+ '\n'
+ 'RELEASES=
+ 'ARCHES=
+ '\n')
This would be easier to read as:
"""
[4]
+ self.assertEqual( run_command. mock_calls[ 0])
+ expected_command, kvm_fixture.
I guess it's somewhat important that the config call is the first. Can assert_ any_call( )?
you note this here, so that this doesn't get changed to using
<mock>.
[5]
+ self.assertEqual( import- pxe-files' ], check_call=True), run_command. mock_calls[ -1])
+ mock.call([u'sudo', u'maas-
+ kvm_fixture.
Similar comment about ordering here.