Agile is dead! Long live DevOps! Um.. ALM… um…
There has been a plethora of “agile is dead” of late posts yet the long list of failed agile that has caused it smell very little like agile. What was missing? Come and find out how to make a success of your agile project, and what will immediately spell disaster…
Paying lip service to a lexicon is no longer enough…
The very small 2-person DevOps team within Red Hat Performance/Scale Engineering has developed a set of Open Source Python-based systems and network automation provisioning tools designed to end-to-end automate the provisioning of large-scale systems and network switches using tools like Foreman, Ansible, and other Open Source bits.
QUADS – or “quick and dirty scheduler” allows a normally overburdened DevOps warrior to fully automate large swaths of systems and network devices based on a schedule, even set systems provisioning to fire off in the future so they can focus on important things like Netflix and popcorn or not read your emails while your datacenter burns in an inferno of rapid, automated skynet provisioning. QUADS will also auto-generate up-to-date infrastructure documentation, track scheduling, systems assignments and more.
In this talk we’ll show you how we’re using QUADS (backed by Foreman) to empower rapid, meaningful performance and scale testing of Red Hat products and technologies. While QUADS is a new project and under constant development, the design approach to handling large-scale systems provisioning as well as the current codebase is consumable for others interested in improving the efficiency and level of automation within their infrastructure.
DevOps at Scale as a problem to solve is becoming more relevant every day but there isn’t that much of information how to do it for real. Also techy people get into technology and forget what DevOps is really about. This talk abstracts from technology and focuses purely on culture and organisational topics in a fun way.
“So… meet delivery lead John. He got a brilliant idea how basically from nothing to make the cutest bunny in the world.”
ShuttleCloud is a small startup specialized in email and contacts migrations. We developed a reliable migration platform in high availability used by clients like Gmail, GContacts and Comcast. For example, Gmail alone has imported data for 3 million users with our API and we process hundreds of terabytes every month.
In this talk, we’ll explain our journey from having near-zero monitoring to having all of our infrastructure monitored with the necessary metrics and alerts. We will share with the audience some of the mistakes we did and what lessons we have learned. We currently have around 200 instances monitored with a comfortable cost-effective in-house monitoring stack based on Prometheus.
We want to demonstrate that you don’t need to have a big fleet to embrace Prometheus and that it is a non-expensive solution for monitoring.
Utilizing Docker & Container technologies we can bring following capabilities closer to the app layer:
These capabilities were previously only available at hardware/switch layer, now we’re seeing SDN (Software Driven Networking) transformation thanks to Dockerization of our platforms.
In this talk, we explore in detail how efficiency and effectiveness are related to DevOps and the traditional separation of Development and Operations.
Companies are usually aiming for high efficiency and predictability. This seems to make sense in the first place, as no one wants to be inefficient, right? But wait a second, the ask for efficiency might be a source of a permanent conflict with the DevOps idea. The focus on “synergy effects” and “good utilization” – which is a focus on efficiency – is often one of the main motivations for creating silos in the organization, for the classical separation between Dev and Ops. Quite often those structures are neither effective nor efficient in the long run.
On the other hand, with DevOps done right one can achieve a high level of effectiveness: Horizontal scaling, that is, increasing for a team their coverage of the value stream from idea to production, brings naturally the focus on doing the right thing for the customer. Furthermore, by improving the efficiency of an effective process, DevOps can enable companies to achieve a significant competitive advantage. Especially the Continuous Delivery pipeline can be a strong engine for delivering features and improvements to enable innovation and a high operational excellence.
What can I learn in this session?
This presentation explores DevOps from a business value perspective, giving you a better understanding of the potential benefits of “devopsing” your organization: more speed, stability and fun (seriously!). But how do you sell DevOps to business executives?
Not all organizations will get these benefits: if you work in a relatively stable environment, you might be wasting your money. Looking at DevOps as medication, what are the curable symptoms, the right dosage, side-effects, and warnings? And is it addictive?
DevOps is grounded in the Theory of Constraints that identifies the most important bottleneck in the way of achieving a goal and then improves it until it is no longer the limiting factor. Yet DevOps only addresses part of the IT value chain. What about the functional requirements, value realization by the users, and the relationship with IT’s business partners? What is your biggest bottleneck? Is an investment in DevOps (shock horror!) just sub-optimization?
Takeaways
1. What kind of organization should invest in DevOps and which benefits can reasonably be expected;
2. A value proposition that you can sell to business executives.
3.Where DevOps fits in the bigger IT picture and what’s needed to avoid sub-optimization.
