PuppetConf 2017: Using Puppet Enterprise APIs with PowerShell- Jason Johnson, Humana
•Download as PPTX, PDF•
0 likes•331 views
Puppet Enterprise has great APIs that can simplify many aspects of the care and feeding of your infrastructure. While users have had success using Puppet Enterprise API in combination with curl, python and bash shell scripts, implementing these tools on Windows can be problematic. We will discuss PowerShell: what it is and how it differs from other shells; its increasing ubiquity; and tools that simplify coding. We will explore how to convert a curl command to PowerShell for (1) checking puppet status endpoints, (2) a puppet db query, and (3) a code manager deployment. Security is not left out as we discuss the issues with untrusted CAs and creating a pfx certificate to ensure secure commands from PowerShell. With this new knowledge you will be able to evolve the existing curl examples into PowerShell scripts to which your Windows colleagues can not only run, but also contribute.
Report
Share
Report
Share
Recommended
PuppetConf 2017: No Server Left Behind - Miguel Di Ciurcio Filho, Instruct
A big percentage of companies do not use proper configuration management nor automation. In this talk, I will share various ideas and experiences, making the audience feel much more prepared and confident in rolling out Puppet to manage old or legacy environments that might be left out of automation and configuration management. It is possible to roll out the Puppet agent with ease on these challenging scenarios, letting Puppet gradually fully manage everything with confidence and close to no impact. One of the reasons that commonly makes companies afraid of rolling out the Puppet agent is the impact of actually letting it do its job, since there might be so much accumulated technical debt due to years of manual work. I’ll show successful strategies used on some of our clients that demonstrate Puppet’s powerful built-in state modeling and simulation mechanisms and various useful resource types that let us very granularly manage configuration without breaking what is already in place.
MonoRails - GoGaRuCo 2012
The document discusses the challenges of scaling a monolithic Rails application over time as features and data grow. It begins by describing a Rails app with over 1000 controllers running on huge MySQL boxes across multiple datacenters. As the app and team grew, testing became spotty and developers became overwhelmed. The document then discusses actual scaling problems like scaling data, codebase, customers and features. It proposes separating the app into internal gems and services to allow independent scaling of components instead of the monolithic approach that becomes difficult to change.
Zone.js
Overview of zone.js (Monkey Patching, Forking, Interception). How its used in Angular for triggering Change Detection and a demo in NodeJS for authentication handling.
All my slides and demos can be found here: https://github.com/IliaIdakiev/slides
Development, Deployment & Collaboration at Etsy
This document discusses development, deployment, and collaboration practices at Etsy. It describes that Etsy deploys changes 50 times per day on average and uses practices like continuous integration, developer VMs, the "Deployinator" tool, monitoring dashboards, on-call rotations, incident response procedures, post-mortem reviews, and knowledge sharing to facilitate frequent deployments in a collaborative environment. The goal is to share practices that work for Etsy and encourage learning and teaching across teams.
Intro to Netflix's Chaos Monkey
The basics you need to know to get up and running with Chaos Monkey in your Amazon Web Service's Cloud enviornment.
Links:
CloudFormation Template:
https://github.com/joehack3r/aws/blob/master/cloudformation/templates/chaosMonkey.json
Simian Army Quick Start Guide:
https://github.com/Netflix/SimianArmy/wiki/Quick-Start-Guide
Chaos Monkey Configuration:
https://github.com/Netflix/SimianArmy/wiki/Chaos-Settings
Chaos Monkey Army:
https://github.com/Netflix/SimianArmy/wiki/The-Chaos-Monkey-Army
Erlang - Dive Right In
Erlang is a functional programming language built for reliability and concurrency. It is used to build scalable and fault-tolerant systems through features like its supervision tree, behaviors, and OTP framework. The document recommends learning more about Erlang through various books and online resources, and suggests trying out the build tools rebar and ChicagoBoss or contributing to open source projects like Riak to get hands-on experience with the language.
Migrating big data
The document summarizes Mozilla's migration of its Socorro crash analysis system from its original infrastructure to a new architecture. It describes Socorro and its purpose of analyzing crash data. It then discusses the rationale for migrating to improve stability, the planning process, building out the new infrastructure with automation and configuration management, load testing the new system, troubleshooting issues during the migration, and lessons learned from the process.
Hadoop Demystified + Automation Smackdown! Austin JUG June 24 2014
This document discusses two approaches to ETL jobs in Hadoop: a manual "special snowflake" approach and an automated approach. The manual approach involves a team spending a year copying and pasting code for 15 jobs. This leads to spaghetti code and is not sustainable. The automated approach involves designing reusable templates and rules to automate the ETL process. This frees up the developer Brent to focus on design rather than manual work. It results in code that is clean, consistent, easy to maintain and passes the "10 minute test" of being idempotent. The document demonstrates generating ETL code from metadata and deploying the automated jobs to Hadoop.
Recommended
PuppetConf 2017: No Server Left Behind - Miguel Di Ciurcio Filho, Instruct
A big percentage of companies do not use proper configuration management nor automation. In this talk, I will share various ideas and experiences, making the audience feel much more prepared and confident in rolling out Puppet to manage old or legacy environments that might be left out of automation and configuration management. It is possible to roll out the Puppet agent with ease on these challenging scenarios, letting Puppet gradually fully manage everything with confidence and close to no impact. One of the reasons that commonly makes companies afraid of rolling out the Puppet agent is the impact of actually letting it do its job, since there might be so much accumulated technical debt due to years of manual work. I’ll show successful strategies used on some of our clients that demonstrate Puppet’s powerful built-in state modeling and simulation mechanisms and various useful resource types that let us very granularly manage configuration without breaking what is already in place.
MonoRails - GoGaRuCo 2012
The document discusses the challenges of scaling a monolithic Rails application over time as features and data grow. It begins by describing a Rails app with over 1000 controllers running on huge MySQL boxes across multiple datacenters. As the app and team grew, testing became spotty and developers became overwhelmed. The document then discusses actual scaling problems like scaling data, codebase, customers and features. It proposes separating the app into internal gems and services to allow independent scaling of components instead of the monolithic approach that becomes difficult to change.
Zone.js
Overview of zone.js (Monkey Patching, Forking, Interception). How its used in Angular for triggering Change Detection and a demo in NodeJS for authentication handling.
All my slides and demos can be found here: https://github.com/IliaIdakiev/slides
Development, Deployment & Collaboration at Etsy
This document discusses development, deployment, and collaboration practices at Etsy. It describes that Etsy deploys changes 50 times per day on average and uses practices like continuous integration, developer VMs, the "Deployinator" tool, monitoring dashboards, on-call rotations, incident response procedures, post-mortem reviews, and knowledge sharing to facilitate frequent deployments in a collaborative environment. The goal is to share practices that work for Etsy and encourage learning and teaching across teams.
Intro to Netflix's Chaos Monkey
The basics you need to know to get up and running with Chaos Monkey in your Amazon Web Service's Cloud enviornment.
Links:
CloudFormation Template:
https://github.com/joehack3r/aws/blob/master/cloudformation/templates/chaosMonkey.json
Simian Army Quick Start Guide:
https://github.com/Netflix/SimianArmy/wiki/Quick-Start-Guide
Chaos Monkey Configuration:
https://github.com/Netflix/SimianArmy/wiki/Chaos-Settings
Chaos Monkey Army:
https://github.com/Netflix/SimianArmy/wiki/The-Chaos-Monkey-Army
Erlang - Dive Right In
Erlang is a functional programming language built for reliability and concurrency. It is used to build scalable and fault-tolerant systems through features like its supervision tree, behaviors, and OTP framework. The document recommends learning more about Erlang through various books and online resources, and suggests trying out the build tools rebar and ChicagoBoss or contributing to open source projects like Riak to get hands-on experience with the language.
Migrating big data
The document summarizes Mozilla's migration of its Socorro crash analysis system from its original infrastructure to a new architecture. It describes Socorro and its purpose of analyzing crash data. It then discusses the rationale for migrating to improve stability, the planning process, building out the new infrastructure with automation and configuration management, load testing the new system, troubleshooting issues during the migration, and lessons learned from the process.
Hadoop Demystified + Automation Smackdown! Austin JUG June 24 2014
This document discusses two approaches to ETL jobs in Hadoop: a manual "special snowflake" approach and an automated approach. The manual approach involves a team spending a year copying and pasting code for 15 jobs. This leads to spaghetti code and is not sustainable. The automated approach involves designing reusable templates and rules to automate the ETL process. This frees up the developer Brent to focus on design rather than manual work. It results in code that is clean, consistent, easy to maintain and passes the "10 minute test" of being idempotent. The document demonstrates generating ETL code from metadata and deploying the automated jobs to Hadoop.
Away day
Netto (nettofarah@gmail.com) and Vini's (vgomes@thoughtworks.com) presentation for the ThoughtWorks Brasil away day 2012.
WTF is Sensu and Monitoring
Broken up into three core sections, this presentation tries to help explain why you monitor software, platforms and your products. What you can look for, and how to best get that information out of your code and finally how Sensu can be used to achieve this in a scalable platform.
Stop using Nagios (so it can die peacefully)
You shouldn't use Nagios any more - it sucks. Let's build a new, better, more awesome monitoring system.
Ruby performance - The low hanging fruit
This document discusses tools and techniques for optimizing Ruby performance. It begins by looking at common expensive tasks like database operations, network access, and inefficient algorithms. It then discusses tools for benchmarking and profiling Ruby code like Benchmark, benchmark-ips, and stackprof. The document provides examples of optimizing ActiveRecord queries and using caching and memoization. It also discusses optimizing the environment through server, database, and caching configuration. Finally, it notes that in some CPU-intensive or async tasks, Ruby may not be the best tool.
Data Driven Monitoring
At Etsy we are big fans of graphing and monitoring all the things. We deploy our main site several times a day and our monitoring provides us with the tight feedback loop we need to make this possible. The same goes for changes in the infrastructure which are deployed in a similar fashion of small and frequent changes. For this to work we have build up monitoring that tracks changes and possible problems in every nook and cranny of the Etsy stack, be it a network change, systems or application level performance or how bad the last week of on-call rotation was. The flipside of monitoring all the things however is that we have a myriad of graphs and alerts that can potentially be important and page the on-call engineer at any given time. The risk of running into alert fatigue and a normalization of deviance through not properly scoped checks is rising with this ever increasing size of the monitoring system. This is why we also continuously monitor our monitoring system and ask questions about whether we have all the information at hand when we get paged, if certain alerts actually need to wake someone up or if they are needed at all. I will give a quick overview of how our monitoring stack is built and then give insights into how we gather data about it and use it to make things better. For site operations and more importantly for the human getting paged when something does go wrong.
A Whirlwind Tour of Etsy's Monitoring Stack
Etsy uses a variety of open source and custom tools to monitor their infrastructure including Ganglia, StatsD, Graphite, Syslog-Ng, Logster, Splunk, Logstash, Eventinator, Chef, Nagios, and Nagios Herald. They collect system, application, and log metrics and events and store them for analysis. Their monitoring setup is fully configured through Chef to provide consistent deployments across environments with over 120 monitoring recipes.
Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Sca...
3 years ago, Springer decided to use Scala on a large, strategic project. This talk is about the journey the development teams made. Why did they choose Scala in the first place? Did they get what they hoped for? What challenges and surprises did they encounter along the way? And, most importantly, are they still happy with their choice?
Mobile CI at Etsy
Etsy uses GitHub Enterprise for code reviews of code committed to their on-premise git repositories. They have over 350 Linux virtual machines called "The Bobs" that are used to build and test code. Etsy also has 25 Mac Minis that are used to build, test, and run linting on their mobile Android and iOS code using an automated process with Chef. The summary describes Etsy's implementation of continuous integration for mobile apps using GitHub, Linux VMs, Mac Minis, and automation with Chef to improve testing and visibility of their code.
Riot Games Scalable Data Warehouse Lecture at UCSB / UCLA
This is a talk that was given for the Scalable Internet Services Masters-level Computer Science class at UCLA and UCSB. It briefly discusses the server architecture for the game League of Legends before going into depth about how the data warehouse can hold petabytes of player data. Discussion about message queue architecture and scalability occurs along the way
Test driven infrastructure development (2 - puppetconf 2013 edition)
The document discusses test driven infrastructure development. It describes issues with the current state where infrastructure changes are not repeatable and difficult to test. The speaker proposes modeling infrastructure as code where environments are defined programmatically and configuration is generated externally rather than defined directly in puppet code. This allows for entire environments to be provisioned on demand and tested in an automated and repeatable way. Key benefits include high availability, ability to test all infrastructure changes, fully repeatable environments, high confidence in changes, and continuous integration/deployment of infrastructure.
Cassandra Summit 2014: Astyanax — To Be or Not To Be
Presenter: Puneet Oberai, Senior Software Engineer at Netflix
In this session, we'll cover a quick introduction to the Astyanax Java client driver, powerful features, comparison to Java Driver and what to do with CQL3.
Scaling small apps
In March 2010, the UK had an election with a televised leadership debate. We built an application that scaled to 2.7 million hits in 90 minutes on top of AppEngine which we built in about 3 days. See the mistakes we made and what went well.
Development, Deployment and Collaboration at Etsy
At Etsy about 150 engineers deploy a single monolithic application more than 60 times a day. This process of deploying small changesets continuously enables us to build up and release robust features and detect and fix bugs extremely fast. All while serving over a billion page views per month. Developing and deploying at such a high velocity however only works because product developers and designers, infrastructure and operations engineers and the security team work closely together. We have an extremely open culture of sharing (inside and outside the company) and make sure we run into as few surprises as possible by bringing everybody on the same page about changes.
Cloud tools
John McCaffrey gives a presentation on cloud tools for development. He discusses terminology related to hosting and deploying applications. Some hosting options he covers include self-hosting, Amazon Web Services, EngineYard, Heroku, and AppHarbor. John then demonstrates deploying applications to Heroku and monitoring tools. He finishes by discussing collaboration tools like email, chat, screen sharing, and code repositories on services like GitHub.
It Sounded Good on Paper - Lessons Learned with Puppet
This talk is a 12 point guide on the things we did wrong during our journey with Puppet. We hope sharing helps people prevent the same mistakes in the future.
Troubleshooting Node.js
This document provides tips for troubleshooting Node.js applications when performance problems occur. It recommends logging everything, testing extensively including load testing, monitoring for errors, memory and CPU usage, and deploying automatically. When issues arise, it advises isolating the problem, measuring impacts of changes, and using tools like flamegraphs, heapdumps and the V8 profiler to identify bottlenecks like CPU-bound code, memory leaks or event loop lag.
Elm - never get a runtime error anymore. Almost.
Elm, a transpiled-to-JavaScript language which makes sure you’ll never have a runtime error in your app. Almost. Why it’s cool, what it looks like, it’s pros and (most importantly) cons.
Benchmarking: You're Doing It Wrong (StrangeLoop 2014)
Knowledge of how to set up good benchmarks is invaluable in understanding performance of the system. Writing correct and useful benchmarks is hard, and verification of the results is difficult and prone to errors. When done right, benchmarks guide teams to improve the performance of their systems. When done wrong, hours of effort may result in a worse performing application, upset customers or worse! In this talk, we will discuss what you need to know to write better benchmarks. We will look at examples of bad benchmarks and learn about what biases can invalidate the measurements, in the hope of correctly applying our new-found skills and avoiding such pitfalls in the future.
Sensu at brightpearl
Sensu is a monitoring system that the author implemented to replace Nagios at their company Brightpearl. Nagios became unmanageable as the infrastructure grew and changed frequently in the cloud. Sensu has a more flexible, distributed architecture using clients, servers, and APIs that can automatically monitor a dynamic infrastructure. While still immature, Sensu provides the scalability, integration, and simplified configuration that Nagios lacked for the author's needs. It has performed well in testing and they are looking forward to fully rolling it out in production.
The Real World - Plugging the Enterprise Into It (nodejs)
This document discusses using Node.js as the foundation for building applications that connect the physical world to enterprise systems through mobile devices and sensors. It describes initial work done to build a proxy and protocol for handling requests and addresses challenges with authentication, scalability, and performance testing. The document shares results from benchmarking the system under different network conditions and outlines next steps to improve concurrency, security, and infrastructure elasticity.
Dev/Test in the Cloud - F
The "Cloud" is not just SaaS and production hosting. One of the easiest ways to start with the cloud is to use it for development and testing. Even if your company is concerned about going to the "Cloud". Dev/Test is a huge productivity enhancer, and a way to start small with the Cloud.
SharePoint Development 101
This document provides a summary of key concepts for new SharePoint developers. It discusses what functionality SharePoint provides out of the box, how the development tools and deployment process differ from a typical web application, important concepts like features and packages, and best practices around areas like disposing objects properly and avoiding direct web.config modifications. It also lists 10 things every SharePoint developer should know and how to avoid getting code rejected by an architecture group.
More Related Content
What's hot
Away day
Netto (nettofarah@gmail.com) and Vini's (vgomes@thoughtworks.com) presentation for the ThoughtWorks Brasil away day 2012.
WTF is Sensu and Monitoring
Broken up into three core sections, this presentation tries to help explain why you monitor software, platforms and your products. What you can look for, and how to best get that information out of your code and finally how Sensu can be used to achieve this in a scalable platform.
Stop using Nagios (so it can die peacefully)
You shouldn't use Nagios any more - it sucks. Let's build a new, better, more awesome monitoring system.
Ruby performance - The low hanging fruit
This document discusses tools and techniques for optimizing Ruby performance. It begins by looking at common expensive tasks like database operations, network access, and inefficient algorithms. It then discusses tools for benchmarking and profiling Ruby code like Benchmark, benchmark-ips, and stackprof. The document provides examples of optimizing ActiveRecord queries and using caching and memoization. It also discusses optimizing the environment through server, database, and caching configuration. Finally, it notes that in some CPU-intensive or async tasks, Ruby may not be the best tool.
Data Driven Monitoring
At Etsy we are big fans of graphing and monitoring all the things. We deploy our main site several times a day and our monitoring provides us with the tight feedback loop we need to make this possible. The same goes for changes in the infrastructure which are deployed in a similar fashion of small and frequent changes. For this to work we have build up monitoring that tracks changes and possible problems in every nook and cranny of the Etsy stack, be it a network change, systems or application level performance or how bad the last week of on-call rotation was. The flipside of monitoring all the things however is that we have a myriad of graphs and alerts that can potentially be important and page the on-call engineer at any given time. The risk of running into alert fatigue and a normalization of deviance through not properly scoped checks is rising with this ever increasing size of the monitoring system. This is why we also continuously monitor our monitoring system and ask questions about whether we have all the information at hand when we get paged, if certain alerts actually need to wake someone up or if they are needed at all. I will give a quick overview of how our monitoring stack is built and then give insights into how we gather data about it and use it to make things better. For site operations and more importantly for the human getting paged when something does go wrong.
A Whirlwind Tour of Etsy's Monitoring Stack
Etsy uses a variety of open source and custom tools to monitor their infrastructure including Ganglia, StatsD, Graphite, Syslog-Ng, Logster, Splunk, Logstash, Eventinator, Chef, Nagios, and Nagios Herald. They collect system, application, and log metrics and events and store them for analysis. Their monitoring setup is fully configured through Chef to provide consistent deployments across environments with over 120 monitoring recipes.
Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Sca...
3 years ago, Springer decided to use Scala on a large, strategic project. This talk is about the journey the development teams made. Why did they choose Scala in the first place? Did they get what they hoped for? What challenges and surprises did they encounter along the way? And, most importantly, are they still happy with their choice?
Mobile CI at Etsy
Etsy uses GitHub Enterprise for code reviews of code committed to their on-premise git repositories. They have over 350 Linux virtual machines called "The Bobs" that are used to build and test code. Etsy also has 25 Mac Minis that are used to build, test, and run linting on their mobile Android and iOS code using an automated process with Chef. The summary describes Etsy's implementation of continuous integration for mobile apps using GitHub, Linux VMs, Mac Minis, and automation with Chef to improve testing and visibility of their code.
Riot Games Scalable Data Warehouse Lecture at UCSB / UCLA
This is a talk that was given for the Scalable Internet Services Masters-level Computer Science class at UCLA and UCSB. It briefly discusses the server architecture for the game League of Legends before going into depth about how the data warehouse can hold petabytes of player data. Discussion about message queue architecture and scalability occurs along the way
Test driven infrastructure development (2 - puppetconf 2013 edition)
The document discusses test driven infrastructure development. It describes issues with the current state where infrastructure changes are not repeatable and difficult to test. The speaker proposes modeling infrastructure as code where environments are defined programmatically and configuration is generated externally rather than defined directly in puppet code. This allows for entire environments to be provisioned on demand and tested in an automated and repeatable way. Key benefits include high availability, ability to test all infrastructure changes, fully repeatable environments, high confidence in changes, and continuous integration/deployment of infrastructure.
Cassandra Summit 2014: Astyanax — To Be or Not To Be
Presenter: Puneet Oberai, Senior Software Engineer at Netflix
In this session, we'll cover a quick introduction to the Astyanax Java client driver, powerful features, comparison to Java Driver and what to do with CQL3.
Scaling small apps
In March 2010, the UK had an election with a televised leadership debate. We built an application that scaled to 2.7 million hits in 90 minutes on top of AppEngine which we built in about 3 days. See the mistakes we made and what went well.
Development, Deployment and Collaboration at Etsy
At Etsy about 150 engineers deploy a single monolithic application more than 60 times a day. This process of deploying small changesets continuously enables us to build up and release robust features and detect and fix bugs extremely fast. All while serving over a billion page views per month. Developing and deploying at such a high velocity however only works because product developers and designers, infrastructure and operations engineers and the security team work closely together. We have an extremely open culture of sharing (inside and outside the company) and make sure we run into as few surprises as possible by bringing everybody on the same page about changes.
Cloud tools
John McCaffrey gives a presentation on cloud tools for development. He discusses terminology related to hosting and deploying applications. Some hosting options he covers include self-hosting, Amazon Web Services, EngineYard, Heroku, and AppHarbor. John then demonstrates deploying applications to Heroku and monitoring tools. He finishes by discussing collaboration tools like email, chat, screen sharing, and code repositories on services like GitHub.
It Sounded Good on Paper - Lessons Learned with Puppet
This talk is a 12 point guide on the things we did wrong during our journey with Puppet. We hope sharing helps people prevent the same mistakes in the future.
Troubleshooting Node.js
This document provides tips for troubleshooting Node.js applications when performance problems occur. It recommends logging everything, testing extensively including load testing, monitoring for errors, memory and CPU usage, and deploying automatically. When issues arise, it advises isolating the problem, measuring impacts of changes, and using tools like flamegraphs, heapdumps and the V8 profiler to identify bottlenecks like CPU-bound code, memory leaks or event loop lag.
Elm - never get a runtime error anymore. Almost.
Elm, a transpiled-to-JavaScript language which makes sure you’ll never have a runtime error in your app. Almost. Why it’s cool, what it looks like, it’s pros and (most importantly) cons.
Benchmarking: You're Doing It Wrong (StrangeLoop 2014)
Knowledge of how to set up good benchmarks is invaluable in understanding performance of the system. Writing correct and useful benchmarks is hard, and verification of the results is difficult and prone to errors. When done right, benchmarks guide teams to improve the performance of their systems. When done wrong, hours of effort may result in a worse performing application, upset customers or worse! In this talk, we will discuss what you need to know to write better benchmarks. We will look at examples of bad benchmarks and learn about what biases can invalidate the measurements, in the hope of correctly applying our new-found skills and avoiding such pitfalls in the future.
Sensu at brightpearl
Sensu is a monitoring system that the author implemented to replace Nagios at their company Brightpearl. Nagios became unmanageable as the infrastructure grew and changed frequently in the cloud. Sensu has a more flexible, distributed architecture using clients, servers, and APIs that can automatically monitor a dynamic infrastructure. While still immature, Sensu provides the scalability, integration, and simplified configuration that Nagios lacked for the author's needs. It has performed well in testing and they are looking forward to fully rolling it out in production.
The Real World - Plugging the Enterprise Into It (nodejs)
This document discusses using Node.js as the foundation for building applications that connect the physical world to enterprise systems through mobile devices and sensors. It describes initial work done to build a proxy and protocol for handling requests and addresses challenges with authentication, scalability, and performance testing. The document shares results from benchmarking the system under different network conditions and outlines next steps to improve concurrency, security, and infrastructure elasticity.
What's hot (20)
Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Sca...
Scala in-practice-3-years by Patric Fornasier, Springr, presented at Pune Sca...
Riot Games Scalable Data Warehouse Lecture at UCSB / UCLA
Riot Games Scalable Data Warehouse Lecture at UCSB / UCLA
Test driven infrastructure development (2 - puppetconf 2013 edition)
Test driven infrastructure development (2 - puppetconf 2013 edition)
Cassandra Summit 2014: Astyanax — To Be or Not To Be
Cassandra Summit 2014: Astyanax — To Be or Not To Be
It Sounded Good on Paper - Lessons Learned with Puppet
It Sounded Good on Paper - Lessons Learned with Puppet
Benchmarking: You're Doing It Wrong (StrangeLoop 2014)
Benchmarking: You're Doing It Wrong (StrangeLoop 2014)
The Real World - Plugging the Enterprise Into It (nodejs)
The Real World - Plugging the Enterprise Into It (nodejs)
Similar to PuppetConf 2017: Using Puppet Enterprise APIs with PowerShell- Jason Johnson, Humana
Dev/Test in the Cloud - F
The "Cloud" is not just SaaS and production hosting. One of the easiest ways to start with the cloud is to use it for development and testing. Even if your company is concerned about going to the "Cloud". Dev/Test is a huge productivity enhancer, and a way to start small with the Cloud.
SharePoint Development 101
This document provides a summary of key concepts for new SharePoint developers. It discusses what functionality SharePoint provides out of the box, how the development tools and deployment process differ from a typical web application, important concepts like features and packages, and best practices around areas like disposing objects properly and avoiding direct web.config modifications. It also lists 10 things every SharePoint developer should know and how to avoid getting code rejected by an architecture group.
Jest: Frontend Testing richtig gemacht @WebworkerNRW
Mal ganz ehrlich: Testen im Frontend hat noch nie viel Spaß gemacht. In meinem Talk möchte ich mit Jest eine Testbibliothek vorstellen, die genau das ändern kann. Jest ist ohne viel Konfiguration direkt einsetzbar und bringt alles mit, was man von einer Testbibliothek erwartet (und noch mehr). An vielen praktischen Beispielen möchte ich meine Lieblingsfeatures wie z.B. Snapshot-Tests, Mocking oder das tolle CLI erläutern und zeigen, dass Testen im Frontend durchaus Spaß machen kann. Eine Ausrede weniger, um auf das Testen im Frontend zu verzichten!
Chef at WebMD
Talk at DevOpsDC on 11/18/14 discussing how WebMD started using Chef, why it didn't work "out of the box" for us, and how we changed that.
Using Apache Camel as AKKA
The document discusses using Apache Camel and Apache Karaf to build distributed, asynchronous systems in a similar way to AKKA. It provides examples of building a dynamic routing system using Camel routing and JMS, as well as a modular ETL system for processing CSV files using a configurable, hot-deployable mutation framework. The examples demonstrate how to achieve scalability, modularity, and asynchronous behavior without deep knowledge of the underlying technologies through an event-driven architecture based on messaging.
Killing Shark-Riding Dinosaurs with ORM
This advanced session will cover topics on how to leverage both CFML and ORM to start creating amazing applications that will be as lethal as a dinosaur riding a shark with an Uzi. We will cover ORM session management, virtual service layers, dynamic finders, dynamic counters and an enhanced Hibernate Criteria builder to create easy and programmatic HQL queries.
SharePoint Saturday Lisbon 2017 - SharePoint Framework, Angular & Azure Funct...
Things are moving fast. Sometimes you might even feel that you own comfort zone is getting of control. But in a Mobile-First, Cloud-First world, things are changing to a crazy pace and to stay on the top of your game, you need keep up with the latest and greatest technologies that are available out there. By staying up to date, you will give to yourself new options that will let you be more productive, write better code and push you in a more open and more collaborative world.
With the official shipment of Angular 4 and the current release of the SharePoint Framework, it is now the time to start moving towards those new technologies in your SharePoint Solutions.
In this session, we will cover the modern tool belt of the SharePoint developer by covering the SharePoint Framework as the new surface to express yourself, Angular as a Framework to enable you to build complete applications within your SharePoint modern experiences and Azure Function as the perfect server-side companion for all your Office 365 & Azure development.
This very demo-intensive session will make sure that at the end you get those 3 key takeaways :
- Understand the role of the SharePoint Framework, Angular and Azure Functions in this Cloud-First, Mobile-First world
- Have a complete sample where the modern tool belt is relevant and useful in a real-world scenario
- Change the way you will think for your next SharePoint project
My first powershell script
Lessons learned from writing my first PowerShell script to restore a set of databases from backups stored on a network drive.
Sensu @ Yelp!: A Guided Tour
This is a presentation demonstrating how Sensu is used at Yelp to support dynamic infrastructure, and promote self-service monitoring among teams.
Video Part 1: https://vimeo.com/92770954
Video Part 2: https://vimeo.com/92838680
2021.laravelconf.tw.slides1
This document provides an overview of a presentation on Laravel Octane given by Albert Chen. The presentation covered: the lifecycle of PHP and Laravel applications; an introduction to Laravel Octane and how it makes applications more friendly for long-lived processes; reminders for developing long-lived PHP applications; Laravel's service container and how containers work in Octane; how Octane supports concurrent tasks using Swoole; additional Octane features like tickers, caching, and process communication; blocking I/O in PHP and how coroutines work in Swoole; whether Octane supports coroutines; and a benchmark comparing Octane to PHP-FPM with Nginx. The document concludes with an
Core Data in RubyMotion #inspect
Core Data doesn't have to be hard. Step by step, learn how to use Core Data in code, creating models and relationships. Loading data and efficiently displaying that data.
GraphQL-PHP: Dos and don'ts
I've had this talk about my experience with implementing a GraphQL API in PHP. There is also a video somewhere, but I was speaking Czech.
Systems Monitoring with Prometheus (Devops Ireland April 2015)
Monitoring means many things to many people. This talk looks at Systems Monitoring, that is how to keep an eye on a given system and use this as part of overall management of a system. This talk will cover Why one monitors, What to monitor, How to monitor, the general design of a monitoring system and how Prometheus is a good fit for this in terms of instrumentation, consoles, alerts, general system health and sanity.
Prometheus is a next-generation monitoring system publicly announced earlier this year, developed by companies including SoundCloud, locals Boxever and Docker. Since launch there has been wide-spread interest, and many community contributions.
For more information see http://prometheus.io or http://www.boxever.com/tag/monitoring
Node.js Development Workflow Automation with Grunt.js
Slides for presentation I have at Hydrahack in Birmingham on 18th March 2014.
http://hydrahack.co.uk/
http://talis.com
Puppet Camp London 2014: Chasing AMI: baking Amazon machine images with Jenki...
"Chasing AMI: baking Amazon machine images with Jenkins, Packer and Puppet" presented at Puppet Camp London April 2014 by Tom Doran, Yelp
Chasing AMI - Building Amazon machine images with Puppet, Packer and Jenkins
Using puppet when configuring EC2 machines seems a natural fit. However bringing up new machines from a community image with puppet is not trivial and can be slow, and so not useful for auto-scaling.
The cloud also offers a solution to ongoing server maintenance, allowing you to launch fresh instances whenever you upgrade your applications (Immutable or Phoenix servers). However to predictably succeed, you need to freeze the puppet code alongside the application version for deployment.
The solution to these issues is generating custom machine images (AMIs) with your software inlined. This talk will cover Yelp's use of a Packer, Jenkins and Puppet for generating AMIs. This will include how we deal with issues like bootstrapping, getting canonical information about a machine's environment and cluster state at launch time, as well as supporting immutable/phoenix servers in combination with more traditional long lived servers inside our hybrid cloud infrastructure.
Refactoring @ Mindvalley: Smells, Techniques and Patterns
Every week my team commits really good, clean code. I decided to get the best of the commits and showcase what makes them good, what smells they address, and what techniques they used.
DevOps Columbus Meetup Kickoff - Infrastructure as Code
The document summarizes the agenda for a DevOps Meetup in Columbus on July 11, 2013. The agenda includes introductions from 6:00-6:15pm, a presentation on "Infrastructure as Code" from 6:15-6:45pm, logistics from 6:45-7:00pm, and an open discussion on tips and experiences from 7:00-7:30pm. The document also provides background information on DevOps approaches, tools for infrastructure as code like Puppet and Chef, and a proposed model for continuous delivery. It introduces two speakers, Stathy Touloumis and Michael Ducy, and suggests brainstorming topics for future meetups from 7:45
Plone api
plone.api is a Python API for Plone that aims to provide a simple, Pythonic and consistent way to access common Plone functionality and content. It started at a Plone conference in 2012 and is gaining momentum with over 95% test coverage and documentation. The API is organized into logical groups like api.portal, api.content, api.user and more to provide common methods for interacting with Plone in a standardized way.
DevOps for Drupal: Why We Cook With Chef
DevOps for Drupal presentation given at DrupalCon 2013 in Portland. Promet Source shares secrets for automation and how to make your infrastructure hum.
Similar to PuppetConf 2017: Using Puppet Enterprise APIs with PowerShell- Jason Johnson, Humana (20)
Jest: Frontend Testing richtig gemacht @WebworkerNRW
Jest: Frontend Testing richtig gemacht @WebworkerNRW
SharePoint Saturday Lisbon 2017 - SharePoint Framework, Angular & Azure Funct...
SharePoint Saturday Lisbon 2017 - SharePoint Framework, Angular & Azure Funct...
Systems Monitoring with Prometheus (Devops Ireland April 2015)
Systems Monitoring with Prometheus (Devops Ireland April 2015)
Node.js Development Workflow Automation with Grunt.js
Node.js Development Workflow Automation with Grunt.js
Puppet Camp London 2014: Chasing AMI: baking Amazon machine images with Jenki...
Puppet Camp London 2014: Chasing AMI: baking Amazon machine images with Jenki...
Chasing AMI - Building Amazon machine images with Puppet, Packer and Jenkins
Chasing AMI - Building Amazon machine images with Puppet, Packer and Jenkins
Refactoring @ Mindvalley: Smells, Techniques and Patterns
Refactoring @ Mindvalley: Smells, Techniques and Patterns
DevOps Columbus Meetup Kickoff - Infrastructure as Code
DevOps Columbus Meetup Kickoff - Infrastructure as Code
More from Puppet
Puppet camp2021 testing modules and controlrepo
This document discusses testing Puppet code when using modules versus a control repository. It recommends starting with simple syntax and unit tests using PDK or rspec-puppet for modules, and using OnceOver for testing control repositories, as it is specially designed for this purpose. OnceOver allows defining classes, nodes, and a test matrix to run syntax, unit, and acceptance tests across different configurations. Moving from simple to more complex testing approaches like acceptance tests is suggested. PDK and OnceOver both have limitations for testing across operating systems that may require customizing spec tests. Infrastructure for running acceptance tests in VMs or containers is also discussed.
Puppetcamp r10kyaml
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.
2021 04-15 operational verification (with notes)
The document discusses operational verification and how Puppet is working on a new module to provide more confidence in infrastructure health. It introduces the concept of adding check resources to catalogs to validate configurations and service health directly during Puppet runs. Examples are provided of how this could detect issues earlier than current methods. Next steps outlined include integrating checks into more resource types, fixing reporting, integrating into modules, and gathering feedback. This allows testing and monitoring to converge by embedding checks within configurations.
Puppet camp vscode
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.
Modules of the twenties
- The document discusses various patterns and techniques the author has found useful when working with Puppet modules over 10+ years, including some that may be considered unorthodox or anti-patterns by some.
- Key topics covered include optimization of reusable modules, custom data types, Bolt tasks and plans, external facts, Hiera classification, ensuring resources for presence/absence, application abstraction with Tiny Puppet, and class-based noop management.
- The author argues that some established patterns like roles and profiles can evolve to be more flexible, and that running production nodes in noop mode with controls may be preferable to fully enforcing on all nodes.
Applying Roles and Profiles method to compliance code
This document discusses adapting the roles and profiles design pattern to writing compliance code in Puppet modules. It begins by noting the challenges of writing compliance code, such as it touching many parts of nodes and leading to sprawling code. It then provides an overview of the roles and profiles pattern, which uses simple "front-end" roles/interfaces and more complex "back-end" profiles/implementations. The rest of the document discusses how to apply this pattern when authoring Puppet modules for compliance - including creating interface and implementation classes, using Hiera for configuration, and tools for reducing boilerplate code. It aims to provide a maintainable structure and simplify adapting to new compliance frameworks or requirements.
KGI compliance as-code approach
This document discusses Kinney Group's Puppet compliance framework for automating STIG compliance and reporting. It notes that customers often implement compliance Puppet code poorly or lack appropriate Puppet knowledge. The framework aims to standardize compliance modules that are data-driven and customizable. It addresses challenges like conflicting modules and keeping compliance current after implementation. The framework generates automated STIG checklists and plans future integration with Puppet Enterprise and Splunk for continued compliance reporting. Kinney Group cites practical experience implementing the framework for various military and government customers.
Enforce compliance policy with model-driven automation
This document discusses model-driven automation for enforcing compliance. It begins with an overview of compliance benchmarks and the CIS benchmarks. It then discusses implementing benchmarks, common challenges around configuration drift and lack of visibility, and how to define compliance policy as code. The key points are that automation is essential for compliance at scale; a model-driven approach defines how a system should be configured and uses desired-state enforcement to keep systems compliant; and defining compliance policy as code, managing it with source control, and automating it with CI/CD helps achieve continuous compliance.
Keynote: Puppet camp compliance
This document discusses how organizations can move from a reactive approach to compliance to a proactive approach using automation. It notes that over 50% of CIOs cite security and compliance as a barrier to IT modernization. Puppet offers an end-to-end compliance solution that allows organizations to automatically eliminate configuration drift, enforce compliance at scale across operating systems and environments, and define policy as code. The solution helps organizations improve compliance from 50% to over 90% compliant. The document argues that taking a proactive automation approach to compliance can turn it into a competitive advantage by improving speed and innovation.
Automating it management with Puppet + ServiceNow
As the leading IT Service Management and IT Operations Management platform in the marketplace, ServiceNow is used by many organizations to address everything from self service IT requests to Change, Incident and Problem Management. The strength of the platform is in the workflows and processes that are built around the shared data model, represented in the CMDB. This provides the ‘single source of truth’ for the organization.
Puppet Enterprise is a leading automation platform focused on the IT Configuration Management and Compliance space. Puppet Enterprise has a unique perspective on the state of systems being managed, constantly being updated and kept accurate as part of the regular Puppet operation. Puppet Enterprise is the automation engine ensuring that the environment stays consistent and in compliance.
In this webinar, we will explore how to maximize the value of both solutions, with Puppet Enterprise automating the actions required to drive a change, and ServiceNow governing the process around that change, from definition to approval. We will introduce and demonstrate several published integration points between the two solutions, in the areas of Self-Service Infrastructure, Enriched Change Management and Automated Incident Registration.
Puppet: The best way to harden Windows
This document promotes Puppet as a tool for hardening Windows environments. It states that Puppet can be used to harden Windows with one line of code, detect drift from desired configurations, report on missing or changing requirements, reverse engineer existing configurations, secure IIS, and export configurations to the cloud. Benefits of Puppet mentioned include hardening Windows environments, finding drift for investigation, easily passing audits, compliance reporting, easy exceptions, and exporting configurations. It also directs users to Puppet Forge modules for securing Windows and IIS.
Simplified Patch Management with Puppet - Oct. 2020
Does your company struggle with patching systems? If so, you’re not alone — most organizations have attempted to solve this issue by cobbling together multiple tools, processes, and different teams, which can make an already complicated issue worse.
Puppet helps keep hosts healthy, secure and compliant by replacing time-consuming and error prone patching processes with Puppet’s automated patching solution.
Join this webinar to learn how to do the following with Puppet:
Eliminate manual patching processes with pre-built patching automation for Windows and Linux systems.
Gain visibility into patching status across your estate regardless of OS with new patching solution from the PE console.
Ensure your systems are compliant and patched in a healthy state
How Puppet Enterprise makes patch management easy across your Windows and Linux operating systems.
Presented by: Margaret Lee, Product Manager, Puppet, and Ajay Sridhar, Sr. Sales Engineer, Puppet.
Accelerating azure adoption with puppet
The document discusses how Puppet can be used to accelerate adoption of Microsoft Azure. It describes lift and shift migration of on-premises workloads to Azure virtual machines. It also covers infrastructure as code using Puppet and Terraform for provisioning, configuration management using Puppet Bolt, and implementing immutable infrastructure patterns on Azure. Integrations with Azure services like Key Vault, Blob Storage and metadata service are presented. Patch management and inventory of Azure resources with Puppet are also summarized.
Puppet catalog Diff; Raphael Pinson
This document discusses using Puppet Catalog Diff to analyze the impact of changes between Puppet environments or catalogs. It provides the command line usage and options for Puppet Catalog Diff. It also discusses how to integrate Puppet Catalog Diff into CI/CD pipelines for automated impact analysis when merging code changes. Additional resources like GitHub projects and Dev.to posts are provided for learning more about diffing Puppet environments and catalogs.
ServiceNow and Puppet- better together, Kevin Reeuwijk
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.
Take control of your dev ops dumping ground
This document discusses how Puppet Relay uses Tekton pipelines to orchestrate containerized workflows. It provides an overview of how Tekton fits into the Relay architecture, with Tekton controllers managing taskrun pods to execute workflow steps defined in YAML. Triggers can initiate workflows based on events, with reusable and composable steps for tasks like provisioning infrastructure or clearing resources. Relay also includes features for parameters, secrets, outputs, and approvals to customize workflows. An ecosystem of open source integrations provides sample workflows and steps for common use cases.
100% Puppet Cloud Deployment of Legacy Software
This document discusses deploying legacy software into the AWS cloud using Puppet. It proposes modeling AWS resources like security groups, autoscaling groups, and launch configurations as Puppet resources. This would allow Puppet to provision the underlying AWS infrastructure and configure servers launched in autoscaling groups. It acknowledges challenges around server reboots but suggests they can be addressed. In summary, it argues custom Puppet resources can easily model AWS resources and using Puppet to configure autoscaling servers is possible despite some challenges around rebooting servers during deployment.
Puppet User Group
This document discusses a partnership between Republic Polytechnic's School of Infocomm and Puppet to promote DevOps practices. It introduces several people involved with the partnership and outlines their mission to prepare more IT companies and individuals for jobs in the DevOps field through training courses. The document describes some short courses offered on DevOps topics and using the Puppet and Microsoft Azure platforms. It provides an example of how Republic Polytechnic has automated infrastructure configuration using Puppet to save time and reduce errors. There is a request at the end for readers to register their interest in DevOps by completing a survey.
Continuous Compliance and DevSecOps
This document discusses continuous compliance and DevSecOps best practices followed by financial services organizations.
Continuous compliance is defined as an ongoing process of proactive risk management that delivers predictable, transparent, and cost-effective compliance results. It involves continuously monitoring compliance controls, providing real-time alerts for failures and remediation recommendations, and maintaining up-to-date policies. Best practices for continuous compliance discussed include defining CIS controls and benchmarks, achieving transparent compliance dashboards and automated fixes for breaches.
DevSecOps is introduced as bringing security earlier in the application development lifecycle to minimize vulnerabilities. It aims to make everyone accountable for security. Challenges discussed include security teams struggling to keep up with DevOps pace and
The Dynamic Duo of Puppet and Vault tame SSL Certificates, Nick Maludy
The document discusses using Puppet and Vault together to dynamically manage SSL certificates. Puppet can use the vault_cert resource to request signed certificates from Vault and configure services to use the certificates. On Windows, some additional logic is needed to retrieve certificates' thumbprints and bind services to certificates using those thumbprints. This approach provides automated certificate renewal and distribution across platforms.
More from Puppet (20)
Applying Roles and Profiles method to compliance code
Applying Roles and Profiles method to compliance code
Enforce compliance policy with model-driven automation
Enforce compliance policy with model-driven automation
Simplified Patch Management with Puppet - Oct. 2020
Simplified Patch Management with Puppet - Oct. 2020
ServiceNow and Puppet- better together, Kevin Reeuwijk
ServiceNow and Puppet- better together, Kevin Reeuwijk
The Dynamic Duo of Puppet and Vault tame SSL Certificates, Nick Maludy
The Dynamic Duo of Puppet and Vault tame SSL Certificates, Nick Maludy
Recently uploaded
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Mind map of terminologies used in context of Generative AI
Mind map of common terms used in context of Generative AI.
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Securing your Kubernetes cluster_ a step-by-step guide to success !
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
GridMate - End to end testing is a critical piece to ensure quality and avoid...
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
By Design, not by Accident - Agile Venture Bolzano 2024
As presented at the Agile Venture Bolzano, 4.06.2024
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Recently uploaded (20)
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex Proofs
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
GridMate - End to end testing is a critical piece to ensure quality and avoid...
GridMate - End to end testing is a critical piece to ensure quality and avoid...
Monitoring Java Application Security with JDK Tools and JFR Events
Monitoring Java Application Security with JDK Tools and JFR Events
A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
By Design, not by Accident - Agile Venture Bolzano 2024
By Design, not by Accident - Agile Venture Bolzano 2024
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
PuppetConf 2017: Using Puppet Enterprise APIs with PowerShell- Jason Johnson, Humana
- 2. • Why use the puppet enterprise APIs • Show the advantages of using PowerShell with PE api’s • Talk about how you can improve your SR ranking in Overwatch What are we going to accomplish
- 3. • Jeremy Adams + Lizzi Lindboe – Puppet api round up from puppetconf 2015 • Matt Cadorette – The best technical solutions engineer ! ( but I may be bias) Thanks!
- 4. • Its consistent! …humans … not so much • Save the clicks! • Ok I admit it… I am totally Lazy Why use PE api
- 5. • Status • RBAC • Orchestration • Puppet DB • Node Classifier Some PE api enpoints ( more added all the time)
- 6. Status api
- 7. RBAC
- 9. Puppet DB
- 10. Node Classifer
- 12. Objects!
- 14. Open source
- 15. • Verb-noun • Get-command *rest* • ( still looking for get-command *bourbon*) Command Discovery
- 16. Training
- 17. • VS Studio is cool – ( ok its more cool than me.. But what isn’t ) Dev Tools
- 18. Can be used my Mortals!
- 19. Ok but I still can do this in Curl
- 20. Is curl in powershell?
- 21. Is curl in powershell?
- 22. Whats up with that?
- 23. Yeah yeah but what about the client tools
- 24. • Hold data in memory • Look at it – Filters – Tables – Where – Out-grid • Report it – export-csv What if you don’t really know what you want to do
- 25. Example!
- 26. Are we working?
- 27. • Windows does not want you to do something bad so … add this ! [System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true} • Or you can import the ca into your trusted root What about ssl?
- 28. • Things are different in PowerShell .. Duh! • Check out http://wahlnetwork.com/2016/02/18/using-powershell-arrays-and- hashtables-with-json-formatting/’ Stuff I had to learn!
- 29. Arrays Json { “environments”: [ “production” ], “wait”: “true” yaml --- environments: - production wait: ‘true’ Powershell force_sync_body =@{ enviroments=@(“production”) wait=“true”
- 30. Json Powershell Hash {} @{} Array [] @() Json syntax to PowerShell
- 31. • Start a puppet job json body Example from puppet docs
- 32. Same thing in PowerShell
- 33. And after a quick switch
- 34. Tokens!
- 35. Force a job run
- 36. Exporting classifier data to json
- 37. Db stuff
- 38. Questions? code and presentation at https://github.com/jgjohn02/puppetconf-2017