scalable configuration management (2)

partially responsible for current situation
trusting vendor defaults too much
putting up with vendor kitsch
no trusted routing registry
egregious lack of instrumentation
moderate lack of clue
business constraints retrohacked into a system not designed for it 
garbage can theory!
inherent interactive complexity of global distributed system 
interdomain (BGP) routing system configuration gets its own slides later
what can be done
researchers: "higher level policy languages" 
abstraction abstraction abstraction
sysadmins: help define scope of your configuration needs 
am not claiming we can definitely get there with incremental steps
only that we don't have an alternative at the moment