CentOS 7
Sponsored Link

OpenStack Rocky : Cinder Storage (LVM)
2018/09/04
 
It's possible to use Virtual Storages provided by Cinder if an Instance needs more disks.
Configure Virtual storage with LVM backend on here.
It needs there are some free spaces on disks of Storage Node.
------------+---------------------------+---------------------------+------------
            |                           |                           |
        eth0|10.0.0.30              eth0|10.0.0.50              eth0|10.0.0.51
+-----------+-----------+   +-----------+-----------+   +-----------+-----------+
|    [ Control Node ]   |   |    [ Storage Node ]   |   |    [ Compute Node ]   |
|                       |   |                       |   |                       |
|  MariaDB    RabbitMQ  |   |      Open vSwitch     |   |        Libvirt        |
|  Memcached  httpd     |   |        L2 Agent       |   |     Nova Compute      |
|  Keystone   Glance    |   |        L3 Agent       |   |      Open vSwitch     |
|  Nova API             |   |     Metadata Agent    |   |        L2 Agent       |
|  Neutron Server       |   |     Cinder-Volume     |   |                       |
|  Metadata Agent       |   |      iSCSI Target     |   |                       |
|  Cinder API           |   |                       |   |                       |
+-----------------------+   +-----------------------+   +-----------------------+

[1] Create a volume group for Cinder on Storage Node.
[root@storage ~]#
pvcreate /dev/sdb1

Physical volume "/dev/sdb1" successfully created
[root@storage ~]#
vgcreate -s 32M vg_volume01 /dev/sdb1

Volume group "vg_volume01" successfully created
[2] Configure Cinder Volume on Storage Node.
[root@storage ~]#
vi /etc/cinder/cinder.conf
# add follows into [DEFAULT] section

enabled_backends = lvm

# add follows to the end
[lvm]
target_helper = lioadm
target_protocol = iscsi
# IP address of Storage Node
target_ip_address = 10.0.0.50
# volume group name just created
volume_group = vg_volume01
volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
volumes_dir = $state_path/volumes

[root@storage ~]#
systemctl restart openstack-cinder-volume

[3] On Storage Node, if Firewalld is running, allow service like follows.
[root@storage ~]#
firewall-cmd --add-service=iscsi-target --permanent

success
[root@storage ~]#
firewall-cmd --reload

success
[4] Configure Nova on Compute Node.
[root@node01 ~]#
vi /etc/nova/nova.conf
# add to the end

[cinder]
os_region_name = RegionOne
[root@node01 ~]#
systemctl restart openstack-nova-compute

[5] Login as a common user you'd like to add volumes to own instances.
For example, create a virtual disk [disk01] with 10GB.
It's OK to work on any node. (This example is on Control Node)
# first, with root priviledge, downgrade Cinder Client to Queens release version

# because it's impossible to run [Volume Create] with current version [python2-cinderclient-4.0.1]

[root@dlp ~(keystone)]#
rpm -q python2-cinderclient

python2-cinderclient-4.0.1-1.el7.noarch
[root@dlp ~(keystone)]#
curl -O http://ftp.jaist.ac.jp/pub/Linux/CentOS/7/cloud/x86_64/openstack-queens/python2-cinderclient-3.5.0-1.el7.noarch.rpm

[root@dlp ~(keystone)]#
rpm -Uvh --oldpackage python2-cinderclient-3.5.0-1.el7.noarch.rpm
# work with any user from here

# set environment variable first

[cent@dlp ~(keystone)]$
echo "export OS_VOLUME_API_VERSION=3" >> ~/keystonerc

[cent@dlp ~(keystone)]$
source ~/keystonerc
[cent@dlp ~(keystone)]$
openstack volume create --size 10 disk01

+---------------------+--------------------------------------+
| Field               | Value                                |
+---------------------+--------------------------------------+
| attachments         | []                                   |
| availability_zone   | nova                                 |
| bootable            | false                                |
| consistencygroup_id | None                                 |
| created_at          | 2018-09-04T01:12:25.000000           |
| description         | None                                 |
| encrypted           | False                                |
| id                  | 6f1a946b-5dfc-403a-9545-5516670f2abe |
| multiattach         | False                                |
| name                | disk01                               |
| properties          |                                      |
| replication_status  | None                                 |
| size                | 10                                   |
| snapshot_id         | None                                 |
| source_volid        | None                                 |
| status              | creating                             |
| type                | None                                 |
| updated_at          | None                                 |
| user_id             | e2252ff04be3409e8e823a0a3a925cad     |
+---------------------+--------------------------------------+

[cent@dlp ~(keystone)]$
openstack volume list

+--------------------------------------+--------+-----------+------+-------------+
| ID                                   | Name   | Status    | Size | Attached to |
+--------------------------------------+--------+-----------+------+-------------+
| 6f1a946b-5dfc-403a-9545-5516670f2abe | disk01 | available |   10 |             |
+--------------------------------------+--------+-----------+------+-------------+
[6] Attach the virtual disk to an Instance.
For the exmaple below, the disk is connected as [/dev/vdb]. It's possible to use it as a storage to create a file system on it.
[cent@dlp ~(keystone)]$
openstack server list

+--------------------------------------+----------+---------+-----------------------------------+---------+----------+
| ID                                   | Name     | Status  | Networks                          | Image   | Flavor   |
+--------------------------------------+----------+---------+-----------------------------------+---------+----------+
| 5b30f928-8834-4ab5-a5ce-760c48d4c9b7 | CentOS_7 | SHUTOFF | int_net=192.168.100.3, 10.0.0.220 | CentOS7 | m1.small |
+--------------------------------------+----------+---------+-----------------------------------+---------+----------+

[cent@dlp ~(keystone)]$
openstack server add volume CentOS_7 disk01
# the status of attached disk turns [in-use] like follows

[cent@dlp ~(keystone)]$
openstack volume list

+--------------------------------------+--------+--------+------+-----------------------------------+
| ID                                   | Name   | Status | Size | Attached to                       |
+--------------------------------------+--------+--------+------+-----------------------------------+
| 6f1a946b-5dfc-403a-9545-5516670f2abe | disk01 | in-use |   10 | Attached to CentOS_7 on /dev/vdb  |
+--------------------------------------+--------+--------+------+-----------------------------------+

# detach the disk

[cent@dlp ~(keystone)]$
openstack server remove volume CentOS_7 disk01

Matched Content
 
Tweet