Deploying systems using AWS DevOps tools

Editor's Notes

• #6: So we’re here to talk about DevOps tonight? To talk about tools on the AWS stack that help our teams when implementing DevOps solutions. Quick show of hands; who’s been to a DevOps talk before?
• #7: Everyone is talking about DevOps… Including us. And it’s great. The more people in the conversation the better.
• #8: It’s not just small boutiques, either. Netflix – forward thinkers in the space. Hubspot – Local to Boston. (Now nation wide LA – BOS) SpaceX – Big Enterprise taking on DevOps Facebook Spotify Etsy Disney Chaos Monkey – The name comes from the idea of releasing a wild monkey with a weapon on your production data center and letting it cause havoc on random infrastructure and using this as an opportunity to learn the weaknesses of the system and continuously improve your ability to absorb and recover from failures (cattle vs. pets)
• #9: Before I go down the technical road of cool tools, we should remember. A clearly defined DevOps process is just as important as picking the right tool for the job. Agile project management is a major tenant of DevOps. Getting an agile team together to agree and subscribe to a process will create an environment of collaboration and by default promote a feedback loop that will allow you to refine the process.
• #10: Source Control – GIT / TFS / Sub Version Build Runners – Jenkins, TeamCity, TFS Automated Testing – nUnit, Selenium, Build Versioning – S3, nuget IaC – CloudFormation, Azure, VMWare Configuration Management – Chef, Puppet Continuous Delivery – CodeDeploy, Octopus, Azure Monitoring – CloudWatch, New Relic
• #11: When you’re looking at tools, think about how much control you want think about how much control you have over your services. Something like Cloud formation gives you granular control over the particulars of your systems And on the other end, something like elastic beanstalk is more convenient, but you’re relying on AWS to provision and configure your system.
• #12: Icons across the top with descriptions of services
• #14: Continuous integration – merging code early and often Continuous delivery – the process which code goes from Dev to Prod
• #15: Fully managed Assumes you already have setup EC2 servers or on prem Repeated deployments to existing application fleet Configure Deployment Groups Versioned Deployments Automate scripts to execute during each deployment Can be used with existing physical servers
• #17: Hooks - These steps are AWS defined
• #18: These steps are AWS defined
• #20: You might hear the term Continuous Delivery applied here
• #22: In a world without Config Management, amongst other difficulties…. First and foremost you’re following long procedural checklists More people = more potential for a breakdown in the pipeline Confusion and frustration
• #26: The ability to clearly define your infrastructure to fit it's landscape. “a build should be a unit of code with configuration outside of it.” Environments, roles, dependencies, etc Eliminate manual changes, inconsistent state of resources, and human error. Your infrastructure is version controlled - interacts with Git, etc Your configurations should endure the same rigorous testing and QA as your code. Organized view of infrastructure past, present, and future. Your configurations should endure the same testing and QA as your code.
• #29: There are many great options out there. Choose the best one that fits your needs. Talk about tools – ansible, salt, chef, puppet, fabric Tools – chef, puppet, ansible, salt, fabric. – each using different methods Loads of online documentation, examples, etc. – you’re not alone. There are "hooks", plugins, and native solutions available – go into windows specific tools, aws-s3, etc. When you really get down to it – while they may all take different paths, they arrive at the same goal. You are managing your infrastructure and systems Talk about plugins and addons – specific example is chef windows cookbook Loads of easy to find information and documentation for most tools – chefdocs/puppetdocs examples Talk about user community and contributors You are not alone – chances are you aren’t the first to have issues, obstacles, and ideas – seek and you shall find
• #30: Puppet is a good choice if stability and maturity are key factors for you. It’s good for large enterprises with a heterogeneous environment and range of skills on the DevOps team. Puppet is one of the long standing tools in the full-fledged configuration management space. It’s an open source tool, but given how long it’s been around, it has been well vetted and deployed in some of the biggest and most demanding environments. Puppet is based in Ruby, but uses a customized Domain Scripting Language (DSL) closer to JSON for working within it. It runs as a master-client setup and uses a model-driven approach. The Puppet code design works as a list of dependencies, which can make things easier or more confusing, depending on your setup.
• #31: Puppet is a good choice if stability and maturity are key factors for you. It’s good for large enterprises with a heterogeneous environment and range of skills on the DevOps team. Puppet is one of the long standing tools in the full-fledged configuration management space. It’s an open source tool, but given how long it’s been around, it has been well vetted and deployed in some of the biggest and most demanding environments. Puppet is based in Ruby, but uses a customized Domain Scripting Language (DSL) closer to JSON for working within it. It runs as a master-client setup and uses a model-driven approach. The Puppet code design works as a list of dependencies, which can make things easier or more confusing, depending on your setup.
• #34: Reduced learning curve with descriptive languages such as those used by Chef, Puppet, and Ansible. Flexibility allows for use with other languages (python, ruby, etc) as well as the ability to leverage vendor APIs. IaC is an organized and concise representation of your infrastructure's configuration. Code should follow the same rigorous testing procedures and QA as your other code IaC can be used to achieve full orchestration of the entire deployment process as well as the automation of all necessary tasks in that cycle.
• #36: CloudFormation is an easy way to create and manage a collection of related AWS resources. Provisioning and updating “stacks” and resources becomes a predictable, orderly, and efficient process. Flexible templates allow for customization using parameters, forming relationships between resources, and scripting. Provides the ability to visualize your infrastructure.
• #37: CloudFormation provides a means to version control your infrastructure using your organization’s tool of choice. CloudFormation stacks can be launched and/or terminated via the AWS Management Console, AWS API, or the AWS command line interface. – cows and pigs With the use of custom scripting, CloudFormation can be integrated with configuration management tools.