Design Patterns in Configuration Management - Part 1

This is the first presentation in a series of talks describing architecture patterns for infrastructure and the underlying code patterns necessary to support these patterns.

This deck describes the following patterns:

* Modularity
* Managing Complex States
* Convention over Configuration
* Proxy/Factory Patterns in Puppet

This presentation is an accompanying deck to the presentation "Data Driven Infrastructure" which can be found at https://speakerdeck.com/jfryman/building-data-driven-infrastructure-with-puppet

A full video of this talk can be found at https://www.youtube.com/watch?v=e4lAzjCKk24

Transcript

1. Design Patterns Configuration Management
2. broader strokes
6. angry page
9. Why not?
10. Step Back
12. Data Driven Infrastructure
13. There is System One
14. Modularity
15. Self Authoritative
16. Must self-correct
17. Utopia
18. James Fryman
20. • Code Examples • Background http://git.io/in341A
21. Language
22. Activity-on-Node
23. State Machine
24. Provisioning Maintenance Process Ready for Master Sync Slave Ready Tombstone Backup Lifecycle
25. Self-Correct Not Serving Log Remove from LB Cycle Service Escalate Assets Missing Ready Validate FS Configuration Success
27. Proxy Pattern
28. define  statemachine::set(      $ensure    =  present,      $base        =  $name,      $state      =  undef,      $backend  =  $statemachine::config::backend,   )  {      if  $state  {          ensure_resource($backend,  $name,  {              "ensure"  =>  $ensure,              "base"      =>  $base,              "state"    =>  $state,          })      }  else  {          statemachine::log  {  "Unable  to  set  state  for  $ {base}.  Missing  state.  Skipping...":  }      }   }
29. class  statemachine::config  (      $logger      =  'statemachine::logger::console',      $backend    =  'statemachine::backend::local',   )  {      validate_string($logger,  $backend)   !    File  {          ensure  =>  file,          owner    =>  'root',          group    =>  'root',          mode      =>  '0755',      }   !    file  {  '/etc/statemachine':          ensure  =>  directory,      }      file  {  '/etc/facter/facts.d/statemachine':          source  =>  'puppet:///modules/statemachine/etc/facter/facts.d/statemachine',      }      file  {  '/usr/local/bin/statemachine':          source  =>  'puppet:///modules/statemachine/usr/local/bin/statemachine',      }   }
30. define  statemachine::backend::local(      $ensure  =  present,      $base      =  $name,      $state    =  undef,   )  {      include  statemachine::backend::local::config      $settings  =  $statemachine::backend::local::config::settings      validate_hash($settings)   !    validate_re($ensure,  '^(absent|present)$')      validate_string($base,  $state)   !    $state_file  =  regsubst($base,  '::',  '_',  'G')   !    file  {  "${settings['base_dir']}/${state_file}":          ensure    =>  $ensure,          owner      =>  'root',          group      =>  'root',          mode        =>  '0644',          content  =>  "${state}\n",      }   }
31. statemachine  {  'frymanet::base':      states  =>  [          'provisioning',          'config',          'ready',      ],   } Declare
32. State Machine
33. State Machine Automatically via Facts Set via ChatOps In response to global state
34. Proxy Pattern
35. Proxy Pattern statemachine::set statemachine::backend statemachine::backend::local
36. statemachine::set statemachine::backend statemachine::backend::local database::new database::backend postgres::adapter::new Factory Pattern
37. No Assembly Required
38. No Assembly Required
39. Problem 1: Unable to wire in a node to provide service. Too Many Choices
40. Self Authoritative
41. Ladder - Convention over Configuration
42. -­‐-­‐-­‐   :base:  frymanet::base   :hierarchy:      -­‐  platform/%{::virtual}      -­‐  platform/%{::productname}      -­‐  platform/%{::operatingsystem}      -­‐  platform/%{::operatingsystem}/%{::lsbdistcodename}      -­‐  platform/%{::cloud}      -­‐  platform/%{::datacenter}      -­‐  platform/%{::datacenter}/%{::operatingsystem} Stacks
43. require  'yaml'   ! module  Puppet::Parser::Functions      newfunction(:find_ladder_rungs,  :type  =>  :rvalue,                              :doc  =>  'Find  all  manifests  eligible  for  import  based  on  a  ladder  stack')   do  |args|          load_stack      =  args[0]          stack_config  =  "#{lookupvar('ladder::config::conf_dir')}/#{load_stack}.yaml"          module_path    =  File.expand_path('..',  Puppet::Module.find('ladder',   compiler.environment.to_s).path)          manifests        =  []   !        #  Recursively  render  the  rung  and  populate  with  real  values          def  expand_rung(rung)              rung.sub!(/%{(.*)}/)  {  |match|  lookupvar(match.first)  }              rung.match(/%{(.*)}/)  ?  expand_rung(rung)  :  rung.gsub(/\//,  '::')          end   !        if  File.exists?  stack_config              stack  =  YAML.load_file  "#{module_path}/#{stack_config}"   !            stack[:hierarchy].each  do  |rung|                  rung_lookup  =  "#{stack[:base]}::#{expand_rung(rung)}"   !                if  Puppet::Module.find(rung_lookup,  compiler.environment.to_s)                      manifests  <<  rung_lookup                  end              end          end   !
44. include  ladders
45. Fail Open
46. Language
48. Service Discovery
49. Intra-Node Communication
50. Control Rods
51. Resources
52. @jfryman fryman@github.com
53. Dziękuję za uwagę