As a number of sites are now running various beta versions of edg1.2
they may be interested in the time scales outlined below which
outline the migration to edg1.2 release. Included in this are
comments on "smaller sites".
In short though from 5.00 tomorrow testbed 1.1.4 no longer exists.
Steve
-----Original Message-----
From: Charles (Cal) Loomis [mailto:[log in to unmask]]
Sent: Thursday, August 08, 2002 11:35 AM
To: [log in to unmask]; WP-Managers; [log in to unmask];
ITeam; [log in to unmask]
Subject: [SA-HELP] 1.1.4 SHUTDOWN; 1.2 Deployment Schedule
In the anticipation of a usable EDG 1.2 release, the Integration Team
discussed the deployment plan for the production and development testbeds.
More details follow but the bottom line is:
*****
The Production Testbed running EDG 1.1.4 will SHUTDOWN at 17:00 Tomorrow
(Friday 9 August). This will allow sites to upgrade to the current beta
release to make the transition to the final 1.2.0 release faster and easier.
Some services may continue to run, but as of the deadline the production
testbed, as is, will be completely unsupported. When the production testbed
returns, it will be running 1.2.0.
*****
More detailed schedule:
1) Today (8 August): Testing of binaries from wp1 by JJ to try to reproduce
earlier acceptable reliability. If successful with hand-installed binaries,
then wp1 will provide new rpms. The Resource Broker will be wiped out and
reinstalled from scratch with the new rpms. JJ's tests will be repeated.
If the same reliability is observed, then this will be included in the
standard release and tagged as 1.2.0.
2) Assuming that the 1.2.0 release is tagged this afternoon, then the 1.2.0
release will be installed on the five main sites (CERN, CNAF, Lyon, NIKHEF,
RAL) on the DEVELOPMENT testbed. JJ's tests will be rerun once all of those
sites have been installed to confirm acceptable behaviour.
3) Assuming that the behaviour of the release is acceptable on the
development testbed, then full deployment of the 1.2.0 release on the
development testbed will commence. In fact, the changes between the current
beta release and the final 1.2.0 release are expected to be confined mainly
to the resource broker. Consequently, sites may choose to install the
current beta version of the 1.2 release to anticipate the final release.
This is the reason support for the 1.1.4 release ends Friday at 17:00.
4) Once running on the production testbed, JJ's tests will again be run to
confirm the behaviour.
5) There are known limitations with the 1.2.0 release. Consequently, an
upgrade release is expected within approximately a week. The upgrade will
include the Globus release-23 and patches for OpenSSL. It will also include
new CA rpms and patched RC (to solve slow response time) if those don't make
it into the 1.2.0 release.
6) This release (1.2.1?) will be tested on the development testbed and when
certified will be deployed on the production testbed. It is expected that
this will be interoperable with 1.2.0, so the upgrade from 1.2.0 to 1.2.1
will be done on a site-by-site basis (if possible).
Site Addition Policy:
The production & development testbeds will be limited to the five main sites
until release 1.2.1 is announced. This is to limit the number of changes
smaller sites need to follow. In particular, the upgrade from 1.2.0 to
1.2.1 will involve large change in the number of rpms.
Release Notes & User's Guide:
Contributions to the 1.2.0 release notes are expected by the editor (Anders)
next Monday (August 12). Contributions to the 1.2.0 User's Guide are
expected Monday August 19. These should be available to the users shortly
after the deadlines.
Disclaimer:
The detailed plan depends on the testing going on today. If the testing is
not successful, then the schedule may shift/change significantly. However
in all cases, support of the current production testbed running 1.1.4 will
end as of 17:00 tomorrow.
Sincerely,
Cal (for the ITeam)
|