On 01/10/2013 01:01 PM, Michael K. Johnson wrote:
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.)
Where does fdev live? In your office, doubling as you office graphical
FL devel system?
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.
What does "please don't use this system for general work" imply from
your perspective? I realize that this probably overlaps with your
answer to eMBee, but I figured it wouldn't hurt asking. =)
If I were to attempt to recap what you have mentioned so far, then I
would think that you intend for fdev to be for shell use and for doing
local test builds with cvc cook --prep; cvc cook, but not for rmake
builds, and not for testing stuff in the general sense.
rmake.foresightlinux.org is the new head node for the rmake build
cluster and should be used only for rmake jobs. It shouldn't be used for
cvc cook at all, and shouldn't be used for IRC shell shell session nor
testing in the general sense either.
A couple of extra questions:
* Do fdev and the rmake head server share home folders and account
(login) data?
* What kind of delay am I looking at if I do a 'cvc ci' from fdev and I
then do a 'cvc log' on the rmake head node? Is it instant-ish? ISTR
remember there being a slight delay on the previous infra, having to do
with ... mirroring or something along those lines?
* Re. your remarks on having a local development system: How easy is it
to set up a "trove cache" (don't know if there is an official term for
it) for use with my local rmake builds? ISTR to remember that having to
fetch and re-fetch the same troves on my devel box was a pretty major
stumbling block in terms of productivity. IIRC, António mentioned how
to set up said cache, but I don't think I ever got it to work
correctly. Being able to do something like "conary install
rmake-cache", which would automatically install the correct cache
configuration, would be sort of neat -- not to mention pretty useful --
for those of us working on FL from overseas...
-Rune
_______________________________________________
Foresight-devel mailing list
[email protected]
https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
