Unfortuntely, I have already passed lab for another tasks, and I can't deploy there environment to reproduce bug.
I had environment with 2 hardware servers as nodes and Fuel on VM. Each node has 2 hard disks, labeled sda and sdb.
Partition for disk on compute node setted as virtual storage on sda and cinder on sdb.
After deployment, I made following steps:
glance image-create --name "disk_io_perf" $opts --copy-from "https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img"
nova flavor-create "disk_io_perf.256" "disk_io_perf.256" "256" "20" "1"
nova keypair-add "disk_io_perf" > "disk_io_perf.pem"
cinder create --display-name test-volume 20
Get vol_id from output
nova boot --flavor "disk_io_perf.256" --image "disk_io_perf" --key-name "disk_io_perf" --security-groups default --nic net-id=novanetwork disk-test
nova volume-attach disk-test VOL_ID /dev/vdb
After this commands in Fuel UI on page "Configure disks" I see 3 disks, new one labeled sdc and contains virtual srorage.
Unfortuntely, I have already passed lab for another tasks, and I can't deploy there environment to reproduce bug. /cloud- images. ubuntu. com/trusty/ current/ trusty- server- cloudimg- amd64-disk1. img"
I had environment with 2 hardware servers as nodes and Fuel on VM. Each node has 2 hard disks, labeled sda and sdb.
Partition for disk on compute node setted as virtual storage on sda and cinder on sdb.
After deployment, I made following steps:
glance image-create --name "disk_io_perf" $opts --copy-from "https:/
nova flavor-create "disk_io_perf.256" "disk_io_perf.256" "256" "20" "1"
nova keypair-add "disk_io_perf" > "disk_io_perf.pem"
cinder create --display-name test-volume 20
Get vol_id from output
nova boot --flavor "disk_io_perf.256" --image "disk_io_perf" --key-name "disk_io_perf" --security-groups default --nic net-id=novanetwork disk-test
nova volume-attach disk-test VOL_ID /dev/vdb
After this commands in Fuel UI on page "Configure disks" I see 3 disks, new one labeled sdc and contains virtual srorage.