Help:Adding Disk Space to Cloud VPS instances

Cloud VPS
Cloud VPS technical documentation Cloud VPS and Toolforge at a glance Cloud VPS project Cloud VPS Infrastructure Cloud Services roles and user rights Cloud VPS administrator documentation Help and communication Glossary Technical documentation resources
Instances and access Set up a Cloud VPS Instance Set up a Cloud VPS Instance using MediaWiki-Vagrant Set up a Cloud VPS Instance using LAMP stack Access Cloud Services Instances Access Cloud Services Instances with PuTTY and WinSCP
Security and policies Security groups and firewall settings Configure sudo policies Server groups
Horizon, proxies and puppet About Horizon Manage floating IP addresses Proxy to reach Cloud VPS server Puppet compiler Standalone puppetmaster
Troubleshooting Locale errors LAMP issues
Additional documentation Resize root partition Development recommendations for easily moving to production

Overview

This page explains how to add additional disk space to your Cloud VPS instance.

Storage quota on Cloud VPS instances

Cloud VPS instances have a maximum storage quota based on the size of the instance. By default only 20G of the allowed quota is allocated to the instance as the / volume.

The additional space is allocated to /srv. If you already have content in /srv, it will be hidden by the new mount.

Back up your content before proceeding, or see recovery instructions below.

Adding space as a second volume

The additional space can be added to the instance as a separate logical volume. The easiest way to do this is by enabling the role::labs::lvm::srv Puppet role.

If you have Horizon puppet set to 'yaml mode' (the default):

1. go to https://horizon.wikimedia.org/project/ ;
2. set "your project" in the project filter;
3. find the instance you want to change the in the table below that;
4. click on the Puppet Configuration tab to get to the Puppet management screen for that instance;
5. Add a new line with "role::labs::lvm::srv" to the "Puppet Classes" field
6. wait for the Puppet job to run, OR connect to the instance and run sudo puppet agent --test --verbose.

If you have Horizon puppet set to 'guided mode':

1. go to https://horizon.wikimedia.org/project/ ;
2. set "your project" in the project filter;
3. find the instance you want to change the in the table below that;
4. click on the Puppet Configuration tab to get to the Puppet management screen for that instance;
5. in the row for role::labs::lvm::srv, click on the Apply Class button;
6. in the pop-up, click on the Apply;
7. wait for the Puppet job to run, OR connect to the instance and run sudo puppet agent --test --verbose.

After the Puppet run completes you should see a new volume mounted at /srv. The size of this volume will depend on the amount of remaining quota for your instance.

Mind the /srv. directory will be owned by root., and this will be enforced by puppet. /srv. is a directory for a collection of local content. Best practice is to create subdirectories for each individual service and give permissions to project members appropriately.

Moving old /srv data to new volume

If you only realized that you need more space after you have put things in the /srv directory of the root partition, follow these basic steps to move that data to the new volume:

1. Add the new volume as shown above
2. Run mount and make sure the volume is mounted. If it is not force another puppet run.
3. Run sudo -s to get a root shell. This will make the next steps easier.
4. puppet agent --disable 'Moving data from /srv to new volume'
5. umount /srv
6. mount /dev/mapper/vd-second--local--disk /mnt
7. Copy data from /srv to /mnt with cd /srv; tar cf - . | (cd /mnt; tar xpvf -)
8. Verify that /mnt now has the expected data.
9. Remove old data from /srv with cd /srv; rm -rf *
10. cd; umount /mnt
11. mount /dev/mapper/vd-second--local--disk /srv
12. Verify that mount worked with mount and by examining /srv
13. puppet agent --enable
14. puppet agent --test --verbose to make sure things stay as expected

Resize root partition

See Help:Resize root partition for an explanation of how to attempt to resize the / volume for an existing instance.

Communication and support

We communicate and provide support through several primary channels. Please reach out with questions and to join the conversation.

Communicate with us

	Connect	Best for
Phabricator Workboard	#Cloud-Services	Task tracking and bug reporting
IRC Channel	#wikimedia-cloud connect	General discussion and support
Mailing List	cloud@	Information about ongoing initiatives, general discussion and support
Announcement emails	cloud-announce@	Information about critical changes (all messages mirrored to cloud@)
News wiki page	News	Information about major near-term plans
Cloud Services Blog	Clouds & Unicorns	Learning more details about some of our work
Wikimedia Technology Blog	techblog.wikimedia.org	News and stories from the Wikimedia technical movement