Allow specific actions per hypervisor/storage/network configuration

[OpenNebulaSupport]

Some features can be supported by some hypervisors but not for others. For example, snapshots for powered off VMs can be taken on vCenter but not for KVM VMs. They should be allowed in some cases.

Progress Status

• [ ] Branch created
• [ ] Code committed to development branch
• [ ] Testing - QA
• [ ] Documentation
• [ ] Release notes - resolved issues, compatibility, known issues
• [ ] Code committed to upstream release/hotfix branches
• [ ] Documentation committed to upstream release/hotfix branches

[paczerny]

Some abilities of hypervisor can be read from oned.conf. I suppose Sunstone gets the info via one.system.config call.

VM_MAD = [
    NAME              = "vcenter",
    ...
    KEEP_SNAPSHOTS    = "yes",
    DS_LIVE_MIGRATION = "yes",
    COLD_NIC_ATTACH   = "yes",
    LIVE_RESIZE       = "yes",
]

User permissions

It would be nice to enable/disable Sunstone actions based on user permissions, that would require new functionality from oned, the idea is:

• New API call - parameters might be object type, object id
• The oned searches the RequestManager->NebulaRegistry to get possible Request executors
• On each request call Request->basic_authorization() to check permissions
• Return list of allowed actions

Note: VM action authorization operation may be modified in oned.conf. And one.vm.action needs special handling for sub-actions