On Tue, Apr 2, 2013 at 4:24 PM, Adam Williamson <awilliam@xxxxxxxxxx> wrote:
Yeah, that's *way* more work than I think the cause merits. We don't exactly have hardware vendors scrambling to pay for certification stickers :)Well, half the time the number in anaconda doesn't get touched unless someone bugs the anaconda team about it, so...On 02/04/13 01:28 PM, "Jóhann B. Guðmundsson" wrote:
Anaconda set's the minimal hw requirements so you should check what's
their today's requirement to function properly
It's a really squishy area to try and deal with, though, honestly. I'm not entirely sure validating HW requirements as part of QA is realistic, because I mean, what if we pick 'mail/web server' as one of the roles? Do we have to set up a kickstart that builds out a running postfix/dovecot/apache/wordpress machine and run it for a couple of weeks and see what resource use is like? It seems a bit impractical. What we can do - and do do at present, though it isn't written in stone anywhere - is check that install is possible with various package sets with various amounts of RAM right around the current anaconda 'hard floor', but trying to determine the minimum resources for various 'real world scenarios' seems like it might be quite a lot of thankless work...
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
I was hoping you guys were already collecting information, or that a datapoint could be added to existing tests. Identifying things like the memory required to complete a default installation, or the base graphics hardware required to run gnome-shell without mashing the keyboard in frustration and moving to another distro, or a recommended figure for available storage using the default packageset and a comfortable amount of room.
I *really* want to stay away from absolute 'minimum' guidelines. Those with the skills to set a system up with comically low resources are not the target audience - we want to set reasonable expectations for the desktop user, and guidelines for other use cases. We can steer towards a lighter spin for machines with low resources, for example, or boast about the node size we can use in the cloud.
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize at fedoraproject.org
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
