../_images/preview.png

Configuring Storage

SCOPE_ENV

Storage is configured at the Farm Role and includes options for configuring the mandatory root storage volume and optional additional storage. The additional storage can be shared on some clouds and marked as reusable. Reusable storage is automatically preserved by a snapshot and added to new servers when they are launched. In AWS this includes copying snapshots to other Availability Zones when a Farm Role is re-launched in a different AZ.

Note

Storage configuration changes do not apply to running Servers. They only take effect when new servers are launched.

Below is an example of a Storage configuration for a root volume. The actual options available are specific to the Cloud allocated to the Farm Role but are typically limited to the volume size and type.

../_images/storage_root.png

For additional storage there are many more options available which are again specific to the Cloud allocated to the Farm Role. This example for AWS shows the full set of options when auto-mount is enabled.

../_images/storage_add.png

The common parameters for additional storage are as follows.

Option Description
Storage Engine Storage type to attach. View Cloud specific pages for more detail.
Filesystem Filesystem to use with the storage (Scalr will automatically format the storage).
Reuse If you enable this option storage from Terminated Servers will be reused when new Servers are provisioned.
Recreate missing volumes If you enable this option, then missing Storage will be re-created by Scalr when Servers are launched. If you do not enable this option, your instances will enter Failed State if Storage is missing. Missing storage is defined as persistent storage (i.e. devices) that were provisioned by Scalr and subsequently deleted through your Cloud Console’s or API. When launching Servers for the first time, no storage will be available, and Scalr will automatically provision what’s needed, regardless of this setting.
Automatically mount device If you enable this option, then Scalr will automatically mount the storage to your instance’s filesystem, to the path that you indicated.
Volume Settings Cloud Specific Volume configuration. View subpages for more detail

Volume Mounting

The way volumes are mounted varies depending on the Operating System.

It is important to be aware that the EBSVolumeMounted Event can fire when volumes are remounted during a reboot. Thus any Orchestration Rules that are trigged by the EBSVolumeMounted Event must be coded to be aware of this possibility and not take any inappropriate actions after reboots that could cause data loss.

For ALL Operating Systems additional volumes (not root / C:) are mounted by the scalr agent (scalarizr) on the first boot of a Server and will trigger the EBSVolumeMounted Event. For subsequent reboots the additional volumes are mounted as follows.

Linux

On first boot scalarizr adds the additional volumes to the operating systems fstab file, e.g. /etc/fstab so that the Operating System itself will remount the volumes on subsequent reboots. Thus the EBSVolumeMounted Event event will NOT fire for additional volumes after a reboot.

However if scalarizr detects that a volume configured in Scalr has not been re-mounted after a reboot, e.g. because the entry was removed from fstab, then it will re-mount the volume and add it back into fstab. In these circumstances the EBSVolumeMounted Event WILL fire.

Windows

Scalarizr performs all required volume mounting on first boot and all subsequent re-boots. Thus the EBSVolumeMounted Event WILL fire on every re-boot.

Note

Scalarizr checks volumes every time it restarts, so if any manual adjustments have been made since the server booted, scalarizr will unmount and remount volumes to ensure the Scalr configuration is re-applied. The EBSVolumeMounted Event will fire for these adjustments. If you wish to change the configuration of Volumes you must do this through Scalr.

AWS Storage Configuration

Additional AWS EBS Volumes can be configured on a Farm Role to be added to every server. The additional EBS options are as follows.

Option Description
EBS Type The full range of EBS types can be selected. See Amazon EBS Product Details NEWWIN for more details
Snapshot The Snapshot to create the volume from. If blank a new Volume is created
Enable EBS encryption Turn on encryption and specify the KMS key
../_images/storage_aws.png

All storage volumes for AWS can be managed in the EBS Volumes page. Go to the main Scalr menu dropdown on the top left MENU_ENV and click on AWS, then EC2, and EBS volumes:

../_images/storage_aws2.png

From the screen above you can do the following:

  • Create and attach storage
  • Change existing volume settings: size, type, tags
  • Check Cloud Watch statistics
  • Snapshot the selected volume
  • Setup automatic snapshots for a volume

Google Cloud Platform Storage Configuration

GCP based Farm Roles can have additional storage added using either “Persistent Disk” or “Local SSD (ephemeral)”.

Persistent Disk : Options are Standard or SSD disk
Local SSD : Only option is the name.

GCP1 GCP2

All storage volumes for GCP can be managed in the GCP Persistent Disk page. Go to the main Scalr menu dropdown on the top left MENU_ENV, click on Google Cloud Platform, then Compute Engine, and Persistent Disks:

../_images/storage_gcp_3.png

From the screen above you can do the following:

  • Change the size of the exists disks

Azure Storage Configuration

Azure based Farm Roles can have additional managed data disks added. The only option is the size.

../_images/storage_azure.png

All storage volumes for Azure can be managed in the Azure Managed Disk page. Go to the main Scalr menu dropdown on the top left MENU_ENV, click on Azure and Managed Disks:

../_images/storage_azure2.png

From the screen above you can do the following:

  • Create a new Managed Disk
  • Update the size and type of existing disks

OpenStack Storage Configuration

OpenStack based Farm Roles can have additional persistent disks added. The only option is the size.

../_images/storage_openstack.png

All storage volumes for Openstack can be managed in the Openstack Volumes page. Go to the main Scalr menu dropdown on the top left MENU_ENV, click on Openstack and then Volumes:

../_images/storage_openstack2.png

From the screen above you can do the following:

  • Create and attach storage
  • Change existing volume settings: size, type, tags
  • Snapshot the selected volume
  • Setup automatic snapshots for a volume

VMWare Storage Configuration

VMware based Farm Roles can have additional virtual disks added. The Volume Settings available are as follows.

Option Description
Provisioning Defines how to initialise the volume using zeroing
Shared Disk Allows the disk to be shared across all servers in the Farm Role. Only available for “Eager Zeroed” provisioning
Datastore Select the datastore that the extra volume should be provisioned to. If the placement strategy is “auto” then all volumes will be placed on the datastore selected by Scalr.
../_images/storage_vmware.png

All storage volumes for VMware can be managed in the VMware Virtual Disks page. Go to the main Scalr menu dropdown on the top left MENU_ENV, click on VMware and then Virtual Disks:

../_images/storage_vmware2.png

From the screen above you can do the following:

  • Create and attach storage