DrupalCon Prague 2013

Proviso, estandarizando la creación de entornos Vagrant

Howard Tyson, Patrick Connolly  · 


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

bcf g2 in the house CF engine no ok cool so hopefully we won't bore you too much with the intro stuff since everybody's fairly familiar we're still going to run through it but we'll make it quick and then we'll start talking about what

provisos all about but first we'll introduce ourselves so again this is our sessions on / visa and which is a goal to sort of standardized vagrant based Drupal development I'm Patrick Connelly I work at my planet digital back in toronto canada i guess

i'm not a dev ops team but I'm I work there and just try to help teams create tools to help themselves serve their own throne infrastructure internally for our projects I am Howard Tyson tis o on drupal.org Twitter and anywhere else I can get it I

work at a company called zip tech where I kind of do a lot of the tech direction and work on a lot of our stack tools and and have kind of been really focused on building up our hosting infrastructure and our vagrant stuff and making that as slick as possible

and so I've been spending a lot of time on kind of that side of things so so I'm we will kind of wanted to frame this with a little bit of history so in the beginning of website development local development was hard because you probably had to kind

of set up all the different pieces yourself for a lamp infrastructure there were endless screen cats on it lots of people back then we're still using windows before this kind of mac revolution where everybody has a glowing apple if they work in tech so

you're probably doing it on windows so you just didn't and a lot of people just kind of went in and used FTP and just kind of said this whole local things too hard doing love all right it and we'll do it live so that was Bill O'Reilly saying

screw it we'll do it live I'm really disappointed after all that our audio software anyway so uh so then we started to build tools we were the monkeys with the bone and that's the sort of tool that we built and we called it ma'am and wamp and

zamp and it worked on my machine this is a vagrant talk so we had to have the obligatory it works on my machine slide right and you had Drupal running locally but was solar running was memcache running was varnish running Redis SSL selenium there are all these

pieces that you really needed that you just didn't have and so for those parts a lot of people still ended up just developing on production or on something like it because those tools just weren't easy to set up and then there was vagrant welcome to

the future and so that's where we stand today vagrant creates virtual machines on in the environment hopefully you guys all know you can kind of provision it with any of those provision or if we were talking about which led us to this rise of all of these

different vagrant projects and all of these different machines we can just run vagrant up and all of the stuff was working perfectly in rehearsal and vagrant bundle installs all of our plugins vagrant has a lot of awesome plugins we're leveraging a lot

of them in the proviso project and it builds your system but uh oops but this kind of led to this proliferation kind of an insurmountable and daunting set of overlapping tools and people working on the same stuff Oh God there are so many tools and so many

machines rising up in this flow where we've got the Drupal vagrant project Oscar Ariadne Oscar again quickstart Drupal pro ager up dev shop drupal lamp the vagrant DVM we've all been reinventing the wheel and we've all been doing things slightly

differently but mostly the same and there hasn't been a place where people have been coming together to start sharing best practices and starting to assemble sort of how is it that this community should be doing this and what are we sort of trying to replicate

and I think there's sort of an upside in a downside to that because part of the idea with vagrant is you can use your real provisioners your real source that's going to be running on production to build your dev infrastructure if you build and maintain

your own dev infrastructure the thing is that a lot of companies don't a lot of companies have some sites that run on Pantheon some that run on aqueous um that run on the clients hosting and so there's an awful lot of kind of shared stuff and there

was no way to collaborate and no space for that until now that's the baby from 2001 um just in case you didn't get that running theme so proviso was born so what happened was a whole bunch of us that have been working on this stuff got together at

drupalcon Portland and started saying oh you wrote a little SSH plugin to automatically add your ssh key to SS agent to do the thing so get would work I did that too Oh yours is kind of better oh but mine does this thing and we started realizing that there

was a whole lot of kind of overlapping effort and we should kind of pull together and start coming up with ways to collaborate so what is proviso it's a community project to assimilate them all resistance is futile if you've got your own vagrant project

just just come on board so first off more than anything else / visa aims to be a community it means to start conversations and get us working in a place where we can start to assemble best practices and look at each other's code and and start contributing

to a common thing don't we have a community yes we do we have especially folks that are working on this kind of stuff a lot of people hang out on groups out drupal.org / devops / high performance those conversations aren't as active as they probably

could and should be based on how much time we're all spending on this but most of the stuff that's happening there is conversing not converging we talk about hey I have this bug on my server but there's no easy way to sort of replicate that issue

to be able to set up exactly exactly what your server looks like and say let's make a tweak in benchmark in a way that all of us can kind of reproduce all of us can contribute to all of us can start to figure out what should a secure server look like what

should a high performance server look like what's the performance implication of terminating SSL with engine X versus Apache versus whatever and just as an example like there's if you look on securing your Drupal site on drupal.org there's a bunch

of pages a bunch of sub pages on how to secure a server and it's all it's all words it's not executable and everyone's doing this when they find it hopefully they're doing this on their own yes so the idea is it's cody's conversation

so let's see oh right so so the idea is can we kind of follow some of the more recent DevOps best practices of can we have code / documentation instead of having a checklist can we have a chef cookbook or a puppet module that just shows you what those

steps should be so that you can look at a working machine because if you sort of if you're building a chef cookbook or sorry yeah chef cookbook or a puppet module that has all of those steps captured in it in a way that's clearly understandable both

of those tools have optimized for being able to read and understand what's being specified in there so that's sort of the best form of documentation because it actually will then run and it's not a checklist that needs to be maintained needs to

be updated and you know you're not missing a step if it works right so the idea is if we can pull all of this in this is such a sales pitch most of this presentation if we can get all of you guys to come to proviso and start pulling some of the conversation

there we can start to turn more and more of our best practices into community modules that we can all use and share locally and on our remote servers potentially so how this is where we start to get into the technical implementation of how we're trying

to tackle this project so so proviso is sort of actually I I skipped a couple of bullets there didn't I um proviso is a proviso and initiative in addition to being a community it's not a finished product it is a thing that we are trying to get more

momentum on and trying to get more people contributing to its not that we don't have code it's not that we don't of stuff running it's just that like how we get together and talk about Drupal core initiatives where we think something is a good

idea and a lot of people are pushing on it that's where pervy so is especially right now so we're trying to work to find the best ways to share because sharing is caring it's also a vagrant project so the idea is that teams that need a vagrant

development environment can use ours and we can again start to reduce duplicate effort with all of those fricking projects that we listed before that mostly set up a lamp stack and then another thing is to make it accessible I don't know if any of you

guys have been following the kalam una guys there this this dev company that's been working on this project called the kallah box it's very cool it is a wrapper around vagrant and virtualbox that gives you a one-click installer for OS 10 they hope

to have one for Windows eventually and then they used nodejs and some desktop you know Jas packaging to build a pretty slick GUI so it's kind of modeled after the maps and the lamps and the samp sout there where you have this like Status page that says

whether Calla box is running whether it's got engine X up my sequel up whether the ssh keys are installed some other Solar's installed and running weather webroot is um rating of happiness its maximal you'll be glad to hear um and the idea is that

you've got a list of local sites you've got a list of your sights on pantheon you've got a list of the different tools these are like quick jumping points for things like PHP my admin you've got commands so that you you can you can they have

[ ... ]

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