MyProxy Requirements Status

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

Req

Assess Statement
 Green  Service class is Critical
 Green  Disk space requirements are estimated at 20GB based on reviewing current myproxy.cern.ch 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 is not required since the myproxy service operates on high ports. This is a documented assumption
 Green  The myproxy data is stored in /var/myproxy. No other directories need to be backed up to restore the service to another machine

Dvl

Assess Statement
 Green  Product code available http://grid-deployment.web.cern.ch/grid-deployment/RpmDir_i386-sl3/external/myproxy-VDT1.2.0rh9_LCG-2.i386.rpm
 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
 Green  Troubleshooting is here
 Green  LDAP is the only required middleware

Hw

Assess Statement
 Green  Minimal CPU power required for application.
 Green  Memory size of 1GB is sufficient.
 Yellow  Two machines allocated currently in burn in test due to be ready 10/10/2005
 Yellow  Machines installed in appropriate location within data centre (UPS,Network)
 Green  No database or external disk requried

Ops

Assess Statement
  RED    2nd level support organisation defined (who to call when there is a problem with the application or middleware)
 Yellow  Mechanism to contact 2nd level organisation
 Yellow  Response time for 2nd level organisation
 Yellow  List of machines where service is running defined
 Yellow  List of configuration parameters and their values for the software components
 Yellow  List of processes to monitor
 Yellow  List of file systems and their emergency thresholds for alarms
  RED    Application status check script requirements defined
  RED    Definition of scheduled processes (e.g. cron)
 Yellow  Test environment defined and available
 Yellow  Problem determination procedures including how to determine application vs middleware vs database issues
  RED    Procedures for start/stop/drain/check status defined
 Yellow  Automatic monitoring of the application in place
  RED    Backup procedures defined and tested

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

Tracking

27/09/2005

Area Updates
Req Added questionairre status

Edit | Attach | Watch | Print version | History: r14 | r12 < r11 < r10 < r9 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r10 - 2005-10-18 - TimBell
 
    • 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