-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22/01/16 12:14, Karanbir Singh wrote: > On 22/01/16 10:53, Niels de Vos wrote: >> We would like to have raw block devices for Gluster testing too. >> Gluster can do snapshots based on lvm-thinp, and we recommend to >> use a dedicated Volume Group for each brick. Our tests can use >> files over /dev/loop* devices, but that is not how things should >> be used for real world setups. > > The way to resolve that would be to request the instances from > Duffy, and then reprovision as needed. that way you own the timelag > and process to provision the box ( we can help, ofcourse ). Rather > than needing a systemside / system-wide change in the base layer. That's also a possibility, but not sure that all projects willing to have more disk space would like to reinstall each node given by Duffy either > >> Not sure about the iscsi suggestion, a network filesystem over >> network block devices is not very common either ;-) > > ofcourse, that depends on what you are testing. If perf becomes a > thing, then you certainly dont want to go down that route. > Yes, and it's also a CI/Test environment, so while it makes sense to try to be as close as possible as what would be done in ideal/real life scenario, it's not always possible. As a summary : - - we can try to bring iscsi targets into the mix, but : - gbit connected - storage node behind itself having not infinite storage space (there are more spaces with the local SSD disks from the provisioned nodes) - - we can change the kickstart files to *not* --grow, and let every project create LVs in the VG as they need/want. As there would be less projects willing that, we can implement in Duffy an extra step (as discussed for the VLAN segregation discussion) to expand/resize by default, and let it in the provisioned state when duffy api is called with an extra parameter ) - - projects can also raw files as block devices on the underlying/existing FS, and setup new VG/LV as needed too (with a performance impact, but still probably faster than using iscsi devices) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlaiGMAACgkQnVkHo1a+xU7FTwCdG8oXnz0cQuDznm/ksNnKsIlg iJ4AoIMZRnI1HADR5MU1eKFfic2eBDu/ =fBuV -----END PGP SIGNATURE-----