Devoxx 2016 talk: Going Global with Nomad and Google Cloud Platform
- 1. @YourTwitterHandle#DV14 #YourTag @NakedN3rd#Devoxx #GoingGlobal Going Global with Nomad and Google Cloud Platform Bastiaan Bakker
- 2. @NakedN3rd#Devoxx #GoingGlobal Gobal, why bother?
- 3. @NakedN3rd#Devoxx #GoingGlobal Latency costs Roundtrip from Asia to Europe adds 500ms latency to every request. In a Google experiment in 2006, increasing page load time from 0.4s to 0.9s resulted in 20% lower traffic and revenue.
- 4. @NakedN3rd#Devoxx #GoingGlobal Failures ● Process ● Server ● Availability Zone ● Region ● LAN ● WAN ● DNS
- 5. @NakedN3rd#Devoxx #GoingGlobal Our toolchest for today
- 6. @NakedN3rd#Devoxx #GoingGlobal Google Cloud Platform ● Fast: create aVM in 30 seconds. ● Clear concepts ● Easy networking ● Global load balancer
- 7. @NakedN3rd#Devoxx #GoingGlobal Nomad ● Cluster manager ● Scheduler ● Task executor ● Service registrator ● Highly scalable & available ● Docker & non-Docker workloads ● Simple & small ● Multi-Region
- 9. @NakedN3rd#Devoxx #GoingGlobal Nomad single region setup
- 10. @NakedN3rd#Devoxx #GoingGlobal Creating the Cluster ● Setting up a Nomad server cluster ● Setting up a Nomad client cluster ● Running the first job, nomad-ui.
- 12. @NakedN3rd#Devoxx #GoingGlobal Helloworld ● A simple demo webapp. ● Written in Go, no OS dependencies. ● 12 factor. ● /hello Says hello and counts how many times. ● /health endpoint returns health ● /fs/... serves filesytem https://github.com/bastiaanb/helloworld
- 13. @NakedN3rd#Devoxx #GoingGlobal Consul ● Service Registry ● Distributed Health Monitoring ● Highly Available ● KV store ● Multi datacenter ● Simple & small
- 16. @NakedN3rd#Devoxx #GoingGlobal Nomad Datacenters “Nomad models infrastructure as regions and datacenters. Regions may contain multiple datacenters. Servers are assigned to regions and manage all state for the region and make scheduling decisions within that region. Requests that are made between regions are forwarded to the appropriate servers.As an example, you may have a US region with the useast1 and uswest1 datacenters, connected to the EU region with the eufr1 and euuk1 datacenters.”
- 17. @NakedN3rd#Devoxx #GoingGlobal Consul Datacenters “we define a datacenter to be a networking environment that is private, low latency, and high bandwidth.This excludes communication that would traverse the public internet, but for our purposes multiple availability zones within a single EC2 region would be considered part of a single datacenter.”
- 19. @NakedN3rd#Devoxx #GoingGlobal Configuration Templating In your Nomad job: template { data = "{{range service "helloworld" }}{{.Address}}:{{.Port}}n{{end}}" destination = "peers.txt" change_mode = "noop" }
- 20. @NakedN3rd#Devoxx #GoingGlobal Consul Prepared Queries { "Name": "", "Template": { "Type": "name_prefix_match" }, "Service": { "Service": "${name.full}", "Failover": { "NearestN": 3 } } }
- 21. @NakedN3rd#Devoxx #GoingGlobal Links ● https://www.nomadproject.io/ ● https://github.com/iverberk/nomad-ui ● https://www.consul.io/ ● https://github.com/eBay/fabio ● https://github.com/bastiaanb/devoxx-2016 https://github.com/bastiaanb/helloworld ● https://cloud.google.com/compute/docs/load-balancing/http/cross-region-exam ● contact: bbakker@xebia.com
Editor's Notes
- #3: Our goal: Creating a global datacenter that is highly available, super scalable and responsive. With ‘highly available’ we mean: can widthstand loss / failure of single processes, but also compute nodes, complete availability zones or even regions. With ‘super scalable’ we mean that we can scale up capacity multiple orders of magnitude without having to change the architecture. With ‘responsive’ we mean that we want requests to be served by a server that is ‘near’ the client. Ergo US users get serviced by a US datacenter, European users by a European one.
- #10: Click to add Notes