Today, the development and operations landscape has shifted to a more collaborative model merging the two (DevOps). Developers need to know much more about the operational components of their software - especially around network programming, services development, and continuous deployment. Likewise, the developer's IT counterpart needs to know much more about development - especially around infrastructure automation (Chef/Puppet), automated testing, and continuous deployment.
Infrastructure as Code (IaC) allows organizations to define and provision their IT infrastructure in code instead of manually. This improves productivity by automating complex setup processes, ensures consistency across environments, and reduces human errors. Some key benefits of IaC include boosting productivity through automation, maintaining consistent configurations, and minimizing risks from human errors. It also increases software development efficiency by enabling incremental development and testing in sandbox environments.
The document discusses Amazon EKS (Elastic Kubernetes Service), which allows users to run Kubernetes on AWS. It highlights that EKS manages the control plane for users and provides native integrations with other AWS services like load balancers, IAM, and container registry. The document also summarizes key capabilities like high availability of the Kubernetes masters, networking options, version upgrades, and how to provision Kubernetes nodes on EKS.
Using Azure DevOps to continuously build, test, and deploy containerized appl...Adrian Todorov
Using Azure DevOps and containers, developers can continuously build, test, and deploy applications to Kubernetes with ease. Azure DevOps provides tools for continuous integration, release management, and monitoring that integrate well with containerized applications on Kubernetes. Developers benefit from being able to focus on writing code while operations manages the infrastructure. Azure Kubernetes Service (AKS) makes it simple to deploy and manage Kubernetes clusters in Azure without having to worry about installing or maintaining the Kubernetes master components.
This document provides an overview and introduction to Terraform, including:
- Terraform is an open-source tool for building, changing, and versioning infrastructure safely and efficiently across multiple cloud providers and custom solutions.
- It discusses how Terraform compares to other tools like CloudFormation, Puppet, Chef, etc. and highlights some key Terraform facts like its versioning, community, and issue tracking on GitHub.
- The document provides instructions on getting started with Terraform by installing it and describes some common Terraform commands like apply, plan, and refresh.
- Finally, it briefly outlines some key Terraform features and example use cases like cloud app setup, multi
This document discusses Terraform, an open-source tool that allows users to define and provision infrastructure resources in a declarative configuration file. It summarizes that Terraform allows users to build, change, and destroy infrastructure components like compute instances, storage buckets, and networking through declarative configuration files, enabling an infrastructure-as-code approach that is easy to version, track changes for, and integrate with continuous delivery practices.
As part of this presentation we covered basics of Terraform which is Infrastructure as code. It will helps to Devops teams to start with Terraform.
This document will be helpful for the development who wants to understand infrastructure as code concepts and if they want to understand the usability of terrform
This document summarizes CI/CD on AWS by Bhargav Amin. It introduces DevOps practices like continuous integration, continuous delivery, and continuous deployment. It explains how to design a CI/CD pipeline and create one on AWS using services like CodeCommit, CodeBuild, CodeDeploy, and CodePipeline. The document provides examples of integrating these services to automate building, testing, and deploying code changes. It also includes a link to a demo repository and discusses managing infrastructure with CI/CD by updating CloudFormation templates in a pipeline.
Best Practices of Infrastructure as Code with TerraformDevOps.com
When your organization is moving to cloud, the infrastructure layer transitions from running dedicated servers at limited scale to a dynamic environment, where you can easily adjust to growing demand by spinning up thousands of servers and scaling them down when not in use.
The future of DevOps is infrastructure as code. Infrastructure as code supports the growth of infrastructure and provisioning requests. It treats infrastructure as software: code that can be re-used, tested, automated and version controlled. HashiCorp Terraform adopts infrastructure as code throughout its tool to prevent configuration drift, manage immutable infrastructure and much more!
Join this webinar to learn why Infrastructure as Code is the answer to managing large scale, distributed systems and service-oriented architectures. We will cover key use cases, a demo of how to use Infrastructure as Code to provision your infrastructure and more:
Agenda:
Intro to Infrastructure as Code: Challenges & Use cases
Writing Infrastructure as Code with Terraform
Collaborating with Teams on Infrastructure
Learn how the Blue/Green Deployment methodology combined with AWS tools and services can help reduce the risks associated with software deployment. We will illustrate common patterns and highlight ways deployment risks are mitigated by each pattern. Topics will include how services like AWS CloudFormation, AWS Elastic Beanstalk, Amazon EC2 Container Service, Amazon Route53, Auto Scaling and Elastic Load Balancing can help automate deployment. We will also address how to effectively manage deployments in the context of data model and schema changes. Learn how you can adopt blue/green for your software release processes in a cost-effective and low-risk way.
AWS Code* services provide an easy way to build and operate a CI/CD pipeline for your project apps. In this session, we will cover the different AWS code services (CodeCommit, CodeBuild, CodeDeploy, CodePipeline and CodeStar) and the integration of these tools into your project.
This document provides an introduction to microservices, including:
- Microservices are small, independently deployable services that work together and are modeled around business domains.
- They allow for independent scaling, technology diversity, and enable resiliency through failure design.
- Implementing microservices requires automation, high cohesion, loose coupling, and stable APIs. Identifying service boundaries and designing for orchestration and data management are also important aspects of microservices design.
- Microservices are not an end goal but a means to solve problems of scale; they must be adopted judiciously based on an organization's needs.
The document describes Amazon EKS (Elastic Container Service for Kubernetes), including an overview of EKS, its architecture, features, and integration with other AWS services. Key points include: EKS manages Kubernetes control planes and nodes are launched in the customer's VPC, EKS supports networking via the AWS VPC CNI plugin, and EKS provides security and access management using IAM roles and policies.
Infrastructure-as-Code (IaC) Using Terraform (Advanced Edition)Adin Ermie
In this new presentation, we will cover advanced Terraform topics (full-on DevOps). We will compare the deployment of Terraform using Azure DevOps, GitHub/GitHub Actions, and Terraform Cloud. We wrap everything up with some key takeaway learning resources in your Terraform learning adventure.
NOTE: A recording of this presenting is available here: https://www.youtube.com/watch?v=fJ8_ZbOIdto&t=5574s
** Kubernetes Certification Training: https://www.edureka.co/kubernetes-certification **
This Edureka tutorial on "Kubernetes Architecture" will give you an introduction to popular DevOps tool - Kubernetes, and will deep dive into Kubernetes Architecture and its working. The following topics are covered in this training session:
1. What is Kubernetes
2. Features of Kubernetes
3. Kubernetes Architecture and Its Components
4. Components of Master Node and Worker Node
5. ETCD
6. Network Setup Requirements
DevOps Tutorial Blog Series: https://goo.gl/P0zAfF
This document provides an introduction to Amazon Web Services (AWS) and AWS Lambda. It begins with an overview of cloud computing and an explanation of what AWS is and its core services. It then discusses AWS Lambda in more detail, describing it as a serverless computing service that allows users to run code without provisioning or managing servers. The document outlines benefits of AWS Lambda like scaling, availability, and low cost. It also provides examples of common use cases for Lambda and demonstrates its capabilities through an example application.
DevOps Interview Questions Part - 2 | Devops Interview Questions And Answers ...Simplilearn
This presentation is about "DevOps interview questions" will take you through some of the most popular questions that you face in a DevOps interview. This video covers interview questions related to source code management, continuous integration, continuous testing, configuration management, containerization and continuous monitoring. "The DevOps Hiring Boom” claims that as many as 80 percent of Fortune 1000 organizations are expected to adopt DevOps by 2019. If you’ve started cross-training to prepare for development and operations roles in the IT industry, you know it’s a challenging field that will take some real preparation to break into. Here are some of the most common DevOps interview questions and answers that can help you while you prepare for DevOps roles in the industry. Learn and get a deeper understanding of these questions to set you apart from the crowd in this booming industry.
This "DevOps interview questions" presentation will answer the questions related to the topics mentioned below:
1. Configuration management - Chef, Puppet and Ansible
2. Containerization - Docker
3. Continuous monitoring - Nagios
Why learn DevOps?
Simplilearn’s DevOps training course is designed to help you become a DevOps practitioner and apply the latest in DevOps methodology to automate your software development lifecycle right out of the class. You will master configuration management; continuous integration deployment, delivery, and monitoring using DevOps tools such as Git, Docker, Jenkins, Puppet, and Nagios in a practical, hands-on and interactive approach. The DevOps training course focuses heavily on the use of Docker containers, a technology that is revolutionizing the way apps are deployed in the cloud today and is a critical skillset to master in the cloud age.
After completing the DevOps training course you will achieve hands-on expertise in various aspects of the DevOps delivery model. The practical learning outcomes of this Devops training course are:
An understanding of DevOps and the modern DevOps toolsets
The ability to automate all aspects of a modern code delivery and deployment pipeline using:
1. Source code management tools
2. Build tools
3. Test automation tools
4. Containerization through Docker
5. Configuration management tools
6. Monitoring tools
Who should take this course?
DevOps career opportunities are thriving worldwide. DevOps was featured as one of the 11 best jobs in America for 2017, according to CBS News, and data from Payscale.com shows that DevOps Managers earn as much as $122,234 per year, with DevOps engineers making as much as $151,461. DevOps jobs are the third-highest tech role ranked by employer demand on Indeed.com but have the second-highest talent deficit.
Learn more at https://www.simplilearn.com/cloud-computing/devops-practitioner-certification-training
This document discusses modernizing applications for the cloud. It outlines different paths like rehosting, refactoring, or rearchitecting applications using containers, microservices, and serverless architectures. It also discusses the importance of DevOps practices and using Azure services to assess applications, create migration roadmaps, and continuously deliver updates. Migrating applications to Azure IaaS can reduce costs while refactoring or rearchitecting can enable new capabilities and improve scalability.
This document provides an introduction to Docker, including:
- Docker allows developers to package applications with all dependencies into standardized units called containers that can run on any infrastructure.
- Docker uses namespaces and control groups to provide isolation and security between containers while allowing for more efficient use of resources than virtual machines.
- The Docker architecture includes images which are templates for creating containers, a Dockerfile to automate image builds, and Docker Hub for sharing images.
- Kubernetes is an open-source platform for automating deployment and management of containerized applications across clusters of hosts.
The document discusses infrastructure as code and related concepts. It introduces just enough operating systems using Vagrant and VeeWee to package applications. Just enough image building is covered using VeeWee to create minimal OS images from source configurations. Just enough infrastructure code is explained through configuration management tools like Chef Solo, Chef Server, and Crowbar that allow infrastructure to be coded and version controlled. The presentation aims to provide feedback to further the discussion on DevOps approaches.
Many AWS customers have adopted a DevOps model for faster and more reliable software delivery. Applying software engineering best practices such as revision control and continuous delivery to your infrastructure is essential for adopting DevOps. In this session, find out how CloudFormation and associated AWS tools allow you to leverage a DevOps model by treating infrastructure as code and applying software engineering best practices to your AWS infrastructure.
Infrastructure as Code (BBWorld/DevCon13)Mike McGarr
This document discusses infrastructure as code and provides examples using tools like Chef, Vagrant, and Jenkins. It summarizes building a Jenkins server from source control using Chef recipes to install Java, add users, and install packages to set up the service. It emphasizes best practices like version control, testing, and treating infrastructure like code.
That DevOps and Agile bring benefit is self-evident; these slides explore how the key benefits can be quantified such that a business case can be built.
Infrastructure as Code represents treating infrastructure components like software that can be version controlled, tested, and deployed. The document discusses tools and techniques for implementing Infrastructure as Code including using version control, continuous integration/delivery, configuration automation, and virtual labs for testing changes. It provides examples of workflows using these techniques and recommends starting small and evolving Infrastructure as Code practices over time.
Infrastructure as Code: Manage your Architecture with GitDanilo Poccia
With the AWS Cloud you have an on-demand, programmable infrastructure that you can manage using tools and practices from software development. You can create resources when you need and dispose of them when you don’t. Using Amazon CloudFormation you can describe your architecture in text files. To change your infrastructure, you edit those files. Having application and infrastructure code in a single, robust, versioned repository like Git gives a lot of advantages. Using AWS Elastic Beanstalk you can link your Git branches to different infrastructure environments (e.g. test, production) and automate deployments. You can create test environments on-demand, even for a short time. Instead of continuously update your resources, you can recreate them quickly from scratch, simplifying lifecycle management and making deployments immutable. As a result, you have more time to focus on the unique features of your application.
At Amazon Web Services, we think about Infrastructure as Code being able to impact not just your low level infrastructure or operating systems but everything from the virtual cement floor of your Amazon Virtual Private Cloud up through the applications your customers interface with.
Come take a tour of the space as we see it. Learn what layers there are to managing your infrastructure as code and what services and tools AWS and its Partners exist across these.
AWS Infrastructure as Code - September 2016 Webinar SeriesAmazon Web Services
AWS CloudFormation lets you model, provision, and update a collection of AWS resources with JSON templates. You can manage your Infrastructure as Code and deploy stacks from a single Amazon EC2 instance to multi-tier applications. In this session, we will explore CloudFormation best practices in planning and provisioning your AWS infrastructure. We will cover recent product updates that will help users to make the most of this service and demonstrate new features. This session will benefit both new and experienced users of CloudFormation.
Learning Objectives:
• Learn best practices for managing your infrastructure as code using CloudFormation
• Discover new techniques for making the most of CloudFormation
• Hear about the latest product updates and new features released
Who Should Attend:
• Developers, DevOps, IT Operations, Systems Administrators, Solutions Architects
Ma tesol e609 approaches to discourse analysis lecture 3Khalda Mohammed
This document provides an overview of a lecture on approaches to discourse analysis. It discusses analyzing the phrase "You know you are Sudanese if..." using various discourse analysis tools and building tasks. Examples from the phrase are analyzed to understand identities, activities, relationships, and social goods/politics conveyed. The lecture also discusses selecting topics for a coursework paper applying discourse analysis to TESOL in Sudan, outlining the paper's structure and providing an assignment to propose a topic.
This document summarizes a presentation on "Infrastructure as Code" for beginners. It discusses automating deployment, provisioning, environments, and virtual machine management through continuous integration/delivery practices and configuration management tools. Specific topics covered include deployment pipelines, desired state configuration, separating configuration for different environments, immutable infrastructure patterns, building golden images, and infrastructure automation through tools like Ansible, Packer and Terraform. A demo is provided to illustrate these concepts in action.
Implementing Infrastructure as Code ConfigMgtCamp 2017Kief Morris
Run-through of key patterns and approaches for applying software engineering practices and microservice design to infrastructure.
Infrastructure as Code is the "A" (Automation) in the "CAMS" model for DevOps.
Fully Automate Application Delivery with Puppet and F5 - PuppetConf 2014Puppet
The document discusses F5 programmability and using Puppet for automation and deployment. It provides an overview of F5 programmability tools like iRules, iApps, and iControl. It then covers benefits of using Puppet for infrastructure as code and automation. Examples are given of using REST APIs and languages like Perl and Python to programmatically configure F5 devices.
This document provides an overview of using Puppet to manage Windows configurations. It discusses the Puppet Resource Abstraction Layer (RAL) and Windows-specific resources. It also covers modules, profiles, roles, Hiera for data separation, and some examples including configuring domain membership, BGInfo, antivirus software, logon messages, local administrators, Windows Firewall, filesystem ACLs, time configuration, and monitoring agents. The document concludes with an example role configuration and encourages attendees to try out the example code.
Infrastructure as code might be literally impossibleice799
The document discusses many challenges and issues with using infrastructure as code. It notes that code operates outside of one's frame of reference unless every line is read thoroughly. It provides examples of bugs that have caused major performance problems and outlines vulnerabilities in common package management systems. The document argues that true reproducible infrastructure will require better computer system building and being honest about technology's limitations.
This presentation deals with logging in the course of mobile development, namely describing the open source logging environment built with ELK stack (ElasticSearch, Logstash and Kibana).
Presentation by Igor Rudyk (Software Engineer, GlobalLogic, Lviv), delivered at Mobile TechTalk Lviv on April 28, 2015.
More details - http://globallogic.com.ua/mobile-techtalk-lviv-2015-report
DevOps Will Save The World! : Public Safety, Public Policy, and DevOps In Context
Joshua Corman, CTO, Sonatype
Link to video: https://www.youtube.com/watch?v=K-hskShNyoo
A Reference Architecture to Enable Visibility and Traceability across the Ent...CollabNet
Software development should not be a “black box” to the business, customers or other developers. Instead collaboration across stakeholders should be the norm--business, development and operations teams. Forrester recently reported that 13% of organizations doing Agile link “upstream” agile planning with ‘“downstream” development.
As a result, executives continue to have only limited or no visibility beyond the initial planning stage of what is in a particular release. It’s not their fault, because today’s tools focus on upfront planning and don’t give you visibility into what’s happening in development. Often times that visibility is too late resulting in software that gets delivered and does not meet the customer’s needs.
Join CollabNet’s most experienced senior solution architects as they explain how you can you gain real time visibility into all stages of the development process—from ideation into production through deployment. Imagine what can your teams get done if all stakeholders are able to collaborate together and view real time feeds into all stages of the delivery pipelines within a single easy-to-use system.
Who Should attend:
Any executive or manager interested in learning how to get traceability and visibility across the enterprise-- particularly, into the build and release management functions of their application lifecycle.
What will be covered:
An enterprise-scalable reference architecture for CI, CD, and DevOps
The importance of build management, release management and application release automation integration
A blueprint for scaling business agility across a large development organization How does CollabNet help organizations solve these problems
A demonstration of TeamForge’s capabilities using Git/Gerrit, Code Review, Jenkins, Nexus, Artifactory, Chef and Automic
Building a Service Delivery Platform - JCICPH 2014Andreas Rehn
This talk will walk through the critical parts of a tool chain that forms the service delivery platform, a robust, secure solution with Jenkins as the main orchestrator that scales with many teams and hundreds of pipelines. I will show a tool chain with Git, Jenkins, Jenkins Job Builder, Puppet, Graphite, Logstash and more that is proven in battle. I will share insights and details on good ways of building a platform for pipelines that recognizes the individual teams needs for fast feedback, traceability and visibility in the delivery process.
Devops, the future is here, it's just not evenly distributed yet.Kris Buytaert
This document discusses the DevOps movement and how operations and development teams can work more collaboratively. Some key points:
- DevOps aims to break down barriers between development and operations teams through better communication and automation.
- In the past, developers would deploy code without considering operational requirements, leading to problems once code was in production. DevOps promotes developing and deploying code as a team effort between devs and ops.
- Automating processes like configuration management, continuous integration, deployment and monitoring helps align dev and ops goals and allows more frequent, lower-risk deployments. Tools like Puppet, Chef, Jenkins and Nagios are mentioned.
- The document advocates for practices like test-driven
Sascha Möllering discusses how his company moved from manual server setup and deployment to automated deployments using infrastructure as code and continuous delivery. They now deploy whenever needed using tools like Chef and JBoss to configure servers. Previously they faced challenges like manual processes, difficult rollbacks, and biweekly deployment windows. Now deployments are automated, safer, and can happen continuously.
DevOps on Windows: How to Deploy Complex Windows Workloads | AWS Public Secto...Amazon Web Services
In this session, you will learn how to deploy complex Windows workloads and ways AWS CloudFormation, AWS OpsWorks, and AWS CodeDeploy enable you to automate your Windows application life-cycle management. We will also discuss the monitoring, logging, and automatically scaling of Windows applications. Learn More: https://aws.amazon.com/government-education/
Presentation to the Perth MS Cloud Computing User Group on November 14, 2017. Covered off on how Chef, InSpec, Habitat and Chef Automate work with Windows, Azure and the Microsoft ecosystem.
My personal story from azure it pro to azure dev opsnj-azure
This document provides an agenda and summary for a presentation on how an Azure IT Pro embraced DevOps practices. The presentation discusses how the presenter started as an Azure IT Pro managing infrastructure, then learned DevOps practices like using Azure Resource Manager templates, infrastructure as code, and continuous deployment. It provides demos of authoring ARM templates in Visual Studio and "DevOps-ing" a web app. The presentation aims to help other Azure IT Pros adopt DevOps practices to deploy infrastructure and applications faster and more reliably.
Building a Continuous Delivery Pipeline With Visual StudioKasun Kodagoda
This document discusses building a continuous delivery pipeline with Visual Studio Team Services. It defines DevOps and key DevOps practices like continuous integration, deployment, and infrastructure as code. Continuous delivery aims to reduce the time between writing code and deploying to production through automation of testing and deployment. Infrastructure as code manages infrastructure using version control and templates. The document demonstrates building a continuous delivery pipeline for an ASP.Net application using Azure Resource Manager templates and Visual Studio Team Services for continuous integration and release management.
This document discusses DevOps and continuous delivery practices using AWS services. It begins by explaining the evolution from monolithic applications to microservices and DevOps. It then provides an overview of AWS services for source control (CodeCommit), continuous integration (CodeBuild), deployment (CodeDeploy), and release management (CodePipeline). It also discusses using CloudFormation for infrastructure as code and best practices for CI/CD pipelines on AWS.
T5 - Mise en place de votre processus DevOps Ofice, Office 365, SharePoint - ...SPS Monaco
Quel développeur n’a jamais rêvé d’avoir une assurance qualité de bout en bout pour éviter le stress et les cauchemars ? Historiquement avec SharePoint on a toujours dit que c’était chose compliquée, coûteuse etc…
Nous verrons un ensemble d’outils et de solutions avec Visual Studio Team Services qui vous démontreront le contraire et vous n’aurez plus d’excuses après cette session pour automatiser la qualité dans vos processus.
Au programme :
- Gestion des sources et des branches
- Build automtisé de solutions/apps SharePoint
- Déploiements automatisés
- Tests automatisés
- Qualité de code
Nombreuses démonstrations
#SPFestDc dev302 Is it possible to do #DevOps with the SharePoint Framework?Vincent Biret
The document discusses how to implement DevOps practices with the SharePoint Framework. It introduces the new toolchain for SharePoint development including IIS Express, project templates, and server-side comparisons. It then covers topics like software lifecycles, using Visual Studio Team Services and Azure for source control, builds, deployments, unit testing, and managing technical debt with tools like SonarQube. Live demos are provided of building and deploying a sample web part, running unit tests, and using SonarQube for linting. The presentation aims to demonstrate how DevOps can increase quality, consistency, save time and money when developing for SharePoint and Office 365.
National Instruments built a DevOps team to rapidly deliver new cloud-based software products using cloud hosting platforms and model-driven automation. With this approach, the small DevOps team has quickly delivered multiple major products to market with low costs. The team uses agile processes, cloud infrastructure from Amazon Web Services and Microsoft Azure, and a custom system called PIE for infrastructure automation. This has allowed National Instruments to innovate faster while maintaining reliability.
Boris Devouge (Microsoft) - DevOps on AzureOutlyer
Boris kicked off the meetup with Microsofts intro to the world of DevOps on Azure and how Microsoft is increasingly playing nice with the Open-Source world.
Video: https://www.youtube.com/watch?v=Hy86wfxT7fo
Join DevOps Exchange London here: http://www.meetup.com/DevOps-Exchange-London
Follow DOXLON on twitter http://www.twitter.com/doxlon
Chef Automate - Wellington DevOps August 2, 2017Matt Ray
Chef Automate is a platform that provides continuous automation for infrastructure, compliance, and applications. It allows users to define infrastructure, compliance policies, and application configuration as code. It also provides workflows to collaborate, build, deploy, manage, and secure automation through an integrated platform. Chef Automate utilizes open source automation engines and works with technology partners and AWS OpsWorks to provide these capabilities at scale across environments.
Software release cycles are now measured in days instead of months. Cutting edge companies are continuously delivering high quality software at a fast pace. In this session, we cover how you can begin your DevOps journey by sharing best practices and tools used by engineering teams at Amazon. We showcase how you can accelerate developer productivity by implementing continuous integration and delivery workflows. In addition, we introduce AWS CodeStar, AWS CodeCommit, AWS CodeBuild, AWS CodePipeline, AWS CodeDeploy, and AWS X-Ray, the services inspired by Amazon's internal developer tools and DevOps practices.
The document discusses how development and testing on AWS can help address challenges companies face with long wait times to obtain servers, difficulty managing multiple environments, and slow experimentation. It describes how AWS allows obtaining servers in minutes, simplifies managing environments, and enables adopting new development practices. It then goes into more detail on how AWS can provide infrastructure for development and test teams on demand through services like VPC, help teams use the tools they need with a variety of SDKs and IDEs, and support more efficient practices like continuous integration/deployment and DevOps through automation and rapid provisioning of environments.
This document provides an overview of DevOps on AWS. It discusses DevOps culture and goals of speed, reliability, and improved collaboration. It then explains why AWS is suitable for DevOps with managed services, scale, automation, and security. The document outlines components of DevOps practices including continuous integration (CI), continuous delivery (CD), infrastructure as code, and continuous monitoring. It also reviews deployment strategies and AWS developer tools to support CI/CD workflows such as CodeCommit, CodeBuild, CodeDeploy, CodePipeline, Cloud9, and CodeStar.
Dev Ops on AWS - Accelerating Software Delivery - AWS-Summit SG 2017Amazon Web Services
Today’s cutting edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share the processes followed by Amazon engineers and discuss how you can bring them to your company by using AWS CodePipeline and AWS CodeDeploy, services inspired by Amazon's internal developer tools and DevOps culture.
#ESPC18 How to do #devops with the #SharePoint Framework and why it matters?Vincent Biret
1) The document discusses how to do DevOps with the SharePoint Framework including introducing the new tooling stack for SPFx, the software development lifecycle, and Visual Studio Team Services for source control and automation.
2) It demonstrates how to set up build pipelines in VSTS to automate builds and deployments including unit testing SPFx web parts.
3) The document also discusses managing technical debt through practices like linting, static analysis, and code quality tools like SonarQube.
Enabling your DevOps culture with AWS-webinarAaron Walker
In this presentation shows you how the benefits of AWS technologies can be combined with a new approach to Development and Operations.
It’s all about delivering new features and functionality faster, without compromising reliability, stability and performance.
* Understand the challenges faced by traditional Development and Operations teams
* Apply Continuous Integration/Delivery processes and tools to enable change
* Appreciate how various AWS technologies can be used to facilitate DevOps
Continuous delivery is the process of automating the deployment of code changes to production. It involves building, testing, and deploying code changes through successive environments like integration, testing, and production. Continuous integration starts the process by automatically building and testing code changes. The release pipeline then automates deploying through environments. This finds issues early and allows for rapid deployment of code changes to production through automated testing and infrastructure provisioning.
Integrating Security into DevOps and CI / CD Environments - Pop-up Loft TLV 2017Amazon Web Services
AWS serverless architecture components such as Amazon S3, Amazon SQS, Amazon SNS, CloudWatch Logs, DynamoDB, Amazon Kinesis, and Lambda can be tightly constrained in their operation. However, it may still be possible to use some of them to propagate payloads that could be used to exploit vulnerabilities in some consuming endpoints or user-generated code. This session explores techniques for enhancing the security of these services, from assessing and tightening permissions in IAM to integrating further tools and mechanisms for inline and out-of-band payload analysis that are more typically applied to traditional server-based architectures, and generalising these techniques to APIs for all AWS services.
Devops architecture involves three main categories of infrastructure: IT infrastructure (version control, issue tracking, etc.), build infrastructure (build servers with access to source code), and test infrastructure (deployment, acceptance, and functional testing). Continuous integration involves automating the integration of code changes, while continuous delivery ensures code is always releasable but actual deployment is manual. Continuous deployment automates deployment so that any code passing tests is immediately deployed to production. The document discusses infrastructure hosting options, automation approaches, common CI/CD workflows, and provides examples of low and medium-cost devops tooling setups using open source and proprietary software.
Portfolio Rationalization - Making Sound Financial and Strategic Decisions in...Robert Greiner
This presentation outlines a methodology and set of frameworks useful for making strategic product portfolio rationalization decisions in times of uncertainty intelligently and quickly (rapid vs. rushed) regardless of organization size.
Additionally, we provide thoughts and ideas around the current emergent state of the world & market due to COVID-19 and how organizations can effectively navigate through three key phases.
Exceptional teams change the world. Dysfunctional teams don't.
This presentation offers practical guidance on how to achieve Team Flow by adopting the mindset, skillset, and toolset required to become an Ideal Team Player.
If you're a leader, we also cover how to foster an environment of Ideal Team Players.
A Point of View on effectively addressing the complexities of securing organizations of all sizes. This approach is complementary and additive to traditional enterprise security models.
Presentation I did with our CFO at a national company-wide presentation event called #FinFest2017. Topics center around the concepts around Financial Independence and practical steps you can take to achieve it as quickly as possible.
This talk is for educational and entertainment purposes only and should not be treated as investment or financial advice.
Fin fest 2014 - Internet of Things and APIsRobert Greiner
An overview of the core concepts behind the ultra-hyped Internet of Things. We start the presentation with an overview and slight re-classification of what the Internet of Things is. Then, we jump into how to *serve* the internet of things - discussing a homebrew project using the RaspberryPi and Microsoft Azure.
Today's technical landscape features workloads that can no longer be accomplished on a single server using technology from years past. As a result, we must find new ways to accommodate the increasing demands on our compute performance. Some of these new strategies introduce trade-offs and additional complexity into a system.
In this presentation, we give an overview of scaling and how to address performance concerns that business are facing, today.
In this presentation, we provide an overview of Cloud Computing and provide some details on the wide range of services that Amazon Web Services offers today. This presentation is intended for people new to cloud computing or experienced cloud developers who have not yet used AWS.
Automated Testing for Websites With Selenium IDERobert Greiner
This presentation is an overview of Automated Testing for websites using Selenium IDE. We start with an introduction and benefits around automated testing and move on to some Selenium IDE specifics.
Introduction to Windows Azure Data ServicesRobert Greiner
This document provides an overview of using Azure for data management. It discusses using PartitionKey and RowKey to organize data into partitions in Azure table storage. It also recommends using the Azure Storage Client library for .NET applications and describes retry policies for handling errors. Links are provided for additional documentation on Azure table storage and messaging between Azure services.
Slides for a talk I gave at work on the importance of code quality and some things we can do to help protect us from repeating mistakes made in the past.
Test-driven development (TDD) involves writing unit tests before production code to reduce defects and debugging time. The three rules of TDD are: 1) write failing tests before production code, 2) only write enough test code to fail initially, and 3) only write enough production code to pass failing tests. TDD results in production code that is well-tested, easier to change over time, and protected from inadvertent errors through automated tests. An example bowling game scorekeeper demonstrates TDD in practice.
This document introduces testing JavaScript code with Jasmine. It discusses that JavaScript should be tested like production code to allow changing, fixing, cleaning, and refactoring code without fear of breaking things. Tests should be fast, independent, repeatable, self-validating by passing or failing, and timely by writing tests before production code. An example is given of writing a failing test for a buggy random die rolling function, running the test to see it fail, fixing the bug, and adding more tests for documentation and confidence in changes.
1. Infrastructure as Code
Merging Development and Operations for a more
effective application development process
FIN talk
Ryan Roark
Clement Yu
Robert Greiner
February 19, 2014
2. Table of Contents
1. The Problem
2. Infrastructure
3. Application
4. Code
5. Putting it all together
6. AWS Goodness
7. Wrapping Up
5. Operations
• Server Admins
• DBAs
• Release
• Networking
• Security
• Monitoring
• Operators maintain
People who deal with applications after they are created
6. Typical Software Development Flow
Write Code
(Dev)
Create Tests Run all Tests
Deploy to
Dev/QA
(Ops)
Integration
Tests
QA Tests
Deploy to
UAT
More Testing
– Regression
(QA)
Performance
Tests
Configure
Production
Environment
Buy
Hardware
Install OS /
Software
Provision
Database
Upgrade
RAM
Deploy to
Production
Manual
Time Consuming
7. Poll: How long does it
take to provision a new
server at your client?
9. DevOps
DevOps is the practice of operations and development
engineers participating together in the entire service
lifecycle, from design through the development
process to production support. (TheAgileAdmin)
10. The New Normal
It’s up to us as developers to help enable our
operations counterparts. We can use our skills to
teach others how to make their jobs easier, so our jobs
become easier.
This requires developers to gain skills in operations:
networking, OS, patching, deployments, etc…
Every systems administrator should know Ruby and
every Developer should know how to configure an
automated deployment on a Windows or Linux server
they setup themselves
12. Infrastructure Automation
• Write your code and write the infrastructure it
runs on
• Servers, Networking, Users, etc…
• Documented, Repeatable, and Fast
• Fixing Deployment Pains
• A/B Deployments (blue/green)
• Rolling Deployments
13. Infrastructure Tooling
• CloudFormation for AWS
• Template driven design with JSON
• Templates versioned like code
• AWS::CloudFormation::Init
• Bootstrap other processes
• OPSWorks & Elastic BeanStalk for AWS
• Demo CloudFormation
16. Configuration Management
• Transform any server quickly
• Build it as a web server, DB server, etc.
• Automate build process
• Install and configuration steps are saved
as code
• Re-configure quickly
• Avoid dependency issues
17. Configuration Tools
• Powerful
• Robust
• Written
in Ruby
• Developer-
friendly
• Steep learning
curve for sys-
admins
• Mature
• Built for sys-
admins
• Easy JSON
data structure
• Master pushes
changes to
agents
• AWS version
of Chef
• Free to use
with instances
19. Continuous Integration
Deploy your code quickly, consistently,
and often
• Practice Deploying Code
• Detect problems faster
• Automatically build code & run tests
• Eliminate the “well it works on my machine”
dilemma
• Encourages public shaming
20. CI in the Sky Cloud
• Code Deploy
• Hook into source control and automate your
deployments to an elastic set of resources
• Code Pipeline
• Continuous delivery and software release automation
• Code Commit
• Code is ‘closer’ to servers it runs on
• Integrates with CodeDeploy and CodePipeline
• Demo Code Deploy
21. Automation outside AWS
• Jenkins
• Self hosted CI Server
• Travis-CI
• Hosted CI Server
• TFS / VisualStudio.com
• Does a little of EVERYTHING
• Easily integrate with Azure
24. Putting it all together
Infrastructure Provisioning
Application Provisioning
Code Provisioning
Now it’s your turn
Developers
Operations
Dev + Ops
25. 2015 AWS DevOps Challenge
Design and implement a fully-automated AWS
environment suitable for hosting and operating a
complex open-source application.
The current plan is to have a panel of judges decide
the winning team’s presentation and demo of solution
Monitor
• Dashboard
Status
Overview
Alert
• Active Push
Notifications
on Error
Log
• Application /
OS log
management
Audit
• Complete
History of
Interactions
Provision
• On-Demand
Environment
Manage
• Live
Changes to
Environment
Deploy
• Automated
Application
Deployment
Patch
• Live
Changes to
Application
26. What’s in it for me?
Gain real world, hands-on experience
with automated provisioning
(infrastructure, application, code)
Showcase your skills to the Dallas office
Gain experience on the AWS platform
Team up to design a solution that
outperforms the competition
Win a trip to the AWS re:Invent 2015
conference in Las Vegas, NV on October
6-8, 2015
27. You heard right… Your score will
(probably) be determined by Judges
29. New AWS Services
At re:Invent, AWS released a number of new services
to their line-up. Here are the highlights.
Lambda Aurora
EC2 Container
Service
31. The Automation Dream
• Automation is our client’s and your friend
• Automation is hard work
• Free to experiment
• AWS Free Tier
• Azure Free Trial