Merge lp://staging/~qzhang/lava-scheduler/add-template4device into lp://staging/lava-scheduler

I'm afraid I don't understand how you are approaching this. There are two basic approaches, define a generic device template that provides blocks for the specific device pages to fill or providing a "device details" template that other templates can include. I did the former in https://code.launchpad.net/~mwhudson/lava-scheduler/cleanup-device-template-1/+merge/95496 and the latter in https://code.launchpad.net/~mwhudson/lava-scheduler/cleanup-device-template-2/+merge/95497 -- I honestly didn't know which would turn out to be nicer, so I did both. I think the first is a bit nicer, but the second is a bit simpler. Do they make sense to you? Which do you prefer?

Thanks, the good examples, I prefer the first. The key point I realize now is I can't include "{% block content %}" and call "{{ block.super }}" to retrieve parent content block, I only need to extends the block definition in {% block content %}

New version, merged new django_table2 modification from upstream

Looks better, I think you can move the 'columns' stuff into the _device_base.html template though?

'columns' merged.

I'll leave this review to everyone else. I think it would be nice to see how we can then simplify it with the stuff that's landed (landing?) to lava-server for very very very simple and much better (faster/cleaner/scalable) table rendering.

Looks good to me.