There has been a lot of hullabaloo over the past few years around a concept called “DevOps.” The idea is that we need to break down the barriers between development and operations teams, and treat infrastructure as code, in order to move towards better software, more reliable and scalable systems, and continuous deployment.
For some of us who have been around a while, this is just a new label for something we’ve always done.
They say those that don’t learn from history are destined to repeat it. In this talk, we will look back at how the DevOps movement evolved, what it advocates, what it doesn’t address, and what you should take away from the movement that will help you in your professional life. We will also use this opportunity to look back over the past decade or two of system administration, and see how our challenges have changed, and how they have remained the same.
Monolith to serverless service based architectures in the enterpriseSameh Deabes
Brief introductions about the following topics and how they relate to each other: SOA, ESB, Cloud, Cloud Native Architecture, Microservices, Multigrained Services, NoESB, API-First, Full Lifecycle API Management, etc.
The session will focus mainly on microservices pitfalls and what to do about it.
Agile and Automation have been growing up together over the past decade. Neither practice nor toolset evolves in a vacuum. Rather, they inform each-other.
This presentation looks at this history, with an eye towards where the current trends are pushing us.
Agile methods and safety critical software - Peter GardnerAdaCore
This talk surveys Agile methods and formulates a list of features that occur in these methods, then considers whether each of the features can be applied in the field of safety-critical software development. The talk concludes that almost all of the features of Agile methods are applicable to safety-critical software but that existing standards are a problem for Agiles de-emphasis of design and documentation. The talk will also look for quantitative evidence in the published literature for the benefits of Agile methods in software development in general, and surveys various published opinions on Agiles application to safety-critical software development.
La Continuous Delivery è una metodologia all’avanguardia nei processi di sviluppo software. Tuttavia, l’elevato numero di incidenti e di istanze di inattività del database sono causate da processi non aggiornati, dalla riscrittura del codice e da altri disturbi del database. Attraverso l’automazione del Database è possibile evitare questi disturbi ed errori.
Visualizza le slide del webinar.
Nrb Mainframe Day - NRB's Agile Software Factory In support of Application In...NRB
Benoit Ebner, mainframe systems engineer at NRB, takes us during this presentation on a tour alongside the battery of selected tools and applications, the NRB mainframe teams use while modernising a customer’s mainframe application environment.
Monolith to serverless service based architectures in the enterpriseSameh Deabes
Brief introductions about the following topics and how they relate to each other: SOA, ESB, Cloud, Cloud Native Architecture, Microservices, Multigrained Services, NoESB, API-First, Full Lifecycle API Management, etc.
The session will focus mainly on microservices pitfalls and what to do about it.
Agile and Automation have been growing up together over the past decade. Neither practice nor toolset evolves in a vacuum. Rather, they inform each-other.
This presentation looks at this history, with an eye towards where the current trends are pushing us.
Agile methods and safety critical software - Peter GardnerAdaCore
This talk surveys Agile methods and formulates a list of features that occur in these methods, then considers whether each of the features can be applied in the field of safety-critical software development. The talk concludes that almost all of the features of Agile methods are applicable to safety-critical software but that existing standards are a problem for Agiles de-emphasis of design and documentation. The talk will also look for quantitative evidence in the published literature for the benefits of Agile methods in software development in general, and surveys various published opinions on Agiles application to safety-critical software development.
La Continuous Delivery è una metodologia all’avanguardia nei processi di sviluppo software. Tuttavia, l’elevato numero di incidenti e di istanze di inattività del database sono causate da processi non aggiornati, dalla riscrittura del codice e da altri disturbi del database. Attraverso l’automazione del Database è possibile evitare questi disturbi ed errori.
Visualizza le slide del webinar.
Nrb Mainframe Day - NRB's Agile Software Factory In support of Application In...NRB
Benoit Ebner, mainframe systems engineer at NRB, takes us during this presentation on a tour alongside the battery of selected tools and applications, the NRB mainframe teams use while modernising a customer’s mainframe application environment.
How Do We Better Sell DevOps? - PuppetConf 2013Puppet
"How Do We Better Sell DevOps?" by Gene Kim, Author of "The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win", IT Revolution Press.
Presentation Overview: In this talk, Gene shares his top lessons learned over my years studying high performing IT organizations on how to sell the value of DevOps, and help other stakeholders and executives have their own a-ha moments. He talks about specific stories about the circumstances that led to these a-ha moments, how they created DevOps champions in surprising places (e.g., Development, CTOs, Product Management, UX, Infosec) in organizations you'll recognize, and how they enabled implementing DevOps patterns that had awesome results.
Speaker Bio: Gene is a multiple award winning CTO, researcher and author. He was founder and CTO of Tripwire for 13 years. He has written three books, including “The Visible Ops Handbook” and “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win." Gene is a huge fan of IT operations, and how it can enable developers to maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He has worked with some of the top Internet companies on improving deployment flow and increasing the rigor around IT operational processes. In 2007, ComputerWorld added Gene to the “40 Innovative IT People Under The Age Of 40” list.
SDLC is a framework defining tasks performed at each step in the software or system development process. It aims to produce high quality system that meets or exceeds customer expectations, work effectively and efficiently in the current and planned information technology infrastructure, and is inexpensive to maintain and cost effective to enhance.
This presentation includes different stages of Software Deveolopment.
Measure and Accelerate Your Software DeliveryAnand Chauhan
Many companies adopt the DevOps practices, but struggle to realize the impact the DevOps investment is making to improve software delivery. Disconnected teams, tools and increasing complexity leads to no visibility into how and where to optimize the process, deliver value to customers and maximize return on that investment. The session covers industry trends, critical need for measurement and touches on CloudBees DevOptics solution purpose built to provide immediate transparency you need to measure, optimize and improve your software delivery process.
"My App has Fallen and Can't Get Up," GE Digital at FutureStack17 NYCNew Relic
Hear how GE Digital improves operational efficiency.
Be sure to subscribe and follow New Relic at:
https://twitter.com/NewRelic
https://www.facebook.com/NewRelic
https://www.youtube.com/NewRelicInc
This session is an overview on what DevOps is (to me) and how it impacts traditional organizations the most. DevOps is way more than just continuous delivery! From an Agile (synergetic) mindset, DevOps takes a step beyond and focusses on automation, collaboration and learning. Apart from that I also look forward to what oppurtunities lie ahead when implementing DevOps.
On March 2nd I presented this DevOps Unraveled session for abt 40 IT-managers at business university Nyenrode. This was part of the Masterclass Agile management
(Dutch website http://www.executiveeducation.nl/open-programmas/programmadetails/masterclass-agile-management/sectie/introductie.html ).
2012 Velocity London: DevOps Patterns DistilledGene Kim
2012 Velocity London,
Presentation by Patrick Debois (@patrickdebois), Damon Edwards (@damonedwards), Gene Kim (@realgenekim), John Willis (@botchagalupe)
How Microsoft ALM Tools Can Improve Your Bottom LineImaginet
Improved efficiencies, enhanced productivity, reduction of wasted time and effort, and improved team collaboration. Each of these benefits that result from adopting a successful ALM strategy will all help your bottom line. Come find out how at this free webinar!
Casestudy: Continuously Delivering Fitness with Redgate DLMRed Gate Software
Presentation at SQL in The city 2016 by Jon Forster and James Smith.
Fitness First is the largest privately owned health club group in the world. It consists of more than 360 Fitness First clubs worldwide reaching just over 927,000 members in 16 countries. DevOpsGuys have transformed the way that Fitness First deliver changes to their core club management systems, through Continuous Delivery and DevOps principles, and building quality into the process was a primary concern.
In this talk, DevOpsGuys will illustrate how the Redgate DLM toolset has been successfully deployed to transform integration and regression testing of fast flowing changes across 16 countries, increasing visibility and creating a robust process.
The International Journal of Engineering & Science is aimed at providing a platform for researchers, engineers, scientists, or educators to publish their original research results, to exchange new ideas, to disseminate information in innovative designs, engineering experiences and technological skills. It is also the Journal's objective to promote engineering and technology education. All papers submitted to the Journal will be blind peer-reviewed. Only original articles will be published.
The papers for publication in The International Journal of Engineering& Science are selected through rigorous peer reviews to ensure originality, timeliness, relevance, and readability.
How Do We Better Sell DevOps? - PuppetConf 2013Puppet
"How Do We Better Sell DevOps?" by Gene Kim, Author of "The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win", IT Revolution Press.
Presentation Overview: In this talk, Gene shares his top lessons learned over my years studying high performing IT organizations on how to sell the value of DevOps, and help other stakeholders and executives have their own a-ha moments. He talks about specific stories about the circumstances that led to these a-ha moments, how they created DevOps champions in surprising places (e.g., Development, CTOs, Product Management, UX, Infosec) in organizations you'll recognize, and how they enabled implementing DevOps patterns that had awesome results.
Speaker Bio: Gene is a multiple award winning CTO, researcher and author. He was founder and CTO of Tripwire for 13 years. He has written three books, including “The Visible Ops Handbook” and “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win." Gene is a huge fan of IT operations, and how it can enable developers to maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He has worked with some of the top Internet companies on improving deployment flow and increasing the rigor around IT operational processes. In 2007, ComputerWorld added Gene to the “40 Innovative IT People Under The Age Of 40” list.
SDLC is a framework defining tasks performed at each step in the software or system development process. It aims to produce high quality system that meets or exceeds customer expectations, work effectively and efficiently in the current and planned information technology infrastructure, and is inexpensive to maintain and cost effective to enhance.
This presentation includes different stages of Software Deveolopment.
Measure and Accelerate Your Software DeliveryAnand Chauhan
Many companies adopt the DevOps practices, but struggle to realize the impact the DevOps investment is making to improve software delivery. Disconnected teams, tools and increasing complexity leads to no visibility into how and where to optimize the process, deliver value to customers and maximize return on that investment. The session covers industry trends, critical need for measurement and touches on CloudBees DevOptics solution purpose built to provide immediate transparency you need to measure, optimize and improve your software delivery process.
"My App has Fallen and Can't Get Up," GE Digital at FutureStack17 NYCNew Relic
Hear how GE Digital improves operational efficiency.
Be sure to subscribe and follow New Relic at:
https://twitter.com/NewRelic
https://www.facebook.com/NewRelic
https://www.youtube.com/NewRelicInc
This session is an overview on what DevOps is (to me) and how it impacts traditional organizations the most. DevOps is way more than just continuous delivery! From an Agile (synergetic) mindset, DevOps takes a step beyond and focusses on automation, collaboration and learning. Apart from that I also look forward to what oppurtunities lie ahead when implementing DevOps.
On March 2nd I presented this DevOps Unraveled session for abt 40 IT-managers at business university Nyenrode. This was part of the Masterclass Agile management
(Dutch website http://www.executiveeducation.nl/open-programmas/programmadetails/masterclass-agile-management/sectie/introductie.html ).
2012 Velocity London: DevOps Patterns DistilledGene Kim
2012 Velocity London,
Presentation by Patrick Debois (@patrickdebois), Damon Edwards (@damonedwards), Gene Kim (@realgenekim), John Willis (@botchagalupe)
How Microsoft ALM Tools Can Improve Your Bottom LineImaginet
Improved efficiencies, enhanced productivity, reduction of wasted time and effort, and improved team collaboration. Each of these benefits that result from adopting a successful ALM strategy will all help your bottom line. Come find out how at this free webinar!
Casestudy: Continuously Delivering Fitness with Redgate DLMRed Gate Software
Presentation at SQL in The city 2016 by Jon Forster and James Smith.
Fitness First is the largest privately owned health club group in the world. It consists of more than 360 Fitness First clubs worldwide reaching just over 927,000 members in 16 countries. DevOpsGuys have transformed the way that Fitness First deliver changes to their core club management systems, through Continuous Delivery and DevOps principles, and building quality into the process was a primary concern.
In this talk, DevOpsGuys will illustrate how the Redgate DLM toolset has been successfully deployed to transform integration and regression testing of fast flowing changes across 16 countries, increasing visibility and creating a robust process.
The International Journal of Engineering & Science is aimed at providing a platform for researchers, engineers, scientists, or educators to publish their original research results, to exchange new ideas, to disseminate information in innovative designs, engineering experiences and technological skills. It is also the Journal's objective to promote engineering and technology education. All papers submitted to the Journal will be blind peer-reviewed. Only original articles will be published.
The papers for publication in The International Journal of Engineering& Science are selected through rigorous peer reviews to ensure originality, timeliness, relevance, and readability.
Les Frost, Senior Technical Architect - Capgemini
The DevOps movement is establishing itself within many organisations. Many people are asking “How do I do DevOps?” or “Can you tell me the recommended DevOps tool stack?”
By the time many organisations adopt DevOps, will the rise of serverless computing such as AWS Lambda mean that they are already out-of-date? The debate is on-going as to whether serverless computing (i.e. outsourcing the management of servers so you can focus on building that critical business functionality), will move organisations from DevOps to NoOps. AWS Lambda enables users to run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of application or back end service – all with zero administration. Just upload your code and Lambda takes care of everything required to run and scale your code with high availability. You can set up your
code to automatically trigger from other AWS services or call it directly from any web or mobile app.
Slides of the "In The Brains" talk given at SkillsMatter on the 28th of October 2014.
The use of test doubles in testing at various levels has become commonplace, however, correct usage is far less common. In this talk Giovanni Asproni shows the most common and serious mistakes he's seen in practice and he'll give some hints on how to avoid them (or fix them in existing code).
WANTED: Seeking Single Agile Knowledge Development Tool-setBrad Appleton
by Brad Appleton,
Presented August 2009 at at Agile 2009 Conference; Chicago, IL USA
What tools and capabilities are necessary to apply Agile development concepts+practices (such as refactoring, TDD, CI, etc.) to all knowledge-artifacts? (not just source-code).
How do you deliver your applications to the cloud?Michael Elder
Cloud, Docker, Bluemix, and DevOps. You feel the pressure of a hyper-competitive marketplace, and you want to win. Your goal is to deliver apps to that make your users happy and excited about your brand and products, but how do you do that? In this talk, we'll provide a technical briefing for how you can use a DevOps-enabled toolchain to deliver your apps with speed and reliability to the cloud platform of your choice. We'll review how UrbanCode Deploy can deliver your applications to OpenStack, IBM SoftLayer, Amazon, and VMWare with a consistent and portable Infrastructure-as-a-Service approach; or how you can use Containers and Cloud Foundry for app tiers that change potentially many times a day. Come take a look and ask your questions, and hopefully come away with a game plan to improve your delivery process today.
In Data Engineer’s Lunch #68, Will Angel, Technical Product Manager at Caribou Financial, will provide an introduction to DevOps practices and tooling including testing, deployment automation, logging, monitoring, and DevOps principles. Additionally, we will discuss some of the ways that DevOps for data engineering is different from conventional application development.
Accompanying Blog: Coming Soon!
Accompanying YouTube: https://youtu.be/eBtrOv_qLHQ
Sign Up For Our Newsletter: http://eepurl.com/grdMkn
Join Data Engineer’s Lunch Weekly at 12 PM EST Every Monday:
https://www.meetup.com/Data-Wranglers-DC/events/
Cassandra.Link:
https://cassandra.link/
Follow Us and Reach Us At:
Anant:
https://www.anant.us/
Awesome Cassandra:
https://github.com/Anant/awesome-cassandra
Email:
solutions@anant.us
LinkedIn:
https://www.linkedin.com/company/anant/
Twitter:
https://twitter.com/anantcorp
Eventbrite:
https://www.eventbrite.com/o/anant-1072927283
Facebook:
https://www.facebook.com/AnantCorp/
Join The Anant Team:
https://www.careers.anant.us
Presentazione dello speech tenuto da Carmine Spagnuolo (Postdoctoral Research Fellow - Università degli Studi di Salerno/ ACT OR) dal titolo "Technology insights: Decision Science Platform", durante il Decision Science Forum 2019, il più importante evento italiano sulla Scienza delle Decisioni.
Performance is a key aspect when developing an application, but for developers, production performance usually is a black box. When production problems arise, a lack of insight into log files and performance metrics forces us to reproduce issues locally before we can start to tackle the root cause. Using real world examples, we show how a unified performance management platform helps teams across the lifecycle to monitor applications, detect problems early on, and collect data that enables developers to efficiently solve problems.
Manual application deployment processes tend to be error prone and inefficient and can make achieving consistent deployments seem impossible.
There is good news. You don’t need to choose between a careful, rigorous approach and a speedy but haphazard one. It’s possible to implement an automated deployment solution that provides consistency and audit trails while improving productivity for your release engineers, operations personnel, and testers. See how!
Learn more about UrbanCode: http://ibm.biz/learnurbancode
DevOps for absolute beginners (2022 edition)Ahmed Misbah
Are you planning to pursue a career in DevOps?
Already working with DevOps but want to know what’s new in 2022?
This session is for you!
Join us in the 2022 edition of “DevOps for absolute beginners” session, where you will learn all about DevOps from the perspective of People, Process, and Technology. We will be talking about topics like Automation, Continous Integration, Continous Delivery, Infrastructure as Code, etc. We will also be talking about the latest trends in DevOps, including Chaos Engineering, MLOps, and eBPF.
The session will conclude with great bonus material for software professional enthusiastic about DevOps, one of them being a carefully crafted learning path for DevOps from years of experience in the industry. Don’t miss out on the rest of the material.
The talk is about a real experience of organization transformation with 15 years old legacy monolith project into DevOps oriented, microservice-based modern company. On our way, we have grown from 40 to 80 engineers for the last two years. We have x20 increased delivery of the old main project and implemented CD for projects and processes.
fter Completing this chapter you should be able to:
understand what software engineering is and why it is important;
understand the concepts of software processes and software process models;
Compare and contrast a variety of models
understand some ethical and professional issues that are important for software engineers;
Bridging the Gap: from Data Science to ProductionFlorian Wilhelm
A recent but quite common observation in industry is that although there is an overall high adoption of data science, many companies struggle to get it into production. Huge teams of well-payed data scientists often present one fancy model after the other to their managers but their proof of concepts never manifest into something business relevant. The frustration grows on both sides, managers and data scientists.
In my talk I elaborate on the many reasons why data science to production is such a hard nut to crack. I start with a taxonomy of data use cases in order to easier assess technical requirements. Based thereon, my focus lies on overcoming the two-language-problem which is Python/R loved by data scientists vs. the enterprise-established Java/Scala. From my project experiences I present three different solutions, namely 1) migrating to a single language, 2) reimplementation and 3) usage of a framework. The advantages and disadvantages of each approach is presented and general advices based on the introduced taxonomy is given.
Additionally, my talk also addresses organisational as well as problems in quality assurance and deployment. Best practices and further references are presented on a high-level in order to cover all facets of data science to production.
With my talk I hope to convey the message that breakdowns on the road from data science to production are rather the rule than the exception, so you are not alone. At the end of my talk, you will have a better understanding of why your team and you are struggling and what to do about it.
What’s New with NGINX Controller Load Balancing Module 2.0?NGINX, Inc.
On-Demand Link: https://www.nginx.com/resources/webinars/new-nginx-controller-load-balancing-module-2-0/
Speaker:
Karthik Krishnaswamy
Sr Product Marketing Manager
NGINX, Inc.
About the webinar
Achieving consistency in application performance begins with a consistent load balancing configuration. NGINX Controller Load Balancing Module 2.0 introduces a policy-driven approach to configuration management resulting in consistent configuration across multiple NGINX Plus instances. This can be achieved with the push of a button, saving time and effort for I&O teams. We will also showcase NGINX Controller’s integration with ServiceNow which seamlessly blends into your IT service management workflows.
The webinar includes a live demo of the Load Balancing Module in action.
Continuous Performance Testing and Monitoring in Agile DevelopmentDynatrace
Continuous Performance Testing and Monitoring in Agile Development
Continuous Performance testing and monitoring is the best way to ensure application performance with quicker development cycles. Balancing agile and DevOps velocity with the need for ongoing performance testing and monitoring is essential. We call it Continuous Performance Validation.
In this webinar, we will show how you can get performance guidance and metrics throughout development, making sure apps perform well from inception to production and beyond.
In this webinar you will learn:
• How to automate performance testing and which tools you need to be successful
• How to use APM during load and performance testing
• How to create a continuous performance validation strategy from Dev to QA and Ops
• Ways teams can collaborate to ensure top application performance
Similar to Fifteen Years of DevOps -- LISA 2012 keynote (20)
APNIC Foundation, presented by Ellisha Heppner at the PNG DNS Forum 2024APNIC
Ellisha Heppner, Grant Management Lead, presented an update on APNIC Foundation to the PNG DNS Forum held from 6 to 10 May, 2024 in Port Moresby, Papua New Guinea.
Bridging the Digital Gap Brad Spiegel Macon, GA Initiative.pptxBrad Spiegel Macon GA
Brad Spiegel Macon GA’s journey exemplifies the profound impact that one individual can have on their community. Through his unwavering dedication to digital inclusion, he’s not only bridging the gap in Macon but also setting an example for others to follow.
1.Wireless Communication System_Wireless communication is a broad term that i...JeyaPerumal1
Wireless communication involves the transmission of information over a distance without the help of wires, cables or any other forms of electrical conductors.
Wireless communication is a broad term that incorporates all procedures and forms of connecting and communicating between two or more devices using a wireless signal through wireless communication technologies and devices.
Features of Wireless Communication
The evolution of wireless technology has brought many advancements with its effective features.
The transmitted distance can be anywhere between a few meters (for example, a television's remote control) and thousands of kilometers (for example, radio communication).
Wireless communication can be used for cellular telephony, wireless access to the internet, wireless home networking, and so on.
Multi-cluster Kubernetes Networking- Patterns, Projects and GuidelinesSanjeev Rampal
Talk presented at Kubernetes Community Day, New York, May 2024.
Technical summary of Multi-Cluster Kubernetes Networking architectures with focus on 4 key topics.
1) Key patterns for Multi-cluster architectures
2) Architectural comparison of several OSS/ CNCF projects to address these patterns
3) Evolution trends for the APIs of these projects
4) Some design recommendations & guidelines for adopting/ deploying these solutions.
# Internet Security: Safeguarding Your Digital World
In the contemporary digital age, the internet is a cornerstone of our daily lives. It connects us to vast amounts of information, provides platforms for communication, enables commerce, and offers endless entertainment. However, with these conveniences come significant security challenges. Internet security is essential to protect our digital identities, sensitive data, and overall online experience. This comprehensive guide explores the multifaceted world of internet security, providing insights into its importance, common threats, and effective strategies to safeguard your digital world.
## Understanding Internet Security
Internet security encompasses the measures and protocols used to protect information, devices, and networks from unauthorized access, attacks, and damage. It involves a wide range of practices designed to safeguard data confidentiality, integrity, and availability. Effective internet security is crucial for individuals, businesses, and governments alike, as cyber threats continue to evolve in complexity and scale.
### Key Components of Internet Security
1. **Confidentiality**: Ensuring that information is accessible only to those authorized to access it.
2. **Integrity**: Protecting information from being altered or tampered with by unauthorized parties.
3. **Availability**: Ensuring that authorized users have reliable access to information and resources when needed.
## Common Internet Security Threats
Cyber threats are numerous and constantly evolving. Understanding these threats is the first step in protecting against them. Some of the most common internet security threats include:
### Malware
Malware, or malicious software, is designed to harm, exploit, or otherwise compromise a device, network, or service. Common types of malware include:
- **Viruses**: Programs that attach themselves to legitimate software and replicate, spreading to other programs and files.
- **Worms**: Standalone malware that replicates itself to spread to other computers.
- **Trojan Horses**: Malicious software disguised as legitimate software.
- **Ransomware**: Malware that encrypts a user's files and demands a ransom for the decryption key.
- **Spyware**: Software that secretly monitors and collects user information.
### Phishing
Phishing is a social engineering attack that aims to steal sensitive information such as usernames, passwords, and credit card details. Attackers often masquerade as trusted entities in email or other communication channels, tricking victims into providing their information.
### Man-in-the-Middle (MitM) Attacks
MitM attacks occur when an attacker intercepts and potentially alters communication between two parties without their knowledge. This can lead to the unauthorized acquisition of sensitive information.
### Denial-of-Service (DoS) and Distributed Denial-of-Service (DDoS) Attacks
1. 15 Years of DevOps
1
Geoff Halprin
The SysAdmin Group
geoff@sysadmin.com.au
LISA 2012 Conference
San Diego, December 2012
(C) Copyright 2012, Geoff Halprin.
2. We will all look a lot more like Google over
the next decade.
!
Software Development has changed
forever.
!
Now it’s System Administration’s turn.
2
11. The Root Causes
The Big M Methodologies
‣ Human Resources
• They eschewed the difference in productivity of
programmers.
‣ Wrong Model
• All the creativity is at the beginning, the rest is just
building.
‣ High Risk, Hence High Formality
• Such large investments require significant controls to
(attempt to) ensure that the value is delivered.
11
12. Software was no longer delivered monolithically
The Environment Was Changing, Too
‣ Smaller, Interconnected Systems
• 2-Tier (Client/Server) networking model (RPC)
- Thick clients
• Enterprise Service Bus
‣ Software Design Patterns (1994)
‣ The Web
• No longer creating long distribution chains for physical
media.
• 3-tier architecture (Model, View, Controller)
12
13. Putting the SDLC on its head
13
The Agile Manifesto (2001)
We Favour:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
14. We follow these principles:
Agile Principles
‣ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
‣ Welcome changing requirements, even late in development. Agile processes harness change for the customer's
competitive advantage.
‣ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter
timescale.
‣ Business people and developers must work together daily throughout the project.
‣ Build projects around motivated individuals. Give them the environment and support they need, and trust them to get
the job done.
‣ The most efficient and effective method of conveying information to and within a development team is face-to-face
conversation.
‣ Working software is the primary measure of progress.
‣ Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a
constant pace indefinitely.
‣ Continuous attention to technical excellence and good design enhances agility.
‣ Simplicity--the art of maximising the amount of work not done--is essential.
‣ The best architectures, requirements, and designs emerge from self-organising teams.
‣ At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour
accordingly.
14
16. Business Value Faster and More Reliably
Agile Versus Waterfall
16
Project
Release 1 Release 3
Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5
Release 2
Agile Project
Value realised over time
2 weeks
Project
Solution
Definition
Design & Build
RDD
Waterfall-based Project
SAD DDD Code
Test
Release
Value realised over time
2 years?
17. A rivalry with much history
‣ The First Wrong Assumption
• That Production looks just like Development.
‣ The Second Wrong Assumption
• The Production looks just like a vanilla vendor install.
‣ The Third Wrong Assumption
• That the Production environment is static.
17
Dev vs Ops, Part 1
18. The Methodologies Assumed We Would Talk
How Did it Get This Way?
‣ ISO/IEC-12207:1995 SDLC
• Does not mention system operations at all
‣ IEEE 1074-1991
• Does not mention system operations at all
‣ Rational Unified Process (2003)
• 3½ whole pages on deployment!
‣ They all assume that the programmers will deal with the operational
aspects of the system as part of their normal SDLC activities.
• This has been proven to be a bad assumption!
18
19. All These Methodologies Assume We Are “In The Room”
‣ This same mistake in thinking can derail Agile software
development projects
• If your company is doing Agile software
development, are Operations participating?
• Are you placing “non-functional” stories in the
backlog, or is the only ‘customer’ the one wanting
new features?
‣ DevOps puts an Ops person in the room
• That doesn’t guarantee the right stories are placed
on the project backlog.
19
The Great Assumption
20. Making a System Administrator’s Life Less Stressful
20
Serviceability Criteria
‣ Each production environment is unique.
• Applications must adapt to their environment.
‣ The environment that an application is deployed into is never static
across its life.
• Applications must cope with the world changing around them.
‣ These goals are achieved by the application exposing the necessary
controls to the system administrator to provide for maintenance.
‣ This is actually a definable set of criteria that, when met, make a
system maintainable across its life.
• We will call these the serviceability criteria.
21. aka “Non-Functional Requirements”
21
Operational Requirements
‣ Serviceability Criteria (Scope: Global)
• Wouldn’t it be nice if all applications exposed these controls in a
uniform manner?
‣ Standard Operating Environment (Scope: Local)
• All applications within a particular environment share these. e.g.
naming conventions, filesystem layout standards.
‣ Application Non-Functional Requirements (Scope: Application)
• These are unique to each application. e.g. Application performance
targets. Data storage requirements.
22. As an industry, we have left each individual sysadmin to
fight for themselves (and repeat the same mistakes).
!
We need to do better.
22
23. One Last Thing...
‣ All programming projects require the basics to be
correct:
• Software Change Management
- aka Change Control
• Software Configuration Management
- aka Version Control
• Software Build and Release Management
23
The Grammar of Programming
27. An Apology
The following history is highly subjective and superficial.
It ignores by omission the incredibly important
contributions of a great many people.
This was not intentional.
27
30. You are in a maze of twisty passages, all different
The Age of the Pioneer
30
‣ Large Systems
‣ Many Networking Variants
• TCP/IP, SNA, X.25, Token Ring, DECnet, Netware
‣ Bespoke Configurations
‣ Vertical Scaling
‣ Everyone had a Unix variant
31. A well-kept secret!
What’s a System Administrator?
31
‣ LISA Conference: 1986
• 100 users or over 1GB of storage
‣ SAGE: 1992 (SAGE-AU: 1993)
• Earlier: Sun User Group, etc.
‣ What’s in a name?
• System Programmer, System Administrator, Network
Administrator, Network Engineer
• Officially: Programmer, Research Scientist, ...
32. LISA plays a key role in bringing thought leaders together
The Profession is Developing
‣ SA-CMM (1993)
‣ SAGE Job Descriptions Booklet (1993)
‣ Formal courses in SysAdmin at CQU (Aus) and U. Oslo
32
33. But TCP/IP is here to stay
The Network Isn’t The Computer
33
‣ The Internet
• TCP/IP becomes the standard network.
‣ Custom IT Solutions
• Everyone is special. Every solution unique.
‣ Tools begin to emerge:
• sudo (1980), top (1984), rdist (1986), perl 4.036 (1993),
cfengine (1993), mrtg (1995), ssh (1995), rsync (1996)
34. Before ITIL, there was SA-BOK
34
The SA-BOK
Network
Management
Facilities
Management
Server
Management
Software
Management
Data
Management
To Organise
Data
Security
Business
Continuity
Planning
To Protect
Performance
Management
Process
Automation
To Optimise
Capacity
Planning
Technology
Planning
To Plan
Service Management
Problem
Management
Production
Management
Asset
Management
Change
Management
To Control
35. With great power comes great responsibility
The Rise of The Web
35
‣ The Emergence of The Web
• Thin clients!
‣ Three Tier Infrastructure Model (Web-App-DB)
• Physical Servers Rule
‣ Linux at the Edge; Solaris at the Core
36. Penguin rising
The Commoditisation of IT
36
‣ Commodity Hardware
• Sun, IBM, Intel still battling for the enterprise.
• Intel/Linux has won the startups.
‣ The Rise of Virtualisation
• VMware and Linux drive adoption of x86 architecture.
37. Nothing will ever be the same again
The Emergence of the Cloud
‣ The Wars are over: Linux, x86, VMs.
• Amazon Web Services. Infrastructure on demand.
‣ The Rise of the API
• Infrastructure as code.
‣ Automation driven by scale
• The WebOps Movement.
• The DevOps Movement.
‣ What’s in a name (part 2)?
• SRE, Web Ops, DevOps...
37
41. The same way that failure of Waterfall drove
developers to change the way we developed
software, Cloud-based sites and the need for
rapidly provisioned, highly scalable
infrastructure drove the way we managed
infrastructure.
41
42. DevOps is to System Administration what
Agile is to Software Development
‣ Culture and Attitude
• First and foremost, DevOps is about creating a
collaborative environment between Dev and Ops,
integrating the teams as much as possible.
‣ Practices and Processes
• Automate as much as possible.
‣ Technology and Tools
• Old and New tools to support the effort.
42
What is DevOps?
43. It all starts by sitting on the same side of the table
DevOps Culture
‣ The simple act of colocating Dev and Ops people is the
single, largest step.
• Visibility of each others work through Kanban walls.
• Shared food and discussions.
• Cross-over of teams.
43
44. Some common DevOps practices
DevOps Practices
‣ Developer Behaviour Changes
• Infrastructure as Code
• Continuous Integration
• Production Support (carrying a pager!)
‣ SysAdmin Behaviour Changes
• Embedded with Dev teams
• Kanban walls for Ops
44
45. Visibility is the first step to collaboration
Kanban Walls for Ops
45
Backlog Ready Active Review Done
Express
46. So many (these are just a few)
DevOps Tools
‣ Configuration Management
• Puppet, Chef, Babushka, cfengine
‣ Software Change Management (Version Control)
• Github
‣ Continuous Integration
• Jenkins, Capistrano
‣ Testing
• Rails, Cucumber, Vagrant
46
47. Infrastructure in the Cloud
And Frameworks
‣ Commercial
• Amazon Web Services
• VMware Dynamic Ops, BMC CLM
‣ Open Source
• Open Stack, CloudForms, Eucalyptus, Open Nebula,
Open Cloud Framework,
• Cloud Foundry, AppFog, Heroku, OpenShift
‣ Standards
• ???
47
48. Adapting Agile tools to DevOps
Cucumber
# language: en!
Feature: Addition!
In order to avoid silly mistakes!
As a math idiot !
I want to be told the sum of two numbers!
!
Scenario Outline: Add two numbers!
Given I have entered <input_1> into the calculator!
And I have entered <input_2> into the calculator!
When I press <button>!
Then the result should be <output> on the screen!
!
Examples:!
| input_1 | input_2 | button | output |!
| 20 | 30 | add | 50 |!
| 2 | 5 | add | 7 |!
| 0 | 40 | add | 40 |
48
49. Test-Driven System Administration
Babushka
dep ‘ruby 1.9.2 in use’ do {!
!
met? {!
shell(‘ruby -version’)[‘ruby 1.9.2 p0’]!
}!
meet {!
shell(‘rvm use 1.9.2’)!
}!
!
end!
!
!
!
Idempotent Scripting!
49
50. Breaks down the silos
What DevOps Does
‣ Ops are now “in the room” with the Dev team.
• Dev do after hours support!
• Dev now build more maintainable code.
‣ An end-to-end system view
• Dev now see (and respond to) the problems their code
causes across the entire lifecycle.
‣ Configuration Management is automated.
‣ Change Management is automated.
‣ Continuous Integration and Release
50
51. Keeping the Code Clean
Continuous Integration and Release
‣ Continuous Integration is a Development Team Practice
• It requires well-behaved developers and a clean code
base.
‣ Continuous Release is a DevOps Practice
• It requires a well-defined (automated) release
procedure.
• It requires well-defined target infrastructure.
51
53. Fully cooked...
What DevOps Isn’t
‣ A silver bullet
• Systems still break. Patches still need to be applied.
• Not all products fit a pure DevOps model.
‣ Complete or holistic
• ITIL? SA-BOK? Normal lifecycle?
‣ Highly scalable into traditional enterprise environments
• Agile started in small teams. It took a while to learn how to
scale it.
• DevOps has started with highly specialised applications,
developed to leverage the DevOps model.
53
54. DevOps sees the vertical world of an application
Problems DevOps Doesn’t Solve
‣ Serviceability Criteria
‣ Technical Debt / Shoemaker Projects
‣ Service Monitoring
‣ The Rest of the Ops Lifecycle
‣ Professional Ethics, Training, etc.
54
55. Does DevOps Fit the Enterprise?
Web Ops versus Enterprise Ops
‣ You can’t just throw away infrastructure
‣ Vertically scaled apps
‣ Enterprise Change Management
‣ Poorly behaving vendors
55
56. Vendors have been writing bad software for a very long
time...
Badly Written Software
‣ 1994: No, you can't have root (Craig Bishop)
‣ 1995: Guidelines for software developers (Geoff Halprin)
‣ 2001: The problem with developers (Geoff Halprin)
‣ 2005: Software release engineering (Geoff Halprin and
Lee Damon)
56
63. A definition
System Administration
‣ To maintain the availability and integrity of computing
resources
‣ To support and encourage the effective use of those
resources
63
64. To make ourselves redundant
Our Motivation
‣ People don't like doing work
‣ Lazy people invent ways to
avoid work
‣ Therefore, all progress is
made by lazy people
64
65. Making Ourselves Redundant
‣ Strategy 1: Consistency
• More consistency = reduced effort across a fleet
‣ Strategy 2: Autonomous Systems
• The more they look after themselves, the less for us to
do!
‣ Strategy 3: Working on the Right Problems!
• Automate the tedium.
• Capture your expertise.
65
66. Working on the right problem
Changing System Files
‣ Our job should not be a memory test
‣ We should concentrate on where the best payoff is
‣ Why do I have to remember which signal to send to
which process for each configuration file?
• Or which ones are binary and need a different editor?
66
67. Why not edit all files the same way?
Change
67
Checko
ut
Edit
Validate
CheckinCommit
# change /etc/passwd
!
/etc/.change:
Default:
checkout rcs co %%
checkin rcs ci %%
edit vi %%
end
!
passwd:
edit: vipw
end
!
inetd.conf:
validate: v_etc_inetd
commit: kill -HUP `...`
68. Moving from managing a single host to managing a fleet
Structured Systems Administration
‣ Treat the whole network as a single system; not as a
large number of independent hosts.
‣ Consistency
‣ Scalability
68
76. Spinning up a Point-of-Presence in 30 minutes
(after the physical rack-and-stack)
76
ISP in a Box
‣ Components
• Configurator. Build configuration files from a central
master properties file.
• Jumpstart with a whole bunch of post-provisioning, to
install patches (with reboots), software, configuration,
etc.
• Configuration of Cisco routers.
• Configuration of central servers to talk to the new POP.
‣ This was all done in 1997
83. The System as a State Machine
• Configuration Management
• Management of State Definition and Integrity
• Change Management
• Management of State Transition Integrity
84. Configuration Management
• Managing State Integrity
• Ability to accurately define system components
(CMDB)
• Ability to accurately define system state
(configuration files, etc)
• Ability to recover system state (backups)
85. Change Management
• Managing State Transition Integrity
• Correctness of target state
• Correctness of work instructions
87. The Purpose of Change Management is to manage the
risks associate with state transition
The Risks Being Managed
‣ Process Failures
• Incorrect Change Procedure
• Procedure Not Followed Correctly
• Unexpected Side-Effect
‣ End State Failures
• Toxic End State
87
88. All Changes share the same risk mitigation strategies
Risk Mitigation
‣ Backups
• The point in time directly before the change is the last
known stable point, hence the baseline for all other
mitigation plans.
‣ Other techniques
• Copy files sideways. Split mirrors. Snapshots.
• Change qualification. Progressive deployment.
• Copilots. Contingency time.
• Automation.
88
89. DevOps sees everything as a code push
DevOps and Change Management
‣ DevOps is highly optimised for a single type of Change --
the code push.
• This often requires a full build from scratch.
• They also deal with complex changes, like database
schema changes with minimal service disruption.
• Service availability is paramount in DevOps change
philosophy.
89
91. System Administration has been talking about
Configuration Management for a long time!
‣ Many Tools
• rdist, cfengine, bcfg2, satan, Netomata, puppet,
chef, ...
‣ Many Approaches
• push/pull, centralised/distributed, various abstraction
layers and models.
‣ Many Papers
• Dozens of papers over 26 years.
91
Traditional Configuration Management
92. DevOps is highly reliant on automated Configuration
Management
‣ DevOps solves this for individual applications.
• The vertical stack.
• Often by blowing a VM away and starting again.
‣ Not the complexity of the entire infrastructure.
• Assumes shared infrastructure (physical compute,
store, network) are all in place (and configured!).
92
DevOps and Configuration Management
93. DevOps doesn’t solve these problems, but it does
establish a better culture for solving them!
93
99. Everything is software now
The Software Defined Data Centre
‣ Virtualisation is only the first step
• It is necessary, but not sufficient
• 20K machines virtualised are still 20K machines
individually managed.
‣ Automation is critical to that journey
• Standardisation is the basis for automation.
‣ Cloud standards are in their infancy
• Expect a lot of change over the coming years.
99
101. DevOps is the harbinger of the next wave
DevOps and Automated Infrastructure
Innovators Early Adopters Early Majority Late Majority Laggards
TheChasm
Early Market
WebOps
Crossing the Chasm
DevOps
Mainstream Market
Enterprise Hybrid Clouds
Late Market
Mainstream Market
Enterprise Private Clouds
102. Infrastructure delivered via API will be the
basis for large scale enterprise outsourcing
of infrastructure and associated support
teams.
102
103. Infrastructure delivered via API will be the basis for large
scale enterprise outsourcing of system teams
The Next Outsourcing Wave?
‣ Rob Thomsett: Process versus Project Work
• First generation of outsourcing was just replacing
staff.
• Infrastructure was bespoke; each machine managed
as an individual, customised solution.
‣ Standardised infrastructure delivered by API
• You can shop around; you can use multiple providers
simultaneously.
103
104. A market place for services
The Infrastructure Service Bus
104
Service Bus
Service
Domains
Compute Storage Network
PortalConsumer
Service
Catalogue
105. This really will change the industry
The Infrastructure Service Bus
‣ Enterprise (Infrastructure) Service Bus
• Service Provider Model
• Being embraced by large enterprises now!
• The outsource providers are becoming cloud
providers!
‣ Our Cloud APIs are evolving into Middleware (message
bus) APIs
• System Administrations looks even more like
enterprise software systems!
105
106. The irony here is that as infrastructure is treated more like
code, the very frameworks and patterns used for software
development become applicable to infrastructure.
106
114. Some of the source data used in this talk
References
‣ The Agile Manifesto
• http://www.agilemanifesto.org
‣ The Facts and Fallacies of Software Engineering
• Robert L. Glass, ISBN 0-321-11742-5.
‣ System Administrator’s Body of Knowledge (SA-BOK)
• http://www.sysadmin.com.au/sa-bok.html
‣ Serviceability Criteria
• https://www.sysadmin.com.au/whitepapers/developer_guidelines-0212.pdf
114