Linux Managed Hosting Service

1
Linux Managed Hosting Service
Merrill Lynch April 7, 2003 Presented by Phil
Tully Philip_tully_at_ml.com
2
Standard Build

• Design model
• Support model
• Implementation method.

3
Standard Build Design model.
Platform Convergence

• Portability across Hardware.
• Portability across Distributions.
• Do not tie processes to closed interfaces
• Portability across Business units.
• Minimize BU dependencies.

4
Standard Build Design model.

• FHS file-system hierarchy standard
• LSB compliant.
• Vendor requirements
• Internal application requirements
• Portability across platforms.
• Open interfaces for commercial products.
• Functional requirements.
• Scheduling
• Security
• Backup/restore
• CR
• Directory functions. (single sign-on, singe home)

5
Standard Build Design model.
6
Standard Build Support model

• Build on Current strengths
• Utilize current CR infrastructure.
• Integrate with current call centers.
• Explore off-Shore opportunities.
• Utilize vendor neutral interfaces.

7
Standard Build(s)

• Development bundle
• Webservices, Databases etc.
• QA bundle
• Production configuration.
• Prod. Bundle
• Development plus production support.
• (Job scheduling, backup/restore, CR Security,
  event management)

8
Linux/390 Standard Build.

• How it will work
• Image copy
• Guest Lan connection
• Email notification
• Parameters
• Cost allocation. - Chargeback
• Decrease time to market.
• Current same day working toward same hour.
• Decentralized control. Customized build process.
• Ongoing process

9
Direction of Effort/z

• NT Fileserver Consolidation
• 1.2Tb already migrated
• Webserver consolidations
• Static, ASP, JSP based sites