On Saturday, March 30, 2013, 12:38:21 AM, Pete Travis wrote: > If the only way to come up with the official figures is for me to test > installations myself, so be it. I have access to enough old hardware > to come up with reasonable results, and spinning up kickstarted > installations that would iterate through reducing values of "mem=NNNm" > would probably give results in short order. > I do recall reading the postings you mention, but I'm reluctant to > recommend that kind of deployment to our users. I am making a > distinction between minimal and recommended requirements, and while > the former would be relatively easy to figure out, the recommended > figure is more subjective. > If I have to come up with the numbers myself, I'll probably skip all > that and simply recommend, say, a dual core >1GHz CPU with at least > 1.5GB of ram and 20GB of available disk space; that seems like a > reasonable baseline. I don't want to set an expectation of support > without input from the developers of the product that I'm documenting, > so I'm writing here for guidance. > --Pete I would suggest that the KVM folks would view your suggested baseline with a very real sense of outrage. As a Fedora user with a mix of older hardware and new, I am uncomfortable with a casual approach to either minimum or recommended resource values. For real hardware, it is important that Fedora be successfully able to install in older hardware running a previous Fedora release. This ensures that folks are able to continue to run Fedora, but in a secure and supported manner. Overstating the installation requirements tends to discourage folks from upgrading (so they run insecure code), or can force them to move to a different distribution for _NO_GOOD_REASON_. It has the secondary effect that little or no effort is made (at the development or test stages) to ensure that the install runs with minimal resources. Assuming too high a resource requirement becomes a self fulfilling problem. For virtual machines, there has been much discussion in the main development list over the last year regarding working towards an absolute minimalist installation and runtime requirement. For the case where many virtual instances are required to coexist on the same host, small differences make enormous differences in the final totals. I would strongly advise against an overly simplistic approach. In the end, it benefits no one. Bring the development community into the discussion, and come up with reasonable classes of systems to be installed and operated as well as realistic final values for each class. Anaconda development should have the ability (and resources) to perform instrumented installations to measure and really understand what factors contribute to the overall resource requirements. This will help with a goal of reducing (or at absolute minimum stabilizing) these resource requirements. Al _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
