How to add local datastore to the cloud.net cloud?
Cloud.net, all versions.
Before You Begin
Ensure that you have the block device visible on the compute resource. OnApp doesn’t support the 4 K block size for local LVM data stores.
|VERY IMPORTANT: Perform the procedures only once per data store! Take care when selecting the disk/partition you want to use for storing virtual servers' data!|
Data stores provide disk space for your virtual servers and operating systems. Data stores are attached to Compute resources.
Add local LVM datastore
To install an LVM data store, follow the next procedure:
Add the new data store to OnApp via the Control Panel user interface:
Go to your Control Panel > Admin > Settings menu.
- Click the Data Stores icon.
- Click the Create Data Store button at the bottom of the screen.
- Follow the steps in the creation wizard:
- Enter a Label for your data store.
- IP address: leave blank
- Select the Data Store Type: LVM.
- Move the Enabled slider to the right to enable a data store. When disabled, OnApp will not allow new disks to be created automatically on that data store. This is useful to prevent an established data store from becoming too full. It also lets you prevent the automatic creation of root disks on 'special' data stores (high speed, etc).
- Click Next.
- Set Disk Capacity in GB.
- Bind the data store with a Local Compute Resource.
- If required, you can also assign the data store to a Data Store Zone. The drop-down menu lists all data store zones set up in the cloud.
When you are finished configuring the data store, click the Create Data Store button.
To use the data store, you have to assign it either to a compute resource or a compute zone.
- Find the data store unique identifier (this is needed to create your volume group in step #4):
(On the data stores page http://xxx.xxx.xxx.xxx/settings/data_stores read the 'identifier' of the newly created data store)
- Connect via SSH to a compute resource that is able to connect to this data store. Create the physical volume:
# pvcreate --metadatasize 50M /dev/xxxReplace xxx with the real device.
- Create the volume group:
# vgcreate <identifier> /dev/xxx
Replace xxx with the real device and IDENTIFIER with the info from the data store page on the UI.
- Test compute resource/volume group visibility. Now when you have the new data store formatted, you should be able to see the volume group from all compute resources. To test this, run pvscan and vgscan on all compute resources. Make sure you can see all identifiers on all compute resources.