At some point a startup needs to grow, without losing agileness. It needs well-know processes. It needs developers to know about the infrastructure. It needs tools that expose knowledge, not that hide it. It needs scalable wokflows, based on self service tools, so system admins and release managers are not a bottleneck for developers. It needs tools that enforce processes, not tons of documentation.
So we implemented and put to work some systems to allow developers to do that:
-Tuenti-in-a-box: Private, replicable, virtualized development and testing environment, with all the features production platform has. No more shared development environments.
-Configcop: Test your application config changes in your development environment, promote it to staging and then to production. Easy, safe, and logged.
-Flow: Development, integration and release management of code made easy. Promote your own code to main integration branch, build and deploy it, release it, all pressing a button from your preferred ticketing system. Of course transparent information, traceability, stats.
All these tools are developing devops culture inside the company, making easy for developers to deploy and test their code, providing information about all stages and ensuring higher code quality by automating testing and other tedious, risky tasks, such as code versioning, tagging, build and distribution to app markets, etc. We would like to share how this ideas and tools helped in Tuenti's development processed, and allowed us to go from 2 releases per week, with multiple hotfixing in a single project, to a multiple project, multiple releases per day, reducing workload and time that code spends ready but unreleased from some days to some minutes.# vimeo.com/76750531 Uploaded 120 Plays 2 Likes 0 Comments
The aim is to explain the long and difficult way done in a classical and quite normal IT department in a classical company towards the DevOps philosophy. We would like to present in a few slides: * why we MUST go to DevOps (from a technical and organizational point of view) * What we practiced as technics and different improvements * Which learning way we used, based on agile practices, * The effort done by the people to destroy existing communication and collaboration barriers * What we would like to reach as level in the next months / years# vimeo.com/76750530 Uploaded 58 Plays 0 Likes 0 Comments
DevOps, when done right, usually goes unnoticed. It’s only when something breaks that all eyes turn to IT. If your boss only sees you when the app is down, however, that’s not really doing your career any favors. In this session we’ll talk about how to prove your value to the organization by looking at the positive side – that is, how much money you’ve saved your company. We’ll take a look at how you can use tools like Chef, Puppet, Sensu and Logstash to quantify your value to your company. After this session, you’ll be able to walk into a meeting with your boss ready to talk about your value to the company (and to ask for a raise).
Why devops matters?
Tools of the trade
Chef + Puppet
Logstash + Loggly + SumoLogic + Splunk
Fabric + Capistrano + Jenkins
Sensu + Graphite
Your real value
A case study in the cost of failure
Reactive to production failures
How to win
Maximum Visibility with Minimum Effort# vimeo.com/76750529 Uploaded 113 Plays 1 Like 0 Comments
Browse This Channel
More stuff from “DevOps Culture”
Heads up: the shoutbox will be retiring soon. It’s tired of working, and can’t wait to relax. You can still send a message to the channel owner, though!