Alex Vinyar is an enterprise architect with 18 years of automation experience who provides on-site consulting engagements to help companies assess their infrastructure and workflows, implement DevOps practices, and train teams. He has worked with many large companies to help them start their DevOps journeys. Some key lessons he has learned include getting executive sponsorship to provide resources and protection for changes, starting with a small initial project, controlling the impact of changes, appointing internal champions, using metrics to prove value, taking care of employees, understanding that culture change takes time, and regularly demoing successes and failures to build community.
How to survive continuous innovation - Sebastien Goasguen - DevOpsDays Tel Av...DevOpsDays Tel Aviv
The document discusses how to continuously innovate with software given the rapid pace of new technologies being introduced and the large research and development budgets of corporations. It emphasizes the need to build solutions that address business needs rather than adopting every new tool, and to develop an adaptive culture within teams that can respond to changing technologies and industry trends. Examples are provided of how open source technologies like Docker have evolved and best practices for evaluating and using new software.
eSynergy Paul Swartout - DevOps - what is it and why is it valuable to businessPatrickCrompton
This document discusses DevOps, which aims to improve collaboration between software development (Dev) and IT operations (Ops) teams. It notes the benefits of Agile software development and continuous delivery. The document then discusses how one company moved from releasing software every 2 weeks with a team of 200 people to having a single engineer release software every 30 minutes with no downtime, by adopting DevOps practices like automation and collaboration between Dev and Ops. Key business benefits of DevOps mentioned include focusing on new features rather than releases, improved platform understanding, aligned team vision and goals, and reduced "us vs them" mentalities. Some pointers on DevOps adoption are that it requires time, tools help but aren't essential, and progress must be
The Journey of devops and continuous delivery in a Large Financial InstitutionKris Buytaert
The Journey of devops and continuous deliverey in a Large Financial Institution,
as presented by @markheistek and myselve at Velocity Conf 2013, Longon
Building effective dev ops engineering culture newRovshan Musayev
Rovshan Musayev, a DevOps engineer, presents on building effective DevOps engineering culture. DevOps aims to automate processes between software development and operations teams to build, test, and release software faster and more reliably. Historically, these teams operated in silos with poor collaboration, whereas DevOps values breaking down silos through practices like infrastructure as code, continuous integration, deployment, and automation. Effective DevOps principles include collaboration between Dev and Ops, empowering autonomy, learning from mistakes, and prioritizing tasks. People are prioritized over processes and tools in the DevOps methodology.
Tom Klaasen has 10 years of experience developing software using Java/J2EE and more recently Ruby on Rails and iOS. He co-founded 10to1 in 2006 which uses an agile development process with 4 highly skilled passionate developers. They focus on communication through daily deployments and meetings with users, prioritizing developing workable applications over extensive testing or documentation. Their agile approach is influenced by the conventions of Ruby on Rails and aims to be flexible rather than following rigid rules.
Android Developer Skills, Techniques, and Patternsgdgut
Ancestry is a large company that provides family history and DNA testing services. It has over 1 billion records in its databases and over 3 million subscribers. As an Android developer at Ancestry, a typical day involves collaborating with teammates to work on user stories, addressing bugs, learning new skills, and ensuring code quality. Developers focus on testing, code reviews, following best practices, and balancing individual and team work. The goal is to build high quality features while continuously improving skills.
The document discusses a collaborative usability testing technique to involve stakeholders in user research. It recommends bringing together stakeholders to observe usability tests, prioritize usability issues observed, and agree on solutions. Participants watch 3 short test sessions, take notes on issues, then consolidate lists of top issues to agree on actions. Being involved makes stakeholders more invested in addressing usability problems. The presenter provides tips for effective collaborative testing and resources for prioritization methods.
Minimum Viable Architecture -- Good Enough is Good Enough in a StartupRandy Shoup
I have spent the last decade building large-scale systems at eBay and Google -- and talking publicly about it -- and this presentation is about why a startup should completely ignore what I said! In an early-stage startup, it is not only not worth architecting for a future of massive scale; it is actively counterproductive. This presentation from the SF Startup CTO Summit outlines the common architectural evolution of a startup through the search, execution, and scaling phases, and discusses the appropriate technologies and disciplines at each phase. It ends with some real-world examples from eBay, Twitter, and Amazon to illustrate the point.
Introductory slides to a collaborative usability observation & issue prioritisation session. A training and service promotion workshop for the University of Edinburgh Website Programme.
Bringing Open-Source Practices to Your Day JobBen Coe
Ben Coe is an employee at npm and lead maintainer of several open source projects. He discusses how open source best practices like automating tests, enforcing coding styles, and keeping dependencies updated can be applied in large corporations. These practices were designed for large asynchronous teams and using them internally, through a concept called InnerSource, can make developing enterprise software easier. npm and GitHub are working together to better integrate their tools and spread the message that open source practices benefit both open source and enterprise development.
WTF: Where To Focus when you take over a Drupal projectSymetris
Jumping into pre-built Drupal projects sometimes requires a leap of faith as much for clients as for developers. The client is usually coming out of a bad previous business relationship and the code is not always structured according to your standards.
During this talk, Symetris will share its experience and provide tips on how to navigate these often uncharted waters. Our goal is to help you convert an uncertain client into a long term partner and have a checklist of what to look out for as developers.
Demystifying DevOps - it's not Agile, but they're friendsMax Griffiths
DevOps aims to help organizations rapidly produce software by improving the interdependence between software development and IT operations. While DevOps has been around for a long time, there is still confusion about what it means. True DevOps culture focuses on shared ownership and a philosophy of fast feedback, customer focus, and optimizing for speed and quality rather than specific roles. Good DevOps looks like simple communication, co-location of teams when possible, and infrastructure defined as code.
The document discusses the benefits of using work-in-progress (WIP) limits to manage software projects more efficiently. It notes that while 100% utilization seems ideal, it actually leads to lower quality and longer cycle times due to multitasking. Introducing moderate WIP limits of around 2x the average WIP has been shown to significantly improve average cycle times by around 60% while only increasing costs marginally. The slack time created allows for continuous improvement, automation, higher quality code, and helps the team self-balance. Ultimately, utilizing WIP limits results in more efficient work compared to constantly keeping teams at 100% utilization.
Velocity Conference NYC 2014 - Real World DevOpsRodrigo Campos
Rodrigo Campos presented on the challenges faced and benefits of adopting a DevOps culture at Walmart's Latin American e-commerce division. The key challenges included deploying a new platform before Black Friday, expanding infrastructure for traffic spikes, developing an agile mindset, and rebuilding trust between teams. Adopting DevOps practices like improved communication, transparency and collaboration helped address these challenges. It resulted in the successful deployment of the new platform with 100% uptime on Black Friday and increased deployment frequency, success rates and adoption of agile methodologies.
This document outlines a structured approach to debugging distributed systems. It begins with observing and documenting the problem. The next steps involve creating a minimal reproducer, debugging the client and server sides, and checking DNS, routing, and network connections. Additional steps include inspecting traffic, attaching remote debuggers, and conducting a post-mortem analysis. Throughout the process, various tools can help with tasks like logging, testing, and network inspection. The document concludes by emphasizing the importance of understanding failure modes through experience debugging real issues with distributed systems.
The Importance of Culture: Building and Sustaining Effective Engineering Org...Randy Shoup
Randy is a 25-year veteran of Silicon Valley, having led engineering organizations at eBay, Google, Oracle, and a number of other companies. Through the lens of his personal experience from hands-on engineer to architect to CTO, at organizations ranging from tiny startups to global giants, Randy will discuss several important aspects of engineering cultures, which both support and hinder the ability to innovate: hiring and retention, ownership and collaboration, quality and discipline, and learning and experimentation.
Randy will suggest some learnings about what has worked well -- and what has not -- in creating and sustaining an effective engineering culture. He will further offer some concrete suggestions on how other organizations -- both large and small -- can evolve their cultures as well.
Skills Matter DevSecOps eXchange Forum 2022 - Software architecture in a DevO...Bert Jan Schrijver
The document discusses how software architects can work with DevOps teams by applying DevOps principles to software architecture. Some key points made:
- DevOps principles like gradual changes, customer orientation, automation, ownership, collaboration, experimentation and continuous improvement should guide architectural decisions and processes.
- The architecture should start simply and evolve iteratively based on feedback from developers and customers.
- Automation, infrastructure as code, and measuring architectural decisions are important.
- The team should own the architecture collaboratively and the architect must be accountable and involved.
The Fundamentals of Continuous Software DesignJeremy Miller
This document discusses principles of continuous software design, including:
- Designing incrementally and reacting to feedback rather than doing big upfront design.
- Making decisions as late as responsibly possible to have the most information.
- Prioritizing reversibility so designs can easily change.
- Using test-driven development, refactoring, and bottom-up design to improve code quality and flexibility over time.
- Constantly challenging designs through techniques like spiking and socializing ideas with others.
How contributing to Open-source made me a better DevOpsAhmed AbouZaid
How participating in Open-source made me a better DevOps
And that actually started not just as a professional system engineer, but much earlier as a normal end-user also as a power user.
This document provides information about the author and DevOps. The author is a DevOps engineer at Pluralsight who has worked in release management since 2006 and is passionate about continuous delivery. DevOps is defined as a culture of continuous improvement through automation, metrics, and sharing to connect development, testing, configuration, and operations. The document asks questions about what is automated, measured, shared, and how teams are structured in a DevOps environment.
DevOps is far more about culture and organization than it is about technology and tooling. This talk will discuss the speaker's experiences leading high-performing engineering teams at Google, eBay, and Stitch Fix, and will offer suggestions for other organizations to level up their DevOps game.
https://www.meetup.com/SV-ELC/events/240087808/
Modern software-service models take advantage of the great benefits in having the same team both build the software as well as operate it in production -- "You Build It; You Run It" is the Amazon mantra. What does this mean in practice?
Organizationally, it means small teams with well-defined areas of responsibility, directly aligned with the business. The teams are cross-functional, meaning that each team has all the skill sets it requires to do its job, while at the same time relying on other teams for supporting services, tools, and libraries.
Process-wise, it means doubling down on practices like test-driven development and continuous delivery. Using continuous delivery practices, high-performing teams can and do release their applications and services multiple times a day. This enables them to iterate rapidly, experiment courageously, and fail more quickly.
Culturally, it means end-to-end ownership. Each team owns its software end-to-end, from design to development to deployment to retirement. The same engineers who are responsible for the features are responsible for quality, performance, operations, and maintenance. This ownership puts incentives in the right place to encourage building maintainable, observable, and operable systems from the start.
All these techniques and approaches are available to everyone, and practical examples in this talk will help other organizations on their journey.
DOES15 - Randy Shoup - Ten (Hard-Won) Lessons of the DevOps TransitionGene Kim
Randy Shoup, Consulting CTO
DevOps is no longer just for Internet unicorns any more. Today many large enterprises are transitioning from the slow and siloed traditional IT approach to modern DevOps practices, and getting substantial improvements in agility, velocity, scalability, and efficiency. But this transition is not without its challenges and pitfalls, and those of us who have led this journey have the scar tissue to prove it.
A successful transition to DevOps practices ultimately involves changes to organization, to culture, and to architecture. Organizationally, we want to create multi-skilled teams with end-to-end ownership and shared on-call responsibilities. Culturally, we want to prioritize solving problems and improving the product over closing tickets. Architecturally, we want to move to an infrastructure with independently testable and deployable components.
The ten practical lessons outlined in this session synthesize the speaker’s experiences leading teams at eBay, Google, and KIXEYE, as well as from his current consulting practice.
Don't forget the people - DevOps Manchester 10th Oct 2015James Heggs
DevOps Manchester 10th Oct 2015
Stories from previous experiences of attempting to move towards a DevOps culture based around the people aspects of decision.
This document outlines a structured approach to debugging distributed systems. It begins with observing and documenting the problem. The next steps involve creating a minimal reproducer, debugging the client and server sides, and checking DNS, routing, and network connections. Traffic and messages should also be inspected. The process concludes by wrapping up findings and conducting a post-mortem analysis. Key challenges in distributed systems like concurrency, lack of a global clock, and independent failures are discussed.
Systems biology in polypharmacology: explaining and predicting drug secondary...Andrei KUCHARAVY
This document discusses using systems biology approaches to predict and explain off-target drug effects. It notes that unexpected secondary drug effects and lack of therapeutic effects are major reasons drug development fails. The document proposes using computational methods to predict all protein targets a drug may affect and using systems biology to model the consequences, including secondary effects, unexpected therapeutic effects via drug repositioning, and unexpected lack of effects. It outlines a master's project to develop models of polypharmacological drug effects by analyzing networks of drug-affected protein targets and retrieving relevant biological annotation to interpret effects.
Minimum Viable Architecture -- Good Enough is Good Enough in a StartupRandy Shoup
I have spent the last decade building large-scale systems at eBay and Google -- and talking publicly about it -- and this presentation is about why a startup should completely ignore what I said! In an early-stage startup, it is not only not worth architecting for a future of massive scale; it is actively counterproductive. This presentation from the SF Startup CTO Summit outlines the common architectural evolution of a startup through the search, execution, and scaling phases, and discusses the appropriate technologies and disciplines at each phase. It ends with some real-world examples from eBay, Twitter, and Amazon to illustrate the point.
Introductory slides to a collaborative usability observation & issue prioritisation session. A training and service promotion workshop for the University of Edinburgh Website Programme.
Bringing Open-Source Practices to Your Day JobBen Coe
Ben Coe is an employee at npm and lead maintainer of several open source projects. He discusses how open source best practices like automating tests, enforcing coding styles, and keeping dependencies updated can be applied in large corporations. These practices were designed for large asynchronous teams and using them internally, through a concept called InnerSource, can make developing enterprise software easier. npm and GitHub are working together to better integrate their tools and spread the message that open source practices benefit both open source and enterprise development.
WTF: Where To Focus when you take over a Drupal projectSymetris
Jumping into pre-built Drupal projects sometimes requires a leap of faith as much for clients as for developers. The client is usually coming out of a bad previous business relationship and the code is not always structured according to your standards.
During this talk, Symetris will share its experience and provide tips on how to navigate these often uncharted waters. Our goal is to help you convert an uncertain client into a long term partner and have a checklist of what to look out for as developers.
Demystifying DevOps - it's not Agile, but they're friendsMax Griffiths
DevOps aims to help organizations rapidly produce software by improving the interdependence between software development and IT operations. While DevOps has been around for a long time, there is still confusion about what it means. True DevOps culture focuses on shared ownership and a philosophy of fast feedback, customer focus, and optimizing for speed and quality rather than specific roles. Good DevOps looks like simple communication, co-location of teams when possible, and infrastructure defined as code.
The document discusses the benefits of using work-in-progress (WIP) limits to manage software projects more efficiently. It notes that while 100% utilization seems ideal, it actually leads to lower quality and longer cycle times due to multitasking. Introducing moderate WIP limits of around 2x the average WIP has been shown to significantly improve average cycle times by around 60% while only increasing costs marginally. The slack time created allows for continuous improvement, automation, higher quality code, and helps the team self-balance. Ultimately, utilizing WIP limits results in more efficient work compared to constantly keeping teams at 100% utilization.
Velocity Conference NYC 2014 - Real World DevOpsRodrigo Campos
Rodrigo Campos presented on the challenges faced and benefits of adopting a DevOps culture at Walmart's Latin American e-commerce division. The key challenges included deploying a new platform before Black Friday, expanding infrastructure for traffic spikes, developing an agile mindset, and rebuilding trust between teams. Adopting DevOps practices like improved communication, transparency and collaboration helped address these challenges. It resulted in the successful deployment of the new platform with 100% uptime on Black Friday and increased deployment frequency, success rates and adoption of agile methodologies.
This document outlines a structured approach to debugging distributed systems. It begins with observing and documenting the problem. The next steps involve creating a minimal reproducer, debugging the client and server sides, and checking DNS, routing, and network connections. Additional steps include inspecting traffic, attaching remote debuggers, and conducting a post-mortem analysis. Throughout the process, various tools can help with tasks like logging, testing, and network inspection. The document concludes by emphasizing the importance of understanding failure modes through experience debugging real issues with distributed systems.
The Importance of Culture: Building and Sustaining Effective Engineering Org...Randy Shoup
Randy is a 25-year veteran of Silicon Valley, having led engineering organizations at eBay, Google, Oracle, and a number of other companies. Through the lens of his personal experience from hands-on engineer to architect to CTO, at organizations ranging from tiny startups to global giants, Randy will discuss several important aspects of engineering cultures, which both support and hinder the ability to innovate: hiring and retention, ownership and collaboration, quality and discipline, and learning and experimentation.
Randy will suggest some learnings about what has worked well -- and what has not -- in creating and sustaining an effective engineering culture. He will further offer some concrete suggestions on how other organizations -- both large and small -- can evolve their cultures as well.
Skills Matter DevSecOps eXchange Forum 2022 - Software architecture in a DevO...Bert Jan Schrijver
The document discusses how software architects can work with DevOps teams by applying DevOps principles to software architecture. Some key points made:
- DevOps principles like gradual changes, customer orientation, automation, ownership, collaboration, experimentation and continuous improvement should guide architectural decisions and processes.
- The architecture should start simply and evolve iteratively based on feedback from developers and customers.
- Automation, infrastructure as code, and measuring architectural decisions are important.
- The team should own the architecture collaboratively and the architect must be accountable and involved.
The Fundamentals of Continuous Software DesignJeremy Miller
This document discusses principles of continuous software design, including:
- Designing incrementally and reacting to feedback rather than doing big upfront design.
- Making decisions as late as responsibly possible to have the most information.
- Prioritizing reversibility so designs can easily change.
- Using test-driven development, refactoring, and bottom-up design to improve code quality and flexibility over time.
- Constantly challenging designs through techniques like spiking and socializing ideas with others.
How contributing to Open-source made me a better DevOpsAhmed AbouZaid
How participating in Open-source made me a better DevOps
And that actually started not just as a professional system engineer, but much earlier as a normal end-user also as a power user.
This document provides information about the author and DevOps. The author is a DevOps engineer at Pluralsight who has worked in release management since 2006 and is passionate about continuous delivery. DevOps is defined as a culture of continuous improvement through automation, metrics, and sharing to connect development, testing, configuration, and operations. The document asks questions about what is automated, measured, shared, and how teams are structured in a DevOps environment.
DevOps is far more about culture and organization than it is about technology and tooling. This talk will discuss the speaker's experiences leading high-performing engineering teams at Google, eBay, and Stitch Fix, and will offer suggestions for other organizations to level up their DevOps game.
https://www.meetup.com/SV-ELC/events/240087808/
Modern software-service models take advantage of the great benefits in having the same team both build the software as well as operate it in production -- "You Build It; You Run It" is the Amazon mantra. What does this mean in practice?
Organizationally, it means small teams with well-defined areas of responsibility, directly aligned with the business. The teams are cross-functional, meaning that each team has all the skill sets it requires to do its job, while at the same time relying on other teams for supporting services, tools, and libraries.
Process-wise, it means doubling down on practices like test-driven development and continuous delivery. Using continuous delivery practices, high-performing teams can and do release their applications and services multiple times a day. This enables them to iterate rapidly, experiment courageously, and fail more quickly.
Culturally, it means end-to-end ownership. Each team owns its software end-to-end, from design to development to deployment to retirement. The same engineers who are responsible for the features are responsible for quality, performance, operations, and maintenance. This ownership puts incentives in the right place to encourage building maintainable, observable, and operable systems from the start.
All these techniques and approaches are available to everyone, and practical examples in this talk will help other organizations on their journey.
DOES15 - Randy Shoup - Ten (Hard-Won) Lessons of the DevOps TransitionGene Kim
Randy Shoup, Consulting CTO
DevOps is no longer just for Internet unicorns any more. Today many large enterprises are transitioning from the slow and siloed traditional IT approach to modern DevOps practices, and getting substantial improvements in agility, velocity, scalability, and efficiency. But this transition is not without its challenges and pitfalls, and those of us who have led this journey have the scar tissue to prove it.
A successful transition to DevOps practices ultimately involves changes to organization, to culture, and to architecture. Organizationally, we want to create multi-skilled teams with end-to-end ownership and shared on-call responsibilities. Culturally, we want to prioritize solving problems and improving the product over closing tickets. Architecturally, we want to move to an infrastructure with independently testable and deployable components.
The ten practical lessons outlined in this session synthesize the speaker’s experiences leading teams at eBay, Google, and KIXEYE, as well as from his current consulting practice.
Don't forget the people - DevOps Manchester 10th Oct 2015James Heggs
DevOps Manchester 10th Oct 2015
Stories from previous experiences of attempting to move towards a DevOps culture based around the people aspects of decision.
This document outlines a structured approach to debugging distributed systems. It begins with observing and documenting the problem. The next steps involve creating a minimal reproducer, debugging the client and server sides, and checking DNS, routing, and network connections. Traffic and messages should also be inspected. The process concludes by wrapping up findings and conducting a post-mortem analysis. Key challenges in distributed systems like concurrency, lack of a global clock, and independent failures are discussed.
Systems biology in polypharmacology: explaining and predicting drug secondary...Andrei KUCHARAVY
This document discusses using systems biology approaches to predict and explain off-target drug effects. It notes that unexpected secondary drug effects and lack of therapeutic effects are major reasons drug development fails. The document proposes using computational methods to predict all protein targets a drug may affect and using systems biology to model the consequences, including secondary effects, unexpected therapeutic effects via drug repositioning, and unexpected lack of effects. It outlines a master's project to develop models of polypharmacological drug effects by analyzing networks of drug-affected protein targets and retrieving relevant biological annotation to interpret effects.
This document provides recommendations for comfortable outfits from various stores that can be worn for activities like going to the beach, relaxing at home, playing soccer, or participating in track and field. A floral summer dress and a comfortable track outfit are highlighted as options that allow enjoyment of activities without worry.
Dokumen tersebut membahas berbagai komunitas dan kegiatan yang diikuti pelajar, seperti komunitas sahabat, acara pulang kampung, komunitas seni seperti hip hop dan film, komunitas penulis, komunitas nasyid, komunitas peduli lingkungan, kerjasama media, serta komunitas entrepreneur.
A short introduction to the more advanced python and programming in general. Intended for users that has already learned the basic coding skills but want to have a rapid tour of more in-depth capacities offered by Python and some general programming background.
Execrices are available at: https://github.com/chiffa/Intermediate_Python_programming
Graph databases in computational bioloby: case of neo4j and TitanDBAndrei KUCHARAVY
This document discusses graph databases and their use in computational biology. It introduces Neo4j and TitanDB as graph database options and describes how biological interaction networks and pathways can be modeled as graphs. Key advantages of graph databases over relational databases are also summarized, such as increased speed for graph queries and simpler programming. The document provides an overview of Neo4j and TitanDB, including their core abstractions, interfaces, and advantages/limitations for storing large biological network data. Examples are given of loading Reactome pathway data into Neo4j and performing graph queries.
This document discusses deployment orchestration using tools like Puppet, Ansible, and Jenkins. It describes setting up configuration management with Puppet, querying configuration data with PuppetDB, and using Ansible to automate and orchestrate deployments by running Puppet agent tests on nodes. The author provides an example workflow of using Jenkins for continuous integration and packaging, along with links to online material and code repositories for further details.
Dokumen tersebut mencari agen dan distributor di setiap kota untuk menjual t-shirt. Memberikan kontak Satriyo DKV14 di Jogjakarta dan nomor teleponnya. Menawarkan t-shirt sebagai media untuk promosi. Memberikan alamat kantor di Yogyakarta. Kemudian menyertakan hadis tentang pahala bagi orang yang mengajak ke petunjuk agama. Dakwah adalah pilar Islam untuk membangun dan menyebarkan ajaran Islam ke seluruh penj
This document discusses the DevOps movement and related concepts. It provides background on how development and operations teams historically worked separately ("Devs vs Ops") and the problems that caused. DevOps aims to break down barriers between teams through practices like automation, continuous integration/delivery, infrastructure as code, and collaboration between teams from the beginning of a project. The document outlines problems DevOps aims to solve and gives examples of tools and approaches for bringing development and operations cultures together.
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
Devops and Drupal focuses on the current state of devops practices among Drupal developers and system administrators. A survey of over 200 Drupal professionals found that while many are aware of devops concepts like continuous integration and deployment, few have fully implemented best practices for areas like automated testing, configuration management, and disaster recovery. Adopting a devops approach can help Drupal teams improve collaboration, deploy more frequently, and better manage systems over time.
Deploying your Drupal site, Upgrading your Drupal Site, Scaling, Clustering and Monitoring it ... all topics Developers are often not involved with ...
Devops For Drupal explains the Devops problem, to a Drupal audience .
Dev ops lessons learned - Michael CollinsDevopsdays
The document discusses lessons learned from trying to implement DevOps in a rapidly growing company. Some key lessons include: (1) being able to clearly articulate what DevOps means for both individuals and the organization; (2) trusting developers and providing them with what they need; and (3) starting DevOps efforts with a focus on development environments rather than just production. The document also emphasizes focusing on toolchains rather than individual tools, using a service delivery pipeline approach, and ensuring good communication and hiring practices.
Devops, the future is here it's not evenly distributed yetKris Buytaert
Devops, the future is here, but it is not evenly distributed. The document discusses the history and principles of devops. It summarizes that traditionally, development and operations teams had different goals and worked in silos, but devops aims to break down these barriers by advocating for automated testing, continuous integration, infrastructure as code, and cross-functional teams to improve collaboration and speed of delivery. Achieving devops culture and practices can help organizations release changes more quickly, reliably and with higher quality.
This document provides tips for growing a devops team by breaking down historical silos between development and operations. It recommends starting by analyzing pain points, creating a cross-functional team with shared goals, improving communication, getting buy-in, automating processes, measuring success and failure, and giving everyone full access and responsibilities. The overall message is that devops requires cultural and process changes, not buying products, and is a continuous improvement journey.
This was a presentation given at San Diego Python's Django Day:
http://www.meetup.com/pythonsd/events/95751792/
https://github.com/pythonsd/learning-django
There are seven things that slow your software team down. Learning to conquer each of them is the key delivering faster.
Originating in the Japanese manufacturing industry in the middle of the 20th century, the ideas behind the seven wastes are still hugely relevant to software development today. I explained each one and how it slows you down, then explained how you can defeat the seven wastes and deliver faster than ever before.
Kris Buytaert discusses the Devops movement and how bringing developers and operations teams together earlier improves systems. He advocates for automation throughout the development and deployment process, from version control and testing to configuration management, monitoring, and upgrades. Adopting a Devops culture and practices like continuous integration, delivery, and deployment can help teams deploy better systems faster at lower risk.
The document discusses the origins and key principles of DevOps. It originates from a 2009 Velocity Conference talk about Flickr's deployment practices of 10+ deploys per day through automation, shared version control, and one-step builds. The main principles discussed are CAMS - Culture, Automation, Measurement, and Sharing. Culture focuses on respect, trust, and avoiding blame. Automation, measurement, and sharing are also emphasized as important aspects of DevOps.
Agile Gurgaon 2016 | Thinking Beyond :: Marry Agile and DevOps for Phenomenal...AgileNetwork
This document discusses marrying Agile and DevOps approaches to get phenomenal results. It begins with an introduction of the author and their experience. It then poses common questions around when to adopt Agile vs DevOps and how they relate. The document outlines differences between traditional and Agile/DevOps mindsets and practices. It provides examples of lessons learned and challenges overcome during one organization's transformation journey. Finally, it discusses steps to get started with a DevOps approach and lists examples of effective DevOps practices.
Yetizen (https://www.linkedin.com/company/yetizen/about/) was a gaming incubator that existed in San Francisco, roughly between 2011 and 2015. I thought it was an interesting experiment, and was happy to give a series of talks there, and advise the portfolio companies.
This talk, from 2013, is about what's involved in being a platform vendor-- a third party whose service is relied up by applications. From the fact that your customers (application companies) don't really trust you to the fact that they make unreasonable demands to the fact that platforms and services are architected differently from applications; it's all in here.
Kris Buytaert gave a talk on DevOps at DrupalCon Munich in 2012. He discussed how the silos between development and operations created problems, and how the DevOps movement aims to break down those barriers through automation, collaboration, and continuous delivery. DevOps is not defined by specific tools but by cultural and process changes like integrating operations work into the entire software lifecycle from early on. The talk covered challenges like managing data and environments across different stages and how tools like Vagrant and configuration management can help address them.
Years of (not) learning , from devops to devoopsKris Buytaert
This document discusses the history of devops from 2009 to the present. It began as a movement in 2009 in Ghent to improve software delivery using open source tools and has since grown globally with over 250 events held. While tools have evolved from things like Puppet and Jenkins to Docker and Kubernetes, the core challenges of culture change, continuous delivery, monitoring, and cloud infrastructure remain. The document cautions that tools alone will not solve problems and that the industry focuses too much on hype and certification over meaningful change. The key takeaway is that after over 10 years, many organizations still struggle with devops principles due to cultural barriers, and the work of bridging development and operations is ongoing.
SaltConf14 - Justin Carmony, Deseret Digital Media - Teaching Devs About DevOpsSaltStack
Let's set aside the buzzwords for a moment and have an honest discussion about DevOps. There is the idea of putting more Dev into Ops, but just as crucial (if not more crucial) is getting your Devs to think more like Ops. Most developers have little to no experience dealing with production environments, and helping them add value to DevOps efforts can be difficult. This talk will cover practical ways of mentoring Devs into more DevOps skills and responsibilities. Ultimately, the goal is to help your Devs gain the skills leading to better production health, application performance and uptime. Of course, we'll also consider how SaltStack can help.
We’re all doing Agile nowadays, aren’t we? We’ll all delivering software in an Agile way. But what does that mean? Does it mean sprints and stand-ups? Kanban even? But what about Extreme Programming? If as a development team we’re not using pair programming, test driven development, continuous integration, and other XP practices, then we’re not really doing Agile software development and we may be on a march to frustration, or even failure.
I’m going to look at why the current trend of companies and projects adopting Scrum, calling themselves Agile, but not transitioning their development to XP, is a recipe for disaster. I’d like to cover the main practices of XP as well as other good practices that can really help a team deliver quality software, whether they’re doing two-week sprints, Kanban, or even Waterfall.
https://www.youtube.com/watch?v=aZgnY9fAHOA
Standing on the Shoulders of Giants: How Community Shapes Development in Elli...Derek Allard
This document discusses the process EllisLab uses to develop new features for ExpressionEngine. It begins by providing an example of how the file management feature was developed. It then explains that feature ideas often come from the EllisLab forums or blogs. New features go through a planning process using Scrum methodology before being built. This involves estimating the time needed, having daily standup meetings, and releasing in sprints. Once released, the community provides feedback on how the new feature can be improved further.
DevOpsGuys - Getting Started with DevOps - Github/Azure WebinarDevOpsGroup
DevOpsGuys - Getting Started with DevOps - Github/Azure Webinar in April 2017 that talks about the 5 key ingredients you need to kick start your DevOps Transformation
Unlocking the Secrets of Love: The Science Behind Heartfelt ConnectionsVikash Gautam
Explore the fascinating science of love and how chemistry, biology, and psychology shape our deepest connections. Discover the brain’s role in attraction, emotional bonding, and how love impacts our lives. Learn the hidden truths behind the power of love and its life-changing effects.
I moved from the Hungarian school system to an international high school in 7th grade, adapting to a new language, teaching style, and diverse cultural environment.
How to Prepare for and Survive a Power OutageBob Mayer
Every person experiences a power outage. Some more than others. They are a fact of life. How do you prepare for it? Especially an extended one? What to do? How do you stay cool or warm as needed? What gear do you need ahead of time?
It is better to be prepared ahead of time.
4. One day before release
●
“Put this code live, here's a tarball, kthxbye!”
“What dependencies has it?
Where do I put it?
What database?
Does it need to be highly available?
What traffic are you expecting?”
●
“Not much, just install it..”
“Okay :-/”
5. 10 days into operation
●
“The servers are slow!”
Why is our load so high? Why is all the memory
used?
Where does this thing write its logs?
Why is that web page generating 100 queries?
Debugging is still enabled?
Who wrote this $#!* ?!
9. It is
•
A human problem
•
A corporate culture problem
“You can’t directly change culture. But you can change
behavior, and behavior becomes culture” – Lloyd Taylor
VP Infrastructure, Ngmoco
12. Talk about goals
Stable Platform
●
New releases
No Downtime
●
New Features
Scalable Platform
●
New platforms
Non Functional Req
●
New architectures
●
Functional Req
15. Listen, analyse
●
What are devs nagging about
•
•
●
Slow builds ?
No enviroments ?
What are ops nagging about
•
•
●
Deployement proces ?
No logs ?
What is mgmt nagging about
•
Quality / Feedback ?
16. Crossfunctional Team
●
Build a project team with skills from all over
•
Development
•
Continuous Integration
•
Testing
•
Infrastructure (HA/ Scale/ Performance)
•
Deployment
•
Measurement
●
Seat them together !
●
Goal = Help improve the business
18. Improve Communication
●
Chatrooms (being online = being available)
•
Topic
•
Virtual watercooler
•
ChatOps
●
Virtual and physical standups (hangout / jabber)
●
Transfer knowledge
●
Not only inside the team