�ݺ�ߣshows by User: schlomo

�ݺ�ߣshows by User: schlomo / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: schlomo / Thu, 28 Jul 2022 15:53:24 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: schlomo The Role of GitOps in IT-Strategy v2 - July 2022 - Schlomo Schapiro /schlomo/the-role-of-gitops-in-itstrategy-v2-july-2022-schlomo-schapiro theroleofgitopsinit-strategyv2-july2022-schlomoschapiro-220728155324-186ed765
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.]]>
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.]]> Thu, 28 Jul 2022 15:53:24 GMT /schlomo/the-role-of-gitops-in-itstrategy-v2-july-2022-schlomo-schapiro schlomo@slideshare.net(schlomo) The Role of GitOps in IT-Strategy v2 - July 2022 - Schlomo Schapiro schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/theroleofgitopsinit-strategyv2-july2022-schlomoschapiro-220728155324-186ed765-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from Schlomo Schapiro

]]> 22 0 https://cdn.slidesharecdn.com/ss_thumbnails/theroleofgitopsinit-strategyv2-july2022-schlomoschapiro-220728155324-186ed765-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 The GitOps Journey - Schlomo Schapiro - Berlin DevOps Meetup 2021-11 /slideshow/the-gitops-journey-schlomo-schapiro-berlin-devops-meetup-202111/250711295 thegitopsjourney-schlomoschapiro-berlindevopsmeetup2021-11-211123173217
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.]]>
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.]]> Tue, 23 Nov 2021 17:32:16 GMT /slideshow/the-gitops-journey-schlomo-schapiro-berlin-devops-meetup-202111/250711295 schlomo@slideshare.net(schlomo) The GitOps Journey - Schlomo Schapiro - Berlin DevOps Meetup 2021-11 schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/thegitopsjourney-schlomoschapiro-berlindevopsmeetup2021-11-211123173217-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from Schlomo Schapiro

]]> 446 0 https://cdn.slidesharecdn.com/ss_thumbnails/thegitopsjourney-schlomoschapiro-berlindevopsmeetup2021-11-211123173217-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 The Role of GitOps in IT-Strategy - November 2021 - Schlomo Schapiro - Continuous Lifecycle 2021 /slideshow/the-role-of-gitops-in-itstrategy-november-2021-schlomo-schapiro-continuous-lifecycle-2021/250677746 theroleofgitopsinitstrategy-november2021-schlomoschapiro-continuouslifecycle2021-211118132008
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. https://schlomo.schapiro.org/p/publications.html]]>
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. https://schlomo.schapiro.org/p/publications.html]]> Thu, 18 Nov 2021 13:20:08 GMT /slideshow/the-role-of-gitops-in-itstrategy-november-2021-schlomo-schapiro-continuous-lifecycle-2021/250677746 schlomo@slideshare.net(schlomo) The Role of GitOps in IT-Strategy - November 2021 - Schlomo Schapiro - Continuous Lifecycle 2021 schlomo 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. https://schlomo.schapiro.org/p/publications.html <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/theroleofgitopsinitstrategy-november2021-schlomoschapiro-continuouslifecycle2021-211118132008-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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. https://schlomo.schapiro.org/p/publications.html

The Role of GitOps in IT-Strategy - November 2021 - Schlomo Schapiro - Continuous Lifecycle 2021 from Schlomo Schapiro

]]> 473 0 https://cdn.slidesharecdn.com/ss_thumbnails/theroleofgitopsinitstrategy-november2021-schlomoschapiro-continuouslifecycle2021-211118132008-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Schlomo Schapiro - Why I like to use the proprietary Cloud services without further abstractions - 23.05.2021 /slideshow/schlomo-schapiro-why-i-like-to-use-the-proprietary-cloud-services-without-further-abstractions-23052021/250524355 schlomoschapiro-ichnutzedieproprietarecloud-dienstedasistvieleinfacher-qawarecloud-nativebattle23-211025182034
Event: https://www.meetup.com/Cloud-Native-Night/events/280209453/]]>
Event: https://www.meetup.com/Cloud-Native-Night/events/280209453/]]> Mon, 25 Oct 2021 18:20:33 GMT /slideshow/schlomo-schapiro-why-i-like-to-use-the-proprietary-cloud-services-without-further-abstractions-23052021/250524355 schlomo@slideshare.net(schlomo) Schlomo Schapiro - Why I like to use the proprietary Cloud services without further abstractions - 23.05.2021 schlomo Event: https://www.meetup.com/Cloud-Native-Night/events/280209453/ <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/schlomoschapiro-ichnutzedieproprietarecloud-dienstedasistvieleinfacher-qawarecloud-nativebattle23-211025182034-thumbnail.jpg?width=120&height=120&fit=bounds" /> Event: https://www.meetup.com/Cloud-Native-Night/events/280209453/

Schlomo Schapiro - Why I like to use the proprietary Cloud services without further abstractions - 23.05.2021 from Schlomo Schapiro

]]> 118 0 https://cdn.slidesharecdn.com/ss_thumbnails/schlomoschapiro-ichnutzedieproprietarecloud-dienstedasistvieleinfacher-qawarecloud-nativebattle23-211025182034-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 The Role of GitOps in IT Strategy - June 2021 - Schlomo Schapiro /schlomo/the-role-of-gitops-in-it-strategy-june-2021-schlomo-schapiro theroleofgitopsinitstrategy-june2021-schlomoschapiro-210615172551
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.]]>
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.]]> Tue, 15 Jun 2021 17:25:51 GMT /schlomo/the-role-of-gitops-in-it-strategy-june-2021-schlomo-schapiro schlomo@slideshare.net(schlomo) The Role of GitOps in IT Strategy - June 2021 - Schlomo Schapiro schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/theroleofgitopsinitstrategy-june2021-schlomoschapiro-210615172551-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from Schlomo Schapiro

]]> 1594 0 https://cdn.slidesharecdn.com/ss_thumbnails/theroleofgitopsinitstrategy-june2021-schlomoschapiro-210615172551-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 The GitOps Journey - GitOpsCon EU 2021 - Schlomo Schapiro /slideshow/the-gitops-journey-gitopscon-eu-2021-schlomo-schapiro/247599990 thegitopsjourney-gitopsconeu2021-schlomoschapiro-210503133055
I'll 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. This talk explains the role of GitOps in IT strategy. See https://schlomo.schapiro.org/2021/04/the-gitops-journey.html for more details and video of this talk]]>
I'll 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. This talk explains the role of GitOps in IT strategy. See https://schlomo.schapiro.org/2021/04/the-gitops-journey.html for more details and video of this talk]]> Mon, 03 May 2021 13:30:54 GMT /slideshow/the-gitops-journey-gitopscon-eu-2021-schlomo-schapiro/247599990 schlomo@slideshare.net(schlomo) The GitOps Journey - GitOpsCon EU 2021 - Schlomo Schapiro schlomo I'll 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. This talk explains the role of GitOps in IT strategy. See https://schlomo.schapiro.org/2021/04/the-gitops-journey.html for more details and video of this talk <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/thegitopsjourney-gitopsconeu2021-schlomoschapiro-210503133055-thumbnail.jpg?width=120&height=120&fit=bounds" /> I'll 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. This talk explains the role of GitOps in IT strategy. See https://schlomo.schapiro.org/2021/04/the-gitops-journey.html for more details and video of this talk

The GitOps Journey - GitOpsCon EU 2021 - Schlomo Schapiro from Schlomo Schapiro

]]> 423 0 https://cdn.slidesharecdn.com/ss_thumbnails/thegitopsjourney-gitopsconeu2021-schlomoschapiro-210503133055-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Want Digitalisation, have Cloud - DevSecOps Days 2021 - Schlomo Schapiro /slideshow/want-digitalisation-have-cloud-devsecops-days-2021-schlomo-schapiro/243745620 suchedigitalisierunghabecloud-devsecopsdays2021-schlomoschapiro-210303080741
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.]]>
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.]]> Wed, 03 Mar 2021 08:07:40 GMT /slideshow/want-digitalisation-have-cloud-devsecops-days-2021-schlomo-schapiro/243745620 schlomo@slideshare.net(schlomo) Want Digitalisation, have Cloud - DevSecOps Days 2021 - Schlomo Schapiro schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/suchedigitalisierunghabecloud-devsecopsdays2021-schlomoschapiro-210303080741-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from Schlomo Schapiro

]]> 356 0 https://cdn.slidesharecdn.com/ss_thumbnails/suchedigitalisierunghabecloud-devsecopsdays2021-schlomoschapiro-210303080741-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Automated Governance - Continous Lifecycle 2019 - Schlomo Schapiro /slideshow/automated-governance-continous-lifecycle-2019-schlomo-schapiro/192697822 automatedgovernance-continouslifecycle2019-schlomoschapiro-191112102536
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]]>
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]]> Tue, 12 Nov 2019 10:25:36 GMT /slideshow/automated-governance-continous-lifecycle-2019-schlomo-schapiro/192697822 schlomo@slideshare.net(schlomo) Automated Governance - Continous Lifecycle 2019 - Schlomo Schapiro schlomo 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 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/automatedgovernance-continouslifecycle2019-schlomoschapiro-191112102536-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from Schlomo Schapiro

]]> 2527 1 https://cdn.slidesharecdn.com/ss_thumbnails/automatedgovernance-continouslifecycle2019-schlomoschapiro-191112102536-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Compliant by Default - Digitaler Wandel - 14.08.2019 - Schlomo Schapiro /slideshow/compliant-by-default-digitaler-wandel-14082019-schlomo-schapiro/163830183 compliantbydefault-digitalerwandel-14-190814141526
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. ]]>
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. ]]> Wed, 14 Aug 2019 14:15:26 GMT /slideshow/compliant-by-default-digitaler-wandel-14082019-schlomo-schapiro/163830183 schlomo@slideshare.net(schlomo) Compliant by Default - Digitaler Wandel - 14.08.2019 - Schlomo Schapiro schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/compliantbydefault-digitalerwandel-14-190814141526-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from Schlomo Schapiro

]]> 443 2 https://cdn.slidesharecdn.com/ss_thumbnails/compliantbydefault-digitalerwandel-14-190814141526-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 DevOps ist normal - DevOps Essentials 2019 - Schlomo Schapiro /slideshow/devops-is-normal-devops-essentials-2019-schlomo-schapiro/148797537 devopsisnormal-devopsessentials2019-schlomoschapiro-190603195012
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]]>
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]]> Mon, 03 Jun 2019 19:50:12 GMT /slideshow/devops-is-normal-devops-essentials-2019-schlomo-schapiro/148797537 schlomo@slideshare.net(schlomo) DevOps ist normal - DevOps Essentials 2019 - Schlomo Schapiro schlomo 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 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/devopsisnormal-devopsessentials2019-schlomoschapiro-190603195012-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from Schlomo Schapiro

]]> 964 2 https://cdn.slidesharecdn.com/ss_thumbnails/devopsisnormal-devopsessentials2019-schlomoschapiro-190603195012-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 The Devops Driving School - DevOps Gathering 2019 - Schlomo Schapiro /slideshow/the-devops-driving-school-devops-gathering-2019-schlomo-schapiro/135843793 devopsgathering2019-thedevopsdrivingschool-schlomoschapiro-190312110353
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]]>
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]]> Tue, 12 Mar 2019 11:03:53 GMT /slideshow/the-devops-driving-school-devops-gathering-2019-schlomo-schapiro/135843793 schlomo@slideshare.net(schlomo) The Devops Driving School - DevOps Gathering 2019 - Schlomo Schapiro schlomo 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 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/devopsgathering2019-thedevopsdrivingschool-schlomoschapiro-190312110353-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from Schlomo Schapiro

]]> 721 2 https://cdn.slidesharecdn.com/ss_thumbnails/devopsgathering2019-thedevopsdrivingschool-schlomoschapiro-190312110353-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Open Source Contribution Policy at DB Systel - Schlomo Schapiro - AK Open Source BITKOM - 14.02.2019 /slideshow/open-source-contribution-policy-at-db-systel-schlomo-schapiro-ak-open-source-bitkom-14022019/131610202 opensourcecontributionpolicyatdbsystel-schlomoschapiro-akopensourcebitkom-14-190213095600
How to create an Open Source Contribution policy, introducing to the policy of DB Systel.]]>
How to create an Open Source Contribution policy, introducing to the policy of DB Systel.]]> Wed, 13 Feb 2019 09:56:00 GMT /slideshow/open-source-contribution-policy-at-db-systel-schlomo-schapiro-ak-open-source-bitkom-14022019/131610202 schlomo@slideshare.net(schlomo) Open Source Contribution Policy at DB Systel - Schlomo Schapiro - AK Open Source BITKOM - 14.02.2019 schlomo How to create an Open Source Contribution policy, introducing to the policy of DB Systel. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/opensourcecontributionpolicyatdbsystel-schlomoschapiro-akopensourcebitkom-14-190213095600-thumbnail.jpg?width=120&height=120&fit=bounds" /> How to create an Open Source Contribution policy, introducing to the policy of DB Systel.

Open Source Contribution Policy at DB Systel - Schlomo Schapiro - AK Open Source BITKOM - 14.02.2019 from Schlomo Schapiro

]]> 447 4 https://cdn.slidesharecdn.com/ss_thumbnails/opensourcecontributionpolicyatdbsystel-schlomoschapiro-akopensourcebitkom-14-190213095600-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Compliant by Default - Continuous Delivery at DB Systel - 16.10.2018 - Schlomo Schapiro and Hendrik Pahl /slideshow/compliant-by-default-continuous-delivery-at-db-systel-16102018-schlomo-schapiro-and-hendrik-pahl/119496187 compliantbydefault-lhsystemsdevopsevent416-181015160033
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 ]]>
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 ]]> Mon, 15 Oct 2018 16:00:33 GMT /slideshow/compliant-by-default-continuous-delivery-at-db-systel-16102018-schlomo-schapiro-and-hendrik-pahl/119496187 schlomo@slideshare.net(schlomo) Compliant by Default - Continuous Delivery at DB Systel - 16.10.2018 - Schlomo Schapiro and Hendrik Pahl schlomo 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 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/compliantbydefault-lhsystemsdevopsevent416-181015160033-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 - Schlomo Schapiro and Hendrik Pahl from Schlomo Schapiro

]]> 1316 1 https://cdn.slidesharecdn.com/ss_thumbnails/compliantbydefault-lhsystemsdevopsevent416-181015160033-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 DevOps + Continuous Delivery + Cloud: The Three Drivers of Enterprise Agility - AWS Summit 07.06.2018 - Schlomo Schapiro https://de.slideshare.net/slideshow/devops-continuous-delivery-cloud-the-three-drivers-of-enterprise-agility-aws-summit-07062018-schlomo-schapiro/101123728 devopscontinuousdeliverycloud-thethreedriversofenterpriseagility-awssummit07-180607130609
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.]]>
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.]]> Thu, 07 Jun 2018 13:06:09 GMT https://de.slideshare.net/slideshow/devops-continuous-delivery-cloud-the-three-drivers-of-enterprise-agility-aws-summit-07062018-schlomo-schapiro/101123728 schlomo@slideshare.net(schlomo) DevOps + Continuous Delivery + Cloud: The Three Drivers of Enterprise Agility - AWS Summit 07.06.2018 - Schlomo Schapiro schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/devopscontinuousdeliverycloud-thethreedriversofenterpriseagility-awssummit07-180607130609-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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.

from Schlomo Schapiro

]]> 1224 2 https://cdn.slidesharecdn.com/ss_thumbnails/devopscontinuousdeliverycloud-thethreedriversofenterpriseagility-awssummit07-180607130609-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Kubernetes - Shifting the mindset from servers to containers - microxchg 2018 - Schlomo Schapiro /slideshow/kubernetes-shifting-the-mindset-from-servers-to-containers-microxchg-2018-schlomo-schapiro/91574921 kubernetes-shiftingthemindsetfromserverstocontainers-microxchange2018-schlomoschapiro-180322172255
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 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.]]> Thu, 22 Mar 2018 17:22:55 GMT /slideshow/kubernetes-shifting-the-mindset-from-servers-to-containers-microxchg-2018-schlomo-schapiro/91574921 schlomo@slideshare.net(schlomo) Kubernetes - Shifting the mindset from servers to containers - microxchg 2018 - Schlomo Schapiro schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/kubernetes-shiftingthemindsetfromserverstocontainers-microxchange2018-schlomoschapiro-180322172255-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 2018 - Schlomo Schapiro from Schlomo Schapiro

]]> 5211 6 https://cdn.slidesharecdn.com/ss_thumbnails/kubernetes-shiftingthemindsetfromserverstocontainers-microxchange2018-schlomoschapiro-180322172255-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Root for all - measuring DevOps adoption - microxchg 2018 - Schlomo Schapiro https://de.slideshare.net/schlomo/root-for-all-measuring-devops-adoption-microxchange-2018-schlomo-schapiro rootforall-measuringdevopsadoption-microxchange2018-schlomoschapiro-180322111611
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 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.]]> Thu, 22 Mar 2018 11:16:11 GMT https://de.slideshare.net/schlomo/root-for-all-measuring-devops-adoption-microxchange-2018-schlomo-schapiro schlomo@slideshare.net(schlomo) Root for all - measuring DevOps adoption - microxchg 2018 - Schlomo Schapiro schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/rootforall-measuringdevopsadoption-microxchange2018-schlomoschapiro-180322111611-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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.

from Schlomo Schapiro

]]> 2678 2 https://cdn.slidesharecdn.com/ss_thumbnails/rootforall-measuringdevopsadoption-microxchange2018-schlomoschapiro-180322111611-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 GUUG FFG 2017 - DevOps for Everybody - A Workplace Strategy for the Digital Age /slideshow/guug-ffg-2017-devops-for-everybody-a-workplace-strategy-for-the-digital-age/73581190 guugffg2017-devopsforeverybody-proposalworkplacestrategyforthedigitalage-170324083053
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.]]>
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.]]> Fri, 24 Mar 2017 08:30:53 GMT /slideshow/guug-ffg-2017-devops-for-everybody-a-workplace-strategy-for-the-digital-age/73581190 schlomo@slideshare.net(schlomo) GUUG FFG 2017 - DevOps for Everybody - A Workplace Strategy for the Digital Age schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/guugffg2017-devopsforeverybody-proposalworkplacestrategyforthedigitalage-170324083053-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from Schlomo Schapiro

]]> 1769 4 https://cdn.slidesharecdn.com/ss_thumbnails/guugffg2017-devopsforeverybody-proposalworkplacestrategyforthedigitalage-170324083053-thumbnail.jpg?width=120&height=120&fit=bounds document Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 GUUG FFG 2017 - DevOps for Everybody - How the entire company can benefit from DevOps /slideshow/guug-ffg-2017-devops-for-everybody-how-the-entire-company-can-benefit-from-devops/73581151 guugffg2017-devopsforeverybody-170324082859
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.]]>
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.]]> Fri, 24 Mar 2017 08:28:58 GMT /slideshow/guug-ffg-2017-devops-for-everybody-how-the-entire-company-can-benefit-from-devops/73581151 schlomo@slideshare.net(schlomo) GUUG FFG 2017 - DevOps for Everybody - How the entire company can benefit from DevOps schlomo 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. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/guugffg2017-devopsforeverybody-170324082859-thumbnail.jpg?width=120&height=120&fit=bounds" /> 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 from DevOps from Schlomo Schapiro

]]> 1730 3 https://cdn.slidesharecdn.com/ss_thumbnails/guugffg2017-devopsforeverybody-170324082859-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 OSDC 2016 - Hybrid Cloud - A Cloud Migration Strategy /slideshow/osdc-2016-hybrid-cloud-a-cloud-migration-strategy/61451303 osdc2016-hybridcloud-acloudmigrationstrategy-160428080740
Do you use Cloud? Why? What about the 15 year legacy of your data center? How many Enterprise vendors tried to sell you their "Hybrid Cloud" solution? What actually is a Hybrid Cloud? Cloud computing is not just a new way of running servers or Docker containers. The interesting part of any Cloud offering are managed services that provide solutions to difficult problems. Prime examples are messaging (SNS/SQS), distributed storage (S3), managed databases (RDS) and especially turn-key solutions like managed Hadoop (EMR). Hybrid Cloud is usually understood as a way to unify or standardize server hosting across private data centers and Public Cloud vendors. Some Hybrid Cloud solutions even go as far as providing a unified API that abstracts away all the differences between different platforms. Unfortunately that approach focuses on the lowest common denominator and effectively prevents using the advanced services that each Cloud vendor also offers. However, these services are the true value of Public Cloud vendors. Another approach to integrating Public Cloud and private data centers is using services from both worlds depending on the problems to solve. Don't hide the cloud technologies but make it simple to use them - both from within the data center and the cloud instances. Create a bridge between the old world of the data center and the new world of the Public Cloud. A good bridge will motivate your developers to move the company to the cloud. Based upon recent developments at ImmobilienScout24, this talk tries to suggest a sustainable Cloud migration strategy from private data centers through a Hybrid Cloud into the AWS Cloud. Bridging the security model of the data center with the security model of AWS. Integrating the AWS identity management (IAM) with the existing servers in the data center. Secure communication between services running in the data center and in AWS. Deploying data center servers and Cloud resources together. Service discovery for services running both in the data center and AWS. Most of the tools used are Open Source and this talk will show how they come together to support this strategy: AWS credential provider for employees and data center servers: http://immobilienscout24.github.io/afp/ Cloud Formation automation: https://github.com/ImmobilienScout24/cfn-sphere Compliancy with European privacy laws: https://github.com/ImmobilienScout24/aws-monocyte ]]>
Do you use Cloud? Why? What about the 15 year legacy of your data center? How many Enterprise vendors tried to sell you their "Hybrid Cloud" solution? What actually is a Hybrid Cloud? Cloud computing is not just a new way of running servers or Docker containers. The interesting part of any Cloud offering are managed services that provide solutions to difficult problems. Prime examples are messaging (SNS/SQS), distributed storage (S3), managed databases (RDS) and especially turn-key solutions like managed Hadoop (EMR). Hybrid Cloud is usually understood as a way to unify or standardize server hosting across private data centers and Public Cloud vendors. Some Hybrid Cloud solutions even go as far as providing a unified API that abstracts away all the differences between different platforms. Unfortunately that approach focuses on the lowest common denominator and effectively prevents using the advanced services that each Cloud vendor also offers. However, these services are the true value of Public Cloud vendors. Another approach to integrating Public Cloud and private data centers is using services from both worlds depending on the problems to solve. Don't hide the cloud technologies but make it simple to use them - both from within the data center and the cloud instances. Create a bridge between the old world of the data center and the new world of the Public Cloud. A good bridge will motivate your developers to move the company to the cloud. Based upon recent developments at ImmobilienScout24, this talk tries to suggest a sustainable Cloud migration strategy from private data centers through a Hybrid Cloud into the AWS Cloud. Bridging the security model of the data center with the security model of AWS. Integrating the AWS identity management (IAM) with the existing servers in the data center. Secure communication between services running in the data center and in AWS. Deploying data center servers and Cloud resources together. Service discovery for services running both in the data center and AWS. Most of the tools used are Open Source and this talk will show how they come together to support this strategy: AWS credential provider for employees and data center servers: http://immobilienscout24.github.io/afp/ Cloud Formation automation: https://github.com/ImmobilienScout24/cfn-sphere Compliancy with European privacy laws: https://github.com/ImmobilienScout24/aws-monocyte ]]> Thu, 28 Apr 2016 08:07:40 GMT /slideshow/osdc-2016-hybrid-cloud-a-cloud-migration-strategy/61451303 schlomo@slideshare.net(schlomo) OSDC 2016 - Hybrid Cloud - A Cloud Migration Strategy schlomo Do you use Cloud? Why? What about the 15 year legacy of your data center? How many Enterprise vendors tried to sell you their "Hybrid Cloud" solution? What actually is a Hybrid Cloud? Cloud computing is not just a new way of running servers or Docker containers. The interesting part of any Cloud offering are managed services that provide solutions to difficult problems. Prime examples are messaging (SNS/SQS), distributed storage (S3), managed databases (RDS) and especially turn-key solutions like managed Hadoop (EMR). Hybrid Cloud is usually understood as a way to unify or standardize server hosting across private data centers and Public Cloud vendors. Some Hybrid Cloud solutions even go as far as providing a unified API that abstracts away all the differences between different platforms. Unfortunately that approach focuses on the lowest common denominator and effectively prevents using the advanced services that each Cloud vendor also offers. However, these services are the true value of Public Cloud vendors. Another approach to integrating Public Cloud and private data centers is using services from both worlds depending on the problems to solve. Don't hide the cloud technologies but make it simple to use them - both from within the data center and the cloud instances. Create a bridge between the old world of the data center and the new world of the Public Cloud. A good bridge will motivate your developers to move the company to the cloud. Based upon recent developments at ImmobilienScout24, this talk tries to suggest a sustainable Cloud migration strategy from private data centers through a Hybrid Cloud into the AWS Cloud. Bridging the security model of the data center with the security model of AWS. Integrating the AWS identity management (IAM) with the existing servers in the data center. Secure communication between services running in the data center and in AWS. Deploying data center servers and Cloud resources together. Service discovery for services running both in the data center and AWS. Most of the tools used are Open Source and this talk will show how they come together to support this strategy: AWS credential provider for employees and data center servers: http://immobilienscout24.github.io/afp/ Cloud Formation automation: https://github.com/ImmobilienScout24/cfn-sphere Compliancy with European privacy laws: https://github.com/ImmobilienScout24/aws-monocyte <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/osdc2016-hybridcloud-acloudmigrationstrategy-160428080740-thumbnail.jpg?width=120&height=120&fit=bounds" /> Do you use Cloud? Why? What about the 15 year legacy of your data center? How many Enterprise vendors tried to sell you their "Hybrid Cloud" solution? What actually is a Hybrid Cloud? Cloud computing is not just a new way of running servers or Docker containers. The interesting part of any Cloud offering are managed services that provide solutions to difficult problems. Prime examples are messaging (SNS/SQS), distributed storage (S3), managed databases (RDS) and especially turn-key solutions like managed Hadoop (EMR). Hybrid Cloud is usually understood as a way to unify or standardize server hosting across private data centers and Public Cloud vendors. Some Hybrid Cloud solutions even go as far as providing a unified API that abstracts away all the differences between different platforms. Unfortunately that approach focuses on the lowest common denominator and effectively prevents using the advanced services that each Cloud vendor also offers. However, these services are the true value of Public Cloud vendors. Another approach to integrating Public Cloud and private data centers is using services from both worlds depending on the problems to solve. Don't hide the cloud technologies but make it simple to use them - both from within the data center and the cloud instances. Create a bridge between the old world of the data center and the new world of the Public Cloud. A good bridge will motivate your developers to move the company to the cloud. Based upon recent developments at ImmobilienScout24, this talk tries to suggest a sustainable Cloud migration strategy from private data centers through a Hybrid Cloud into the AWS Cloud. Bridging the security model of the data center with the security model of AWS. Integrating the AWS identity management (IAM) with the existing servers in the data center. Secure communication between services running in the data center and in AWS. Deploying data center servers and Cloud resources together. Service discovery for services running both in the data center and AWS. Most of the tools used are Open Source and this talk will show how they come together to support this strategy: AWS credential provider for employees and data center servers: http://immobilienscout24.github.io/afp/ Cloud Formation automation: https://github.com/ImmobilienScout24/cfn-sphere Compliancy with European privacy laws: https://github.com/ImmobilienScout24/aws-monocyte

OSDC 2016 - Hybrid Cloud - A Cloud Migration Strategy from Schlomo Schapiro

]]> 5451 7 https://cdn.slidesharecdn.com/ss_thumbnails/osdc2016-hybridcloud-acloudmigrationstrategy-160428080740-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 WARNING is a waste of my time /slideshow/warning-is-a-waste-of-my-time/54350224 devopsdays2015warningisawasteofmytime-151025110323-lva1-app6892
How many log levels do you know? How many log levels are actually useful? What is the practical difference between WARNING and NOTICE? I believe that in a world of automation, I need only two log levels: ERROR and everthing else. ERROR means that I as a human should take action. Everything else is irrelevant for me. All the other log levels are IMHO a remnant of the past from the last century. This ignite talk looks at the WARNING problem from both a Dev and an Ops perspective in order to find a useful definition for the age of automation. See http://blog.schlomo.schapiro.org/2015/04/warning-is-waste-of-my-time.html for blog article with more info.]]>
How many log levels do you know? How many log levels are actually useful? What is the practical difference between WARNING and NOTICE? I believe that in a world of automation, I need only two log levels: ERROR and everthing else. ERROR means that I as a human should take action. Everything else is irrelevant for me. All the other log levels are IMHO a remnant of the past from the last century. This ignite talk looks at the WARNING problem from both a Dev and an Ops perspective in order to find a useful definition for the age of automation. See http://blog.schlomo.schapiro.org/2015/04/warning-is-waste-of-my-time.html for blog article with more info.]]> Sun, 25 Oct 2015 11:03:22 GMT /slideshow/warning-is-a-waste-of-my-time/54350224 schlomo@slideshare.net(schlomo) WARNING is a waste of my time schlomo How many log levels do you know? How many log levels are actually useful? What is the practical difference between WARNING and NOTICE? I believe that in a world of automation, I need only two log levels: ERROR and everthing else. ERROR means that I as a human should take action. Everything else is irrelevant for me. All the other log levels are IMHO a remnant of the past from the last century. This ignite talk looks at the WARNING problem from both a Dev and an Ops perspective in order to find a useful definition for the age of automation. See http://blog.schlomo.schapiro.org/2015/04/warning-is-waste-of-my-time.html for blog article with more info. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/devopsdays2015warningisawasteofmytime-151025110323-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /> How many log levels do you know? How many log levels are actually useful? What is the practical difference between WARNING and NOTICE? I believe that in a world of automation, I need only two log levels: ERROR and everthing else. ERROR means that I as a human should take action. Everything else is irrelevant for me. All the other log levels are IMHO a remnant of the past from the last century. This ignite talk looks at the WARNING problem from both a Dev and an Ops perspective in order to find a useful definition for the age of automation. See http://blog.schlomo.schapiro.org/2015/04/warning-is-waste-of-my-time.html for blog article with more info.

WARNING is a waste of my time from Schlomo Schapiro

]]> 6019 7 https://cdn.slidesharecdn.com/ss_thumbnails/devopsdays2015warningisawasteofmytime-151025110323-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-schlomo-48x48.jpg?cb=1730797242 blog.schlomo.schapiro.org https://cdn.slidesharecdn.com/ss_thumbnails/theroleofgitopsinit-strategyv2-july2022-schlomoschapiro-220728155324-186ed765-thumbnail.jpg?width=320&height=320&fit=bounds schlomo/the-role-of-gitops-in-itstrategy-v2-july-2022-schlomo-schapiro The Role of GitOps in ... https://cdn.slidesharecdn.com/ss_thumbnails/thegitopsjourney-schlomoschapiro-berlindevopsmeetup2021-11-211123173217-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/the-gitops-journey-schlomo-schapiro-berlin-devops-meetup-202111/250711295 The GitOps Journey - S... https://cdn.slidesharecdn.com/ss_thumbnails/theroleofgitopsinitstrategy-november2021-schlomoschapiro-continuouslifecycle2021-211118132008-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/the-role-of-gitops-in-itstrategy-november-2021-schlomo-schapiro-continuous-lifecycle-2021/250677746 The Role of GitOps in ...