Grid3Dev

1
Grid3Dev

• Its current description

2
What is Grid3Dev Currently?

• A Development environment
• The Grid3 Integration Testbed

3
The Grid3Dev Environment

• Consists of a set of services designed to allow
  groups to create their own testbeds
• The Grid3Dev services are
• The grid3dev software cache
• This software cache is identical to being used in
  the production cache but it points it
  configurations to the Grid3Dev services instead
  of the production services
• The grid3dev monitoring infrastructure
• A DEV version of the ML systems complete with its
  own separate collector database and ML group
  (grid3dev)
• A DEV version of the ganglia top level gmeta
  collector
• GridCat Just the GridCat download tar ball, it
  has been designed to allow you to create your own
  catalog and is independent of other services
• The Grid3Dev version of the Grid3 Authentication
  service
• Currently thats just the Grid3Dev VOMS
  maintained by the Grid3Dev group
• Grid3dev Operations Not supported by the iGOC

4
The Grid3Dev Environment (2)

• The environment is designed to allow testbed to
  come together to develop and test new Grid3
  software components, services, infrastructure
  etc. in parallel to other Grid3 activities. The
  services are there to provide testbeds with
  whatever relevant aspects of the Grid3 production
  environment is needed for its test.
• Its main purpose is to allow any number of these
  development projects to occur without affecting
  or interfering with production or integration
  activities

5
Grid3Dev Integration Testbed

• This is an instantiation or example of a
  testbed created from the Grid3Dev environment
• Its purpose is solely to develop, certify and
  validate new Grid3 production caches
• Details of integration testbed and the working
  group
• It uses all of the Grid3Dev services that are
  part of the Grid3dev environment
• Packaging It is the generator of the official
  grid3dev.pacman cache

6
Grid3Dev Integration Testbed (2)

• Monitoring All monitoring applications
  represented in the Grid3 production grid but the
  dev version (currently doesnt use ACDC)
• It uses the grid3dev VOMs service
• Operations support is not provided by the iGOC
  but by the grid3dev team with GridCat operations
  checks running from the ivdgl webserver.
• Consists of n sites where n is manned by those
  directly involved in the integration test
• It has its own archived mailing list
  (grid3dev_at_ivdgl.org)
• It has its own webpage
• Includes gridcat and links to the dev monitoring
  and information are found

7
Status of Grid3dev Services

• Software packaging
• Grid3dev.pacman
• VDT 1.2.1
• grid3 schema
• grid3 info provider, configured to point to
  grid3dev services
• Authorization
• Grid3dev VOMS running at IU version 0.7.1 newer
  than production one (0.6.1)
• Monitoring
• GridCat version 0.5.0 will be released next
  Monday, much improved, supports world views new
  schema with facilities information much much
  more. Older version available at
  www.ivdgl.org/gridcat
• Ganglia gmeta collector Available at IU but its
  not currently running. It just needs to be turned
  on
• MonaLISA grid3dev group available and DB
  collector ready and waiting

8
Status of the Grid3dev Grid

• Not currently operating as a Grid
• Waiting for direction from Grid3dev/OSG
  deployment groups
• Need a program of work for next round of Grid3
  production upgrade
• Would like to identify flavor of sites, ie pbs
  condor