MyProxy Requirements Status

Changes to the status should be reflected for each group to WlcgScDash.


Assess Statement
 Green  Service class is Critical
 Green  Disk space requirements are estimated at 20GB based on reviewing current configuration
 Green  There is no database requirement for myproxy
 Green  There is no middleware components in addition to the myproxy software required
 Green  External connectivity to port 7512 is required. This is the port for the myproxy-server.
 Green  The myproxy data is stored in /var/myproxy. No other directories need to be backed up to restore the service to another machine. TSM client is configured to perform a daily backup of this directory. In the HA configurations, a second copy is also stored on the slave machine.
 Green  The high level diagram of the service is defined in WmsFlows


Assess StatementSorted descending
 Green  Troubleshooting is here. Problem guides for CERN are defined in PxPrb.
 Green  Product code available
 Green  LDAP is the only required middleware as part of the BDII information export.
 Yellow  LCG Code certification status is not known but the 2.2 version has been in the test since July
 Green  Administration Guide is available at myproxy docs


Assess Statement
 Green  Minimal CPU power required for application. Server rarely about 5% CPU so no issue for midrange configuration.
 Green  Memory size of 1GB is sufficient. No swapping on production configuration.
 Green  px101 and px103 are allocated for the production service. px102 and px104 are allocated for the LFC myproxy service.
 Green  Machines are installed in the LCG servers area along with the other middleware servers. This is reliant on the switch from French to Swiss electricity in the event of a failure of primary supply.
 Green  No database or external disk requried
 Green  The hardware configurations required is defined in PxWlcg


Assess Statement
 Green  2nd level support is performed by the service manager on duty. 3rd level application support is from the organisation.
 Green  E-Mail to SMOD
 Yellow  No formal service level response agreement is in place for the SMOD so compliance with LCG MoU is not possible
 Green  The machines required for the production service are listed in PxWlcg.
 Green  Configuration procedures and full installation details are in PxWlcg. Configuration is entirely via CDB and YAIM.
 Green  Lemon sensors PxLoad and PxStatus are in place to provide lemon alert when the service is down.
 Green  /var/myproxy is monitored through the standard FIO mechanisms.
 Green  service myproxy status reports the status of the application.
 Green  Cron jobs are covered in PxWlcg.
 Yellow  No test environment is currently defined. The old MyProxy box is available is required. Given the CDB configuration, a new server could be set up in < 1 day.
 Green  Problem determination procedures are defined in PxPrb.
 Green  Procedures for start/stop/drain/check status defined at PxWin.
 Green  Automatic monitoring of the application in place using PxLoad and PxStatus
 Green  Backup of /var/myproxy is performed nightly and restore tests to slave were able to retrieve proxy information

Related Documentation

Link Description
ScFourServiceTechnicalFactors Information regarding the implemention of the SC4 services
PxNotes Information about the potential MyProxy implementations
PxWlcg How the actual implementation was performed



Area Updates
Req Added questionairre status

Edit | Attach | Watch | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r14 - 2006-11-28 - LaurenceField
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback