| Date Of Receipt: 18-JUL-1995 09:01:22.52
From: SMURF::FLUME::"tappan@zk3.dec.com" "Sarah Tappan USG 18-Jul-1995 0859"
To: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <jmf@zk3.dec.com>
CC: jproj@zk3.dec.com, odehelp@zk3.dec.com, tresvik@zk3.dec.com
Subj: Re: draft: DECode-II V3.0 Upgrade for Digital UNIX pools on 8/9
Josh,
Can you say a little bit on how this has been staged/tested? Or is there
a plan that you can reference? Are we confident that developers with normal
sandbox environments will not be impacted? What testing has occured here and
at our remote sites? Do all remote sites have to switch at once and if so is
that being proactively coordinated? Do all pools have to go at once? Is mail
sufficient training on the changes?
If there is a small risk of developer impact then Aug 9 should be ok for
PT. If there is a chance that we will loose developers for a day or longer,
it will have schedule impact on PT.
sarah
> Jproj team, I'd like to spend about 5 minutes on this at the start of
> our meeting Wednesday of this week (prior to Pt's /sbin discussion);
> please check your calendars to see if the targeted date looks ok to you
> for the upgrade (i.e. locking pools Wednesday 8/9 in the a.m.).
>
> Feedback on this memo welcome (in mail or at the meeting).
>
> Thanks very much... -josh
>
>
> -------------------------------------
>
> To:osf_developers
> cc:odehelp,usg
> Subject:DECode-II V3.0 Upgrade for Digital UNIX pools on 8/9
> --------
> Developers/Writers/Testers working on the Digital UNIX product,
>
> We are planning to upgrade the ODE tool development environments being
> using for the various components of Digital UNIX, on Wednesday August 9,
> from DECode-II V2 to V3.0 (ssb level).
>
> For more ODE information, see "What's New in DECode II V3.0" at this URL:
> http://www.zso.dec.com/ode/ODE-Whats-new.html
> or http://www.zk3.dec.com/ode/ODE-Whats-new.html
>
> This will include a coordinated effort to upgrade the following pools,
> for all the ongoing streams (i.e. pt, hw5, ptlite, ase, clusters, mls+,
> all of support), at all sites which take part in development:
>
> - source pools (os, x11, cde, dx)
> - doc pools (refpages, books)
> - qaqc pool
> - privately managed group shared sandboxes/pools
>
> On that day, all pools will be taken off-line for the morning while we
> upgrade our environments across usg.
>
> Users will need to do a small amount of one-time setup:
> - Enable NFS locking (New Requirement)
> - Set path to pickup v3.0 tools
>
> Shared Sandbox and Pool administrators will need to do some additional work
> to install the new ode server, covered in separate mail to that audience.
> /* If you are managing an ODE server resource, please */
> /* contact me to make sure you are kept "in the loop". */
>
> Additional details and reminders will be provided later. If you have
> any questions, please send mail to reng@zk3.dec.com.
>
> Thank you very much.
>
> - Digital UNIX Release Engineering
>
>
>
> ----------------------------------------------------------------------
> Joshua M. Friedman Internet: jmf@zk3.dec.com
> Mailstop: ZKO3-3/W20 DECnet: flume::friedman
> Digital UNIX Engineering 603-881-1548
> 110 Spitbrook Road dtn 381-1548
> Nashua, NH 03062 Office: zko3-3/z20
> ----------------------------------------------------------------------
>
>
>
>
>
|
| Date Of Receipt: 18-JUL-1995 11:30:43.60
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 18-Jul-1995 1128"
To: tappan@zk3.dec.com
CC: jproj@zk3.dec.com, odehelp@zk3.dec.com, tresvik@zk3.dec.com,
jmf@DEC:.zko.flume
Subj: Re: draft: DECode-II V3.0 Upgrade for Digital UNIX pools on 8/9
Sarah, thank you for all the good questions! I will make sure these
are all covered in my plan, which is in progress, and that the
appropriate level of proactive coordination is taking place.
> Josh,
>
> Can you say a little bit on how this has been staged/tested?
We currently have the V3 tools running here on a "tutorial" project for
testing, which was upgraded from V2 to V3 to test the documented
upgrade process. Also, we are about to (this week) do this same
upgrade for our "release" pool, so that release engineering as a group
gets first-hand experience with the new tools for several weeks
before the remaining pools upgrade.
In addition, DECwest (ODE group) has been running these tools for about
six months now on their ODE pools.
> Or is there a plan that you can reference?
I am working on a plan which I will soon make available, based on plans
I've written for other ODE tools upgrades we have done in the past.
This will also reference the project plan for ODE V3.0 itself.
> Are we confident that developers with normal sandbox environments will
> not be impacted?
Part of the testing we have done with the tutorial pool, and to be done
with the release pool, is using existing sandboxes with an upgraded
pool. This has been designed to all work, and our testing has shown
this does work fine. Also, note that since we use 'make' and related
DE tools from our backingtrees, there is no risk to the builds being
impacted in terms of introducing new DE tools.
> What testing has occured here and at our remote sites?
I think I covered this.
> Do all remote sites have to switch at once and if so is that being
> proactively coordinated?
Yes this is being proactively coordinated. I have discussed this with
the ODE site admins at UNX (Rich Larsen), Seattle (Tina Anderson), as well
as the admins for the DOC pools (Joyce Demers) and the QAQC pool (Paul
Hantman), and all are comfortable with upgrading simultaneously.
> Do all pools have to go at once?
Not really, but we determined it would make life a lot easier if there
were one set of "default" tools in use everywhere for all the pools.
This is the fallback we can exercise if necessary, based on different
releases' schedules, that different pools can upgrade at different times
(however after the upgrade users of the old tools will have to hardcode
the /usr/sde/ode2.0/tools path rather than use the default /usr/sde/tools).
Note, however, that any project which upgrades must upgrade for all
developers at all sites.
> Is mail sufficient training on the changes?
We are planning to hold an overview/training session for ZK3 and UNX on
the differences between V2 and V3, shortly before or after the upgrade,
however this has not yet been scheduled (I'll get going on this). The
DECwest ODE team has offered that they can run this. It might work best
to have one video link conference ZSO-ZK3 and another ZSO-UNX.
Also, there has been significant investment in web-based hypertext
documentation in V3, and very little has changed in the user command
space, and so I feel confident that what we have planned is sufficient.
> If there is a small risk of developer impact then Aug 9 should be ok for
> PT. If there is a chance that we will loose developers for a day or longer,
> it will have schedule impact on PT.
>
> sarah
From what we understand about the V3 product and the upgrade path, the
risk of extended downtime/impact/problems is very small. Note that the
timeframe was chosen with the assumption that PTLITE would be out the
door, and that this would be a relatively "quiet" time for all releases.
Again, thank you very much.
-josh
|