Merge lp:~linaro-validation/lava-dashboard-tool/nonlegacy-rpc-and-auth-support into lp:lava-dashboard-tool

[Zygmunt Krynicki]

Add support for authenticated and non-legacy APIs, see the commit message for more details.

[Michael Hudson-Doyle (mwhudson)]

This looks basically fine. I'm not sure an extra roundtrip per invocation is really a good idea -- we notice things like that down on the bottom of the world. Would it not be possible to assume the new api and if that fails with something 404ish, try the old url? Or just upgrade to using the new API -- how many legacy installations of the dashboard are there in reality?

But no opposition to landing this as is.

[Zygmunt Krynicki (zyga)]

There are two causes for latency:

1) Calling server.dashboard.version()
2) Calling server.system.listMethods()

We could probably ignore both for some time and stop supporting launch-control but IMHO it's too early for that yet. We could try to work around that with more complex code (one multicall would tell us both the version and the methods) (at one cost of latency) but I don't think we need to over-complicate that just yet.

[lp:~linaro-validation/lava-dashboard-tool/nonlegacy-rpc-and-auth-support]

156. By Zygmunt Krynicki on 2011-07-21

Move the call to use_non_legacy_api earlier

157. By Zygmunt Krynicki on 2011-07-21

Bump version to 0.6