This document discusses managing PowerShell DSC with Puppet. It begins with an agenda that includes how Puppet Enterprise works, why use Puppet and DSC together, and a demo. It then discusses how Puppet automates machine provisioning and configuration. It explains that using Puppet and DSC together allows you to use existing skills to do more while gaining the benefits of both tools. It demos converting a DSC configuration to a Puppet manifest and shows how tracking changes is important for compliance.
This document provides an overview of using Puppet to deploy and manage IIS and ASP.NET on Windows servers. It discusses Puppet Enterprise and how it automates machine provisioning and application management. It then covers configuring and deploying IIS and ASP.NET using Puppet's Windows resources and management abstractions in a consistent and repeatable way. The document concludes with a demo and details on Puppet's Windows support and modules for managing technologies like SQL Server, WSUS, and Azure on Windows.
This document discusses using PowerShell and Desired State Configuration (DSC) for automation in DevOps. It introduces DSC as an extension to PowerShell that allows creating configuration scripts and files to ensure servers are configured as needed. DSC is presented as a tool that can help with challenges around application lifecycle management, release management, and ensuring consistent server configurations across environments like development, test, and production. Specific capabilities of DSC highlighted include authoring configurations, applying configurations through a staging process, and solving problems of managing different server roles, applications, and environments consistently through automation.
Puppet provides support for managing Windows environments including Windows servers, applications, and Azure virtual machines. Puppet's Windows support includes Puppet agents, core resources for managing files, registry keys, services, and more. Puppet also supports additional Windows technologies like IIS, SQL Server, PowerShell DSC, Chocolatey, and Azure virtual machines. The roadmap outlines continued improvements and support for additional Windows features, applications, and cloud platforms.
Windows Configuration Management: Managing Packages, Services, & Power Shell-...Puppet
This document discusses using Puppet to manage Windows configuration. It covers installing packages using Chocolatey, managing services like WSUS, and using PowerShell with Puppet. Puppet works by defining the desired configuration, simulating changes, enforcing the configuration, and reporting differences. The presenters demonstrate installing packages, managing services, and using PowerShell modules with Puppet. They also discuss Puppet support for Windows, including supported modules for tasks like SQL Server management, patching with WSUS, and using DSC resources.
This document provides an overview of using Puppet to manage infrastructure on Microsoft Azure. It begins with an introduction to Puppet and how Puppet Enterprise works to define infrastructure with code, gain situational awareness of changes, and orchestrate changes intelligently. It then discusses how Puppet can be used to manage Azure infrastructure, provides examples of Puppet modules for supporting Windows, and lists resources for learning more about Puppet on Windows and Azure. A demo is given of using Puppet to provision and manage VMs on Azure.
The document summarizes the new features in Puppet Enterprise. It discusses the new web UI and reporting capabilities, automated workflows for deployments, platform improvements including language enhancements and performance upgrades, and concludes by thanking the audience and inviting them to the next webinar on upgrading to Puppet Enterprise 2016.2.
Puppet Enterprise allows you to more effectively integrate OS patch management into a unified platform management approach. It ties together proven Microsoft technologies like WSUS and DSC to define OS update policies, manage patches as part of overall system configuration, and continuously enforce patching policies. The demo shows managing the WSUS client, packages with Chocolatey, and configuration with PowerShell using Puppet's unified approach.
What's New in Puppet Enterprise 2016.2 (EMEA)Puppet
Puppet Enterprise 2016.2 introduces several new features to help users troubleshoot configurations faster using change success reporting, discover and group servers more easily based on facts, run Puppet in Docker containers, and manage IBM z Systems and LinuxONE. It also provides integrated management of infrastructure and applications using a common language, simplifies management of IBM WebSphere, and allows driving change with confidence through phased deployments and real-time visibility into deployment results.
This document provides an overview of using Puppet to deploy and manage IIS and ASP.NET on Windows servers. It discusses Puppet Enterprise and how it automates machine provisioning and application management. It then covers configuring and deploying IIS and ASP.NET using Puppet's Windows resources and management abstractions in a consistent and repeatable way. The document concludes with a demo and details on Puppet's Windows support and modules for managing technologies like SQL Server, WSUS, and Azure on Windows.
This document discusses using PowerShell and Desired State Configuration (DSC) for automation in DevOps. It introduces DSC as an extension to PowerShell that allows creating configuration scripts and files to ensure servers are configured as needed. DSC is presented as a tool that can help with challenges around application lifecycle management, release management, and ensuring consistent server configurations across environments like development, test, and production. Specific capabilities of DSC highlighted include authoring configurations, applying configurations through a staging process, and solving problems of managing different server roles, applications, and environments consistently through automation.
Puppet provides support for managing Windows environments including Windows servers, applications, and Azure virtual machines. Puppet's Windows support includes Puppet agents, core resources for managing files, registry keys, services, and more. Puppet also supports additional Windows technologies like IIS, SQL Server, PowerShell DSC, Chocolatey, and Azure virtual machines. The roadmap outlines continued improvements and support for additional Windows features, applications, and cloud platforms.
Windows Configuration Management: Managing Packages, Services, & Power Shell-...Puppet
This document discusses using Puppet to manage Windows configuration. It covers installing packages using Chocolatey, managing services like WSUS, and using PowerShell with Puppet. Puppet works by defining the desired configuration, simulating changes, enforcing the configuration, and reporting differences. The presenters demonstrate installing packages, managing services, and using PowerShell modules with Puppet. They also discuss Puppet support for Windows, including supported modules for tasks like SQL Server management, patching with WSUS, and using DSC resources.
This document provides an overview of using Puppet to manage infrastructure on Microsoft Azure. It begins with an introduction to Puppet and how Puppet Enterprise works to define infrastructure with code, gain situational awareness of changes, and orchestrate changes intelligently. It then discusses how Puppet can be used to manage Azure infrastructure, provides examples of Puppet modules for supporting Windows, and lists resources for learning more about Puppet on Windows and Azure. A demo is given of using Puppet to provision and manage VMs on Azure.
The document summarizes the new features in Puppet Enterprise. It discusses the new web UI and reporting capabilities, automated workflows for deployments, platform improvements including language enhancements and performance upgrades, and concludes by thanking the audience and inviting them to the next webinar on upgrading to Puppet Enterprise 2016.2.
Puppet Enterprise allows you to more effectively integrate OS patch management into a unified platform management approach. It ties together proven Microsoft technologies like WSUS and DSC to define OS update policies, manage patches as part of overall system configuration, and continuously enforce patching policies. The demo shows managing the WSUS client, packages with Chocolatey, and configuration with PowerShell using Puppet's unified approach.
What's New in Puppet Enterprise 2016.2 (EMEA)Puppet
Puppet Enterprise 2016.2 introduces several new features to help users troubleshoot configurations faster using change success reporting, discover and group servers more easily based on facts, run Puppet in Docker containers, and manage IBM z Systems and LinuxONE. It also provides integrated management of infrastructure and applications using a common language, simplifies management of IBM WebSphere, and allows driving change with confidence through phased deployments and real-time visibility into deployment results.
SaltConf14 - Justin Carmony, Deseret Digital Media - Teaching Devs About DevOpsSaltStack
Let's set aside the buzzwords for a moment and have an honest discussion about DevOps. There is the idea of putting more Dev into Ops, but just as crucial (if not more crucial) is getting your Devs to think more like Ops. Most developers have little to no experience dealing with production environments, and helping them add value to DevOps efforts can be difficult. This talk will cover practical ways of mentoring Devs into more DevOps skills and responsibilities. Ultimately, the goal is to help your Devs gain the skills leading to better production health, application performance and uptime. Of course, we'll also consider how SaltStack can help.
Puppet Camp Charlotte 2015: Manage Your Switches Like ServersPuppet
Scott Suehle from Cumulus Networks presented on managing network switches like servers using Cumulus Linux. Cumulus Linux allows switches to be managed like Linux servers through tools like Puppet for configuration automation. It supports a wide range of hardware and provides zero-touch provisioning through scripts like Puppet to initially configure switches. Cumulus Linux uses Linux tools and processes for switch installation and management for improved collaboration between network and system teams.
Dev ops: Continuous delivery and Windows AzureIbon Landa
This document discusses various DevOps practices and tools for continuous delivery including Azure, Chef, Vagrant, Juju, and Release Management. It emphasizes automating infrastructure provisioning and application deployments, having well-defined and collaborative delivery processes, versioning everything, deploying the same way to every environment, and measuring the delivery process. Tools like Chef, Vagrant and Juju can be used to automatically install and configure software on virtual machines in Azure, OpenStack, or other cloud providers. Release Management helps automate .NET application deployments and provides analytics. The overall goal is to enable early and continuous delivery of valuable software to customers.
This document provides an introduction and agenda for a Puppet Enterprise presentation. It begins with introductions of the speakers and then discusses how Puppet Enterprise can help companies automate their infrastructure and applications to deliver software simply and at scale. It presents a live demo of how Puppet Enterprise works by defining configurations, simulating changes, and enforcing policies. Finally, it suggests next steps for audiences to learn more including contacting sales, downloading a free trial, and exploring self-paced trainings.
WinOps Conf 2016 - Jeffrey Snover - The DevOpsification of Windows ServerWinOps Conf
Everyone knows that DevOps is not about technology – it is about culture and process. But some technologies make some certain processes and cultures difficult and other technologies makes them easy.
This session explores why and how Windows Server 2016 was developed with DevOps in mind and what this means to customers adopting a devops workflow.
The document discusses the challenges of scaling Jenkins enterprise-wide and how the CloudBees Jenkins Platform (CJP) addresses them. It presents CJP as providing centralized plugin management, administration, security, analytics, and support that overcome limitations of open source Jenkins in scaling. Specifically, CJP allows for centralized security policies, horizontal scaling, analytics of builds and performance, and shared resources across environments.
Using the Atlassian Plugin Platform to Create Your Own SaaS Plugin PlatformAtlassian
The document discusses using the Atlassian Plugin Platform to build a plugin system for Qato, DZone's enterprise question and answer platform. Key points include leveraging the Atlassian framework to avoid reinventing the wheel, supporting multi-tenancy by tying plugins to the proper tenant, and allowing Spring annotations in plugins. The Atlassian Plugin Framework allowed DZone to quickly add extensibility to Qato through a plugin system.
Atlaskickin' the Plugin SDK, AtlasCamp US 2012Atlassian
Jonathan Doklovic, Developer Relations Engineer
The Atlassian SDK is what makes Atlassian plugin development possible. Jonathan Doklovic will run through the recent dev speed focused improvements we've made to the SDK and give you some productivity protips that will make developing plugins even more joyful.
AtlasCamp 2010: The Atlassian Plugin SDK For Fun & Profit - Ben SpeakmonAtlassian
The document discusses the challenges of plugin development and how the Atlassian Plugin SDK addresses them. It outlines problems like different startup processes, configuration locations, and installation methods across Atlassian products. The SDK standardizes these areas with tools like atlas-run, automatic configuration, and installation from the command line. It also improves the development cycle through features like hot reloading of code changes and testing against multiple versions. The presentation encourages involvement in the open source SDK project.
Automation for Anyone at Nutanix NEXT 2017 USChris Wahl
Are you wondering how to solve repetitive tasks with software automation, but you struggle every time you see the word “developer” or “code?” Do you know what APIs are and how they make these tasks easy to solve? In this session, we’ll explore the framework that can apply to mundane tasks (i.e. PowerShell, Pester), and we’ll discuss what open source tools are available to help solve these problems. Walk away with the advice you need to get started!
SaltConf14 - Craig Sebenik, LinkedIn - SaltStack at Web ScaleSaltStack
This talk will focus on the unique challenges of managing Web scale and an application stack that lives on tens of thousands of servers spread across multiple data centers. Learn more about LinkedIn's unique topology, about the development of an efficient build environment, and hear more about LinkedIn plans for a deployment system based on Salt. Also, all of the software that runs LinkedIn sends a LOT of data. In order to stay ahead of this tidal wave of data, the team must address scale challenges seen in very few environments through efficient use of monitoring and metrics systems. This talk will highlight best practices and user training necessary for the use of SaltStack in large environments.
Packing It In: Images, Containers and Config ManagementMichael Goetz
Learn about the many different tools gaining momentum to manage system configurations. Hear about when you should think about configuration management tools and when it might be OK to just pack it into a re-usable image. We’ll cover the basics around Docker and Packer before diving into a full-stack example leveraging all three topics in harmony together.
There is no doubt that security has been in the spotlight over the last few years, recent events have been responsible for the increased demand for better and more secure systems. Security was often treated as an afterthought or something that could be implemented ‘later’. In this session, we will go over some best practices, using existing tools and frameworks to help you set up a more secure environment and to get a grasp of what is happening in your environment. We will leverage your existing automation skills to secure and automate these workflows. Expect a session with a lot of demos and resources that can directly be implemented.
Steve Thair (DevOps Guys) - DevOps for Windows in the WildOutlyer
Steve talked about DevOps Guys experience working with several Windows customers, and how they did all the DevOps basics on Windows such as automation and deployments, and some best practices for those of you out there looking to implement DevOps on Windows yourselves!
Video: https://www.youtube.com/watch?v=YXxwUx3dP80
Join DevOps Exchange London here: http://www.meetup.com/DevOps-Exchange-London
Follow DOXLON on twitter http://www.twitter.com/doxlon
This document provides an introduction to Puppet Enterprise. It begins with an agenda for the meeting which includes an introduction to Puppet Enterprise and a live demo. It then introduces the speakers. It discusses how Puppet Enterprise helps companies become great software companies by automating tasks for speed, reliability and security across devices and through software stacks. It shows a demo of how Puppet Enterprise works with nodes requesting configurations and reporting. It recommends starting with automating core infrastructure before moving to application infrastructure and orchestration. Finally, it provides next steps for getting a demo, downloading Puppet Enterprise, and accessing training resources.
Desired State Configuration (DSC) is a technology introduced in Windows Management Framework 4.0 for declaratively configuring systems. It is a distributed, heterogeneous configuration management platform that uses resources and configurations to ensure systems are in the desired state. DSC resources can be built-in, from the DSC Resource Kit, community resources, or class-defined as of WMF 5.0. The document then provides a demo of using DSC for IIS configuration and discusses how DSC is a PowerShell language extension with built-in support for password encryption.
The document summarizes a DevOps 2016 Summit agenda. It includes presentations on Kubernetes DevOps by Ray Tsang from Google, DevOps powered by containers by Glenn West from Red Hat, Docker by a speaker from MediaTek, using Elasticsearch, Logstash and Kibana for log centralization and visualization, IoT Docker DevOps by Linker Network Software, shaking up culture with automation by a Yahoo Japan speaker, monitoring by a speaker from Gogolook, Chinese infrastructure by Sammy Lin, continuous integration/delivery by a speaker from Vpon, and what DevOps is through building on lean and agile practices.
Managing Windows Systems with Puppet - PuppetConf 2013Puppet
"Managing Windows Systems with Puppet" by James Sweeny Professional Services Engineer, Puppet Labs.
Presentation Overview: Since Puppet grew up in the *nix world, there is a common misconception that it can't be used to effectively manage Windows. This talk hopes to dispel confusion on the matter and demonstrate that Windows can be managed effectively and easily with Puppet. Along with basic how-tos and tips on working with Windows systems using Puppet, Windows specific issues and caveats will be discussed with effective mitigations.
Speaker Bio: James is a recovering sysadmin currently working as a Professional Services Engineer at Puppet Labs. He performs training and advises on configuration and systems management best practices in his day job. Though his focus is primarily on Linux systems, he frequently is tasked to work on Solaris, OS/X, and Windows. He is unafraid to admit that he runs Windows 7 on his primary desktop.
SaltConf14 - Justin Carmony, Deseret Digital Media - Teaching Devs About DevOpsSaltStack
Let's set aside the buzzwords for a moment and have an honest discussion about DevOps. There is the idea of putting more Dev into Ops, but just as crucial (if not more crucial) is getting your Devs to think more like Ops. Most developers have little to no experience dealing with production environments, and helping them add value to DevOps efforts can be difficult. This talk will cover practical ways of mentoring Devs into more DevOps skills and responsibilities. Ultimately, the goal is to help your Devs gain the skills leading to better production health, application performance and uptime. Of course, we'll also consider how SaltStack can help.
Puppet Camp Charlotte 2015: Manage Your Switches Like ServersPuppet
Scott Suehle from Cumulus Networks presented on managing network switches like servers using Cumulus Linux. Cumulus Linux allows switches to be managed like Linux servers through tools like Puppet for configuration automation. It supports a wide range of hardware and provides zero-touch provisioning through scripts like Puppet to initially configure switches. Cumulus Linux uses Linux tools and processes for switch installation and management for improved collaboration between network and system teams.
Dev ops: Continuous delivery and Windows AzureIbon Landa
This document discusses various DevOps practices and tools for continuous delivery including Azure, Chef, Vagrant, Juju, and Release Management. It emphasizes automating infrastructure provisioning and application deployments, having well-defined and collaborative delivery processes, versioning everything, deploying the same way to every environment, and measuring the delivery process. Tools like Chef, Vagrant and Juju can be used to automatically install and configure software on virtual machines in Azure, OpenStack, or other cloud providers. Release Management helps automate .NET application deployments and provides analytics. The overall goal is to enable early and continuous delivery of valuable software to customers.
This document provides an introduction and agenda for a Puppet Enterprise presentation. It begins with introductions of the speakers and then discusses how Puppet Enterprise can help companies automate their infrastructure and applications to deliver software simply and at scale. It presents a live demo of how Puppet Enterprise works by defining configurations, simulating changes, and enforcing policies. Finally, it suggests next steps for audiences to learn more including contacting sales, downloading a free trial, and exploring self-paced trainings.
WinOps Conf 2016 - Jeffrey Snover - The DevOpsification of Windows ServerWinOps Conf
Everyone knows that DevOps is not about technology – it is about culture and process. But some technologies make some certain processes and cultures difficult and other technologies makes them easy.
This session explores why and how Windows Server 2016 was developed with DevOps in mind and what this means to customers adopting a devops workflow.
The document discusses the challenges of scaling Jenkins enterprise-wide and how the CloudBees Jenkins Platform (CJP) addresses them. It presents CJP as providing centralized plugin management, administration, security, analytics, and support that overcome limitations of open source Jenkins in scaling. Specifically, CJP allows for centralized security policies, horizontal scaling, analytics of builds and performance, and shared resources across environments.
Using the Atlassian Plugin Platform to Create Your Own SaaS Plugin PlatformAtlassian
The document discusses using the Atlassian Plugin Platform to build a plugin system for Qato, DZone's enterprise question and answer platform. Key points include leveraging the Atlassian framework to avoid reinventing the wheel, supporting multi-tenancy by tying plugins to the proper tenant, and allowing Spring annotations in plugins. The Atlassian Plugin Framework allowed DZone to quickly add extensibility to Qato through a plugin system.
Atlaskickin' the Plugin SDK, AtlasCamp US 2012Atlassian
Jonathan Doklovic, Developer Relations Engineer
The Atlassian SDK is what makes Atlassian plugin development possible. Jonathan Doklovic will run through the recent dev speed focused improvements we've made to the SDK and give you some productivity protips that will make developing plugins even more joyful.
AtlasCamp 2010: The Atlassian Plugin SDK For Fun & Profit - Ben SpeakmonAtlassian
The document discusses the challenges of plugin development and how the Atlassian Plugin SDK addresses them. It outlines problems like different startup processes, configuration locations, and installation methods across Atlassian products. The SDK standardizes these areas with tools like atlas-run, automatic configuration, and installation from the command line. It also improves the development cycle through features like hot reloading of code changes and testing against multiple versions. The presentation encourages involvement in the open source SDK project.
Automation for Anyone at Nutanix NEXT 2017 USChris Wahl
Are you wondering how to solve repetitive tasks with software automation, but you struggle every time you see the word “developer” or “code?” Do you know what APIs are and how they make these tasks easy to solve? In this session, we’ll explore the framework that can apply to mundane tasks (i.e. PowerShell, Pester), and we’ll discuss what open source tools are available to help solve these problems. Walk away with the advice you need to get started!
SaltConf14 - Craig Sebenik, LinkedIn - SaltStack at Web ScaleSaltStack
This talk will focus on the unique challenges of managing Web scale and an application stack that lives on tens of thousands of servers spread across multiple data centers. Learn more about LinkedIn's unique topology, about the development of an efficient build environment, and hear more about LinkedIn plans for a deployment system based on Salt. Also, all of the software that runs LinkedIn sends a LOT of data. In order to stay ahead of this tidal wave of data, the team must address scale challenges seen in very few environments through efficient use of monitoring and metrics systems. This talk will highlight best practices and user training necessary for the use of SaltStack in large environments.
Packing It In: Images, Containers and Config ManagementMichael Goetz
Learn about the many different tools gaining momentum to manage system configurations. Hear about when you should think about configuration management tools and when it might be OK to just pack it into a re-usable image. We’ll cover the basics around Docker and Packer before diving into a full-stack example leveraging all three topics in harmony together.
There is no doubt that security has been in the spotlight over the last few years, recent events have been responsible for the increased demand for better and more secure systems. Security was often treated as an afterthought or something that could be implemented ‘later’. In this session, we will go over some best practices, using existing tools and frameworks to help you set up a more secure environment and to get a grasp of what is happening in your environment. We will leverage your existing automation skills to secure and automate these workflows. Expect a session with a lot of demos and resources that can directly be implemented.
Steve Thair (DevOps Guys) - DevOps for Windows in the WildOutlyer
Steve talked about DevOps Guys experience working with several Windows customers, and how they did all the DevOps basics on Windows such as automation and deployments, and some best practices for those of you out there looking to implement DevOps on Windows yourselves!
Video: https://www.youtube.com/watch?v=YXxwUx3dP80
Join DevOps Exchange London here: http://www.meetup.com/DevOps-Exchange-London
Follow DOXLON on twitter http://www.twitter.com/doxlon
This document provides an introduction to Puppet Enterprise. It begins with an agenda for the meeting which includes an introduction to Puppet Enterprise and a live demo. It then introduces the speakers. It discusses how Puppet Enterprise helps companies become great software companies by automating tasks for speed, reliability and security across devices and through software stacks. It shows a demo of how Puppet Enterprise works with nodes requesting configurations and reporting. It recommends starting with automating core infrastructure before moving to application infrastructure and orchestration. Finally, it provides next steps for getting a demo, downloading Puppet Enterprise, and accessing training resources.
Desired State Configuration (DSC) is a technology introduced in Windows Management Framework 4.0 for declaratively configuring systems. It is a distributed, heterogeneous configuration management platform that uses resources and configurations to ensure systems are in the desired state. DSC resources can be built-in, from the DSC Resource Kit, community resources, or class-defined as of WMF 5.0. The document then provides a demo of using DSC for IIS configuration and discusses how DSC is a PowerShell language extension with built-in support for password encryption.
The document summarizes a DevOps 2016 Summit agenda. It includes presentations on Kubernetes DevOps by Ray Tsang from Google, DevOps powered by containers by Glenn West from Red Hat, Docker by a speaker from MediaTek, using Elasticsearch, Logstash and Kibana for log centralization and visualization, IoT Docker DevOps by Linker Network Software, shaking up culture with automation by a Yahoo Japan speaker, monitoring by a speaker from Gogolook, Chinese infrastructure by Sammy Lin, continuous integration/delivery by a speaker from Vpon, and what DevOps is through building on lean and agile practices.
Managing Windows Systems with Puppet - PuppetConf 2013Puppet
"Managing Windows Systems with Puppet" by James Sweeny Professional Services Engineer, Puppet Labs.
Presentation Overview: Since Puppet grew up in the *nix world, there is a common misconception that it can't be used to effectively manage Windows. This talk hopes to dispel confusion on the matter and demonstrate that Windows can be managed effectively and easily with Puppet. Along with basic how-tos and tips on working with Windows systems using Puppet, Windows specific issues and caveats will be discussed with effective mitigations.
Speaker Bio: James is a recovering sysadmin currently working as a Professional Services Engineer at Puppet Labs. He performs training and advises on configuration and systems management best practices in his day job. Though his focus is primarily on Linux systems, he frequently is tasked to work on Solaris, OS/X, and Windows. He is unafraid to admit that he runs Windows 7 on his primary desktop.
How Puppet Enables the Use of Lightweight Virtualized Containers - PuppetConf...Puppet
The document summarizes how Puppet can be used to enable lightweight virtualized containers by configuring applications and their dependencies into immutable container images during the build process. It compares deploying a Jenkins application with LDAP authentication on virtual machines versus containers. It discusses challenges with service resources in containers and provides solutions like overriding service resources or using multi-process images with systemd to build immutable Puppet-configured application images.
AnsibleFest 2015 was a day-long series of learning seminars by Ansible developers. Our IT Operations Manager, Marius was one of the speakers and he presented “How to Automate Big Data with Ansible”.
Full Stack Automation with Katello & The ForemanWeston Bassler
This document summarizes a presentation about FullStackAutomationwithKatelloandForeman. It introduces the presenters Justin Miller and Weston Bassler and their backgrounds. The presentation covers the Foreman project, Katello project, and how they work together. Foreman is an open source tool for provisioning, configuring, and managing servers. Katello adds content management capabilities like repositories and subscriptions. The document outlines key features of provisioning, configuration, repositories, subscriptions, and more. It includes links to demo videos showcasing functions like host discovery, bulk actions, and Docker integration.
Linux host orchestration with Foreman, Puppet and GitlabBen Tullis
A brief look at the Foreman host lifecycle management system, beginning with its rapid provisioning features and moving onto its integration with the Puppet configuration management system.
GItlab is introduced to the mix and an example is given of how it can be integrated with Forman and Puppet to form an on-premise configuration versioning component. This configuration, which builds upon the Puppet multiple environments feature, is currently being employed in the task of building a test-driven continuous delivery system for the OpenCorporates project.
Foreman is a lifecycle management tool for physical and virtual servers, that has traditionally been Puppet-centric. There are now several plugins for additional configuration management systems, including Salt. This talk will demo provisioning a new minion, applying states, viewing grains, setting pillars and more -- all from within the Foreman UI.
Windows PowerShell Desired State Configuration (DSC) for Veteran Chefs - Chef...Chef
This document compares the configuration management tools Chef and DSC (Desired State Configuration) from Microsoft. Both Chef and DSC support configuration as code, domain-specific languages, idempotent operations, and convergence to manage node configurations. DSC uses PowerShell as its scripting language and has resources and properties to define configurations. Chef uses Ruby as its scripting language and has resources defined with attributes. The document provides examples of configuring an environment variable using both tools and recommends sessions to attend at a Chef conference focused on DSC, PowerShell, and automating configurations.
Building and Managing your Virtual Datacenter using PowerShell DSC - Florin L...ITCamp
PowerShell DSC is a configuration management platform that provides the operations team the capability to deploy and manage systems by defining the desired configuration of a machine while having the assurance that whatever happens, the machines configuration will remain the same.
In this session you will learn what is PowerShell DSC, and how it can grant you the power of implementing a DevOps oriented environment by building and managing your infrastructure in an automatic and consistent fashion.
Package Management on Windows with ChocolateyPuppet
This document discusses using Puppet and Chocolatey for package management on Windows systems. It provides an overview of how Puppet works, why Chocolatey is useful as a package manager for Windows, how to use the Chocolatey Puppet provider to manage packages, how to create Chocolatey packages, host your own Chocolatey package server, and resources for learning more about Puppet and Windows management. It also includes an agenda for the content covered and a question and answer section.
--session donnée dans le cadre du 24HOP Francophone--
http://www.sqlpass.org/24hours/2016/french/Sessions.aspx
Les données sont le nouveau pétrole ? Alors vous avez besoin de pipelines.
Azure Data Factory est la solution pour déplacer des données entre vos briques de stockage ou de calcul, qu’elles soient dans le Cloud ou dans votre Data Center.
Dans cette session, vous découvrirez cette technologie et comment construire votre 1er pipeline.
Puppet Enterprise is an automation platform that allows organizations to define their infrastructure in code and automatically enforce configurations across their environments. It was demonstrated how Puppet defines infrastructure using a common language and automates configuration through a workflow of defining the desired state, simulating changes, and enforcing configurations on nodes. Benefits shown include significant increases in deployment speed, reductions in outages and security fix time, and improvements in successful audits. Puppet provides unique capabilities like abstraction and works across datacenters, clouds, and containers at enterprise scale.
PuppetConf 2017: Puppet Development Kit: A Seamless Workflow for Module Devel...Puppet
The Puppet Development Kit (PDK) provides tools to help developers easily create high-quality Puppet modules. It includes tools for testing, linting, and validating modules. Using the PDK improves the module development experience and helps ensure modules are configured correctly and ready to use. The PDK is designed for both new and experienced Puppet users and makes it easier to get started with best practices like testing and code quality checks.
OpenStack Summit 2013 Hong Kong - OpenStack and WindowsAlessandro Pilotti
OpenStack summit session about how to deploy Windows instances using Cloudbase-Init and Heat!
The session takes care of explaining all the issues you might encounter, for example how to choose the rioght KVM VirtIO drivers.
This document provides information about DevOps training courses offered by a company. It details the different training modes including classroom and online options. The classroom training is offered on weekends or weekdays. The online training is interactive and offered regularly or on weekends. The courses cover Docker, Puppet, Jenkins and include hands-on labs. Upon completion, students receive a course completion certificate and can work on a proof of concept project. An external DevOps certification is also offered.
This document provides information about DevOps training courses offered by a company. It details the different training modes including classroom and online options. The classroom training is offered on weekends or weekdays. The online training is interactive and offered regularly or on weekends. The courses cover Docker, Puppet, Jenkins and include hands-on learning. Upon completion, students will receive a course completion certificate and can work on a proof of concept project to earn a DevOps Associate Certificate.
This document provides information about DevOps training courses offered by a company. It details the different training modes including classroom and online options. The classroom training is offered on weekends or weekdays. The online training is interactive and offered regularly or on weekends. The courses cover Docker, Puppet, Jenkins and include hands-on labs. Upon completion, students receive a course completion certificate and can work on a proof of concept project. An external DevOps certification is also offered.
This document provides information about DevOps training courses offered by a company. It details the different training modes including classroom and online, topics that will be covered like Docker, Puppet, and Jenkins, prerequisites, and target audience. Hands-on projects are included to build a web server and install monitoring tools. Upon completion, students receive a certificate and can get assistance obtaining an external DevOps certification. Top companies seeking DevOps professionals are listed and the training is designed to provide practical experience on cloud servers.
This document provides information about DevOps training courses offered by a company. It details the different training modes including classroom and online options. The classroom training is offered on weekends or weekdays. The online training is interactive and offered regularly or on weekends. The courses cover Docker, Puppet, Jenkins and include hands-on learning and projects. Successful students will receive a course completion certificate and can pursue a DevOps Associate Certificate by completing a proof of concept project.
This document provides information about DevOps training courses offered by a company. It details the different training modes including classroom and online options. The classroom training is offered on weekends or weekdays. The online training is interactive and offered regularly or on weekends. The courses cover Docker, Puppet, Jenkins and include hands-on labs. Upon completion, students will receive a course completion certificate and can optionally work on a proof of concept project to earn a DevOps Associate Certificate.
This document provides information about DevOps training courses offered by a company. It details the different training modes including classroom and online options. The classroom training is offered on weekends or weekdays. The online training is interactive and offered regularly or on weekends. The courses cover Docker, Puppet, Jenkins and include hands-on labs. Upon completion, students receive a course completion certificate and can work on a proof of concept project and optional certification assistance.
Meet Puppet's new product lineup.
As we enter a new age of automation — where every company needs to be able to deliver better software, faster — our goal is to provide the tools you need to iterate faster, ship sooner and deliver more customer value.
Earlier this month, we announced brand new products, Puppet Tasks™ and Puppet Discovery™, to give you greater control and end-to-end visibility over your software delivery. We also introduced exciting updates to Puppet Enterprise and a new integration with Splunk.
Join Nigel Kersten, Chief Technical Strategist, and Tim Zonca, VP of Marketing, on 26 October from 4:30 - 5:30 p.m. PT for an in-depth look at what’s new:
Puppet Discovery is a new offering that lets you see everything you have in real time across your on-premises, cloud and container infrastructure, and know what you need to automate next.
Puppet Tasks, a new family of offerings that encompass both Puppet Bolt™ and Puppet Enterprise Task Management, makes it simple to automate ad hoc tasks, deploy one-off changes, and execute sequenced actions in an imperative way.
Our new integration with Splunk provides a unified workflow between the intelligence provided by Splunk and the automation provided by Puppet, giving you the power to turn insights into action faster.
With Distelli joining Puppet, we’re uniting the entire software delivery lifecycle, to bring you a platform built for the enterprise, that integrates with a wide variety of tools and helps you avoid vendor lock-in.
What's new in Docker - InfraKit - Docker Meetup Berlin 2016Patrick Chanezon
This document provides an overview of Docker and its products and initiatives:
1. Docker provides tools for container isolation using Linux kernel features like namespaces and cgroups. It also utilizes image layers for packaging applications.
2. Docker's products focus on the developer experience through tools like Docker for Mac/Windows, as well as orchestration with Swarm mode and services in Docker 1.12.
3. For operations, Docker provides tools to integrate with load balancers, templates, and other infrastructure through products like Docker Universal Control Plane and Docker Cloud. Docker is building tools to program infrastructure as code.
As we enter a new age of automation — where every company needs to be able to deliver better software, faster — our goal is to provide the tools you need to iterate faster, ship sooner and deliver more customer value.
In October, we announced brand new products, Puppet Tasks™ and Puppet Discovery™, to give you greater control and end-to-end visibility over your software delivery.
Join Eric Sorenson, Director of Product Management, on 7 December at 11:00 a.m. AEDT for an in-depth look at what’s new:
Puppet Discovery is a new offering that lets you see everything you have in real time across your on-premises, cloud and container infrastructure, and know what you need to automate next.
Puppet Tasks, a new family of offerings that encompass both Puppet Bolt™and Puppet Enterprise Task Management, makes it simple to automate ad hoc tasks, deploy one-off changes, and execute sequenced actions in an imperative way.
With Puppet Pipelines, we’re uniting the entire software delivery lifecycle, to bring you a platform built for the enterprise, that integrates with a wide variety of tools and helps you avoid vendor lock-in.
The document introduces the Puppet Development Kit (PDK) which provides tools to help developers easily adapt existing Puppet modules and create new modules. It describes how the PDK includes tools to generate module skeletons with tests, convert older modules to integrate validation and testing, and update modules to stay current with PDK best practices through the 'pdk convert' and 'pdk update' commands. The PDK is presented as providing benefits like standardized development workflows, pre-configured tools for linting, syntax and unit testing, and publishing modules to the Puppet Forge in a standardized way.
Nigel Kersten presented on Puppet and infrastructure automation. Some key points include:
- Puppet is an open source tool for infrastructure automation and application deployment. It uses a declarative language to define and enforce the desired state of systems.
- Puppet Enterprise builds on Puppet to add features for reporting, workflows, access control and more.
- Related tools like MCollective, PuppetDB, Facter and Hiera work together to provide orchestration, inventory, hierarchical data and other capabilities.
- Puppet Labs is continually improving Puppet and related tools while also growing its customer base and hiring more employees.
Azure Resource Manager templates: Improve deployment time and reusabilityStephane Lapointe
Azure Resource Manager is the future of Azure and his templating features are a big improvement and simplification of how you provision resources on Azure. See how you can create ARM template in Visual Studio to create complex, multiple resources templates and how they can be combined and reused. Learn the different template functions available and how they can help you build more advanced template.
This document provides an introduction to PowerShell for database developers. It begins by stating the goals of the presentation which are to amaze with PowerShell capabilities, convince that PowerShell is needed, provide a basic understanding of PowerShell programming, and point to support resources. It then provides an overview of what PowerShell is, including its history and why Windows needed a shell. It discusses PowerShell concepts like cmdlets, variables, operators, loops, and functions. It also provides examples of PowerShell scripts and best practices. Throughout it emphasizes PowerShell's power and integration with Windows and databases.
In this presentation, we start by briefly talking about why configuration management and automation tools are becoming increasingly important along with our general approach and the community that supports it. We will also provide a comprehensive overview of the technologies used with Puppet, so expect to learn more about Puppet Enterprise, Puppet, PuppetDB, MCollective, Forge and more. Other programs that help people learn about Puppet, like training and certification programs are also included.
This document provides an overview of Puppet and Puppet Enterprise. It summarizes the key components and projects that make up Puppet like Puppet, Facter, Hiera, MCollective and PuppetDB. It describes the capabilities of Puppet Enterprise like configuration management, orchestration, discovery, provisioning and reporting. The document also provides community growth metrics and information on training offered by Puppet Labs.
The document provides information about three Microsoft resources for technical training and software evaluation: the TechNet Evaluation Center, IT Camps, and Microsoft Virtual Academy. The TechNet Evaluation Center allows downloading free trials of Microsoft software. IT Camps are free, hands-on technical training events led by Microsoft experts. Microsoft Virtual Academy provides free online technical courses on Microsoft technologies.
This document contains slides from a presentation about Puppet, an open source configuration management tool. It discusses Puppet's architecture, components like Facter, Hiera and MCollective, and how Puppet can be used to automate infrastructure configuration and deployment. It also promotes joining the Puppet community, taking training courses, and encourages questions.
Similar to Managing PowerShell DSC with Puppet (20)
Puppet camp2021 testing modules and controlrepoPuppet
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.
This document appears to be for a PuppetCamp 2021 presentation by Corey Osman of NWOPS, LLC. It includes information about Corey Osman and NWOPS, as well as sections on efficient development, presentation content, demo main points, Git strategies including single branch and environment branch strategies, and workflow improvements. Contact information is provided at the bottom.
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.
This document provides tips and tricks for using Puppet with VS Code, including links to settings examples and recommended extensions to install like Gitlens, Remote Development Pack, Puppet Extension, Ruby, YAML Extension, and PowerShell Extension. It also mentions there will be a demo.
- 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 codePuppet
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.
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 automationPuppet
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.
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 + ServiceNowPuppet
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.
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. 2020Puppet
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.
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.
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 ReeuwijkPuppet
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.
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 SoftwarePuppet
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.
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.
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 MaludyPuppet
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.
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
inQuba Webinar Mastering Customer Journey Management with Dr Graham HillLizaNolte
HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable.
In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed:
Key Takeaways:
Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement.
Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers.
Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.
The Department of Veteran Affairs (VA) invited Taylor Paschal, Knowledge & Information Management Consultant at Enterprise Knowledge, to speak at a Knowledge Management Lunch and Learn hosted on June 12, 2024. All Office of Administration staff were invited to attend and received professional development credit for participating in the voluntary event.
The objectives of the Lunch and Learn presentation were to:
- Review what KM ‘is’ and ‘isn’t’
- Understand the value of KM and the benefits of engaging
- Define and reflect on your “what’s in it for me?”
- Share actionable ways you can participate in Knowledge - - Capture & Transfer
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
ScyllaDB is making a major architecture shift. We’re moving from vNode replication to tablets – fragments of tables that are distributed independently, enabling dynamic data distribution and extreme elasticity. In this keynote, ScyllaDB co-founder and CTO Avi Kivity explains the reason for this shift, provides a look at the implementation and roadmap, and shares how this shift benefits ScyllaDB users.
AI in the Workplace Reskilling, Upskilling, and Future Work.pptxSunil Jagani
Discover how AI is transforming the workplace and learn strategies for reskilling and upskilling employees to stay ahead. This comprehensive guide covers the impact of AI on jobs, essential skills for the future, and successful case studies from industry leaders. Embrace AI-driven changes, foster continuous learning, and build a future-ready workforce.
Read More - https://bit.ly/3VKly70
"What does it really mean for your system to be available, or how to define w...Fwdays
We will talk about system monitoring from a few different angles. We will start by covering the basics, then discuss SLOs, how to define them, and why understanding the business well is crucial for success in this exercise.
From Natural Language to Structured Solr Queries using LLMsSease
This talk draws on experimentation to enable AI applications with Solr. One important use case is to use AI for better accessibility and discoverability of the data: while User eXperience techniques, lexical search improvements, and data harmonization can take organizations to a good level of accessibility, a structural (or “cognitive” gap) remains between the data user needs and the data producer constraints.
That is where AI – and most importantly, Natural Language Processing and Large Language Model techniques – could make a difference. This natural language, conversational engine could facilitate access and usage of the data leveraging the semantics of any data source.
The objective of the presentation is to propose a technical approach and a way forward to achieve this goal.
The key concept is to enable users to express their search queries in natural language, which the LLM then enriches, interprets, and translates into structured queries based on the Solr index’s metadata.
This approach leverages the LLM’s ability to understand the nuances of natural language and the structure of documents within Apache Solr.
The LLM acts as an intermediary agent, offering a transparent experience to users automatically and potentially uncovering relevant documents that conventional search methods might overlook. The presentation will include the results of this experimental work, lessons learned, best practices, and the scope of future work that should improve the approach and make it production-ready.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
What is an RPA CoE? Session 2 – CoE RolesDianaGray10
In this session, we will review the players involved in the CoE and how each role impacts opportunities.
Topics covered:
• What roles are essential?
• What place in the automation journey does each role play?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Getting the Most Out of ScyllaDB Monitoring: ShareChat's TipsScyllaDB
ScyllaDB monitoring provides a lot of useful information. But sometimes it’s not easy to find the root of the problem if something is wrong or even estimate the remaining capacity by the load on the cluster. This talk shares our team's practical tips on: 1) How to find the root of the problem by metrics if ScyllaDB is slow 2) How to interpret the load and plan capacity for the future 3) Compaction strategies and how to choose the right one 4) Important metrics which aren’t available in the default monitoring setup.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
"NATO Hackathon Winner: AI-Powered Drug Search", Taras KlobaFwdays
This is a session that details how PostgreSQL's features and Azure AI Services can be effectively used to significantly enhance the search functionality in any application.
In this session, we'll share insights on how we used PostgreSQL to facilitate precise searches across multiple fields in our mobile application. The techniques include using LIKE and ILIKE operators and integrating a trigram-based search to handle potential misspellings, thereby increasing the search accuracy.
We'll also discuss how the azure_ai extension on PostgreSQL databases in Azure and Azure AI Services were utilized to create vectors from user input, a feature beneficial when users wish to find specific items based on text prompts. While our application's case study involves a drug search, the techniques and principles shared in this session can be adapted to improve search functionality in a wide range of applications. Join us to learn how PostgreSQL and Azure AI can be harnessed to enhance your application's search capability.
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Managing PowerShell DSC with Puppet
1. Managing PowerShell DSC with Puppet
Ethan Brown
Technical Lead, Windows Engineering
James Pogran
Software Engineer,
Author of Learning PowerShell DSC
2. Agenda
• How Puppet Enterprise works
• Why Puppet and DSC
• Demo
• Puppet Labs Windows support
• Resources
• Q&A
3. Our software
automates the provisioning,
configuration &
ongoing management
of your machines & the applications,
services & software running on them.
6. Why Puppet and DSC
• Use the skills you have to do more
• DSC and Puppet: Best of both worlds
• Tracking and reporting on change
7. Use the skills you have to do more
• Migrate a DSC Configuration script to a Puppet manifest with
a few text edits
• Puppet DSL is similar to PowerShell DSC syntax
• Less code when used together
9. DSC and Puppet: Best of Both Worlds
• 200+ DSC Resources made by Microsoft and the community
• 4000+ modules made by Puppet and the community
• Interoperable with multiple platforms
10. Best of Both Worlds: Immediate Value
• Solving problems using
the strengths of Puppet
and DSC
12. Best of Both Worlds: Advanced Scenario
• Let’s deploy an ASP.NET 4.5.2 website
– Puppet reduces the number of steps to get IIS installed
– DSC IIS module has more features
– Also posted here: https://puppetlabs.com/blog/dsc-deep-dive-
installing-and-configuring-iis-using-puppet-and-powershell-dsc
14. Tracking and Reporting on Change
• Reporting is a must for have any company that has to do any
kind of compliance auditing
• Track changes across your environment to ensure the correct
state
• Knowing when something broke is just as important as
knowing what broke
19. Summary
• Use the skills you have to do more
• DSC and Puppet: Best of both worlds
• Tracking and reporting on change
20. Puppet Labs Windows Support
• 32- & 64-bit Support – Native MSI packages for x64 as of Puppet
Enterprise 3.7
• Broad Platform Support - Windows 2008, 2012, 7, 8, 10
• Windows Provisioning - Provision Windows OSes with Razor
• Puppet Supported & Approved Modules for Windows – Including
Windows Module Pack, Supported SQL Sever & DSC modules
• Azure Integration – Microsoft Azure extension handler for
bootstrapping Puppet installs. Supported Azure module.
21. Puppet Supported Modules
• SQL Server – Installs & manages MS SQL Server 2012 & 2014 on
Windows systems
• WSUS Client – Configure clients to point to update servers; schedule
updates
• DSC – Manages PowerShell DSC resources
• Azure – Provision and manage Azure VMs
• ACL – manage permissions with Windows ACLs
• Registry – manage Registry keys and values
• PowerShell – execute PowerShell commands with Puppet
• Reboot – Automatically reboot after install
22. Puppet Approved Modules
• IIS – install and manage IIS
• Chocolatey – package manager
• windows_env – manage Windows environment variables
• Windows Java – Install and manage Oracle Java on Windows
• pget – PowerShell alternative to wget or curl
23. Windows Webinar Series
Register for upcoming webinars at: http://info.puppetlabs.com/1885-
Windows-Series-Main_LP-Registration.html
• Patch Management on Windows with Puppet
• Setting up Windows for System and Application Monitoring
• Getting Up and Running with the Windows Module Pack
• Get Started on Azure with Puppet
25. Resources
PuppetConf 2015 Windows Track
• Chocolatey and Puppet - Rob Reynolds
• Azure for the Non-Microsoft Person - Rob Reynolds & Scott Hanselman, MSFT
• Better Together: Managing Windows with Puppet and DSC - Ethan Brown & Bruce Payette,
MSFT
Blog
• Chocolatey blog series
• PowerShell DSC blog series
Docs
• Managing Windows Configurations
Books
• Learning PowerShell DSC by James Pogran
Education
• Learning VM
• Puppet Essentials for Windows – Instructor-led
• Puppet Essentials for Windows - Virtual
Editor's Notes
My name is James Pogran. I've been working on automating systems on the Windows platform for over 14 years. Now I'm a developer at Puppet Labs working to make automation in Windows even better.
I used PowerShell DSC at my last job to deploy a large client/server application in production. There was no documentation at the time, so I wrote my own book called Learning PowerShell DSC, to help others who were struggling with DSC.
While you can use DSC on it's own, it's so much better with Puppet. Today I will be talking about using Puppet and PowerShell DSC together, what the benefits are, and provide some real world use cases.
Our software helps you automate the configuration and ongoing management of your machines and the software running on them, so you spend less time fighting fires and more time deploying great software.
We help you make rapid, repeatable changes and automatically enforce the consistency of systems and devices–across physical and virtual machines, on prem or in the cloud.
Thanks for that great introduction to Puppet. We have covered why Puppet is important tool to have and how it works, but why should you use Puppet and PowerShell DSC?
Whether you are new to Puppet or have been using it for years, there are lots of reasons for using Puppet and DSC together.
Today we are going to talk about three reasons Puppet and DSC can work together to enable you to do more. I will go over each reason in more detail as we proceed, but I’ll quickly summarize the points right now.
Puppet enables you to use the skills you already have to do more
The Puppet DSL is similar to DSC syntax, so you can get up and running quickly
You can migrate a DSC Configuration script to a Puppet manifest with just a few text edits
Overall there is less code when you use them together
With DSC and Puppet you get all of the advantages of both worlds
There are thousands of resources made by Puppet, Microsoft and the community that you can use right away
You immediately become able to handle multiple platforms that cover your entire environment
Puppet provides rich management capabilities that you can layer on top of DSC, including node classification, status of nodes, role based access control, and more
Tracking and reporting on change becomes easier
Knowing when something broke is just as important as knowing when something succeeded
Reporting is a must have for have any company that has to do any kind of compliance auditing
Now that was a quick run through. Lets go through these one by one
First off, doing more with less sounds like a cliché, but it's a fact of life for any sysadmin or developer. Time and resource constraints necessitate flexibility and resourcefulness.
You will get productive fast with Puppet and DSC. Converting an existing PowerShell DSC Configuration script to a Puppet manifest is just a few text edits.
With Puppet you can take your existing PowerShell DSC skills and knowledge and apply them directly to fixing the problem at hand without having to learn everything upfront. As you do more, you can delve deeper, but you can get going quickly.
Oftentimes a Puppet manifest has less code to write than a PowerShell DSC configuration script. We’ll see more of how this works later in our demos.
Let’s get started
On the left is a PowerShell DSC configuration script, on the right is a Puppet manifest. It is a direct port from the DSC script. In it we are compressing a log directory and ensuring that a file is present on the file system with specific text inside it.
If you're new to Puppet but PowerShell is familiar, you'll be right at home using the Puppet DSC module. Even if you are not familiar, its so human readable that you can see what’s going on right away.
DSC works a lot like Puppet in many ways: it's declarative, uses a similar syntax, and similar terminology. Right away, you can see that there are only a few syntactical differences you need to account for when migrating to a Puppet manifest.
You have to add a ‘dsc_’ prefix to all resource declarations and to all parameters.
Your equal signs turn into hash rockets
Commas are added at the end of each value
These are simple, short changes that make sense. The syntax is so similar, there isn't any cognitive dissonance. Switching from a PowerShell DSC Resource to a Puppet module declaration is really just a few text edits and then you’re done.
You’ll start to notice that there is less to write using Puppet. No configuration blocks to add, no DSC Resource module import declarations to keep track of, just the individual components you need.
All PowerShell DSC types are supported, including base types like integers and Booleans, complex types like PSCredentials and any custom type bindings that you may use.
Now that we have covered how to transition to a Puppet manifest using DSC, we’ll talk about what you can DO with Puppet and DSC
A key part of any sysadmin or developers life is re-using good tools and code. If there is something good out there, use it. If someone else has already solved the problem, use their solution. We stand on shoulders of giants when we work together.
That’s why the Puppet DSC module enables you to use the 200+ PowerShell DSC Resources that have already been released and tested by the PowerShell community. Some of these resources cover scenarios not yet addressed by Puppet, providing immediate value. Like Lego pieces, you can mix and match the DSC Resources and Puppet modules to address any situation you encounter.
And when you come to something that DSC can’t do yet or a platform that it doesn’t yet support, you can look toward the existing 4,000+ Puppet modules to have your back. Puppet supports almost all OS and platforms under the sun: Windows, Linux, Network devices, storage arrays, etc, allowing you to cover your entire environment using first class modules and best practices.
Let’s look at a real world example showing how you can mix and match DSC and Puppet to get the job done
DSC is a powerful platform, but it’s a new technology. Like many new products, it needs to choose which features to implement first. Like Jeffey Snover says, to ship is to choose. This is not a bad thing, its focusing on delivering value first and getting it right. Then fill in the edges as time goes on. This does result in some waiting, but as we will see in a moment we can address that now.
In this slide we see a PowerShell community member asking for the ability to restart a service when it’s configuration file has changed. Dave Wyatt, one of the maintainers of Pester, replies that it’s a big wishlist item for him, and that he currently works around it by using a Script DSC Resource. It’s a good workaround, but you have to do all the work to ensure the Script DSC Resource is idempotent, i.e. that it only changes the state of the system if it is not in the desired state. It’s extra work for you, and something that isn’t portable. You will have to modify it for every individual service.
While we wait for the shipping cycle for PowerShell DSC, we can use Puppet WITH DSC to solve this problem right now.
Here we are installing the awesome Foo Product software on our target node using Puppet and PowerShell DSC. Foo Product has a configuration file it uses which allows users to change certain behavior in the program. We need to update the configuration file after the product is installed, which requires us to restart the service.
We model this by declaring a PowerShell DSC Package resource that will handle installing the MSI for us.
We then use a Puppet File module to ensure the file is present on the target node, and contains the exact text we want.
Lastly we set the Puppet Service module to ensure the service is running.
Notice the line in the File declaration where it says it will notify the Service module. This means that if the File module changes anything, it will send a notification to Puppet to tell the Service module to perform a refresh. The Service module doesn’t know anything about the config file, or when it changes, it just receives the notification from Puppet that it needs to refresh, or restart. These change notifications, along with many other features make Puppet a really powerful way to model and control change in your environment.
Lets run this example now.
This was a nice simple example, but doesn’t really show anything too fancy. Let’s move onto something more complicated.
We just showcased how you can use Puppet and DSC together in a simple example. Now lets show something more complicated by deploying an ASP.NET Website.
This is more complicated because there are several software requirements needed for a ASP.NET website to run (IIS, .NET 4.5.2, etc) as well as some configuration settings (ApplicationPool, directories, files) that need to be set correctly.
We’re using DSC along with Puppet because the IIS DSC Resource has some pretty nice features in it that we’ll use here to get a website up and running quickly.
We won’t go into too much detail of setting up an ASP.NET website because I’ve written a blog post walking you through the steps on the Puppet Blog in our DSC Deep Dive series. If you want more information on the example, go there and read all about it!
Lets get started
I’m going to run this demo while I talk, so that we aren’t all watching a screen scroll quietly by.
In this demo we ported an existing PowerShell DSC Configuration script to a Puppet manifest. When we move to the Puppet manifest, we immediately see a reduction in code ceremony that results in less code written and less to think about.
The immediate benefits we see are:
No DSC Resource module imports and DSC Configuration function declaration are required
We can describe the dependencies between resources using a simpler dependency symbol, which results in less to write as well as making it easier to move sections around or add new sections without remember to keep array statements in sync
Global resource defaults to parameters reduces the amount of repetitive code you have to write.
You get all the benefits from the maturity of the Puppet DSL and the reach of the DSC Resources in the same manifest
We have gone over how Puppet and DSC together enables you to do more with your existing skill sets and provides a large toolset to accomplish any task. The last thing we are going to cover today is how to see the results of everything we’ve done so far.
Change reporting is a must have for any company that has to comply with any kind of auditing. Being able to pinpoint when something was successfully changed is a huge step towards getting control over your environment, never mind proving it to auditors or your coworkers.
Seeing the changes across your environment presented in an easily accessible way reduces the amount of time spent verifying change. You don’t have to manually go out and check the state, it’s already collected for you.
Historical reporting is important because knowing when something broke is just as important as knowing what broke. If you are able to find out the time a change happened, correlation to other events becomes easier and reduces the amount of time spent troubleshooting.
Lets delve a little deeper into what is available built into PowerShell DSC and how Puppet expands on that by showing changes across your environment over time.
While PowerShell DSC does not keep historical data on changes performed, it does provide some ways for you to find out what changed manually.
PowerShell shows status of the whole operation if queried, not on resource by resource. This provides a good indication of the state of the last run, but you can’t find out how that changed over time as these results are not kept. In PowerShell v4 this is accomplished by using the EventLogs and searching for the last run result. In PowerShell v5 you can use Get-DscConfigurationStatus cmdlet as show here to get the same information.
PowerShell results are only available on target node, unless a DSC Pull Server is setup. A Pull Server can store the last result for all target nodes configured to point to it, but it still requires a manual HTTP call to get the information. You can script these calls to generate reports, but this is not built-in
Now that we have seen what is built in to DSC, lets see how we can extend that using Puppet
Puppet can extend DSC by providing historical change tracking and reporting.
Configuration results and history are available on the target node as well as in the Puppet Server Web UI. The Web UI provides a single pane of glass interface that shows the status of your environment as a whole all the way down to individual servers. It even shows resource by resource change. As we see in the slide, the result of each DSC Resource execution is shown. A log is provided of the execution as well.
Puppet Server keeps track of changes by keeping all of these reports. This allows you to investigate over time how things change in your environment. For instance it could alert you to a target node that is continually being changed outside of specification, so that you can ensure compliance.
Seeing the results of DSC and Puppet is great, but what about when things go wrong? How do you find out what’s going on? Let’s look at how you do this in DSC and then with Puppet
Finding any errors that are occuring during a DSC Configuration run is an exercise in searching the Eventlog. This can either be done manually with EventViewer or using the xDscDiagnostics module cmdlets: Get-xDscOperation and Trace-xDscOperation. They can be run either locally or remotely.
Get-xDscOperation lists statuses of the last few run DSC operations. It returns an object that has information about the time that run was created, whether the run was successful or not, all the events generated by that run, and the unique job identifier for that run. You use this cmdlet to find the specific DSC Job that created the error condition you want to investigate.
Trace-xDscOperation takes the JobId or SequenceId from the Get-xDscOperation cmdlet as parameters and gives you a readable list of events generated by their respective DSC operation. By default, Trace-xDscOperation will list all the events generated by the most recent run. This cmdlet returns an object that contains properties such as event type, event message, and time of event creation. The results of this cmdlet are what you use to figure out which part of the DSC Configuration is failing, and what the root cause is.
We just saw how investigating errors when applying configurations in DSC requires looking at EventLogs on the target node, either using EventViewer or the DscDiagnostics module the PowerShell team created.
In Puppet errors are surfaced up front and are easy to diagnose compared to searching through dozens of events. These are the same messages you would see from DSC in the EventLog or on the PowerShell console, viewable inside the Puppet Server UI.
Puppet automatically logs the results of all actions taken, either by Puppet or DSC, so you can review exactly what happened without having to ‘go to the target node’ or run commands manually yourself. This is a huge time saver, when you’re on the line to figure out why something is going wrong. It’s just a few clicks compared to several minutes running commands and searching through events.
We have come along way in our discussion about Puppet and DSC.
We’ve shown how we can use the skills you have to do more, how the syntax is similar and that migrating to Puppet manifests requires little extra effort.
We’ve seen how the thousands of Puppet modules and hundreds of DSC resources can enable you to cover any scenario you are faced with, on any platform you support
Finally we’ve covered how you can track these changes in your environment and report on them for compliance.
I hope that this has been informative and useful. I'm going to pass off to Ethan to talk more about Puppet
First, we think it’s critical to adopt automation technology that helps you model and enforce the desired state of the services you deliver.
Second, we think that you should automate those processes (among others) from your core infrastructure up through your applications, all in one place for full enforcement, traceability and auditability.
Third, we think you should automate across the entire lifecycle, from initial provisioning of infrastructure through decommissioning.
Finally, you should do this across everything. If it has an IP address, you should automate the management of it.
Let’s dig into each of these.
First, we think it’s critical to adopt automation technology that helps you model and enforce the desired state of the services you deliver.
Second, we think that you should automate those processes (among others) from your core infrastructure up through your applications, all in one place for full enforcement, traceability and auditability.
Third, we think you should automate across the entire lifecycle, from initial provisioning of infrastructure through decommissioning.
Finally, you should do this across everything. If it has an IP address, you should automate the management of it.
Let’s dig into each of these.
First, we think it’s critical to adopt automation technology that helps you model and enforce the desired state of the services you deliver.
Second, we think that you should automate those processes (among others) from your core infrastructure up through your applications, all in one place for full enforcement, traceability and auditability.
Third, we think you should automate across the entire lifecycle, from initial provisioning of infrastructure through decommissioning.
Finally, you should do this across everything. If it has an IP address, you should automate the management of it.
Let’s dig into each of these.