TIAD : Full stack automation

•

2 likes•1,412 views

Today, the reactivity of the IT department and time to market become major objectives for businesses. Achieving these goals requires mechanically the enforcement of the quality of the delivered products: without this, acceleration would mean multiplication of incidents. Quality will also bring serenity for everybody. Leveraging on our own achievements for major CAC40 businesses, we will explain you how automation of the whole delivery chain - along with other practices - will contribute to improve the Information System.

Clément Cunin
Adrien Blind
19 mars 2015 . #TIAD . @tiadparis
Full Stack Automation
@ tiadparis - @adrienblind - @clcunin

Who are we?
Clément Cunin
Developer Java & agilifier
@clcunin
clement.cunin@free.fr
Adrien Blind
DevOps coach
@adrienblind
adrien@blind-net.fr
one one

Why ?
@ tiadparis - @adrienblind - @clcunin
#TIAD

Time to Market
@ tiadparis - @adrienblind - @clcunin
#TIAD

Repeatability
@ tiadparis - @adrienblind - @clcunin
#TIAD

Serenity
@ tiadparis - @adrienblind - @clcunin
#TIAD

How ?
@ tiadparis - @adrienblind - @clcunin
#TIAD

Throughput :
~ One release / day
@ tiadparis - @adrienblind - @clcunin
#TIAD
Delay :
~ 15 min (from commit to production)

@ tiadparis - @adrienblind - @clcunin
#TIAD
“You build it,
You run it”
-- Werner Vogels (Amazon)

New Paradigm
Logiciel
@ tiadparis - @adrienblind - @clcunin
#TIAD

Automate is a part of service
@ tiadparis - @adrienblind - @clcunin
#TIAD

Pizza team
@ tiadparis - @adrienblind - @clcunin
#TIAD

New release-notes process
@ tiadparis - @adrienblind - @clcunin
#TIAD

Rethink your process
@ tiadparis - @adrienblind - @clcunin
#TIAD

One version to run them all
@ tiadparis - @adrienblind - @clcunin
#TIAD

Version number - Build number
@ tiadparis - @adrienblind - @clcunin
#TIAD

Remove maintenance branches
@ tiadparis - @adrienblind - @clcunin
#TIAD

The easiest way
@ tiadparis - @adrienblind - @clcunin
#TIAD

Automatisation des déploiements
Extend the pipeline
@ tiadparis - @adrienblind - @clcunin
#TIAD

package {‘tiad’:
ensure => present,
}
service {‘tiad’:
ensure => running,
}
@ tiadparis - @adrienblind - @clcunin
#TIAD
Infra as Code

@ tiadparis - @adrienblind - @clcunin
#TIAD
Ephemeral environments

@ tiadparis - @adrienblind - @clcunin
#TIAD
Deliver the whole service

Reproduce again and again
@ tiadparis - @adrienblind - @clcunin
#TIAD

@ tiadparis - @adrienblind - @clcunin
#TIAD
Measure everything

Non-event release
@ tiadparis - @adrienblind - @clcunin
#TIAD

• Interesting trends
• Resilience &
scalability within
the application
@ tiadparis - @adrienblind - @clcunin
#TIAD
Redesign your app.
Delivery
frequency
Infrastructure
commodity
trafic, data,
compute

@ tiadparis - @adrienblind - @clcunin
#TIAD
Scale up!

Russian dolls
@ tiadparis - @adrienblind - @clcunin
#TIAD
DevOps (pizza) teams to build &
operate applicative services
DevOps (pizza) teams to build &
operate infrastructure services

@ tiadparis - @adrienblind - @clcunin
#TIAD
Doggy bag

@ tiadparis - @adrienblind - @clcunin
#TIAD
Get an holistic view

@ tiadparis - @adrienblind - @clcunin
#TIAD
Don’t forget your guys

1 224 km/h
@ tiadparis - @adrienblind - @clcunin
#TIAD

@ tiadparis - @adrienblind - @clcunin
#TIAD

At a previous JAX event I talked about effective cloud native Java developer workflow. Two years later and many new developer technologies have come and gone, but I still hear daily from cloud developers about the pain and friction associated with building, debugging, and deploying to the cloud. In this talk I’ll share my latest learning on how to bring the fun and productivity back into delivering Kubernetes-based software. Join this talk to: Learn why the core tenets of continuous delivery — speed and safety — must be considered in all parts of the cloud native SDLC Explore how cloud native coding benefits from thinking separately about the inner development loop, continuous integration, continuous deployment, observability, and analysis Understand how cloud native best practices and tooling fit together. Learn about artifact syncing (e.g. Skaffold), dev environment bridging (e.g. Telepresence), GitOps (e.g. Argo), and observability-focused monitoring (e.g. Prometheus, Jaeger) Explore the importance of cultivating an effective cloud platform and associated team of experts Walk away with an overview of tools that can help you develop and debug effectively when using Kubernetes

Principles of microservices velocity

Sam Newman

Microservices are small services with independent lifecycles that work together. There is an underlying tension in that definition – how independent can you be when you have to be part of a whole? I’ve spent much of the last couple of years trying to understand how to find the right balance, and in this talk/tutorial I’ll be presenting the core seven principles that I think represent what makes microservices tick. After a brief introduction of what microservices are and why they are important, we’ll spend the bulk of the time looking at the principles themselves, wherever possible covering real-world examples and technology: - Modelled around business domain – using techniques from domain-driven design to find service boundaries leads to better team alignment and more stable service boundaries, avoiding expensive cross-service changes. - Culture of automation – all organisations that use microservices at scale have strong cultures of automation. We’ll look at some of their stories and think about which sort of automation is key. - Hide implementation details – how do you hide the detail inside each service to avoid coupling, and ensure each service retains its autonomous nature? - Decentralize all the things! – we have to push power down as far as we can, and this goes for both the system and organisational architecture. We’ll look at everything from autonomous self-contained teams and internal open source, to using choreographed systems to handle long-lived business transactions. - Deploy independently – this is all about being able to deploy safely. So we’ll cover everything from deployment models to consumer-driven contracts and the importance of separating deployment from release. - Isolate failure – just making a system distributed doesn’t make it more stable than a monolithic application. So what do you need to look for? - Highly observable – we need to understand the health of a single service, but also the whole ecosystem. How? In terms of learning outcomes, beginners will get a sense of what microservices are and what makes them different, whereas more experienced practitioners will get insight and practical advice into how to implement them.

How to Implement Hybrid Cloud Solutions Successfully

SoftServe

The FaaS and the Furious

David Schmitz

Serverless Computing ist der nächste logische Schritt, um Anwendungen in die Cloud zu bringen. Im Kern von Amazons Serverless Computing Angebots liegt AWS Lambda. AWS Lambda ist unter anderem durch den Sprachassistenten Alexa populär geworden, wird aber in unterschiedlichen Bereichen für innovative Produkte verwendet. Dieser Vortrag stellt Serverless Computing anhand eines Amazon Alexa Skills vor, der das Konferenzprogramm der Devcon 2017 als Sprachassistent anbietet. Wir schauen im Rahmen des Beispiels auf die architekturellen und infrastrukturellen Herausforderungen diese Event-Driven Ansatzes und lernen, wo Serverless Computing sinnvoll ist und wo andere Ansätze besser geeignet sein können. Schliesslich werfen wir noch einen kurzen Blick auf Alternativen zu AWS Lambda und bewerten die Vor- und Nachteile.

Hundreds of projects, thousands of jobs, each generating data about the status, commit, change logs and quality reports of your projects. How can you restore order in this amount of data and use it to gather useful information about your projects? > In this talk, I will explain how I collect the data over thousands of jobs, commit after commit, build after build, how he stored it and used it in turn to extract useful information and to inject this data as feedback into our pipelines.

Continuous Integration & Development with Gitlab

Ayush Sharma

Secure Architecture and Programming 101

Mario-Leander Reimer

Security still is an underrated non-functional requirement in software engineering, often neglected or even forgotten during the construction and implementation of software systems. If things go wrong the reputation and business of your customers as well as yours might be at stake. Retrofitting security is laborious and expensive, it needs to be considered from day. Sounds hard? Not at all. This presentation will show that writing secure code and constructing secure systems is not as hard as it may sound. First, we will briefly dissect some well-known security vulnerabilities which were the result of only minor programming errors and we will demonstrate how easy insecurely written Java code can be exploited. However, writing secure code from day one is just as easy. For this we will present a handful of basic rules and tools every secure developer must know. This session will discuss the secure usage of open source software components in enterprise applications and describe patterns to securely incorporate these libraries. The session will further present basic patterns to construct secure components and system architectures. This presentation has been presented at the O'Reilly Software Architecture Conference in London 2016. #OReillySACon

CI/CD As first and last line of defence

Jimmy Dahlqvist

CI/CD (continuous integration/continuous delivery) aims to automate software delivery through repeatable processes. It acts as both the first and last line of defense by integrating automated testing into development workflows and deploying to production only when tests pass. The document outlines how CI/CD enables pull request testing, merge testing, nightly testing, blue/green deployments, canary releases, and chaos engineering to catch issues early and validate changes before production.

Real world serverless - architecture, patterns and lessons learned

David Schmitz

Serverless computing is quite the rage today. It enables companies to move to a platform with basically limitless capacity and it allows teams to embrace DevOps right from the start. So, this is literally the silver bullet we have waited for and everybody should embrace it. Right? Well, it depends… In this talk we will look at different scenarios and approaches to building and designing complex Serverless applications on AWS beyond your basic “Hello World”. We will cover architectures and patterns that help in adopting Serverless, for example how to design your Serverless landscape without getting lost in event-driven-chaos. Covering the whole development process, we will look at real world problems like testing, debugging, monitoring and securing your Serverless applications. Furthermore, we will use some of the essential tools that make working with AWS Lambda easier, such using Claudia.JS. Finally, we will discuss the drawbacks and misconceptions, like potential vendor lock-in and the illusion of NoOps. If you find Serverless computing interesting, then this talk will show you how to adapt this architectural style without getting burned too much.

Rundeck Overview

Rundeck

Rundeck is an open source automation platform that allows users to define, schedule, and execute jobs across multiple servers to automate system administration tasks. It was started in 2010 and has over 100 contributors. Rundeck provides a web interface, API, and CLI to define workflows and orchestrate tasks. It supports plugins for popular DevOps tools and can integrate with other systems like ITSM tools. Rundeck Enterprise provides additional features like high availability, security controls, and support.

GitLab Commit DevOps: How GitLab Can Save your Kubernetes environment from Be...

Nico Meisenzahl

Cloud native environments are a double edged sword - used right, the benefits are immense. However, it also introduces multiple entry points for example security breaches. In this session, Nico will show how application vulnerabilities make it easy to hijack a Kubernetes cluster. He will also talk about why it's important to implement zero-trust to prevent data leaks and malicious workloads from being executed on a hijacked cluster. In addition, you will learn how GitLab can protect you from being hijacked. Nico will talk about how to create more secure applications by using Static Application Security Testing (SAST) as well as how to secure your Kubernetes cluster with Container Host Security, Container Network Security or a Web Application Firewall.

The IDI Digital Transformation - OpenStack Day Israel 2016

Cloud Native Day Tel Aviv

Deployment Automation & Self-Healing with Dynatrace & Ansible

Jürgen Etzlstorfer

Bianca Henderson from Ansible and Jürgen Etzlstorfer from Dynatrace discuss how to automate deployments of the Dynatrace OneAgent using Ansible and enable self-healing applications. They demonstrate how to deploy Dynatrace agents to over 1,300 servers in just a few minutes using Ansible. They also show how Dynatrace can detect issues automatically, perform root cause analysis, send problem notifications to Ansible Tower to trigger playbooks that remediate issues. This enables fully automated self-healing of applications through the integration of Dynatrace and Ansible.

GitLab Commit: Enhance your Compliance with Policy-Based CI/CD

Nico Meisenzahl

Whether you want to get started with Governance or improve your current process, this talk will show you how to improve your compliance by implementing policy-based CI/CD (Continuous Integration / Continuous Delivery) with GitLab CI and Open Policy Agent. Philippe and Nico will tell you all the details about Open Policy Agent and how you can easily integrate it into your existing CI/CD pipelines. Join our session to learn how to improve compliance, from gating your dependencies to controlling your infrastructure.

Microservice no fluff, the REAL stuff

nklmish

Continuous Lifecycle: Enhance Your Compliance and Governance With Policy-Base...

Nico Meisenzahl

This document discusses using Open Policy Agent (OPA) to enhance compliance and governance in CI/CD pipelines. It introduces OPA as a general-purpose policy engine that uses a declarative policy language to decouple application logic from policy decisions. The document explains how OPA works, including its Rego policy language and built-in functions. It provides examples of using OPA for tasks like validating Kubernetes manifests and Terraform configuration changes.

Nir Doboviski: In Space No One Can Hear Microservices Scream – a Microservice...

CodeValue

Everything-as-code. Polyglotte Software-Entwicklung in der Praxis.

QAware GmbH

OOP 2017, München: Vortrag von Mario-Leander Reimer (@LeanderReimer, Cheftechnologe bei QAware). Abstract: Als zeitgemäßer Entwickler muss man eine Vielzahl an Sprachen sicher beherrschen. Wir definieren unsere Entwicklungsumgebung mit Gradle, wir bauen unsere Software in Java, Kotlin oder sogar JavaScript. Wir verwenden Groovy und Scala, um unsere Software zu testen. Die Build-Pipeline wird per DSL und JSON definiert. Mit YAML und Python beschreiben wir die Infrastruktur und das Deployment unserer Anwendungen. Die Dokumentation unserer Architekturen erledigen wir mit AsciiDoc und JRuby. Willkommen in Babel! Hallo Software-Industrialisierung! Use the right tool for the job! Das ist das Motto dieser Session. Jede Sprache hat Stärken in einer bestimmten Domäne. Diese Stärken gilt es zu nutzen. Aber einfach blind jede gerade angesagte Sprache einzusetzen, ist sicher nicht die Lösung. Genau das versuchen wir mit dieser Session zu vermitteln. Stattdessen braucht es eine gut integrierte und abgestimmte Tool-Chain. Wir berichten aus der Praxis: what worked for us and what did not.

The art of decomposing monoliths - Kfir Bloch - Codemotion Amsterdam 2016

Codemotion

Microservices are the new black. You've heard about them, you've read about them, you may have even implemented a few, but sooner or later you'll run into the age-old conundrum: How do I break my monolith apart? Where do I draw service boundaries? In this talk you will learn several widely-applicable strategies for decomposing your monolithic application, along with their respective risks and the appropriate mitigation strategies. These techniques are widely used at Wix, took us a long time to develop and have proven consistently effective; hopefully they will help you avoid the same battle

Easy Microservices with JHipster - Devoxx BE 2017

Deepu K Sasidharan

Cómo construir un pipeline de entrega continua

Software Guru

Esta charla comentaremos un par de casos de prácticos en la implementación de CD en aplicaciones múltiples incluyendo, web, clientes móviles y creación de servicios, resaltaremos los elementos tecnológicos que se pueden ocupar en cada caso, y la creación de elementos que orquestan líneas de producción completas para un producto de software. Sesión presentada por Juan Reyes en SG Next 2017

Securing your Cloud Environment v2

ShapeBlue

Harnessing Domain Driven Design

Capgemini

Gayathri Thiyagarajan Lead Software Engineer - Capgemini Andrew Harmel-Law Principal Software Engineer - Capgemini Eric Evans’ Domain Driven Design (DDD) is a core text for all developers, and it's experiencing a renaissance due to the rise of microservices. But are most of us really applying DDD when we're "doing" distributed systems development? Gayathri and Andrew are going to argue that we're not, but we should be – we need to recalibrate. We'll begin by laying out what DDD means to us based on experiences we've had building microservices with distributed teams over the last two years. We'll touch lightly on the well-understood elements such as "ubiquitous language", "intention revealing interfaces" and "hands on architects", before clarifying and explaining the much misapplied concept of "bounded contexts". Finally we'll draw up in front of the largely ignored ones, such as the many patterns for inter-team communication which derive from "context maps". As we move away from the well-understood to the disregarded, we'll illustrate why these later ones are by far the most important to successful microservice-based projects. We'll explain why they matter, and the bene ts you'll see from applying them. You will leave ready to apply the full power of DDD, and you'll have more fun as you do it.

Seamlessly Detect and React to IT-Service Related Problems

Dynatrace

What's hot

Journey to the cloud, the why and how of serverless

Yan Cui

Scaling micro services at gilt

Adrian Trenaman

Collibra wrojug-ontrack-20100424

Damien Coraboeuf

Continuous Integration & Development with Gitlab

Ayush Sharma

Secure Architecture and Programming 101

Mario-Leander Reimer

CI/CD As first and last line of defence

Jimmy Dahlqvist

Real world serverless - architecture, patterns and lessons learned

David Schmitz

Rundeck Overview

Rundeck

GitLab Commit DevOps: How GitLab Can Save your Kubernetes environment from Be...

Nico Meisenzahl

The IDI Digital Transformation - OpenStack Day Israel 2016

Cloud Native Day Tel Aviv

Deployment Automation & Self-Healing with Dynatrace & Ansible

Jürgen Etzlstorfer

GitLab Commit: Enhance your Compliance with Policy-Based CI/CD

Nico Meisenzahl

Microservice no fluff, the REAL stuff

nklmish

Continuous Lifecycle: Enhance Your Compliance and Governance With Policy-Base...

Nico Meisenzahl

Nir Doboviski: In Space No One Can Hear Microservices Scream – a Microservice...

CodeValue

Everything-as-code. Polyglotte Software-Entwicklung in der Praxis.

QAware GmbH

The art of decomposing monoliths - Kfir Bloch - Codemotion Amsterdam 2016

Codemotion

Easy Microservices with JHipster - Devoxx BE 2017

Deepu K Sasidharan

Cómo construir un pipeline de entrega continua

Software Guru

Securing your Cloud Environment v2

ShapeBlue

What's hot (20)

Journey to the cloud, the why and how of serverless

Scaling micro services at gilt

Collibra wrojug-ontrack-20100424

Continuous Integration & Development with Gitlab

Secure Architecture and Programming 101

CI/CD As first and last line of defence

Real world serverless - architecture, patterns and lessons learned

Rundeck Overview

GitLab Commit DevOps: How GitLab Can Save your Kubernetes environment from Be...

The IDI Digital Transformation - OpenStack Day Israel 2016

Deployment Automation & Self-Healing with Dynatrace & Ansible

GitLab Commit: Enhance your Compliance with Policy-Based CI/CD

Microservice no fluff, the REAL stuff

Continuous Lifecycle: Enhance Your Compliance and Governance With Policy-Base...

Nir Doboviski: In Space No One Can Hear Microservices Scream – a Microservice...

Everything-as-code. Polyglotte Software-Entwicklung in der Praxis.

The art of decomposing monoliths - Kfir Bloch - Codemotion Amsterdam 2016

Easy Microservices with JHipster - Devoxx BE 2017

Cómo construir un pipeline de entrega continua

Securing your Cloud Environment v2

Similar to TIAD : Full stack automation

Harnessing Domain Driven Design

Capgemini

Seamlessly Detect and React to IT-Service Related Problems

Dynatrace

Principles of Microservices - NDC 2014

Sam Newman

Serverless Security Workflows - cyber talks - 19th nov 2019

Dinis Cruz

The document discusses how serverless technologies can help security teams scale their operations through automated workflows. It advocates that security teams adopt serverless approaches to build workflows that are event-driven and leverage services like AWS Lambda, Azure Functions, and Google Cloud Functions. By taking a serverless approach, security activities like incident response, threat modeling, and risk analysis can be automated and scaled more easily. The document also discusses using technologies like Jira, Slack, property graphs and Jupyter notebooks to capture security data and build automated workflows and dashboards.

D6: Cloud Directions ( Predix Transform 2016)

Predix

[BreizhCamp, format 15min] Construire et automatiser l'ecosystème de son Saa...

François-Guillaume Ribreau

This document discusses building and automating an API ecosystem for a SaaS application using OpenAPI (Swagger) specifications. It describes using Swagger to generate API documentation, input validation, client libraries, and other components. The solution involves defining the API in a single Swagger specification file and using CI/CD pipelines to automatically generate documentation, tests, client libraries and other code artifacts from that file on each release.

TechTalk: Reduce Risk with Canary Deployments

CA Technologies

This document discusses canary deployments as a technique for reducing risk when introducing new code to production. It defines canary deployments as deploying new code to a small subset of servers first before fully deploying. Canary deployments allow testing the new code on real users before rolling out widely. CA Release Automation supports defining and executing canary deployments to help reliably deploy new functionality while mitigating risks of failures. The document provides examples of how Netflix and Etsy use canary deployments and demonstrates a typical canary deployment workflow supported by CA Release Automation.

apidays Paris 2022 - The Magic of Service Mesh, Charly Molter, Kong

apidays

apidays Paris 2022 - APIs the next 10 years: Software, Society, Sovereignty, Sustainability December 14, 15 & 16, 2022 The Magic of Service Mesh: Everything Your Sidecar Does for You Charly Molter, Engineering Manager at Kong ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/ Deep dive into the API industry with our reports: https://www.apidays.global/industry-reports/ Subscribe to our global newsletter: https://apidays.typeform.com/to/i1MPEW

Osm

Gilard Application Programmers

This document describes how Gilard Electronics Pvt. Ltd., an Indian electronics manufacturer, infused modern technology like digitization and IoT to improve competitiveness. It details how Gilard implemented an ERP system in 1987 to digitize operations like production planning and inventory control. In 2015, Gilard upgraded to newer ERP technologies and added IoT sensors to digitally monitor and control manufacturing processes. Now Gilard's entire operations from new product development to sales and finance are digitized and integrated on a central database for real-time access and decision making. The digitization helps Gilard improve quality, productivity, efficiency and reduce costs to better compete in a challenging market.

CDRTool: CDR mediation and rating engine for OpenSIPS

Saúl Ibarra Corretgé

Goto Chicago; Journeys To Cloud Native Architecture: Sun, Sea And Emergencies...

OpenCredo

This document discusses journeys to cloud native architectures and provides principles for success. It begins with an overview of the cloud native dream from a business perspective, aiming for faster time to market and scalability. However, common issues that can arise include tackling too much too quickly, relying on a surface-level understanding, using ineffective tools and processes, and not anticipating failure. The document concludes with principles for a successful cloud native journey: don't take on too much too quickly, acquire sufficient expertise, choose tools wisely, engage security, and plan for failure through active testing of sad paths.

The Security Capabilities of Everything IP

Andreas Taudte

The document discusses IP address management (IPAM) and how it involves managing IP addresses, host names, DNS, and DHCP. It notes the challenges of legacy tools in addressing modern mobility and cloud computing trends. IPAM provides automation, auditing, visibility, consistency checks, and support for IPv6 to simplify requests and administration across networks, DHCP, and asset systems. The discussion focuses on how BlueCat provides a centralized IPAM platform to manage over 25 million IP addresses with high performance and scalability.

TIAD 2016 : Continuous Integration mesured and controlled

TIAD : Full stack automation

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to TIAD : Full stack automation

Similar to TIAD : Full stack automation (20)

More from The Incredible Automation Day

More from The Incredible Automation Day (20)

Recently uploaded

Recently uploaded (20)

TIAD : Full stack automation