CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Attach Multiple Volumes to Tiers


You can attach multiple volumes to all tier types in N-tier applications. For each volume, you must specify the size and can optionally configure the volume type.

Node Restart Behavior

When you restart a  node or deploy an application, the appropriate volumes (defined in the Topology Modeler > Properties tab) are attached. For example, if Node 1 has Volumes V1 and V2, and Node 2 has volumes V3 and V4, then on restart, the same volume combination (number of volumes, size, and type) are attached to the nodes.

Configurable Volume Attributes


Size is a required volume information attribute. 


Type is an optional volume information attribute that only provides values for AWS cloud instances identified in this section. For other cloud instances, the default volume type is used.

Azure Type Nuances

Prior to CloudCenter, you could create a storage account and create storage for instances under that account. With the introduction of Managed Disks in Azure,  you can select one of three pre-defined disk sizes during deployment in CloudCenter and later:

The Number of Volumes field pre-populates the default volume size as specified in the UI Configuration Options section below.

Ensure that the Number of Volumes field does not display 0 (zero) if you need to assign a predefined type to an Azure RM-based deployment.

Azure cloud instances display one of the following values for the Type attribute:

  • Premium (Managed)
  • Standard (Managed)
  • Unmanaged

AWS Type Nuances

AWS cloud instances display one of the following values for the Type attribute:

  • Magnetic
  • General Purpose (SSD)
  • Provisioned IOPS (SSD)

Google Type Nuances

Google cloud instances display one of the following values for the Type attribute:

  • Standard Persistent Disk
  • SSD Persistent Disk
  • Local SSD Scratch disk   


Input/Output Operations Per Second (IOPS) is an optional volume information attribute. This attribute is only applicable if the Type attribute displays the Provisioned IOPS (SSD) value (see Submit Job). The ratio of provisioned IOPS and the requested volume size can be a maximum of 30. That is, a volume with 3000 IOPS must be a minimum of 100 GB in size.

A Provisioned IOPS (SSD) volume can range in size from 4 GB to 16 TB and in IOPS from 100 to 20000.

UI Configuration Options

  • When modelling N-tier applications, specify the Number of Volumes to be attached to each tier and the Default Volume Size for each volume in the Topology Modeler Properties tab's General Settings fields. If the selected cloud doesn't have volume types, the default volume size is prepopulated when running this application.
  • When deploying applications, you can specify the volume information (size, type, and iops) for each volumes to be attached to a particular tier. The default volume size specified while modeling the app will be pre-populated. By default, all services does not have any persistent volume disk attached out-of-the box. If required, you can change the default volume size at this point.

  • Volume type selection for AWS. 
  • You can configure the root volume size for AWS deployments using either the UI or the Submit Job (v2) API.

    The previous generation AWS instance types like the t1, m1 series do not support the resizing of root volume.

    • To provide a larger size for root volume for an AWS deployment, use the CloudCenter instance type. The storage is provided in addition to the instance store and must be larger than the Root Volume size in the AMI. If set to zero, then the Root Volume size in the AMI is used.
    • Root volume size = 0 (zer0) value: Configure the root volume size as 0 for the older generation of instance types. This zero configuration, by default, uses the AMI's root volume size.
    • Root volume size = non-zero value:

      • The General Purpose SSD type option is automatically selected for the each root volume.

      • Be sure to configure the root volume size to be higher than the size specified in the AMI but less than the size supported by AWS for General Purpose SSDs.

API Configuration Options

See the volumeInfos and the rootVolumeSize attributes in the Submit Job (v1) and the Submit Job (v2) APIs.

© 2017-2019 Cisco Systems, Inc. All rights reserved