Working with /mnt size on EY Cloud

Working with /mnt size on EY Cloud

When you’re booting a new environment or adding a new cluster to a specific environment, you might want to specify a custom size for the /mnt partition or you can ignore those fields. If you specify a value on the respective field for /mnt size, the system will take such value and assign it to the /mnt partition. Otherwise, if you don’t specify a value, the system will assign 25GB.

Prerequisite:  You need the username and password for your EY Cloud account. If you do not already have this, submit a request with Engine Yard Support.

To determine if the /mnt default size works

1. Log in to EY Cloud at http://cloud.engineyard.com.

2. Create a new environment with the following data:

• Todo App

• Production

• Passenger 4

• Stable-v4

• Ruby 2.1

• RubyGems 2.4.8

• PostgreSQL 9.4

• US East (N. Virginia)

• Staging Setup

Wait for chef to completion.

Verify chef runs to completion and app works as expected.

SSH into each instance and check the /mnt size (df -h /mnt).

Make sure the /mnt size is 25GB for all instances.

To determine if the /mnt custom size works

1. Log in to EY Cloud at http://cloud.engineyard.com.

2. Create a new environment with the following data:

• Todo App

• Production

• Passenger 4

• Stable-v4

• Ruby 2.1

• RubyGems 2.4.8

• PostgreSQL 9.4

• US East (N. Virginia)

• Custom Setup

• 1 App Instance (default size)

• /data volume: 20GB
• /mnt size: 10GB

• 1 DB Instance (default size)

• /data volume: 150GB
• /mnt size: none (leave it in blank)

• 1 Utility Instance (default size)

• name: up to you
• /data volume size: 15GB
• /mnt size: 1GB

Wait for chef to completion.

Verify chef runs to completion and app works as expected.

SSH into each instance and check the /mnt size (df -h /mnt).

Make sure the /mnt size is 10GB for app, 25GB for DB and 1GB for utility