[Ci-users] Disk space on ci nodes

[Karanbir Singh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 22/01/16 11:55, Fabian Arrotin wrote:
> 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

- From the provider side - we need an interface to make it possible, and
we already have all the mechanics for it. So should be fairly simple
to expose to the jenkins slaves.

> 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.

no!

the main value prop from ci.centos.org is VERY much to focus on user
space and real world testing, hence the baremetal and no pre-existing
setups on the machines.

regards

- -- 
Karanbir Singh, Project Lead, The CentOS Project
+44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS
GnuPG Key : http://www.karan.org/publickey.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWoiHTAAoJEI3Oi2Mx7xbtMsMH/RqyFWSh852e79da463P7VK8
6ZHwzxwGA2d6e094xxwhTt/cdRGB8zenkDb9Q5jujZVUbUNSAMEVt+Nak4Jsy4yM
mv7dPLoatoLW1P/sSiImBcw38/RFLnRXbDbsUvM5E0IQ6qop+4UPu2ULpT8PxWm5
xXKUwyWUBtXVlthERsdkJKxdDiprhMdb8ehYihCMS6WugI1AW7D5XKaiaoY04SuT
UuCdszAwQA4iIWVkC3Tjwgb9bd8ze/qgzBa3U+0CbainEAg9HLRNZKcIhhazHxtD
xaFKamwQ5ebsQF8xVAVYnCJTrdaYMcm9Db+73CKALQZsCxqgQBOQSy4JCzp4Oto=
=gUQr
-----END PGP SIGNATURE-----