1. Pacman in a Nutshell Saul Youssef Boston University

2. Pacman lets you define how a mixed tarball/rpm/gpt/native software environment is Fetched Installed Setup Updated my_environment.pacman This can be figured out once and exported to the rest of the world via caches. % pacman –get my_environment

3. A Cache Python.pacman Cernlib.pacman Condor.pacman VRVS.pacman An XXX.pacman file contains instructions for how to fetch and install software, not necessarily the software itself.

4. This is a problem where the grid really helps Boston BNL LBNL ANLIndiana UT Arlington U.Michigan We can share the pain

5. Pacman 2.0 has dependent installations too Boston BNL LBNL ANL Indiana UT Arlington U.Michigan VDT /usr/local/bin

7. The caches you have decided to trust Installed software, pointer to local documentation Dependencies are automatically resolved

8. nedit is native Dependent installation refers to another root created Pacman installation This one is another local installation which serves as a virtual cache Tells you if an update is available

9. Root has installed some grid software…

10. Given this, a non-root user then does the single command % pacman –get atlas_testbed And this results in a complete installation as follows…

11. This is the root package with dependencies resolved from the list of real & virtual caches and natively installed software.

12. Unusual use of packages may be very useful How to save a software environment for 5 years. % pacman –fetch –no_native atlas_production Atlas_grid_certificate.pacman Atlas_production_gridmap.pacman 50Gig.pacman RedHat7.2.pacman OpenSSH.pacman

13. It seems to me that non-traditional packages will be useful, e.g. pacman –get DOE-certificate Advantages are the same as for software: One person can maintain DOE-certificate.pacman so that it always points to the right documentation and always does the right thing. Instructions automatically come up at the time when they are needed. We can update the procedure for doing this globally with a minimum of fuss and confusion. Convenient way to guarantee a standard certificate for the outside world.

14. pacman –get Atlas-testbed-gridmap Similarly… Many of us got the following email recently…

15. As was previously announced, support for Ssh Protocol 1 has been disabled at the RCF and US Atlas Computing Facilities. Access to these facilities is now only allowed with Ssh Protocol 2. Users who have not upgraded to an Ssh Protocol 2 capable client will need to upgrade in order to access the facilities. Information on Ssh Protocol 2 capable clients is available from the Ssh FAQ. http://www.employees.org/~satch/ssh/faq/ssh-faq.html Shigeki Misawa (misawa@bnl.gov) -- This message forwarded from the RCF announcements page. Recent messages are available at: http://www.rhic.bnl.gov/RCF/Announcements/announce.html _______________________________________________ Usatlas-users-l mailing list Usatlas-users-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/usatlas-users-l OpenSSH-protocol2.pacman

16. We are inches away from CMT RPM Pacman Cache This would let us define a complete Atlas/Grid/3d-party environment which can be reproduced with one command. source = ‘http://physics.bu.edu/~youssef/cmt/’ systems = {‘*’:[‘cmt0.rpm’,’’]} depends = [‘cmt1’,’cmt2’,’cmt3’] cmt0.pacman: % pacman –get cmt0 Pacman globus2 Python

17. Pacman was originally developed at Boston University. Further development and support of Pacman is jointly with Alain Roy and the Condor Team at University of Wisconson. To get started, go to http://physics.bu.edu/~youssef/pacmanhttp://physics.bu.edu/~youssef/pacman Pacman has successfully been used at BU, ANL, BNL, LBNL, Indiana U. U.Michigan, U.Texas/Arlington, U.Oklahoma and U.Wisconson. For sample caches related to Atlas, see http://atlasgrid.bu.edu/atlasgrid/atlas/atlas_cache/cache.html This includes Jason Smith’s cache containing Globus2 distributed using rpms. The GriPhyN/iVDGL VDT toolkit is distributed using Pacman, see http://www.lsc-group.phys.uwm.edu/vdt/