OpenStack Victoria : Use Cinder Storage (LVM)2021/03/24 |
|
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 | | Neutron Server | | Nova Compute |
| Keystone Glance | | OVN-Northd | | Open vSwitch |
| Nova API | | Cinder Volume | | OVN Metadata Agent |
| Cinder API | | iSCSI Target | | OVN-Controller |
+-----------------------+ +-----------------------+ +-----------------------+
|
| [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 systemctl restart openstack-cinder-volume |
| [3] | On Storage Node, If Firewalld is running, allow service ports. |
|
[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
# if SELinux enabled, change policy like follows
[root@node01 ~]#
vi iscsiadm.te # create new
module iscsiadm 1.0;
require {
type iscsid_t;
class capability dac_override;
}
#============= iscsid_t ==============
allow iscsid_t self:capability dac_override;
checkmodule -m -M -o iscsiadm.mod iscsiadm.te [root@node01 ~]# semodule_package --outfile iscsiadm.pp --module iscsiadm.mod [root@node01 ~]# semodule -i iscsiadm.pp |
| [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. (example below is on Control Node) |
|
# set environment variable [cent@dlp ~(keystone)]$ echo "export OS_VOLUME_API_VERSION=3" >> ~/keystonerc [cent@dlp ~(keystone)]$ source ~/keystonerc
openstack volume create --size 10 disk01 +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | attachments | [] | | availability_zone | nova | | bootable | false | | consistencygroup_id | None | | created_at | 2021-03-24T05:24:45.000000 | | description | None | | encrypted | False | | id | 4cb0cd28-3c3e-465b-bbb6-2d87f7b0a694 | | multiattach | False | | name | disk01 | | properties | | | replication_status | None | | size | 10 | | snapshot_id | None | | source_volid | None | | status | creating | | type | __DEFAULT__ | | updated_at | None | | user_id | e08c35de3b6746bd9518c97f7068a71e | +---------------------+--------------------------------------+[cent@dlp ~(keystone)]$ openstack volume list +--------------------------------------+--------+-----------+------+-------------+ | ID | Name | Status | Size | Attached to | +--------------------------------------+--------+-----------+------+-------------+ | 4cb0cd28-3c3e-465b-bbb6-2d87f7b0a694 | disk01 | available | 10 | | +--------------------------------------+--------+-----------+------+-------------+ |
| [6] | Attach the virtual disk to an Instance. For the example 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 | +--------------------------------------+-------------+---------+------------------------------------+-----------------+----------+ | da1c8adc-4733-4ee5-a654-49d652a6aaa3 | CentOS-St-8 | SHUTOFF | private=192.168.100.63, 10.0.0.253 | CentOS-Stream-8 | m1.small | +--------------------------------------+-------------+---------+------------------------------------+-----------------+----------+
[cent@dlp ~(keystone)]$
openstack server add volume CentOS-St-8 disk01
# the status of attached disk turns [in-use] like follows [cent@dlp ~(keystone)]$ openstack volume list +--------------------------------------+--------+--------+------+--------------------------------------+ | ID | Name | Status | Size | Attached to | +--------------------------------------+--------+--------+------+--------------------------------------+ | 4cb0cd28-3c3e-465b-bbb6-2d87f7b0a694 | disk01 | in-use | 10 | Attached to CentOS-St-8 on /dev/vdb | +--------------------------------------+--------+--------+------+--------------------------------------+ # detach the disk [cent@dlp ~(keystone)]$ openstack server remove volume CentOS-St-8 disk01 |
| Sponsored Link |
|
|