 They don't have wireless mics for us. So I'll be basically doing a little bit of podium hugging today. I apologize in advance I guess we can go ahead and get started This is the state of Drupal DevOps if you're in the wrong room, you're going to realize it really quick a Lot of people Have all kinds of interesting responses when they hear the word DevOps some are good some are bad some are confusion Some are you're crazy some are you don't know what you're talking about And everything in between the best one though is when the operations people stand up and say I've been doing this my entire life Why are you calling it something? I've never heard So it's a neat little balance This is Drupal con Austin if you were confused about that I cannot help My name is Kevin bridges on the internet some kind of known as cyber swat Director of technology at a company called new media Denver new media Denver is a very interesting place We are specializing in DevOps implementations. We are specializing in consulting management workflow issues Deployment issues things that we have seen in the enterprise repeatedly have been able to isolate and help people with So Let's get right into it Basically cyber swat does not mean what you think that it does I know that lots of people have neat connotations that they associate with that, but it's not what you think I'm not a Drupal developer or a DevOps engineer That's gonna be shocking to a lot of people. I used to be quite good at Drupal I am no longer quite good at Drupal, but I can help out with Implementing it I can help out with deploying it and I can make it run really well I'm an open source technologist. Sure and simple DevOps is not equivalent to open source So if you walk into a DevOps conversation and you think that somebody is going to immediately start having the same Conversations that a typical open source developer will have you are wrong There's reasons for that I think a lot of that has to do with the fact that DevOps kind of spring from the enterprise and reality Drupal knows about DevOps specifically because We have people that had to maintain our success. So as developers we got larger We were doing bigger sites eventually those bigger sites started working with more ingrained operations teams Those teams had to figure out what this Drupal thing was They had to figure out what memcache was they had to figure out what a whole host of things were that were specific to our environment Our code is not written very performant Tends to take a little bit more resources to operate than most systems I'm also the director of technology at New Media Denver basically covered that as far as Drupal is concerned I've worked on some pretty interesting sites worked With a lot of really good people along the way and was able to do a lot of really neat things one of the first big ones I think for the Drupal community in general was popular science. We launched that very early on It was one of the very first Drupal six sites. They hit the the airwaves And it was well received we did some very extensive write-ups about it Really tried to use open source to help people understand how we did what we did and what they needed to do to Reproduce what we did and I think that's the first time that anybody wrote a case study to that magnitude or for that goal on Drupal.org Another site that I was heavily involved in was examiner calm Basically, we launched examiner calm a couple months before Drupal 7 was released I had a very interesting team of people working on it some very talented individuals as well We started introducing things like MongoDB at that time Basically Examiner calm is a top 50 website property in the United States. It was a high traffic scenario It involved many servers many people and a lot of organization Basically became a release manager at a certain point during that process to be able to to start bridging that gap between What we needed to do to keep the site running what we needed to do to get our releases out there and and everything in between That also involved things like talking to a very focused and very Opinionated development team that very much had things that they were accustomed to doing that needed to change to be able to grow so it was a combination of managing technical and managing people and To totally different things And then I moved right into the top secret space Yeah That is a bit of a pain point for me because I can't talk about what it is that I do As a result of that and I'm an open-source developer. I didn't get in this to be top secret I got in this because I enjoy talking I enjoy teaching I enjoy doing what I do and I'm doing it to make the world a better place When I have a top secret Project it doesn't tend to necessarily necessarily align with all of those. I think principles that I'm looking for I've worked at some neat companies along the way a company called Ping vision very early on Definitely not the same company today Worked at a company called bonnier corporation bonnier corporation 250 year old sweet Swedish company Basically helped them set up a system as a result of doing pop-side to migrate all the rest of their magazines from Java based CMS platforms over to Drupal so lots of vignette lots of data migrations lots of repetitive work It was a very interesting project to be involved with that's some really cool people there, too Ended up working for another company called third digital people Might or might not know who that is but it's a large company as well and then worked for Ironically, Hakuya So I've also done some things with Drupal con I've served as a coder track chair and a devops track chair for multiple Drupal cons I've been involved since Drupal con Denver on a Drupal con level I'm no longer involved That that's a hard pace to maintain Each project basically led me more into devops and further and further from open source and and again That's just a huge pain point for me. I don't understand that It just drives me crazy and we'll get to that a little bit more I'm on my way back to open source and I'm bringing devops with me So basically the intent of what I'm doing why I'm presenting this data why I'm standing up here and talking about devops Even though everybody hates the word devops is because it's a necessity Somebody has to do it. We have to talk. We have to communicate. We have to start working together And if we're not then we're missing great opportunities so Mandatory we're hiring plug if anybody likes what I say if you don't like what I say if you can do what I'm saying better Come talk to me Please because I want to work with you if you can contribute to this conversation Even if you're running another company come talk to me There is things that we can do together to make this whole system a better thing So this is going to be done a little bit differently basically we're dealing with a lot of data So I'm going to do it the open source way, which is a little bit different. Here's an example I sent an email to Gene Kim Gene Kim is a very prolific blogger. He works at public labs He wrote the Phoenix project, which is an awesome book if you guys haven't read it If you need to understand the principles of DevOps go out and buy that book Basically what they do in that book is they equate what we do in the technology space What we think is so new unique to old school industry practices So they literally took a 1920s manual that talked about how to move a production line from point A to point B How to find bottlenecks in that production line how to identify weak points and how to get your team to work together This is not rocket science. This is stuff that the human race has been doing for a very long time They basically replaced a box with a computer and rewrote the book. It's very interesting All of the data that I'm going to show you is up on this project page right now So if you go to Drupal or a project DevOps underscore survey, you will be able to download the database It's a scrub database of all the respondents. There's a PDF document that has a lot more data That's in the slide you will be able to dissect it and the data scientists in the room We'll be able to tell me everything that I did wrong with what I'm about to present and I look forward to that conversation Please make use of this data The goal is that we need to track metrics We need to be able to identify where we have come from What we are doing and where we are going and until we can do those three things as a community Then we're just kind of lost Another one this presentation if you don't like the way I talk you can download this presentation from github.com New media Denver slash presentations. It's already up and online Everything that I do goes into the public space because our organization has identified that if you want to be truly Successful you need to be able to separate what makes you a unique snowflake and what those structural components are and you need to develop workflows that Help your engineers and your operations people and everybody in between Become public-facing figures if you're doing DevOps correctly if you're separating your data from your structure And you're not being forced into a business situation where you have to cut corners You have to keep that snowflake data Then you're basically going to instill a workflow where you have the ability to get more efficient at what you're doing You're starting to work in very structured ways and it changes everything It's it's very slow at first. It takes a little bit to get going, but it's worth the effort Basically think of it like Pilates, right? So the first time that you start doing Pilates or at least for me I thought it was just dickulous couldn't move couldn't do anything. I didn't know what the hell was going on Ended up started doing it for a couple weeks stuck with it. I'm a stubborn person. I don't quit very well Eventually it got to the point where it started being okay Wasn't totally comfortable with it, but eventually I got to that point where it was like well Why haven't I been doing this my entire life? I mean, I'm losing weight. I'm more active. I'm thinking better This just makes no sense that I wasn't doing this thing before DevOps is that DevOps is very painful at first You have to understand it you have to define it and then you have to look at yourself You have to do introspection you have to find out what your organization is what your organization is trying to accomplish And then you have to give it the right tools the right workflow and the right methodologies to accomplish it If you're not doing those in an open space, then you're recreating the wheel and your organization is investing a lot of money in you Doing that so basically what ends up happening is the moment that you think that You're you're unique you're really not and you're spending a lot of money And you're not being as efficient as you could be. It's a very interesting paradigm It just starts to resonate after a little while so Again back to I'm gonna say a lot of crazy things during this presentation I expect people to tell me where I'm wrong I look forward to it because I know that everything that I'm saying is likely wrong. I'm only a person I'm just trying to figure this out. I have a little bit of data that I've been able to collect to help make some points But show me where I mess up and let's talk in room 10 B blink reaction this Thursday 1045 to 1145 I have Bob scheduled There's some conversations that I want to engage in there So let's get down to it. What is DevOps? Survey says Oh that they actually did is there was a survey going on at the same time from the DevOps people I Have not answered that because I do have a lot of respect for DevOps, but I had no idea what they were talking about right Yeah So that's what Drupal thinks of DevOps basically through and through And it's an interesting paradigm because the people that can benefit the most from using DevOps are the people that have no idea What's going on with DevOps and the challenge that I've been finding is that it's a very tactful and deliberate conversation to be able to have somebody Understand number one that they need DevOps number two how to do it and the number three how it can impact them directly What tends to happen is something totally different but let's get back to the presentation. What is DevOps? We need to define that right? I mean, that's why we're here. So let's ask everybody that took the survey. What is DevOps? Survey says So basically what that was was a dev cloud or Word cloud of everybody's response the people that claim to know DevOps the people that claim to implement DevOps They can't even tell you what DevOps is because DevOps is not a thing. It's a buzzword. It's a marketing term It is designed to get you to think about what you're doing in a different way than what you're accustomed to doing It's the same thing as agile all over again It's quite interesting. Most people throw DevOps around like it's just a thing I'm sure most of you have seen the DevOps in a box video if you haven't Google for it. It is phenomenal It is it's people are making a joke of it now So there there's schools of thought that say I will not even consider your company if you say that you're hiring a DevOps engineer I will not consider you if you say that you are a DevOps practitioner because you don't get it and I disagree with that But we'll get to that later So why are we here? Because we all need virtualized dev environments. I read the session proposals for Drupalcon many times It tends to be a natural first step for development shops to want to virtualize their development environments So here's typically how that that happens and in this tweet. I just oh my goodness So this tweet is a very typical tweet from a very smart person who I admire greatly He is trying to get started in vagrant development. He's associated with Drupal. He doesn't say that he wants to do Drupal here He's just saying local vagrant development. So what immediately happens is you get all kinds of cool comments that are really helpful Yeah, again helpful and then you get some even more knowledgeable people in the virtualization space Basically schlepping their their solution that they've been using for X amount of time without ever asking the original poster Why he wanted to use vagrant in the first place or what he was trying to accomplish from it or what his long-term vision was or Anything like that. So immediately start getting recommendations. Oh that I should jump in and download this He's already starting to feel a little bit overwhelmed. He needs a session at Drupalcon I think that's a great idea But what are we going to talk about? I mean all that I've heard is vagrant virtualization. How does that apply to anything? And it goes on and on you get you know Yeah, it's sorry about that But basically what ended up happening is there a lot of good solutions out there There's a lot of people working on this problem because all of us are dealing with it every single day if you're running a development shop I'm sure that and I have the data to back it up that you've realized that virtualization is becoming a thing Dockers going to come up pretty soon core OS is going to be involved There's a lot of neat stuff happening in this space right now people need to use this stuff But where do you start? What do you do? It's pretty interesting and basically what it leads to is eventually this Complete in total option paralysis you have no idea what's going on You think you're happy because you just learned a lot of stuff and in the end you're laying on the floor not doing anything So it's pretty interesting. I don't know Maybe I'm stretching. I don't know, but I don't think that I am so let's try it again Why are we here? Maybe we'll get it right this time It's real simple. We're here because of culture Automation measurement and sharing those of you in the DevOps space. No, this is cams This is the simplest definition that you will ever get Doesn't even say DevOps anywhere doesn't even have those letters in it But this is everything that DevOps is this is everything that we accomplished through the agile movement through being able to Communicate more efficiently. There's schools of thought that say that silos are bad But silos, you know as Kevin bearer said in a recent presentation have been around since the days of Plato get over it They're gonna be an enterprise. You need them to succeed in enterprise if you don't understand that then you're probably Missing a couple of points So what does that bring us back to it brings us back to sharing the enterprises the companies the organizations that are capable of understanding what their snowflake Business model is and what their structure is are the ones that are going to be successful so We still haven't really quite nailed down DevOps as it relates to the Drupal community This is Notorious in so many ways But basically for this story, I'm gonna tell you Basically just think of DevOps as bananas, right? Pretty simple. They're really sweet. They're really good. They're really nutritious. They have a lot of value to certain types of people Those types of people tend to be monkeys These monkeys like their bananas a lot They basically find out eventually that in order to succeed in order to survive you need to Eat bananas because it's the only food on the island if you're eating your bananas You're able to do other work. You're able to do other things Eventually that monkey gets smart. He's like man, these bananas are good So I'm gonna tell my friends about these bananas and these little monkeys are all starting to get together They're starting to share. They're starting to talk. They're like, hey, these bananas. They're so great I can do x y and z with them here Let me show you how to do that and it starts to grow it starts to spread But what ends up happening along the way is monkeys start getting bigger Eventually you get a couple little gorillas in there. So those gorillas now are Pretty good at moving bananas around. They're pretty Adequate at what they do. They understand the value and what they are doing. So they're helping out more and more monkeys It's still a little innocuous. It doesn't really mean anything right now It's just a couple monkeys helping each other, but eventually monkeys turn into gorillas and At some point you have a couple of gorillas that are pretty dominant in space And what ends up happening in a scenario like this if you look at it very carefully you have a lot of monkeys that are pretty happy They're doing some pretty neat stuff. They're impressive. They are really working well together But you have a couple of gorillas on top of it that are Progressively hiding what it is that is making these monkeys so good They're in essence becoming a barrier to those bananas because they're standing in the way They they need more sustenance. They need more fuel. They need more Everything so they're bigger. They're larger. They're meaner and basically what ends up happening is they stop you from getting to those bananas and You can't share them You can't talk about them because the perception is that those bananas are basically the business model So if I give you my business model, how the hell am I gonna compete? How am I going to you know? Pay my employees if I can't have something that's unique So let me ask you a question just kind of we'll go back to technology for a minute. How many of you have installed Apache? Okay, everybody in the room except for Jeff But that's cool because I know he has how many of you used a config file when you install the patchy Everybody in the room so basically the act of putting a config file in place for Apache to read is not unique It's not there's a number of ways of accomplishing that so let's break that out Let's say hey if you're working with Apache guess what you're gonna need a config file Guess what it should probably look like this and hey here's one step further. I have tests that will support it I have tests that will work in x y and z these tests Abstract what it is that I'm talking about and because we have slowed down and broken cycles We're doing test-driven development now. We have the ability to say in plain English what this thing does So the next time that let's say a business person comes along who knows nothing about technology they can query your tests and get a Clear plain English definition that Apache put that file in place and that files needed to configure Apache Done. I know what the system does now Why don't we have that for Drupal? I mean seriously We all do the same stuff. We use vagrant. We use some of us use vagrant. We use all kinds of caching technologies We use a PC. We use PHP. We use Apache. We use engine X We use all kinds of stuff and we tend to do it pretty consistently. So why are we all reinventing the wheel? Gorilla traction form silos plain and simple the nice thing about The interesting thing about that particular silo is that those monkeys are so ingrained with supporting those gorillas that they will never be able to go anywhere else. So it's effectively a trap It's unfortunate Open source changes silos. That's why I got involved with Drupal. That's why I'm here today Not because I'm supporting silos, but because I'm supporting open source. It changes the world. We need to start doing it So why a survey? This is very interesting to me. How many of you have heard of DevOps days? A couple people. DevOps days is a Global conference much like Drupalcon except that it happens more frequently. It's done on an open source model Anybody can step up organize a quick event and it's kind of like Drupal camps. They're getting a lot of penetration This happens to be one of the organizers of DevOps days. His name is Chris Boytard. This is him approximately two years ago Morton posted a post asking people what they thought about voting on Drupalcon sessions because there's this interesting stigma that it is Almost impossible to present for a Drupalcon because you have to be one of those Phenomenal rock stars to be able to do anything and like let me tell you right now My experience from doing the number of code reviews that I have and working with the teams that I have is that if you have Somebody that is in your team that is a rock star then your code needs to be fixed plain and simple There is no need for a rock star anywhere. It's a code smell But this gentleman spent a little bit of time trying to penetrate the Drupal community He is now the DevOps chair for the European Track and if you look real carefully at how North America and Europe are organizing the DevOps track It is intensely interesting And by that I mean I believe that people like Chris came to the Drupal community because we made them we gave Enterprising operations people tools that they needed to fix So they had to learn about our stuff They had to introduce us to DevOps and they had to do what they needed to do to help elevate us as a community So that they could stay sane and I think it's our turn to reciprocate So let's just get right into the data. I've said my craziness for the day I'm gonna let you guys reflect on that for a little while and I'm gonna get into the data as much as I can So basically what we have and I'll just talk about where this data came from real quickly is Open-source project called lime survey. It's in an XML format. I sent Chris an email. He sent me the XML format We have both versions on that Drupal dot org project page I Would really love to see somebody pick this up at some point in the future Maybe use it in a future Drupal con or use it in their business or write presentations about it And tell us what it is that we're doing right and doing wrong and there's some very interesting things that can be gleaned from this The first thing that we're seeing between these two years is that we are experiencing consistent growth and site management and site building It's it's pretty straightforward. I mean these who are you kind of questions? These are the types of organizations that are growing right now We're also seeing across the board, you know going back to this gorilla concept We're seeing a decrease in clients self-hosting sites. It's becoming more difficult for a client to self-host their site They have to run a host of technologies a lot of people don't have the bandwidth or the capacity to do it They're busy fighting that Drupal cliff and trying to become rock stars. So it's an interesting paradigm There's that word The number of people pulled into DevOps is on par with a number of people that introduced DevOps I find that to be exceedingly interesting particularly because what it means is that for You're almost getting an equal response of people that are introducing a new technology having this conversation Changing the way people think talking to their engineering buddies and having them think about things a little bit differently And you're accomplishing great things and it's spreading so as you're planting a seed another one's popping up whether it wants to or not and Eventually the idea is that these things take root and and really change organizations. That's why we are here That's why we do DevOps According to the Drupal community we no longer need to explain why DevOps I mean if you look at it this one here, no, why should I use DevOps? What the heck is it 33% of the respondents in 2012 said why I don't even understand what you're talking about in 2014 I had one response that said why and I'm pretty sure based on who put it in there It was a sarcastic response So that says a lot about where we are where we've been coming from and we'll get to where we're going in a little bit But that comes back to the tenants of DevOps You have to measure to be able to have the right conversation with the right people at the right time And if you're not prepared to do that you're going to reinvent the wheel You're going to work harder than you need to work and you need to solve that in my opinion So about your site is your current production site up to date Basically, this is a security question. How many outstanding security issues do you have? That we know about 87% of respondents are subscribed to Drupal security news That is pretty good. I think that's up from I think it was in the 60s when they had first asked this question So I was pretty excited about that the percentage of sites that are up to date for core only decreased by 13% So basically that could be read a couple of different ways the way that I'm gonna State it until somebody proves me wrong is that people are getting better at maintaining contrib The percentage of sites that are up to date for both core and contrib have increased by 8% Seems pretty positive The percentage of sites that are not up to date at all has increased by 4% So basically what this is telling us is that we seem to have a difficult time keeping up We're not doing DevOps properly and we're not teaching it properly because the people still cannot keep up And if there is anything to know about Drupal, it is a very public piece of software There is a lot of security issues with it. You need to be aware of them You need to keep your sites up to date Otherwise we'll have something like what happened with WordPress and all the Drupal sites become a bot form basically We kind of don't want that so Basically as we talk more and more about site development we start seeing some trends More people are developing using multiple environments. We're starting to see really good use of devs staging Testing those types of environments pop up people are hearing the conversation They're understanding what it is that we're doing their efficiency in that process is is probably the next conversation But at least they're listening This highlights the need for Consistency between environments and this goes back to testing and being able to define what it is that you're doing Not only from an engineering perspective, but what is that thing that you're doing from a security perspective? What is that thing that you're doing from a metrics perspective if I introduce that to my system? How do I send a notification to the right ops person that they're going to need to tweak something in varnish? For example to be able to keep up with me or they need to spin it up another machine They have to have some sort of an indicator and I think that if you're doing test-driven development and you're doing possibly behavior-driven development depending on your type of organization that you have Mechanisms to be able to make that type of connection send that type of signal and communicate with those people efficiently 8% of respondents are still deploying critical changes on production first or unaware of what a critical fix is That says a lot. I mean that maybe that's your you know where I started in my basement writing Drupal sites Working on one site. It's all I had. It's all I could afford. I couldn't do anything else. So maybe that's that crowd I don't know. It's a disconcerting number to me I don't think that anybody should Not know how to update a Drupal site So these are fun slides and I say that these are fun slides because let's step back from the presentation for a minute There's a very active conversation going on right now And I've kind of hinted at the concept of code smells where you think that what you're doing is so unique that it can't Possibly fit into anybody else's pattern There's a certain level of blindness that happens once you make that assumption and I've seen great improvements happen when people can remove that blindness So we'll just continue on for a little bit more 96% of respondents utilize version control You'll notice that this chart is starting to move quite a bit in 2012. It was not that we definitely had people that were a little Diversified in how they actually use version control, but it's changing. It's getting fixed Basically, what's wrong with the other 4%? I don't understand how you can exist in today's world and not use version control I mean just for your sanity But that's neither here nor there So remember the time amount of time that we spent bike shedding the migration to get how many people actually remember that conversation It went on for months and months and months and we are still bike shedding about it and still talking about it And still arguing about it And I've had some of the most brilliant people in the Drupal community come into organizations and make recommendations about things like source control Because it's what they're comfortable with but they don't they're engineers, right? They don't really balance that people aspect and if you're noticing a trend where most of the world is doing something else And you're not willing to Participate there then you might be short-circuiting your effectiveness And we see that pretty clearly in the next slide 94% of respondents now use get What this tells me is I don't ever have to ask this question again We can stop talking about get versus CVS versus SVN if you're not doing it with 94% of the community Supporting that decision and then that's your prerogative. Have a nice day. I'm gonna stick with the 94% SVN is the next closest with 2% Interesting all the ones that were relevant disappeared. They weren't even a line item So that says how quickly this industry changes and that's also one of the traps that we all need to be aware of Is the second that somebody like me stands up here and tells you that something is a certain way? It's changing already Your technology your code the things that you implement is workflows You need to remove emotional attachments and understand how to utilize those things in a way that is effective for what it is that you're trying to accomplish and I can guarantee you that you will be a Better developer and a better person as a result of it. It's very interesting So about site development The use of continue a continuous integration platforms is increasing Everybody's heard Jenkins. It's consistently outperforming other platforms and adoption that tends to be I think because of you know things like open source a or Human nature you start talking about a complicated problem a couple people start putting forth a lot of effort they come up with a Reasonable solution a couple more people start talking about that they all start understanding it better and then it starts spreading until eventually It's such a a known commodity that everybody's just kind of doing it you saw that happen with get I think you're gonna see similar things here depending on your level of enterprise ness So Let's keep going the types of tests we run are relatively consistent over time And those of you that are data scientists and very well versed in this type of thing will note immediately that this should probably be a bar chart I'm not a data scientist I just use Google Docs and click buttons and this is what came out. So please fix it But what is interesting here is that you'll notice that the breakup of this particular Chart doesn't really fluctuate that much what that tells me is that we basically Know what it is that we're testing how we're gonna go about doing it and those technologies are not in flux It's a two-year time span. So why even have those questions anymore it from a Drupal perspective It seems like we're most interested in performance followed by usability followed by GUI testing So what that tells me is that if I want to be very effective at supporting Drupal teams That I should probably find some way to do those three things effectively and maybe let the rest of them slide for a little bit Not forever, but if I'm communicating properly I'm doing it in an open-source way and I'm putting this stuff out there Then other people can use it other people can adopt it and I won't have to have this conversation again I have three very good ways of doing x y and z and let's collaborate So site development the use of testing frameworks is increased. That is awesome Operations people. I don't know if any of you have ever seen it. There's a dev ops GIF basically that shows the difference between a script written written by a System administrator and a script written by a programmer the system administrator script looks like something out of terminators This is gargantuan robot that's just stomping around and then you look at what the developer wrote and it's this very precise thing That's moving Marbles very rapidly very precise. It's a very interesting paradigm And I think that one of the things that is being in great is that frameworks open source What we're doing is a community is applicable across the board and it's being adopted Selenium right now leads the pack that ties back to the fact that we are very interested in usability testing We are very interested in GUI testing. We're very interested in what those button clickers are capable of doing Cucumber has increased by 2% Behavior-driven development is an interesting paradigm There's an entire school of thought as to whether or not it's applicable to technology or if it's just applicable to Business but in both cases there's value and it should be considered Be hat is the biggest mover at almost 7% and straight up yay symphony for so many reasons I mean the symphonies Introducing the Drupal community to how to write tests properly. It's helping provide frameworks that are used by others It's giving us structure and helping the entire community learn Things that are removing blinders that are helping them think out of the box I'm be had is one of the most phenomenal things out of this in my Opinion another good thing about symphony in the general direction of Drupal 8 right now is that you know configs are starting to go into files It's about time. I can start sourcing this stuff. It's great So continuing with site development more developers are working locally What you're seeing here is basically a decrease in live production work You're seeing a decrease in working on on staging environments You're seeing a decrease in working on development environments But you are seeing people bringing stuff further and further back in which goes back to that tweet You'd need to be able to do that efficiently. Everybody's doing it. Everybody's starting to do it. These systems are coming online They're active. They're live They're doing what they're supposed to be doing and the developers are reacting and this is a sign of that Yeah, and back to consistency for divide environments basically a I was talking to a gentleman at the booth the other day and he came up to me and said that I have a vendor that I'm working with and I have a Particular issue where I tested on two or three environments that I have and I push it up following their procedures Doesn't work in their production environment works in every other environment up to that point and they won't give me any logs I can't see what's going on. I can't adjust anything that I'm working on I have to wait for a ticket from some deep dark department inside of this this Organization and I haven't gotten a response. I can't get a response. It's like black air or black. Well, you know black box There you go. That's what that's called It's not open source. It's it's disconcerting and again this slide kind of highlights the growth You'll see here in this 12.9% the virtualization is increased Whether or not people are doing it right whether or not people are understanding it Whether or not people are sending people down the wrong path by making recommendations that aren't properly thought out It's increasing. We need to deal with it. We need to accept all those scenarios and we need to make it work So basically this is an awesome slide because what we're seeing across the board is that when we're asking people How do you configure your modules? People are starting to do it the right way and it is about time. I Do not enjoy logging into a site having to click into the admin page to configure a module I don't think anybody should ever have to do that unless they're testing something out But what we're seeing is that features is bridging this gap considerably for Drupal 7 We're seeing adoption of features come up 18% in a two-year time period and that's pretty substantial. That's huge Manual configuration changes from the GUI are down 27% Apparently people don't like clicking buttons either at least the people that are willing to fill out the survey Site profile installations have improved from less than 1% Which blows my mind to 6% how many of you use site install profiles when you deploy Drupal? A fair number of people in here There is no way to programmatically install a site with without that in some capacity You're either doing a database dump. You're starting from a certain point It's it's it's really a shame if you're not using an install profile And you're not doing it in a way that it's reusable for your organization Particularly if your organization's responsibility is to deal with clients I'll stop there Database installations have decreased by 9% what that means is people dumping database from local Let's Shlep it up to production or wherever else that is the worst possible way to Install a Drupal site and I really do hope that nobody's doing it here If you need clarification on that come talk to me afterwards and we'll sit down Have the use of features has increased by 9% so Basically what that's saying is that in those install profiles It's likely that you're gonna find some features work there and features is doing some great things in this space right now features Strong on those. Those are all fantastic tools. They can get a little unwieldy sometimes But it is the best that we have right now So what's behind Drupal? It's safe to say that Apache and engine X are dominating this particular market plain and simple Nobody mentioned IIS and we gave them the opportunity to do so Engine X usage as a web server is increased by 12% which is I Think a disruptive Point to pay attention to the underdog here has basically De-thrown the king. I mean plain and simple engine X is taking over It's it's really an effective technology at what it does and I think a key component of why it is as Effective as it is is because it focuses on a smaller subset of tasks It's identified those tasks and it focuses to do those very well It's the key to why Linux is as stable as it is It's the key to why Linux has been around as long as it is if you are developing a project that is so Infinitely complex it it's going to take weeks and months to figure out how to even start you are doing it wrong plain and simple Data systems are increasing in complexity. We know this because we're seeing increases in replication across the board It's very interesting now Single instances of my sequel are down roughly 28% and this you know this is data take it with a grain of salt I have a very specific subset of people that probably filled this out They're likely a little more on the enterprise, but it's still an interesting statistic a Fair amount of this replication growth is a result of hosting providers that cater to Drupal. That's my wild ass assumption There's no merit or basis to that but it might be true What we're seeing highlighted in some of these other slides is that people are using more and more hosting providers Because it simplifies their process It also locks them into a silo. So it's an interesting trade-off So what's behind Drupal are you using memcached? I'm surprised that we still have to ask for this, but it is true We do We've identified that Yes, Redis actually came up quite a bit and and I think that Sonobom sent me a couple of tweets specifically about it joking But you need to start looking at caching layers. You need to start looking at APC You need to look in a knobcode cache. You need to be able to to use redis memcache Varnish anything else in front of it? Drupal needs a lot of help sometimes these tools are very effective at reducing your infrastructure costs across the board If you are in a scenario where you're maybe dealing with some old metal You need to get your entire organization's cost under control It's a great way to have a high impact if you're not already using it So basically varnish has increased by 17 percent relative percentage of people not using this layer of caching has decreased by 20% this is good. That means we're making the internet a better place. We're improving people's experiences We're addressing usability across the board as a result of it indirectly. It's all really cool how it ties together The use of HA proxy is increasing you need to pay attention to that HA proxy is a very valuable tool It is something that you should really consider if you haven't already put it in your arsenal Apache keeps losing market share It's an interesting statement. It's not even a question anymore. They are losing market share They're losing out to smaller more efficient more capable projects that are More focused. It's something to consider when you design your workflows and your business practices Internal dedicated infrastructure is down by 9% less people are hosting in-house more people are hosting in the cloud Shared server usage has fallen by 14 percent. That is phenomenal. You're going to hear a lot about open shift It's a fantastic technology. It does a lot of really cool things. You should check it out. It probably has It will probably impact that number more significantly as we continue forward And it's true. I mean we're migrating to the cloud if you need any further proof I don't know So basically what it boils down to is DevOps is Kind of like a spiral or a spiral of life or whatever you want to call it. I'll go a little bit zen and holistic on everybody Think of it like the washing machine, right? When you're at the top point of that washing machine you have something like oh, we need to focus on project management You come back down a little bit and then oh well project management is nailing it But marketing's in the way. These guys are promising these girls are promising all kinds of stuff that I I can't deliver So let's rain that in a little bit. So let's come down here and see what's left. Oh development needs some improvement now So let's let's call this DevOps and let's go over here and do this thing and then by the time you get to the top It's not a perfect circle. You've solved Points along the way. They may not be perfect solutions But they are something that have improved your scenario in your situation And when you come back around you have the ability to get a little more focused and a little more Effective a little more surgical at what it is that you're doing and you refine the message and you keep doing it Don't ever get stuck in the thought or the mindset that what you're doing right now is the only way to do it It is the right way to do it you will Basically go broke if you do that So the moment of zen has passed and I promised an iPad to the people that filled this thing out I'm going to deliver So I have put this into a third-party service It can be audited by anybody that wants to the links out there on the Presentation that's checked into github. It all ties together. It's kind of cool This is the gentleman the one his name is Nicola page Unfortunately, he is not here with us today. I sent him an email. He is I believe he said Rafting down the canals of Venice I Didn't want to interrupt him. I was like that sounds cool, but he won the drawing And that's basically it if you have any thoughts There's a couple of really good places for you to focus the first one is Drupal org slash DevOps I know it's a stupid word I know that it sends the wrong connotation a lot of times and I retract the use of the word stupid because obviously that's incorrect but It's a great place to have this conversation. There's a lot of people that are listening there It's not used effectively But that's because we need to come together and we need to figure out and identify how to use it to solve your problems And I need help with that Going to have a boff to discuss this very thing I would encourage anybody that has any questions or just wants to talk please show up. It's going to be fun It's going to happen this Thursday 1045 to 1145 and Evaluate this session. I mean plain and simple the DA works very hard to be able to put these shows together if you don't Give them the information that they need like hey, maybe this DevOps track needs to be restructured a little bit Maybe it should be focused more on performance. Maybe it should be more security They will not have that data or that feedback unless you give it to them and we cannot adjust the content of these shows So please do that And that's it Any questions did I scare everybody? Sure, there's a microphone up here if you could just form a line we have about five minutes So I apologize for my English Just a question about what is the state of mind for Networked for a system On with Drupal For example for synchronize The files directly between a lot of Well, I think that by mindset what it comes down to it is Testing I think that that first most people need to understand what that is and what tools and components are involved in it And the mindset comes about from showing people how to to validate what it is that they're doing with those things and understanding What those things should be doing and I think that that for most people that's the challenge right now If you'd like to basically come to the boff and let's sit down and talk and I'll give you some really concrete examples Thank you very much. Mm-hmm. All right enjoy Drupal con Give a lot of feedback while you're here talk to people the sessions are great But I think that your real value is from the people that are around you There's a lot of interest interesting conversations that you can have and I encourage you to do so. Thank you