OTA & KVS support

[bwsw]

When KVM & OTA services are present, then this plugin may be used. It's activated in the config from the UI perspective. The plugin implements secure API-VM, VM-API interfaces.

VM creation alteration

Before implementing the plugin UI must implement an altered VM deployment mechanism, which first creates VM stopped and next starts VM. This is important from the perspective of KVS implementation because KVS uses VM UUID and it's impossible to build user data when an VM is started upon creation. So the process must be implemented as follows:

1. create VM stopped
2. get VM KVS and private key for it.
3. create OTA token for the KVS credentials.
4. set userdata with OTA credentials.
5. start VM

UI additional interfaces

A new tab must be implemented for VM, which displays KVS when the plugin is enabled. The tab is very similar to the tags tab but allows to refresh values and allows to set new K/V when users want to.

When VM is created a new tab must be added where the user may add userdata in the form of K/V. When the plugin is disable, the user enters userdata in the form of raw text which must be base64-d before VM creation.