Introducing Puppet Enterprise’s Event Inspector
-
Upload
puppet-labs -
Category
Technology
-
view
1.245 -
download
1
description
Transcript of Introducing Puppet Enterprise’s Event Inspector
Introducing Puppet Enterprise’s event inspectorJoe WagnerSenior User Experience Designer | Puppet Labs @jcwag
puppetconf.com #puppetconf
What is event inspector?
puppetconf.com #puppetconf
What is event inspector?
puppetconf.com #puppetconf
What is event inspector?
puppetconf.com #puppetconf
What is event inspector?
puppetconf.com #puppetconf
What is event inspector?
puppetconf.com #puppetconf
event - Puppet’s attempt to modify an individual property of a given resource.
What is event inspector?
puppetconf.com #puppetconf
Types of events
Failure - Puppet was unsuccessful enforcing a configuration.
Change - Puppet was successful enforcing a configuration and this resulted in a change to a resource’s property.
Skip - Puppet was unable to enforce a configuration due to failed enforcement elsewhere.
Noop - Puppet simulated enforcing a configuration.
puppetconf.com #puppetconf
July 1, 2012
puppetconf.com #puppetconf
July 1, 2012(~ 1 year ago)
puppetconf.com #puppetconf
PE: Home screen reporting
puppetconf.com #puppetconf
PE: Node run reports
puppetconf.com #puppetconf
PE: Inventory search
puppetconf.com #puppetconf
PE: External node classifier
puppetconf.com #puppetconf
PE: Live Management
puppetconf.com #puppetconf
Understanding your needs
puppetconf.com #puppetconf
Our fabulous researchers
JennyFei
puppetconf.com #puppetconf
Test Pilot Program
Last year: 130 test pilotsThis year: 400 and counting
puppetconf.com #puppetconf
You are all snowflakes.
puppetconf.com #puppetconf
GUI / CLI Showdown
• control
• speed
• scripting
• display of information
• manipulation of information
CLI wins: GUI wins:
puppetconf.com #puppetconf
PE reporting
puppetconf.com #puppetconf
PE reporting
puppetconf.com #puppetconf
Early prototype testing
puppetconf.com #puppetconf
Focus on most recent events
“To me, this is one of the important aspects to quickly see visually what has happened on the system.”
-- test pilot
“It would change drastically the way colleagues are applying manifests and would give better feedback loop for node state and execution time.”
-- test pilot
puppetconf.com #puppetconf
Evolution of the prototype
puppetconf.com #puppetconf
Beyond nodes
"You might expect an application to be made of certain components, like java, and a development container. Ideally you’d have a grouping with some meaning that would be functional."
-- test pilot
“When we’re getting into a couple hundred nodes, I’m not looking at individual nodes changed, I’m looking at changes to Apache.”
-- test pilot
puppetconf.com #puppetconf
Node View
puppetconf.com #puppetconf
Class View
puppetconf.com #puppetconf
Resource View
puppetconf.com #puppetconf
Three views into your infrastructure
class = what
node = where
resource = how
puppetconf.com #puppetconf
August 23, 2013
puppetconf.com #puppetconf
August 23, 2013(Today)
puppetconf.com #puppetconf
Summary Pane
puppetconf.com #puppetconf
Node details
puppetconf.com #puppetconf
Event detail pane
puppetconf.com #puppetconf
What’s next.
puppetconf.com #puppetconf
Future improvements:robust filtering
puppetconf.com #puppetconf
Future improvements:comparing node events
puppetconf.com #puppetconf
Future improvements:running puppet
puppetconf.com #puppetconf
Future improvements:main screen redesign
puppetconf.com #puppetconf
Your questions.
Thank YouJoe WagnerSenior User Experience Designer | Puppet Labs @jcwag
Collaborate. Automate. Ship.