DrupalCon Prague 2013

Monitorizando aplicaciones Drupal

Kris Buytaert  · 


Extracto de la transcripción automática del vídeo realizada por YouTube.

so I'm the last guy standing between you and bears some of you might expect them en torno here talking about distributed systems but he pulled this talk two weeks ago and during one of the tractor calls I got pulled out as being his backup so that's

why today I'll be talking about monitoring in an infrastructure monitoring Drupal in an infrastructure as code H if you feel like you're in the wrong talk and you don't want to see this feel free to actually still leave because I can understand

if you feel that way in 10 minutes you can also do but please bring me a beer then so yeah let me first introduce myself I'm pleased about that there's a faq out there I'm not related to dress but we do know each other since before Drupal existed

ages ago I used to be a software developer even wrote bhp and then I became an Operations person because I need to deploy stuff and I was the guy constantly rocking machines and putting stuff in production today my role is I'm the CTO of one of the larger

open-source consultancy firms in Europe we are in Nuits we have offices in Belgium the Netherlands in Kiev we do a lot of Drupal work but we're not a Drupal shop so if i look at what i do today i'm mostly building large-scale infrastructures doing

it the dev up style so doing continuous delivery doing automated infrastructure who can tell me what DevOps is this is DevOps track guys who can tell me what DevOps is are you all afraid to reply to questions or does nobody know who was in my talk last year

okay so nobody knows what DevOps is to pee okay be sure collaboration of operations and developers now it give that a 50-percent score so this is what DevOps is to me it's about culture it's about how developers and operations people work together

it's about automation and when we talk about automation we mean ultimate all the thing we want to test automation or ultimate the builds we want to automate the deployments with one automated monitoring basically when we talk about automation we think

about infrastructure as code and when we think about DevOps we also think about monitoring metrics and all that stuff and we also talked about sharing and that's the camps the clams keyboards which was coined by John Edwards Damon Edwards and John Willis

we have a podcast called DevOps cafe and the L the influence of the lean movement has been introduced by Jean Kim because they figured out well there's a lot of lean stuff in this and there's a lot of stuff which is based on and it's also cool

because if you had just the camps without the L in there lots of people figured out well if you make an anagram out of it it's just a scam which it's absolutely not so how many of you are testing your double coat okay some of you you have continuous

integration you have stuff where you actually put in place an environment where software is being pushed to production with a set of rules with a set of checks which you want to succeed and that's how big organizations work that's how organizations

work they're afraid of pushing software into production and they want to have tests in place that make sure that stuff goes the right way but for some reason on the infrastructure level on the actual operating system level we've been tolerating that

people logged on to machines manually and started deploying stuff in there we didn't allow the software developers to do that but the infrastructure people well that was fine so with the advent of clouds and large-scale deployments there's a lot of

new tooling that came on the market which allowed us to do this different and that's basically what infrastructure as code is about infrastructure as code makes us think again about how we build our infrastructure today how we model it how we can fastly

reproduce the platform and how we can basically have disaster recovery for free the same way we build software and if I look at a platform these days there's a large part of that which I want to completely reproducible think about it like Drupal core nobody's

going to touch this part or three skills a kitty and this part is completely in source codes everything there if i'm running a platform in production acceptance or testing it's identical then on top of that i have a part where i give it an identity

like the sides directory where you basically give this is the v host it's this site you give it an identity with some specific configuration enable these modules and for the operating system for the whole stack it's pretty similar you add some business

rules and the whole block down here that's something which is in version control which you can manage them which you can redeploy over and over and over again you need some scale out maybe you have some custom parts but it's all automated and that's

something you can rebuild the thing you need to add anything you need to back up the actual user generated content because that's something which you cannot version it's going to be volatile it's going to change frequently but the whole lower stack

you have to think you have to start thinking about that as code and make sure it can be reproduced infrastructure as code also means that as infrastructure people are doing this we need to start thinking as developers I mean I come from a development background

a lot of other people come from a development background but we really think about our infrastructure as code we have quality checks in there we also use version control we also use testing we also use continuous integration and continuous delivery and that

means we build up our core infrastructure that way we add the middleware deployment in this way apache solr engine eggs all the components that are used to build a website and we do this in an automated fashion we do continuous delivery of the full stack we

and for security rules in there so we actually tune the parameters for this firewalls and all stuff automatically so when we deploy stuff we deploy a host a service and the application with the monitoring and that's the link to the monitoring part configured

automatically so monitoring who likes monitoring really I mean about two years ago John Vincent losses on Twitter was really fed up with all the monitoring things we were having any basically tweeted with the hashtag monitoring sucks and he put up a git repository

put in all the different tools he know and we pretty much started looking at what is out there what tools are out there what do we need to change what's new and then how can we improve this thing which is monitoring to me basically the monitoring sucks

movement is a sub movement of the DevOps movement it's people who care about open source will care about monitoring and improving the monitoring space in the open source world and one of the reasons why monitoring sucks is well a lot of those tools are

[ ... ]

Nota: se han omitido las otras 3.402 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.