Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Devops is not about Tooling

574 views

Published on

But tools are so much fun

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Devops is not about Tooling

  1. 1. Devops, it's not aboutDevops, it's not about toolingtooling But tooling is so much fun ! @KrisBuytaert
  2. 2. Kris BuytaertKris Buytaert ● I used to be a Dev,I used to be a Dev, ● Then Became an OpThen Became an Op ● Chief Trolling Officer and Open SourceChief Trolling Officer and Open Source Consultant @Consultant @inuits.euinuits.eu ● Everything is an effing DNS ProblemEverything is an effing DNS Problem ● Building Clouds since before the bookstoreBuilding Clouds since before the bookstore ● Some books, some papers, some blogsSome books, some papers, some blogs ● Evangelizing devopsEvangelizing devops
  3. 3. What's this Devops thing really about ?What's this Devops thing really about ?
  4. 4. World , 200X-2009World , 200X-2009 Patrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, JezzPatrick Debois, Gildas Le Nadan, Andrew Clay Shafer, Kris Buytaert, Jezz Humble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, andHumble, Lindsay Holmwood, John Willis, Chris Read, Julian Simpson, and lots of others ..lots of others .. Gent , October 2009Gent , October 2009 Mountain View , June 2010Mountain View , June 2010 Hamburg , October 2010Hamburg , October 2010 Boston, March 2011Boston, March 2011 Mountain View, June 2011Mountain View, June 2011 ........
  5. 5. Amsterdam , 5th aniverseryAmsterdam , 5th aniversery June 28-30June 28-30 Student Discounts AvailableStudent Discounts Available
  6. 6. devops, a definition:devops, a definition:
  7. 7. ● Adopt the new philosophy. We are in a new economic age. Western managementAdopt the new philosophy. We are in a new economic age. Western management must awaken to the challenge, must learn their responsibilities, and take on leadershipmust awaken to the challenge, must learn their responsibilities, and take on leadership for change.for change. ● Cease dependence on inspection to achieve quality. Eliminate the need for massiveCease dependence on inspection to achieve quality. Eliminate the need for massive inspection by building quality into the product in the first place.inspection by building quality into the product in the first place. ● Improve constantly and forever the system of production and service, to improveImprove constantly and forever the system of production and service, to improve quality and productivity, and thus constantly decrease costs.quality and productivity, and thus constantly decrease costs. ● Institute training on the job.Institute training on the job. ● Institute leadership The aim of supervision should be to help people and machines andInstitute leadership The aim of supervision should be to help people and machines and gadgets do a better job.gadgets do a better job. ● Drive out fear, so that everyone may work effectively for the company.Drive out fear, so that everyone may work effectively for the company. ● Break down barriers between departments. People in research, design, sales, andBreak down barriers between departments. People in research, design, sales, and production must work as a team, in order to foresee problems of production andproduction must work as a team, in order to foresee problems of production and usage that may be encountered with the product or service.usage that may be encountered with the product or service. ● Eliminate slogans, exhortations, and targets for the work force asking for zero defectsEliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity. Such exhortations only create adversarial relationships,and new levels of productivity. Such exhortations only create adversarial relationships, as the bulk of the causes of low quality and low productivity belong to the system andas the bulk of the causes of low quality and low productivity belong to the system and thus lie beyond the power of the work force.thus lie beyond the power of the work force. •Eliminate management by objective. Eliminate management by numbers and numericalEliminate management by objective. Eliminate management by numbers and numerical goals. Instead substitute with leadership.goals. Instead substitute with leadership. •Remove barriers that rob the hourly worker of his right to pride of workmanship. TheRemove barriers that rob the hourly worker of his right to pride of workmanship. The responsibility of supervisors must be changed from sheer numbers to quality.responsibility of supervisors must be changed from sheer numbers to quality. •Remove barriers that rob people in management and in engineering of their right to prideRemove barriers that rob people in management and in engineering of their right to pride of workmanship.of workmanship. ● Institute a vigorous program of education and self-improvement.Institute a vigorous program of education and self-improvement. ● Put everybody in the company to work to accomplish the transformation. ThePut everybody in the company to work to accomplish the transformation. The transformation is everybody's job.transformation is everybody's job.
  8. 8. William EdwardsWilliam Edwards DemingDeming 1986, Out of the Crisis.1986, Out of the Crisis. http://en.wikipedia.org/wiki/W._Edwards_Deminghttp://en.wikipedia.org/wiki/W._Edwards_Deming
  9. 9. C(L)AMSC(L)AMS ● CultureCulture ● (Lean)(Lean) ● AutomationAutomation ● MeasurementMeasurement ● SharingSharing Damon Edwards and John WillisDamon Edwards and John Willis Gene KimGene Kim
  10. 10. ““DevOps is a cultural andDevOps is a cultural and professional movement”professional movement” Adam JacobAdam Jacob
  11. 11. Whats in it for you ?Whats in it for you ? ● Faster time to marketFaster time to market • Features go live in hours vs yearsFeatures go live in hours vs years ● In a more safe (Secure)In a more safe (Secure) ● Reliable fashionReliable fashion • Fully automatedFully automated ● More happyMore happy {customers,developers,managers,investors}{customers,developers,managers,investors}
  12. 12. How did we get here ?How did we get here ?
  13. 13. The Old DaysThe Old Days ● ““Put this Code Live, here's a tarball” NOW!Put this Code Live, here's a tarball” NOW! ● What dependencies ?What dependencies ? ● No machines available ?No machines available ? ● What database ?What database ? ● Security ?Security ? ● High Availability ?High Availability ? ● Scalability ?Scalability ? ● My computer can't install this ?My computer can't install this ?
  14. 14. Devs vs OpsDevs vs Ops
  15. 15. (Historically) Different Goals(Historically) Different Goals DevelopmentDevelopment ● New releasesNew releases ● New FeaturesNew Features ● New platformsNew platforms ● New architecturesNew architectures ● Functional ReqFunctional Req OperationsOperations ● Stable PlatformStable Platform ● No DowntimeNo Downtime ● Scalable PlatformScalable Platform ● Non Functional ReqNon Functional Req
  16. 16. Culture,Culture, automation,automation, Measturement,Measturement, sharingsharing
  17. 17. Analyze ThisAnalyze This ● What are devs nagging aboutWhat are devs nagging about • Slow builds ?Slow builds ? • No enviroments ?No enviroments ? ● What are ops nagging aboutWhat are ops nagging about • Bad artefacts ?Bad artefacts ? • No logs ?No logs ? ● What is mgmt nagging aboutWhat is mgmt nagging about • Quality / Feedback ?Quality / Feedback ?
  18. 18. Are you speaking the sameAre you speaking the same language ?language ? ● Configuration management vs configurationConfiguration management vs configuration managementmanagement ● What is Operations ?What is Operations ? ● What is #devops ?What is #devops ?
  19. 19. Crossfunctional TeamCrossfunctional Team ● Build a project team with skills from all overBuild a project team with skills from all over • DevelopmentDevelopment • Continuous IntegrationContinuous Integration • TestingTesting • Infrastructure (HA/ Scale/ Performance)Infrastructure (HA/ Scale/ Performance) • DeploymentDeployment • MeasurementMeasurement ● Seat them together !Seat them together ! ● Goal = Help the businessGoal = Help the business
  20. 20. Shared BacklogShared Backlog ● CHALLENGE : Getting Non FunctionalCHALLENGE : Getting Non Functional Requirements in the development backlogRequirements in the development backlog • On team levelOn team level • On management levelOn management level • On business user levelOn business user level ● Put the Product Owner on CallPut the Product Owner on Call
  21. 21. There's a tool for thatThere's a tool for that ● RedmineRedmine ● GitlabGitlab ● TracTrac ● PhabricatorPhabricator ● TaigaTaiga
  22. 22. Enable CommunicationEnable Communication
  23. 23. There's a tool for thatThere's a tool for that ● Good old Irc,Good old Irc, ● Xmpp (ejabberd,openfire, …),Xmpp (ejabberd,openfire, …), ● JitsiJitsi ● Mattermost ,Mattermost , ● ……..
  24. 24. Build TrustBuild Trust ● ExperimentExperiment • DevDev • TestTest ● ProdProd ● Automate all theAutomate all the thingsthings ● Measure successMeasure success ● Measure FailureMeasure Failure
  25. 25. With great power ...With great power ... Your code will go to production..Your code will go to production.. You will be able to fix it ..You will be able to fix it .. You will have access to the logsYou will have access to the logs Access to the metrics...Access to the metrics...
  26. 26. While we talk about animals..While we talk about animals..
  27. 27. Your machines as CattleYour machines as Cattle
  28. 28. Treat your people as petsTreat your people as pets
  29. 29. BondBond ● Internal DevopsdaysInternal Devopsdays ● Internal Open Source DaysInternal Open Source Days ● Hack DaysHack Days ● Teach a collegue daysTeach a collegue days ● Ramdon Lunch meetupsRamdon Lunch meetups ● Eat CakeEat Cake ● Both inside and outside the officeBoth inside and outside the office
  30. 30. What tool?What tool?
  31. 31. Culture,Culture, Automation,Automation, Measurement,Measurement, SharingSharing
  32. 32. Automate all the thingsAutomate all the things ● BuildBuild • reproducable builds are undiscussablereproducable builds are undiscussable ● TestTest • testing reduces risktesting reduces risk • automate deployments of your test infraautomate deployments of your test infra ● DeployDeploy • Infrastructure as CodeInfrastructure as Code • 100% automation100% automation • Can you rebuild your infrastructure ?Can you rebuild your infrastructure ?
  33. 33. NirvanaNirvana An “ecosystem” that supports continuous delivery, fromAn “ecosystem” that supports continuous delivery, from infrastructure, data and configuration management toinfrastructure, data and configuration management to business.business. Through automation of the build, deployment, and testingThrough automation of the build, deployment, and testing process, and improved collaboration between developers,process, and improved collaboration between developers, testers, and operations, delivery teams can get changestesters, and operations, delivery teams can get changes released in a matter of hours — sometimes even minutes–noreleased in a matter of hours — sometimes even minutes–no matter what the size of a project or the complexity of its codematter what the size of a project or the complexity of its code base.base. Continuous Delivery , Jez HumbleContinuous Delivery , Jez Humble
  34. 34. How do we get there ?How do we get there ?
  35. 35. Use VersionUse Version Control,Control, No ExcusesNo Excuses Also forAlso for scripts/config/cookbooksscripts/config/cookbooks ,manifests,etc,manifests,etc
  36. 36. Infra Requirements:Infra Requirements: ● GitGit • GitlabGitlab • GithubGithub • GitoliteGitolite • GitblitGitblit • GitoriousGitorious
  37. 37. Continuous IntegrationContinuous Integration ● BuildsBuilds ● Nightly BuildsNightly Builds ● Builds with testsBuilds with tests ● Nightly Builds with testsNightly Builds with tests ● Frequent integrationFrequent integration ● Continuous IntegrationContinuous Integration
  38. 38. CI ToolsCI Tools ● HudsonHudson ● JenkinsJenkins A zillion pluginsA zillion plugins ● Go (Cruise Control)Go (Cruise Control) ● TravisTravis ● GitlabCIGitlabCI ● Also test your (Puppet/Chef/CFengine)Also test your (Puppet/Chef/CFengine)
  39. 39. Infra Requirements:Infra Requirements: ● Issuetracker / PM ToolsIssuetracker / PM Tools ● Communication ToolsCommunication Tools ● GitGit ● CI ToolCI Tool
  40. 40. Build PipelinesBuild Pipelines
  41. 41. Jenkins PipelineJenkins Pipeline
  42. 42. A pipelineA pipeline ● Checkout codeCheckout code ● SyntaxSyntax ● StyleStyle ● Code CoverageCode Coverage ● TestsTests ● BuildBuild ● More TestsMore Tests ●
  43. 43. Test AutomationTest Automation ● Unit testsUnit tests ● Regression testsRegression tests ● TDDTDD ● BDDBDD ● SeleniumSelenium ● FitnesseFitnesse ● CucumberCucumber
  44. 44. Can you Automate yourCan you Automate your Pipeline Creation ?Pipeline Creation ? ● Puppetizing PipelinesPuppetizing Pipelines ● Templating PipelinesTemplating Pipelines ● Workflow PluginWorkflow Plugin ● JJBJJB ● ……
  45. 45. Can you Automate yourCan you Automate your Pipeline Creation ?Pipeline Creation ? ● Pipeline as CodePipeline as Code ● Jenkins Job DSLJenkins Job DSL ● Pipeline PluginPipeline Plugin
  46. 46. devops (<)> continuous delilverydevops (<)> continuous delilvery
  47. 47. How many times a day ?How many times a day ? ● 10 @ Flickr10 @ Flickr ● Deployments used to be painDeployments used to be pain ● Nobody dared to deploy a siteNobody dared to deploy a site ● Practice makes perfectPractice makes perfect ● Knowing you can vs constantly doing itKnowing you can vs constantly doing it
  48. 48. " Our job as engineers (and ops, dev-ops, QA," Our job as engineers (and ops, dev-ops, QA, support, everyone in the company actually) is tosupport, everyone in the company actually) is to enable the business goals. We strongly feel thatenable the business goals. We strongly feel that in order to do that you must havein order to do that you must have the ability tothe ability to deploy code quickly and safelydeploy code quickly and safely. Even if the. Even if the business goals are to deploy strongly QA’d codebusiness goals are to deploy strongly QA’d code once a month at 3am (it’s not for us, we push allonce a month at 3am (it’s not for us, we push all the time), having a reliable and easy deploymentthe time), having a reliable and easy deployment should beshould be non-negotiablenon-negotiable."." Etsy Blog upon releasing DeployinatorEtsy Blog upon releasing Deployinator http://codeascraft.etsy.com/2010/05/20/quantum-of-deployment/http://codeascraft.etsy.com/2010/05/20/quantum-of-deployment/
  49. 49. Infrastructure as CodeInfrastructure as Code ● Treat configuration automation as codeTreat configuration automation as code ● Development best practicesDevelopment best practices • Model your infrastructureModel your infrastructure • Version your cookbooks / manifestsVersion your cookbooks / manifests • Test your cookbooks/ manifestsTest your cookbooks/ manifests • Dev/ test /uat / prod for your infraDev/ test /uat / prod for your infra ● Model your infrastructureModel your infrastructure ● A working service = automated ( Application Code + InfrastructureA working service = automated ( Application Code + Infrastructure Code + Security + Monitoring )Code + Security + Monitoring ) ● IAC -ne scriptingIAC -ne scripting
  50. 50. Surviving the 10Surviving the 10thth floor testfloor test
  51. 51. Pick your poisonPick your poison ● CfEngineCfEngine ● PuppetPuppet ● ChefChef ● AnsibleAnsible ● SaltSalt • Or combine themOr combine them
  52. 52. Infra Requirements:Infra Requirements: ● GitGit ● CI ToolCI Tool ● Test FrameworksTest Frameworks ● IAC FrameworkIAC Framework • Includes ReportingIncludes Reporting • Also requires the aboveAlso requires the above
  53. 53. Culture Hack:Culture Hack: Set up CI / CD for your infrastructure first, If theSet up CI / CD for your infrastructure first, If the people running your infra don't know howpeople running your infra don't know how CI/CD works , how do you expect them toCI/CD works , how do you expect them to support / teach your application teams ?support / teach your application teams ? You also get them to learn about the toolingYou also get them to learn about the tooling they will need to support and they will share thethey will need to support and they will share the pain and the joy of the application developerspain and the joy of the application developers
  54. 54. Spinning up stacksSpinning up stacks ● ForemanForeman ● Terraform ..Terraform .. ● Pitfall :Pitfall : • Require a CI Tool to deployRequire a CI Tool to deploy
  55. 55. Why ops like to packageWhy ops like to package ● Packages give you featuresPackages give you features •Consistency, security, dependenciesConsistency, security, dependencies ● Uniquely identify where files come fromUniquely identify where files come from •Package or cfg-mgmtPackage or cfg-mgmt ● Source repo not always availableSource repo not always available •Firewall / Cloud etc ..Firewall / Cloud etc .. ● Weird deployment locations , no easy accessWeird deployment locations , no easy access ● Little overhead when you automateLittle overhead when you automate ● CONFIG does not belong in a packageCONFIG does not belong in a package
  56. 56. #devopsdays 2010 Open#devopsdays 2010 Open Space ConclusionsSpace Conclusions ● Always package software YOU deployAlways package software YOU deploy • Exceptions: code that changes faster thanExceptions: code that changes faster than you can package it. (Very rare)you can package it. (Very rare) ● Do NOT package Config FILES ,Do NOT package Config FILES , • Use a cfgmgmt tool for thisUse a cfgmgmt tool for this ● Languages are still reinventing the wheel :(Languages are still reinventing the wheel :(
  57. 57. fpmfpm
  58. 58. SaySay thanks tothanks to JordanJordan SisselSissel
  59. 59. A pipelineA pipeline ● Checkout codeCheckout code ● SyntaxSyntax ● StyleStyle ● Code CoverageCode Coverage ● TestsTests ● BuildBuild ● More TestsMore Tests ● PackagePackage
  60. 60. Repository ManagementRepository Management
  61. 61. Repository ManagementRepository Management ● PulpPulp • Pro : MirroringLovePro : MirroringLove • Con : Mongo, Stability, .deb, forgeCon : Mongo, Stability, .deb, forge ● PRMPRM ● Yum Repo Server by IS24Yum Repo Server by IS24 ● AptlyAptly
  62. 62. Deploy SoftwareDeploy Software ● Repo per environmentRepo per environment ● Package {'mysoftware': ensure => present}Package {'mysoftware': ensure => present} ● Strict versioning in config ?Strict versioning in config ? Ensure => '0.98.4'Ensure => '0.98.4'
  63. 63. Deployment isn't the EndDeployment isn't the End
  64. 64. OrchestrationOrchestration ● Manage 1000 nodes,Manage 1000 nodes, ● TriggerTrigger •UpgradesUpgrades •Config RunsConfig Runs •Service ChangesService Changes ● Think :Think : •McollectiveMcollective •ConsulConsul •RundeckRundeck •AnsibleAnsible
  65. 65. The New DaysThe New Days ● ““Put this Code Live, here's Docker Container”Put this Code Live, here's Docker Container” NOW!NOW! ● No machines available ?No machines available ? ● What database ?What database ? ● Security ? What distro is this even ?Security ? What distro is this even ? ● High Availability ?High Availability ? ● Scalability ?Scalability ? ● How do we monitor his ?How do we monitor his ? ● How did you build this ?How did you build this ?
  66. 66. If all you know is docker, every whale looks like aIf all you know is docker, every whale looks like a private cloudprivate cloud Image Build by devs,Image Build by devs, maintained by nobodymaintained by nobody
  67. 67. Closing the gaps between dev and opsClosing the gaps between dev and ops AgainAgain ● Who build this ?Who build this ? ● What about SecurityWhat about Security ● How do you even build a containerHow do you even build a container ● How do you build the hosts that run theHow do you build the hosts that run the containers ?containers ? ● Infrastructure as code ++Infrastructure as code ++
  68. 68. Now:Now: ● Use containers to build, test, packageUse containers to build, test, package ● Spin up development environmentsSpin up development environments ● Teach your developers about stateTeach your developers about state ● Learn how to monitor, manage containersLearn how to monitor, manage containers In 18 months:In 18 months: ● Move to productionMove to production
  69. 69. Culture,Culture, Automation,Automation, Measurement :Measurement : measure all the thingsmeasure all the things SharingSharing
  70. 70. Monitoring is usually anMonitoring is usually an aftertoughtaftertought ENOBUDGET, ENOTIMEENOBUDGET, ENOTIME
  71. 71. An 2008 OLS PaperAn 2008 OLS Paper ● We have bloated Java toolsWe have bloated Java tools ● Some open Core stuffSome open Core stuff ● DYI folks want traditional NagiosDYI folks want traditional Nagios ● DBA RequiredDBA Required
  72. 72. #monitoringsucks#monitoringsucks ● John Vincent (@lusis), june 2011John Vincent (@lusis), june 2011 ● A sub #devops movementA sub #devops movement ● https://github.com/monitoringsucks/https://github.com/monitoringsucks/
  73. 73. Why #monitoringsucksWhy #monitoringsucks ● Manual config (gui)Manual config (gui) ● Not in sync with realityNot in sync with reality ● Hosts onlyHosts only ● Services sometimesServices sometimes ● Aplication neverAplication never ● Chaos or out of sync with realityChaos or out of sync with reality ● Alert FatigueAlert Fatigue
  74. 74. What we wantWhat we want ● Small , well suited componentsSmall , well suited components • CollectCollect • Transport / MangleTransport / Mangle • StoreStore • AnalyseAnalyse • Act / AlertAct / Alert • VisualizeVisualize
  75. 75. #monitoringlove#monitoringlove • • Ulf Mansson #devopsdays Rome 2011Ulf Mansson #devopsdays Rome 2011 • A new era of toolingA new era of tooling • #monitoringlove hacksessions @inuits#monitoringlove hacksessions @inuits • #monitorama#monitorama
  76. 76. Infra Requirement:Infra Requirement: ● System Checks,System Checks, ● Basic Alerting,Basic Alerting,
  77. 77. Automation ofAutomation of #monitoring#monitoring brought backbrought back thethe #love#love
  78. 78. AutomationAutomation
  79. 79. Automation gives , automated maintainedAutomation gives , automated maintained monitoring of the services we define.monitoring of the services we define.
  80. 80. Monitoring aMonitoring a serviceservice vsvs Monitoring aMonitoring a ServiceService
  81. 81. CollectD all the metrics,CollectD all the metrics, at high intervalsat high intervals
  82. 82. Infra Requirements:Infra Requirements: Metric Collection,Metric Collection, TSDB,TSDB,
  83. 83. Oldschool graphiteOldschool graphite
  84. 84. GraphiteGraphite ● Graphing at ScaleGraphing at Scale ● Graphing at EaseGraphing at Ease ● Any metric is a graphAny metric is a graph ● echo "somestring $somevalue $timestamp" |echo "somestring $somevalue $timestamp" | nc <%= graphitehost %> 2003nc <%= graphitehost %> 2003
  85. 85. Graphite++Graphite++ ● DashboardsDashboards • GrafanaGrafana ● Engines :Engines : • InfluxDBInfluxDB • CyaniteCyanite ● PrometheusPrometheus
  86. 86. GrafanaGrafana
  87. 87. Triggers on GraphsTriggers on Graphs ● Export Java MetricsExport Java Metrics ● JMXTransJMXTrans ● Export JMXConfigsExport JMXConfigs ● Configure NRPEConfigure NRPE CheckCheck ● Export NagiosCheckExport NagiosCheck ● Collect JMX ExportsCollect JMX Exports on JMXTransNodeon JMXTransNode ● Graph EmGraph Em Collect Icinga ConfigsCollect Icinga Configs on Icingaon Icinga
  88. 88. AggregationAggregation ● Alert on streamsAlert on streams ● Alert on aggregated metricsAlert on aggregated metrics
  89. 89. Math 101Math 101 ● f(x)f(x) ● f'(x)f'(x) ● f''(x)f''(x) ● ... statistics 101... statistics 101
  90. 90. But I have log files..But I have log files..
  91. 91. Logs and MetricsLogs and Metrics ● Graylog2Graylog2 ● ELSA (Enterprise Log Search and Archive)ELSA (Enterprise Log Search and Archive) ● ELK StackELK Stack
  92. 92. ● Collect fromCollect from anywhereanywhere ● FilterFilter ● Send anywhereSend anywhere ● QueingQueing
  93. 93. Self Service MetricsSelf Service Metrics ● Being able to add new metricsBeing able to add new metrics ● Build your own dashboardsBuild your own dashboards ● Look at metrics / logs on all platformsLook at metrics / logs on all platforms ● Learn from the LogfilesLearn from the Logfiles ● Learn from the platformLearn from the platform ●
  94. 94. Culture,Culture, Automation,Automation, Measurement,Measurement, SharingSharing
  95. 95. DashboardsDashboards
  96. 96. Visualize Business MetricsVisualize Business Metrics ● $revenue$revenue ● #sales#sales ● signupssignups ● conversionsconversions ● Api callsApi calls ● Application useApplication use
  97. 97. SharingSharing ● Open SpaceOpen Space ● Open SourceOpen Source ● GithubGithub ● Talk about ExperiencesTalk about Experiences ● Publish the codePublish the code
  98. 98. FoodFood
  99. 99. Quiz Time :Quiz Time : Which tool did I forget ?Which tool did I forget ?
  100. 100. YouYou
  101. 101. It's not about the toolsIt's not about the tools It's about changeIt's about change It's about the peopleIt's about the people
  102. 102. ContactContact Kris Buytaert Kris.Buytaert@inuits.euKris Buytaert Kris.Buytaert@inuits.eu Further ReadingFurther Reading @krisbuytaert@krisbuytaert http://www.krisbuytaert.be/blog/http://www.krisbuytaert.be/blog/ http://www.inuits.eu/http://www.inuits.eu/ InuitsInuits Essensesteenweg 31Essensesteenweg 31 2930 Brasschaat2930 Brasschaat BelgiumBelgium 891.514.231891.514.231 +32 475 961221+32 475 961221

×