In the old infrastructure, fdev.foresightlinux.org did lots of things. It was the foresight-commits repository front end, the web proxy for jira and confluence, the rmake head node, the system to launch rmake jobs from, the external DNS master, and a general shell server.
A lot of work for a single-socket, 4-core, 8GB system. It did remarkably well, but sometimes was a little slow when we asked it to do too much. In the new infrastructure, fdev.foresightlinux.org is a full GNOME development system with recent FL installed. It is not a web server, rmake front end, or DNS master. It is for running shell sessions (for example, feel free to run IRC in shell on fdev if you prefer) and doing local test builds in your home directory (cvc cook --prep, cvc cook) against the installed GNOME development environment. It is not connected to the rmake build cluster. (I apologize for the confusion when developers logged into it and wondered why rmake was not working.) In the new cluster, we have rmake.foresightlinux.org that is the rmake head node and the shell system from which to launch rmake jobs. Don't do local builds on it. It is currently connected to two build nodes, each of which has two slots; a third similar node will be added in the next few weeks after we finish some more infrastructure work. Please don't use this system for general work. The occasional "cvc cook --prep" is fine, but we don't want to bog down rmake. I (temporarily) updated the motd on each system with a reminder. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
