1 / 4

Status of the Globus Distribution for Testbed 1

Status of the Globus Distribution for Testbed 1. Andrew McNab, University of Manchester mcnab@hep.man.ac.uk. Current release: beta-21. This is based on Globus 2.0 beta released in November. Beta code only differed from alpha releases (eg alpha-15) in terms of bug fixes.

jaimejones
Télécharger la présentation

Status of the Globus Distribution for Testbed 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status of the GlobusDistribution for Testbed 1 Andrew McNab, University of Manchester mcnab@hep.man.ac.uk

  2. Current release: beta-21 • This is based on Globus 2.0 beta released in November. • Beta code only differed from alpha releases (eg alpha-15) in terms of bug fixes. • However, which flavors of each subpackages are available followed Globus recommendations (this mainly affected pgm -> pgm_static) • We stopped building the “empty” Globus subpackages any more (ie that just contain the metadata file and filelist.) • Used for Testbed software releases this year and the EU Demo. • Apart from a security fix for gsi-wuftpd and some important fixes to the environment setting scripts, this has been frozen to provide stable platform for run up to Demo.

  3. Some outstanding issues (as of last Friday) • Some issues with gsincftp and globus-url-copy in versions used in distribution (gsincftp deprecated now for EDG) • NetLogger not supported by all relevant Globus subpackages, so cannot yet easily be included in release framework. • Some other smaller issues need to be fixed and included in next release. • AFS modifications for gsi-wuftpd produced by Lyon need to be included. • New versions of globus_ftp_client, globus_ftp_control and gass from 20 Feb need to be tested and included. • Do we need to rewrite gridmap.c to fit in with WP4 CE changes? • However … Globus published a new set of Beta II bundles on Friday.

  4. So, “Globus Beta II” now? • We should produce a full set of RPM’s from the new beta2 bundles, so they can be evaluated if nothing else. • Should we (a) go straight to this as the pre-production version? • Or (b) make changes to beta21, publish that and then publish a set of Beta II RPM’s for testing? • [My preference is (a) ] • However, whatever we do/publish, it does not become the version everyone has to use until the ITeam decides to include it in the current release.

More Related