A comprehensive walkthrough of how to manage infrastructure-as-code using Terraform. This presentation includes an introduction to Terraform, a discussion of how to manage Terraform state, how to use Terraform modules, an overview of best practices (e.g. isolation, versioning, loops, if-statements), and a list of gotchas to look out for.
For a written and more in-depth version of this presentation, check out the "Comprehensive Guide to Terraform" blog post series: https://blog.gruntwork.io/a-comprehensive-guide-to-terraform-b3d32832baca
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.
This document discusses Terraform, an open-source infrastructure as code tool. It begins by explaining how infrastructure can be defined and managed as code through services that have APIs. It then provides an overview of Terraform, including its core concepts of providers, resources, and data sources. The document demonstrates Terraform's declarative configuration syntax and process of planning and applying changes. It also covers features like modules, state management, data sources, and developing custom plugins.
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
Terraform is a tool for building, changing, and version controlling infrastructure safely and efficiently. It allows users to define and provision resources through code rather than manual configuration. Key concepts include variables, outputs, providers that interface with cloud platforms, reusable modules, and managing infrastructure through commands like plan, apply, and destroy. The presentation demonstrated Terraform's capabilities with a live demo and provided additional resources for learning more.
The document provides an overview of Terraform and discusses why it was chosen over other infrastructure as code tools. It outlines an agenda covering Terraform installation, configuration, and use of data sources and resources to build example infrastructure including a VCN, internet gateway, subnets, and how to taint and destroy resources. The live demo then walks through setting up Terraform and using it to provision example OCI resources.
While many organizations have started to automate their software develop processes, many still engineer their infrastructure largely by hand. Treating your infrastructure just like any other piece of code creates a “programmable infrastructure” that allows you to take full advantage of the scalability and reliability of the AWS cloud. This session will walk through practical examples of how AWS customers have merged infrastructure configuration with application code to create application-specific infrastructure and a truly unified development lifecycle. You will learn how AWS customers have leveraged tools like CloudFormation, orchestration engines, and source control systems to enable their applications to take full advantage of the scalability and reliability of the AWS cloud, create self-reliant applications, and easily recover when things go seriously wrong with their infrastructure.
This document discusses infrastructure as code and the HashiCorp ecosystem. Infrastructure as code allows users to define and provision infrastructure through code rather than manual configuration. It can be used to launch, create, change, and downscale infrastructure based on configuration files. Tools like Terraform allow showing what changes will occur before applying them through files like main.tf and variables.tf. Terraform is part of the broader HashiCorp ecosystem of tools.
Building infrastructure as code using Terraform - DevOps KrakowAnton Babenko
This document provides an overview of a DevOps meetup on building infrastructure as code using Terraform. The agenda includes Terraform basics, frequent questions, and problems. The presenter then discusses Terraform modules, tools, and solutions. He addresses common questions like secrets handling and integration with other tools. Finally, he solicits questions from the audience on Terraform use cases and challenges.
This document discusses Terraform, an open source tool for building, changing, and versioning infrastructure safely and efficiently. It provides declarative configuration files to manage networks, virtual machines, containers, and other infrastructure resources. The document introduces Terraform and how it works, provides examples of Terraform code and its output, and offers best practices for using Terraform including separating infrastructure code from application code, using modules, and managing state. Terraform allows infrastructure to be treated as code, provides a faster development cycle than other tools like CloudFormation, and helps promote a devOps culture.
This document provides an introduction and overview of Terraform, including what it is, why it is used, common use cases, and how it compares to CloudFormation. It then demonstrates hands-on examples of using Terraform to provision AWS resources like S3 buckets, EC2 instances, and CloudFront distributions. The workflow of initializing, planning, and applying changes with Terraform is also outlined.
Are you looking to automate your infrastructure but not sure where to start? View this presentation on ‘Getting started with Infrastructure as code’ to learn how to leverage IaC to deploy and manage resources on Azure. You will learn:
• Introduction to IaC
• Develop a simple IaC using Terraform
• Manage the deployed infrastructure using Terraform
View webinar recording at https://www.winwire.com/webinars
This document summarizes a meetup about infrastructure as code. It discusses the differences between treating infrastructure as "pets" versus "cattle", where pets are cared for individually and cattle are treated as disposable. When infrastructure is coded declaratively using tools like Terraform, the infrastructure can be version controlled, updated continuously, and rolled back like code. The meetup demonstrated setting up infrastructure on Azure using Terraform to define resources like virtual machines in code. Advanced techniques like storing state remotely and using modules were also discussed.
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
How to test infrastructure code: automated testing for Terraform, Kubernetes,...Yevgeniy Brikman
This talk is a step-by-step, live-coding class on how to write automated tests for infrastructure code, including the code you write for use with tools such as Terraform, Kubernetes, Docker, and Packer. Topics covered include unit tests, integration tests, end-to-end tests, test parallelism, retries, error handling, static analysis, and more.
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, tools, benefits, paradigms and more.
Presentation from DigitalOnUs DevOps: Infrastructure as Code Meetup (September 20, 2018 - Monterrey Nuevo Leon MX)
This document provides an introduction to Terraform and its key concepts. It describes Terraform as a tool for building, changing, and versioning infrastructure safely and efficiently using declarative configuration files. The document outlines some of Terraform's main components like providers, data sources, resources, variables and outputs. It also discusses the benefits of structuring Terraform configurations using modules to improve reusability and manageability.
This talk is a very quick intro to Docker, Terraform, and Amazon's EC2 Container Service (ECS). In just 15 minutes, you'll see how to take two apps (a Rails frontend and a Sinatra backend), package them as Docker containers, run them using Amazon ECS, and to define all of the infrastructure-as-code using Terraform.
This document discusses asynchronous I/O in Java and Scala using the Play Framework. It describes how LinkedIn uses a service-oriented architecture with hundreds of services making requests to each other. It then covers how Play supports non-blocking I/O using asynchronous code, promises, and futures to allow parallel requests without blocking threads. Key points covered include using map and flatMap to transform promises and futures, handling errors and timeouts, and the benefits of non-blocking I/O for scalability.
Listen up, developers. You are not special. Your infrastructure is not a beautiful and unique snowflake. You have the same tech debt as everyone else. This is a talk about a better way to build and manage infrastructure: Terraform Modules. It goes over how to build infrastructure as code, package that code into reusable modules, design clean and flexible APIs for those modules, write automated tests for the modules, and combine multiple modules into an end-to-end techs tack in minutes.
You can find the video here: https://www.youtube.com/watch?v=LVgP63BkhKQ
This document discusses rapid prototyping techniques for quickly building products from ideas. Rapid prototyping allows developers to build products faster through instant feedback on code changes and leveraging existing open source libraries. It is suggested that dynamic languages, interactive development environments, and pushing code to the browser can provide very fast feedback. While prototypes may be thrown away, the rapid trial and error process of prototyping can lead to higher quality products and better engineers through continuously improving ideas.
The document discusses LinkedIn's adoption of the Dust templating language in 2011. Some key points:
- LinkedIn needed a unified view layer as different teams were using different templating technologies like JSP, GSP, ERB.
- They evaluated 26 templating options and selected Dust as it best met their criteria like performance, i18n support, and being logic-less.
- Dust templates are compiled to JavaScript for client-side rendering and to Java for server-side rendering (SSR) through Google's V8 engine, allowing templates to work on both client and server.
- SSR addresses challenges like SEO, supporting clients without JavaScript, and i18n by rendering
This is the story of the Hackday and[in]cubator programs at LinkedIn; this is the story of scalable, best-of-breed methods for driving innovation; this is the story of transformation: of your career, company, and the world.
Video of the live presentation: http://tcbaltics.com/video/jim-brikman
Azure Infrastructure as Code and Hashicorp TerraformAlex Mags
This document discusses using Infrastructure as Code with Terraform and Azure. It begins with an introduction to Terraform and how it can be used to manage Azure infrastructure in a declarative way. The document then covers the Terraform workflow including editing configuration files, running a plan, and deploying infrastructure. It demonstrates Terraform through a live demo and discusses how it can benefit operations, security, and development teams. It concludes by discussing the partnership between Microsoft and HashiCorp to further integrate Terraform with Azure.
WinOps Conference London 2017 session
Public Cloud IaaS vs traditional on prem and how Hashicorp Terraform is a great tool to configure Azure. Recorded here: https://www.youtube.com/watch?v=LDZXRBBuXCU
Alex Magnay - Azure Infrastructure as Code with Hashicorp TerraformWinOps Conf
This document summarizes a presentation about using Terraform and Azure. The presentation introduces Infrastructure as Code and Terraform, shows how to manage Azure resources with Terraform, demonstrates the Terraform workflow, and discusses use cases for operations, security, and development teams. It also covers tips for using Terraform effectively and safely with Azure. Microsoft and Hashicorp have partnered to improve support for provisioning Azure services with Terraform.
Six Startup Lessons & The Essence of Venture CapitalAllan Martinson
This document provides 6 lessons for startups based on the author's experience. The 3 main points are:
1. Lesson 1 emphasizes that startups are about people, not just business ideas. It takes years of incubation and the right founding team with complementary skills and values to succeed.
2. Lesson 3 stresses the importance of pivoting if a startup fails to gain product/market fit or customer validation within set milestones. Slow failure is worse than failure.
3. Lesson 6 advises that raising venture capital requires understanding the venture capital process and life cycle of typical high-tech companies. It is important to pick smart investors who will provide long-term support.
To go faster in a car, you need not only a powerful engine, but also safety mechanisms like brakes, air bags, and seat belts. This is a talk about the safety mechanisms that allow you to build software faster. It's based on the book "Hello, Startup" (http://www.hello-startup.net/). You can find the video of the talk here: https://www.youtube.com/watch?v=4fKm6ImKml8
The Truth About Startups: What I wish someone had told me about entrepreneurs...Yevgeniy Brikman
This is the talk I gave at MIT's Martin Center for Entrepreneurship. It's a talk I wish someone gave me when I was in college to help me think about the role of entrepreneurship and startups in my career.
You can find the video of the talk here: https://www.youtube.com/watch?v=Rus32iR_Ag0
A brief overview of what we do at Gruntwork. Learn what we mean by "DevOps as a Service" and how you can get your entire infrastructure, defined as code, in about a day. https://www.gruntwork.io/
Practical workshop at UX London 2016, delivered by Doug Morwood of Business Models Inc UK. Great Value Proposition Design leads to great business success. Why? Because only by truly understanding the needs of the customer can we design solutions that last.
Business Model Innovation by Business Models Inc. Training SummaryBusiness Models Inc.
This document provides an overview of a training on business model innovation. It discusses how the world is changing and the need to design better business models. It introduces techniques for business model innovation such as applying business model patterns, looking at options to change various elements of the business model like customers or revenue streams, and using techniques like "what if" scenarios. The training emphasizes an iterative process of exploring options, testing assumptions, and getting feedback to design new business model prototypes.
Virtual Business Incubator Framework for Enriching Innovation Ecosystem 2013Vasily Ryzhonkov
The main purpose of this work is to find possible solutions for overcoming challenges of existing business incubation models. The end goal is to provide practitioners with the model of economic development tool which will help them to build new generation of business incubators, e.g. to guide management teams, policy makers, entrepreneurs and educators in establishing a successful business incubation program (BIP). Eventually the model intends to expand the limits of existing business incubation models.
Effective Marketing for the Public Practitioner - Presentation by Michael 'M...Practice Paradox
The document provides an overview of a marketing presentation for public practitioners given by Michael 'MC' Carter. Some key points:
1. The presentation covers why marketing has become a focus for many accounting firms, dispels common myths about marketing, and provides practical marketing tips.
2. A survey found the top challenges facing firms are growth, profitability, and cash flow. Many accountants have not received marketing or sales training.
3. The presentation defines an effective marketing machine and emphasizes measuring client relationships through the number of services provided per client. Niching and understanding social styles can help firms improve their marketing.
The document discusses the key components of a business model including users/customers, products/services, revenue flows, pricing, demand creation, and sales/distribution. It defines users as those who interact with the product for free, customers as those who pay for the product, and markets as customer segments. The business model canvas maps these components to understand what problem is being solved, who has this problem, how value is delivered and monetized, and how users and customers are acquired.
The document provides an overview of a workshop on business model design. It introduces business model canvas as a tool to visualize and design business models. Examples are used to illustrate how the canvas can be applied to understand Spotify's business model. Additional tools like vision canvas and context canvas are introduced. Tips are provided on how to use the business model canvas for redesign and innovation, including testing assumptions with customers and applying patterns from other business models.
My talk at FullStackFest, 4.9.2017. Become more familiar with managing infrastructure using Terraform, Packer and deployment pipeline. Code repository - https://github.com/antonbabenko/terraform-deployment-pipeline-talk
This document provides an overview of Terraform, an open-source infrastructure as code tool. It discusses Terraform's goals of providing a unified view of infrastructure, composing multiple tiers of infrastructure from IaaS to PaaS to SaaS, and safely changing infrastructure over time with one workflow. Key features highlighted include being open source, using infrastructure as code, resource providers that interface with cloud APIs, and the plan and apply workflow. The document also covers topics like collaboration and version history in Terraform Enterprise, file examples, the plan and apply commands, resource providers, and new features in recent Terraform versions like destroy provisioners, remote backends, state locking, and state environments.
Presentación empleada en el primer MeetUp AWS del grupo de usuarios de Valencia.
Infraestructura como código empleando Terraform. Se muestra las principales características de esta tecnología que nos permite ser más ágiles y rápidos desplegando nuestras plataformas en AWS.
Terraform modules provide reusable, composable infrastructure components. The document discusses restructuring infrastructure code into modules to make it more reusable, testable, and maintainable. Key points include:
- Modules should be structured in a three-tier hierarchy from primitive resources to generic services to specific environments.
- Testing modules individually increases confidence in changes.
- Storing module code and versions in Git provides versioning and collaboration.
- Remote state allows infrastructure to be shared between modules and deployments.
Speaker: Jacob Aae Mikkelsen
Once you have successfully developped your application in Grails, Ratpack or your other favorite framework, you would like to see it deployed as fast and painless as possible, right?
This talk will cover some of the supporting cast members of a succesful modern infrastructure, that developers can understand and use efficiently, and with good DevOps practices.
Key elements are
Docker
Infrastructure as Code
Container Orchestration
The demo-goods will hopefully be on our side, as this talk includes quite some live demos!
PuppetDB: Sneaking Clojure into Operationsgrim_radical
The document provides an overview of PuppetDB, which is a system for storing and querying data about infrastructure as code and system configurations. Some key points:
- PuppetDB stores immutable data about systems and allows querying of this data to enable higher-level infrastructure operations.
- It uses techniques like command query responsibility separation (CQRS) to separate write and read pipelines for better performance and reliability.
- The data is stored in a relational database for efficient querying, and queries are expressed in an abstract syntax tree (AST)-based language.
- The system is designed for speed, reliability, and ease of deployment in operations. It leverages techniques from Clojure and the JVM.
This document contains biographical information about Boulos Dib, an independent consultant specializing in software development. It provides details about Dib's early experience with personal computers and programming languages. It also lists upcoming presentations by Dib on LightSwitch and Silverlight at the NYC Code Camp in October 2011. The document concludes with an overview of PowerShell scripting.
Declare your infrastructure: InfraKit, LinuxKit and MobyMoby Project
InfraKit is a toolkit for infrastructure orchestration. With an emphasis on immutable infrastructure, it breaks down infrastructure automation and management processes into small, pluggable components. These components work together to actively ensure the infrastructure state matches the user's specifications. InfraKit therefore provides infrastructure support for higher-level container orchestration systems and can make your infrastructure self-managing and self-healing.
https://www.youtube.com/watch?v=IeweKUdHJc4
My presentation from Hashiconf 2017, discussing our use of Terraform, and our techniques
to help make it safe and accessible.
Using Terraform to manage the configuration of a Cisco ACI fabric.Joel W. King
Terraform is an open-source infrastructure as code software tool created by HashiCorp. It is written in GoLang. Cisco has developed an ACI terraform provider used to interact with the Cisco APIC. Network engineers define and provision the ACI infrastructure using a declarative configuration language known as HCL, HashiCorp Configuration Language.
This session will begin with a short presentation on Terraform and how it can be used to manage resources in an ACI fabric. There is a companion GitLab repository (https://gitlab.com/joelwking/terraform_aci) which will be used as a demo environment. Attendees can download Vagrant and VirtualBox to their laptop and execute the demonstration using the Cisco DevNet Always-on ACI sandbox.
Immutable Deployments with AWS CloudFormation and AWS LambdaAOE
This document describes an immutable infrastructure approach using AWS Lambda and CloudFormation. Key points:
- Infrastructure is defined as code using CloudFormation templates for reproducibility and versioning.
- Lambda functions are used to provision resources, configure settings, run tests, and clean up resources to enforce immutability.
- A pipeline handles building AMIs, deploying stacks, testing, updating DNS, and deleting old stacks in an automated and repeatable way.
Aprovisionamiento multi-proveedor con Terraform - Plain Concepts DevOps dayPlain Concepts
La infraestructura como código (IaC) es una de las prácticas relacionadas con la cultura DevOps que está cogiendo más tracción en el desarrollo de software y Terraform es una de las herramientas más recomendadas para ello.
Se suele relacionar sobre todo con la creación de infraestructura en los grandes servicios “Cloud” -AWS, Azure, Google Cloud,…- pero es además algo aplicable a otros aspectos de IT como podrían ser la creación de usuarios en servicios de terceros o propios (Github, bases de datos,…), configuración de dominios (Dyn, GoDaddy,…), configuración de alertas (Grafana, OpsGenie)…
Durante esta sesión se explicará su funcionamiento básico y veremos en directo despliegues en varias de estas plataformas.
Jan Stępień - GraalVM: Fast, Polyglot, Native - Codemotion Berlin 2018Codemotion
GraalVM challenges the status quo on the JVM. This newly-released JIT compiler brings substantial speed improvements and support for polyglot applications. It also allows us to translate our JVM bytecode into self-contained native binaries. In this session we’ll explore GraalVM’s potential. We’ll focus on Clojure, but our discussion will apply to many more programming languages. We’ll use GraalVM to build small native binaries. We’ll discuss the method’s limitations and their impact. Finally, we’ll build complete Clojure web apps weighing a fraction of their traditional JVM incarnations.
LAMP Stack (Reloaded) - Infrastructure as Code with Terraform & PackerJan-Christoph Küster
Talk given at Coding Leipzig Meetup (8th August, 2018).
Why infrastructure should be managed as code (IaC), a small intro to the IaC-tooling Terraform (and Packer), and a demo that shows how to use Terraform to deploy a good old LAMP Stack into the Cloud by the push of a button (https://github.com/cloudetc/lamp-stack-for-aws).
This document provides an overview of Terraform including its key features, installation process, and common usage patterns. Terraform allows infrastructure to be defined as code and treated similarly to other code. It generates execution plans to avoid surprises when provisioning resources. Complex changes can be automated while avoiding human errors. The document covers installing Terraform, deploying AWS EC2 instances, variables, outputs, modules, and workspaces. It demonstrates how Terraform can be used to provision and manage infrastructure in a safe, efficient manner.
Session talk presented at Innosoft 2022.11.11 University of Sevilla.
Presented the concept of Infrastructure as Core and its practical approach using Hashicorp Terraform a a tool to provision in the cloud. Examples with AWS are provided in a Guthub repository.
Cloud adoption fails - 5 ways deployments go wrong and 5 solutionsYevgeniy Brikman
"All happy cloud deployments are alike; each unhappy cloud deployment is unhappy in its own way." — Leo Tolstoy, Site Reliability Engineer
At Gruntwork, I've had the chance to see the cloud adoption journeys of hundreds of companies, from tiny startups to Fortune 50 giants. I've seen those journeys go well. I've seen those journeys go poorly. In this talk, I discuss a few of the ways cloud adoption can go horribly wrong (massive cost overruns, endless death marches, security disasters), and more importantly, how you can get it right.
To help you get it right, we looked at the cloud journeys that were successful and extracted from them the patterns they had in common. We distilled all this experience down into something called the Gruntwork Production Framework, which defines five concrete steps you can follow to adopt the cloud at your own company—and hopefully, to end up with your very own happy cloud deployment.
Lessons learned from writing over 300,000 lines of infrastructure codeYevgeniy Brikman
This talk is a concise masterclass on how to write infrastructure code. I share key lessons from the “Infrastructure Cookbook” we developed at Gruntwork while creating and maintaining a library of over 300,000 lines of infrastructure code that’s used in production by hundreds of companies. Come and hear our war stories, laugh about all the mistakes we’ve made along the way, and learn what Terraform, Packer, Docker, and Go look like in the wild.
Infrastructure as code: running microservices on AWS using Docker, Terraform,...Yevgeniy Brikman
This is a talk about managing your software and infrastructure-as-code that walks through a real-world example of deploying microservices on AWS using Docker, Terraform, and ECS.
Every startup begins with an idea. This is a talk on how to come up with startup ideas and how to use validation to pick the ones worth working on. It's based on the book "Hello, Startup" (http://www.hello-startup.net/). You can find the video of the talk here: https://www.youtube.com/watch?v=GkmiE8d_5Pw
A guide to hiring based on my book, "Hello, Startup". Learn who to hire, where to find them, how to interview them, and how to make an offer they can't refuse.
Recording: https://www.youtube.com/watch?v=jaSmYLymc0U
Book: http://www.hello-startup.net
This is an excerpt from my talk "Startup DNA" (http://www.slideshare.net/brikis98/startup-dna) that just focuses on the "Speed Wins" concept. For more info, check out my book "Hello, Startup: A Programmer's Guide to Building Products, Technologies, and Teams" at http://www.hello-startup.net.
Node.js vs Play Framework (with Japanese subtitles)Yevgeniy Brikman
Video: http://www.nicovideo.jp/watch/1410857293
Here's the showdown you've been waiting for: Node.js vs Play Framework. Both are popular open source web frameworks that are built for developer productivity, asynchronous I/O, and the real time web. But which one is easier to learn, test, deploy, debug, and scale? Should you pick Javascript or Scala? The Google v8 engine or the JVM? NPM or Ivy? Grunt or SBT? Two frameworks enter, one framework leaves.
This version of the presentation has Japanese subtitles. For the English only version, see http://www.slideshare.net/brikis98/nodejs-vs-play-framework
Video: https://www.youtube.com/watch?v=b6yLwvNSDck
Here's the showdown you've been waiting for: Node.js vs Play Framework. Both are popular open source web frameworks that are built for developer productivity, asynchronous I/O, and the real time web. But which one is easier to learn, test, deploy, debug, and scale? Should you pick Javascript or Scala? The Google v8 engine or the JVM? NPM or Ivy? Grunt or SBT? Two frameworks enter, one framework leaves.
This is the English version of the presentation. For the version with Japanese subtitles, see http://www.slideshare.net/brikis98/nodejs-vs-play-framework-with-japanese-subtitles
Web pages can get very complex and slow. In this talk, I share how we solve some of these problems at LinkedIn by leveraging composition and streaming in the Play Framework. This was my keynote for Ping Conference 2014 ( http://www.ping-conf.com/ ): the video is on ustream ( http://www.ustream.tv/recorded/42801129 ) and the sample code is on github ( https://github.com/brikis98/ping-play ).
Video of the presentation: http://www.youtube.com/watch?v=8z3h4Uv9YbE
At LinkedIn, we have started to use the Play Framework to build front-end and back-end services at massive scale. Play does things a little differently: it's a Java and Scala web framework, but it doesn't follow the servlet spec; it's fairly new, but it runs on top of robust technologies like Akka and Netty; it uses a thread pool, but it's built for non-blocking I/O and reactive programming; most importantly, it's high performance, but also high productivity. We've found that the Play Framework is one of the few frameworks that is able to maintain the delicate balance of performance, reliability, and developer productivity. In the Java and Scala world, nothing even comes close. In this talk, I'll share what we've learned so far, including details of rapid iteration with Java and Scala, the story behind async I/O on the JVM, support for real time web apps (comet, WebSockets), and integrating Play into a large existing codebase.
Startup DNA: the formula behind successful startups in Silicon Valley (update...Yevgeniy Brikman
[Updated May 5, 2017] "Successful startups are all alike; every unsuccessful startup is unsuccessful in its own way." These are my personal observations on a few traits that make startups successful. You can find a video of the talk at https://www.youtube.com/watch?v=z_D9oXCK2lM and the book at http://www.hello-startup.net/.
Are you interested in learning about creating an attractive website? Here it is! Take part in the challenge that will broaden your knowledge about creating cool websites! Don't miss this opportunity, only in "Redesign Challenge"!
How RPA Help in the Transportation and Logistics Industry.pptxSynapseIndia
Revolutionize your transportation processes with our cutting-edge RPA software. Automate repetitive tasks, reduce costs, and enhance efficiency in the logistics sector with our advanced solutions.
this resume for sadika shaikh bca studentSadikaShaikh7
I am a dedicated BCA student with a strong foundation in web technologies, including PHP and MySQL. I have hands-on experience in Java and Python, and a solid understanding of data structures. My technical skills are complemented by my ability to learn quickly and adapt to new challenges in the ever-evolving field of computer science.
Navigating Post-Quantum Blockchain: Resilient Cryptography in Quantum Threatsanupriti
In the rapidly evolving landscape of blockchain technology, the advent of quantum computing poses unprecedented challenges to traditional cryptographic methods. As quantum computing capabilities advance, the vulnerabilities of current cryptographic standards become increasingly apparent.
This presentation, "Navigating Post-Quantum Blockchain: Resilient Cryptography in Quantum Threats," explores the intersection of blockchain technology and quantum computing. It delves into the urgent need for resilient cryptographic solutions that can withstand the computational power of quantum adversaries.
Key topics covered include:
An overview of quantum computing and its implications for blockchain security.
Current cryptographic standards and their vulnerabilities in the face of quantum threats.
Emerging post-quantum cryptographic algorithms and their applicability to blockchain systems.
Case studies and real-world implications of quantum-resistant blockchain implementations.
Strategies for integrating post-quantum cryptography into existing blockchain frameworks.
Join us as we navigate the complexities of securing blockchain networks in a quantum-enabled future. Gain insights into the latest advancements and best practices for safeguarding data integrity and privacy in the era of quantum threats.
Details of description part II: Describing images in practice - Tech Forum 2024BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
Blockchain and Cyber Defense Strategies in new genre timesanupriti
Explore robust defense strategies at the intersection of blockchain technology and cybersecurity. This presentation delves into proactive measures and innovative approaches to safeguarding blockchain networks against evolving cyber threats. Discover how secure blockchain implementations can enhance resilience, protect data integrity, and ensure trust in digital transactions. Gain insights into cutting-edge security protocols and best practices essential for mitigating risks in the blockchain ecosystem.
Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...Erasmo Purificato
Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)
AC Atlassian Coimbatore Session Slides( 22/06/2024)apoorva2579
This is the combined Sessions of ACE Atlassian Coimbatore event happened on 22nd June 2024
The session order is as follows:
1.AI and future of help desk by Rajesh Shanmugam
2. Harnessing the power of GenAI for your business by Siddharth
3. Fallacies of GenAI by Raju Kandaswamy
UiPath Community Day Kraków: Devs4Devs ConferenceUiPathCommunity
We are honored to launch and host this event for our UiPath Polish Community, with the help of our partners - Proservartner!
We certainly hope we have managed to spike your interest in the subjects to be presented and the incredible networking opportunities at hand, too!
Check out our proposed agenda below 👇👇
08:30 ☕ Welcome coffee (30')
09:00 Opening note/ Intro to UiPath Community (10')
Cristina Vidu, Global Manager, Marketing Community @UiPath
Dawid Kot, Digital Transformation Lead @Proservartner
09:10 Cloud migration - Proservartner & DOVISTA case study (30')
Marcin Drozdowski, Automation CoE Manager @DOVISTA
Pawel Kamiński, RPA developer @DOVISTA
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
09:40 From bottlenecks to breakthroughs: Citizen Development in action (25')
Pawel Poplawski, Director, Improvement and Automation @McCormick & Company
Michał Cieślak, Senior Manager, Automation Programs @McCormick & Company
10:05 Next-level bots: API integration in UiPath Studio (30')
Mikolaj Zielinski, UiPath MVP, Senior Solutions Engineer @Proservartner
10:35 ☕ Coffee Break (15')
10:50 Document Understanding with my RPA Companion (45')
Ewa Gruszka, Enterprise Sales Specialist, AI & ML @UiPath
11:35 Power up your Robots: GenAI and GPT in REFramework (45')
Krzysztof Karaszewski, Global RPA Product Manager
12:20 🍕 Lunch Break (1hr)
13:20 From Concept to Quality: UiPath Test Suite for AI-powered Knowledge Bots (30')
Kamil Miśko, UiPath MVP, Senior RPA Developer @Zurich Insurance
13:50 Communications Mining - focus on AI capabilities (30')
Thomasz Wierzbicki, Business Analyst @Office Samurai
14:20 Polish MVP panel: Insights on MVP award achievements and career profiling
Fluttercon 2024: Showing that you care about security - OpenSSF Scorecards fo...Chris Swan
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge.
You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter.
The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
Transcript: Details of description part II: Describing images in practice - T...BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and slides: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
The Rise of Supernetwork Data Intensive ComputingLarry Smarr
Invited Remote Lecture to SC21
The International Conference for High Performance Computing, Networking, Storage, and Analysis
St. Louis, Missouri
November 18, 2021
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data.
The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs.
Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution!
Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.
INDIAN AIR FORCE FIGHTER PLANES LIST.pdfjackson110191
These fighter aircraft have uses outside of traditional combat situations. They are essential in defending India's territorial integrity, averting dangers, and delivering aid to those in need during natural calamities. Additionally, the IAF improves its interoperability and fortifies international military alliances by working together and conducting joint exercises with other air forces.
2. We’ve pre-written Terraform
packages for the most common
AWS components.
We test, update, and support
these packages.
When a software team
purchases a package, they get
100% of the source code.
http://gruntwork.io
Gruntwork
11. provider "aws" {
region = "us-east-1"
}
resource "aws_instance" "example" {
ami = "ami-408c7f28"
instance_type = "t2.micro"
tags { Name = "terraform-example" }
}
This template creates a single EC2
instance in AWS
12. > terraform plan
+ aws_instance.example
ami: "" => "ami-408c7f28"
instance_type: "" => "t2.micro"
key_name: "" => "<computed>"
private_ip: "" => "<computed>"
public_ip: "" => "<computed>"
Plan: 1 to add, 0 to change, 0 to destroy.
Use the plan command to see
what you’re about to deploy
16. variable "name" {
description = "The name of the EC2 instance"
}
Define a variable. description,
default, and type are optional.
17. resource "aws_instance" "example" {
ami = "ami-408c7f28"
instance_type = "t2.micro"
tags { Name = "${var.name}" }
}
Note the use of ${} syntax to
reference var.name in tags
variable "name" {
description = "The name of the EC2 instance"
}
18. > terraform plan
var.name
Enter a value: foo
~ aws_instance.example
tags.Name: "terraform-example" => "foo"
Use plan to verify your changes. It
prompts you for the variable.
19. > terraform apply -var name=foo
aws_instance.example: Refreshing state...
aws_instance.example: Modifying...
tags.Name: "terraform-example" => "foo"
aws_instance.example: Modifications complete
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
You can also pass variables using
the -var parameter
21. resource "aws_eip" "example" {
instance = "${aws_instance.example.id}”
}
Notice the use of ${} to depend on
the id of the aws_instance
resource "aws_instance" "example" {
ami = "ami-408c7f28"
instance_type = "t2.micro"
tags { Name = "${var.name}" }
}
28. > ls -al
-rw-r--r-- 6024 Apr 5 17:58 terraform.tfstate
-rw-r--r-- 6024 Apr 5 17:58 terraform.tfstate.backup
By default, state is stored locally
in .tfstate files
29. > terraform remote config
-backend=s3
-backend-config=bucket=my-s3-bucket
-backend-config=key=terraform.tfstate
-backend-config=encrypt=true
-backend-config=region=us-east-1
You can enable remote state
storage in S3, Atlas, Consul, etc.
46. variable "name" {
description = "The name of the EC2 instance"
}
variable "ami" {
description = "The AMI to run on the EC2 instance"
}
variable "port" {
description = "The port to listen on for HTTP requests"
}
Specify module inputs in vars.tf
47. resource "aws_instance" "example" {
ami = "${var.ami}"
instance_type = "t2.micro"
user_data = "${template_file.user_data.rendered}"
tags { Name = "${var.name}" }
}
Create resources in main.tf
48. output "url" {
value = "http://${aws_instance.example.ip}:${var.port}"
}
Specify outputs in outputs.tf
53. module "example_rails_app" {
source = "git::git@github.com:foo/bar.git//module?ref=0.1"
name = "Example Rails App"
ami = "ami-123asd1"
port = 8080
}
Specify the module’s inputs like
any other Terraform resource
54. module "example_rails_app_stg" {
source = "./rails-module"
name = "Example Rails App staging"
}
module "example_rails_app_prod" {
source = "./rails-module"
name = "Example Rails App production"
}
You can reuse the same module
multiple times
55. > terraform get -update
Get: file:///home/ubuntu/modules/rails-module
Get: file:///home/ubuntu/modules/rails-module
Get: file:///home/ubuntu/modules/asg-module
Get: file:///home/ubuntu/modules/vpc-module
Run the get command before
running plan or apply
65. global (Global resources such as IAM, SNS, S3)
└ main.tf
└ .terragrunt
stage (Non-production workloads, testing)
└ main.tf
└ .terragrunt
prod (Production workloads, user-facing apps)
└ main.tf
└ .terragrunt
mgmt (DevOps tooling such as Jenkins, Bastion Host)
└ main.tf
└ .terragrunt
66. global (Global resources such as IAM, SNS, S3)
└ main.tf
└ .terragrunt
stage (Non-production workloads, testing)
└ main.tf
└ .terragrunt
prod (Production workloads, user-facing apps)
└ main.tf
└ .terragrunt
mgmt (DevOps tooling such as Jenkins, Bastion Host)
└ main.tf
└ .terragruntEach folder gets its own .tfstate
67. global (Global resources such as IAM, SNS, S3)
└ main.tf
└ .terragrunt
stage (Non-production workloads, testing)
└ main.tf
└ .terragrunt
prod (Production workloads, user-facing apps)
└ main.tf
└ .terragrunt
mgmt (DevOps tooling such as Jenkins, Bastion Host)
└ main.tf
└ .terragrunt
Use terraform_remote_state to share
state between them
74. global (Global resources such as IAM, SNS, S3)
└ iam
└ sns
stage (Non-production workloads, testing)
└ vpc
└ mysql
└ frontend
prod (Production workloads, user-facing apps)
└ vpc
└ mysql
└ frontend
mgmt (DevOps tooling such as Jenkins, Bastion Host)
└ vpc
└ bastion
75. global (Global resources such as IAM, SNS, S3)
└ iam
└ sns
stage (Non-production workloads, testing)
└ vpc
└ mysql
└ frontend
prod (Production workloads, user-facing apps)
└ vpc
└ mysql
└ frontend
mgmt (DevOps tooling such as Jenkins, Bastion Host)
└ vpc
└ bastion
Each component in each environment
gets its own .tfstate
76. global (Global resources such as IAM, SNS, S3)
└ iam
└ sns
stage (Non-production workloads, testing)
└ vpc
└ mysql
└ frontend
prod (Production workloads, user-facing apps)
└ vpc
└ mysql
└ frontend
mgmt (DevOps tooling such as Jenkins, Bastion Host)
└ vpc
└ bastion
Use terraform_remote_state to share
state between them
78. stage
└ vpc
└ mysql
└ frontend
prod
└ vpc
└ mysql
└ frontend
How do you avoid copy/pasting code
between stage and prod?
79. stage
└ vpc
└ mysql
└ frontend
prod
└ vpc
└ mysql
└ frontend
modules
└ vpc
└ mysql
└ frontend
Define reusable modules!
80. stage
└ vpc
└ mysql
└ frontend
prod
└ vpc
└ mysql
└ frontend
modules
└ vpc
└ mysql
└ frontend
└ main.tf
└ outputs.tf
└ vars.tf
Each module defines one reusable
component
81. variable "name" {
description = "The name of the EC2 instance"
}
variable "ami" {
description = "The AMI to run on the EC2 instance"
}
variable "memory" {
description = "The amount of memory to allocate"
}
Define inputs in vars.tf to
configure the module
82. module "frontend" {
source = "./modules/frontend"
name = "frontend-stage"
ami = "ami-123asd1"
memory = 512
}
Use the module in stage
(stage/frontend/main.tf)
83. module "frontend" {
source = "./modules/frontend"
name = "frontend-prod"
ami = "ami-123abcd"
memory = 2048
}
And in prod
(prod/frontend/main.tf)
85. stage
└ vpc
└ mysql
└ frontend
prod
└ vpc
└ mysql
└ frontend
modules
└ vpc
└ mysql
└ frontend
If stage and prod point to the
same folder, you lose isolation
86. stage
└ vpc
└ mysql
└ frontend
prod
└ vpc
└ mysql
└ frontend
modules
└ vpc
└ mysql
└ frontend
Any change in modules/frontend
affects both stage and prod
87. infrastructure-live
└ stage
└ vpc
└ mysql
└ frontend
└ prod
└ vpc
└ mysql
└ frontend
infrastructure-modules
└ vpc
└ mysql
└ frontend
Solution: define modules in a
separate repository
88. infrastructure-live
└ stage
└ vpc
└ mysql
└ frontend
└ prod
└ vpc
└ mysql
└ frontend
infrastructure-modules
└ vpc
└ mysql
└ frontend
Now stage and prod can use
different versioned URLs
0.1
0.2
89. module "frontend" {
source =
"git::git@github.com:foo/infrastructure-
modules.git//frontend?ref=0.2"
name = "frontend-prod"
ami = "ami-123abcd"
memory = 2048
}
Example Terraform code
(prod/frontend/main.tf)
101. resource "aws_instance" "example" {
count = 3
ami = "${var.ami}"
instance_type = "t2.micro"
tags { Name = "${var.name}-${count.index}" }
}
Create three EC2 Instances, each
with a different name
102. Do even more with interpolation
functions:
terraform.io/docs/configuration/interpolation.html
103. resource "aws_instance" "example" {
count = 3
ami = "${element(var.amis, count.index)}"
instance_type = "t2.micro"
tags { Name = "${var.name}-${count.index}" }
}
variable "amis" {
type = "list"
default = ["ami-abc123", "ami-abc456", "ami-abc789"]
}
Create three EC2 Instances, each
with a different AMI
104. output "all_instance_ids" {
value = ["${aws_instance.example.*.id}"]
}
output "first_instance_id" {
value = "${aws_instance.example.0.id}"
}
Note: resources with count are
actually lists of resources!
107. But you can do a limited form of
if-statement using count
108. resource "aws_instance" "example" {
count = "${var.should_create_instance}"
ami = "ami-abcd1234"
instance_type = "t2.micro"
tags { Name = "${var.name}" }
}
variable "should_create_instance" {
default = true
}
Note the use of a boolean in the
count parameter
116. Valid plan to create IAM instance
profiles
> terraform plan
+ aws_iam_instance_profile.instance_profile
arn: "<computed>"
create_date: "<computed>"
name: "stage-iam-nat-role"
path: "/"
roles.2760019627: "stage-iam-nat-role"
unique_id: "<computed>”
Plan: 1 to add, 0 to change, 0 to destroy.
118. You get an error
> terraform apply
Error applying plan:
* Error creating IAM role stage-iam-nat-role:
EntityAlreadyExists: Role with name stage-iam-nat-role already
exists
status code: 409, requestId: [e6812c4c-6fac-495c-be9d]
123. > terraform apply
...
* aws_route.internet-gateway:
error finding matching route for Route table (rtb-5ca64f3b)
and destination CIDR block (0.0.0.0/0)
124. > terraform apply
...
* Resource 'aws_eip.nat' does not have attribute 'id' for
variable 'aws_eip.nat.id'
125. > terraform apply
...
* aws_subnet.private-persistence.2: InvalidSubnetID.NotFound:
The subnet ID 'subnet-xxxxxxx' does not exist
126. > terraform apply
...
* aws_route_table.private-persistence.2:
InvalidRouteTableID.NotFound: The routeTable ID 'rtb-2d0d2f4a'
does not exist
127. > terraform apply
...
* aws_iam_instance_profile.instance_profile: diffs didn't
match during apply. This is a bug with Terraform and should be
reported.
* aws_security_group.asg_security_group_stg: diffs didn't
match during apply. This is a bug with Terraform and should be
reported.
The most generic one: diffs didn’t
match during apply
128. Most of these are harmless. Just
re-run terraform apply.
129. And try to run Terraform close to
your AWS region (replica lag)
146. Advantages of Terraform:
1. Define infrastructure-as-code
2. Concise, readable syntax
3. Reuse: inputs, outputs, modules
4. Plan command!
5. Cloud agnostic
6. Very active development
147. Disadvantages of Terraform:
1. Maturity. You will hit bugs.
2. Collaboration on Terraform state is
tricky (but not with terragrunt)
3. No rollback
4. Poor secrets management
148. Questions?
Want to know when we share additional DevOps training?
Sign up for our Newsletter.
gruntwork.io/newsletter