Hi Senthil,
Sorry for the unclear commit message.
There are two approaches to add a new permission
1. By custom permissions
As it showed (
https://staging.review.linaro.org/#/c/321/5/lava_scheduler_app/models.py), I removed it, because in order to apply new permission, we need to run command "/srv/lava/instances/<INSTANCE>/bin/lava-server manage syncdb --all". We have modify lava-deployment-tool to add "--all" parameter. But, after my test, it will cause database migration fail when install a brain new instance
2. By data migration
This method no need to modify lava-deployment-tool. The new permission will take effect by runing "lava-server manage migrate lava_scheduler_app"
Sorry for the blocking, I'll do some test tomorrow.
Arthur