[235] in Kakapo Windows Team
FW: Notes on the last kakapo meeting 12/04/03
daemon@ATHENA.MIT.EDU (Brian Murphy)
Thu Dec 18 08:47:20 2003
Reply-To: <bmurphy@MIT.EDU>
From: "Brian Murphy" <bmurphy@MIT.EDU>
To: <kakapo@mit.edu>
Date: Thu, 18 Dec 2003 08:47:15 -0500
Message-ID: <000a01c3c56d$7464b510$a200bb12@bmurphy>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
My Apologies for not sending these notes out sooner. Also, at the bottom
is the list of Agenda items Richard had proposed. Given that we will be
meeting in just over an hour I would not expect that we can determine
what topics belong with Kakapo and which ones should be handed off to
other teams. So, over the next couple of weeks please review the list
and provide feedback.
Thank you Richard for capturing these notes at the last meeting....Brian
-----Original Message-----
From: Richard Edelson [mailto:redelson@MIT.EDU]
Sent: Tuesday, December 09, 2003 3:15 PM
To: Brian Murphy
Subject: Notes on the last kakapo meeting 12/04/03
Some notes on the last kakapo meeting 12/04/03:
Tom Coveney reports he is working with LFMSDM and WAC regarding new
deployments to win.mit.edu
Phil discussed the current state of the External Windows Review Report
and
some of it's findings. He will distribute an on-line copy to the team.
Richard has written a list of proposed agenda items for kakapo, which
was
reviewed by Phil and others present. Phil's suggestion was to distribute
the list to the team for comments regarding which items were in the
scope
of kakapo and which might just be feedback we could be providing another
team. Some items were regarding drafting SLA's, Phil mentioned we have a
person who specializes in this SLA's who we should work with.
MechE will be expanding it's win.mit.edu deployment, Chad will be in
contact with them on an ongoing basis.
We discussed Windows statistics in a number of contexts. Tom Coveney is
collecting information on existing NT 4 domains and their plans to
migrate
to Windows 2000. He says about one third of the migrations are in some
state of progress, some large departments plan to migrate to independent
domains, but the majority of departments seem to prefer to join
win.mit.edu. Chad said he would work with Tom to continue to gather this
data. Chad working on some usage stats for Academic Computing customers
within win.mit.edu. Pismere team is also doing some usage stats
development. Phil suggested that kakapo should be bringing all this data
together.
Sidney Pacific requested adding an athena machine and offered to convert
a
Windows machine for the purpose, Phil noted that this was outside of
kakapo's scope being strictly a budget issue impacting athena clusters
and
would be followed up on appropriately.
Last week content was deleted accidentally from the
/is/topics/windows/server/ website. It was noted that a staging site was
not being used to update content. Phil said he would speak with Jane
White
to see that a staging directory is implemented for content updates.
Closing week: Chad plans to shutdown some of the Windows clusters due to
possible power interruptions during this time. All domain infrastructure
services will remain running. Next week kakapo will draft a message to
be
sent via email regarding the closing week.
The helpdesk asked how to determine who is the admin contact of a
machine
within a win.mit.edu container. It can be found via the following
commands:
stella hostname -lcn Will output the name of the container
the machine
resides in
mitch -i container name Will output info on the container
including the
admin contact list
Brian said he would also poll the helpdesk for more technical
information
they feel they need. They also asked how they should track bug status.
The Pismere team is closing down, no update on details yet.
------------------------------------------------------------------------
--------------------------------
Proposed Agenda items:
Some of these may overlap with First Contact, but that's not necessarily
a
bad thing. The idea here would be for one or two people within the
kakapo
group to take some of the proposed agenda as action items. They would
write
a draft to be presented to the entire group for review.
1). SLA's for win.mit.edu customers. General SLA for the service and
possibly some more specific ones for some customers.
2). Event Management: Response times, Levels of events, Escalation
3). Change Management: Patching, time windows, notification policies,
testing criteria
4). Roles of support groups
5). Software distribution: web, msi's
6). Application support: Enterprise apps, Desktop apps
7). Release Engineering
8). Documentation
9). Support Model
10). Scope of central domain, purpose of independent domains
11). Evaluation: Review of new Windows service offerings / extended
services
12). Security: Model/distribution. How proactive should IS be. can we
provide more granular choices to customers. Review of processes, i.e.
how
patches are evaluated.
13). Migration status
