We currently indicate in the JON documentation that a minimum of 10 GB of storage is required for the operation of JON Server. This section should also note that if user disk quotas are enforced, the user needs at minimum 10 GB. I am not sure how we want to do this because it would appear the JON server may rely on temporary space outside of its installation. Meaning that on a system that has a separate partition and disk quota for temporary files, this temp space must be taking into consideration.
We may want to break this up into the storage space required for the JON server's installation directory and storage space required for temporary files and artifacts while the JON server is running.
The goal here is to prevent the user from getting into a situation where we may be writing to a file system location that is under a different quota rule or has a partition size smaller then what we will need. For example, if we are writing to /tmp in some instances, and the /tmp partition is only 6 GB, at what point will JON server start to fail?
In addition, we currently provide a "minimum" requirement and a "maximum" requirement. Is this really ideal? Can we guarantee that we will never exceed 40 GB? For example, if the user modified the log4j configuration of the server and sets the max log file size to 1 GB and states that they want to retain the last 10 log files, we would be at 10 GB as a minimum.
I meant to include a link to the requirements from the JON 2.4 documentation: http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/2.4/html/Installation_Guide/Prerequisites.html#hardware
Bulk closing of BZs that have no target version set, but which are ON_QA for more than a year and thus are in production for a long time.