Service routing with Consul & HAProxy

From Stockholm HashiCorp User Group meetup #1, Sept 8, 2016.

Transcript

1. Service  routing  with   Consul  &  HAProxy magnus.bengtsson@expressen.se
2. stats ~  300  deploys  /  week   ~  800  new  containers  /  week   ~  2k  req’s  /  sec  on  haproxy  
3. problem accessing  our  services?
4. problem  Availability?
5. need  Standardized  access   layer
6. summary  tools  used      how  we  access  services    takeaways
7. tools? not  batteries  included  but  removable,   but  rather  just  the  bag  of  batteries   for  us  to  play  with!
8. tao  Simple,  Modular,  Composable
 ’the  tao  of  HashiCorp’
9. tools Consul
10. Consul… service  catalog   [tags].name
11. Consul… DNS  interface:   tag.name.service.consul
12. Consul… HTTP  api:   $  curl  localhost:8500/v1/catalog/services   {      "consul":  [],      "redis":  [],      "postgresql":  [          "master",          "slave"      ]   }
13. Consul… distributed  K/V
14. Consul… health  checks
15. tools Helios
16. tools Helios  -­‐>  Nomad
17. tools registrator   https://github.com/gliderlabs/registrator
18. Registrator… registers(!)
19. Registrator… docker.sock
20. tools consul-­‐template
21. consul-­‐template… populate  data  in  files
22. consul-­‐template… Go  templating
23. consul-­‐template… re-­‐render  on  changes
24. consul-­‐template… ..in  service  catalog
25. consul-­‐template… ..in  k/v
26. consul-­‐template… ..and  do  action
27. tools HAProxy
28. HAProxy… L4-­‐L7  TCP  Proxy
29. HAProxy… small,  fast,  simple  but   powerful
30. about  service   discovery… a  few  ways  to  do  it
31. service  discovery   with  consul Service A api:20012
32. service  discovery   with  consul 1.api? Service A api:20012
33. service  discovery   with  consul 1.api? 2. api=10.50.0.10:20012 Service A api:20012
34. service  discovery   with  consul 1.api? 2. api=10.50.0.10:20012 Service A api:20012 3.api!
35. service  routing   with  HAProxy Service api api
36. service  routing   with  HAProxy Service api for each service… api
37. service  routing   with  HAProxy api:
 10.50.0.10:20012
 Service api for each service… api
38. service  routing   with  HAProxy api:
 10.50.0.10:20012
 Service production.api api for each service… api
39. service  routing   with  HAProxy api:
 10.50.0.10:20012
 Service production.api api for each service… api
40. www.expressen.se Bigip HAProxy Scheduler
 Agent Docker Consul-
 template registrator HAProxy Scheduler
 Agent Docker Consul-
 template registrator
41. templating Let’s  create  a   dashboard!
42. templating … <h1>Dashboard for: {{datacenters | join " "}}</h1> {{range services}} {{range service .Name "any"}} <p> Name: {{.Name}} Tags: {{range .Tags}}{{.}}{{end}} Status: {{if ne .Status "passing"}}<span style="background- color:red">{{.Status}} state!</span>{{end}} {{if eq .Status "passing"}}<span style="background- color:green;">Ok</span>{{end}} </p> {{end}} {{end}} …
43. HAProxy  basics frontends
44. HAProxy  basics backends
45. HAProxy  routing name-­‐based   Host:production.api.service.consul
46. HAProxy  routing port   frontend api-in bind 0.0.0.0:1234
47. feeding  HAProxy frontends  (in)   frontend http-in bind 0.0.0.0:80 mode http {{range $key, $pairs := tree "env/prod/haproxy/sites/" | explode }} {{ if $pairs }}{{ if $pairs.backends }} acl {{$key}}-host hdr_beg(host) -i {{$pairs.backends}}. use_backend {{$key}}-servers if {{$key}}-host {{end}}{{end}} {{end}}
48. feeding  HAProxy frontends  (in)   frontend http-in bind 0.0.0.0:80 mode http acl api-host hdr_beg(host) -i production.api. use_backend api-servers if api-host
49. feeding  HAProxy backends  (server)   {{range $key, $pairs := tree "env/prod/haproxy/sites" | explode }} {{ if $pairs }} backend {{$key}}-servers {{ if eq (or $pairs.mode "http") "http" }} option httpchk {{or $pairs.httpchk "GET /healthz"}} {{ end }} http-response set-header X-App {{$key}} # servers{{$backends := or $pairs.backends "localhost"}} {{range service $backends}} server {{.Node}}_{{.Port}} {{.Address}}: {{.Port}} check {{end}} {{end}} {{end}}
50. feeding  HAProxy backends  (server)   backend api-servers option httpchk GET /healthz balance roundrobin http-response set-header X-App api # servers server app141_20081 10.0.0.141:20081 check server app159_20106 10.0.0.159:20106 check
51. takeaways easy  to  start  using  a  dynamic  env.
52. takeaways use  the  k/v  store  in  consul  for   control.
53. takeaways It’s  fast.
54. takeaways It’s  fun.
55. takeaways It’s  modular.
56. takeaways keeps  us  in  control.
57. takeaways correlations.
58. takeaways uptime.
59. takeaways    Simple,  Modular  &                         Composable
60. takeaways    Simple,  Modular  &                        
61. takeaways    Simple,  Modular  &                         Combustible
62. thank  you! questions?