> To fix 1: the MAAS Node should get a predictable IP address, not a randomly assigned one.
The IP address is assigned by uvtool (which, in turn, uses kvm)… not sure it's possible to get the same IP address every time, but I'll see if it's doable.
> To fix 2: the username and password should be stable and known. It's a test tool, so a randomly generated password is unnecessary. Stick with something easy to remember like admin/insecure
You're right, I'll change that.
> To fix 3: the login data should appear BEFORE testing begins, e.g. between the step where MAAS is installed on the VM and where test_power_up_node begins.
> To fix 1: the MAAS Node should get a predictable IP address, not a randomly assigned one.
The IP address is assigned by uvtool (which, in turn, uses kvm)… not sure it's possible to get the same IP address every time, but I'll see if it's doable.
> To fix 2: the username and password should be stable and known. It's a test tool, so a randomly generated password is unnecessary. Stick with something easy to remember like admin/insecure
You're right, I'll change that.
> To fix 3: the login data should appear BEFORE testing begins, e.g. between the step where MAAS is installed on the VM and where test_power_up_node begins.
This is already the case, see http:// bazaar. launchpad. net/~maas- maintainers/ maas-test/ trunk/view/ head:/maastest/ cases.py# L158