An Integral Open Source Software selection model with a business case on IT Infrastructure Monitoring System

1,189 views

Published on

This investigation is focused on developing a method applicable to Open Source Software (OSS) selection process that considers both technology and management requirements and reveals the real Total Cost of Ownership (TCO) and Total Cost Of Acquisition (TCA), proving that there are costs, both direct or indirect, of implementing an OSS solution. This model includes two main criteria: Technological and Management.

Special thanks to:
- Graphs/Pictures by Salvador Soto (@gesoto).

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,189
On SlideShare
0
From Embeds
0
Number of Embeds
33
Actions
Shares
0
Downloads
28
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

An Integral Open Source Software selection model with a business case on IT Infrastructure Monitoring System

  1. 1. An Integral Open Source Softwareselection model with a business case onIT Infrastructure Monitoring SystemBy José Manuel López LujánMay, 2013Docs: http://jmll.me/thesis-docSlides: http://jmll.me/thesis-de-ppt
  2. 2. • Research Question• Scope & Methodology• Evaluation Models• The Integral OSS Evaluation Model• Case Study: IT infrastructure Monitoring software• Conclusions• ChallengesAgenda2
  3. 3. “Would it be possible to identify the most importantelements, Management and Technological, with thepurpose of defining an Open Source Software selectionmodel; and could this model be applied to select an ITInfrastructure Monitoring System?”Research Question3
  4. 4. • What is the need of having an enterprise-ready OSSselection model?• What is the attractiveness of the OSS from an IT andManagement perspective?• Is there any current OSS evaluation or procurementmodels?• Which criteria can be defined for OSS?Research Question4
  5. 5. • Methodology• Literature• The model• The Case study• OSS Evaluation model• University of Toronto,I+TS Division, EIS, HIG.• IT InfrastructureMonitoring System:• Nagios, Zabbix andCactiMethodology & Scope5Proof by example
  6. 6. Evaluation ModelsName Year Source Corp/Org MethodOpen Source Maturity Model(C-OSMM)Open Business Readiness Rating(O-BRR)Open Source Maturity Model(N-OSMM)Qualification and Selection of Open SourceSoftware (Q-SOSS)Open Source Maturity Model(Q-OMM)2003Duijnhouwer &WiddowsCap Gemini Yes2005Wasserman, Chan,& PalOpen-BRR Yes2005 Golden Navica Software Yes2006 Atos-Origin Atos-Origin Yes2009 QualiPSoWittmann &Nambakam,No6
  7. 7. The IntegralOSS Evaluation Model7
  8. 8. DefinitionThe evaluation Criteria• Functionality• License• Community• Seniority• Performance• Scalability• Documentation• Total Cost ofOwnership• Support• Interoperability• Security• Roadmap18
  9. 9. DefinitionThe evaluation CriteriaI-OSSEM O-BRR N-OSMM C-OSMM Q-SOSS Q-OMMFunctionalityLicenseCommunitySenioritySupportInteroperabilitySecurityRoadmapPerformanceScalabilityDocumentationTCOFunctionality - - Functionality FunctionalityLicense - Licensing License/Copyright LicensesCommunity/Adoption-Developer and userCommunityActivity/Adoption Popularity- - Age Maturity Number of commitsSupport Support Support Support Quality test- IntegrationCollaboration withother products- StandardsSecurity - Security - -Professionalism - Roadmap Roadmap RoadmapPerformance - Performance - -Scalability - ModularityModularity/Codemodification-Documentation Documentation Ease of deployment Documentation Documentation- Training TrainingTraining/Consulting/SupportTCO/Training19
  10. 10. IdentificationRequirementsRequirementsHardwareSoftwareDocumentationDocumentationDocumentationDocumentationOfficialNon-OfficialRelevantBooksSupport &CommunitySupport &CommunitySupport &CommunitySupport &CommunityOfficialNon-OfficialIssue tracker siteRelevantDistributionDistributionDistributionSourceBinariesPlatformsGeneralGeneralGeneralGeneralGeneralGeneralNameVersionLicenseTypeSiteLanguage+Services+Services+ServicesTrainingSupportConsultingArchitectureArchitectureModularityPlugins210
  11. 11. QualificationTotal Cost of Ownership311
  12. 12. QualificationTotal Cost of OwnershipStage Driver/Cost Initial AcquisitionYear Year 2 Year 3SelectionSelectionAcquisitionAcquisitionAcquisitionAcquisitionIntegrationIntegrationIntegrationUseUseUseUseRetirementRetirementUp-front evaluation study $- $- $-Up-front proof of concept implementation $- $- $-Software $- $- $-Customization for business needs $- $- $-Integration $- $- $-Hardware $- $- $-Migration (data and users) $- $- $-Training $- $- $-Process and Best practice Change $- $- $-Cost of Support Services – in house $- $- $-Cost of Support Services – contracted $- $- $-Maintenance and upgrades $- $- $-Training $- $- $-Exit costs (in relation to hardware and software) $- $- $-Exit costs (in relation to changeover, retraining) $- $- $-Total Cost/Year $- $- $-Discount factor 5%TCO $-312
  13. 13. ValuationCriterion Weight OSS1 % OSS2 % PerfectFunctionalityLicenseCommunitySenioritySupportInteroperabilitySecurityRoadmapPerformanceScalabilityDocumentationTCO1 87% 78% 100%2 100% 0% 100%2 25% 75% 100%2 71% 43% 100%2 67% 67% 100%1 80% 80% 100%2 77% 100% 100%1 83% 50% 100%1 33% 33% 100%2 25% 100% 100%2 62% 74% 100%1 90% 100% 100%Final ScoreFinal PercentileFinal Score 12.28 12.59 19Final Percentile 65% 66% 100%413
  14. 14. Selection514
  15. 15. Case Study on ITInfrastructure Monitoring• Information & Technology Services• EnterpriseVirtualization & Storage Specialist at EIS• Hybrid: CSS and OSS• Enterprise Monitoring at the Data Centre• Data Centre Renovation• Budget 5.1M CAD, ROI of two years15
  16. 16. Case Study on ITInfrastructure Monitoring• Virtual and Physical Servers• Many devices need monitoring: PDU, UPS, sensors.• Already implemented IT-IMS:• Cacti16
  17. 17. Questions17MonitoringMeasuring“Does our current monitoring package meet allour needs? ““Can the package be scaled up as the DC and itsvirtual infrastructure and systems grow? “Controlling
  18. 18. Definition• Business Context• Business Requirements• Functional• Non-Functional• Technological• The Evaluation Criteria118
  19. 19. DefinitionWhat are the requirements for the ITInfrastructure Monitoring System?TechnologicalSupport  SNMP  v1  and  v2c,  v3  Linux/Unix  pla:orms.  DB  backend  should  be  configurable  to  use  any  OS/CS  –  RDBMSHandle  64bit  valuesGather  SNMP  data  at  1min  intervalsCompiled  not  interpreted.191
  20. 20. DefinitionWhat are the requirements for the ITInfrastructure Monitoring System?1Non-FunctionalUser Management tools, Role based access controlOwnership of devicesGraphs should be created on demand, not in mass with every sampleAuthentication framework, such as LDAP, ShibbolethData Importing/Exporting formats XML, CSV, XLSReconcile missing data and identify the network fault.Keep at least 25 months of data at 1 minute intervalsImport/Export data and templatesScale to thousand of devicesHandle more than 64K outstanding requestsMemory footprint should not increase with the number of devices being monitored20
  21. 21. DefinitionWhat are the requirements for the ITInfrastructure Monitoring System?1FunctionalNetwork  fault  determinaQon  -­‐  Logic  hierarchyAuto  topology  creaQonInterface  Discovery  should  be  automaQc  for  switches  and  devicesTopographic  map  of  the  devices.Device  Auto  discovery  capabiliQes  Threshold  triggeredAlerQng  lists  and  scheduled  alerts  –  alert  scheduleMobile  alerQng.  SMS/Email  or  PushNoQficaQonsIndependent  probing  capabiliQesAgentless  non-­‐intrusive211
  22. 22. DescriptionCacti0.8.8aGNU General Public LicenseMonitoring Systemhttp:///cacti.netPHPNetwork AccessWeb Server (Apache), MySQL, PHP, RRDTool, net-snmp. Runs over Unix and Windowshttp://docs.cacti.net/ ; http://www.cacti.net/downloads/docs/html/http://blog.cactiusers.org/Comprehensive Linux Install Guide by Lee Carter, Solaris Install Guide by JavierVidal Postigo, German Install Guide bySebastian Larisch.Cacti 0.8 Beginners Guide,Thomas Urbanhttp://forums.cacti.net; http://cacti.net/mailing_lists.phphttp://blog.cactiusers.org/http://bugs.cacti.net/https://help.ubuntu.com/community/Cactisvn checkout svn://svn.cacti.net/cacti; http://www.cacti.net/downloads/cacti-0.8.8a.tar.gzWindows, Linux/UnixPIA - Plugin Architecturehttp://docs.cacti.net/pluginshttp://gregsowell.com/?page_id=86; http://www.transitiv.co.uk/services/training/cacti; http://www.credativ.co.uk/services/training/monitoring/cacti/http://www.transitiv.co.uk/services/consultancy/cactihttp://www.transitiv.co.uk/services/consultancy/cactiIdentificationCacti222
  23. 23. 2IdentificationNagiosSub-category DescriptionName Nagios CoreVersion 3.4.4License GNU General Public LicenseType Monitoring SystemSite http://www.nagios.org/Language CHardware Network AccessSoftware C Compiler,Web Server (Apache), GD Library and Unix/Linux as OS.Official http://nagios.sourceforge.net/docs/3_0/toc.htmlNon-Official http://exchange.nagios.org/directory/Documentation/Nagios-Core-DocumentationRelevant http://www.fullyautomatednagios.org/wordpress/documentation/BooksNagios Core Administration Cookbook By:Tom Ryder; Nagios: Building Enterprise-Grade Monitoring Infrastructures forSystems and Networks, Second Edition By: David JosephsenOfficial http://library.nagios.com/; http://support.nagios.com/forum/; http://support.nagios.com/wiki/index.php/Main_PageNon-Official https://help.ubuntu.com/community/NagiosIssue tracker site http://tracker.nagios.org/my_view_page.phpRelevant http://nagiosplugins.org/supportSource http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-3.4.4.tar.gzPlatforms Linux/UnixModularity Plugin ArchitecturePlugins http://www.nagios.org/download/plugins; http://nagiosplugins.orgTraining http://www.nagios.com/services/training/Support http://support.nagios.com/; http://support.nagios.com/wiki/index.php/Main_PageConsulting http://www.nagios.org/support/servicepartners/23
  24. 24. 2IdentificationZabbixSub-category DescriptionName ZabbixVersion 2.0.4License GNU General Public License version 2Type Monitoring SystemSite http://www.zabbix.org/Language C (server, proxy, agent), PHP (frontend), Java (Java gateway)Hardware Network Access, 100MB Disk Space, 256M RAM, Pentium IV or equivalentSoftware Apache Web Server, MySQL, PostgreSQL, SQLite, Oracle or IBM DB2Official https://www.zabbix.com/wiki/doku.php; http://blog.zabbix.com/Non-Official https://s3.amazonaws.com/analyticarts/zabbix/Zabbix2-0Manual.pdfRelevant N/ABooks Zabbix 1.8 Network Monitoring By: Rihards OlupsOfficialhttps://www.zabbix.com/forum/; https://support.zabbix.com/secure/Dashboard.jspa; https://lists.sourceforge.net/lists/listinfo/zabbix-announce; https://lists.sourceforge.net/lists/listinfo/zabbix-usersNon-Official N/AIssue tracker site https://support.zabbix.com/browse/ZBXRelevant N/ASource http://sourceforge.net/projects/zabbix/files/ZABBIX%20Latest%20Stable/2.0.4/zabbix-2.0.4.tar.gz/downloadBinaries http://www.zabbix.com/download.phpPlatforms Cross PlatformModularity PluginsTraining http://www.zabbix.com/business_solutions.phpSupport http://www.zabbix.com/business_solutions.phpConsulting http://www.zabbix.com/business_solutions.php24
  25. 25. Qualification3DocumentationDocumentationDocumentationDocumentationCacti Nagios ZabbixOverallTechnicalUser2.00 1.00 2.001.36 1.09 1.181.67 1.67 1.67Score 1.68 1.25 1.62RoadmapRoadmapRoadmapRoadmapCacti Nagios ZabbixRoadmapProject activity2 0 23 3 3Score 2.5 1.5 2.5ScalabilityScalabilityScalabilityScalabilityCacti Nagios ZabbixOverallLinearScalable1.0 2.0 3.01.0 1.0 1.0Score 1.0 1.5 2.0SupportSupportSupportSupportCacti Nagios ZabbixSelfPaidCommunity1 0 11 1 11 1 1Score 3.0 2.0 3.0FunctionalityFunctionalityFunctionalityFunctionalityCacti Nagios ZabbixFunctionalNon-FunctionalTechnological0.8 1.0 1.00.7 0.7 0.91.3 1.3 1.3Score 0.9 1.0 1.1SenioritySenioritySenioritySeniorityCacti Nagios ZabbixLifespan 11 14 9Score 3.0 3.0 2.0253
  26. 26. QualificationSupport326
  27. 27. QualificationDocumentation327
  28. 28. QualificationPerformance328
  29. 29. QualificationCommunityData gathered from SourceForge.net, 2013CactiTop633CR16.3NagiosTop7,017CR40.9293
  30. 30. QualificationCommunity3CommunityOSS PackageCommunityCommunityType ScoreCactiNagiosZabbixORG 1COR 4ORG 1Data gathered from SourceForge.net, 2013ZabbixTop109CR8.1630
  31. 31. QualificationTotal Cost of Ownership (Cacti)3$ in Canadian Dollars (CAD)31Stage Driver/CostInitialAcquisitionYearYear 2 Year 3SelectionSelectionAcquisitionAcquisitionAcquisitionAcquisitionIntegrationIntegrationIntegrationUseUseUseUseRetirementRetirementUp-front evaluation study $852.20 $- $-Up-front proof of concept implementation $150.00 $- $-Software $- $- $-Customization for business needs $426.10 $510.00 $520.20Integration $1,917.45 $510.00 $520.20Hardware $1,210.00 $1,210.00 $1,210.00Migration (data and users) $- $- $-Training $213.05 $- $-Process and Best practice Change $421.10 $1,086.53 $1,108.27Cost of Support Services – in house $16,351.50 $16,678.53 $17,012.10Cost of Support Services – contracted $- $- $-Maintenance and upgrades $1,022.64 $5,786.09 $5,901.81Training $1,278.30 $1,303.87 $1,329.94Exit costs (in relation to hardware and software) $- $- $-Exit costs (in relation to changeover, retraining) $- $- $-Total Cost/Year $22,950.44 $26,175.29 $26,674.59Discount factor 5%TCO $72,073.92
  32. 32. QualificationTotal Cost of Ownership3$73,144.17Zabbix$74,422.47Nagios$72,073.92Cacti$ in Canadian Dollars (CAD)323
  33. 33. Valuation4Criterion Weight Cacti % Nagios % Zabbix % Perfect %FunctionalityLicenseCommunitySenioritySupportInteroperabilitySecurityRoadmapPerformanceScalabilityDocumentationTCO2 73% 78% 83% 100%1 100% 100% 100% 100%2 33% 100% 33% 100%1 100% 100% 67% 100%1 100% 67% 100% 100%2 84% 89% 63% 100%1 100% 100% 100% 100%1 83% 50% 83% 100%2 33% 33% 67% 100%2 33% 50% 67% 100%2 98% 73% 95% 100%1 100% 33% 66% 100%Final ScoreFinal PercentileFinal Score 12.77 12.99 13.15 18Final Percentile 71% 72% 73% 100%33
  34. 34. Valuation4Cacti Nagios Zabbix34
  35. 35. Selection• Insight into the deficiencies of Cacti• Zabbix’ scalability and core features fulfill most of UofTinstrumentation needs.• A change from Cacti to Zabbix would substantially change thecost or efficacy of the Enterprise Monitoring Solution• Zabbix implementation plus integration with the current Cactiinstance, in order to work as a distributable monitoringsystem, and take advantage of the features of both systems.535
  36. 36. Selection• Remarkable expertise of the HIG.• TCO of a second package is dwarfed by the other operatingcosts of the Data Centre.• Cacti scalability will improve• Spine• Isolated instances536
  37. 37. • Reveals advantages and disadvantages of given OSS• High level of detail supporting the decision.• The best solution might come from joining forces by creating ahybrid system• How to measure criteria and the flexibility to add or remove.Conclussions37
  38. 38. • Highlighting TCO hidden costs overlooked by SeniorManagement.• Hidden costs like: man-hours invested in self-training, lookingfor support in the community or documentation.• Shatters the illusion that OSS is free.• All this to avoid mistakes that often incur in unexpected costs.Conclussions38
  39. 39. • Implementing the model for additional kinds of software.• Implementing the model in the private sector. Downtimecosts, maintenance costs, etc.• Including Return On Investment (ROI)• Will be proposed to the internal use of HIG and eventually toEIS.Challenges39
  40. 40. An Integral Open Source Softwareselection model with a business case onIT Infrastructure Monitoring SystemBy José Manuel López LujánMay, 2013Docs: http://jmll.me/thesis-docSlides: http://jmll.me/thesis-de-ppt

×