Your SlideShare is downloading. ×
 glideinWMS Frontend Installation - Part 2 - Frontend Installation -glideinWMS Training Jan 2012
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

glideinWMS Frontend Installation - Part 2 - Frontend Installation -glideinWMS Training Jan 2012

823
views

Published on

Instructions on how to install the Frontend part of a glideinWMS system. …

Instructions on how to install the Frontend part of a glideinWMS system.
Part of the glideinWMS Training session held in Jan 2012 at UCSD.

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
823
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. glideinWMS Training @ UCSD glideinWMS Frontend Installation Part 2 – Frontend Installation by Igor Sfiligoi (UCSD)UCSD Jan 18th 2012 Frontend Install 1
  • 2. Overview ● Introduction ● Planning and System setup ● Prerequisites ● Actual Frontend InstallationUCSD Jan 18th 2012 Frontend Install 2
  • 3. Refresher - Glideins ● A glidein is just a properly configured Condor execution node submitted as a Grid job ● glideinWMS Central manager provides glidein Execution node Collector CREAM automation glidein Execution node Negotiator Submit node Submit node glidein Execution node Submit node Execution node glidein Schedd Startd Globus Job glideinWMSUCSD Jan 18th 2012 Frontend Install 3
  • 4. Refresher – VO Frontend ● The frontend monitors the user Condor pool, does the matchmaking and requests glideins ● Factory a slave Configure Condor G.N. Submit node Frontend node Worker node Monitor Submit node Frontend Condor glidein Central manager Startd Match Globus Job Request glideins Factory node Condor glidein Execution node CREAM Factory glidein Execution node Submit glideinsUCSD Jan 18th 2012 Frontend Install 4
  • 5. Refresher - glidein_startup ● Glidein startup script mostly an empty shell ● Real code and config files downloaded ● From both Factory and Frontend Web servers Factory node glidein_startup HTTPd ● Load files Squid from factory Web ● Load files from frontend Web Frontend node ● Run executables ● Start Condor Startd HTTPd ● Cleanup Nothing will work if HTTPd not runningUCSD Jan 18th 2012 Frontend Install 5
  • 6. Refresher - Cardinality ● N-to-M relationship ● Each Frontend can talk to many Factories ● Each Factory may serve many Frontends VO Frontend VO Frontend Glidein Factory Collector Schedd Negotiator Collector Startd Startd Schedd User job User job Negotiator Startd Glidein Factory User jobUCSD Jan 18th 2012 Frontend Install 6
  • 7. Refresher - Matchmaking ● The glideinWMS triggers glidein submission ● The “regular” negotiator matches jobs to glideins Central manager glidein Execution node Collector CREAM glidein Execution node Negotiator Submit node Submit node glidein Execution node Submit node Execution node glidein Schedd Startd Globus Job glideinWMSUCSD Jan 18th 2012 Frontend Install 7
  • 8. Refresher – Security Handles ● Mutual authentication with Factory ● Frontend provides (and Factory whitelists) One set ● Service Proxy to talk to Factory Collector for whole ● Frontend Security name Frontend (all Groups) ● Pilot Proxy Can have many such pairs ● Proxy Security Class ● Frontend whitelists (obtained from Factory admins) ● Factory Collector DN ● Own mapping @Factory One set per factory collector ● Factory mapping @FactoryUCSD Jan 18th 2012 Frontend Install 8
  • 9. A word about monitoring ● The frontend keeps historical stats for monitoring purposes ● Storage based on Round Robin Databases rrdtool - http://oss.oetiker.ch/rrdtool/ ● Web interface to RRDs also provided ● No server side code ● Fully client side rendering in Javascript JavascriptRRD - http://javascriptrrd.sourceforge.net/UCSD Jan 18th 2012 Frontend Install 9
  • 10. Planning and System setupUCSD Jan 18th 2012 Frontend Install 10
  • 11. It is a big world ● Many pieces, Frontend processes just a part ● Condor Submit node Frontend node ● Web Server Monitor Submit node Condor ● Factory Frontend Match Central manager ● The Grid Web Server Request glideins ● Must play nicely Fetch Factory node files with all of them Condor Factory glidein Submit glideinsUCSD Jan 18th 2012 Frontend Install 11
  • 12. Condor You should have Condor installed by now! See yesterdays talk(s)UCSD Jan 18th 2012 Frontend Install 12
  • 13. Planning ● Frontend can be installed on its own node ● Or shared with other services ● Avoid nodes where many users log into ● For security reasons ● Will hold the pilot cert(s) ● Condor Central Manager a good companion ● If it has enough Hardware for both Experience: CMS has been switching between dedicated node and co-locating with CM as the pool grew and HW got replacedUCSD Jan 18th 2012 Frontend Install 13
  • 14. Hardware requirements ● The CPU and Memory resources scale with the Condor use, both Actual memory usage depends on attributes used for matchmaking ● Jobs in the queue O(1k)-O(100k) ● Glideins registered with the VO Collector ● Each Frontend group spawns 5 processes ● So useful to have multiple CPUs ● Minimal IO useUCSD Jan 18th 2012 Frontend Install 14
  • 15. Components requiring root ● The Frontend processes do not need root privileges ● And can be installed fully as non-root ● However, a few components are easier to install as root Will thus use ● The (OSG) Grid Client & CAs this method in this talk ● The Web server ● rrdtool python libraries Not my favorite, but will shortly ● Frontend RPM also available describe it toward the endUCSD Jan 18th 2012 Frontend Install 15
  • 16. OSG Grid Client ● Requires RHEL5-compatible Linux Pacman based VDT could be ● RHEL6 support promised for early 2012 installed as non-root but now deprecated ● Procedure in a nutshell ● Add EPEL and OSG RPM repositories to sys conf. ● yum install osg-ca-certs ● yum install osg-client Other Grid clients ● Enable CRL fetching crontab (e.g. EGI/glite) will work just as wellhttps://twiki.grid.iu.edu/bin/view/Documentation/Release3/InstallOSGClientUCSD Jan 18th 2012 Frontend Install 16
  • 17. Web server ● Any Web server will do ## install the web server install the web server ● Serving just static files yum remove -y httpd yum remove -y httpd cd glideinWMS/install/ ● The glideinWMS provided cd glideinWMS/install/ ## Q&A installer in batch mode Q&A installer in batch mode installer will clean up the config ./glideinWMS_install << EOF 88 ./glideinWMS_install << EOF cc ● Will use system 80 Port to use 80 yum install 11 EOF EOF ● But get rid of any eventual old httpd beforehand ● Create a directory owned by the frontend user ● /var/www/html/vofrontendUCSD Jan 18th 2012 Frontend Install 17
  • 18. RRDTool ● The Frontend is a python script ● Thus needs the RRDTool python libraries ● Easiest way is getting them from EPEL ● Which you already have if using the OSG Client % yum install rrdtool-python % yum install rrdtool-pythonUCSD Jan 18th 2012 Frontend Install 18
  • 19. PrerequisitesUCSD Jan 18th 2012 Frontend Install 19
  • 20. Before you begin ● Before you start the actual installation, you need a few things: Assuming “frontend” ● Decide what UID will you be using in this talk ● A host/service certificate for the Frontend ● One or more pilot certificates – And they must be registered with your VOMS ● Decide on the Security Name for your Frontend ● Find a Factory to support you Hint: The OSG glidein factoryUCSD Jan 18th 2012 Frontend Install 20
  • 21. Frontend certificate ● OSG provides a script to talk to DOEGrids https://twiki.grid.iu.edu/bin/view/Documentation/Release3/GetHostServiceCertificates#Request_a_Service_Certificate ● Unfortunately, must be run as root ● Procedure in a nutshell ● Install OSG client Ask for the “VOfrontend” ● yum install osg-cert-scripts service ● cert-request … ● Wait for email ● cert-retrieve … If you have other ways ● cp into ~frontend/.globus/ to obtain a service cert, feel free to use them ● chown to frontend:frontendUCSD Jan 18th 2012 Frontend Install 21
  • 22. Pilot certificate(s) ● Just another type of service certificate Try to make it ● Use service name VOpilotXX Globally Unique ● Follow instructions on previous slide ● Then register it with your VOMS If you decide to use multiple pilot certificates Each VO uses a slightly different with different privileges you may want procedure, so I am not going to to describe this step pick multiple security class names for added security (default is “frontend”)UCSD Jan 18th 2012 Frontend Install 22
  • 23. The Security Name ● The Frontend Security Name is a Globally Unique name your Frontend will use to securely communicate with the Factories ● A good pick is “VOsomething” ● This may or may not be the same as the Frontend Name ● Which also must be Globally Unique ● and is used as a ClassAd Name ● The Frontend name often contains a version string; Security name does/must notUCSD Jan 18th 2012 Frontend Install 23
  • 24. Contact the factory admins ● You will need a Factory to submit glideins ● While the Factory is a slave to the Frontend ● It chooses its masters! ● To use the OSG glidein factory, send an email to osg-gfactory-support@physics.ucsd.edu ● You will need to provide ● Frontend certificate DN And you will get back the factory information ● Security name you need during the installation http://hepuser.ucsd.edu/twiki2/bin/view/UCSDTier2/OSGgfactoryUCSD Jan 18th 2012 Frontend Install 24
  • 25. Frontend InstallationUCSD Jan 18th 2012 Frontend Install 25
  • 26. Frontend Installation ● Now you should have all the pieces to start the installation I assume you already have the glideinWMS ● In a nutshell “binaries” http://tinyurl.com/glideinWMS ● Automate proxy creation ● Get access to a Condor client ● Get JavascriptRRD tarball and extract it http://sourceforge.net/projects/javascriptrrd/ ● Create Frontend config file Get the latest one with flot and tooltip ● Instantiate the Frontend ● Start the Frontend All as a regular user (e.g. “frontend”)UCSD Jan 18th 2012 Frontend Install 26
  • 27. Proxies vs certs ● In the previous slides, you were told to obtain a service and pilot certificates ● But the Frontend needs proxies! ● You must convert certs into proxies ● Proxies are short lived Must be longer ● Should be hours for the service proxy than the glidein lifetime (and ● A few days for the pilot proxy no less than 12h) ● You must keep them valid at all times ● With a cron script (or equivalent)UCSD Jan 18th 2012 Frontend Install 27
  • 28. Example cron script ● Really just voms-proxy-init #!/bin/bash #!/bin/bash home=/home/frontend/.globus home=/home/frontend/.globus umask 0077 umask 0077 idstr=service idstr=service export X509_USER_PROXY=${home}/x509_$idstr.proxy export X509_USER_PROXY=${home}/x509_$idstr.proxy voms-proxy-init -cert ${home}/${idstr}cert.pem -key ${home}/${idstr}key.pem voms-proxy-init -cert ${home}/${idstr}cert.pem -key ${home}/${idstr}key.pem -hours 12 -valid 12:0 -hours 12 -valid 12:0 idstr=vopilot01 idstr=vopilot01 export X509_USER_PROXY=${home}/x509_$idstr.proxy export X509_USER_PROXY=${home}/x509_$idstr.proxy voms-proxy-init -cert ${home}/${idstr}cert.pem -key ${home}/${idstr}key.pem voms-proxy-init -cert ${home}/${idstr}cert.pem -key ${home}/${idstr}key.pem -voms VO:/VO/role=pilot -hours 72 -valid 72:0 -voms VO:/VO/role=pilot -hours 72 -valid 72:0 ● Then add it to crontab ## crontab -l crontab -l 31 3,9,15,21 * * ** * /home/frontend/.globus/refresh_proxy.sh>/dev/null 2>/dev/null 31 3,9,15,21 * /home/frontend/.globus/refresh_proxy.sh >/dev/null 2>/dev/nullUCSD Jan 18th 2012 Frontend Install 28
  • 29. The Condor client ● The Frontend uses the Condor client cmdline tools to talk to both the rest of the VO Condor daemons and to the Factory(s) ● Just the binaries ● Unless you host the Frontend on a submit node (which is not recommended) you will need to install a private version of Condor binaries ● Properly configuring it will make it usable for debugging, tooUCSD Jan 18th 2012 Frontend Install 29
  • 30. Installing the Condor client ● As usual, using the provided installer the easiest way ● Manual install would require: ● Unpack the tarball ● Point it to the CM ● Make sure no daemons are ever started (it is a client!)UCSD Jan 18th 2012 Frontend Install 30
  • 31. Installing with the Q&A Installer~/glideinWMS/install$ ./glideinWMS_install ~/glideinWMS/install$ ./glideinWMS_install... ...Please select: 6 Please select: 6[6] Condor for VO Frontend [6] Condor for VO Frontend… …Where do you have the Condor tarball? /home/frontend/Downloads/condor-7.6.4-x86_rhap_5-stripped.tar.gz Where do you have the Condor tarball? /home/frontend/Downloads/condor-7.6.4-x86_rhap_5-stripped.tar.gzWhere do you want to install it?: [/home/condor/glidecondor] /home/frontend/glidecondor/glidecondor Where do you want to install it?: [/home/condor/glidecondor] /home/frontend/glidecondor/glidecondorIf something goes wrong with Condor, who should get email about it?: me@myemail If something goes wrong with Condor, who should get email about it?: me@myemailDo you want to split the config files between condor_config and condor_config.local?: (y/n) [y] y Do you want to split the config files between condor_config and condor_config.local?: (y/n) [y] y... ...Do you want to get it from VDT?: (y/n) y Do you want to get it from VDT?: (y/n) yDo you have already a VDT installation?: (y/n) yWhere is have already a VDT /etc/osg/wn-clienty Do you the VDT installed?: installation?: (y/n) Where is the VDT installed?: /etc/osg/wn-clientWill you be using a proxy or a cert? (proxy/cert) proxy Will you be using a proxy or a cert? (proxy/cert) proxyWhere is your proxy located?: /home/frontend/.globus/x509_service.proxyMy DN =is your proxy located?: /home/frontend/.globus/x509_service.proxy Where DN1 My DN = DN1... ...DN: DNXXX DN: DNXXX xNnickname: [condor001] uidXXX nickname: [condor001] uidXXXIs this a trusted Condor daemon?: (y/n) y Is this a trusted Condor daemon?: (y/n) y... ...DN: DN:What node is the collector running (i.e. CONDOR_HOST)?: collectornode.mydomain What node is the collector running (i.e. CONDOR_HOST)?: collectornode.mydomainUCSD Jan 18th 2012 Frontend Install 31
  • 32. Creating the frontend config file ● This is the main step of the installation! ● Here I explain only the basics ● Actual frontend config tuning in the next talk ● As usual, using the provided installer makes life easier ● And is the recommended way to get the basic template ● You will likely want to tune the created config, thoughUCSD Jan 18th 2012 Frontend Install 32
  • 33. Using the Q&A Installer - 1/3$ ./glideinWMS_install $ ./glideinWMS_install... ...Please select: 7 Please select: 7[7] VO Frontend [7] VO FrontendDo you have already a javascriptRRD installation?: (y/n) y Do you have already a javascriptRRD installation?: (y/n) yWhere is javascriptRRD installed?: /home/frontend/javascriptrrd-0.6.1 Where is javascriptRRD installed?: /home/frontend/javascriptrrd-0.6.1Where will you host your config files?: [/home/frontend/frontstage] /home/frontend/frontstage Where will you host your config files?: [/home/frontend/frontstage] /home/frontend/frontstageWhere will the web data be hosted?: [/var/www/html/vofrontend] /var/www/html/vofrontend Where will the web data be hosted?: [/var/www/html/vofrontend] /var/www/html/vofrontendWhat Web URL will you use?: [http://my.node/vofrontend/] http://my.node/vofrontend/ What Web URL will you use?: [http://my.node/vofrontend/] http://my.node/vofrontend/Where will you host your log files?: [/home/frontend/frontlogs] /home/frontend/frontlogs Where will you host your log files?: [/home/frontend/frontlogs] /home/frontend/frontlogsGive a name to this VO Frontend?: [myVO-cabinet-10-10-5] VOfe This is your Give a name to this VO Frontend?: [myVO-cabinet-10-10-5] VOfeGive a name to this VO Frontend instance?: [v1_0] v1_0 Give a name to this VO Frontend instance?: [v1_0] v1_0 security nameWhat node is the WMS collector (i.e. the gfactory) running?: factory.node What node is the WMS collector (i.e. the gfactory) running?: factory.nodeWhat is the classad identity of the glidein factory?: [gfactory@factory.node] gfactory@factory.node What is the classad identity of the glidein factory?: [gfactory@factory.node] gfactory@factory.nodeWhat is the WMS collector DN (i.e. subject)?: DN1 What is the WMS collector DN (i.e. subject)?: DN1Where is your proxy located?: /home/frontend/.globus/x509_service.proxy You get Where is your proxy located?: /home/frontend/.globus/x509_service.proxy this datavoms-proxy-info is needed to extract the VO information from the proxy voms-proxy-info is needed to extract the VO information from the proxy from theDo you want to get it from VDT?: (y/n) y Do you want to get it from VDT?: (y/n) y factoryDo you have already a VDT installation?: (y/n) y Do you have already a VDT installation?: (y/n) yWhere is the VDT installed?: /etc/osg/wn-client Where is the VDT installed?: /etc/osg/wn-client adminsFor security reasons, we need to know what will the WMS collector map us to. For security reasons, we need to know what will the WMS collector map us to.What is the mapped name?: vo1@factory.node What is the mapped name?: vo1@factory.nodeUCSD Jan 18th 2012 Frontend Install 33
  • 34. Using the Q&A Installer - 2/3 Using pool collector collector.node Using pool collector collector.node What is the pool collector DN (i.e. subject)?: DN2 What is the pool collector DN (i.e. subject)?: DN2 List and secondary pool collectory the glideins should use instead of the main collector. List and secondary pool collectory the glideins should use instead of the main collector. Leave an empty collector name when finished. Leave an empty collector name when finished. Collector name: collector.node:9620-9819 Collector name: collector.node:9620-9819 Collector DN (i.e. subject): DN3 Collector DN (i.e. subject): DN3 Collector name: Tree of collectors Collector name: The following schedds have been found: The following schedds have been found: [1] schedd1.node [1] schedd1.node ... ... Do you want to monitor all of them?: (y/n) y Do you want to monitor all of them?: (y/n) y What is the DN (i.e. subject) for schedd schedd1.node?: DNxxx What is the DN (i.e. subject) for schedd schedd1.node?: DNxxx x N ... ...UCSD Jan 18th 2012 Frontend Install 34
  • 35. Using the Q&A Installer - 3/3What kind of jobs do you want to monitor?: [JobUniverse==5] JobUniverse==5 What kind of jobs do you want to monitor?: [JobUniverse==5] JobUniverse==5Give a name to the main group: [main] main Give a name to the main group: [main] mainWhat expression do you want to use to match glideins to jobs? What expression do you want to use to match glideins to jobs?Match string: [True] glidein["attrs"]["GLIDEIN_Site"] in job["DESIRED_Sites"].split(",") Match string: [True] glidein["attrs"]["GLIDEIN_Site"] in job["DESIRED_Sites"].split(",")What job attributres are you using in the match expression? What job attributres are you using in the match expression?Job attributes: [DESIRED_Sites] DESIRED_Sites Job attributes: [DESIRED_Sites] DESIRED_SitesWhat glidein/factory attributres are you using in the match expression? What glidein/factory attributres are you using in the match expression?Factory attributes: [GLIDEIN_Site] GLIDEIN_Site Factory attributes: [GLIDEIN_Site] GLIDEIN_SiteDo you want to use the frontend proxy to submit glideins: (y/n) [y] n Will use glexec Do you want to use the frontend proxy to submit glideins: (y/n) [y] nAn empty entry means you are done. wherever available An empty entry means you are done.proxy fname: /home/frontend/.globus/x509_vopilot1.proxy proxy fname: /home/frontend/.globus/x509_vopilot1.proxyproxy fname: proxy fname:How do you want to categorize the use of glexec if available at sites?: [OPTIONAL] OPTIONAL How do you want to categorize the use of glexec if available at sites?: [OPTIONAL] OPTIONALDo you want to expose the Grid env. to the user jobs?: (y/n) y Do you want to expose the Grid env. to the user jobs?: (y/n) yDo you want to create the VO Frontend instance (as opposed to just the config file)?: (y/n) [n] n Do you want to create the VO Frontend instance (as opposed to just the config file)?: (y/n) [n] nConfiguration file is located at /home/frontend/frontstage/instance_v1_0.cfg/frontend.xml Configuration file is located at /home/frontend/frontstage/instance_v1_0.cfg/frontend.xml Here is your config file UCSD Jan 18th 2012 Frontend Install 35
  • 36. Instantiating the Frontend ● Once you are happy with the config, run create_frontend By default, the security ● It will create the Frontend instance in name is used to create the ~/frontstage/frontend_VOfe-v1_0 frontend name ● You will work in there from now on ~/glideinWMS/creation$ ./create_frontend ~/frontstage/instance_v1_0.cfg/frontend.xml ~/glideinWMS/creation$ ./create_frontend ~/frontstage/instance_v1_0.cfg/frontend.xml Created frontend VOfe-v1_0 Created frontend VOfe-v1_0 Active entries are: Active entries are: main main Work files can be found in /home/frontend/frontstage/frontend_VOfe-v1_0 Work files can be found in /home/frontend/frontstage/frontend_VOfe-v1_0 Log files can be found in /home/frontend/frontlogs/frontend_VOfe-v1_0 Log files can be found in /home/frontend/frontlogs/frontend_VOfe-v1_0 Support files are in /var/www/html/vofrontend/stage/frontend_VOfe-v1_0 Support files are in /var/www/html/vofrontend/stage/frontend_VOfe-v1_0 Monitoring files are in /var/www/html/vofrontend/monitor/frontend_VOfe-v1_0 Monitoring files are in /var/www/html/vofrontend/monitor/frontend_VOfe-v1_0UCSD Jan 18th 2012 Frontend Install 36
  • 37. Starting the Frontend ● The Frontend instance has a init.d-like script ./frontend_startup start|stop ● This script also must be used to make any config changes to the Frontend ● Never change the frontend.xml in the Frontend dir ● Work on a copy (possibly in ../instance_v1_0.cfg/) and then run ./frontend_startup reconfig new_configUCSD Jan 18th 2012 Frontend Install 37
  • 38. Installing the Frontend from the OSG RPM repositoryUCSD Jan 18th 2012 Frontend Install 38
  • 39. The Frontend RPM ● OSG RPM repository provides a frontend RPM ● Advantages: ● It is an RPM, so tighter system integration ● Partially pre-configured to talk to the OSG factory ● Disadvantages: ● It is an RPM, thus installed and maintained as root ● No support for versioning Processes still running ● Requires more manual configuration as frontend https://twiki.grid.iu.edu/bin/view/Documentation/Release3/InstallGlideinWMSFrontendUCSD Jan 18th 2012 Frontend Install 39
  • 40. Installation of the RPM ● Similar to OSG Grid Client ● Indeed good practice to install the OSG Client first ● Requires a RPM-based Condor installation ● But will provide basic Condor config files in /etc/condor/config.d/ (not going into details in this talk, see Twiki) ● The actual RPM install a simple yum install glideinwms-vofrontend ● You still need to configure it, though https://twiki.grid.iu.edu/bin/view/Documentation/Release3/InstallGlideinWMSFrontendUCSD Jan 18th 2012 Frontend Install 40
  • 41. Configuration ● The RPM comes with a basic template in /etc/gwms-frontend/frontend.xml ● All security sections must be modified: ● To talk to the rest of the Condor pool (CM and submit nodes) ● For the Factory interaction (the info you got from the Factory admins) ● Regarding the service and pilot proxies https://twiki.grid.iu.edu/bin/view/Documentation/Release3/InstallGlideinWMSFrontendUCSD Jan 18th 2012 Frontend Install 41
  • 42. Installation and startup ● The RPM provids a init.d script /etc/init.d/gwms-frontend ● You will need to run the reconfig once to finish the installation # /etc/init.d/gwms-frontend reconfig # /etc/init.d/gwms-frontend reconfig /var/lib/gwms-frontend/vofrontend/frontend.xml /var/lib/gwms-frontend/vofrontend/frontend.xml Warning: Cannot find /var/lib/gwms-frontend/vofrontend/frontend.xml Warning: Cannot find /var/lib/gwms-frontend/vofrontend/frontend.xml If this is the first reconfig, you can ignore this message. If this is the first reconfig, you can ignore this message. { -force_name name -writeback yes|no -update_scripts yes|no -xml xml | -help } { -force_name name -writeback yes|no -update_scripts yes|no -xml xml | -help } Reconfiguring the frontend [OK] Reconfiguring the frontend [OK] ● After that, it is ready to be started /etc/init.d/gwms-frontend startUCSD Jan 18th 2012 Frontend Install 42
  • 43. The EndUCSD Jan 18th 2012 Frontend Install 43
  • 44. Pointers ● The official glideinWMS project Web page is http://tinyurl.com/glideinWMS ● glideinWMS development team is reachable at glideinwms-support@fnal.gov ● The OSG glidein factory is reachable at osg-gfactory-support@physics.ucsd.eduUCSD Jan 18th 2012 Frontend Install 44
  • 45. Acknowledgments ● The glideinWMS is a CMS-led project developed mostly at FNAL, with contributions from UCSD and ISI ● The glideinWMS factory operations at UCSD is sponsored by OSG ● The funding comes from NSF, DOE and the UC systemUCSD Jan 18th 2012 Frontend Install 45