Dapatkan sumber kredensial demo untuk melakukan langkah-langkah berikut sebagai proyek non-administrasi:
$ . demo-openrc
Buat volume 1GB:
$ openstack volume create --size 1 volume1
+---------------------+--------------------------------------+
| Field | Value |
+---------------------+--------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2016-03-08T14:30:48.391027 |
| description | None |
| encrypted | False |
| id | a1e8be72-a395-4a6f-8e07-856a57c39524 |
| multiattach | False |
| name | volume1 |
| properties | |
| replication_status | disabled |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | creating |
| type | None |
| updated_at | None |
| user_id | 684286a9079845359882afc3aa5011fb |
+---------------------+--------------------------------------+
Setelah waktu yang singkat, status volume harus berubah dari creating ke available:
$ openstack volume list
+--------------------------------------+--------------+-----------+------+-------------+
| ID | Display Name | Status | Size | Attached to |
+--------------------------------------+--------------+-----------+------+-------------+
| a1e8be72-a395-4a6f-8e07-856a57c39524 | volume1 | available | 1 | |
+--------------------------------------+--------------+-----------+------+-------------+
Tempelkan volume ke sebuah instance:
$ openstack server add volume INSTANCE_NAME VOLUME_NAME
Ganti INSTANCE_NAME dengan nama instance dan VOLUME_NAME dengan nama volume Anda ingin tempelkan untuk itu.
Contoh
Tempel volume Volume1 ke instance provider-instance:
$ openstack server add volume provider-instance volume1
Catatan
Command ini tidak memberikan output.
Lihat daftar volume:
$ openstack volume list
+--------------------------------------+--------------+--------+------+--------------------------------------------+
| ID | Display Name | Status | Size | Attached to |
+--------------------------------------+--------------+--------+------+--------------------------------------------+
| a1e8be72-a395-4a6f-8e07-856a57c39524 | volume1 | in-use | 1 | Attached to provider-instance on /dev/vdb |
+--------------------------------------+--------------+--------+------+--------------------------------------------+
Mengakses instance Anda menggunakan SSH dan menggunakan command fdisk untuk memverifikasi keberadaan volume sebagai perangkat penyimpanan blok /dev/vdb.
$ sudo fdisk -l
Disk /dev/vda: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders, total 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/vda1 * 16065 2088449 1036192+ 83 Linux
Disk /dev/vdb: 1073 MB, 1073741824 bytes
16 heads, 63 sectors/track, 2080 cylinders, total 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/vdb doesn't contain a valid partition table
Catatan
Anda harus membuat sistem file pada perangkat dan me-mount file itu menggunakan volume.
Untuk informasi lebih lanjut tentang bagaimana mengelola volume, lihat Manage volumes dalam OpenStack End User Guide.
Balik ke Luncur sebuah instance.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.