Virtual Machines (VMs) are fully functional computational instances. They operate as if they were real physical entities with all the elements of a physical server. A user obtains his VM with full root access. He can fully manage it and install any software he has and needs. All VM in CloudFerro clouds have preconfigured access to EODATA storage.

In CloudFerro Users can use Virtual Machines (VMs) by defining their different parameters and characteristics, including machine type (physical or virtual), RAM, CPU type and number of vCores, Storage quantity and type, Operating System, middleware components, Virtual Networks connected to the machine.

Users determine the characteristics of a newly provisioned VM by selecting its flavor and base image. VMs with the same name offer identical performance from the user perspective across different clouds. Currently available flavours are presented in the following tables:

Figure 1 - Intel base flavours in CF2, WAW3-1, WAW3-2, FRA1-2
Virtual Machines (VM)
Available VMvCoresRAM (GB**)SSD Network Storage (GB)NVMe Local Storage (GB***)
eo1*
eo1.xsmall1180
eo1.small22160
eo1.xmedium1280
eo1.medium24160
eo1.large48320
eo2****
eo2.medium14160
eo2.large28320
eo2.xlarge416640
eo2.2xlarge8321280
eo2.3xlarge16642560
eo2.4xlarge321283840
eo2.5xlarge642563840
hm
hm.medium216640
hm.large4321280
hm.xlarge8642560
hm.2xlarge161283840
hm.3xlarge322563840
hm.4xlarge644843840
hmd
hmd.medium216050
hmd.large4320100
hmd.xlarge8640200
hmd.2xlarge161280400
hmd.3xlarge322560800
hmd.4xlarge6448401600

* In WAW3-2 eo1 should be used as sandbox or non crytical usage as it dosnt offer guarantiedCPU performance
** Openstack Clouds assaigne and report in GiB
*** Local storage is only avaiable as ephemeral storage, all crytical data should be backed up to other form of storage
**** In WAW3-2 eo2 was replaced with eo2a as primary Compute flavour

Figure 2 - AMD base flavours in CF2, WAW3-1, WAW3-2, FRA1-2
Virtual Machines (VM)
Available VMvCoresRAM (GB**)SSD Network Storage (GB)NVMe Local Storage (GB***)
eo2a*
eo2a.medium14160
eo2a.large28320
eo2a.xlarge416640
eo2a.2xlarge8321280
eo2a.3xlarge16642560
eo2a.4xlarge321283840
eo2a.5xlarge642563840
hm
hma.medium216640
hma.large4321280
hma.xlarge8642560
hma.2xlarge161283840
hma.3xlarge322563840
hma.4xlarge644843840
hmd*
hmad.medium216050
hmad.large4320100
hmad.xlarge8640200
hmad.2xlarge161280400
hmad.3xlarge322560800
hmad.4xlarge6448401600

* Those flavours are only avaiable in WAW3-2
** Openstack Clouds assaigne and report in GiB
*** Local storage is only avaiable as ephemeral storage, all crytical data should be backed up to other form of storage

Operating systems and images

Users may utilize VM-s and other cloud Resources using the CloudFerro Dashboard, the REST API, a command line client or the Openstack Orchestration scripts (Heat). VMs can be connected to the network using virtual interfaces.

List for operating system and ready to use images available in Clouds. Some images may not be available in all locations For better information refer to horizon dashboard.

  • CentOS 7
  • Ubuntu 14.04 LTS, 16.04 LTS, 18.04 LTS
  • Windows 2016 mini / full
  • RHEL 6,7 mini / full
  • SLES 12 mini / full
  • OSGeo 11.0
  • App Catalog Image

All the VMs come fully configured (based on the image selected) and ready-for-use, with an administrative User account, network access, preconfigured toolboxes and software components. Volume Storage may be attached to running VM-s to extend the storage space available. VMs can be started, stopped, rebooted, paused, suspended and snapshotted. Live backup functionality is also available, including server quiescing. VMs may also be attached to Virtual Networks. Virtual Networks may be system-defined or User-defined.

System defined networks include:

  • Internet network used to access the global internet
  • The EO Storage network available in Projects/Environments that are allowed access the EODATA

Provisioning

Users may utilize VM-s and other cloud Resources using the CloudFerro Dashboard, the REST API, a command line client or the Openstack Orchestration scripts (Heat). VMs can be connected to the network using virtual interfaces.

Billing

The VMs can be billed in monthly or longer quanta (Fixed Term Mode) or can be billed per hours of usage (Per Usage Mode). Users may also temporarily shelve their VMs based on persistent storage, paying only for the persistent storage space they occupy. Detailed pricing and avaiability of configurations is documented in