Difference between revisions of "UEC: Manajemen Storage"
Onnowpurbo (talk | contribs) |
Onnowpurbo (talk | contribs) |
||
| Line 3: | Line 3: | ||
Storage Controller adalah komponen Eucalyptus yang memberikan layanan persistent block storage yang compatible dengan Amazon Elastic Block Store. Perintah euca2ools atau EC2 dapat digunakan untuk manajemen volume. Berikut adalah beberapa perintah euca yang digunakan untuk manajemen volume | Storage Controller adalah komponen Eucalyptus yang memberikan layanan persistent block storage yang compatible dengan Amazon Elastic Block Store. Perintah euca2ools atau EC2 dapat digunakan untuk manajemen volume. Berikut adalah beberapa perintah euca yang digunakan untuk manajemen volume | ||
| − | == | + | ==Interaksi dengan Storage Controller== |
===Linux Instances=== | ===Linux Instances=== | ||
| − | + | Membuat Volume 10 GB | |
| − | uecadmin@client1:~$ euca-create-volume -s 10 -z mycloud | + | uecadmin@client1:~$ euca-create-volume -s 10 -z mycloud |
| − | VOLUME vol-333C04B8 10 creating 2010-03-26T05:20:56.383Z | + | VOLUME vol-333C04B8 10 creating 2010-03-26T05:20:56.383Z |
List the volumes | List the volumes | ||
| − | uecadmin@client1:~$ euca-describe-volumes | + | uecadmin@client1:~$ euca-describe-volumes |
| − | VOLUME vol-333C04B8 10 mycloud available 2010-03-26T05:20:56.383Z | + | VOLUME vol-333C04B8 10 mycloud available 2010-03-26T05:20:56.383Z |
Attach a volume to a running instance | Attach a volume to a running instance | ||
| − | uecadmin@client1:~$ euca-attach-volume -i i-41620887 -d /dev/sdb vol-333C04B8 | + | uecadmin@client1:~$ euca-attach-volume -i i-41620887 -d /dev/sdb vol-333C04B8 |
The volumes status changes from “available” to “in-use” if it is attached properly as shown in the output of “euca-describe-volumes” below: | The volumes status changes from “available” to “in-use” if it is attached properly as shown in the output of “euca-describe-volumes” below: | ||
| − | uecadmin@client1:~$ euca-describe-volumes | + | uecadmin@client1:~$ euca-describe-volumes |
| − | VOLUME vol-333C04B8 10 mycloud in-use 2010-03-26T05:41:28.019Z | + | VOLUME vol-333C04B8 10 mycloud in-use 2010-03-26T05:41:28.019Z |
| − | ATTACHMENT vol-331F04B2 i-41620887 unknown,requested:/dev/sdb 2010-03-26T05:43:51.343Z | + | ATTACHMENT vol-331F04B2 i-41620887 unknown,requested:/dev/sdb 2010-03-26T05:43:51.343Z |
[sourcecode] | [sourcecode] | ||
You can login to the instance through ssh and see the new volume as a newly attached block storage, which shows up in the example below as /dev/sdb: | You can login to the instance through ssh and see the new volume as a newly attached block storage, which shows up in the example below as /dev/sdb: | ||
[sourcecode] | [sourcecode] | ||
| − | $ sudo fdisk -l | + | $ sudo fdisk -l |
| − | Disk /dev/sda: 2195 MB, 2195718144 bytes | + | Disk /dev/sda: 2195 MB, 2195718144 bytes |
| − | 4 heads, 32 sectors/track, 33504 cylinders | + | 4 heads, 32 sectors/track, 33504 cylinders |
| − | Units = cylinders of 128 * 512 = 65536 bytes | + | Units = cylinders of 128 * 512 = 65536 bytes |
| − | Disk identifier: 0x000adc1c | + | Disk identifier: 0x000adc1c |
| − | + | ||
| − | + | Device Boot Start End Blocks Id System | |
| − | /dev/sda1 1 32769 2097152+ 83 Linux | + | /dev/sda1 1 32769 2097152+ 83 Linux |
| − | /dev/sda3 32769 33504 47071 82 Linux swap / Solaris | + | /dev/sda3 32769 33504 47071 82 Linux swap / Solaris |
| − | + | ||
| − | Disk /dev/sdb: 10.7 GB, 10737418240 bytes | + | Disk /dev/sdb: 10.7 GB, 10737418240 bytes |
| − | 64 heads, 32 sectors/track, 10240 cylinders | + | 64 heads, 32 sectors/track, 10240 cylinders |
| − | Units = cylinders of 2048 * 512 = 1048576 bytes | + | Units = cylinders of 2048 * 512 = 1048576 bytes |
| − | Disk identifier: 0x00000000 | + | Disk identifier: 0x00000000 |
Disk /dev/sdb doesn't contain a valid partition table | Disk /dev/sdb doesn't contain a valid partition table | ||
| Line 52: | Line 52: | ||
Detach a volume: | Detach a volume: | ||
| − | uecadmin@client1:~$ euca-detach-volume vol-333C04B8 | + | uecadmin@client1:~$ euca-detach-volume vol-333C04B8 |
==WS3 Storage Controller== | ==WS3 Storage Controller== | ||
| Line 80: | Line 80: | ||
Snapshots can be created by using euca-create-snapshot command: | Snapshots can be created by using euca-create-snapshot command: | ||
| − | uecadmin@client1:~$ euca-create-snapshot vol-333C04B8 | + | uecadmin@client1:~$ euca-create-snapshot vol-333C04B8 |
euca-describe-snapshots lists the available snapshots. | euca-describe-snapshots lists the available snapshots. | ||
| − | uecadmin@client1:~$ euca-describe-snapshots | + | uecadmin@client1:~$ euca-describe-snapshots |
| − | SNAPSHOT snap-32A804A2 vol-333C04B8 completed 2010-04-15T13:48:32.01Z 100% | + | SNAPSHOT snap-32A804A2 vol-333C04B8 completed 2010-04-15T13:48:32.01Z 100% |
Volumes from these snapshots can be created by using the snapshot id. | Volumes from these snapshots can be created by using the snapshot id. | ||
| − | uecadmin@client1:~$ euca-create-volume -s 10 --snapshot snap-32A804A2 --zone mycloud | + | uecadmin@client1:~$ euca-create-volume -s 10 --snapshot snap-32A804A2 --zone mycloud |
Please note that the volume can only be created after the snapshot status is completed. Similarly, snapshots from a volume can only be created after the volume status is created, but not during the creating stage. To delete a snapshot: | Please note that the volume can only be created after the snapshot status is completed. Similarly, snapshots from a volume can only be created after the volume status is created, but not during the creating stage. To delete a snapshot: | ||
| − | uecadmin@client1:~$ euca-delete-snapshot snap-32A804A2 | + | uecadmin@client1:~$ euca-delete-snapshot snap-32A804A2 |
Revision as of 06:29, 28 December 2010
Storage Controller
Storage Controller adalah komponen Eucalyptus yang memberikan layanan persistent block storage yang compatible dengan Amazon Elastic Block Store. Perintah euca2ools atau EC2 dapat digunakan untuk manajemen volume. Berikut adalah beberapa perintah euca yang digunakan untuk manajemen volume
Interaksi dengan Storage Controller
Linux Instances
Membuat Volume 10 GB
uecadmin@client1:~$ euca-create-volume -s 10 -z mycloud VOLUME vol-333C04B8 10 creating 2010-03-26T05:20:56.383Z
List the volumes
uecadmin@client1:~$ euca-describe-volumes VOLUME vol-333C04B8 10 mycloud available 2010-03-26T05:20:56.383Z
Attach a volume to a running instance
uecadmin@client1:~$ euca-attach-volume -i i-41620887 -d /dev/sdb vol-333C04B8
The volumes status changes from “available” to “in-use” if it is attached properly as shown in the output of “euca-describe-volumes” below:
uecadmin@client1:~$ euca-describe-volumes VOLUME vol-333C04B8 10 mycloud in-use 2010-03-26T05:41:28.019Z ATTACHMENT vol-331F04B2 i-41620887 unknown,requested:/dev/sdb 2010-03-26T05:43:51.343Z
[sourcecode] You can login to the instance through ssh and see the new volume as a newly attached block storage, which shows up in the example below as /dev/sdb:
[sourcecode]
$ sudo fdisk -l
Disk /dev/sda: 2195 MB, 2195718144 bytes 4 heads, 32 sectors/track, 33504 cylinders Units = cylinders of 128 * 512 = 65536 bytes Disk identifier: 0x000adc1c Device Boot Start End Blocks Id System /dev/sda1 1 32769 2097152+ 83 Linux /dev/sda3 32769 33504 47071 82 Linux swap / Solaris Disk /dev/sdb: 10.7 GB, 10737418240 bytes 64 heads, 32 sectors/track, 10240 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table
You can format /dev/sdb, mount it and use it as a persistent storage. It is better to unmount the volume before bringing down the instance, to avoid any data corruption.
Detach a volume:
uecadmin@client1:~$ euca-detach-volume vol-333C04B8
WS3 Storage Controller
Walrus is a storage service in Eucalyptus which is compatible with Amazon’s S3. Using Walrus users can store persistent data, which is organized as buckets and objects. WS3 is a file level storage system, as compared to the block level storage system of Storage Controller.
See Amazon’s S3 Getting Started Guide for more information http://docs.amazonwebservices.com/AmazonS3/2006-03-01/gsg/).
Walrus Controller options can be modified from the Web UI, on the “Configuration” page under “Walrus Configuration” section.
For using Walrus to manage Eucalyptus VM images, you can use Amazon’s tools to store/register/delete them from Walrus. Other third party tools can also be used to interact with Walrus directly. Third party tools for interacting with Walrus
* s3curl S3 Curl is a command line tool that is a wrapper around curl.
http://open.eucalyptus.com/wiki/s3curl
* s3cmd is a tool that allows command line access to storage that supports the S3 API.
http://open.eucalyptus.com/wiki/s3cmd
* s3fs is a tool that allows users to access S3 buckets as local directories.
http://open.eucalyptus.com/wiki/s3fs
Snapshots
The volumes that have been created on the Block Storage can be used to create point-in-time snapshots of volumes, which are stored on WS3. These snapshots can be used as the starting point for new Block Storage volumes and protect data for long-term durability. The same snapshot can be used to create many volumes as per requirement.
Snapshots can be created by using euca-create-snapshot command:
uecadmin@client1:~$ euca-create-snapshot vol-333C04B8
euca-describe-snapshots lists the available snapshots.
uecadmin@client1:~$ euca-describe-snapshots SNAPSHOT snap-32A804A2 vol-333C04B8 completed 2010-04-15T13:48:32.01Z 100%
Volumes from these snapshots can be created by using the snapshot id.
uecadmin@client1:~$ euca-create-volume -s 10 --snapshot snap-32A804A2 --zone mycloud
Please note that the volume can only be created after the snapshot status is completed. Similarly, snapshots from a volume can only be created after the volume status is created, but not during the creating stage. To delete a snapshot:
uecadmin@client1:~$ euca-delete-snapshot snap-32A804A2