FAQ
There are two ways to do that:
1. Using image
0. (optional) Clean up the VM (remove ssh server keys, logs, unnecessary data, etc.)
1. Create snapshot of the VM you want to clone
2. In the list of VM snapshots, click on “Manage” button next to the snapshot you want to clone
3. Choose “Create Image”
4. Once the image is created, you have to attach it into destination virtual datacenter.
Now you can use it to create one or more clones of the original VM.
2. Using the backup
1. Create a backup of the VM you want to clone
2. Create a new VM with empty disk (no image)
3. Clone the backup of the VM to the newly created VM
Example: server is stuck in deploying status and nothing is being deployed.
To cancel a running task, it is recommended to do it from command line. Download the es command here. Before issuing the command, make sure the task is really not being processed to prevent half-done operations without a cleanup.
./es get /task # find the pending task's uuid (visible also in GUI)
./es put /task/(task_id)/cancel # not all types of tasks can be canceled
./es delete /task/(task_id) -force # if the first command didn't succeed
Use the last command with caution as it doesn't do a cleanup of what was already done.
https://docs.danubecloud.org/api-reference/api/task.html#task-task-id-cancel
https://docs.danubecloud.org/api-reference/api/task.html#delete--task-(task_id)
By the way, the VM deploy task has timeout of 10 minutes. Sometimes it is worth to wait and it might resolve itself. The cause of hung tasks might be unsynchronized clock. Check the ntpd is working.
Some Danube Cloud images have firewall enabled by default. Check you firewall settings.
Please check and allow API access for your user account. Also, please make sure that you are using a valid username and password or API key.
Generated key that can be used instead of user/password authentication. It is visible in the user's profile in Danube Cloud.
This key is used to verify whether a callback response comes from your Danube Cloud installation.
The callback response will contain a random token and a verification string. You should generate your own verification string by attaching the callback key after the random token and create an MD5 hash from the string. If your MD5 hash matches the verification string you can be sure the callback came from your Danube Cloud system.
Unfortunately, this feature is not built into Danube Cloud yet. However Danube Cloud supports custom ISO images. These images need to be distributed manually onto your compute node(s) into the /iso folder.
Monitoring and more accurate VM resource graphs can be turned on by enabling a monitoring agent, which is preconfigured in our VM disk images. The agent has to be reachable by a monitoring server (mon01.local or a dedicated monitoring server).
