You’re configuring your systems using Puppet, but where do you go to see if your changes worked? How do you troubleshoot failures? We’ve been talking to Puppet users like you to design a tool for Puppet Enterprise that solves these problems. Come learn about this new robust reporting application. Speakers Joe Wagner Senior User Experience Designer, Puppet Labs Joe Wagner is lead User Experience Designer for Puppet Enterprise. He has 12 years experience reducing frustration and increasing satisfaction by designing tools that do what their users need them to do. He can be found Friday afternoons walking with his two daughters through the Portland office, sharing their excitement in finding the puppets painted on the office walls.

1. Introducing Puppet
Enterprise’s event inspector
Joe Wagner
Senior User Experience Designer | Puppet Labs
@jcwag

2. puppetconf.com #puppetconf
What is event inspector?

3. puppetconf.com #puppetconf
What is event inspector?

4. puppetconf.com #puppetconf
What is event inspector?

5. puppetconf.com #puppetconf
What is event inspector?

6. puppetconf.com #puppetconf
What is event inspector?

7. puppetconf.com #puppetconf
event - Puppet’s attempt to modify an
individual property of a given resource.
What is event inspector?

8. 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.

9. puppetconf.com #puppetconf
July 1, 2012

10. puppetconf.com #puppetconf
July 1, 2012
(~ 1 year ago)

11. puppetconf.com #puppetconf
PE: Home screen reporting

12. puppetconf.com #puppetconf
PE: Node run reports

13. puppetconf.com #puppetconf
PE: Inventory search

14. puppetconf.com #puppetconf
PE: External node classifier

15. puppetconf.com #puppetconf
PE: Live Management

16. puppetconf.com #puppetconf
Understanding your needs

17. puppetconf.com #puppetconf
Our fabulous researchers
Jenny
Fei

18. puppetconf.com #puppetconf
Test Pilot Program
Last year: 130 test pilots
This year: 400 and counting

19. puppetconf.com #puppetconf
You are all snowflakes.

20. puppetconf.com #puppetconf
GUI / CLI Showdown
• control
• speed
• scripting
• display of information
• manipulation of
information
CLI wins: GUI wins:

21. puppetconf.com #puppetconf
PE reporting

22. puppetconf.com #puppetconf
PE reporting

23. puppetconf.com #puppetconf
Early prototype testing

24. 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

25. puppetconf.com #puppetconf
Evolution of the prototype

26. 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

27. puppetconf.com #puppetconf
Node View

28. puppetconf.com #puppetconf
Class View

29. puppetconf.com #puppetconf
Resource View

30. puppetconf.com #puppetconf
Three views into your
infrastructure
class = what
node = where
resource = how

31. puppetconf.com #puppetconf
August 23, 2013

32. puppetconf.com #puppetconf
August 23, 2013
(Today)

33. puppetconf.com #puppetconf
Summary Pane

34. puppetconf.com #puppetconf
Node details

35. puppetconf.com #puppetconf
Event detail pane

36. puppetconf.com #puppetconf
What’s next.

37. puppetconf.com #puppetconf
Future improvements:
robust filtering

38. puppetconf.com #puppetconf
Future improvements:
comparing node events

39. puppetconf.com #puppetconf
Future improvements:
running puppet

40. puppetconf.com #puppetconf
Future improvements:
main screen redesign

41. puppetconf.com #puppetconf
Your questions.

42. Thank You
Joe Wagner
Senior User Experience Designer | Puppet Labs
@jcwag
Collaborate. Automate. Ship.