$30 off During Our Annual Pro Sale. View Details »

DevOps isn't just for the Web

DevOps isn't just for the Web

These are my slides for the #ChefConf 2012 Ignite.

When we hear or read about DevOps usually is about how web operators can work better with the other teams (like developers, QA or business people) to deliver value, but we read less about other kind of development business.

I'd like to talk about how this DevOps culture fit also in other enviroments like the Desktop and distros ones.

Juanje Ojeda

May 18, 2012
Tweet

More Decks by Juanje Ojeda

Other Decks in Technology

Transcript

  1. DevOps isn't just for the Web Let's see with one

    example
  2. Ignite •This is my first English talk •Spanish jokes aren't

    much funny in English... •I'm going to oversimplify some concepts •I'm not web operator •I came from working with Linux distributions and desktop environments Disclaimer
  3. Ignite •This is my first English talk •Spanish jokes aren't

    much funny in English... •I'm going to oversimplify some concepts •I'm not web operator •I came from working with Linux distributions and desktop environments Disclaimer
  4. Ignite Background

  5. Ignite Guadalinex •Ubuntu derivative distribution •Open Source •Different flavors for

    different user cases: • Centros Guadalinfo (Civic centers) • Schools • Libraries • E-Government kiosks • ...
  6. Ignite Guadalinex Guadalinfo •> 750 centers all over Andalusia •~

    750.000 users •Deploy new centers and versions •Remote support and deliver bugfixes •Metrics •Upstream security upgrades
  7. Ignite The value chain •Business people •Desktop applications developers •Debian/Ubuntu

    developers •Deployable system developers •Support team
  8. Ignite Integrators as a facilitators •~ Operators •They care about

    stability and security •Integrate apps into the distro •Deploy the final product
  9. Ignite Developers... well, are developers •They look for better features

    •They like the last tools and libraries •They usually don't work on the final system
  10. Ignite Developers and Integrators Before was the Wall

  11. Ignite Developers and Integrators And a lot of technical debt

    and support team and...
  12. Ignite •Communication •Common sense •Empathy •Automation over human memory •Work

    as a team to deliver value DevOps (mostly) is about:
  13. Ignite •Why can't I use that lib version? •Why did

    we deliver that feature? •Why can't I add this change after that date? It's a simple change Other people's shoes:
  14. Ignite When you experience other people's problem, you change your

    attitude to them Other people's shoes:
  15. Ignite •Desktop developers make apps easy to package •Integrators fix

    easy bugs at the apps •Support team know better why things break •All can alert the right person when something breaks Some rotation helps
  16. Ignite •CI build our packages, create the repository and the

    final ISO •Everybody at the team see the project's status •Less manual things to do •Early detection of mistakes and bugs Automation and CI saved our lives
  17. Ignite •Use local VM like Vagrant for developers •Agile system

    like Kanban for better coordination •Tools like Chef for manage changes and deploy nodes •Improve the monitoring and metrics (logstash, graphite, sensu...) This started 5 years ago, now we can do better
  18. Ignite •Mobile developments •Desktop applications (LibreOffice, Firefox...) •Hardware •Etc This

    is just an example, those ideas could works also with:
  19. Ignite More links to connect to the chain Translators App's

    last version
  20. Ignite More links to connect to the chain Documentalists Designers

    Support staff
  21. Ignite DevOps could be called *.* Thanks Juanje Ojeda @juanjeojeda