Set Up a vCPU Server

a user with full root or administrator access rights can create a vcpu server a vcpu server, once provisioned, retains all its settings, such as resources, drive allocation, password, etc , even after a restart at the operating system level a vcpu server is deleted from your virtual data center (vdc) https //docs ionos com/cloud/support/general information/glossary of terms#virtual data center vdc only when you delete it from the dcd for more information, see vcpu servers https //docs ionos com/cloud/compute services/compute engine/vcpu server create a vcpu server vcpu servers offer flexible configurations for ram and cpus you can create a vcpu server via the dcd or the api prerequisite make sure you have the appropriate privileges only contract administrators, owners, and users with the create data center privilege can set up a vdc https //docs ionos com/cloud/support/general information/glossary of terms#vdc other user types have read only access and cannot provision changes to create a new vcpu server via the dcd, follow these steps in the dcd , go to menu > virtual data centers important the procedure listed here applies only to the canvas mode if you do not have a data center, create a data center using either of these two modes canvas or xpress after creating a data center using the canvas https //docs ionos com/cloud/set up ionos cloud/get started/create data center/use canvas mode, continue with the following steps to add and provision a vcpu server within it for instructions on creating and provisioning a server using the xpress mode, see use the xpress mode https //docs ionos com/cloud/set up ionos cloud/get started/create data center/use xpress select the data center to configure a vcpu server within it drag the vcpu server element from the palette into the workspace the created vcpu server is automatically highlighted in turquoise the inspector pane allows you to configure the properties of this individual vcpu instance in the inspector pane on the right, configure your vcpu server in the settings tab name choose a name unique to this vdc https //docs ionos com/cloud/support/general information/glossary of terms#vdc availability zone https //docs ionos com/cloud/support/general information/glossary of terms#availability zone the zone where you wish to physically host the vcpu choosing a auto selects a zone automatically this setting can be changed after provisioning preset select an appropriate configuration from the drop down list the values s , m , l , xl , and xxl contain predefined vcpu to ram ratios you can always override the values to suit your needs and the preset automatically changes to custom when you edit the predefined ratio indicating that you are no longer using the predefined ratio vcpus specify the number of vcpus you may change these after provisioning the capabilities are limited to your customer contract limits for more information about the contract resource limits in dcd, see resource overview https //docs ionos com/cloud/set up ionos cloud/management/usage/resource overview ram specify ram size; you may choose any size between 0 25 gb to 240 gb in steps of 0 25 gb this setting can be increased after provisioning network security groups select one or more network security groups from the drop down list to associate them with the vcpu server you can choose from any of the default or custom groups nic multi queue select or clear nic multi queue https //docs ionos com/cloud/network services/vdc networking/nic multi queue to turn the feature on or off for your vcpu server it allows the network interface card to utilize multiple cpu cores for processing network traffic in parallel, significantly improving network throughput and reducing latency this feature is particularly beneficial for high performance applications and servers handling large volumes of network i/o operations ssh keys select the premade ssh key https //docs ionos com/cloud/support/general information/glossary of terms#secure shell ssh keys you must first have a key stored in the ssh key manager for more information about how to create and add ssh keys, see openssh instructions https //docs ionos com/cloud/security/ssh key manager/connect via ssh/connect via ssh terminal ad hoc key copy and paste the public part of your ssh key into this field to create a new vcpu server via the api, specify the following properties specify a name for your vcpu server set type vcpu set the availabilityzone to auto specify cores and ram in mib you can also update the cores and ram using a patch request at any time for more information, see partially modify servers https //api ionos com/docs/cloud/v6/#tag/servers/operation/datacentersserverspatch note do not specify the following properties templateuuid and cpufamily for example, assume that a vdc exists with the following uuid aaa 2bbb 3ccc 4ddd 5eee entities like volumes or nics are not included in the following example, but their usage is identical to servers of type enterprise for more information, see cloud api (6 0) https //api ionos com/docs/cloud/v6/ select the respective block to view a sample request and a sample response example request curl request post h 'authorization\ bearer $token' \\ \ url "https //api ionos com/cloudapi/v6/datacenters/1aaa 2bbb 3ccc 4ddd 5eee/servers" \\ \ header "content type application/json" \ data binary ' { "properties" { "name" "my vcpu", "type" "vcpu", "availabilityzone" "auto", "cores" 1, "ram" 2048 } } ' example response { "id" "b01c b5f6 4f77 9991 f539", "type" "server", "href" "https //api ionos com/cloudapi/v6/datacenters/1aaa 2bbb 3ccc 4ddd 5eee/servers/b01c b5f6 4f77 9991 f539", "metadata" { "etag" "2f2ca522ce", "createddate" "2023 08 08t09 35 11z", "createdby" "john doe\@example com", "createdbyuserid" "1234 1234 1234 1234 1234", "lastmodifieddate" "2023 08 08t09 35 11z", "lastmodifiedby" "john doe\@example com", "lastmodifiedbyuserid" "1234 1234 1234 1234 1234", "state" "busy" }, "properties" { "name" "my vcpu", "cores" 1, "ram" 2048, "availabilityzone" "auto", "vmstate" null, "bootcdrom" null, "bootvolume" null, "cpufamily" "intel skylake", "type" "vcpu" } } add a bootable drive drag a storage element (hdd or ssd) from the palette onto a vcpu server in the workspace to connect them together the highlighted vcpu will expand with a storage section click the unnamed hdd storage to highlight the storage section now you can see new options in the inspector pane on the right note storage type cannot be changed after provisioning configure storage enter a name that is unique within your vdc select a zone in which you want the storage device to be maintained when you select a (auto), our system assigns the optimal zone the availability zone cannot be changed after provisioning specify the required storage capacity you can increase the size after provisioning, even while the vcpu server is running, as long as its operating system supports it it is not possible to reduce the storage size after provisioning you can select one of images or snapshots, or use your own only images and snapshots that you have access to are available for selection since provisioning does not require you to specify an image, you can also create empty storage volumes authentication set the root or administrator password for your vcpu according to the guidelines this is recommended for both operating system types select an ssh key stored in the ssh key manager copy and paste the public part of your ssh key into this field select the storage volume from which the vcpu is to boot by clicking on boot or make boot device provision your changes the storage device is now provisioned and configured according to your settings alternative mode when adding a storage element using the inspector, select the appropriate checkbox in the add storage dialog box if you wish to boot from the network, set this on the vcpu vcpu in the workspace > inspector > storage it is recommended to always use virtio to benefit from the full performance of infiniband ide is intended for troubleshooting if, for instance, the operating system has no virtio drivers installed in this case, windows usually displays a "blue screen" when booting after provisioning, the live vertical scaling properties of the selected image are displayed you can make changes to these properties later, which will require a reboot you can set the properties of your uploaded images before you apply them to storage volumes in the image manager (optional) add and configure further storage elements (optional) make further changes to your data center provision your changes the storage device is now provisioned and configured according to your settings add a cd rom drive to assign an image and specify a boot device, you need to add and configure a storage element click on cd rom to add a cd rom drive so that you can use iso images to install and configure an operating system from scratch set up a network by connecting the vcpu server to other elements, such as an internet access element or other vcpu server through their nics provision your changes the vcpu server is available according to your settings stop, start, or reset a vcpu server when shutting down a vcpu server only at the operating system level, costs continue to accrue because its physical resources remain allocated to avoid cpu and ram charges, you can stop and deallocate the server's resources using the data center designer (dcd) this releases the resources for redistribution while keeping the server part of your infrastructure, in case you want to start it again a reset forces the vcpu server to shut down and reboot but may result in data loss stop a vcpu server choose a vcpu server from the settings tab in the inspector pane, select power > stop in the dialog box that appears, confirm your action by selecting the appropriate checkbox and clicking apply stop provision your changes confirm the action by entering your password result the vcpu server stops and billing is suspended start a vcpu server choose a vcpu server from the settings tab in the inspector pane, select power > start in the dialog box that appears, confirm your action by selecting the appropriate checkbox and clicking apply start provision your changes confirm the action by entering your password result the chosen vcpu server is booted a new public ip address is assigned to it depending on the configuration and billing is resumed reset a vcpu server choose a vcpu server from the settings tab in the inspector pane, select power > reset (optional) in the dialog box that appears, connect using the remote console and shut down the vcpu server at the operating system level to prevent data loss confirm your action by selecting the appropriate checkbox and clicking apply reset provision your changes confirm the action by entering your password result the vcpu server shuts down and reboots scale a vcpu server in the workspace , select the required vcpu server and use the inspector pane on the right note to modify multiple vcpu servers, select the data center and change the properties in the settings tab in this tab, you will find an overview of all assets belonging to the selected vdc you can change vcpus, ram, vcpu server status, and storage https //docs ionos com/cloud/support/general information/glossary of terms#storage size without having to manually update each vcpu server in the workspace modify storage ( optional ) create a snapshot https //docs ionos com/cloud/backup and storage/images snapshots/snapshots/how tos/create snapshot of the system to ensure recoverability in case of failure in the workspace, select the required vcpu server and increase the cpu size provision your changes you must set the new size at the operating system level of your vcpu server result the size of the cpu is adjusted in the dcd delete a vcpu server when you no longer need a particular vcpu server, with or without the associated storage devices, in your cloud infrastructure, you can remove it with a single mouse click or via the keyboard to ensure that no processes are interrupted, and no data is lost, we recommend you turn off the vcpu server before you delete it warning when you delete a vcpu server, its storage devices, or the entire data center, it is essential to note that the action does not automatically delete their backups however, deleting a backup unit will delete all associated backups when you no longer need the backups of a deleted vcpu server, delete them manually from the backup unit manager https //docs ionos com/cloud/backup and storage/backup service/how tos/delete backup unit to avoid unnecessary costs select the vcpu server in the workspace right click and open the context menu of the element select delete server you may also select the element icon and press the del key in the dialog box that appears, choose whether you also want to delete storage devices that belong to the vcpu server provision your changes result the vcpu server and its storage devices are deleted