This document summarizes Sanjeev Sharma's presentation on adopting DevOps practices to eliminate bottlenecks using Lean principles. The presentation covers: 1) viewing DevOps through a "Lean" lens to reduce waste and improve flow, 2) addressing bottlenecks with techniques like shifting left testing, full stack deployment, and emphasizing culture and people; and 3) resources for DevOps assessments and further information. The overall message is that DevOps can help optimize software delivery through collaboration, automation, and continuous feedback.
DevOps is a set of practices intended to reduce the time between committing a change to a system and deploying it to production while ensuring high quality. It focuses on bridging the gap between developers and operations teams. Key DevOps principles include systems thinking, amplifying feedback loops, and a culture of experimentation. DevOps aims to achieve continuous delivery through practices like automated deployments, infrastructure as code, and deployment strategies like blue-green deployments and rolling upgrades.
This document provides advice from 29 DevOps experts on successfully transitioning to continuous delivery. The experts discuss building the business case for continuous delivery, getting started with the transition, integrating automation practices, getting team buy-in, and continuing the journey of improvement. Key benefits highlighted include faster time to market, reduced costs, increased customer satisfaction, and competitive advantage.
2019 12 Clojure/conj: Love Letter To Clojure, and A Datomic Experience ReportGene Kim
Talk video: https://www.youtube.com/watch?v=5mbp3SEha38&t=1652s
Blog post: https://itrevolution.com/love-letter-to-clojure-part-1
I will explain how learning the Clojure programming language three years ago changed my life. It led to a series of revelations about all the invisible structures that are required to enable developers to be productive. These concepts show up all over The Unicorn Project, but most prominently in the First Ideal of Locality and Simplicity, and how it can lead to the Second Ideal of Focus, Flow, and Joy.
Without doubt, Clojure was one of the most difficult things I’ve learned professionally, but it has also been one of the most rewarding. It brought the joy of programming back into my life. For the first time in my career, as I’m nearing fifty years old, I’m finally able to write programs that do what I want them to do, and am able to build upon them for years without them collapsing like a house of cards, as has been my normal experience.
The famous French philosopher Claude Lévi-Strauss would say of certain tools, “Is it good to think with?” For reasons that I will try to explain in this post, Clojure embraces a set of design principles and sensibilities that were new to me: functional programming, immutability, an astonishingly strong sense of conservative minimalism (e.g., hardly any breaking changes in ten years!), and much more…
Clojure introduced to me a far better set of tools to think with and to also build with. It’s also led to a set of aha moments that explain why for decades my code would eventually fall apart, becoming more and more difficult to change, as if collapsing under its own weight. Learning Clojure taught me how to prevent myself from constantly self-sabotaging my code in this way.
DevOps Beyond the Buzzwords: What it Means to Embrace the DevOps LifestyleMark Heckler
Session presented at CodeMash 2016.
DevOps is a hot topic, but it’s a bit ambiguous. What do developers really need to know about DevOps? What is it? What ISN’T it? What difference does it make? We’ll start by examining “DevOps”, what it means to embrace it, and the various personnel involved. We consider the potential benefits associated with a DevOps approach and the risks associated with adopting it…and with not adopting it. We take a quick look at some of the tools and platforms that can be used to implement a productive DevOps environment, including (but not limited to):
* Continuous Integration/Continuous Delivery (CI/CD) software
* Infrastructure Build Automation tools
* Virtualization, Containerization, and Cloud options
Finally, we run a live scenario using several of the tools discussed to demonstrate the key components of a DevOps-committed lifestyle. We start from nothing, using available tooling to build the target platform in a scriptable, repeatable fashion…then demonstrate effective use of CI/CD software for a more streamlined and effective software build/test/deploy cycle…and finally show how containers and cloud services form the foundation upon which everything else is built.
2019 Top Lessons Learned Since the Phoenix Project Was ReleasedGene Kim
This document summarizes key lessons from a presentation by Gene Kim on building a world-class engineering culture. Some of the main surprises discussed include: (1) the business value of DevOps is even higher than previously thought, (2) DevOps benefits operations and security as much as development, (3) measuring code deployment lead time is more important than deployments per day, and (4) Conway's Law has implications for organizational structure and architecture. The presentation also discusses how DevOps enables organizations to become dynamic learning organizations.
Devops, the future is here, it's just not evenly distributed yet.Kris Buytaert
This document discusses the DevOps movement and how operations and development teams can work more collaboratively. Some key points:
- DevOps aims to break down barriers between development and operations teams through better communication and automation.
- In the past, developers would deploy code without considering operational requirements, leading to problems once code was in production. DevOps promotes developing and deploying code as a team effort between devs and ops.
- Automating processes like configuration management, continuous integration, deployment and monitoring helps align dev and ops goals and allows more frequent, lower-risk deployments. Tools like Puppet, Chef, Jenkins and Nagios are mentioned.
- The document advocates for practices like test-driven
2012 Velocity London: DevOps Patterns DistilledGene Kim
2012 Velocity London,
Presentation by Patrick Debois (@patrickdebois), Damon Edwards (@damonedwards), Gene Kim (@realgenekim), John Willis (@botchagalupe)
Five Ways Automation Has Increased Application Deployment and Changed CultureXebiaLabs
Paychex, a recognized leader in the payroll, human resource, and benefits outsourcing industry, found that the demand for application deployments had increased beyond what could be supported by manual configuration. Keeping up with this demand required a shift from manually providing a service to developing an automated platform for self-service resulting in a culture change with new partnering across their DEV, OPS and Architecture teams.
David Jozis, Automation Engineer at Paychex, discusses the challenges they encountered when making these significant changes and how they were able to overcome them to accomplish 5x as many deployments as before.
Devops at SlideShare: Talk at Devopsdays Bangalore 2011Kapil Mohan
The document discusses the challenges faced by SlideShare in deploying to production, including tedious manual deployment processes, lack of automation and visibility. This led to long downtimes, wasted time troubleshooting issues and arguments between teams. To address these problems, SlideShare implemented DevOps practices like automated deployments, continuous integration, monitoring and alerting tools. This improved deployment frequency from zero to 5 times a day, increased visibility, shared ownership and helped scale their engineering processes.
DevOps is a movement to change how IT is done by promoting collaboration between development and operations teams. It aims to reduce waste and improve delivery of software by making development and operations processes more efficient through automation, monitoring, and communication. The DevOps philosophy advocates enhancing software design with operational knowledge, building feedback loops from production into development to improve systems, and fostering a culture of shared responsibility. Key DevOps practices include accelerating the flow of changes to production through continuous integration, delivery, and deployment; adding development practices to operations like automated testing; and empowering developers to do production work to break down barriers between teams. DevOps uses tooling throughout the development and operations process to measure and monitor systems and provide feedback.
1) The document provides an overview of DevOps, discussing current business problems like slow releases and downtime that DevOps aims to address.
2) It defines DevOps as a set of practices emphasizing collaboration between development and IT to automate software delivery and infrastructure changes.
3) Key DevOps concepts discussed include continuous integration, continuous delivery, infrastructure as code, and improving communication between teams.
DevOps Kaizen: Find and Fix What is Really Behind Your Problemsdev2ops
This document provides an overview of DevOps Kaizen, which is a methodology for continuous improvement in DevOps. It discusses how Kaizen focuses on continuously improving the flow of work through scientific problem-solving approaches and total workforce engagement. The document outlines elements of a DevOps Kaizen program, including making work processes visible, planning improvements, and overcoming barriers to change. Techniques for process mapping, identifying inefficiencies, and creating improvement plans are also presented.
Continuously Deploying Culture: Scaling Culture at Etsy - Velocity Europe 2012Patrick McDonnell
There was a time not long ago when Etsy was laden with barriers, silos, broken communication, and noncooperation. This talk will focus on the various stages of Etsy's cultural development from the early days to present. We will tell of how Etsy overcame numerous challenges and built a strong company culture while continuing to scale.
DevOps is mainstream - at least the tools, the automation and the metrics. But what happened to DevOps Culture? Does it still matter? If yes - how do we achieve it?
Kris Buytaert discusses the evolution from separate development (Dev) and operations (Ops) teams to a DevOps model where both work together. In the past, Devs would deploy code without considering operational requirements, but now both sides collaborate throughout the development process. Buytaert advocates automating infrastructure management and deployment to improve workflow between Devs and Ops. Adopting practices like configuration management and continuous integration helps bring the two roles together.
DevOps is an increasingly useful tool for achieving business objectives, enabling your teams to work together to improve the efficiency and quality of software delivery. However, despite its growing popularity, there is still a lack of clarity over what DevOps actually means, how organizations should do it and what's the best way to get started.
DevOps 101 takes a brief look at the history of DevOps, why it started, what problems it is intended to solve and how you can start implementing it.
The slides were delivered by James Betteley, Head of Education at the DevOpsGuys in a one-hour webinar. The full recording is available here - https://youtu.be/4gC3WpbetKs?t=2s
James has spent the last few years neck-deep in the world of DevOps transformation, helping a wide range of organizations optimize the way they collaborate to deliver better software, faster. James was joined by Elizabeth Ayer, Portfolio Manager, from Redgate Software. Elizabeth looks after a range of Redgate products that help teams extend their DevOps practices to SQL Server databases.
For more information visit www.devopsguys.com and www.red-gate.com
This document provides an overview of DevOps concepts and practices. It begins with a brief history of DevOps, describing how earlier software development models led to the need for DevOps. It then covers core DevOps concepts like continuous integration, continuous delivery, and continuous deployment. The document discusses DevOps culture at companies like Netflix, Google, Amazon, and Etsy. It also includes a table listing many popular DevOps tools categorized by function like source control, configuration management, testing, deployment etc. The overall summary is that the document is an introduction to DevOps that outlines its origins and needs, defines key practices, and surveys industry use cases and relevant tools.
DevOps Beyond the Buzzwords: Culture, Tools, & Straight TalkMark Heckler
Discussion of DevOps concepts, enabling tools & platforms, and some candid observations. Small plug at end for Cloud Foundry. Slides only, sparkling commentary & conversation with attendees only available in person. :)
This document discusses the business case for DevOps. It begins with an introduction of the speaker and defines some DevOps terminology. It then explains that DevOps involves a technology shift towards more reliable software delivery and improved software operability in production. The document presents a case study of a company that improved software delivery and operability through adopting DevOps practices. It concludes that DevOps provides the communication and collaboration between development and operations teams needed to deliver reliable software systems in the modern era.
by Roberto Pozzi - This round table represents a unique chance to meet the main solution vendors and learn directly from their specialists how PaaS adoption can streamline continuous delivery processes and increase team focus and productivity to dramatically improve time to market. Continuous delivery is an agile approach to software delivery that helps to achieve frequent and reliable releases through team collaboration and full automation. Platform as a service (PaaS) is a cloud computing paradigm that enables rapid deployment of applications without the complexity of managing the underlying infrastructure.
Presentation I held @Codemotion Roundtable on Continuous Delivery & PaaS.
How can you bring value at speed in an ever changing context?
You have to concentrate on what is really valuable, remove waste from your processes and eliminate all your Technical Debt.
Main principles you have to follow are:
- Dev & test in production like environment
- Deliver continuously, experiment continuously
- Validate quality continuously
- Collaborate and be open to feedback
How can you do this without adopting a PaaS approach? Not impossibile but very hard.
Mobile to Mainframe - the Challenges of Enterprise DevOps AdoptionSanjeev Sharma
Delivering software is complex. Systems being developed are made up of multiple components, which in turn interact with other systems, services, application servers, data sources and invocations of 3rd party systems. In an Enterprise this complexity is further enhanced by the cross-platform nature of the infrastructure typical enterprises have. While the customers may be interacting with Systems of Engagement using Mobile and Web Apps, the core capabilities of the enterprise that the customers access are in Systems of Record that are running on large datacenters and more than likely Mainframe systems. Keeping these complex systems up and running and constantly updated with the latest capabilities is a task that requires constant coordination between the lines of business, various cross-platform development, QA and operations teams.
DevOps addresses these development and deployment challenges. The goal of DevOps is to align Dev and Ops by introducing a set of principles and practices such as continuous integration and continuous delivery. Cross-platform enterprise Systems take the need for these practices up a level due to their inherent complexity and distributed nature. Such systems need even more care in applying DevOps principles as there are multiple platforms to be targeted, in a coordinated manner, each with its own requirements, quirks, and nuanced needs.
This talk will take a look at the DevOps challenges specific to Cross-platform Enterprise Systems and present Best Practices to address them.
Applying lean, dev ops, and cloud for better business outcomesKartik Kanakasabesan
1) Adopting DevOps, Lean, and cloud approaches can help government agencies deliver better citizen services with fewer resources by accelerating delivery of new features and getting faster feedback.
2) A DevOps approach involves applying Lean principles to get new ideas into production fast, get people to use new features, and get feedback in order to continuously improve. This allows agencies to change faster, which is an asset rather than an anchor.
3) Adopting cloud technologies helps remove bottlenecks around environment availability and provisioning, allowing standardized, lower cost, and faster delivery of applications and services.
Applying DevOps, PaaS and cloud for better citizen service outcomes - IBM Fe...Sanjeev Sharma
1) Applying DevOps practices like continuous integration/delivery can help government agencies deploy IT projects faster and get citizen services into production quicker.
2) Using a Platform as a Service (PaaS) like IBM Bluemix allows agencies to build and manage applications faster while reducing costs and skills requirements.
3) Adopting a DevOps culture and tools that automate testing, deployment, and monitoring can help agencies accelerate delivery of citizen services with better outcomes and less resources.
IBM UrbanCode Deploy: Automates and manages the deployments of business applications made of many component pieces such as web services, databases, content, CICS and mobile apps. Through automation, costly errors and manual labor are drastically reduced. UrbanCode Deploy also eliminates a common bottleneck between agile development teams and slower operations groups thereby speeding time to market. UrbanCode Deploy excels at driving down cost and reducing risk.
IBM UrbanCode Deploy with Patterns: A leading edge offering that combines all the great capabilities of UrbanCode Deploy with additional capabilities for designing and deploying full-stack environments on cloud and updating configurations for existing cloud environments.
IBM UrbanCode Release: A robust collaborative release management tool that helps you handle the growing number and complexity of releases. You can plan, execute, and track a release through every stage of the delivery lifecycle.
IBM UrbanCode Build: An enterprise continuous integration server used for managing builds, build artifacts and the dependancies inherent with them. UrbanCode Build specializes in reducing errors and speeding handoffs through a managed self-service build infrastructure.
DevOps aims to improve collaboration between development and operations teams to accelerate software delivery cycles and reduce risks. This allows for more frequent and reliable software releases while incorporating customer and end user feedback. The document discusses how DevOps addresses inefficiencies in traditional software development models and leverages practices like continuous integration, delivery, deployment and monitoring. It also explores how DevOps and hybrid cloud environments can help organizations improve customer experiences through faster and more reliable application updates.
This document provides an overview and introduction to DevOps. It discusses that DevOps involves people, processes, and tools working together. It describes how DevOps extends lean and agile principles across the entire application development lifecycle from development to operations. Specifically, it promotes a culture of collaboration between development and operations teams. It also explains how DevOps aims to address bottlenecks in the software delivery process through practices like continuous integration, deployment, and testing.
IBM Pulse session 2727: Continuous delivery -accelerated with DevOpsSanjeev Sharma
Continuous delivery accelerated with DevOps. The document discusses how DevOps and continuous delivery can help speed up software releases through automation. It defines DevOps as taking a holistic view of development and operations. Continuous delivery is establishing a pipeline to reliably and repeatedly deploy any changes to any environment through automation. This pipeline includes continuous integration, testing, deployment, monitoring, and feedback loops.
Mobile to mainframe - The Challenges and Best Practices of Enterprise DevOps IBM UrbanCode Products
Delivering software is complex. Systems being developed are made up of multiple components, which in turn interact with other systems, services, application servers, data sources and invocations of 3rd party systems. In an Enterprise this complexity is further enhanced by the cross-platform nature of the infrastructure typical enterprises have. While the customers may be interacting with Systems of Engagement using Mobile and Web Apps, the core capabilities of the enterprise that the customers access are in Systems of Record that are running on large datacenters and more than likely Mainframe systems. Keeping these complex systems up and running and constantly updated with the latest capabilities is a task that requires constant coordination between the lines of business, various cross-platform development, QA and operations teams.
DevOps addresses these development and deployment challenges. The goal of DevOps is to align Dev and Ops by introducing a set of principles and practices such as continuous integration and continuous delivery. Cross-platform enterprise Systems take the need for these practices up a level due to their inherent complexity and distributed nature. Such systems need even more care in applying DevOps principles as there are multiple platforms to be targeted, in a coordinated manner, each with its own requirements, quirks, and nuanced needs. This talk takes a look at the DevOps challenges specific to Cross-platform Enterprise Systems and present Best Practices to address them.
The document discusses challenges in software delivery including costly and error-prone manual processes, risks from managing multiple configurations and versions, and slow deployment times. It notes examples of companies incurring major losses from software failures and glitches. The document promotes DevOps as enabling continuous delivery, feedback and improvements. It presents IBM solutions for collaborative lifecycle management including modular open components and how they integrate to support DevOps.
IBM DevOps Enabling continuous integration & deliveryRoberto Pozzi
This presentation is the result of several engagements with clients on the topic of software lifecycle management and continuous delivery.
I acknowledge the contribution of Daniel Berg (Chief Architect, DevOps Tools & Strategy) for all the slides related to DevOps and IBM DevOps Strategy
DevOps 101 provides an overview of DevOps concepts and adoption in the enterprise. It discusses why DevOps is important to accelerate software delivery, improve quality, and increase collaboration between development and operations. The document outlines key aspects of adopting DevOps, including focusing on people, processes, and technologies. It also provides an overview of IBM's DevOps solution to help organizations continuously deliver innovation through improved software development and delivery.
DevOps is a software development method that stresses collaboration between developers and IT operations professionals. It aims to create solutions that are rapid, repeatable, consistent, flexible and scalable. Traditionally, development and operations were separate, leading to slow processes and finger pointing during issues. DevOps aligns the two areas to address these challenges through automation, continuous integration and delivery, and culture change. The document then outlines IBM's DevOps tools that can help organizations improve processes across the development lifecycle.
IBM's DevOps solution aims to bring innovation faster to customers by applying Lean principles to create a continuous feedback loop. It addresses typical DevOps challenges like siloed environments and long development cycles. The solution proposes collaboration tools, cloud-enabled environments, deployment automation, and a hybrid cloud to streamline the DevOps lifecycle. Case studies show outcomes like 90% reduced testing time and 4-week reductions in time-to-market.
This document provides an overview of the IBM UrbanCode Deploy course. It introduces UrbanCode Deploy as a solution for automating deployments and managing application releases. Key topics covered include common deployment challenges, UrbanCode Deploy terminology, components, applications, and environments. The course materials and outline are also summarized. It provides information on the lab environment setup, including the UrbanCode Deploy server, agents, and targets. A basic workflow for using UrbanCode Deploy is also outlined.
How to Balance System Speed and Risk for Multi-Platform InnovationClaudia Ring
Walking the line between speed to market and stability of mission-critical systems is something many enterprise organizations deal with on a consistent basis, especially when planning a major application release. Multi-speed IT is a term that connotes the difficulty of balancing speed and risk for these enterprises, but also one that inherently defines a solution; moving at different speeds depending on system requirements. While moving at various speeds based on whether you are releasing changes for Systems of Engagement (SOE) or Systems of Record (SOR) can seem negative, it can be used as a stepping stone towards complete enterprise agility and iterative improvements in release management across both types of systems. Join Rosalind Radcliffe, IBM Distinguished Engineer and Chief Architect for DevOps, as she discusses;
How to begin incorporating continuous testing into the release cycle for both SOE's and SOR's
How deployment automation can be incorporated into multi-platform deployments
How earlier, more frequent testing and automated deployments can help stabilize risk while increasing speed
Customer success with using these testing and deployment solutions to achieve agility across both SOE's and SOR's
NBCUniversal is implementing DevOps practices like continuous integration, delivery, and testing using tools from IBM like UrbanCode Deploy, IBM Dev-Test Environment as a Service (IDTES), and IBM Cloud Orchestrator. This allows them to continuously test code, deploy applications across hybrid clouds, and improve collaboration between development and operations teams. NBCUniversal's DevOps practices aim to address issues like slow release processes and lack of integration between development stages.
The document discusses DevOps capabilities for IBM Z systems. It introduces Application Discovery and Delivery Intelligence (ADDI) which can discover and understand application landscapes, enable impact analysis for changes, and improve development and testing efforts. It also discusses the Application Delivery Foundation for Z (ADFz) which includes tools for development, testing, and automating delivery pipelines. Finally, it provides demos of capabilities like dependency based builds, automated unit testing, and shift left testing approaches.
The document discusses DevOps capabilities for IBM Z systems. It introduces Application Discovery and Delivery Intelligence (ADDI) which can discover and understand application landscapes and enable safer changes. It also discusses the Application Delivery Foundation for z Systems (ADFz) which includes tools for development, testing, and automation. Finally, it provides demos of capabilities like dependency based builds, automated unit testing, and integrating tools into a continuous delivery pipeline.
Similar to CampDevOps keynote - DevOps: Using 'Lean' to eliminate Bottlenecks (20)
This document discusses democratizing security as the next frontier for DevSecOps adoption in enterprises. It covers evolving delivery practices like Agile, DevOps, and SRE. Democratizing involves making capabilities self-service, granting permission to act with guardrails, and building trust. This includes democratizing infrastructure, software delivery, data, and security by making them technology agnostic, self-service, and including them in the DevSecOps toolchain to improve applications, platforms, processes, and culture. Security chaos engineering and value stream mapping are also discussed as ways to identify vulnerabilities and inefficiencies to continuously improve operational readiness and adoption.
This document discusses democratizing data and including it as part of the DevOps toolchain. It argues that data should be made available as a service and provisioned in a secure and compliant manner to empower developers. The document recommends using a DataOps approach and platform like Delphix to virtualize data from various sources and provision production-like test data for developers in an automated way. This helps overcome issues like long test data provisioning times and lack of access to production data, improving the delivery pipeline. Case studies of insurance and banking clients adopting this approach are also presented.
Cloud expo 2018: From Apollo 13 to Google SRE - When DevOps meets SRESanjeev Sharma
This document discusses Site Reliability Engineering (SRE), which is Google's approach to service management. It outlines the key tenets of SRE, which include ensuring a durable focus on engineering, pursuing maximum change velocity without violating service-level objectives, monitoring, emergency response, change management, demand forecasting and capacity planning, provisioning, and efficiency and performance. The document also discusses best practices for incident management in SRE and how DevOps and SRE can be applied in the enterprise.
How to achieve 'Flow' in your delivery pipeline.
This was an 'Ignite' session at DevOpsDaysDC 2018. Ignite sessions are 5 minutes long with 20 slides auto-advancing every 15 seconds.
DeliverAgile2018 - from Apollo 13 to Google SRESanjeev Sharma
This document discusses Site Reliability Engineering (SRE) and how it relates to DevOps. It provides definitions of SRE and outlines Google's approach. The document also discusses key SRE concepts like reliability targets, best practices for incident management, and how SRE can be applied in the enterprise by balancing innovation and optimization. Finally, it highlights areas where DevOps and SRE intersect, noting that both aim to continuously deliver business value.
The complexity of managing and delivering the high level of reliability expected of web-based, cloud hosted systems today, and the expectation of Continuous Delivery of new features has led to the evolution of a totally new field of Service Reliability Engineering catered for such systems. Google, who has been a pioneer in this field, calls it Site Reliability Engineering (SRE). While it would be more aptly named Service Reliability Engineering, the name has caught on. The seminal work documenting Google approach and practices is in the book by Google by the same name (commonly referred to as the ‘SRE book’), and has become the defacto standard on how to adopt SRE in an organization. This session will cover adopting SRE as a practice in organizations also adopting DevOps; address the challenges to adopting SRE faced by large traditional enterprises, and how to overcome them.
From DevOps to DevSecOps: 2 Dimensions of Security for DevOpsSanjeev Sharma
This document discusses security considerations for DevOps enterprises transitioning to DevSecOps. It identifies three dimensions of security: 1) securing the perimeter, 2) securing the delivery pipeline, and 3) securing deliverables. For the delivery pipeline, it notes vulnerabilities related to supply chains, insider attacks, errors in development, and weaknesses in design/code/integration. It emphasizes applying security practices throughout the development lifecycle, from coding through deployment. The document provides references for further reading on DevOps security best practices.
Unicorns on an Aircraft Carrier: CDSummit London and Stockholm KeynoteSanjeev Sharma
The document discusses achieving business value through innovation and optimization using DevOps practices. It describes how DevOps works well for small isolated teams but greater collaboration is needed across larger organizations. The author advocates a multi-speed approach to IT that balances innovation using newer technologies with stability from more traditional systems. Standardizing tools and practices can help scale DevOps across the enterprise by breaking down silos.
This document provides information about a DevOps workshop that IBM can sponsor for clients. The workshop aims to help clients develop a pragmatic approach to adopting DevOps practices to balance optimization and innovation. The goals are to understand business and IT goals for DevOps, identify gaps in DevOps capabilities, and create a prioritized roadmap for adoption. The workshop would involve executives, developers, and operations staff and last 6-7 hours, with follow-up presentations of results and recommendations. IBM also offers related workshops focused on transformation using Bluemix and best practices.
IBM InterConnect 2016: Security for DevOps in an Enterprise Sanjeev Sharma
1) The document discusses security considerations for DevOps enterprises, including securing the perimeter, delivery pipeline, and deliverables. It outlines risks like vulnerabilities in the supply chain, insider attacks, and errors in development.
2) It recommends adopting a DevOps architecture with an industrialized core and agile/innovation edge to support both traditional and cloud-native applications. This involves transforming traditional IT and adopting practices like infrastructure as code.
3) The document provides an example of mapping a delivery pipeline to identify bottlenecks and shows where security testing and controls can be implemented at each stage, from idea to production. It emphasizes the need for continuous security.
The document discusses adopting DevOps practices at enterprise scale, outlining three patterns of DevOps adoption: driving business agility, scaling for the enterprise across hybrid environments, and driving innovation through rapid experimentation and feedback using techniques like containerization and microservices. It provides examples and case studies of organizations addressing bottlenecks in their development and deployment processes by applying practices like continuous integration, deployment automation, test automation, and service virtualization.
dev@InterConnect workshop - Lean and DevOpsSanjeev Sharma
The document discusses how adopting DevOps practices can improve efficiency and effectiveness in software delivery. It argues that focusing on the delivery of valuable product features rather than non-value adding processes can minimize waste. Specifically, it recommends shifting testing activities left in the development cycle to reduce unnecessary rework later on through earlier feedback on integration and system behaviors. Adopting practices like continuous delivery and automation can further help optimize the delivery pipeline and improve productivity.
To grow their business, companies need to securely deliver data globally with extreme speed while ensuring governance, compliance and service level agreements. This requires automating the application delivery pipeline so that applications can be delivered and updated frequently while maintaining performance. A hybrid cloud environment is necessary to provide both on-premise and cloud-based options. IBM offers several products to help companies achieve this, including Cloud Orchestrator, Cloud Manager, UrbanCode Deploy, BlueMix, MobileFirst Platform, and Aspera for hybrid cloud capabilities.
DTS-1778 Understanding DevOps - IBM InterConnect SessionSanjeev Sharma
- The document discusses DevOps and how it can help improve the delivery pipeline by automating deployment of infrastructure and applications. It addresses how DevOps enables continuous integration, delivery, testing and monitoring across hybrid cloud environments.
- It describes challenges like different development and deployment speeds for "front-end" and "back-end" systems, and how DevOps practices like service virtualization and deployment automation can help coordinate rapid and slower iterations.
- The document provides an overview of IBM's DevOps adoption model and recommends starting with collaborative development and continuous delivery practices to address bottlenecks and improve efficiency.
Mobile to Mainframe - En-to-end transformationSanjeev Sharma
This document discusses challenges and solutions related to connecting mobile applications to mainframe and backend systems. It describes how mobile apps are the front-end to complex backend enterprise systems. It then discusses challenges like fragmented platforms, mobile app quality, and ensuring the right apps are built. Finally, it provides solutions such as starting with a minimum viable product, matching mobile and backend UX, separating backend architecture components, continuous testing, and integrating systems of engagement with systems of record.
DevOps and Application Delivery for Hybrid Cloud - DevOpsSummit sessionSanjeev Sharma
The world is Hybrid. Organizations adopting DevOps are building Delivery Pipelines leveraging environments that are complex - spread across hybrid cloud and physical environments. Adopting DevOps hence required Application Delivery Automation that can deploy applications across these Hybrid Environments.
Using Lean Thinking to identify and address Delivery Pipeline bottlenecksSanjeev Sharma
Using Lean Thinking to identify and address Delivery Pipeline bottlenecks discusses applying Lean principles to accelerate feedback and improve time to value across the development, testing, and production stages. It identifies common bottlenecks like deploying infrastructure and provides examples of how adopting DevOps practices like continuous delivery can help optimize pipelines and flow of work. The document advocates mapping bottlenecks and implementing solutions like capturing infrastructure as code to enable faster, more reliable application deployments.
This document provides an overview of DevOps concepts and adoption. It discusses adopting DevOps through a focus on people, processes, and technology. It outlines implementing continuous delivery pipelines and integrating systems of engagement with systems of record. The document proposes applying Lean principles to software delivery to create continuous feedback loops with customers.
Enabling DevOps in the cloud - Federal Cloud Innovation CenterSanjeev Sharma
This document discusses enabling DevOps for cloud deployments. It introduces DevOps as a lean approach to reduce waste and improve efficiency. Deploying applications to the cloud with DevOps allows for standardization, lower costs, and faster delivery. IBM's BlueMix platform and DevOps services provide tools for continuous delivery pipelines to deploy to cloud environments. Future directions involve supporting OpenStack cloud patterns to drive consistency with proven best practices.
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
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.
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
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.
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.
Coordinate Systems in FME 101 - Webinar SlidesSafe Software
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights.
During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to:
- Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value
- Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems
- Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors
- Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported
- Look Ahead: Gain insights into where FME is headed with coordinate systems in the future
Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
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.
TrustArc Webinar - 2024 Data Privacy Trends: A Mid-Year Check-InTrustArc
Six months into 2024, and it is clear the privacy ecosystem takes no days off!! Regulators continue to implement and enforce new regulations, businesses strive to meet requirements, and technology advances like AI have privacy professionals scratching their heads about managing risk.
What can we learn about the first six months of data privacy trends and events in 2024? How should this inform your privacy program management for the rest of the year?
Join TrustArc, Goodwin, and Snyk privacy experts as they discuss the changes we’ve seen in the first half of 2024 and gain insight into the concrete, actionable steps you can take to up-level your privacy program in the second half of the year.
This webinar will review:
- Key changes to privacy regulations in 2024
- Key themes in privacy and data governance in 2024
- How to maximize your privacy program in the second half of 2024
Comparison Table of DiskWarrior Alternatives.pdfAndrey Yasko
To help you choose the best DiskWarrior alternative, we've compiled a comparison table summarizing the features, pros, cons, and pricing of six alternatives.
The DealBook is our annual overview of the Ukrainian tech investment industry. This edition comprehensively covers the full year 2023 and the first deals of 2024.
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.