Infrastructure is Development

(1)

Red Hat Summit 2009 | Michael Stahnke 1

Infrastructure is Development

Michael Stahnke

(stahnma)

02-SEP-2009

(2)

Red Hat Summit 2009 | Michael Stahnke

2

The ideas presented today are not representative

of my employer, business success, past jobs and

do not offer endorsement to any particular

products brands or companies. Heck, a lot of this

stuff isn't even my idea to begin with.

http://www.flickr.com/photos/sea-turtle/3049443478/

(3)

Red Hat Summit 2009 | Michael Stahnke

3

“There are only two hard

problems in Computer Science:

cache invalidation and naming

things.”

(4)

Red Hat Summit 2009 | Michael Stahnke

4

(5)

Red Hat Summit 2009 | Michael Stahnke

5

(6)

6

(7)

7

(8)

8

Who Am I?

(9)

Where Am I?

http://stahnma.fedorapeople.org

http://www.stahnkage.com

@stahnma on Twitter

@stahnma on identi.ca

stahnma on github

[email protected]

(10)

Red Hat Summit 2009 | Michael Stahnke

10

Where Am I?

(11)

Red Hat Summit 2009 | Michael Stahnke

11

Baseline

Infrastructure – the collection of all components that make

up the non-external facing IT realm. Primarily, in this

case, servers connected to storage and network. It can

include network/SAN devices in some cases.

(12)

Red Hat Summit 2009 | Michael Stahnke

12

What's Coming Up

(13)

Red Hat Summit 2009 | Michael Stahnke

13

What's Coming Up

(14)

Red Hat Summit 2009 | Michael Stahnke

14

What's Coming Up

(15)

Red Hat Summit 2009 | Michael Stahnke

15

Three Domains

(16)

Red Hat Summit 2009 | Michael Stahnke

16

Three Domains

1. Infrastructure Practices

2. People

(17)

Three Domains

1. Infrastructure Practices

2. People

3. Technology Choices

(18)

Red Hat Summit 2009 | Michael Stahnke

18

(19)

19

(20)

20

(21)

21

(22)

22

(23)

23

(24)

24

(25)

25

(26)

Red Hat Summit 2009 | Michael Stahnke

26

Admins fight management

(27)

Red Hat Summit 2009 | Michael Stahnke

27

(28)

28

Are delivered

(29)

Red Hat Summit 2009 | Michael Stahnke

29

Through Ideas

(30)

Red Hat Summit 2009 | Michael Stahnke

30

Put together by Good People

(31)

Red Hat Summit 2009 | Michael Stahnke

31

Using some awesome technologies

(32)

Red Hat Summit 2009 | Michael Stahnke

32

Topic 1

(33)

Red Hat Summit 2009 | Michael Stahnke

33

(34)

34

Steal Ideas

(35)

Red Hat Summit 2009 | Michael Stahnke

35

(36)

36

Opening your infrastructure

includes your issues

(37)

Red Hat Summit 2009 | Michael Stahnke

37

Open your infrastructure

and your solutions

(38)

Red Hat Summit 2009 | Michael Stahnke

38

(39)

39

To Have a High Performing Team :

You

must

know

(40)

Red Hat Summit 2009 | Michael Stahnke

40

What do you have?

Asset Database

LDAP Directory

Hardware Management Tools

Power Management Tools

Monitoring Tools

Provisioning Tools

Storage Management Tools

Backup Tools

Policy Engines

Patch Tools

Security Scanning Tools

Virtualization Management Tools

Log Management Tools

(41)

Red Hat Summit 2009 | Michael Stahnke

41

Common Example:

Asset Database – Who knows?

LDAP Directory – RHDS, 389, SunOne, AD, OpenLDAP

Hardware Management Tools – IBM Director, DRAC

Power Management Tools – APC

Monitoring Tools – Nagios, Tivoli, OpenView

Provisioning Tools – Cobbler, Vmware,

Storage Management Tools – IBM Whatever, Some Custom Stuff

Backup Tools – Netbackup, Tivoli, Networker, Tar, Gzip, Rsync, Cron

Policy Engines – Cfengine, Puppet, Scripts

Patch Tools – RHN, NIM, Custom Repos

Security Scanning Tools – Lots of stuff

Virtualization Management Tools – vCenter, Virt-Manager, Spacewalk, RHN

Log Management Tools – Syslog Server

(42)

Red Hat Summit 2009 | Michael Stahnke

(43)

43

What now?

(44)

Red Hat Summit 2009 | Michael Stahnke

44

What now?

A. You can cry about it

(45)

Red Hat Summit 2009 | Michael Stahnke

45

What now?

B. You can remove data sources

C. You can integrate/federate them

(46)

Red Hat Summit 2009 | Michael Stahnke

46

What now?

D. All of the Above

(47)

Red Hat Summit 2009 | Michael Stahnke

47

What now?

D. All of the Above

The correct answers are both B and C; however it is very likely you

will encounter A, so the likely answer is, in fact, D.

(48)

Red Hat Summit 2009 | Michael Stahnke

48

Infrastructure is

Development

(49)

Red Hat Summit 2009 | Michael Stahnke

49

The

Infrastructure is the

Application

(50)

Red Hat Summit 2009 | Michael Stahnke

50

(51)

51

Infrastructure Goals

(52)

Red Hat Summit 2009 | Michael Stahnke

52

Infrastructure Goals

Deliver results to the business

(53)

Red Hat Summit 2009 | Michael Stahnke

53

Infrastructure Direction

(54)

Red Hat Summit 2009 | Michael Stahnke

54

Infrastructure Direction

Solving Problems

Automation

(55)

Red Hat Summit 2009 | Michael Stahnke

55

Infrastructure Direction

Solving Problems

Automation

(56)

Red Hat Summit 2009 | Michael Stahnke

56

Infrastructure Direction

Solving Problems

Automation

The right mix of people

(57)

Red Hat Summit 2009 | Michael Stahnke

57

Infrastructure Direction

Solving Problems

Automation

The right decision processes

Vision

(58)

Red Hat Summit 2009 | Michael Stahnke

58

Infrastructure Direction

Solving Problems

Automation

The right decision processes

Vision

(59)

Red Hat Summit 2009 | Michael Stahnke

59

(60)

60

Axiom 1

Reuse before building

or purchasing

(61)

Red Hat Summit 2009 | Michael Stahnke

61

(62)

62

(63)

63

(64)

64

Your Infrastructure isn't a secret

Everybody has servers, a network, some storage

Somebody has probably solved this problem

Check some common places:

Google

IRC

Sourceforge

Ohloh.net

Amazon book selection

(65)

Red Hat Summit 2009 | Michael Stahnke

65

So when I say re-use???

(66)

Red Hat Summit 2009 | Michael Stahnke

66

So when I say re-use???

(67)

Red Hat Summit 2009 | Michael Stahnke

67

So when I say re-use???

(68)

Red Hat Summit 2009 | Michael Stahnke

68

So when I say re-use???

Find other organizations successes on an open

infrastructure

(69)

Red Hat Summit 2009 | Michael Stahnke

69

You can't reuse?

(70)

Red Hat Summit 2009 | Michael Stahnke

70

You can't reuse?

(71)

Red Hat Summit 2009 | Michael Stahnke

71

You can't reuse?

(72)

Red Hat Summit 2009 | Michael Stahnke

72

You can't reuse?

Ok, you can look at building

or purchasing...

(73)

Red Hat Summit 2009 | Michael Stahnke

73

I have/need a purchased

(74)

Red Hat Summit 2009 | Michael Stahnke

74

I have/need a purchased

proprietary solution for Problem X

So do I, and I'm sorry.

(75)

Red Hat Summit 2009 | Michael Stahnke

75

(76)

76

Purchased Software Selection Criteria

(77)

Red Hat Summit 2009 | Michael Stahnke

77

Purchased Software Selection Criteria

There a few things to evaluate

Price

(78)

Red Hat Summit 2009 | Michael Stahnke

78

Purchased Software Selection Criteria

Price

(79)

Red Hat Summit 2009 | Michael Stahnke

79

Purchased Software Selection Criteria

Price

Performance

Functionality

(80)

Red Hat Summit 2009 | Michael Stahnke

80

Purchased Software Selection Criteria

Price

Performance

Functionality

But really....

(81)

Red Hat Summit 2009 | Michael Stahnke

81

(82)

82

(83)

83

Cloud Computing is all the rage

(84)

Red Hat Summit 2009 | Michael Stahnke

84

The GUI is for what some user interface designer thought

you wanted to do. The CLI is for what you actually need

to get done.

(85)

Red Hat Summit 2009 | Michael Stahnke

85

The GUI is for what some user interface designer thought

you wanted to do. The CLI is for what you actually need

to get done.

(86)

Red Hat Summit 2009 | Michael Stahnke

86

Axiom 2

Don't Leverage the

Meatcloud

(87)

Red Hat Summit 2009 | Michael Stahnke

87

(88)

88

(89)

89

Rules for Software Evaluation

Do not implement any product that does not provide an

API.

(90)

Red Hat Summit 2009 | Michael Stahnke

90

Rules for Software Evaluation

API.

The provided API must have all functionality that the

application provides.

(91)

Red Hat Summit 2009 | Michael Stahnke

91

Rules for Software Evaluation

API.

The provided API must be tailored to more than one

language and platform.

(92)

Red Hat Summit 2009 | Michael Stahnke

92

Rules for Software Evaluation

API.

Source code counts as an API, and may be restricted to

one language or platform.

(93)

Red Hat Summit 2009 | Michael Stahnke

93

Rules for Software Evaluation

API.

Source code counts as an API, and may be restricted to

one language or platform.

The API must include functional examples and not require

someone to be an expert on the product to use.

(94)

Red Hat Summit 2009 | Michael Stahnke

94

Rules for Software Evaluation

Do not use any product with configurations that are not

machine parseable and machine writable

(95)

Red Hat Summit 2009 | Michael Stahnke

95

Rules for Software Evaluation

All data stored in the product must be machine readable

and writable by applications other than the product itself.

(96)

Red Hat Summit 2009 | Michael Stahnke

96

Rules for Software Evaluation

All data stored in the product must be machine readable

and writable by applications other than the product itself.

Writing work-arounds to cover the deficiencies in a

product should be less work than writing the product’s

designed functionality.

(97)

Red Hat Summit 2009 | Michael Stahnke

97

(98)

98

(99)

99

(100)

(101)

101

What's the difference between development and

automation?

(102)

Red Hat Summit 2009 | Michael Stahnke

102

(103)

103

(104)

104

(105)

105

(106)

106

(107)

107

(108)

108

(109)

109

(110)

Red Hat Summit 2009 | Michael Stahnke

110

What's the difference between development and

automation?

(111)

Red Hat Summit 2009 | Michael Stahnke

111

Developers write code for use by somebody else

(112)

Red Hat Summit 2009 | Michael Stahnke

112

System Admins write code for use by themselves,

and hopefully somebody else

(113)

Red Hat Summit 2009 | Michael Stahnke

113

People make the

Infrastructure Agile

(114)

Red Hat Summit 2009 | Michael Stahnke

114

Attract Talent

(115)

Red Hat Summit 2009 | Michael Stahnke

115

Retain Talent

(116)

Red Hat Summit 2009 | Michael Stahnke

116

People

(117)

Red Hat Summit 2009 | Michael Stahnke

117

People

(118)

Red Hat Summit 2009 | Michael Stahnke

118

People

(119)

Red Hat Summit 2009 | Michael Stahnke

119

People

“...organizations which design systems ... are constrained

to produce designs which are copies of the

communication structures of these organizations.”

(120)

Red Hat Summit 2009 | Michael Stahnke

120

People

(121)

Red Hat Summit 2009 | Michael Stahnke

121

(122)

122

(123)

123

Some helpful hiring questions

(124)

Red Hat Summit 2009 | Michael Stahnke

124

Some helpful hiring questions

(125)

Red Hat Summit 2009 | Michael Stahnke

125

Some helpful hiring questions

(126)

Red Hat Summit 2009 | Michael Stahnke

126

Some helpful hiring questions

Do you know what version control is?

(127)

Red Hat Summit 2009 | Michael Stahnke

127

Some helpful hiring questions

(128)

Red Hat Summit 2009 | Michael Stahnke

128

Some helpful hiring questions

(129)

Red Hat Summit 2009 | Michael Stahnke

129

Some helpful hiring questions

(130)

Red Hat Summit 2009 | Michael Stahnke

130

Some helpful hiring questions

(131)

Red Hat Summit 2009 | Michael Stahnke

131

Some helpful hiring questions

(132)

Red Hat Summit 2009 | Michael Stahnke

132

Two Types of People

(133)

Red Hat Summit 2009 | Michael Stahnke

133

Breadth vs Depth

Breadth

(134)

Red Hat Summit 2009 | Michael Stahnke

134

Breadth vs Depth

Breadth

Systems Automation People.

Big Picture thinkers.

(135)

Red Hat Summit 2009 | Michael Stahnke

135

Breadth vs Depth

Breadth

(136)

Red Hat Summit 2009 | Michael Stahnke

136

Breadth vs Depth

Breadth

Visionaries.

Holistic View.

(137)

Red Hat Summit 2009 | Michael Stahnke

137

Breadth vs Depth

Depth

(138)

Red Hat Summit 2009 | Michael Stahnke

138

Breadth vs Depth

Depth

Solve the problem for this exact situation.

Tune like it's going out of style.

(139)

Red Hat Summit 2009 | Michael Stahnke

139

Breadth vs Depth

Depth

(140)

Red Hat Summit 2009 | Michael Stahnke

140

Breadth vs Depth

Depth

Maximum ROI.

(141)

Red Hat Summit 2009 | Michael Stahnke

141

Breadth vs Depth

(142)

Red Hat Summit 2009 | Michael Stahnke

142

People

(143)

Red Hat Summit 2009 | Michael Stahnke

143

People

(144)

Red Hat Summit 2009 | Michael Stahnke

144

How many people is

the right amount?

(145)

Red Hat Summit 2009 | Michael Stahnke

145

(146)

146

(147)

147

(148)

148

(149)

149

(150)

150

(151)

151

(152)

(153)

Red Hat Summit 2009 | Michael Stahnke

153

Axiom 2

Don't Leverage the

Meatcloud

(154)

Red Hat Summit 2009 | Michael Stahnke

154

(155)

155

(156)

156

(157)

157

Axiom 3

Decouple your

Infrastructure.

(158)

Red Hat Summit 2009 | Michael Stahnke

158

(159)

159

(160)

160

Moving Forward

Can you implement an Open

Strategy to solve this issue?

(161)

Red Hat Summit 2009 | Michael Stahnke

161

Moving Forward

If you have to solve it yourself, can it

be Open for others?

(162)

Red Hat Summit 2009 | Michael Stahnke

162

Moving Forward

(163)

Red Hat Summit 2009 | Michael Stahnke

163

Moving Forward

Driving on hexagonal wheels isn't fun

(164)

Red Hat Summit 2009 | Michael Stahnke

164

Moving Forward

http://www.flickr.com:80/photos/andrewmbutler/2762480367/

(165)

Red Hat Summit 2009 | Michael Stahnke

165

Moving Forward

Quit reinventing the wheel...poorly

(166)

Red Hat Summit 2009 | Michael Stahnke

166

Steal it all

Practical Examples of Open

Infrastructure

(167)

Red Hat Summit 2009 | Michael Stahnke

167

Steal it all

Practical Examples

The Fedora Infrastructure Project

(168)

Red Hat Summit 2009 | Michael Stahnke

168

Steal it all

Practical Examples

The Community Services Infrastructure

Standards

http://infrastructure.fedoraproject.org/csi/free-software-policy/en-US/html-single/

(169)

Red Hat Summit 2009 | Michael Stahnke

169

De-coupled Infrastructure Benefits

Commonly accepted

solutions to problem

(170)

Red Hat Summit 2009 | Michael Stahnke

170

De-coupled Infrastructure Benefits

Commonly accepted

Portability of solutions

(171)

Red Hat Summit 2009 | Michael Stahnke

171

De-coupled Infrastructure Benefits

Commonly accepted

Ability to hire

knowledgeable individuals

http://www.flickr.com:80/photos/thomas-merton/255204957

(172)

Red Hat Summit 2009 | Michael Stahnke

172

De-coupled Infrastructure Benefits

Commonly accepted

Ability to hire

Able to retain rock stars

(173)

Red Hat Summit 2009 | Michael Stahnke

173

De-coupled Infrastructure Benefits

Commonly accepted

Ability to hire

Able to retain rock stars

Community built around

tools and support

(174)

Red Hat Summit 2009 | Michael Stahnke

174

3 Axioms

1. Reuse before building or

purchasing

2. Don't leverage the meatcloud

3. Decouple your infrastructure

(175)

Red Hat Summit 2009 | Michael Stahnke

(176)

176

(177)

177

(178)

178

(179)

179

(180)

180

Your Time is Valuable

Identify tasks on which the team spends the most time.

Commonly

(Growth) Deployment

Account Management

Ad-Hoc File Transfer type activity

Patches

(181)

Red Hat Summit 2009 | Michael Stahnke

181

Time Evaluation

Evaluate your team's time spent on “

Displacement

Activities

”

Fund Raising

Parties/Showers

Volunteer Stuff

Charity

This is normally done because the person can't actually

meet the requirements of $DAYJOB

(182)

Red Hat Summit 2009 | Michael Stahnke

182

Pick a Task

Focus on one thing

Focus on one thing only

Seriously, this will help

(183)

Red Hat Summit 2009 | Michael Stahnke

183

(184)

184

(185)

185

Don't automate bad process.

(186)

Red Hat Summit 2009 | Michael Stahnke

186

(187)

187

(188)

188

(189)

(190)

190

(191)

191

Pick a Task

Let's start with system Deployment

You have some great options for tools

Do you need a tool?

(192)

Red Hat Summit 2009 | Michael Stahnke

192

Pick a Task

Let's start with system Deployment

You have some great options for tools

Do you need a tool?

Do you need it automated?

Do you need a pan-flute?

(193)

Red Hat Summit 2009 | Michael Stahnke

193

Process Evaluation

(194)

Red Hat Summit 2009 | Michael Stahnke

194

Process Evaluation

(195)

Red Hat Summit 2009 | Michael Stahnke

195

Process Evaluation

(196)

Red Hat Summit 2009 | Michael Stahnke

196

Process Evaluation

(197)

Red Hat Summit 2009 | Michael Stahnke

197

Process Evaluation

(198)

Red Hat Summit 2009 | Michael Stahnke

198

Process Evaluation

(199)

Red Hat Summit 2009 | Michael Stahnke

199

Gather Requirements

(200)

Red Hat Summit 2009 | Michael Stahnke

200

Gather Requirements

http://stahnma.fedorapeople.org

http://www.stahnkage.com