github.com/emc-advanced-dev/unik@v0.0.0-20190717152701-a58d3e8e33b7/docs/providers/vsphere.md (about)

     1  # vSphere UniK Provider
     2  
     3  UniK supports running rumprun and OSv unikernels on vSphere.
     4  The vSphere stub of your `daemon-config.yaml` file should look something like the following:
     5  ```yaml
     6  providers:
     7    #...
     8    vsphere:
     9    - name: vsphere-1
    10      vsphere_user: user
    11      vsphere_password: password
    12      vsphere_url: url
    13      datastore: datastore1
    14      datacenter: ha-datacenter
    15      network: VM Network #optional
    16  ```
    17  
    18  Running on vSphere requires the host network to support UDP broadcast (see [instance listerner](../instance_listener.md)). Instances that launch on vSphere without access to UDP broadcast will fail to bootstrap.
    19  
    20  UniK stores a JSON representation of the state in the local `$HOME/.unik/vsphere/state.json`
    21  
    22  UniK stores files for running virtual machines in the following folders in the configured datastore:
    23  * Images (boot vmdks, copied when an instance is launched): `[datastore_name] unik/vsphere/images`
    24  * Instances (contains vSphere folder for each instance, plus the copy of the original boot image): `[datastore_name] unik/vsphere/instances`
    25  * Volumes (mountable volumes which will persist after Instances are removed): `[datastore_name] unik/vsphere/volumes`
    26  
    27  If UniK gets into a bad state (i.e. you manually remove a file or vSphere VM), you should manually edit the `$HOME/.unik/vsphere/state.json` file to remove the instance that no longer exists. UniK will eventually become self-correcting to deal with disruptions in the state.