1 / 9

Exploring Total Costs of Linux: Notes from a Long-Time User

Delve into insights from a seasoned Linux user, Rich Braun, and Online Buddies Inc., discussing software-as-a-service, Java, VMware, and centralized administration. Examine vendor strategies for administrative console, support contracts, enhanced features, production-grade releases, and career skills development, along with cost distribution details. Discover how vendor tactics aim to streamline operations and enhance user experience, influencing software budgets and skill development.

axel
Download Presentation

Exploring Total Costs of Linux: Notes from a Long-Time User

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Total Costs of Linux Notes from a Long-Time User Rich Braun  Online Buddies Inc. 18 Feb 2009

  2. Software-as-a-service • Java • VMware and its free cousins • Complexity • All this leads to centralized admin 1970s-style timesharing is back

  3. Vendor Strategies: • 1: The Administrative Console • 2: Embedded Support Contracts • 3: Enhanced Features • 4: Production-Grade Releases • 5: Career Skills Development Where the Money Goes

  4. Vendor strategy 1 • Use our one tool to rule them all • Your problems will be solved • But actually, it’s our problem solved • We want you to use our apps • Examples: RHN software updates, yast2 Administrative console

  5. Vendor Strategy 2 • Software validated in one environment • There is no single “Linux standard” • Support contract stipulates valid env • Examples: DoubleClick/Oracle; Zend Platform Embedded support contracts

  6. Vendor Strategy 3 • Application source is “open” • Some features are closed • Debuggers and monitoring tools typical • Examples: MySQL, Zend Platform Enhanced Features

  7. Vendor Strategy 4 • Longer release cycle: 1- to 2-years • Minor releases each 90 days • Open Source version continuously patched • Examples: SLES, RHEL • Often difficult/impossible to migrate dev to production Production-Grade Releases

  8. Vendor Strategy 5 • Trade Conferences • User Groups • Certifications • Examples: Oracle, Novell Career Skills Development

  9. Marketing or Dev buys 3rd-party app • Internal automation – home-grown admin • If you get all this right: • HW budget = $ X • SW budget = $2X • Salaries = $ X Bottom Line

More Related