Back to Top

Frequently Asked Questions - Configuring Virtual Machines (VMs)

  1. Stop the VM
  2. Click on the rightmost + icon (circled in red in image)
  3. Select new Compute Offering (this determines the size)
  4. Restart VM

Resizing on the fly is coming soon.

You can add an additional storage volumes to an existing virtual machine (VM) instance:
 
1. Log in to Safe Swiss Cloud VDC control panel.
 
2. In the left navigation bar, click Storage:
 
3. Create a new volume by clicking the button  "Add" (to view an existing volume, choose Volumes in Select View)
 
4. Provide the following details, and click OK:
- Name. Give the volume a unique name so you can find it later.
- Availability Zone. Where do you want the storage to reside? This should be close to the VM that will use the volume.
- Disk Offering. Select  a desired Disk Offering from the list of available offerings.
 
You can select between different Disk size and two disk types (Silver and Gold).
- Silver type is the cloud equivalent of a hard disk with up to 500 IOPS.
- Gold type is the cloud equivalent of a hard disk with up to 1'000 IOPS.

 
The new volume appears in the list of volumes with the state “Allocated.” The volume data is stored in Safe Swiss Cloud, but the volume is not yet ready for use.
 
5. To start using the volume, continue to Attaching a Volume to an existing VM. Note! This VM has to be stopped before Attaching.
If the existing VM is not stopped, go to "Instances" in the left navigation bar, choose the VM and press Stop Instance icon:
 
6. Go to "Storage" in the left navigation bar, search the volume ("NewVolume" in our case), click on this volume ("NewVolume" in our case) and then click the Attach Disk button:
 
7. Select the necessary VM from the list of existing VMs and press OK:
 
The Volume is now attached to the VM and ready for use within the VM.
 
The process has to be completed by logging into the VM and configuring the newly attached storage volume in the operating system. 

Instructions for Linux

The newly attached volume will appear as a device called /dev/vdb or /dev/vdc etc. (instead of /dev/sdb, /dev/sdc etc.). For more information about how to partition, format and mount the device, please see http://www.cyberciti.biz/faq/linux-disk-format/

Instructions for Windows

For more information on how to use the newly attached volume, please see http://technet.microsoft.com/en-us/magazine/dd637755.aspx  

In the Safe Swiss Cloud Control Panel:

  1. Click on the VM you want to create a template from.
  2. Stop the VM. Templating functionality is only active when the VM is stopped.
  3. Click "View Volumes"
  4. Click the "Root Volume"
  5. The + icon is the "Create Template" function - click on it.
  6. Give your template Name and Description.
  7. Make sure that the correct operating system is selected. If your version of the operating system is not shown, please choose the closest version.
  8. If you have implemented Reset Password feature, please make sure that you check the checkbox "Password Enabled". For instruction on how to implement the Reset Password feature in your template, please check official CloudStack guide: http://cloudstack-administration.readthedocs.org/en/latest/templates.htm...
  9. Please make sure the rest of the checkbox fields are not checked.
  10. There is a notification when the template creation completes. You can do other things in the control panel in the meantime.
  11. After completion, the template will be available in the "Add Instance" wizard and the Templates menu.
  1. Ssh into your virtual machine (or get some other shell command line access to the virtual machine)
  2. Use fdisk to see which disks are available
  3. The Data Disk will show up as the second disk e.g. /dev/sdb or /dev/vdb depending on the Linux variant or as the D disk in Windows.

 

No.

We do not restrict the number of virtual machines (VM) you can start in each Virtual Data Center.

There are also no changes associated with a VM - you pay for the total amount of CPU, RAM and Storage you allocate.

Any operating system of your choice such as Linux and Windows, but also all kinds of BSD. Most operating systems that run on Intel and compatible processors can be run on Safe Swiss Cloud.

You can always create your own templates from ISO files.

You will find the default list of available templates here.

The default hypervisor is KVM.

For special requirements (minimum 10 physical servers), we can enable cloud infrastructure based on the following hypervisors:

  1. Xen
  2. VMWare ESXi with vSphere

We provide the following templates "out of the box". You can always create your own with your own ISO.

Linux:

  1. CentOS-6-x86_64-Minimal
  2. CentOS-6-x86_64-LAMP-Virtualmin
  3. CentOS-7-x86_64-Minimal
  4. CentOS-7-x86_64-LAMP-Virtualmin
  5. Debian-7-x86_64-Minimal
  6. Debian-7-x86_64-LAMP-Virtualmin
  7. Debian-8-x86_64-Minimal
  8. Debian-8-x86_64-LAMP-Virtualmin
  9. Ubuntu-14.04-x86_64-Minimal
  10. Ubuntu-14.04-x86_64-LAMP-Virtualmin
  11. CoreOS

Windows

  1. Windows-Server-2008-R2-Standard-x64
  2. Windows-Server-2012-R2-Standard-x64
  3. Windows-Server-2012-R2-Core-Standard-x64

Please make sure to get the proper licenses for commercial operating systems like Windows. These are not included by default.

Yes - there are various ways to do this.

You need to export your VM to a file and convert it to qcow2 format. Safe Swiss Cloud uses KVM virtualization using the qcow2 format, so VMs in this format can easily be imported.

We have migrated VMs from most commonly used hypervisors including VMware, Hyper-V and KVM. If you need assistance with your migration we will be happy to help you.

Yes.

We use KVM for our virtualisation, so we will be able to take your KVM VMs and run them practically unchanged.  We might suggest some tuning to improve I/O and network throughput at Safe Swiss Cloud.

We will use Ubuntu here as an example.

  • 1. Install cloudmonkey:

apt-get install python-pip

pip install --upgrade pip

pip install cloudmonkey

  • 2. Then create config file for cloudmonkey:

mkdir .cloudmonkey

cat <<'EOF' > .cloudmonkey/config

[core]

profile = ssc

asyncblock = true

paramcompletion = true

history_file = /root/.cloudmonkey/history

log_file = /root/.cloudmonkey/log

cache_file = /root/.cloudmonkey/cache

 

[ui]

color = true

prompt = >

display = default

 

[swiss1]

url = https://swiss1.safeswisscloud.ch:443/client/api

username = [YOUR USER NAME]

apikey = [YOUR API KEY]

secretkey = [YOUR SECRET KEY]

timeout = 3600

expires = 600

domain = /[YOUR DOMAIN]

signatureversion = 3

verifysslcert = true

password = [YOUR PASSWORD]

 

[swiss2]

url = https://swiss2.safeswisscloud.ch:443/client/api

username = [YOUR USER NAME]

apikey = [YOUR API KEY]

secretkey = [YOUR SECRET KEY]

timeout = 3600

expires = 600

domain = /[YOUR DOMAIN]

signatureversion = 3

verifysslcert = true

password = [YOUR PASSWORD]

EOF

  • 3. Then run cloudmonkey and type in the following commands:

3.1 First for swiss1

# cloudmonkey -p swiss1

Apache CloudStack  cloudmonkey 5.3.2. Type help or ? to list commands.

 

Using management server profile: ssc 

 

(ssc) > sync

274 APIs discovered and cached

(ssc) > 

3.2 Now add the ssh key

(ssc) > register sshkeypair name=my-ssh publickey='ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAuvwUV7YLiOpjJoNMeD3dNlcLVejDrYOK1yH9GGnpgL7QeuQ/8vltUSzS1D9IaDEpdRQS8MxkDQWH4zToh0HeqIGI5Y WrEQfSTl5ZhySWWRAid4/FN56KgsSK2A5KlHbQkXMpyKQooI96aCjVzDMB8pqhyhYyyDhnCYVuV9b0/qzuAX8E9S8dMwvrBrUaStWBNaDBpPvDibEAlQ465 GNVAHvsDRq4w9TYCHizHuvl1Idr67POm7eJcJYvbUel71VkEH/b7LaKRU1iQyWOmRb65ROjI3qLVu2DzbSRnKujIUye3ABoo/gjNH0zc/sYnMfEwFGESKsfJFbt 5sOV7tdiQ=='

 

3.3 Next deploy a VM containing the ssh key

(ssc) > deploy virtualmachine serviceofferingid=a0236e81-1152-4191-9f14-3fe322dc40c4 templateid=09e9b37e-9435-49c8-85b8-ee915c1bc155 keypair=my-ssh networkids=[YOUR_NETWORK_ID] name=my-coreos displayname=my-coreos zoneid=1d954519-907f-45c0-bd56-36b38ff6bbe4 

 

3.4 Use the same procedure for swiss2, but with different ids for zone, network, template and serviceoffering:

# cloudmonkey -p swiss2

Apache CloudStack  cloudmonkey 5.3.2. Type help or ? to list commands.

 

Using management server profile: ssc 

 

(ssc) > sync 

274 APIs discovered and cached

(ssc) > 

 

3.5 Add the ssh key

(ssc) > register sshkeypair name=my-ssh publickey='ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAuvwUV7YLiOpjJoNMeD3dNlcLVejDrYOK1yH9GGnpgL7QeuQ/8vltUSzS1D9IaDEpdRQS8MxkDQWH4zToh0HeqIGI5Y WrEQfSTl5ZhySWWRAid4/FN56KgsSK2A5KlHbQkXMpyKQooI96aCjVzDMB8pqhyhYyyDhnCYVuV9b0/qzuAX8E9S8dMwvrBrUaStWBNaDBpPvDibEAlQ465 GNVAHvsDRq4w9TYCHiz/Huvl1Idr67POm7eJcJYvbUel71VkEH/b7LaKRU1iQyWOmRb65ROjI3qLVu2DzbSRnKujIUye3ABoo/gjNH0zc/sYnMfEwFGESKsfJF bt5sOV7tdiQ=='

 

3.6 Now deploy a VM containing the ssh key

(ssc) > deploy virtualmachine serviceofferingid=1e0a3524-abcf-479d-8a8c-146d74c8e81b templateid=f0f96794-7904-4dab-828d-94bdd4401f5c keypair=my-ssh networkids=[YOUR_NETWORK_ID] name=my-coreos displayname=my-coreos zoneid=9e165259-d754-4704-9813-f235c4f613f7

 

 

NOTE: Replace the ssh key and network id with your own. You can also change the serviceoffering ID to suit your needs.

You are able to list your own networks with the following commands:

 

#For Swiss1

cloudmonkey -p swiss1 list networks filter=name,id

#For Swiss2

cloudmonkey -p swiss2 list networks filter=name,id

 

Similar for serviceofferings:

 

cloudmonkey -p swiss1 list serviceofferings filter=name,id

 

cloudmonkey -p swiss2 list serviceofferings filter=name,id

 

  • 4. Then it is possible to do port forward port 22 from a public IP in the VR to the newly created VM and to ssh with the keys without needing to type the password

ssh core@[YOUR_VMs_PUBLIC_IP]

 

Here are the CloudMonkey commands to Create/Deploy a virtual machine in a stopped state (and with IP Address).
 
To deploy a VM, the minimum information you need are the following:
  • ZoneID
  • ServiceOfferingID
  • TemplateID
To get the ZoneID type the following command:
List Zones filter=name,id
This will return the following:
name id
DC-ZURICH-GLATTBRUGG 3d1dcf11-d482-4f28-a2dd-6afcb51545d2
 
 
Next use the following command to get the ServiceOfferingID:
List ServiceOfferings filter=name,id
This will return the following:
name id
FREE - Clustered (1 vCPU - 512M RAM)   bbd12548-9a33-46df-a9f9-97b190c4d2a2
Micro - Clustered HA (1 vCPU - 1 GB) 632e628e-4ee9-4808-a27b-53a8e580187f
Mini - Clustered HA (2 vCPU, 2GB) efd10c0c-431e-4819-abb4-c13c5a28e8fd
Small - Clustered HA (2 vCPU - 4GB) 013c5e22-2f83-48e5-afec-31e1307f4b15
Medium-S Clustered HA (4 vCPU - 4 GB) 90ffeca2-1116-4bbe-bce4-61351a60fcd6
Medium - Clustered HA (4 vCPU - 8GB) f202ca2c-790a-4047-85cb-d831e4e94e7e
Medium-L - Clustered HA (4 vCPU - 16GB) 992ec625-9180-44a2-8bf1-e08bb87025d5
Large-S - Clustered HA (8 vCPU - 8 GB) 9a953625-8081-4e56-aa14-5507ae0b0bcf
Large-6-16 - Clustered HA (6 vCPU - 16 GB) 482a5570-2f7e-4fec-9aa8-ff8ef10bd311
Large - Clustered HA (8 vCPU - 16 GB) 6dadbc20-2020-4980-af15-5ce3c247e21c
XLarge - Clustered HA (8 vCPU - 32 GB)  b738293e-98bf-49c8-837b-09dc0b192ec7
 
Next you need the TemplateID. Since you have created your own template from a transfer, you use the following command:
List Templates TemplateFilter=self filter=name,id
This will return (using my own as an example):
id name
0c8f4b3b-cc0a-488e-b3c5-214b9b63ec0a tv-Template-MS-Server-2012R2-RDP
 
If you wish to use the SafeSwissCloud provided templates, use TemplateFilter=featured.
 
Now that you have this information you are ready to deploy your VM with the following command:
 
Deploy VirtualMachine ZoneID=<zoneid> ServiceOfferingID=<serviceofferingid> TemplateID=<templateid> StartVM=false IPAddress=192.168.30.10 Name=My-VirtualMachine DisplayName=“My Virtual Machine”
 
(Replace <zoneid> etc with valid IDs) (Command line is not case sensitive)
 
StartVM=false allows you to create the VM in a “stopped” state. Default value is “true”.
IPAddress=<IP Address> allows you to manually set the VM IP address, must be within the network CIDR range and not already allocated. An error will be returned if you try to set a wrong or pre-allocated IP.
Name and DisplayName should be set otherwise the VM name will be the GUID. Once created you can only change the DisplayName. To change the VM Name you will have to destroy and recreate the VM.

If you are logged in SafeSwissCloud VDC, perform the following steps to add an affinity group:

1. On the left panel, click Affinity Groups.

2. The Affinity Groups page displays. You need to press '+Add new affinity group'

3. The Add new affinity group dialog box displays. Define a name using which you can identify the affinity group; enter a description for the affinity group (this description will help you to identify the affinity group when you need to select one for creating an instance) and press "OK".

New affinity group will be created and added.