PuppetConf 2016: Heresy in the Church of Docker – Corey Quinn, The Quinn Advisory Group

•

0 likes•338 views

Here are the slides fromCorey Quinn's PuppetConf 2016 presentation called Heresy in the Church of Docker. Watch the videos at https://www.youtube.com/playlist?list=PLV86BgbREluVjwwt-9UL8u2Uy8xnzpIqa

Technology

Heresy in the Church of Docker
@QuinnyPig
Corey Quinn
The Quinn Advisory Group

Heresy in the Church of Docker
Corey Quinn
The Quinn Advisory Group
@QuinnyPig

That Time My Boss
Destroyed a Cubicle
Corey Quinn
@QuinnyPig

Docker is the first ever OS Container
System
@QuinnyPig

Docker is the first ever OS Container
System
•LXC
@QuinnyPig

Docker is the first ever OS Container
System
•LXC
•Solaris Zones
@QuinnyPig

Docker is the first ever OS Container
System
•LXC
•Solaris Zones
•FreeBSD Jails
@QuinnyPig

Docker is the first ever OS Container
System
•LXC
•Solaris Zones
•FreeBSD Jails
•Chroots
@QuinnyPig

Docker is the first ever OS Container
System
•LXC
•Solaris Zones
•FreeBSD Jails
•Chroots
•OpenVZ
@QuinnyPig

Docker is the first ever OS Container
System
•LXC
•Solaris Zones
•FreeBSD Jails
•Chroots
•OpenVZ
•LPARS
@QuinnyPig

•LXC
•Solaris Zones
•FreeBSD Jails
•Chroots
•OpenVZ
•LPARS
•Virtualization(?)
Docker is the first ever OS Container
System
@QuinnyPig

Docker is the first ever OS Container
System
•LXC
•Solaris Zones
•FreeBSD Jails
•Chroots
•OpenVZ
•LPARS
•Virtualization(?)
•Vagrant
@QuinnyPig

Interlude
"What's a Microservice?"
@QuinnyPig

Microservice Characteristics
• Small, independent processes
@QuinnyPig

Microservice Characteristics
• Small, independent processes
• Communicate with each other via API calls
@QuinnyPig

Microservice Characteristics
• Small, independent processes
• Communicate with each other via API calls
• Modular
@QuinnyPig

Microservice Characteristics
• Small, independent processes
• Communicate with each other via API calls
• Modular
• Environment Agnostic
@QuinnyPig

Microservice Characteristics
• Small, independent processes
• Communicate with each other via API calls
• Modular
• Environment Agnostic
• Scalable development model
@QuinnyPig

DockerDocker
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Networking
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Rolling Deployments
Networking
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Monitoring
Rolling Deployments
Networking
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Supervision
Monitoring
Rolling Deployments
Networking
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Config Changes
Supervision
Monitoring
Rolling Deployments
Networking
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Peer / Service discovery
Config Changes
Supervision
Monitoring
Rolling Deployments
Networking
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Container Hosting
Peer / Service discovery
Config Changes
Supervision
Monitoring
Rolling Deployments
Networking
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Code Quality
Container Hosting
Peer / Service discovery
Config Changes
Supervision
Monitoring
Rolling Deployments
Networking
Development Production
@QuinnyPig

DockerDocker
Kubernetes
Security
Code Quality
Container Hosting
Peer / Service discovery
Config Changes
Supervision
Monitoring
Rolling Deployments
Networking
Development Production

Based on a tweet by
@mfdii + @julian_dunn
@QuinnyPig

Suitably modified
by @josh_atwell
@QuinnyPig

Corey Quinn
Heresy in the Church of Docker
@QuinnyPig

Docker (and by extension, microservices based architecture) has expanded our horizons with respect to how the industry builds and supports applications at scale. It’s changed the way we think about our code, what production looks like, and how we live. But in our rush to embrace this exciting new paradigm, are we throwing away the lessons of the past? In this entertaining and somewhat irreverent talk, Corey presents the ”other side” of the containerization craze: how configuration management fits into a world consumed by the Docker Docker Docker madness, how ”containers all the way down” can let you down when you least expect it, and how promising technologies should perhaps be vetted a bit more thoroughly before you try to run critical services on top of them.

Gitgithub101slideshare 150922131830-lva1-app6891

Brian Okinyi

This document provides an overview of version control using git and GitHub. It explains that git is a distributed version control system that allows users to track changes to files and collaborate on projects. GitHub is a web-based hosting service for git repositories that provides additional features like a user interface, documentation, and pull requests. The document outlines how to install git, create a GitHub account, and covers key git concepts like commits, repositories, cloning, pulling, and pushing changes.

Building Your (My) First Gem

Cameron Kidman

Building a Ruby gem involves generating a gem skeleton using the "bundle gem" command which sets up the necessary file structure including a Gemfile, README, Rakefile and gemspec. The code for the gem is added to the /lib folder following a test-driven development approach with tests added to the /spec folder. Once the gem is complete, it can be published to RubyGems.org by building the gemspec, adding credentials, and pushing the generated gem file.

Ditch Sandboxes for Docker

Travis Thieman

Demo

Miracle Anyanwu

This document provides an overview of installing Git and creating a GitHub account, as well as explaining some key concepts about version control with Git and GitHub. It discusses installing Git on Linux, Mac and Windows systems, creating a GitHub account, and what Git and GitHub are. Key Git concepts explained include snapshots, commits, repositories, branches, merging, and what a HEAD means in Git. GitHub is described as a website that hosts Git repositories and adds extra functionality for code collaboration.

Paasta: Application Delivery at Yelp

C4Media

PuppetConf 2016: Delivering Premium Quality Modules: Using Beaker and VMpoole...

Puppet

The document discusses KPN's use of Beaker and VMpooler for multi-platform testing of Puppet modules. It outlines the requirements for an automated testing pipeline that runs syntax, unit, and acceptance tests on Linux and Windows platforms in parallel. The solution involved setting up a Jenkins master and build slaves along with VMpooler to provision VMs for testing. Beaker is used to run acceptance tests across multiple platforms. Details are provided on configuring the testing components and writing acceptance tests. Metrics on modules, test types, runs, and failed tests are presented.

PuppetConf 2016: Puppet and UCS: Policy-Based Management All the Way Down – C...

Puppet

This document provides an overview of measuring and tuning performance for the Puppet Enterprise (PE) platform. It discusses gathering data from PE services like Puppet Server and PuppetDB through JVM logging, metrics, and configurations. Important metrics for Puppet Server include JRuby usage and catalog compilation times. Tuning options involve adjusting JRuby capacity and rebalancing agent checkins. The document also covers monitoring PuppetDB for storage usage and command processing, as well as optimizing PostgreSQL query performance.

Canadian Cyber Cecurity

Peter Scheffler

This document summarizes key findings from a 2015 cyber security study of Canadian organizations and other cyber security reports. Some key points: - On average, Canadian companies were attacked 40 times in 2015 and 51% suffered data loss from an attack. - 35% saw one Advanced Persistent Threat attack per month on average. Distributed denial-of-service (DDoS) attacks were still the most common, with companies experiencing 5 per month on average. - The document recommends deploying identity and access management solutions, network monitoring tools, and security information and event management systems to improve security. It also discusses using BIG-IP to provide visibility into encrypted traffic for security services while maintaining performance.

PuppetConf 2016: The Challenges with Container Configuration – David Lutterko...

Puppet

PuppetConf 2016: Best Practices for Puppet in the Cloud – Randall Hunt, Amazo...

Puppet

This document summarizes best practices for using Puppet configuration management in the AWS cloud. It describes ServiceChannel's journey from an on-premise infrastructure to migrating to AWS, including initial exploration of single EC2 instances and hybrid on-premise/AWS deployments. Key steps for deploying Puppet in AWS are discussed such as understanding AWS services, network configuration, enabling CloudTrail logging, and using IAM roles. The Puppet Labs AWS module is introduced for provisioning AWS resources through Puppet. Benefits seen from adopting DevOps practices like Puppet in AWS include faster deployment times, increased stability, and shorter recovery windows.

PuppetConf 2016: Watching the Puppet Show – Sean Porter, Heavy Water Operations

Puppet

PuppetConf 2016: Using Puppet with Kubernetes and OpenShift – Diane Mueller, ...

Puppet

F5 TLS & SSL Practices

Brian A. McHenry

The document discusses SSL/TLS trends, practices, and futures. It covers global SSL encryption trends and drivers like increased spending on security and regulatory pressure. It discusses SSL best practices like enabling TLS 1.2, disabling weak protocols, using strong cipher strings, and enabling HTTP Strict Transport Security. The document also looks at solutions from F5 like hardware security modules, advanced key and certificate management, and market leading encryption support. It explores emerging standards like TLS 1.3 and topics like elliptic curve cryptography. Finally, it discusses what's next such as OCSP stapling and F5's SSL everywhere architecture.

Puppet camp2021 testing modules and controlrepo

Puppet

This document discusses testing Puppet code when using modules versus a control repository. It recommends starting with simple syntax and unit tests using PDK or rspec-puppet for modules, and using OnceOver for testing control repositories, as it is specially designed for this purpose. OnceOver allows defining classes, nodes, and a test matrix to run syntax, unit, and acceptance tests across different configurations. Moving from simple to more complex testing approaches like acceptance tests is suggested. PDK and OnceOver both have limitations for testing across operating systems that may require customizing spec tests. Infrastructure for running acceptance tests in VMs or containers is also discussed.

Puppetcamp r10kyaml

Puppet

2021 04-15 operational verification (with notes)

Puppet

The document discusses operational verification and how Puppet is working on a new module to provide more confidence in infrastructure health. It introduces the concept of adding check resources to catalogs to validate configurations and service health directly during Puppet runs. Examples are provided of how this could detect issues earlier than current methods. Next steps outlined include integrating checks into more resource types, fixing reporting, integrating into modules, and gathering feedback. This allows testing and monitoring to converge by embedding checks within configurations.

Puppet camp vscode

Puppet

Modules of the twenties

Puppet

- The document discusses various patterns and techniques the author has found useful when working with Puppet modules over 10+ years, including some that may be considered unorthodox or anti-patterns by some. - Key topics covered include optimization of reusable modules, custom data types, Bolt tasks and plans, external facts, Hiera classification, ensuring resources for presence/absence, application abstraction with Tiny Puppet, and class-based noop management. - The author argues that some established patterns like roles and profiles can evolve to be more flexible, and that running production nodes in noop mode with controls may be preferable to fully enforcing on all nodes.

Applying Roles and Profiles method to compliance code

Puppet

This document discusses adapting the roles and profiles design pattern to writing compliance code in Puppet modules. It begins by noting the challenges of writing compliance code, such as it touching many parts of nodes and leading to sprawling code. It then provides an overview of the roles and profiles pattern, which uses simple "front-end" roles/interfaces and more complex "back-end" profiles/implementations. The rest of the document discusses how to apply this pattern when authoring Puppet modules for compliance - including creating interface and implementation classes, using Hiera for configuration, and tools for reducing boilerplate code. It aims to provide a maintainable structure and simplify adapting to new compliance frameworks or requirements.

KGI compliance as-code approach

Puppet

This document discusses Kinney Group's Puppet compliance framework for automating STIG compliance and reporting. It notes that customers often implement compliance Puppet code poorly or lack appropriate Puppet knowledge. The framework aims to standardize compliance modules that are data-driven and customizable. It addresses challenges like conflicting modules and keeping compliance current after implementation. The framework generates automated STIG checklists and plans future integration with Puppet Enterprise and Splunk for continued compliance reporting. Kinney Group cites practical experience implementing the framework for various military and government customers.

Enforce compliance policy with model-driven automation

Puppet

This document discusses model-driven automation for enforcing compliance. It begins with an overview of compliance benchmarks and the CIS benchmarks. It then discusses implementing benchmarks, common challenges around configuration drift and lack of visibility, and how to define compliance policy as code. The key points are that automation is essential for compliance at scale; a model-driven approach defines how a system should be configured and uses desired-state enforcement to keep systems compliant; and defining compliance policy as code, managing it with source control, and automating it with CI/CD helps achieve continuous compliance.

Keynote: Puppet camp compliance

Puppet

This document discusses how organizations can move from a reactive approach to compliance to a proactive approach using automation. It notes that over 50% of CIOs cite security and compliance as a barrier to IT modernization. Puppet offers an end-to-end compliance solution that allows organizations to automatically eliminate configuration drift, enforce compliance at scale across operating systems and environments, and define policy as code. The solution helps organizations improve compliance from 50% to over 90% compliant. The document argues that taking a proactive automation approach to compliance can turn it into a competitive advantage by improving speed and innovation.

Automating it management with Puppet + ServiceNow

Puppet

As the leading IT Service Management and IT Operations Management platform in the marketplace, ServiceNow is used by many organizations to address everything from self service IT requests to Change, Incident and Problem Management. The strength of the platform is in the workflows and processes that are built around the shared data model, represented in the CMDB. This provides the ‘single source of truth’ for the organization. Puppet Enterprise is a leading automation platform focused on the IT Configuration Management and Compliance space. Puppet Enterprise has a unique perspective on the state of systems being managed, constantly being updated and kept accurate as part of the regular Puppet operation. Puppet Enterprise is the automation engine ensuring that the environment stays consistent and in compliance. In this webinar, we will explore how to maximize the value of both solutions, with Puppet Enterprise automating the actions required to drive a change, and ServiceNow governing the process around that change, from definition to approval. We will introduce and demonstrate several published integration points between the two solutions, in the areas of Self-Service Infrastructure, Enriched Change Management and Automated Incident Registration.

Puppet: The best way to harden Windows

Puppet

This document promotes Puppet as a tool for hardening Windows environments. It states that Puppet can be used to harden Windows with one line of code, detect drift from desired configurations, report on missing or changing requirements, reverse engineer existing configurations, secure IIS, and export configurations to the cloud. Benefits of Puppet mentioned include hardening Windows environments, finding drift for investigation, easily passing audits, compliance reporting, easy exceptions, and exporting configurations. It also directs users to Puppet Forge modules for securing Windows and IIS.

Simplified Patch Management with Puppet - Oct. 2020

Puppet

Does your company struggle with patching systems? If so, you’re not alone — most organizations have attempted to solve this issue by cobbling together multiple tools, processes, and different teams, which can make an already complicated issue worse. Puppet helps keep hosts healthy, secure and compliant by replacing time-consuming and error prone patching processes with Puppet’s automated patching solution. Join this webinar to learn how to do the following with Puppet: Eliminate manual patching processes with pre-built patching automation for Windows and Linux systems. Gain visibility into patching status across your estate regardless of OS with new patching solution from the PE console. Ensure your systems are compliant and patched in a healthy state How Puppet Enterprise makes patch management easy across your Windows and Linux operating systems. Presented by: Margaret Lee, Product Manager, Puppet, and Ajay Sridhar, Sr. Sales Engineer, Puppet.

Accelerating azure adoption with puppet

Puppet

The document discusses how Puppet can be used to accelerate adoption of Microsoft Azure. It describes lift and shift migration of on-premises workloads to Azure virtual machines. It also covers infrastructure as code using Puppet and Terraform for provisioning, configuration management using Puppet Bolt, and implementing immutable infrastructure patterns on Azure. Integrations with Azure services like Key Vault, Blob Storage and metadata service are presented. Patch management and inventory of Azure resources with Puppet are also summarized.

Puppet catalog Diff; Raphael Pinson

Puppet

This document discusses using Puppet Catalog Diff to analyze the impact of changes between Puppet environments or catalogs. It provides the command line usage and options for Puppet Catalog Diff. It also discusses how to integrate Puppet Catalog Diff into CI/CD pipelines for automated impact analysis when merging code changes. Additional resources like GitHub projects and Dev.to posts are provided for learning more about diffing Puppet environments and catalogs.

ServiceNow and Puppet- better together, Kevin Reeuwijk

Puppet

ServiceNow and Puppet can be integrated in four key areas: 1) Self-service infrastructure allows non-Puppet experts to control infrastructure through a ServiceNow interface; 2) Enriched change management automatically generates ServiceNow change requests from Puppet changes and populates them with impact details; 3) Automated incident registration forwards details of configuration drift corrections in Puppet to ServiceNow to create incidents; and 4) Up-to-date asset management would periodically upload Puppet inventory data to ServiceNow to keep the CMDB accurate without disruptive discovery runs.

Viewers also liked

PuppetConf 2016: An Introduction to Measuring and Tuning PE Performance – Cha...

Puppet

Canadian Cyber Cecurity

Peter Scheffler

PuppetConf 2016: The Challenges with Container Configuration – David Lutterko...

Puppet

PuppetConf 2016: Best Practices for Puppet in the Cloud – Randall Hunt, Amazo...

Puppet

PuppetConf 2016: Watching the Puppet Show – Sean Porter, Heavy Water Operations

Puppet

PuppetConf 2016: Using Puppet with Kubernetes and OpenShift – Diane Mueller, ...

Puppet

F5 TLS & SSL Practices

Brian A. McHenry

Viewers also liked (7)

PuppetConf 2016: An Introduction to Measuring and Tuning PE Performance – Cha...

Canadian Cyber Cecurity

PuppetConf 2016: The Challenges with Container Configuration – David Lutterko...

PuppetConf 2016: Best Practices for Puppet in the Cloud – Randall Hunt, Amazo...

PuppetConf 2016: Watching the Puppet Show – Sean Porter, Heavy Water Operations

PuppetConf 2016: Using Puppet with Kubernetes and OpenShift – Diane Mueller, ...

F5 TLS & SSL Practices

More from Puppet

Puppet camp2021 testing modules and controlrepo

Puppet

Puppetcamp r10kyaml

Puppet

2021 04-15 operational verification (with notes)

Puppet

Puppet camp vscode

Puppet

Modules of the twenties

Puppet

Applying Roles and Profiles method to compliance code

Puppet

KGI compliance as-code approach

Puppet

Enforce compliance policy with model-driven automation

Puppet

Keynote: Puppet camp compliance

Puppet

Automating it management with Puppet + ServiceNow

Puppet

Puppet: The best way to harden Windows

Puppet

Simplified Patch Management with Puppet - Oct. 2020

Puppet

Accelerating azure adoption with puppet

Puppet

Puppet catalog Diff; Raphael Pinson

Puppet

ServiceNow and Puppet- better together, Kevin Reeuwijk

Puppet

Take control of your dev ops dumping ground

Puppet

This document discusses how Puppet Relay uses Tekton pipelines to orchestrate containerized workflows. It provides an overview of how Tekton fits into the Relay architecture, with Tekton controllers managing taskrun pods to execute workflow steps defined in YAML. Triggers can initiate workflows based on events, with reusable and composable steps for tasks like provisioning infrastructure or clearing resources. Relay also includes features for parameters, secrets, outputs, and approvals to customize workflows. An ecosystem of open source integrations provides sample workflows and steps for common use cases.

100% Puppet Cloud Deployment of Legacy Software

Puppet

This document discusses deploying legacy software into the AWS cloud using Puppet. It proposes modeling AWS resources like security groups, autoscaling groups, and launch configurations as Puppet resources. This would allow Puppet to provision the underlying AWS infrastructure and configure servers launched in autoscaling groups. It acknowledges challenges around server reboots but suggests they can be addressed. In summary, it argues custom Puppet resources can easily model AWS resources and using Puppet to configure autoscaling servers is possible despite some challenges around rebooting servers during deployment.

Puppet User Group

Puppet

This document discusses a partnership between Republic Polytechnic's School of Infocomm and Puppet to promote DevOps practices. It introduces several people involved with the partnership and outlines their mission to prepare more IT companies and individuals for jobs in the DevOps field through training courses. The document describes some short courses offered on DevOps topics and using the Puppet and Microsoft Azure platforms. It provides an example of how Republic Polytechnic has automated infrastructure configuration using Puppet to save time and reduce errors. There is a request at the end for readers to register their interest in DevOps by completing a survey.

Continuous Compliance and DevSecOps

Puppet

This document discusses continuous compliance and DevSecOps best practices followed by financial services organizations. Continuous compliance is defined as an ongoing process of proactive risk management that delivers predictable, transparent, and cost-effective compliance results. It involves continuously monitoring compliance controls, providing real-time alerts for failures and remediation recommendations, and maintaining up-to-date policies. Best practices for continuous compliance discussed include defining CIS controls and benchmarks, achieving transparent compliance dashboards and automated fixes for breaches. DevSecOps is introduced as bringing security earlier in the application development lifecycle to minimize vulnerabilities. It aims to make everyone accountable for security. Challenges discussed include security teams struggling to keep up with DevOps pace and

The Dynamic Duo of Puppet and Vault tame SSL Certificates, Nick Maludy

Puppet

The document discusses using Puppet and Vault together to dynamically manage SSL certificates. Puppet can use the vault_cert resource to request signed certificates from Vault and configure services to use the certificates. On Windows, some additional logic is needed to retrieve certificates' thumbprints and bind services to certificates using those thumbprints. This approach provides automated certificate renewal and distribution across platforms.

More from Puppet (20)

Puppet camp2021 testing modules and controlrepo

Puppetcamp r10kyaml

2021 04-15 operational verification (with notes)

Puppet camp vscode

Modules of the twenties

Applying Roles and Profiles method to compliance code

KGI compliance as-code approach

Enforce compliance policy with model-driven automation

Keynote: Puppet camp compliance

Automating it management with Puppet + ServiceNow

Puppet: The best way to harden Windows

Simplified Patch Management with Puppet - Oct. 2020

Accelerating azure adoption with puppet

Puppet catalog Diff; Raphael Pinson

ServiceNow and Puppet- better together, Kevin Reeuwijk

Take control of your dev ops dumping ground

100% Puppet Cloud Deployment of Legacy Software

Puppet User Group

Continuous Compliance and DevSecOps

The Dynamic Duo of Puppet and Vault tame SSL Certificates, Nick Maludy

Recently uploaded

GenAI Pilot Implementation in the organizations

kumardaparthi1024

UiPath Test Automation using UiPath Test Suite series, part 6

DianaGray10

Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI. UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities. Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes. What will you get from this session? 1. Insights into integrating generative AI. 2. Understanding how this integration enhances test automation within the UiPath platform 3. Practical demonstrations 4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath Topics covered: What is generative AI Test Automation with generative AI and Open AI. UiPath integration with generative AI Speaker: Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP

Artificial Intelligence for XMLDevelopment

Octavian Nadolu

In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject. We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup. Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved. The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring. The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise. By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.

National Security Agency - NSA mobile device best practices

Quotidiano Piemontese

GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...

Neo4j

Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.

みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...

名前です男

Serial Arm Control in Real Time Presentation

tolgahangng

Removing Uninteresting Bytes in Software Fuzzing

Aftab Hussain

Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process. In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds. - These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.

Best 20 SEO Techniques To Improve Website Visibility In SERP

Pixlogix Infotech

Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack

shyamraj55

“I’m still / I’m still / Chaining from the Block”

Claudio Di Ciccio

GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...

Neo4j

Leonard Jayamohan, Partner & Generative AI Lead, Deloitte This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.

AI 101: An Introduction to the Basics and Impact of Artificial Intelligence

IndexBug

How to Get CNIC Information System with Paksim Ga.pptx

danishmna97

Driving Business Innovation: Latest Generative AI Advancements & Success Story

Safe Software

Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency. During the hour, we’ll take you through: Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board. Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes. Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI. We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI. This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!

Cosa hanno in comune un mattoncino Lego e la backdoor XZ?

Speck&Tech

ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune. Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile. BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).

Pushing the limits of ePRTC: 100ns holdover for 100 days

Adtran

Presentation of the OECD Artificial Intelligence Review of Germany

innovationoecd

Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf

Malak Abu Hammad

Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers: * What is Vector Search? * Importance and benefits of vector search * Practical use cases across various industries * Step-by-step implementation guide * Live demos with code snippets * Enhancing LLM capabilities with vector search * Best practices and optimization strategies Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications. #MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology

Mariano G Tinti - Decoding SpaceX

Mariano Tinti

Recently uploaded (20)

GenAI Pilot Implementation in the organizations

UiPath Test Automation using UiPath Test Suite series, part 6

Artificial Intelligence for XMLDevelopment

National Security Agency - NSA mobile device best practices

GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...

Serial Arm Control in Real Time Presentation

Removing Uninteresting Bytes in Software Fuzzing

Best 20 SEO Techniques To Improve Website Visibility In SERP

Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack

“I’m still / I’m still / Chaining from the Block”

GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...

AI 101: An Introduction to the Basics and Impact of Artificial Intelligence

How to Get CNIC Information System with Paksim Ga.pptx

Driving Business Innovation: Latest Generative AI Advancements & Success Story

Cosa hanno in comune un mattoncino Lego e la backdoor XZ?

Pushing the limits of ePRTC: 100ns holdover for 100 days

Presentation of the OECD Artificial Intelligence Review of Germany

Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf

Mariano G Tinti - Decoding SpaceX

PuppetConf 2016: Heresy in the Church of Docker – Corey Quinn, The Quinn Advisory Group

1. Heresy in the Church of Docker @QuinnyPig Corey Quinn The Quinn Advisory Group

2. Heresy in the Church of Docker Corey Quinn The Quinn Advisory Group @QuinnyPig

3. @QuinnyPig

4. That Time My Boss Destroyed a Cubicle Corey Quinn @QuinnyPig

10. @QuinnyPig

11. @QuinnyPig

12. @QuinnyPig

13. @QuinnyPig

14. @QuinnyPig

15. @QuinnyPig

16. Heresy in the Church of Docker @QuinnyPig Corey Quinn The Quinn Advisory Group

17. @QuinnyPig

18. @QuinnyPig

19. Docker is the first ever OS Container System @QuinnyPig

20. Docker is the first ever OS Container System •LXC @QuinnyPig

21. Docker is the first ever OS Container System •LXC •Solaris Zones @QuinnyPig

22. Docker is the first ever OS Container System •LXC •Solaris Zones •FreeBSD Jails @QuinnyPig

23. Docker is the first ever OS Container System •LXC •Solaris Zones •FreeBSD Jails •Chroots @QuinnyPig

24. Docker is the first ever OS Container System •LXC •Solaris Zones •FreeBSD Jails •Chroots •OpenVZ @QuinnyPig

25. Docker is the first ever OS Container System •LXC •Solaris Zones •FreeBSD Jails •Chroots •OpenVZ •LPARS @QuinnyPig

26. •LXC •Solaris Zones •FreeBSD Jails •Chroots •OpenVZ •LPARS •Virtualization(?) Docker is the first ever OS Container System @QuinnyPig

27. Docker is the first ever OS Container System •LXC •Solaris Zones •FreeBSD Jails •Chroots •OpenVZ •LPARS •Virtualization(?) •Vagrant @QuinnyPig

28.

29. @QuinnyPig

30. @QuinnyPig

31. @QuinnyPig

32. Interlude "What's a Microservice?" @QuinnyPig

33. Microservice Characteristics @QuinnyPig

34. Microservice Characteristics • Small, independent processes @QuinnyPig

35. Microservice Characteristics • Small, independent processes • Communicate with each other via API calls @QuinnyPig

36. Microservice Characteristics • Small, independent processes • Communicate with each other via API calls • Modular @QuinnyPig

37. Microservice Characteristics • Small, independent processes • Communicate with each other via API calls • Modular • Environment Agnostic @QuinnyPig

38. Microservice Characteristics • Small, independent processes • Communicate with each other via API calls • Modular • Environment Agnostic • Scalable development model @QuinnyPig

39. @QuinnyPig

40. @QuinnyPig

41. + @QuinnyPig

42. @QuinnyPig

43. @QuinnyPig

44. DockerDocker Development Production @QuinnyPig

45. DockerDocker Kubernetes Development Production @QuinnyPig

46.

47. DockerDocker Kubernetes Networking Development Production @QuinnyPig

48. DockerDocker Kubernetes Rolling Deployments Networking Development Production @QuinnyPig

49. DockerDocker Kubernetes Monitoring Rolling Deployments Networking Development Production @QuinnyPig

50. DockerDocker Kubernetes Supervision Monitoring Rolling Deployments Networking Development Production @QuinnyPig

51. DockerDocker Kubernetes Config Changes Supervision Monitoring Rolling Deployments Networking Development Production @QuinnyPig

52. DockerDocker Kubernetes Peer / Service discovery Config Changes Supervision Monitoring Rolling Deployments Networking Development Production @QuinnyPig

53. DockerDocker Kubernetes Container Hosting Peer / Service discovery Config Changes Supervision Monitoring Rolling Deployments Networking Development Production @QuinnyPig

54.

55. DockerDocker Kubernetes Code Quality Container Hosting Peer / Service discovery Config Changes Supervision Monitoring Rolling Deployments Networking Development Production @QuinnyPig

56. @QuinnyPig

57. DockerDocker Kubernetes Security Code Quality Container Hosting Peer / Service discovery Config Changes Supervision Monitoring Rolling Deployments Networking Development Production

58. OpenSSL: Less SSL, more Open @QuinnyPig

59. DockerDocker Kubernetes Security Code Quality Container Hosting Peer / Service discovery Config Changes Supervision Monitoring Rolling Deployments Networking Development Production @QuinnyPig

60. @QuinnyPig

61. @QuinnyPig

62. Based on a tweet by @mfdii + @julian_dunn @QuinnyPig

63. Suitably modified by @josh_atwell @QuinnyPig

64. @QuinnyPig practicalmonitoring.com

65. Corey Quinn Heresy in the Church of Docker @QuinnyPig