Puppet camp 2015 phoenix david patterson
•
5 likes•1,696 views
This document discusses using Puppet for configuration management and summarizing the benefits and concerns of getting management and developers onboard. It outlines a two phase process of pre-presentation to gather information and address concerns, and a development/implementation phase with communication. Benefits include stability, consistency, control and time savings while concerns include time to implement, accountability and being "another tool". The document advocates treating dev and ops as symbiotic and providing necessary documentation and resources.
Report
Share
Report
Share
Download to read offline
Recommended
Embrace DevOps: Delivery Value with Puppet Automation
This is the first of series of meetup conducted in AWS Chennai. Session 2 was "Embrace DevOps: Delivery Value with Puppet Automation". AWS Chennai Meetup at 8KMiles.
Agile ncr2016 ppt
Agile without DevOps is incomplete as DevOps helps align development and operations teams to improve customer experiences and respond faster to business needs. DevOps utilizes automation, collaboration between teams, and continuous delivery to support Agile principles like iterative delivery and adapting to change. Specifically, DevOps automates testing, deployment, monitoring and other processes to enable Agile teams to release working software more frequently with high quality and reliability.
Measuring DevOps Performance
What is the best way to measure DevOps performance? There are many ways that people have tried to measure productivity in software delivery in the past -- what works and what doesn’t? In this webinar, Dr. Nicole Forsgren and Robert Reeves will present some lessons learned about measuring software delivery and why it’s important. The webinar will also highlight the key factors driving DevOps performance and offer a preview to some of the challenges on the horizon.
Tune into this webinar to learn about:
Flaws in previous attempts to measure performance
What really matters (hint: focus on outcomes)
The four measures that are key to delivery performance
The *big* difference between high performers and the rest
Why maturity models don’t work
What high performers can do for their organizations
What challenges are up next in technology transformations… things like data, serverless, and security.
Seven deadly wastes
There are seven things that slow your software team down. Learning to conquer each of them is the key delivering faster.
Originating in the Japanese manufacturing industry in the middle of the 20th century, the ideas behind the seven wastes are still hugely relevant to software development today. I explained each one and how it slows you down, then explained how you can defeat the seven wastes and deliver faster than ever before.
Going faster with kanban
The document discusses the Kanban methodology for managing software development projects. It begins by explaining what Kanban is and its origins. It then outlines the key Kanban principles of visualizing workflow, limiting work-in-progress, managing flow, making policies explicit, using feedback loops, and continuously improving. Examples are provided of how to implement these principles using a Kanban board. Advanced techniques like epic clustering and swim lanes are also covered. Tips are given on getting started with Kanban and allowing it to evolve over time.
Why WIP Matters
We prize our ability to multitask yet we rarely acknowledge the impact this has on our ability to get work done. Teams look to process to create efficiencies but ignore one simple tool that has the ability to transform the amount, the speed, and the quality of their work: Limiting Work In Progress. In this talk I will share my stories and experiences of the power that limiting WIP has to bring a team focus, flexibility and follow through.
Introduction to Kanban
Kanban is a method for integrating lean principles into software project delivery. It focuses on visualizing workflow, limiting work-in-progress, and managing flow to improve the current process, reduce task switching, detect and address bottlenecks, and make priorities adaptable. Key aspects of Kanban include limiting WIP for each activity, exposing bottlenecks, measuring and tracking lead time and cycle time, and holding retrospectives to evaluate improvements and keep adjusting policies based on team feedback and data.
DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required
This document discusses predictability in workflows and queues. It begins by defining predictability and noting that predictable systems usually have reduced cycle times and variation. It then discusses how workflows can be viewed as chains of queues and how queues can impact cycle times, throughput, and motivation if allowed to grow too large. The document provides choices that can be made to influence queues, such as using push vs pull systems and prioritization methods. It also recommends monitoring queue size and cycle time ranges as leading indicators of predictability. The overall message is that managers have control over predictability by understanding and managing their queues.
Recommended
Embrace DevOps: Delivery Value with Puppet Automation
This is the first of series of meetup conducted in AWS Chennai. Session 2 was "Embrace DevOps: Delivery Value with Puppet Automation". AWS Chennai Meetup at 8KMiles.
Agile ncr2016 ppt
Agile without DevOps is incomplete as DevOps helps align development and operations teams to improve customer experiences and respond faster to business needs. DevOps utilizes automation, collaboration between teams, and continuous delivery to support Agile principles like iterative delivery and adapting to change. Specifically, DevOps automates testing, deployment, monitoring and other processes to enable Agile teams to release working software more frequently with high quality and reliability.
Measuring DevOps Performance
What is the best way to measure DevOps performance? There are many ways that people have tried to measure productivity in software delivery in the past -- what works and what doesn’t? In this webinar, Dr. Nicole Forsgren and Robert Reeves will present some lessons learned about measuring software delivery and why it’s important. The webinar will also highlight the key factors driving DevOps performance and offer a preview to some of the challenges on the horizon.
Tune into this webinar to learn about:
Flaws in previous attempts to measure performance
What really matters (hint: focus on outcomes)
The four measures that are key to delivery performance
The *big* difference between high performers and the rest
Why maturity models don’t work
What high performers can do for their organizations
What challenges are up next in technology transformations… things like data, serverless, and security.
Seven deadly wastes
There are seven things that slow your software team down. Learning to conquer each of them is the key delivering faster.
Originating in the Japanese manufacturing industry in the middle of the 20th century, the ideas behind the seven wastes are still hugely relevant to software development today. I explained each one and how it slows you down, then explained how you can defeat the seven wastes and deliver faster than ever before.
Going faster with kanban
The document discusses the Kanban methodology for managing software development projects. It begins by explaining what Kanban is and its origins. It then outlines the key Kanban principles of visualizing workflow, limiting work-in-progress, managing flow, making policies explicit, using feedback loops, and continuously improving. Examples are provided of how to implement these principles using a Kanban board. Advanced techniques like epic clustering and swim lanes are also covered. Tips are given on getting started with Kanban and allowing it to evolve over time.
Why WIP Matters
We prize our ability to multitask yet we rarely acknowledge the impact this has on our ability to get work done. Teams look to process to create efficiencies but ignore one simple tool that has the ability to transform the amount, the speed, and the quality of their work: Limiting Work In Progress. In this talk I will share my stories and experiences of the power that limiting WIP has to bring a team focus, flexibility and follow through.
Introduction to Kanban
Kanban is a method for integrating lean principles into software project delivery. It focuses on visualizing workflow, limiting work-in-progress, and managing flow to improve the current process, reduce task switching, detect and address bottlenecks, and make priorities adaptable. Key aspects of Kanban include limiting WIP for each activity, exposing bottlenecks, measuring and tracking lead time and cycle time, and holding retrospectives to evaluate improvements and keep adjusting policies based on team feedback and data.
DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required
This document discusses predictability in workflows and queues. It begins by defining predictability and noting that predictable systems usually have reduced cycle times and variation. It then discusses how workflows can be viewed as chains of queues and how queues can impact cycle times, throughput, and motivation if allowed to grow too large. The document provides choices that can be made to influence queues, such as using push vs pull systems and prioritization methods. It also recommends monitoring queue size and cycle time ranges as leading indicators of predictability. The overall message is that managers have control over predictability by understanding and managing their queues.
Making disaster routine
This document discusses how organizations can prepare for disasters by making failures routine through practices like chaos engineering and active monitoring. It recommends:
1) Practicing failure scenarios as a team to improve disaster response procedures and checklists.
2) Introducing variables like server crashes and network issues in production environments using chaos engineering to test resiliency.
3) Monitoring application health over time to detect performance trends that could indicate future issues.
4) Treating failures as routine events by having established procedures and checklists to minimize panic and focus response efforts.
Moving QA from Reactive to Proactive with qTest
This document discusses moving quality assurance from a reactive to a proactive approach using qTest. It outlines some of the challenges with the current reactive approach, such as crashes occurring and teams blaming the QA team. It then discusses how to take a more proactive approach by efficiently creating and organizing tests, monitoring tests, reusing tests and parameters, consolidating results, and defining test scenarios before coding using behavior driven development. The key recommendations are to record manual and exploratory tests, use a test management system that promotes reuse, radiate test results to development systems, build combined testing dashboards, and use BDD to ensure early test planning.
Extending JIRA to Enable High Volume KPI Benchmarking - Keyur Patel
At Intel, KPIs are measured and reported weekly across multiple, global projects. In this session, we'll cover the business case and architecture behind developing an end-to-end process management system for KPI benchmarking, tracking, and monitoring using JIRA for more than 6,000 users.
DOES16 San Francisco - David Blank-Edelman - Lessons Learned from a Parallel ...
Lessons Learned from a Parallel Universe
David N. Blank-Edelman, Technical Evangelist, Apcera
Just within the last ten or so years, we have seen at least two separate communities evolve at the crossroads of development and operations. The first—DevOps—grew up very much in public, the second matured sequestered within the halls of “special” companies like Google and Facebook and is only now starting to gain visibility and traction in the wider world. The DevOps and Site Reliability Engineering (SRE) communities barely speak, yet both have common ancestors and much to offer each other. Let’s look at what they have in common, how they differ, and what are the key things we can learn from both.
DevOps Enterprise Summit San Francisco 2016
ToT UK 2018- Pizza Kanban Workshop
The document introduces Agile and Kanban concepts. It discusses the origins of Agile in addressing issues with traditional software development approaches. The key principles of Agile are outlined, including valuing customer collaboration over contracts and responding to change over following rigid plans.
Kanban concepts are then introduced through an interactive "pizza game" exercise. The game demonstrates visualizing workflow and limiting work-in-progress to manage flow more effectively. Key Kanban pillars are evaluated based on the game, such as making processes explicit and using feedback loops to continuously improve collaboratively. Overall the document uses the pizza game to translate Agile and Kanban theories into practical lessons.
Building Production-Ready Microservices: DevopsExchangeSF
Michael Kehoe talks about what production-ready means, how to build production-ready microservices and how to measure their readiness
Geek Sync | Kick Start SQL Server 2016 Performance Tips and Tricks
You can watch the replay for this Geek Sync webcast in the IDERA Resource Center: http://ow.ly/DlpB50A5e4j
With every updated SQL Server release, new and efficient features are introduced that database administrators can add to their repository. As many of you know, SQL Server 2016 has introduced lots of new and beneficial features.
Join IDERA and Pinal Dave for a special Geek Sync as we cover a few of the new features in SQL Server 2016. Aside from grasping an overview of these features, you will learn how to use these updates to your advantage.
Improving Test Team Throughput via Architecture by Dustin Williams
A lot of modern testing teams are built from people with some automation experience, developers, and people who think code is something used to open a safe. These diverse backgrounds bring a diverse set of ideas, but don’t always find optimal division of work. With some fairly small changes in automated test design, we can leverage the best skills of all team members to not only improve throughput, but to end up with a better overall product. These design principles help isolate truly challenging code problems and help separate the concerns of test structure and test execution. If your team has ever said (with sad faces) “We’re still automating that”, then come discover how tomorrow you can exclaim “That’s Done!”
Making a Mock by Kelsey Shannahan
Testing within a closed system is easy. Everything is generally accessible and can be interacted with freely. But what happens when the application requires integration with one or more third parties in order to function? In unit tests, we can use mocks and there are many Ruby libraries to make that happen. However, this doesn’t help us much when we’re testing deployed code in end-to-end scenarios or exploratory tests. The solution I found was to build a mock application to mimic the third party. This talk will cover the process and tools used to build the application, the advantages/disadvantages it provides, and explain how this mock is utilized in real-world situations.
Carl shaulis agile_td2014
This document discusses how to achieve continuous delivery through injecting testing at various stages of the software development lifecycle. It outlines the goals of continuous delivery as better quality software, finding and fixing defects faster, and minimizing human error. It then describes the foundations for continuous delivery as design, development, acceptance, automation, monitoring, performance, multi-variant testing, and immunization. Throughout each stage, testing plays a key role in providing feedback, collaborating with teams, and facilitating excellence.
Code Yellow: Helping Operations Top-Heavy Teams the Smart Way
All engineering teams run into trouble from time to time. Alert fatigue, caused by technical debt or a failure to plan for growth, can quickly burn out SREs, overloading both development and operations with reactive work. Layer in the potential for communication problems between teams, and we can find ourselves in a place so troublesome we cannot easily see a path out. At times like this, our natural instinct as reliability engineers is to double down and fight through the issues. Often, however, we need to step back, assess the situation, and ask for help to put the team back on the road to success.
We will look at the process for Code Yellow, the term we use for this process of “righting the ship”, and discuss how to identify teams that are struggling. Through a look at three separate experiences, we will examine some of the root causes, what steps were taken, and how the engineering organization as a whole supports the process.
QASymphony Atlanta Customer User Group Fall 2017
Thanks to all who came out and were part of our first customer user group! All our expectations for the day were exceeded and we hope you feel the same way.
If you weren't able to make it, here's what you missed:
Judy Chung, Product Manager, gave a summary of recent and upcoming features (site level fields, new UI of TestPad) as well as a sneak preview of our newest product (codename: Automation Hub).
Elise Carmichael, VP of Quality, demo-ed several best practice topics, ranging from organizing your qTest repository to reviewing the different automation integration options.
Erika Chestnut, Director of QA at Sterling Talent Solutions, shared her story as a QASymphony customer who recently replaced HP Quality Center with qTest and provided insight into leading change management across her organization.
Geek Sync I Surviving the Holidays with SQL Server
You can watch the replay for this Geek Sync webcast in the IDERA Resource Center: http://ow.ly/3mt150A5fo2
It's the end of the year and you want to have a safe and uninterrupted holiday vacation. Or you're the one who won't be taking time off but you have plenty of co-workers who will and you don't want to be stuck holding the bag if something goes wrong (and Murphy says it will). While this sounds like a pipe dream for anyone who works in IT, there are steps you can take to minimize your chances of being interrupted by that frantic phone call or email from work.
Why Does (My) Monitoring Suck?
Monitoring services is easy, right? Set up a notification that goes out when a certain number increases past a certain threshold to let you know that there’s a problem. But if that’s the case, why are so many teams drowning in alerts and dreading their time on call? The reason is that we tend to monitor the wrong things: reactive alerts, metrics that we don’t completely understand how they impact our service, and capacity alerts. We look at our own view of the service and fail to consider that our customers have a different view.
Come learn to let go of what does not help, and explore how to monitor for what truly matters: what the customer sees. This starts with defining our agreements with our customers, continues through building applications intelligently and instrumenting all the things, and finishes with picking the right signals out of that instrumentation to generate alerts that are actionable, not ones that introduce confusion and noise. We will also touch on capacity planning, and how it should never wake you up. You’ll find it’s possible to assure that you meet your service level objectives while still maximizing your sleep level objectives.
Dev ops
The document discusses DevOps concepts including problems with traditional development approaches, what DevOps is, and CALMS principles. Some key points:
- Traditional approaches had long feedback loops between development and users that hindered agility
- DevOps aims to minimize this loop by having developers also handle operations
- CALMS outlines cultural aspects of DevOps including culture, automation, lean processes, metrics, and sharing knowledge.
Lazar Milovic - No estimates
Many scrum teams struggle with estimations and so did mine. Story points, man days, scaling. What is a story point? How to find the best task for reference?
So we decided to try something different. To try not to estimate, but use historical data instead.
Come and hear more about our jurney.
Everything You Need to Know About Migrating Applications
This document discusses important considerations for migrating applications, including user training, performance tuning, endpoints, site properties, timer scheduling, data migration, foreign keys, database cloning, and a step-by-step process for fetching, mapping, and updating data during migration. Special attention is given to data migration challenges such as database rules, different data storage types and sizes, and ensuring referential integrity.
The changing role of the team leader in a DevOps transformation
There is much discussion about the changing roles of Development and Operations staff when organisations undergo agile/digital/devops transformations. But what about the changing role of the Team Leader?
In pre-agile environments, as a Team Lead, your role is one of structure and co-ordination, it is through you that work routes. You know the skills and capacity of your team and are regularly making decisions about what can and can’t be done.
But as your team starts to work in agile teams, the need for you to keep them busy is reduced, as this is now a responsibility of the product owner and agile team itself.
FMEWT17 Getting Satrted FME 2017 (Ken)
This document provides an overview of new features in FME 2017 including improved connectivity to more formats and web services, more powerful transformations for working with dates and times, enhancements to the data inspector and FME Server, and updates to FME Cloud pricing and capabilities. Key highlights include Active Directory support for FME Server user management, new options for handling failed jobs, and increased compute units and RAM for all FME Cloud instance types.
Supervise your Akka actors - Devoxx
The document discusses supervising Akka actors to increase reliability and performance of a data processing workflow. It describes moving the workflow from a Talend-based ETL process to an Akka actor system with Scala. Key aspects covered include using actors to isolate business logic, implementing supervision strategies to handle failures, adding metrics and health checks for monitoring, and lessons learned around actor system design and testing. The results were successfully moving the workflow to production using the Akka framework.
Configuration Management: What, Why, and How?
The slidedeck from Configuration Management: What, Why, and How? Presented at #HACKPSU 2017 by Joseph Karns. This slide deck covers the following topics:
- What is DevOps
- What is Configuration Management
- Why should you use Configuration Management
- How do you implement Configuration Management
- How does DevOps apply to Configuration Management
Functionality, security and performance monitoring of web assets (e.g. Joomla...
This presentation was from Joomla day 2016 held right here in KLCC Malaysia. Astiostech presented several important factors to consider when monitoring a web service with of course special focus on Joomla. However, these guidelines can be used for just about any web service you may want to monitor. Monitoring is pivotal to a web infrastructure and it should not be considered today as a luxury. With tools like Nagios XI, we can simply start monitoring with mere clicks of a web browser and you're pretty much on the right track.
More Related Content
What's hot
Making disaster routine
This document discusses how organizations can prepare for disasters by making failures routine through practices like chaos engineering and active monitoring. It recommends:
1) Practicing failure scenarios as a team to improve disaster response procedures and checklists.
2) Introducing variables like server crashes and network issues in production environments using chaos engineering to test resiliency.
3) Monitoring application health over time to detect performance trends that could indicate future issues.
4) Treating failures as routine events by having established procedures and checklists to minimize panic and focus response efforts.
Moving QA from Reactive to Proactive with qTest
This document discusses moving quality assurance from a reactive to a proactive approach using qTest. It outlines some of the challenges with the current reactive approach, such as crashes occurring and teams blaming the QA team. It then discusses how to take a more proactive approach by efficiently creating and organizing tests, monitoring tests, reusing tests and parameters, consolidating results, and defining test scenarios before coding using behavior driven development. The key recommendations are to record manual and exploratory tests, use a test management system that promotes reuse, radiate test results to development systems, build combined testing dashboards, and use BDD to ensure early test planning.
Extending JIRA to Enable High Volume KPI Benchmarking - Keyur Patel
At Intel, KPIs are measured and reported weekly across multiple, global projects. In this session, we'll cover the business case and architecture behind developing an end-to-end process management system for KPI benchmarking, tracking, and monitoring using JIRA for more than 6,000 users.
DOES16 San Francisco - David Blank-Edelman - Lessons Learned from a Parallel ...
Lessons Learned from a Parallel Universe
David N. Blank-Edelman, Technical Evangelist, Apcera
Just within the last ten or so years, we have seen at least two separate communities evolve at the crossroads of development and operations. The first—DevOps—grew up very much in public, the second matured sequestered within the halls of “special” companies like Google and Facebook and is only now starting to gain visibility and traction in the wider world. The DevOps and Site Reliability Engineering (SRE) communities barely speak, yet both have common ancestors and much to offer each other. Let’s look at what they have in common, how they differ, and what are the key things we can learn from both.
DevOps Enterprise Summit San Francisco 2016
ToT UK 2018- Pizza Kanban Workshop
The document introduces Agile and Kanban concepts. It discusses the origins of Agile in addressing issues with traditional software development approaches. The key principles of Agile are outlined, including valuing customer collaboration over contracts and responding to change over following rigid plans.
Kanban concepts are then introduced through an interactive "pizza game" exercise. The game demonstrates visualizing workflow and limiting work-in-progress to manage flow more effectively. Key Kanban pillars are evaluated based on the game, such as making processes explicit and using feedback loops to continuously improve collaboratively. Overall the document uses the pizza game to translate Agile and Kanban theories into practical lessons.
Building Production-Ready Microservices: DevopsExchangeSF
Michael Kehoe talks about what production-ready means, how to build production-ready microservices and how to measure their readiness
Geek Sync | Kick Start SQL Server 2016 Performance Tips and Tricks
You can watch the replay for this Geek Sync webcast in the IDERA Resource Center: http://ow.ly/DlpB50A5e4j
With every updated SQL Server release, new and efficient features are introduced that database administrators can add to their repository. As many of you know, SQL Server 2016 has introduced lots of new and beneficial features.
Join IDERA and Pinal Dave for a special Geek Sync as we cover a few of the new features in SQL Server 2016. Aside from grasping an overview of these features, you will learn how to use these updates to your advantage.
Improving Test Team Throughput via Architecture by Dustin Williams
A lot of modern testing teams are built from people with some automation experience, developers, and people who think code is something used to open a safe. These diverse backgrounds bring a diverse set of ideas, but don’t always find optimal division of work. With some fairly small changes in automated test design, we can leverage the best skills of all team members to not only improve throughput, but to end up with a better overall product. These design principles help isolate truly challenging code problems and help separate the concerns of test structure and test execution. If your team has ever said (with sad faces) “We’re still automating that”, then come discover how tomorrow you can exclaim “That’s Done!”
Making a Mock by Kelsey Shannahan
Testing within a closed system is easy. Everything is generally accessible and can be interacted with freely. But what happens when the application requires integration with one or more third parties in order to function? In unit tests, we can use mocks and there are many Ruby libraries to make that happen. However, this doesn’t help us much when we’re testing deployed code in end-to-end scenarios or exploratory tests. The solution I found was to build a mock application to mimic the third party. This talk will cover the process and tools used to build the application, the advantages/disadvantages it provides, and explain how this mock is utilized in real-world situations.
Carl shaulis agile_td2014
This document discusses how to achieve continuous delivery through injecting testing at various stages of the software development lifecycle. It outlines the goals of continuous delivery as better quality software, finding and fixing defects faster, and minimizing human error. It then describes the foundations for continuous delivery as design, development, acceptance, automation, monitoring, performance, multi-variant testing, and immunization. Throughout each stage, testing plays a key role in providing feedback, collaborating with teams, and facilitating excellence.
Code Yellow: Helping Operations Top-Heavy Teams the Smart Way
All engineering teams run into trouble from time to time. Alert fatigue, caused by technical debt or a failure to plan for growth, can quickly burn out SREs, overloading both development and operations with reactive work. Layer in the potential for communication problems between teams, and we can find ourselves in a place so troublesome we cannot easily see a path out. At times like this, our natural instinct as reliability engineers is to double down and fight through the issues. Often, however, we need to step back, assess the situation, and ask for help to put the team back on the road to success.
We will look at the process for Code Yellow, the term we use for this process of “righting the ship”, and discuss how to identify teams that are struggling. Through a look at three separate experiences, we will examine some of the root causes, what steps were taken, and how the engineering organization as a whole supports the process.
QASymphony Atlanta Customer User Group Fall 2017
Thanks to all who came out and were part of our first customer user group! All our expectations for the day were exceeded and we hope you feel the same way.
If you weren't able to make it, here's what you missed:
Judy Chung, Product Manager, gave a summary of recent and upcoming features (site level fields, new UI of TestPad) as well as a sneak preview of our newest product (codename: Automation Hub).
Elise Carmichael, VP of Quality, demo-ed several best practice topics, ranging from organizing your qTest repository to reviewing the different automation integration options.
Erika Chestnut, Director of QA at Sterling Talent Solutions, shared her story as a QASymphony customer who recently replaced HP Quality Center with qTest and provided insight into leading change management across her organization.
Geek Sync I Surviving the Holidays with SQL Server
You can watch the replay for this Geek Sync webcast in the IDERA Resource Center: http://ow.ly/3mt150A5fo2
It's the end of the year and you want to have a safe and uninterrupted holiday vacation. Or you're the one who won't be taking time off but you have plenty of co-workers who will and you don't want to be stuck holding the bag if something goes wrong (and Murphy says it will). While this sounds like a pipe dream for anyone who works in IT, there are steps you can take to minimize your chances of being interrupted by that frantic phone call or email from work.
Why Does (My) Monitoring Suck?
Monitoring services is easy, right? Set up a notification that goes out when a certain number increases past a certain threshold to let you know that there’s a problem. But if that’s the case, why are so many teams drowning in alerts and dreading their time on call? The reason is that we tend to monitor the wrong things: reactive alerts, metrics that we don’t completely understand how they impact our service, and capacity alerts. We look at our own view of the service and fail to consider that our customers have a different view.
Come learn to let go of what does not help, and explore how to monitor for what truly matters: what the customer sees. This starts with defining our agreements with our customers, continues through building applications intelligently and instrumenting all the things, and finishes with picking the right signals out of that instrumentation to generate alerts that are actionable, not ones that introduce confusion and noise. We will also touch on capacity planning, and how it should never wake you up. You’ll find it’s possible to assure that you meet your service level objectives while still maximizing your sleep level objectives.
Dev ops
The document discusses DevOps concepts including problems with traditional development approaches, what DevOps is, and CALMS principles. Some key points:
- Traditional approaches had long feedback loops between development and users that hindered agility
- DevOps aims to minimize this loop by having developers also handle operations
- CALMS outlines cultural aspects of DevOps including culture, automation, lean processes, metrics, and sharing knowledge.
Lazar Milovic - No estimates
Many scrum teams struggle with estimations and so did mine. Story points, man days, scaling. What is a story point? How to find the best task for reference?
So we decided to try something different. To try not to estimate, but use historical data instead.
Come and hear more about our jurney.
Everything You Need to Know About Migrating Applications
This document discusses important considerations for migrating applications, including user training, performance tuning, endpoints, site properties, timer scheduling, data migration, foreign keys, database cloning, and a step-by-step process for fetching, mapping, and updating data during migration. Special attention is given to data migration challenges such as database rules, different data storage types and sizes, and ensuring referential integrity.
The changing role of the team leader in a DevOps transformation
There is much discussion about the changing roles of Development and Operations staff when organisations undergo agile/digital/devops transformations. But what about the changing role of the Team Leader?
In pre-agile environments, as a Team Lead, your role is one of structure and co-ordination, it is through you that work routes. You know the skills and capacity of your team and are regularly making decisions about what can and can’t be done.
But as your team starts to work in agile teams, the need for you to keep them busy is reduced, as this is now a responsibility of the product owner and agile team itself.
FMEWT17 Getting Satrted FME 2017 (Ken)
This document provides an overview of new features in FME 2017 including improved connectivity to more formats and web services, more powerful transformations for working with dates and times, enhancements to the data inspector and FME Server, and updates to FME Cloud pricing and capabilities. Key highlights include Active Directory support for FME Server user management, new options for handling failed jobs, and increased compute units and RAM for all FME Cloud instance types.
Supervise your Akka actors - Devoxx
The document discusses supervising Akka actors to increase reliability and performance of a data processing workflow. It describes moving the workflow from a Talend-based ETL process to an Akka actor system with Scala. Key aspects covered include using actors to isolate business logic, implementing supervision strategies to handle failures, adding metrics and health checks for monitoring, and lessons learned around actor system design and testing. The results were successfully moving the workflow to production using the Akka framework.
What's hot (20)
Extending JIRA to Enable High Volume KPI Benchmarking - Keyur Patel
Extending JIRA to Enable High Volume KPI Benchmarking - Keyur Patel
DOES16 San Francisco - David Blank-Edelman - Lessons Learned from a Parallel ...
DOES16 San Francisco - David Blank-Edelman - Lessons Learned from a Parallel ...
Building Production-Ready Microservices: DevopsExchangeSF
Building Production-Ready Microservices: DevopsExchangeSF
Geek Sync | Kick Start SQL Server 2016 Performance Tips and Tricks
Geek Sync | Kick Start SQL Server 2016 Performance Tips and Tricks
Improving Test Team Throughput via Architecture by Dustin Williams
Improving Test Team Throughput via Architecture by Dustin Williams
Code Yellow: Helping Operations Top-Heavy Teams the Smart Way
Code Yellow: Helping Operations Top-Heavy Teams the Smart Way
Geek Sync I Surviving the Holidays with SQL Server
Geek Sync I Surviving the Holidays with SQL Server
Everything You Need to Know About Migrating Applications
Everything You Need to Know About Migrating Applications
The changing role of the team leader in a DevOps transformation
The changing role of the team leader in a DevOps transformation
Similar to Puppet camp 2015 phoenix david patterson
Configuration Management: What, Why, and How?
The slidedeck from Configuration Management: What, Why, and How? Presented at #HACKPSU 2017 by Joseph Karns. This slide deck covers the following topics:
- What is DevOps
- What is Configuration Management
- Why should you use Configuration Management
- How do you implement Configuration Management
- How does DevOps apply to Configuration Management
Functionality, security and performance monitoring of web assets (e.g. Joomla...
This presentation was from Joomla day 2016 held right here in KLCC Malaysia. Astiostech presented several important factors to consider when monitoring a web service with of course special focus on Joomla. However, these guidelines can be used for just about any web service you may want to monitor. Monitoring is pivotal to a web infrastructure and it should not be considered today as a luxury. With tools like Nagios XI, we can simply start monitoring with mere clicks of a web browser and you're pretty much on the right track.
Making security-agile matt-tesauro
Software development is happening faster then ever. Can your AppSec program keep up? This talk shows how an AppSec pipeline can help speed things up.
Road to Continuous Delivery - Wix.com
The document discusses Aviran Mordo's presentation on Wix's journey towards continuous delivery. Some key points:
- Wix has transitioned from traditional waterfall development to continuous delivery, deploying changes around 60 times per day.
- This was enabled by adopting DevOps practices like test-driven development, feature toggles, A/B testing, automated deployments, and monitoring.
- Tools like App-Info, New Relic, and custom deployment tools were crucial for implementing continuous delivery at Wix's scale across multiple data centers and cloud providers.
- Transitioning required cultural changes, empowering developers, and embracing risk and failure to improve continuously. Wix now develops and replaces infrastructure
Continuous Delivery Distilled
Matt Callanan takes the 15 chapters of the famous "Continuous Delivery" book by Jez Humble & Dave Farey and distills it down into 1 hour of convincing arguments, walking through the pieces involved to make it happen including cultural challenges, automated testing, automated deployment & deployment pipelines. Not sure how to get started with DevOps? Finding it hard to convince colleagues & managers that CD is the way forward? Matt has used this presentation to help facilitate enterprise-wide adoption of Continuous Delivery. Slides from a presentation given at DevOps Brisbane March 2014.
The Continuous delivery Value @ codemotion 2014
System Crash, failure data migration, partial update: issues that no one would ever want to meet during the deploy and ... hoping for the best is not enough.
The deployment activity is important as those that precede it. The Continuous Delivery will give you low risk, cheap, fast, predictable delivery and ... soundly.
The Continuous delivery value - Funaro
This document discusses the benefits of continuous delivery and deployment. It notes that without proper processes, deployments can fail due to crashes, failed migrations, or interrupted updates when introducing new features. Continuous delivery uses tools and methodologies to make releases low risk, fast, predictable, and ensure smooth deployments. The document outlines some of the key aspects of continuous delivery like source code management, continuous integration, automated deployments, monitoring, and root cause analysis. It discusses how these practices can help make software releases cheaper, more frequent, rapid, and reduce stress and errors compared to traditional release processes.
Dev ops ci-ap-is-oh-my_security-gone-agile_ut-austin
An overview of how to change security from a reactive part of the org to a collaborative part of the agile development process. Using concepts from agile and DevOps, how can applicaton security get as nimble as product development has become.
Django production
This was a presentation given at San Diego Python's Django Day:
http://www.meetup.com/pythonsd/events/95751792/
https://github.com/pythonsd/learning-django
Devops, Secops, Opsec, DevSec *ops *.* ?
This document discusses the DevOps movement and related concepts. It provides background on how development and operations teams historically worked separately ("Devs vs Ops") and the problems that caused. DevOps aims to break down barriers between teams through practices like automation, continuous integration/delivery, infrastructure as code, and collaboration between teams from the beginning of a project. The document outlines problems DevOps aims to solve and gives examples of tools and approaches for bringing development and operations cultures together.
Lucas Gravley - HP - Self-Healing And Monitoring in a DevOps world
Managing one or two unique machines in an ad-hoc manner is not a story that many people talk about nowadays. Today, small teams need to manage hundreds or thousands of nodes, serving a myriad of purposes, running any number of critical Dev and Ops workloads. And they have to do it in a way that still leaves time for unplanned and strategic work.
Learn how HP ties DevOps automation, monitoring information and ChatOps collaboration together to eliminate manual, error-prone work and keep critical services running
Devops, the future is here, it's just not evenly distributed yet.
This document discusses the DevOps movement and how operations and development teams can work more collaboratively. Some key points:
- DevOps aims to break down barriers between development and operations teams through better communication and automation.
- In the past, developers would deploy code without considering operational requirements, leading to problems once code was in production. DevOps promotes developing and deploying code as a team effort between devs and ops.
- Automating processes like configuration management, continuous integration, deployment and monitoring helps align dev and ops goals and allows more frequent, lower-risk deployments. Tools like Puppet, Chef, Jenkins and Nagios are mentioned.
- The document advocates for practices like test-driven
Design patterns for efficient DevOps processes - Rebecca Fitzhugh - DevOpsDay...
The document discusses design patterns for efficient DevOps processes including value stream mapping, release engineering, test automation, and change management. It provides recommendations such as collecting current state information directly, ensuring release engineers understand intended deployments, automating error-prone steps, centralizing test coordination, and making change management a priority integrated within the DevOps pipeline. Design patterns that increase efficiency include continuous delivery pipelines, testing all levels from unit to integration to functionality, and establishing different change modes to balance speed, quality, and risk.
Automate Everything! (No stress development/Tallinn)
Brief story about how to bring much happiness to live using modern technologies and some good engineering principles. To learn more, aim yourself to http://dev.solita.fi/ - or just decide to improve a bit today.
Automating Security in Cloud Workloads with DevSecOps
This session is designed to teach security engineers, developers, solutions architects, and other technical security practitioners how to use a DevSecOps approach to design and build robust security controls at cloud-scale. This session walks through the design considerations of operating high-assurance workloads on top of the AWS platform and provides examples of how to automate configuration management and generate audit evidence for your own workloads. We’ll discuss practical examples using real code for automating security tasks, then dive deeper to map the configurations against various industry frameworks. This advanced session showcases how continuous integration and deployment pipelines can accelerate the speed of security teams and improve collaboration with software development teams.
Devops at Startup Weekend BXL
Kris Buytaert discusses the Devops movement and how bringing developers and operations teams together earlier improves systems. He advocates for automation throughout the development and deployment process, from version control and testing to configuration management, monitoring, and upgrades. Adopting a Devops culture and practices like continuous integration, delivery, and deployment can help teams deploy better systems faster at lower risk.
5 Steps on the Way to Continuous Delivery
Slides from Andrew Phillips' talk on 23 April 2013 at JAX 2013, Mainz, Germany: http://jax.de/2013/sessions?tid=2983#session-25099
Ncerc rlmca202 adm m1 ssm
The document discusses principles of continuous delivery and deployment pipelines. It introduces the concept of a deployment pipeline which is an automated implementation of building, deploying, testing and releasing an application. Every change triggers a new instance of the pipeline which first creates binaries and installers, runs tests on them, and once all tests pass, releases the candidate. The goal is to deliver software as quickly as possible by having an automated and reliable process.
Continuous Delivery Decision points
This document discusses continuous delivery decision points and environments. It notes that as DevOps shifts focus from build/deploy automation to continuous delivery, test environments are proliferating and need to be provisioned and managed efficiently. It also emphasizes that collaboration around testing is important, and teams must make strategic decisions about promoting code changes to subsequent stages or iterating further. Maintaining properly designed automated and manual tests is key to making these decisions. Organizational culture and leadership must also support empowering developers and teams to deliver changes incrementally.
SecDevOps: The New Black of IT
Just when you thought DevOps was the new black, along comes SecDevOps. In this webinar, Andrew Storms, Sr. Director of DevOps at CloudPassage and Alan Shimel Co-Founder of DevOps.com will discuss the emerging hybrid role of DevOps and Security. Tune in to hear them cover the following topics and why DevOps should want to play a bigger part in security:
Go beyond the traditional using DevOps tools, practices, methods to create a force multiplier of SecDevOps
Orchestrate and Automate - Deputize everyone to incorporate security into their day to day responsibilities
Examples of security automation, case situations minimizing risk and driving flexibility for DevOps
See how SaaS provider CloudPassage integrates security into its own development and operations workflows
Similar to Puppet camp 2015 phoenix david patterson (20)
Functionality, security and performance monitoring of web assets (e.g. Joomla...
Functionality, security and performance monitoring of web assets (e.g. Joomla...
Dev ops ci-ap-is-oh-my_security-gone-agile_ut-austin
Dev ops ci-ap-is-oh-my_security-gone-agile_ut-austin
Lucas Gravley - HP - Self-Healing And Monitoring in a DevOps world
Lucas Gravley - HP - Self-Healing And Monitoring in a DevOps world
Devops, the future is here, it's just not evenly distributed yet.
Devops, the future is here, it's just not evenly distributed yet.
Design patterns for efficient DevOps processes - Rebecca Fitzhugh - DevOpsDay...
Design patterns for efficient DevOps processes - Rebecca Fitzhugh - DevOpsDay...
Automate Everything! (No stress development/Tallinn)
Automate Everything! (No stress development/Tallinn)
Automating Security in Cloud Workloads with DevSecOps
Automating Security in Cloud Workloads with DevSecOps
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
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
Ensuring the optimal performance of your audio-visual (AV) equipment is crucial for delivering exceptional experiences. AV performance validation is a critical process that verifies the quality and functionality of your AV setup. Whether you're a content creator, a business conducting webinars, or a homeowner creating a home theater, validating your AV performance is essential.
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
Orca: Nocode Graphical Editor for Container Orchestration
Tool demo on CEDI/SISTEDES/JISBD2024 at A Coruña, Spain. 2024.06.18
"Orca: Nocode Graphical Editor for Container Orchestration"
by Pedro J. Molina PhD. from Metadev
Superpower Your Apache Kafka Applications Development with Complementary Open...
Kafka Summit talk (Bangalore, India, May 2, 2024, https://events.bizzabo.com/573863/agenda/session/1300469 )
Many Apache Kafka use cases take advantage of Kafka’s ability to integrate multiple heterogeneous systems for stream processing and real-time machine learning scenarios. But Kafka also exists in a rich ecosystem of related but complementary stream processing technologies and tools, particularly from the open-source community. In this talk, we’ll take you on a tour of a selection of complementary tools that can make Kafka even more powerful. We’ll focus on tools for stream processing and querying, streaming machine learning, stream visibility and observation, stream meta-data, stream visualisation, stream development including testing and the use of Generative AI and LLMs, and stream performance and scalability. By the end you will have a good idea of the types of Kafka “superhero” tools that exist, which are my favourites (and what superpowers they have), and how they combine to save your Kafka applications development universe from swamploads of data stagnation monsters!
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
Presented at NLJUG's J-Spring 2024.
Stork Product Overview: An AI-Powered Autonomous Delivery Fleet
Imagine a world where instead of blue and brown trucks dropping parcels on our porches, a buzzing drove of drones delivered our goods. Now imagine those drones are controlled by 3 purpose-built AI designed to ensure all packages were delivered as quickly and as economically as possible That's what Stork is all about.
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Consistent toolbox talks are critical for maintaining workplace safety, as they provide regular opportunities to address specific hazards and reinforce safe practices.
These brief, focused sessions ensure that safety is a continual conversation rather than a one-time event, which helps keep safety protocols fresh in employees' minds. Studies have shown that shorter, more frequent training sessions are more effective for retention and behavior change compared to longer, infrequent sessions.
Engaging workers regularly, toolbox talks promote a culture of safety, empower employees to voice concerns, and ultimately reduce the likelihood of accidents and injuries on site.
The traditional method of conducting safety talks with paper documents and lengthy meetings is not only time-consuming but also less effective. Manual tracking of attendance and compliance is prone to errors and inconsistencies, leading to gaps in safety communication and potential non-compliance with OSHA regulations. Switching to a digital solution like Safelyio offers significant advantages.
Safelyio automates the delivery and documentation of safety talks, ensuring consistency and accessibility. The microlearning approach breaks down complex safety protocols into manageable, bite-sized pieces, making it easier for employees to absorb and retain information.
This method minimizes disruptions to work schedules, eliminates the hassle of paperwork, and ensures that all safety communications are tracked and recorded accurately. Ultimately, using a digital platform like Safelyio enhances engagement, compliance, and overall safety performance on site. https://safelyio.com/
TMU毕业证书精仿办理
多伦多都会大学毕业证成绩单(留信网认证)【176555708微信】不能毕业办理假文凭回国找工作
【多伦多都会大学毕业证成绩单仿制】（176555708微信☀️）伪造研究生学位证书TMU毕业证文凭,多伦多都会大学文凭证书学籍信息入库,多伦多都会大学学位证书留学高校学位证书补办
【TMU毕业证【微信176555708】多伦多都会大学文凭学历】【微信176555708】【多伦多都会大学文凭学历证书】【多伦多都会大学毕业证书与成绩单样本图片】毕业证书补办 Fake Degree做学费单【毕业证明信-推荐信】成绩单，录取通知书，Offer，在读证明，雅思托福成绩单，真实大使馆教育部认证，回国人员证明，留信网认证。网上存档永久可查！
Assure Contact Center Experiences for Your Customers With ThousandEyes
Assure Contact Center Experiences for Your Customers With ThousandEyes
WWDC 2024 Keynote Review: For CocoaCoders Austin
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
一比一原版(sdsu毕业证书)圣地亚哥州立大学毕业证如何办理
原版一模一样【微信：741003700 】【(sdsu毕业证书)圣地亚哥州立大学毕业证成绩单】【微信：741003700 】学位证，留信认证（真实可查，永久存档）原件一模一样纸张工艺/offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原。
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
【主营项目】
一.毕业证【q微741003700】成绩单、使馆认证、教育部认证、雅思托福成绩单、学生卡等！
二.真实使馆公证(即留学回国人员证明,不成功不收费)
三.真实教育部学历学位认证（教育部存档！教育部留服网站永久可查）
四.办理各国各大学文凭(一对一专业服务,可全程监控跟踪进度)
如果您处于以下几种情况：
◇在校期间，因各种原因未能顺利毕业……拿不到官方毕业证【q/微741003700】
◇面对父母的压力，希望尽快拿到；
◇不清楚认证流程以及材料该如何准备；
◇回国时间很长，忘记办理；
◇回国马上就要找工作，办给用人单位看；
◇企事业单位必须要求办理的
◇需要报考公务员、购买免税车、落转户口
◇申请留学生创业基金
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】外观非常简单，由纸质材料制成，上面印有校徽、校名、毕业生姓名、专业等信息。
办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】格式相对统一，各专业都有相应的模板。通常包括以下部分：
校徽：象征着学校的荣誉和传承。
校名:学校英文全称
授予学位：本部分将注明获得的具体学位名称。
毕业生姓名：这是最重要的信息之一，标志着该证书是由特定人员获得的。
颁发日期：这是毕业正式生效的时间，也代表着毕业生学业的结束。
其他信息：根据不同的专业和学位，可能会有一些特定的信息或章节。
办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】价值很高，需要妥善保管。一般来说，应放置在安全、干燥、防潮的地方，避免长时间暴露在阳光下。如需使用，最好使用复印件而不是原件，以免丢失。
综上所述，办理(sdsu毕业证书)圣地亚哥州立大学毕业证【微信：741003700 】是证明身份和学历的高价值文件。外观简单庄重，格式统一，包括重要的个人信息和发布日期。对持有人来说，妥善保管是非常重要的。
Upturn India Technologies - Web development company in Nashik
Nashik's top web development company, Upturn India Technologies, crafts innovative digital solutions for your success. Partner with us and achieve your goals
The Rising Future of CPaaS in the Middle East 2024
Explore "The Rising Future of CPaaS in the Middle East in 2024" with this comprehensive PPT presentation. Discover how Communication Platforms as a Service (CPaaS) is transforming communication across various sectors in the Middle East.
42 Ways to Generate Real Estate Leads - Sellxpert
Generate hot real estate leads with these simple strategies. 42 innovative ways to attract clients in the real estate industry.
Voxxed Days Trieste 2024 - Unleashing the Power of Vector Search and Semantic...
Vector databases are redefining data handling, enabling semantic searches across text, images, and audio encoded as vectors.
Redis OM for Java simplifies this innovative approach, making it accessible even for those new to vector data.
This presentation explores the cutting-edge features of vector search and semantic caching in Java, highlighting the Redis OM library through a demonstration application.
Redis OM has evolved to embrace the transformative world of vector database technology, now supporting Redis vector search and seamless integration with OpenAI, Hugging Face, LangChain, and LlamaIndex. This talk highlights the latest advancements in Redis OM, focusing on how it simplifies the complex process of vector indexing, data modeling, and querying for AI-powered applications. We will explore the new capabilities of Redis OM, including intuitive vector search interfaces and semantic caching, which reduce the overhead of large language model (LLM) calls.
一比一原版(USF毕业证)旧金山大学毕业证如何办理
USF硕士毕业证成绩单【微信95270640】一比一伪造旧金山大学文凭@假冒USF毕业证成绩单+Q微信95270640办理USF学位证书@仿造USF毕业文凭证书@购买旧金山大学毕业证成绩单USF真实使馆认证/真实留信认证回国人员证明
#一整套旧金山大学文凭证件办理#—包含旧金山大学旧金山大学本科毕业证成绩单学历认证|使馆认证|归国人员证明|教育部认证|留信网认证永远存档教育部学历学位认证查询办理国外文凭国外学历学位认证#我们提供全套办理服务。
一整套留学文凭证件服务：
一：旧金山大学旧金山大学本科毕业证成绩单毕业证 #成绩单等全套材料从防伪到印刷水印底纹到钢印烫金
二：真实使馆认证（留学人员回国证明）使馆存档
三：真实教育部认证教育部存档教育部留服网站永久可查
四：留信认证留学生信息网站永久可查
国外毕业证学位证成绩单办理方法：
1客户提供办理旧金山大学旧金山大学本科毕业证成绩单信息：姓名生日专业学位毕业时间等（如信息不确定可以咨询顾问：我们有专业老师帮你查询）；
2开始安排制作毕业证成绩单电子图；
3毕业证成绩单电子版做好以后发送给您确认；
4毕业证成绩单电子版您确认信息无误之后安排制作成品；
5成品做好拍照或者视频给您确认；
6快递给客户（国内顺丰国外DHLUPS等快读邮寄）。
教育部文凭学历认证认证的用途：
如果您计划在国内发展那么办理国内教育部认证是必不可少的。事业性用人单位如银行国企公务员在您应聘时都会需要您提供这个认证。其他私营 #外企企业无需提供！办理教育部认证所需资料众多且烦琐所有材料您都必须提供原件我们凭借丰富的经验帮您快速整合材料让您少走弯路。
实体公司专业为您服务如有需要请联系我: 微信95270640奈一次次令他失望山娃今年岁上五年级识得很多字从走出小屋开始山娃就知道父亲的家和工地共有一个很动听的名字——天河工地的底层空空荡荡很宽阔很凉爽在地上铺上报纸和水泥袋父亲和工人们中午全睡在地上地面坑坑洼洼山娃曾多次绊倒过也曾有长铁钉穿透凉鞋刺在脚板上但山娃不怕工地上也常有五六个从乡下来的小学生他们的父母亲也是高楼上的建筑工人小伙伴来自不同省份都操着带有浓重口音的普通话可不知为啥山娃不仅很快与他们熟识了
Mobile App Development Company In Noida | Drona Infotech
React.js, a JavaScript library developed by Facebook, has gained immense popularity for building user interfaces, especially for single-page applications. Over the years, React has evolved and expanded its capabilities, becoming a preferred choice for mobile app development. This article will explore why React.js is an excellent choice for the Best Mobile App development company in Noida.
Visit Us For Information: https://www.linkedin.com/pulse/what-makes-reactjs-stand-out-mobile-app-development-rajesh-rai-pihvf/
Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...
Closing talk for the Performance Engineering track at Community Over Code EU (Bratislava, Slovakia, June 5 2024) https://eu.communityovercode.org/sessions/2024/why-apache-kafka-clusters-are-like-galaxies-and-other-cosmic-kafka-quandaries-explored/ Instaclustr (now part of NetApp) manages 100s of Apache Kafka clusters of many different sizes, for a variety of use cases and customers. For the last 7 years I’ve been focused outwardly on exploring Kafka application development challenges, but recently I decided to look inward and see what I could discover about the performance, scalability and resource characteristics of the Kafka clusters themselves. Using a suite of Performance Engineering techniques, I will reveal some surprising discoveries about cosmic Kafka mysteries in our data centres, related to: cluster sizes and distribution (using Zipf’s Law), horizontal vs. vertical scalability, and predicting Kafka performance using metrics, modelling and regression techniques. These insights are relevant to Kafka developers and operators.
Recently uploaded (20)
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
Orca: Nocode Graphical Editor for Container Orchestration
Orca: Nocode Graphical Editor for Container Orchestration
Superpower Your Apache Kafka Applications Development with Complementary Open...
Superpower Your Apache Kafka Applications Development with Complementary Open...
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
J-Spring 2024 - Going serverless with Quarkus, GraalVM native images and AWS ...
Stork Product Overview: An AI-Powered Autonomous Delivery Fleet
Stork Product Overview: An AI-Powered Autonomous Delivery Fleet
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Assure Contact Center Experiences for Your Customers With ThousandEyes
Assure Contact Center Experiences for Your Customers With ThousandEyes
Upturn India Technologies - Web development company in Nashik
Upturn India Technologies - Web development company in Nashik
The Rising Future of CPaaS in the Middle East 2024
The Rising Future of CPaaS in the Middle East 2024
Voxxed Days Trieste 2024 - Unleashing the Power of Vector Search and Semantic...
Voxxed Days Trieste 2024 - Unleashing the Power of Vector Search and Semantic...
Mobile App Development Company In Noida | Drona Infotech
Mobile App Development Company In Noida | Drona Infotech
Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...
Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...
Puppet camp 2015 phoenix david patterson
- 1. My Soul has a Price Selling management and developers on Puppet
- 2. About me • David Patterson - david.patterson@apollo.edu - david@damnetwork.net • Using linux since approx ’95 - Are you on my lawn? • As an admin since late 90’s • Went from small Co. -> Enterprise • Yggdrasil, Slackware, Redhat, OEL, Mandrake, Debian, Gentoo, and yes, Ubuntu. • Currently Apollo Global • Puppet for approx 2 years • Still consider myself a newbie with Puppet
- 3. Why? You *have* to have approval and buy-in.
- 4. 2 stages • Pre - Gather your info and present it • During - Planning, development and deployment
- 5. Management Benefits Concerns Control Time Savings Stability Cost of Tool Reports Cost of Time to Implement Graphs Accountability
- 6. Developers Benefits Concerns Consistency Control Speed Managed Items Stability Accountability Ease of Use “Another PITA tool. Ugh”
- 7. Configuration Management I hope this works, it’s my first second third.
- 8. My Philosophy • Provide stable, secure, consistent servers • Dev/Apps and Ops are symbiotic • Provide documentation • Provide Dev/Apps everything they need to do *their* job
- 9. Our current state: Cats. • They do what they want. • They answer to no-one. • They go where they want. • I don’t like cats.
- 11. Why Dogs? They can be trained to do anything.
- 12. Almost.
- 13. Mcollective
- 14. • Automation • Config Consistency • Build Consistency • Security and Compliance • Rapid Deployment
- 15. • Automation • Config Consistency • Build Consistency • Control • Control • Control • Security Compliance • Speed • Control • Rapid Deployments • Control • Control • Control • Control • Control Stability Control Consistency Speed
- 16. Separate the data from the code. • Hierarchal data • host -> app -> role -> Env -> DC • One place to change data • Less repetition • Quickly add new hierarchy • No changes to puppet code
- 18. TimeSavings
- 20. Reports
- 27. Ease of Use Managed Items
- 28. Ease of Use
- 29. Accountability
- 30. Collectives
- 31. What version of a package TimeSavings
- 33. Check file differences Ease of Use
- 34. Feb March April May June July Aug RP Dev RP QA RP Prod UK Dev UK QA UK Prod I HAVE A TIMELINE!!! Sorta..
- 35. What’s next? • Build Automation • Access Control • Easy Reporting • Patching • Lots of beer time for the linux dudes
- 36. They’re sold!!! Now what?
- 37. Phase II: Development and Implementation • Communicate • Put your plan in an easily accessible place • Address Concerns • Be Available
- 38. Questions?