-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El Wed, 23 Oct 2013 14:04:29 +0200 "Sandro \"red\" Mathys" <red@xxxxxxxxxxxxxxxxx> escribió: > On Wed, Oct 23, 2013 at 1:17 PM, Matthew Miller > <mattdm@xxxxxxxxxxxxxxxxx> wrote: > > On Wed, Oct 23, 2013 at 12:38:40PM +0200, Sandro red Mathys wrote: > >> Now trying to launch the image as such (the m1.tiny flavor happens > >> to come with a 1 GB root disk by default in OpenStack Havana), it > >> will always fail. > >> > >> Therefore, I propose to change the partition size to 1024MB > >> instead of 2048MB. Or even to just 600MB but clouds specify the > >> root disk size in GBs rather than MBs anyway, and 600MB might > >> limit further development stronger than really necessary. > > > > I *think* it will install into a partition size that big -- I'll > > try. The problem is that just doing a 'yum update' tends to fill > > the remaining space very quickly, making a 1GB image questionable > > in pratical use right now. > > [root@f20 ~]# df -h | grep vda > /dev/vda1 9.9G 574M 9.3G 6% / > [root@f20 ~]# yum update -y &> /dev/null > [root@f20 ~]# df -h | grep vda > /dev/vda1 9.9G 922M 8.9G 10% / > [root@f20 ~]# yum clean all &> /dev/null > [root@f20 ~]# df -h | grep vda > /dev/vda1 9.9G 767M 9.1G 8% / > > Okay, I guess that's valid concerns. The 1GB limit is within reach > during an update. Still, for quick testing purposes, etc. 1GB > instances are often spun up and for cases where that's not enough > people can still start the instance with a bigger root disk and have > it auto-resized. > > Also, an install size of nearly 600MB feels kinda huge. I mean the > LiveCDs are (or used to be) <=700MB and had full desktop environments > running. Live cds never had a <= 700MB size, they have always used compression and been at least 2GB Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJSa9rXAAoJEH7ltONmPFDRPtkP/2eiHZ49ZaoUAa3yuVEIo0Jy 1Pvs/mWvSgukCAGcrmAEQXgp2p32CRj1F0dyJaKxiGFJ0stdzOtNXlxkT6iLIOKI RGNWljl+9RMBZQW7/sDg6LZ9YE7mjCKokAud+Q7l2lFlcdsww4NPX7JhoK1bvOmZ mVwhdxTi8bG5MyKZpHerPl7BkYQ+mJ36qUVFbyxaROiSl7zJ40ZJkVWE8M1Qii6t PkXjCtriXVGj47VDhIT43ok670N54u+AEFXnkQ/D182oK0HnuqiX8n//S7yzLpMJ AeASGsycfo0ocW7RcbJvmetxR0Dhm28hu5vBkItioQc9Dt53E8PaSz/CG1opJ9Y7 GhDE7xziWYrnbrEm0xKLmqbR4q40d1L1+3nt7rlUzeta73uylBqw6XE5ioXU3J2+ Rakfpb4NAXBmgGKVJOvhbcOeIzvfqwRJB2fn9CYIkG6o9qVwMmKP7CShySraeMcI ge2FuENeIRpWdve1MLJJz95YpwOsMnj5PDr3HkVmFwIYXKGMzIJ5EQJ+QjAUMRbU NylWb2NAL50AZSPLomijUpKuw0iX1JQM4axmtaPox9LVjh774MtlhLmH8QpyoAW4 lKD7CqdZAsNhYjXxerIDV5wXl3/nadEIo/1x1JCDbPpaeNv6sNEqXETDUlfc92D8 l2qdaBAojRtc+8SYBAPL =eD7C -----END PGP SIGNATURE----- _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
