FY09 Tactical Plans for Services/Linux (SL, SLF, Errata)

1
FY09 Tactical Plans forServices/Linux (SL, SLF,
Errata)

• Wayne Baisley
• 09/26/2008

2
FY09 Tactical Plan for Services/Linux (SL,
SLF, Errata)

• Relevant Strategic Plan(s)
• FY09 Tactical Plan Services Linux 2828-v2
• Tactical Plan Leader Wayne Baisley
• Organizational Unit home CD/LSC/CSI/DSS

3
FY09 Tactical Plan Strategies and Goals

• Tactical Plan Strategies
• Encourage people to use central services
• Include user community in decision making process
  via Unix Users and Sysadmin roundtable.
• Collaborate with other labs
• Maintain life cycle processes which anticipate
  user needs, changes in technology, growth (or
  decline) in demand, etc., and allow for tactical
  plans to be developed 12-18 months ahead, with
  implementation 6 months ahead of need
• Tactical Plan Goals
• Provide robust, stable and secure infrastructure
  to support the major operating systems.

4
FY09 Tactical Plan Objectives

• Tactical Plan Objectives
• Provide timely releases of supported versions of
  SL/F in conjunction with upstream vendor.
• Provide timely releases of new versions of SL/F
  in conjunction with upstream vendor.
• Maintain security errata for supported versions
  in a timely manner.
• Update existing distribution and build systems.
• Evaluate linux inventory service.
• Understand user requirements through a series of
  user community meetings.

5
FY09 Tactical Plan A short glance back

• FY08 Accomplishments
• SL/F 3.0.9 maintenance version
• SL/F 4.6
• SL/F 5.1 and 5.2
• Timely errata and security patches
• Fermi Linux is now 10 years old

6
FY09 Tactical Plan Past Action Items

• Resolution of Past Action Items
• 25.2 Linux What is the process to reach a
  generally acceptable and cost-benefit optimal
  decision for the Short-Term Support Platform
  (Fedora vs. Ubuntu vs. other)? How to select
  effect customer representatives to participate in
  decision-making process?
• This has been partially addressed. Besides
  the monthly Unix Users Meetings, weve had
  discussions with other stakeholders (Jason Allen,
  in particular).

7
Service Activity Services/SL/Operations
Activity type Ongoing Timescale Continuous Mile
stones N/A Metrics Number of packages
maintained/released throughout the year.
8
Service Activity Services/SLF/Operations
Activity type Ongoing Timescale Continuous Mile
stones N/A Metrics Number of packages
maintained/released throughout the
year. Activity type New Timescale October
2008 to November 2008 Milestones Understand user
requirements through a series of user
community meetings. Metrics Have a list of
user requirements at the end of evaluation
period.
9
Service Activity Services/Errata/Operations
Activity type Ongoing Timescale Continuous Mile
stones N/A Metrics Number of errata
built/released throughout the year.
10
Service Activity Services/SLF/Projects
Activity type New Timescale November 2008 to
January 2009 Milestones Evaluate a Linux
inventory service. Compare what we currently
have with new open sourced upstream vendor
product. Metrics We would have a
recommendation at the end of the
evaluation.   Activity type New Timescale May
2009 to September 2009 Milestones Update
existing distribution and build
systems. Metrics New servers should be in
place. Old servers should be decommissioned
11
Service Activity Services/SLF/Projects
Activity type New Timescale December 2008 to
July 2009 Milestones Evaluate and establish a
Short Term Support release service Metrics A
working STS service/infrastructure at the end of
the evaluation.  
12
FY09 Resource Request, Preliminary Allocation
Level 0 Activity Services/Desktop Server
Support
FY09 Tactical Plan Activity Level 1 FTE Request At Activity Level 1 MS Request At Activity Level 1 FTE Allocation At Activity Level 1 MS Allocation At Activity Level 1
OS/Server Support Linux (SL, SLF, Errata) 2.10 36,700
Total   2.10 36,700
13
Impact of Preliminary Allocation

• Priorities
• Our highest priority is to get the security
  errata recompiled, tested, and released with
  minimal delay.
• The next priority will be to release the
  appropriate Scientific Linux and Scientific Linux
  Fermi 5.x and 4.x releases. There is always new
  hardware coming out, and the users need the new,
  updated releases because sometimes the older
  distribution won't install on the latest
  hardware.
• Our next priority should be to understand the
  user requirements through a series of meetings.
  This list of user requirements will help us with
  our evaluation of the linux inventory service,
  which is our next priority.
• Finally, we need to update the hardware of the
  Scientific Linux Fermi build and distribution
  infrastructure. This should take us into the
  next fiscal year.

14
Impact of Preliminary Allocation

• Risk Assessment
• If we fall behind on the Security errata, the Lab
  is opened up to either security issues or
  possible public embarrassment.
• Not providing a timely release of new and
  supported versions of SL/F has an impact on the
  development of scientific tools both internal to
  FNAL as well as the GRID.
• If we do not update the build and distribution
  infrastructure, we risk having the current
  machines break down, because they are old and out
  of warranty. These breakdowns will prevent
  security errata from either being built, or being
  distributed. This will open the Lab up to
  security issues or possible public embarrassment.
• If we do not understand user requirements, it is
  possible that we might put effort into projects
  that are not needed or wanted.

15
Template Guidance (not part of the presentation)

• Activity Activity Level 1 or lower explicitly
  listed in Tactical Plan
• Activities have been classified in Tactical Plans
  as either being more Project-like or Service-like
• Projects finite defined lifetime, defined
  deliverable. Includes RD work.
• A.k.a Upgrades,
• Services same operation or task repeatedly.
• A.k.a. Operations, Maintenance, Support,
• Whether an activity is a project or service
  determines which format slide to use later.
• Terminology
• Obligation Budget Allocated budget. This may
  differ from the budget request.
• YTD Obligations Fully incurred expenses. Does
  not include RIPs, Req.s in CD, etc.
• Current FY08 Forecast Estimate of all
  obligations to be incurred by the end of FY08.
• MS Equipment Operating. Operating includes
  Travel, Material Purchases, Professional Services
  (contractors), Maintenance (licenses), and Other.
• RIP Requisitions in Progress