PyCon 2013 Test Driven Infrastructure

•

1 gefällt mir•1,222 views

Test Driven Infrastructure (with examples in RPM packages). How to save your butt by adding a few cheap and simple tests to your packages. Use visudo to validate sudo configuration (sudo will stop to work with broken configs!). Use bash and python to validate scripts against typos, forgotton braces etc. I gave this talk at the PyConDE 2013 (https://2013.de.pycon.org/), Original video with all lightning talks is http://pyvideo.org/video/2438/mittwoch-lightning-talks

Technologie

www.immobilienscout24.de

Test Driven Infrastructure

Köln | 16.10.2013 | Schlomo Schapiro
Systemarchitekt, Open Source Evangelist

License: http://creativecommons.org/licenses/by-nc-nd/3.0/

%prep
%setup -q
%install
install … %{buildroot}/…
install … %{buildroot}/…
%files
%defattr(-,root,root,-)
/...

BuildRequires: sudo
%build
set -e
visudo -c -f sudoers
%install
install -m 0440 sudoers -D
%{buildroot}/etc/suoders.d/%{name}
%files%defattr(-,root,root,-)
/etc/suoders.d/%{name}

BuildRequires: PyYAML, pylint
%build
set -e
# syntax checks
bash -n my_script.sh
# Should be valid python code
pylint -E yum-repo-propagate
# should be valid YAML file
python -c "
import yaml
yaml.safe_load( open('config.yaml') )
"
...

Continuous Delivery
RPM Build Jobs (Unit Tests)
 Build RPM_1 and upload to DEV YUM Repo
 Build RPM_2 and upload to DEV YUM Repo
 ...

FOO Integration Test Job
 yadtshell update DEVFOO
 rsh devfoo99 run-some-local-tests
 curl http://devfoo99/deep-status
 yum-repo-propagate -y DEVFOO -d PRO RPM_1 RPM_2

Update FOO in Production

Thank you very much!
Please contact me for further
questions and discussions.
Kontakt:
Immobilien Scout GmbH
Andreasstraße 10
10243 Berlin

Fon:
+49 30 243 01-1229
Email: schlomo.schapiro@immobilienscout24.de
URL: www.immobilienscout24.de

All images are either public domain, used in appropriate
context or taken from openclipart.org

8

Weitere ähnliche Inhalte

Ähnlich wie PyCon 2013 Test Driven Infrastructure

Common wisdom has it that the test effort should be related to the risk of a change. However, the reality is different: Developers build elaborate automated test chains to test every single commit of their application. Admins regularly “test” changes on the live platform in production. But which change carries a higher risk of taking the live platform down? What about the software that runs at the “lower levels” of your platform, e.g. systems automation, provisioning, proxy configuration, mail server configuration, database systems etc. An outage of any of those systems can have a financial impact that is as severe as a bug in the “main” software! One of the biggest learnings that any Ops person can learn from a Dev person is Test Driven Development. Easy to say - difficult to apply is my personal experience with the TDD challenge. This talk throws some light on recent developments at ImmobilienScout24 that help us to develop the core of our infrastructure services with a test driven approach: - How to do unit tests, integration tests and systems tests for infrastructure services? - How to automatically verify Proxy, DNS, Postfix configurations before deploying them on live servers? - How to test “dangerous” services like our PXE boot environment or the automated SAN mounting scripts? - How to add a little bit of test coverage to everything we do. - Test Driven: First write a failing test and then the code that fixes it. The tools that we use are Bash, Python, Unit Test frameworks and Teamcity for build and test automation. See http://blog.schlomo.schapiro.org/2013/12/test-driven-infrastructure.html for more about this topic.

OSDC 2014 Test Driven Infrastructure

Schlomo Schapiro

Common wisdom has it that the test effort should be related to the risk of a change. However, the reality is different: Developers build elaborate automated test chains to test every single commit of their application. Admins regularly “test” changes on the live platform in production. But which change carries a higher risk of taking the live platform down? What about the software that runs at the “lower levels” of your platform, e.g. systems automation, provisioning, proxy configuration, mail server configuration, database systems etc. An outage of any of those systems can have a financial impact that is as severe as a bug in the “main” software! One of the biggest learnings that any Ops person can learn from a Dev person is Test Driven Development. Easy to say - difficult to apply is my personal experience with the TDD challenge. This talk throws some light on recent developments at ImmobilienScout24 that help us to develop the core of our infrastructure services with a test driven approach: * How to do unit tests, integration tests and systems tests for infrastructure services? * How to automatically verify Proxy, DNS, Postfix configurations before deploying them on live servers? * How to test “dangerous” services like our PXE boot environment or the automated SAN mounting scripts? * How to add a little bit of test coverage to everything we do. * Test Driven: First write a failing test and then the code that fixes it.

OSDC 2014: Schlomo Schapiro - Test Driven Infrastructure

NETWAYS

Groovy for System Administrators

Daniel Woods

Jump into Squeak - Integrate Squeak projects with Docker & Github

hubx

PVS-Studio: analyzing pull requests in Azure DevOps using self-hosted agents

Andrey Karpov

Hammr is an OW2 open source, command-line tool for creating consistent and repeatable machine images for different cloud or virtual environments, or migrating live systems from one environment to another. Designed for cloud era environments, where agility and automation are key, hammr helps organizations automate the creation of machine images for hybrid environments. This presentation will focus on the hybrid capabilities of hammr for any virtual or cloud target environment. It will also include a focus on DevOps and Docker integration, and show how hammr can be used to quickly build and run Docker images, helping accelerate development and test processes among other benefits. Finally, we will present the latest hammr features, including the ability for cloud providers to customize target platforms and expose their own IaaS infrastructure as top-level branded objects accessible via hammr, thus easing the path from user images to their cloud infrastructure.

Hammr Project Update: Machine Images and Docker Containers for your Cloud, OW...

OW2

Baking in the cloud with packer and puppet

Alan Parkinson

This presentation was given at the Mac Admin & Developer Conference UK in February 2017. Session description follows: You’re dealing with terrible installer packages, applications that perform ad-hoc system setup tasks and assume every user is an admin. It seems so often they were never tested in multi-user or enterprise environments. Your colleagues wonder “How hard could this be? At home I just install it and it works,” and they roll their eyes as you bemoan the sad realities of deploying desktop software. This session will explore techniques for identifying the causes of these issues, and how to approach the various problems systematically to develop solutions. In no particular order, we’ll visit Bash, Python, packaging, launchd, configuration profiles, defaults, and the Hopper Disassembler.

Advanced Mac Software Deployment and Configuration: Just Make It Work!

Timothy Sutton

Making environment for_infrastructure_as_code

Soshi Nemoto

SaltConf14 - Ben Cane - Using SaltStack in High Availability Environments

SaltStack

Travis and fastlane

Steven Shen

Writing and Publishing Puppet Modules - PuppetConf 2014

Puppet

This presentation was given at the MacSysAdmin 2016 conference in Gotebörg, Sweden. Session description follows: Apple’s popularity and their approach to selling hardware is revolutionizing how IT gets that hardware into the hands of its users. Every year’s new Macs and OS X bring new changes, which doesn’t leave much time for the repetitive setup tasks that are involved in getting machines ready for users (or our testing!). It’s easy to fall behind on OS support, but we have no choice but to support the latest. The Mac sysadmin community is blessed with so many great open-source tools at its disposal for deploying and managing Macs. We'll look at approaches and tools for automating these to bring speed, consistency and sanity to our deployment processes. By being more systematic, we can be more agile, and reclaim time to work on more important problems. This session will focus on OS X hardware and tools, but the approaches discussed apply equally to iOS devices.

Tools and Process for Streamlining Mac Deployment

Timothy Sutton

Ask a beginner to deploy a Python web application and they will often complain it is too hard. Although we have standards for how a Python web application should interface with a web server, the web servers for Python all work differently, with a myriad of options and being difficult to set up properly. In this talk you will be given a preview of a project called 'warpdrive', a project being developed to simplify the process of deploying a Python web application. The 'warpdrive' project makes it easy to run your Python web application on your own system, but it can also create a Docker image for your application, providing you with an easy path to deploying it on a Docker service. How 'warpdrive' works is also compatible with next generation Platform as a Service (PaaS) offerings such as the latest OpenShift, which has been reimplemented around Docker and Kubernetes. See how working on and deploying your Python web application could be made so much easier using 'warpdrive'.

“warpdrive”, making Python web application deployment magically easy.

Graham Dumpleton

Dependencies Managers in C/C++. Using stdcpp 2014

biicode

Component pack 6006 install guide

Roberto Boccadoro

uygulamalarla siber güvenlik-siber guvenlik haftasi.pptx

anilyelken

The security of an application is a continuous struggle between solid proactive controls and quality in SDLC versus human weakness and resource restrictions. As the pentester's experience confirms, unfortunatelly even in high-risk (e.g. banking) applications, developed by recognized vendors, the latter often wins - and we end up with critical vulnerabilities. One of the primary reasons is lack of mechanisms enforcing secure code by default, as opposed to manual adding security per each function. Whenever the secure configuration is not default, there will almost inevitably be bugs, especially in complex systems. I will pinpoint what should be taken into consideration in the architecture and design process of the application. I will show solutions that impose security in ways difficult to circumvent unintentionally by creative developers. I will also share with the audience the pentester's (=attacker's) perspective, and a few clever tricks that made the pentest (=attack) painful, or just rendered the scenarios irrelevant.

Applications secure by default

Slawomir Jasek

Applications secure by default

SecuRing

How to Install Ghost (CMS) MEMO

Naoto MATSUMOTO

Ähnlich wie PyCon 2013 Test Driven Infrastructure (20)

OSDC 2014 Test Driven Infrastructure

OSDC 2014: Schlomo Schapiro - Test Driven Infrastructure

Groovy for System Administrators

Jump into Squeak - Integrate Squeak projects with Docker & Github

PVS-Studio: analyzing pull requests in Azure DevOps using self-hosted agents

Hammr Project Update: Machine Images and Docker Containers for your Cloud, OW...

Baking in the cloud with packer and puppet

Advanced Mac Software Deployment and Configuration: Just Make It Work!

Making environment for_infrastructure_as_code

SaltConf14 - Ben Cane - Using SaltStack in High Availability Environments

Travis and fastlane

Writing and Publishing Puppet Modules - PuppetConf 2014

Tools and Process for Streamlining Mac Deployment

“warpdrive”, making Python web application deployment magically easy.

Dependencies Managers in C/C++. Using stdcpp 2014

Component pack 6006 install guide

uygulamalarla siber güvenlik-siber guvenlik haftasi.pptx

Applications secure by default

How to Install Ghost (CMS) MEMO

Mehr von Schlomo Schapiro

What is the role of GitOps in IT strategy? This talk gives an overview and puts GitOps into the context of current challenges in IT strategy. Main aspects are continuous delivery, policy as code, automated governance, compliant-by-default work environments, acceptable means of compliance and a comprehensive automation of all development and operations related processes with the goal of true hands-off operations. The result places GitOps as a major building block of any modern IT strategy. GitOps helps building essential key IT capabilities. It creates the motivation to truly “fix the basics” via sustainable solutions to enable creating higher level automation solutions. With GitOps engineers can focus much more on business value and spend less effort on boring IT topics.

The Role of GitOps in IT-Strategy v2 - July 2022 - Schlomo Schapiro

Schlomo Schapiro

I will show why GitOps is a major waypoint in the journey from old-style Dev vs. Ops data center operations towards a truly automated hands-off operations future. GitOps is the technological core required for compliance automation, large-scale operations, and lowering the cost of compliance & governance as well as lowering the cost of internal tooling. GitOps will give us a future, where we all take a step back, watch the bots do the admin job, and where we Dev, Ops, everybody work on improving the bots and invent new automation solutions. Schlomo Schapiro is an Agile IT and Open Source enthusiast dedicated to advancing an agile mindset and a DevOps-orientated culture in IT. He works as Principal Engineer at Forto in Berlin, is author of several Open Source projects, conference speaker and regularly publishes blog and magazine articles. See https://schlomo.schapiro.org/2021/04/the-gitops-journey.html for more details.

The GitOps Journey - Schlomo Schapiro - Berlin DevOps Meetup 2021-11

Schlomo Schapiro

The Role of GitOps in IT-Strategy - November 2021 - Schlomo Schapiro - Contin...

Schlomo Schapiro

Schlomo Schapiro - Why I like to use the proprietary Cloud services without f...

Schlomo Schapiro

See https://www.youtube.com/watch?v=_uDzXmbiUIg for German-language talk to these slides. What is the role of GitOps in IT strategy? This talk gives an overview and puts GitOps into the context of current challenges in IT strategy. Main aspects are continuous delivery, policy as code, automated governance, compliant-by-default work environments, acceptable means of compliance and a comprehensive automation of all development and operations related processes with the goal of true hands-off operations. The result places GitOps as a major building block of any modern IT strategy. GitOps helps building essential key IT capabilities. It creates the motivation to truly “fix the basics” via sustainable solutions to enable creating higher level automation solutions. With GitOps engineers can focus much more on business value and spend less effort on boring IT topics.

The Role of GitOps in IT Strategy - June 2021 - Schlomo Schapiro

Schlomo Schapiro

The GitOps Journey - GitOpsCon EU 2021 - Schlomo Schapiro

Schlomo Schapiro

Cloud, Automation und DevOps als Treiber der Digitalisierung: Wir zeigen den Weg der Deutschen Bahn in die Zukunft. Unter dem Motto “Fix the Basics” entwickeln wir grundlegende Services für Engineers, die u.a. Security- und Compliance-Prüfungen automatisieren und die Teams dadurch in die Lage versetzen, sich auf die Produktion von Business Value zu fokussieren. Einer dieser Services ist Continuous Delivery as a Service, eine anpassbare, hochautomatisoierte CD-Implementierung, die nach dem Ansatz "compliant by default" eine einfache und richtlinienkonforme Möglichkeit zum Deployment von Software darstellt. Der Vortrag zeigt auf, dass die Automation von Security- und Compliance-Vorgaben bei gleichzeitigem Fokus auf Usability für die Engineers ein kritischer Bestandteil auf dem weg zur Digitalisierung ist. Teams werden in die Lage versetzt, ihren Code nachhaltig qualitativ zu verbessern, die Unternehmen profitieren durch die folgende Innovation und die Fokussierung auf Business-relevante Lösungen. Vorkenntnisse Keine Vorkenntnisse erforderlich Lernziele * Die enge Beziehung zwischen DevOps, Continuous Delivery und Cloud kennenlernen und verstehen, warum sie eine optimale Arbeitslandschaft für Entwickler bietet. * "Entwicklerproduktivität" sollte an erster Stelle stehen, da wir so unserem Team helfen, sich auf die Entwicklung neuer Features zu konzentrieren, statt auf die Suche nach dem richtigen Werkzeug. * Automation ist die Schlüsselfertigkeit, um den Dreiklang DevOps, CD und Cloud erfolgreich zu machen. * Die Bereitstellung von grundlegenden Services in der Entwicklung versetzt die eigene Entwicklung in die Lage, echte Innovation zu betreiben.

Want Digitalisation, have Cloud - DevSecOps Days 2021 - Schlomo Schapiro

Schlomo Schapiro

Video: https://youtu.be/U4cHbXYy1FQ How to combine traditional IT governance with continuous delivery? Not At All! A highly automated continuous deployment environment creates a whole new world of challenges for companies to meet their compliance and governance requirements. Traditional - manual - processes don’t manage to keep up with quick and frequent releases. The solution to this conflict of interests is the automation of all compliance checks and the automated certification of every software delivery into production. Sounds obvious and simple, but it is difficult to implement. The talk shows how we tackle this topic at DB Systel and how we create solutions for automated compliance certification. See https://bit.ly/5pdops for more materials and the 5 DevOps Principles

Automated Governance - Continous Lifecycle 2019 - Schlomo Schapiro

Schlomo Schapiro

Wie passt klassische IT Governance zu Continuous Delivery? Gar nicht! Eine hochgradig automatisierte Continuous Deployment Welt stellt die Firma vor ganz neue Herausforderungen im Bereich Compliance und Governance. Klassische - manuelle - Prozesse kommen den schnellen und häufigen Releases gar nicht mehr hinterher. Die Lösung ist die Automation aller Governance prüfungen und die automatisierte Zertifizierung jeder Softwarelieferung. Das klingt banal und einfach, ist im Detail jedoch nicht einfach umzusetzen. Der Vortrag zeigt am konkreten Beispiel der DB Systel, wie wir das Thema angehen und Lösungen für die automatisierte Zertifizierung geschaffen haben.

Compliant by Default - Digitaler Wandel - 14.08.2019 - Schlomo Schapiro

Schlomo Schapiro

Video: https://vimeo.com/348556177 DevOps ist normal – oder etwa doch nicht? Wer kann das schon für seine Firma guten Gewissens sagen? Während sich die übliche DevOps-Diskussion um das Wie dreht, adressiert Schlomo die Frage, wann DevOps normal geworden ist und was dafür passieren muss, damit alle dieser Meinung sind. Von einer neuen DevOps-Definition ausgehend stellt der Vortrag eine einfache Argumentationskette für DevOps vor, in der die DevOps-Transformation mit Fahren lernen verglichen wird. So wie es heutzutage normal ist, dass die meisten Erwachsenen einen Führerschein haben, so normal sollte DevOps in jeder IT sein. Diese Analogie lässt sich auch in einem Aufzugsgespräch verwenden, um das Management von der Normalität des DevOps-Ansatzes zu überzeugen. Mit der DevOps-Definition gelingt es den Teilnehmern, jede DevOps-Diskussion zu gewinnen und damit DevOps zur neuen Normalität zu machen. Am konkreten Beispiel der DB Systel zeigt der Vortrag, wie mit dem Thema DevOps-Teams konstruktiv umgegangen werden kann. Siehe https://bit.ly/5pdops für weiteres Material und die 5 DevOps Prinzipien

DevOps ist normal - DevOps Essentials 2019 - Schlomo Schapiro

Schlomo Schapiro

How to convince your company that DevOps is a transitional mode of operations and the means to a goal instead of goal in itself. What comes after DevOps is “done”? DevOps is like learning to drive and a “DevOps Team” is like a motor cycle driving school. You learn in theory and practice to survive amongst “live traffic”, where other road participants are not very considerate. You have to comply with a lot of regulations. From early on you drive your motor cycle alone and the driving instructor follows you in his car keeping a safe distance. He talks with you via radio and tells you where to pay attention and how to drive. But you drive all alone and by yourself - amongst live traffic. If you hit a tree and die, it is your own fault. If you cause a crash, it is your own fault. Same about learning DevOps. You are responsible for your product in production with “live traffic” and real customers. If you crash your server, it your own fault. If your code quality causes harm to the company, it is your own fault. Your DevOps Coach sits next to you and talks to you while you type away at your screen, like a driving instructor. In the end you prove your driving skills, get your license and ride happily singing full speed into the sunset. Same about DevOps, after a training period you work alone. You build it - you run it. You go full speed ahead and deliver value over value. Who has a bumper sticker claiming “I have a driving license”? That’s why “DevOps Team” is a passing thing and once you qualify you are just an Engineering Team who are fully responsible for their product end to end. No need to put a claim to what is normal, because DevOps is normal. Video: https://youtu.be/N2EWEfhQt2M

The Devops Driving School - DevOps Gathering 2019 - Schlomo Schapiro

Schlomo Schapiro

Open Source Contribution Policy at DB Systel - Schlomo Schapiro - AK Open Sou...

Schlomo Schapiro

Learn about the journey of Deutsche Bahn towards Cloud computing, DevOps and agile transformation, with special focus on our Continuous Delivery strategy and implementation. After a brief overview of what is happening at DB Systel, we will show our Continuous Delivery as-a-Service (CDaaS) approach. CDaaS is an integrative approach to Continuous Delivery ensuring governance and security compliance whilst being fully focused on the user experience. We will show the extensibility and simplicity of CDaaS and how it helps DevOps teams improve code quality. Key take aways are a profound understanding of the intimate relationship between DevOps, Continuous Delivery and Cloud which enables a truly integrated work environment for our developers. By putting ?Developer Productivity? first we ensure that our teams can focus on developing their features over choosing the right tool or knowing all platform topics in-depth

Compliant by Default - Continuous Delivery at DB Systel - 16.10.2018 - Schlom...

Schlomo Schapiro

More than just buzzwords, true agility depends on the successful combination of DevOps, Continuous Delivery and Cloud platforms. Learn which technology choices have the greatest impact on the company culture. Take DevOps adoption to the next level by introducing DevOps key performance indicators as a measure of your company’s progress. This session presents current developments and projects at DB Systel, the IT company of Deutsche Bahn.

DevOps + Continuous Delivery + Cloud: The Three Drivers of Enterprise Agility...

Schlomo Schapiro

Kubernetes: Shifting the mindset from servers to containers With Kubernetes pods and containers several fundamental assumptions of server operations don't apply any more. Some Linux services like SSH even disappear and are provided by Kubernetes instead. This talk explores the mindset shift that developers and admins of Linux servers have to do in order to fully take advantage of the power of a Kubernetes cluster: * Servers turn into pods * Linux application services turn into containers * Standard services like cron and SSH disappear completely * How to separate between initialization, run and maintenance phases * Building pods with multiple containers that work together Following practical examples from real migration projects participants gain a new understanding of the role of services, init scripts, cron jobs and other standard Linux components. Key takeaways are a better understanding of how to model a complex system on top of Kubernetes and practical tips for migrating servers into Kubernetes containers. Successfully adopting Kubernetes requires a big change in how developers and admins think about servers - bigger than any change before. Bigger than the change brought by VMs. This talk shows why it pays to change traditional concepts and to embrace the new world of Linux services modularization that Kubernetes stands for. See Using Kubernetes with Multiple Containers for Initialization and Maintenance (http://blog.schlomo.schapiro.org/2017/06/using-kubernetes-with-multiple.html) for more information and a demo.

Kubernetes - Shifting the mindset from servers to containers - microxchg 201...

Schlomo Schapiro

Root for All - Measuring DevOps Adoption DevOps is about culture and mindset more than about technology - but how do you measure success? How do you know if your company really "does" DevOps? It turns out that root access to production servers is not only the proverbial holy grail but actually serves as a fact-based measure for the trust and automation levels in an organization. This talk explores the connection between root access and automation on one hand and DevOps mindsets, cross functional teams and shared responsibility on the other hand. Based on practical experiences, the talk provides concrete suggestions for achieving true DevOps happiness. As a result you will know why in the end there is no harm at all in granting root access to everybody. Key takeaways are solid arguments that you can use to convince your boss and your peers to take a different approach on root access demonstrating how shared responsibility works for real. See Root for All - A DevOps Measure? (http://blog.schlomo.schapiro.org/2017/06/root-for-all-devops-measure.html) for more background information.

Root for all - measuring DevOps adoption - microxchg 2018 - Schlomo Schapiro

Schlomo Schapiro

How should our internal IT look in order to be a driving force for a company’s success in the digital age? This proposal is based on all my learnings from the previous 15 years and especially the Agile and DevOps revolution in IT. It takes the concept of a Product Development Organization to apply everywhere and provides a sure path to increase productivity and improve culture through technology. Transforming Corporate IT into a Workplace product takes internal IT out of the proverbial basement and puts it in the front of the internal value chain. Most of the standard tooling for product development also fits the Workplace product. This proposal is written for a typical company that employs both modern web technologies like G Suite and cloud services as well as traditional technologies like Microsoft Office and data centers.

GUUG FFG 2017 - DevOps for Everybody - A Workplace Strategy for the Digital Age

Schlomo Schapiro

DevOps ist aus der IT nicht mehr wegzudenken und hat sich als Arbeitsweise etabliert, die nicht nur die Qualität und operative Effizienz verbessert, sondern auch eine nachhaltige Entwicklung ermöglicht. In den meisten Unternehmen ist die IT jedoch eine Minderheit. Wie können wir mit den Ideen und Erkenntnissen aus der DevOps Welt die ganze Firma voranbringen? Warum funktioniert die agile Zusammenarbeit nicht automatisch mit anderen Abteilungen? Was macht die ITler so besonders? Die Schnittstelle zwischen allen Mitarbeitern und IT Themen ist die interne IT. Sie trägt die Verantwortung dafür, dass alle Mitarbeiter mit Hilfe von IT ihre Aufgaben effizient und effektiv erledigen können. Während die interne IT oftmals nur als Kostenstelle betrachtet wird, leistet sie in Wahrheit einen sehr hohen Beitrag zur Wertschöpfungskette: Schlechte Werkzeuge führen direkt zu langsamer Arbeit und frustrieren, gute Werkzeuge befähigen die Mitarbeiter und erhöhen die Freude an der gemeinsamen Arbeit. Heute leisten es sich viele Unternehmen noch, dass ihre Mitarbeiter auf einer digitalisierten Plattform manuelle Tätigkeiten verrichten. Messgrößen sind etwa die Anzahl der Copy-Paste Vorgänge (Mensch als technische Schnittstelle), die Anzahl an internen Emails mit Dateianhang (Dokumente werden vervielfältigt anstatt sie zentral bereit zu stellen) sowie die Anzahl der Logins die ein Mitarbeiter täglich absolviert (schwach oder gar nicht integrierte Systeme). Die Herausforderungen der fortschreitenden Digitalisierung und Verteuerung von Arbeitskraft erfordern hier auch ein Umdenken. Der Vortrag zeichnet einen Weg von DevOps in der IT zu einem neuen Denkansatz für den Umgang mit IT im Unternehmen. Dabei entwickeln sich Mitarbeiter von IT Konsumenten zu beteiligten Nutzern, die den Computer als Werkzeug für sich entdecken können. Die interne IT stellt nicht nur gute Services zur Verfügung sondern fokussiert sich auf die Produktivität und Zufriedenheit aller Mitarbeiter.

GUUG FFG 2017 - DevOps for Everybody - How the entire company can benefit fro...

Schlomo Schapiro

How Open Source, Agile Methods and DevOps come together at ImmobilienScout24. Was verbindet Open Source, Agiles Mindset und DevOps? In der richtigen Kombination dieser Themen entsteht für die IT eine neue Basis der Zusammenarbeit. Ein Rückblick auf die letzten 6 Jahre bei ImmobilienScout24 zeigt, wie die Anwendung in der Praxis unsere IT-Abteilung voran gebracht hat. Bei der Cloudmigration profitieren wir insbesondere von der offenen Kultur in der Firma und der Community.

DevOps, Agile and Open Source at ImmobilienScout24

Schlomo Schapiro

EuroPython 2014 YAML Reader Lightning Talk

Schlomo Schapiro

Mehr von Schlomo Schapiro (20)