Franceschi: "Scenario 1: brand new project: easiest; most freedom of tech choices; brand new OS/stack; clean start, no tech debt, faster/smoother deployment times
Franceschi: "Scenario 2: Infrastructure migration: existing systems may not be centrally managed; migration of existing stacks to new systems
Franceschi: "Scenario 2: Infrastructure migration: downsides: existing systems may not be centrally managed; migration of existing stacks to new systems, all new systems should at least be fully managed
Define the standard baseline; create stacks/roles you need
Enlarge coverage of application stacks
Start from what is more used and needed
how easy/quickly can it be done?
how stable are systems?
what maintenance efforts are required?
number of systems?
what's benefit of automating?
what is the roadmap for the platform/app? (maintenance or high rate of change?
harder and more dangerous, because it's production
probably different OS to manage
undetermined existing setup procedure
manual configs accumulated over time
Evaluate agent setup on older systems
evaluate effort and benefits
evaluate the migration alternative
Franceschi: "Priorities: automate svr deploys; automate common system configs; automate most important stacks; run testing and app deploys, then automate; automate or delegate monitoring, integrate what already works well
Franceschi: "Config rollouts
notify users of the ongoing changes
have a test environment
test effects on any single different OS
propogate the configs
watch the logs and reports
don't be surprised of skeletons: review & patch uncovered configs
Franceschi: "Mindset chg for sysadmins; when infrastructure is code, it's versioned, tested, re-used; oh, u're a developer now
Up: "Benefits Of Using Kanban In IT Ops", Dragos Dumitriu, DJAA (@netheart)
.@netheart retelling amazing XIT story improving flow at MSFT in 2005 after they offshored IT work