This session will focus on the practicals of building a fully-functional stack of container cluster tools, with different options for stacking those tools from the OS-up.
We’ve all seen examples of common technologies stacks, like the good ol’ LAMP and MEAN stacks for apps, but what about lower-level infrastructure? And can we get it without cloud vendor lock in please? Oh and pure containers and infrastructure-as-code too?
With Docker, sure thing! This session will cover:
Which OS/Distro and Kernel to use
VM’s or Bare Metal
Recommended Swarm architectures
Tool stacks for “pure open source”, “cloud-service based”, and “Docker EE” scenarios
Demos of these tools working together including InfraKit, Docker, Swarm, Flow-Proxy, ELK, Prometheus, REX-Ray, and more.
No Advance 8868886958 Chandigarh Call Girls , Indian Call Girls For Full Nigh...
Building your production tech stack for docker container platform
1. BRET FISHER
Docker Captain, DevOps Dude,
Author of Docker Mastery
Building Your Docker Tech Stack
bretfisher.com/dockercon18
@bretfisher
2. People ask "Where's my LAMP for container clusters?"
Your solutions will be a "stack" of infrastructure tools
Cloud-native container tools are new
We need patterns and examples of full cluster stacks
Problem: No Server Tool Lives In Isolation
3. Build examples of full-er/ish stacks on different tools
Options for solo to medium-sized DevOps/Ops teams
Use Docker Swarm latest stable as orchestrator
Avoid cloud vendor lock-in*
4 Goals for Today
* Lock-in: A service I can't swap out in my server stack
4. Limit "going production Docker" project scope. Go Lean!
Focus first on quality Dockerfiles
Stay on your familiar host OS with 4.x Kernel
Use base images of familiar OS (keep same pkg mgr)
Swarm CE can be 1 or more nodes, use it everywhere
Swarm EE is your "easy button" for security and ops
Last Time On Bret's DockerCon Talk
5. Two Stacks, Same Core
Docker CE Swarm
Used for Dev/Test
Heavy use of OSS/free
Gluttony of choice for 3rd party
Newest engine features
Docker EE Swarm
Used for Staging/Prod
Heavy use of paid support
Use Docker Solution Briefs
Mature engine with hotfixes
++
14. Cloud agnostic, minimal infra
Apps auto-recover on node fail
Incoming TLS
Centralized logging
Centralized monitoring
Healthcheck all containers
Infra Requirements of dogvs.cat
Performance auto-scaling
Self-healing nodes
Support serverless functions
Services highly available
Han Solo Requirements Optional Requirements for Later
15. Simple Infrastructure, Easy Deployment
"How can I deploy a multi-tier app
on a few servers, with all the bells
and whistles of orchestration with
load balancing and auto recovery?"
Han Solo,
The Sysadmin
16. 3+ Droplets (Ubuntu 16.04)
Block Storage (Volumes)
Load Balancer (incoming HTTP)
Digital Ocean dogvs.cat
Services Needed for High Availability
28. Deploy Stacks: Maintenance Tasks
docker stack deploy -c stack-prune.yml prune
backups (in stack file with app)
29. Day Two Operations: Updates
stack deploy ∞
micromanage update_config and healthcheck
tune your limits and reservations
30. Security?
host setup scanning: Docker Bench
image scanning: Aqua Microscanner
behavior monitoring: Sysdig Falco
user namespaces
31. Next Steps
more nodes? make 'em workers
CI/CD stacks: gitlab, jenkins
make redis, mysql, psql HA
add app metrics to Prometheus
swap Overlay for Weave Net
swap ELK for Papertrail, etc.
swap Prometheus for Sysdig,
Datadog, Librato, etc.
add socat proxy to Traefik
33. Complex Infrastructure, Harder Deployment
"How can I deploy many multi-tier
app on a many servers, with all the
b e l l s a n d w h i s t l e s o f H A
orchestration, have load balancing
at all levels, with failover and
auto recovery?"
Amazonian
Team
44. Next Steps
All the things in Swarm CE
monitoring via CloudWatch and
Telegraph
logging via CloudWatch Logs
45. Summary
Infrastructure as code, make everything repeatable
No "special" nodes, use remote management
Grow as you go, assume you'll resize
Look for compose files of popular tools to make stacks
Don't throw out the good in search of the perfect