On Fri, Jan 11, 2013 at 01:43:15AM +0100, Rune Morling wrote: > Where does fdev live? In your office, doubling as you office graphical FL > devel system?
That would be painful! No, they are virtual instances running on a cluster. If you're asking about the old fdev machine, it's going to live in a quietly anonymous location sucking down backups, just in case. :) (Right now it's waiting for me to set that up.) > 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. =) It means that the only normal use for the rmake.foresightlinux.org machine should be running rmake jobs. (There's one exception; I also run on it the script that mirrors from the commits repository to the public repository.) On fdev.foresightlinux.org, you can run screen/byobu sessions, irssi, git, mercurial, small local (not repository) builds, and so forth. > 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. Exactly. Your shell sessions shouldn't be bogged down by big build jobs, and your local cooks shouldn't slow down rmake. > A couple of extra questions: > > * Do fdev and the rmake head server share home folders and account (login) > data? At least right now, yes. > * 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? If you do it in the same directory, in the same context, then you won't see any delay, because you'll be pointing at the -commits repository, and so you won't have to wait for mirror. The delay you are thinking of is relative to when it shows up for public consumption, which is after it is mirrored. A mirror job is kicked off every minute, as long as there isn't already a job running. > * 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... I think you want a caching conary proxy. It's much easier now: conary install conary-proxy service memcached restart service httpd restart It's not just useful overseas. I have a caching proxy for my home machines. I run one on my laptop where I also build lots of images. It will also work for system updates, and if you have multiple machines, you can run the cache on one machine and point the rest of the machines at it with conary configuration. Just create a file, call it /etc/conary/config.d/proxyMap on each of the systems that says: proxyMap * conary://proxymachinename/conary/ That tells conary to use application-level proxy (the caching proxy) for all conary requests for all repositories. /etc/cron.daily/conary-proxy by default deletes things that have not been accessed for about a month. That's probably good enough for almost everyone... _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
