Database deployments - dotnetsheff

Database deployments - dotnetsheff 2 March 2021 https://www.meetup.com/dotnetsheff/events/273184959/

Software

Database deployments
Giulio Vian — 3 March 2021

In a Start-up far far away
DBA
Senior
Dev
Scrum
Master
Junior
Dev

Free!
too good to be true
• 0 $/£/€ = gratis!
• open source
• any DB!
• 1,400 stars
• and works!

Months
pass
It’s Friday:
Let’s deploy the
latest version!

Migration-based
Source: https://www.red-gate.com/hub/product-learning/sql-source-control/moving-from-application-automation-to-true-devops-by-including-the-database

State-based
Source: https://www.red-gate.com/hub/product-learning/sql-source-control/moving-from-application-automation-to-true-devops-by-including-the-database

Diff script from schema-based tool
uh oh

Migration based
v1  v2
Hides conflicts
Order matters
State based
v1  v2
Miss object renames
Rollback drifts
Schema evolution

Migration based
v1  v2
State based
v1  v2
What to use

Are the two mutually exclusive?
No
Dev can use a Schema diff tool like SSDT to draft
migration scripts
Migration script can be augmented stating the baseline
version
State-based tools have pre- and post-deploy phases for
data migration
We can add dependency check between migration
scripts
To warn about scripts interaction and dependency

Hardware spec:
1 KB RAM
(16KB after upgrade)
4 KB ROM
(8KB after upgrade)
First computer Past Companies Communities
Giulio Vian Senior DevOps Engineer
@giulio_vian
giuliovdev@hotmail.com

References
Tools
SQL Server Data Tools (SSDT)
RedGate SQL Compare
devart
Flyway
dbup
dbdeploy.net
Articles
https://en.wikipedia.org/wiki/Sc
hema_migration
https://martinfowler.com/article
s/evodb.html
https://michaeljswart.com/2018
/01/100-online-deployments
http://blog.dixo.net/2015/02/bl
ue-turquoise-green-deployment
Books
Refactoring Databases:
Evolutionary Database Design
http://www.agiledata.org/

Thank you!
Giulio Vian
@giulio_vian
giuliovdev@hotmail.com

Database Refactoring Cycle
Initial state Final state
Implement the refactoring
Test on non-production
Refactoring completed
deploy new schema,
migrate data
deploy new application version

Database Refactoring Cycle
Initial state Final state
Transitional state
Implement the refactoring
Test on non-production
Refactoring completed
All systems use the new schema
Coexistence of
old and new schema
Expand:
deploy new schema,
migrate data,
add scaffolding code
Contract:
Drop old schema objects
and scaffolding code

La morale
Tools are
limited
Know your
stuff is the
only way
Discipline

Migration troubles
with DbUp
also FlyWay, Liquibase, etc.

This document is a summary of a webinar about infrastructure as code. It introduces the speaker, Srirajan, and discusses how automation tools like Chef, Puppet, Ansible and others can be used to define infrastructure in code. Key benefits of infrastructure as code include automation, repeatability, and disaster recovery. The webinar also discusses testing infrastructure code and version controlling code changes.

Azure dev ops integrations with Jenkins

Damien Caro

The document discusses various ways to integrate Jenkins with Azure services. It describes the Azure Storage, Slave, and Container Service plugins that help with continuous integration and deployment workflows. It also mentions that the Azure Slave v2 plugin, Azure Container Service plugin, and Azure DevOps integrations portal will soon be available in public preview, while an Azure Jenkins image is already in the Azure Marketplace. NASA's JPL uses Jenkins with Azure services like storage and virtual machines for continuous integration of their Mars terrain pipeline code.

Ed Elliott - Practical DSC in Azure

Powershell DSC is the future of configuration management on Windows but it can be very frustrating when it fails, especially in Azure. In this session we will explore how to deploy configurations to windows servers using Azure Automation and DSC. We will go over the concepts involved and have a walk through of getting a DSC configuration to apply to a set of virtual machines. We will take a demo configuration with multiple dependencies and deploy that to a Windows Virtual Machine in Azure – we will examine what happens at each step and show you how to troubleshoot it if and when your deployment fails.

Webinar: Continuous Deployment with MongoDB at Kitchensurfing

MongoDB

Continuous Deployment is gaining popularity with companies like Facebook and Etsy, but its successful implementation creates technical challenges and will require any team to make workflow changes. Learn how Kitchensurfing switched to continuous deployments and how they’ve grown from one deploy a week to 10+ deploys a day with zero downtime and zero worries, thanks to MongoDB. Hear about their workflow, the tools they use, and how they manage communication with product owners to make sure everyone is always in the loop.

Infrastructure as Code

Robert Greiner

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.

Continuous Integration and Deployment Best Practices on AWS

With AWS, organizations now have the ability to develop and run their applications with speed and flexibility like never before. Working with an infrastructure that can be 100% API-driven enables organizations to use lean methodologies and realize these benefits. In this session, we will explore some key concepts and design patterns for continuous deployment and continuous integration, two elements of lean application and infrastructure development. We will look at several use cases where IT organizations leveraged AWS to rapidly develop and iterate on applications for scale, high availability and cost optimization. Speaker: Adrian White, Solutions Architect, Amazon Web Services

WinOps Conf 2016 - Michael Greene - Release Pipelines

There are benefits to be gained when patterns and practices from developer techniques are applied to operations. Notably, a fully automated solution where infrastructure is managed as code and all changes are automatically validated before reaching production. This is a process shift that is recognized among industry innovators. For organizations already leveraging these processes, it should be clear how to leverage Microsoft platforms. For organizations that are new to the topic, it should be clear how to bring this process to your environment and what it means to your organizational culture. This presentation explains the components of a Release Pipeline for configuration as code, the value to operations, and solutions that are used when designing a new Release Pipeline architecture.

Contract-based Testing Approach as a Tool for Shift Lef

Katherine Golovinova

The document discusses contract based testing and shifting testing left. It describes testing at different levels, including UI, integration, and unit testing. It outlines how to implement contract testing between a consumer and provider by creating pacts, publishing them to a broker, and having the provider verify against the pacts. Benefits include apps working together continuously, avoiding duplicative work, and visibility into dependencies. The presentation encourages attendees to try out contract testing.

The goal of every developer is get her super cool new feature out to customers, as fast as possible, with little to no bugs and with no manual effort so she can go back to coding the next awesome one. Doing all of this takes tremendous amounts of effort to plan, coordinate and execute on a DevOps engineer. Continuous Integration coupled with Continuous Deployment aide in this endeavor. But again, those are cumbersome and can be difficult to set up. AWS has four new tools to help with this; AWS CodeDeploy, CodeCommit, CodePipeline, and CodeBuild. Each one has specialized features to help get your code to customers faster, more reliable and bug free as possible. In this presentation, we will walk through how to setup a CI/CD pipeline using those AWS tools and demonstrate how we can go from yay it compiles to a 5-star review.

WinOps Conf 2016 - Jeffrey Snover - The DevOpsification of Windows Server

MS Insights Brazil 2015 containers and devops

Damien Caro

AWS Webcast - Build Agile Applications in AWS Cloud for Government

Introduction to Infrastructure as Code & Automation / Introduction to Chef

All Things Open

Serverless

Vishwas N

This document discusses serverless computing and compares it to traditional server-based computing. Some key points: - Serverless allows for inherent scalability, cost savings since customers only pay for resources used, and lower latency since code can execute near users. However, testing/debugging is more difficult and vendor lock-in is a risk. - Serverless is compared to IaaS/PaaS/SaaS models, with serverless being akin to "buying a plane ticket and flying" rather than owning/renting infrastructure. - Popular serverless options like Python and JavaScript Azure Functions are discussed, along with benefits like auto-completion, independent IDE usage, and ease of cloud integration and deployment.

CI/CD on AWS Deploy Everything All the Time

Why does DevOps matter? How can you use continuous integration to build your product faster, make it more highly available, and be able to recover from bugs quickly? Let one of our solutions architects walk you through continuous integration and continuous delivery on AWS. This session includes live demos of our tools AWS CodeCommit, AWS CodePipeline, and AWS CodeDeploy. Speaker: Leo Zhandovsky, Solutions Architect, Amazon Web services recordings to the Canberra Summit can be found here https://aws.amazon.com/events/anz/on-demand/canberra-summit/

WinOps Conf 2016 - Ed Wilson - Configuration Management with Azure DSC

Configuration management at scale, even with PowerShell and PowerShell DSC, can quickly become complicated, error-prone, and unruly. The new Desired State Configuration (DSC) feature of Azure Automation, in the Microsoft’s Operations Management Suite, provides a solution - a central, secure location for all your PowerShell DSC items and reports, that is scalable, reliable, and highly-available. Come learn how it can transform configuration management across your organization, using the PowerShell tools and knowledge you already have.

Infrastructure as Code (BBWorld/DevCon13)

Mike McGarr

AWS Webcast - Build Agile Applications in AWS Cloud for Government

Accelerating Innovation with DevOps on AWS

Much has been said about DevOps culture, this webinar talks about exactly what it means to exercise a DevOps methodology inside your organization and takes a more detailed look at Continuous Integration and Continuous Deployment – two of the elements of a successful DevOps framework. With AWS’s API driven infrastructure, running a lean platform becomes possible and the ability to treat ‘Infrastructure as Code’. Reasons to attend: Learn how to set up and experience the benefits of 'Continuous Integration' and 'Continuous Deployment' for your Development Environment. Learn about DevOps best practices and the agility that the AWS Cloud can bring your business. Learn how business have successfully implemented DevOps methodologies.

From VMs to Containers: Decompose and Migrate Old Legacy JavaEE Application

It is not a trivial task to decompose large monolithic enterprise applications and migrate them into multiple containers architecture without redesign. In this presentation, we dive deeply into the decomposition process and show the ways of making it smooth with the help of auto-scaling and load balancing. Find out the main road blockers and possible solutions during migration of GlassFish based applications from VMs to Containers based on the real experience.

CI/CD with Azure DevOps and Azure Databricks

GoDataDriven

This document describes a CI/CD pipeline for automating deployment of Python code and notebooks to Azure Databricks. The pipeline uses Pre-Commit hooks to run linters and tests on commits. If tests pass, a Python wheel is built and published to Azure DevOps artifacts. The pipeline then copies the version file to the development workspace and copies the full notebook folder to production, allowing installation of the specific library version in notebooks. The goal is continuous deployment with testing at each stage to reliably deploy small code changes.

Day 3 - DevOps Culture - Continuous Integration & Continuous Deployment on th...

This document discusses continuous integration (CI) and continuous deployment (CD) workflows on AWS. It provides examples of CI/CD pipelines and tools. It also demonstrates how to automate infrastructure deployment and management using AWS services like CloudFormation, containerization with Docker, and extending CI/CD tools to interact with AWS APIs. The document concludes with a discussion on how to implement best practices for innovation, quality and governance in CI/CD processes.

Connect + Docker + AWS = Bitbucket Pipelines

Atlassian

Nathan Burrell from Atlassian discusses how Connect, AWS, and Docker can be used together with Bitbucket Pipelines. Connect provides an integration point for third party services with Atlassian products. AWS is used to host and run microservices. Docker is utilized for containerization of services both locally during development and in production on AWS. The talk covers Connect descriptors, permissions, iFrames, and webhooks for integrating with Atlassian products, as well as how microservices are structured and interact with each other when run on AWS using services like DynamoDB, ECS, and SQS. Kubernetes is also mentioned for container management at scale. Security best practices when using Docker and Kubernetes in production are briefly discussed

Spinnaker Microsrvices

Ambassador Labs

Philip Lombardi discusses Datawire's experience using Spinnaker for continuous deployment of microservices. While Spinnaker allows for custom deployment workflows and works as promised, Datawire encountered issues with Spinnaker's complex UI, difficulty reconfiguring and upgrading, and slow developer experience. Lombardi concludes that Spinnaker may be overkill for small teams and its deployment, UI, and configuration need improvement for broader adoption.

Nginx conference 2015

ING-IT

NGINX was implemented to replace IBM WebSeal and F5 BigIP load balancers at ING Bank. The implementation involved: 1. Integrating NGINX into the continuous delivery pipeline for automated deployments. 2. Developing custom authentication, load balancing, and monitoring modules for NGINX to add missing functionality. 3. Gradually replacing IBM WebSeal and F5 BigIP devices with NGINX to gain more control over the load balancing infrastructure and simplify operations.

Network Infrastructure as Code with Chef and Cisco

Matt Ray

Chef is an open source framework for managing infrastructure as code. It uses a declarative language and recipes to describe and configure systems to match a desired state. Chef works by having clients pull policies from a server and apply them locally, then reporting the state back. Cisco and Chef are working together to bring official Chef support to Cisco's NX-OS and IOS-XR platforms through Omnibus packages and a Cisco cookbook with resources for managing Cisco devices. This will allow network infrastructures to be managed as code through testing, versioning, and continuous delivery practices.

56k.cloud training

Brian Christner

This document provides an overview of Docker and cloud native training presented by Brian Christner of 56K.Cloud. It includes an agenda for Docker labs, common IT struggles Docker can address, and 56K.Cloud's consulting and training services. It discusses concepts like containers, microservices, DevOps, infrastructure as code, and cloud migration. It also includes sections on Docker architecture, networking, volumes, logging, and monitoring tools. Case studies and examples are provided to demonstrate how Docker delivers speed, agility, and cost savings for application development.

Automated Scaling of Microservice Stacks for JavaEE Applications

Continuous Deployment: The Dirty Details

Mike Brittain

Getting started with agile database migrations for java flywaydb

Girish Bapat

What's hot

DevOps and AWS - Code PaLOUsa 2017

James Strong

WinOps Conf 2016 - Jeffrey Snover - The DevOpsification of Windows Server

MS Insights Brazil 2015 containers and devops

Damien Caro

AWS Webcast - Build Agile Applications in AWS Cloud for Government

Introduction to Infrastructure as Code & Automation / Introduction to Chef

All Things Open

Serverless

Vishwas N

CI/CD on AWS Deploy Everything All the Time

WinOps Conf 2016 - Ed Wilson - Configuration Management with Azure DSC

Infrastructure as Code (BBWorld/DevCon13)

Mike McGarr

AWS Webcast - Build Agile Applications in AWS Cloud for Government

Accelerating Innovation with DevOps on AWS

From VMs to Containers: Decompose and Migrate Old Legacy JavaEE Application

CI/CD with Azure DevOps and Azure Databricks

GoDataDriven

Day 3 - DevOps Culture - Continuous Integration & Continuous Deployment on th...

Connect + Docker + AWS = Bitbucket Pipelines

Atlassian

Spinnaker Microsrvices

Ambassador Labs

Nginx conference 2015

ING-IT

Network Infrastructure as Code with Chef and Cisco

Matt Ray

56k.cloud training

Brian Christner

Automated Scaling of Microservice Stacks for JavaEE Applications

What's hot (20)

DevOps and AWS - Code PaLOUsa 2017

WinOps Conf 2016 - Jeffrey Snover - The DevOpsification of Windows Server

MS Insights Brazil 2015 containers and devops

AWS Webcast - Build Agile Applications in AWS Cloud for Government

Introduction to Infrastructure as Code & Automation / Introduction to Chef

Serverless

CI/CD on AWS Deploy Everything All the Time

WinOps Conf 2016 - Ed Wilson - Configuration Management with Azure DSC

Infrastructure as Code (BBWorld/DevCon13)

AWS Webcast - Build Agile Applications in AWS Cloud for Government

Accelerating Innovation with DevOps on AWS

From VMs to Containers: Decompose and Migrate Old Legacy JavaEE Application

CI/CD with Azure DevOps and Azure Databricks

Day 3 - DevOps Culture - Continuous Integration & Continuous Deployment on th...

Connect + Docker + AWS = Bitbucket Pipelines

Spinnaker Microsrvices

Nginx conference 2015

Network Infrastructure as Code with Chef and Cisco

56k.cloud training

Automated Scaling of Microservice Stacks for JavaEE Applications

Similar to Database deployments - dotnetsheff

Continuous Deployment: The Dirty Details

Mike Brittain

Getting started with agile database migrations for java flywaydb

Girish Bapat

SQL Saturday San Diego

Kellyn Pot'Vin-Gorman

The document discusses using data virtualization and masking to optimize database migrations to the cloud. It notes that traditional copying of data is inefficient for large environments and can incur high data transfer costs in the cloud. Using data virtualization allows creating virtual copies of production databases that only require a small storage footprint. Masking sensitive data before migrating non-production databases ensures security while reducing costs. Overall, data virtualization and masking enable simpler, more secure, and cost-effective migrations to cloud environments.

Flyway (33rd Degree)

Axel Fontaine

This document introduces Flyway, an open source database migration framework for Java. It was created by Axel Fontaine, an independent consultant based in Munich, Germany. Flyway allows developers to automatically manage and version database changes in a simple and scalable way. It aims to improve cooperation between development and database administration teams through a shared understanding of database changes. The document outlines Flyway's key features and goals, provides code examples, and discusses how it can help with challenges like aligning development, test and production databases or migrating existing databases.

(ARC402) Deployment Automation: From Developers' Keyboards to End Users' Scre...

Some of the best businesses today are deploying their code dozens of times a day. How? By making heavy use of automation, smart tools, and repeatable patterns to get process out of the way and keep the workflow moving. Come to this session to learn how you can do this too, using services such as AWS OpsWorks, AWS CloudFormation, Amazon Simple Workflow Service, and other tools. We'll discuss a number of different deployment patterns, and what aspects you need to focus on when working toward deployment automation yourself.

Sql source control

AndyPickett

The document discusses best practices for putting databases under source control. It recommends (1) checking in database schemas, reference data, and migration scripts into source control for revision history and merge conflict resolution. It also recommends (2) implementing continuous integration and deployment pipelines to automate database builds and deployments from source control to target environments. Key tools mentioned include SQL Source Control from Redgate for source control and SQL Compare/Data Compare for schema and data synchronization.

OWASP WTE - Now in the Cloud!

Matt Tesauro

This document provides information about the OWASP Web Testing Environment (WTE) project and its leader Matt Tesauro. It discusses the history and goals of the WTE project, which provides a collection of web application security testing tools in an easy-to-use environment. It also outlines ideas for the future of the project, such as providing automated cloud-based instances of the WTE and aligning its tools with the OWASP Testing Guide.

Database deployment: still hard after all these years - Data Saturday #1

Migrating a modern spring web application to serverless

Jeroen Sterken

The presentation I presented with my collegue Wim, at Spring IO Barcelona 2019. https://2019.springio.net/sessions/migrating-a-modern-spring-web-application-to-serverless In this presentation we want to share how we transformed a typical spring realtime web into a serverless application and the challenges we encountered to make this a serverless application for easy scaling and resource optimization. We will share our experiences and give you tips and tricks on what we learned in the process, like: - Spring resource optimization - Server side rendering versus fat clients - Session management - Realtime UI updates in serverless environments - Connecting functions - Security - Portability between cloud providers - …

Database CI/CD Pipeline

muhammadhashir57

1. Traditional database development faces issues like lack of source control, tedious deployment scripts, and manual processes. 2. DevOps principles like continuous integration, static code analysis, and automation can help address these issues. Database changes can be tracked in source control and deployed automatically. 3. There are different approaches to database deployment like state-based using DACPAC files or migration-based using incremental scripts stored in source control. Tools like SSDT, ReadyRoll, and Flyway support these approaches.

PHP North-East - Automated Deployment

Michael Peacock

This document discusses building a simple automated deployment platform with PHP and Linux. It describes taking a website offline for manual upgrades, which is time-consuming and error-prone. The document then outlines techniques for automating the deployment process, including exporting code from version control, applying file permissions and configuration changes, backing up and patching databases, running unit tests, and using symlinks to swap environments. It emphasizes the need for rollback capabilities and managing multiple environments like staging and production. The goal is to provide techniques for small teams and startups to continuously and reliably deploy updates.

Automated Deployment

phpne

The Last Frontier- Virtualization, Hybrid Management and the Cloud

Kellyn Pot'Vin-Gorman

This document discusses virtualization, hybrid management, and cloud computing. It begins with an introduction to virtualization and discusses trends showing increasing adoption of public cloud infrastructure and platforms. The document then explores how companies are migrating applications and data to the cloud using various approaches like backups, data migration tools, and virtualization. It argues that data virtualization provides benefits over traditional migration methods by reducing costs, network usage, and storage requirements when moving workloads to the cloud.

Flyway: The agile database migration framework for Java

Axel Fontaine

MSDN - Converting an existing ASP.NET application to Windows Azure

Maarten Balliauw

Puppet Camp Melbourne Nov 2014 - A Build Engineering Team’s Journey of Infras...

Peter Leschev

Deploy, scale and manage your application with AWS Elastic Beanstal

Containerizing legacy applications

Andrew Kirkpatrick

The document discusses containerizing legacy applications that rely on dynamic file-based configurations and secrets. It begins by asking questions to gauge how many organizations have legacy applications and what challenges they pose. It then outlines steps to containerize a legacy application like MyBB without rewriting code, including running the application in a container, using templated static configuration files injected by an orchestrator, and updating configuration dynamically. The presentation aims to provide a practical approach for migrating difficult-to-maintain legacy applications to containers.

Practical SQL Azure: Moving into the cloud

Timothy Corey

This document provides an overview and demonstration of moving a database into Microsoft Azure SQL. It begins with an introduction and roadmap of topics to be covered, which include an overview of SQL Azure, migrating a local database to the cloud, and best practices. The presentation then demonstrates how to set up a SQL database in Azure, configure database settings, fix incompatibilities when migrating a database, package a database using BACPAC files, and directly deploy a database to Azure SQL. It concludes with a section on SQL Azure best practices related to data security, safety and availability.

Microservices and Friends

Yun Zhi Lin

Similar to Database deployments - dotnetsheff (20)

Continuous Deployment: The Dirty Details

Getting started with agile database migrations for java flywaydb

SQL Saturday San Diego

Flyway (33rd Degree)

(ARC402) Deployment Automation: From Developers' Keyboards to End Users' Scre...

Sql source control

OWASP WTE - Now in the Cloud!

Database deployment: still hard after all these years - Data Saturday #1

Migrating a modern spring web application to serverless

Database CI/CD Pipeline

PHP North-East - Automated Deployment

Automated Deployment

The Last Frontier- Virtualization, Hybrid Management and the Cloud

Flyway: The agile database migration framework for Java

MSDN - Converting an existing ASP.NET application to Windows Azure

Puppet Camp Melbourne Nov 2014 - A Build Engineering Team’s Journey of Infras...

Deploy, scale and manage your application with AWS Elastic Beanstal

Containerizing legacy applications

Practical SQL Azure: Moving into the cloud

Microservices and Friends

More from Giulio Vian

Come implementare la governance nella vostra piattaforma e lavorare felici se...

DevOps Conf 2024 - Roma - 10 mag 2024 https://devopsconf.dotnetdev.it Gli strumenti che usiamo per lo sviluppo e il rilascio sono essenziali per controllare i processi in uso e garantire che soddisfino requisiti aziendali, legali, e regolamentari. In questa sessione illustrerò come passare da norme (policies) astratte a implementationi su piattaforme come Azure DevOps o GitHub delle stesse così da poter prevenire prima e verificare poi il corretto svolgimento delle operazioni. E diventare amici del direttore Rischi e Audit.

Is Technical Debt the right metaphor for Continuous Update?

Is Technical Debt the right metaphor for Continuous Update - AllDayDevOps 2022

The environmental pressure on software has dramatically changed in a few years, both in quality and quantity. Security is the main force but other dynamics can be seen, including the adoption of agile, shortest product cycles, and more. As a consequence the software is no more written once and run many times: it must be updated continuously. If we, as an industry, continue to use the classic category of Technical Debt, IT will be crushed by the forces at hand, pulling the business side along. I propose to introduce a new term for this phenomenon: Technical Inflation. It is not simply to mark the difference but to help discuss and explain to other stakeholders what is happening on the technical side and the effect on the entire business. The new perspective impacts how we plan and budget, how we manage changes and automation, and the need to excel in engineering to save the bottom line.

Software rotting - DevOpsCon Berlin

Software rotting

Software rotting - 28 Apr - DeveloperWeek Europe 2022

"Software rotting or why you need to change your approach to security" 28 April 2022 DeveloperWeek Europe 2022 https://www.developerweek.com/europe/conference/conference-tracks/devops-security/ A new phenomenon stands out in recent years: security must pervade the entire software development lifecycle. Except it isn't. Current generation of processes and tools is lacking crucial features to properly manage modern security risks. Think of the Log4J event. Were you able to identify all affected components? Were they internally developed, or you need a vendor support? How fast you were able to deliver a fix? In this talk we'll explore the challenges, what you can do with current tools, and which gaps should be addressed by communities through better practices and new tools.

L'impatto della sicurezza su DevOps

L'impatto della sicurezza su DevOps

A map for DevOps on Microsoft Stack - MS DevSummit

This document provides an overview of DevOps on the Microsoft stack. It discusses three ways of implementing DevOps: 1) Flowing work from idea to production using tools like GitHub, Azure Boards, Azure DevOps Server, and infrastructure as code. 2) Gathering feedback using observability tools like Application Insights and alerting. 3) Fostering communication, documentation, learning and fun through tools like GitHub Pages, Teams, LinkedIn Learning and DevTest Labs. The document recommends resources for learning more about DevOps and the Microsoft stack.

Perché è così difficile il deploy dei database - DevCast DevOps Serie

Pipeline your Pipelines - 2020 All Day DevOps

Giulio Vian discusses automating build infrastructure by treating it as code that can be versioned, backed up, and rebuilt. This allows building environments to be rebuilt if lost, fixes to be deployed to production, and old versions to be rebuilt. Infrastructure as code uses version control, secrets stores, and pipelines to build runtime, CI/CD, and application infrastructure in a fractal manner.

How to write cloud-agnostic Terraform code - Incontro DevOps Italia 2020

The document discusses how to write Terraform code that is cloud-agnostic and not specific to a single provider. It recommends abstracting common services like networking and computing blocks, and using variables and modules to deploy resources for multiple platforms. Examples are given using count and conditional deployment based on variables, as well as referencing subnets and regions in a provider-independent way. The document aims to help make Terraform configurations reusable across different cloud providers.

Top 10 pipeline mistakes - dotnetsheff

The document lists the top 10 pipeline mistakes, including unsafe secrets, untraceable artifacts, environment-specific deploy packages, lack of testing, use of bleeding edge technology, overly complex builds, flaky builds, overuse of versioning, implicit assumptions, and reliance on dubious plugins. The author provides recommendations to address each mistake, such as using secret stores, adding versioning and links to artifacts, deploying the same packages to all environments, including quality checks, ensuring deployable technology and available agents, splitting processes, enabling reproducible builds, adding version specifications, checking tool requirements, and using autonomous pipelines.

Introduction to Terraform with Azure flavor

Terraform is a tool for provisioning and managing infrastructure as code. It allows defining and deploying infrastructure through configuration files rather than interactive console tools. The configuration files describe the components needed for an application and their relationships, and Terraform uses this information to provision and update infrastructure safely and efficiently. Terraform works by defining resources such as compute instances, storage, and networking components using a high-level configuration language, and then generates and executes the plans to build, change, and version those resources. It supports a variety of cloud platforms including Azure.

How collaboration works between Dev and Ops - DevOps Agile Testing and Test S...

This document summarizes tools and techniques for collaboration between Dev and Ops teams, including: - Shared version control of infrastructure as code, secrets stores, and documentation to provide transparency. - The use of dashboards, chat, wikis, and monitoring and logging tools to share information across teams. - Having Dev and Ops use the same environment names and classifications to facilitate coordination between pipelines, dashboards, and other systems.

Usare SQL Server for Linux e Docker per semplificare i processi di testing - ...

DevOps@Work 2020 Roma, 16 January 2020 https://www.domusdotnet.org/events/ SQL Server per Linux apre un nuovo mondo di possibilità per testare il codice SQL in modi che prima non erano pensabili. Esploriamo alcune opzioni come: - Ripristinare il database ad uno stato noto tra un test e l'altro - Provare più varianti di configurazione - Eseguire test di integrazione nella pipeline CI - Test delle migrazioni dello schema - Attach di grossi database eseguendo i container nel cloud

Pipeline your pipelines!

The document discusses automating build and deployment pipelines using infrastructure as code. It recommends: 1. Treating development environments like production by making them automated, disposable, and recreated from code. 2. Not sharing secrets between environments and making credentials, keys, and other sensitive data unique to each automated environment. 3. Automating the creation of all infrastructure components including VMs, containers, Kubernetes clusters from configuration files to ensure they can be recreated identically on any cloud provider.

Why is DevOps vital for my company’s business

The document discusses why DevOps is vital for companies in the modern business landscape. It notes that software is now central to many businesses and products, like cars which contain over 150 million lines of code. DevOps applies lean principles to streamline the process of delivering software by reducing waste and improving feedback loops between development and operations teams. Implementing DevOps through systems thinking, amplifying feedback, and continuous experimentation can lead to benefits like less risk, faster feedback, and increased value delivery and organizational efficiency.

Introduzione a GitHub Actions (beta)

Terraform for Azure Quickstart