PyCon 2014

Introducción a Salt, la alternativa Python a Chef y Puppet

Peter Baumgartner  · 




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

hello everybody welcome to the last session in the automation ops team to track I'm very happy to introduce to you Peter Baum Carter he's going to talk about salt salt stack and give it away all right thank you thanks everybody for coming so yeah this

is getting started with salt like you said I'm Peter Baumgartner founder of a company called Lincoln loop we do lots of web application development in pythons so we end up setting up a lot of servers to do that we use salt just to get a idea who's

here how many people in the audience have used chef or puppet in the past for configuration management Wow okay fabric have you used fabric okay and is anybody here use salt okay this is a pretty introductory talk so if you've used salt quite a bit you

may find it boring or repetitive but yeah and he saw devs in the in the audience okay good nobody to tell me I'm wrong oh wait did I see a hand oh no okay well if I screw something up let me know okay so let's get started what is salt stack salt stack

this is from their website saltstack delivers a dynamic infrastructure communication bus used for orchestration remote execution configuration management and much more so kind of some buzzword bingo there and a lot of things going on so so let's break

it down salt stack is configuration management other configuration management tools you may have heard of cfengine was one of the early ones there's chef and puppet like many of you have used ansible is out there as well another Python option so before

configuration management we would set up a server we'd set up nginx on the server and we'd configure nginx in the nginx comp file then we'd want to make a change to nginx comp and we'd back it up and then we would do it again and again and

we just need to stop doing that so after configuration management it looks like this configuration management lets you have a single set of files that tell you exactly what your server is doing how it is configured when people make changes you get a nice log

so you can put it in version control all these nice things you you basically version controlled your servers it's self documenting when somebody wants to know what the server is doing they can review your configuration management system and see that it's

as easy to set up one server as it is a hundred servers so repeatable and reusable so next up saltstack is remote execution remote execution is kind of the territory of fabric Capistrano func basically the ability to run one or more commands against one or

more remote systems this is sort of out of the scope of what chef and puppet are designed to do some examples of when you want to use remote execution deploying your code running all the things necessary to do a deploy running one-off scripts doing critical

package updates so the open SSL heartbleed issue is a great example of when you might want to run a specific command one time against many systems and you can use it for system monitoring as well so you know check the load on this server every five minutes

or this set of servers and report back so that's what saltstack is or a subset at least we'll cover today why would you want to choose saltstack big thing for me I'm a Python developer I typically work build websites in Django so salt stacks written

in Python it's configured with Y amel which is a dead simple kind of configuration language and it uses Jinja to as a templating engine so coming from to the django world Jinja two templates were very familiar to me it's all familiar tools easy for

me to hack on in contrast tools like chef and puppet use their own custom DSL they're sort of based off of Ruby that wasn't very comfortable for me so those are things I liked about salt another thing I like it's got really good documentation if

you want to print it out on their website it be over 800 pages they are insanely responsive they're there IRC room is always full of people if you file an issue on github don't be surprised if you get a response the same day and and finally it's

backed by a for-profit organization so there's people with a vested interest in making sure salt is cutting-edge state-of-the-art and works they're not going to go away or get busy with their day job and disappear so all things I liked about it so

that's that's why you might want to choose saltstack how about some reasons maybe why you might not want to choose saltstack here's sort of the the common things I hear about why people don't like salt it's a young project it moves fast

there they're constantly building new features that might be scary as long as they kind of maintain stability that's that's a plus in my book there they're making it better without breaking old stuff and in my general experience over the last

probably couple years now that's the case and it doesn't use SSH as its transport transport and communication mechanism between servers so SSH is tried-and-true people trust it that's great a lot of the things salt needs to do it does over a kind

of an always-on communication bus between servers SSH really doesn't work as well for that and doesn't scale to the level they want to scale they're you know talking thousands of servers managed by by one master it has some SSH support it's

an alpha status right now but yeah you don't want to use it in production so let's dive in and actually start learning about salt so the first thing we need to do is take of a cat vocabulary lesson the state of kind of DevOps in general is is terrible

[ ... ]

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