Docker at Flux7
Upcoming SlideShare
Loading in...5
×
 

Docker at Flux7

on

  • 5,167 views

This the talk I gave at Docker Docker Docker Austin Cloud Users meetup in Austin on January 21st, 2014. The talk was about the use of Docker at Flux7 Labs (flux7.com). I chose to deep dive into one of ...

This the talk I gave at Docker Docker Docker Austin Cloud Users meetup in Austin on January 21st, 2014. The talk was about the use of Docker at Flux7 Labs (flux7.com). I chose to deep dive into one of the most interesting Internet of Things use cases: Implement multi-tenancy on Solar Panel Monitoring Solution using Docker.

Statistics

Views

Total Views
5,167
Views on SlideShare
2,913
Embed Views
2,254

Actions

Likes
8
Downloads
23
Comments
0

7 Embeds 2,254

http://www.scoop.it 2164
http://plus.url.google.com 41
https://twitter.com 35
http://www.linkedin.com 10
http://flux7.com 2
https://www.linkedin.com 1
http://webcache.googleusercontent.com 1
More...

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Docker at Flux7 Docker at Flux7 Presentation Transcript

  • DOCKER @ FLUX7 LABS
  • DOCKER AUSTIN FOR MORE DISCUSSIONS ON DOCKER!
  • Who am I? ● Aater Suleman ○ Part-time UT Professor ○ Geek, Architect, Developer, Ops, DevOps … ● Co-founder & CEO Flux7 Labs ○ DevOps Solutions ■ Deployments ■ Cost/performance optimized large scale website (Ruby on rails, node.js, Django) and Hadoop deployments
  • Four projects: VyScale Dev Flow Docker's impact on performance (whitepaper WIP) Multi-tenancy Live process migration using CRIU (criu.org)
  • Application: Single Service Provider Internet of Things -- Solar Panel Monitoring Receive Sensor Data XML Data over TCP Report Generation based on data Big Data Analytics Report sent to End User
  • Gateway3 sensors Gateway1 Gateway2 Location1 Location3 Location2 Provider Span A provider has Mifi routers installed at multiple Locations which collect data from sensors and sends it to a remote TCP server via the internet. Browser Uses the Flask app at port 80 Internet Flask App Port 80 TCP server Port 6000 Cassandra port 9160 Single Provider System
  • COMPONENTS 1. Cassandra for data persistence which we later use for generating reports for each gateway. 2. A Twisted TCP server listening at PORT 6000, for data ingestion from multiple gateways owned by the provider. 3. A Flask app serving at PORT 80 as the admin panel for setting customizations and viewing reports.
  • Customer 1 G Customer 2 … Customer N G G G Each customer can have multiple gateways commissioned to them. *G - Gateway Remote Twister TCP Server (Non–Blocking I/O) Web App Power consumption status on website and mails Mailer Cassandra NoSQL data store (High Volume High Velocity Write which scales Linearly across the cluster )
  • SINGLE PROVIDER LAUNCH For launching the single provider version, the following was done: 1. nohup python tcp_server.py & # For firing up the TCP server. 2. nohup python flask_app.py & # For firing up the admin panel Both these code bases houses hard-coded Cassandra KEYSPACE Success!
  • Application: Multiple Service Providers …
  • Provider 2 sends data to port 6002 and accesses flask app at port 8082 Provider 1 sends data to port 6001 and accesses flask app at port 8081 Internet TCP server containerruns at port 6000. Exposes port 6000 and published it to port 6001 for provider 1 Flask container-runs flask app at port 80. Exposes port 80 and published it to port 8081 for provider 1 TCP server container-runs at port 6000. Exposes port 6000 and published it to port 6002 for provider 2 Flask container-runs flask app at port 80. Exposes port 80 and published it to port 8082 for provider 2 Cassandra
  • KNEE-JERK APPROACH Sprinkle Tenant ID everywhere in the code and DB Time consuming Poor isolation Security Expensive Maintenance Rigidity
  • MULTIPLE HOST/VMS An alternate solution is to use Virtual Machine (VM) Hosts are expensive ($) VMs are expensive (high overhead)
  • AND THE SOLUTION
  • WHY DOCKER? Docker containers provide isolation that is Fast Inexpensive How: Isolated environments for running multiple instances of the app
  • PLAN Create a docker container for the new version of the app Setup environments/dependencies correctly Start a Cassandra container.
  • AUTOMATION An automation was the next foreseeable step, and for that we found Docker-py extremely useful. We used something like: # Yes. We love Python! def start_provider(provider_id, gateway_port, admin_port ): docker_client = docker.Client(base_url='unix://var/run/docker.sock', version='1.6', timeout=100) # start a docker container for consuming gateway data at gateway_port start_command = 'python software/remote_server.py ' + provider_id remote_server = docker_client.create_container('flux7/labs', # docker image command=start_command, # start command contains the keyspace parameter, keyspace is the provider_id name='remote_server_' + provider_id, # name the container, name is provider_id ports=[(6000, 'tcp'),]) # open port for binding, remote_server.py listens at 6000 docker_client.start(remote_server, port_bindings={6000: ('0.0.0.0', gateway_port)}, links={'db': 'cassandra'}) # start a docker container for serving admin panel at admin_port start_command = 'python software/flask_app.py ' + provider_id remote_server = docker_client.create_container('flux7/labs', # docker image command=start_command, # start command contains the keyspace parameter, keyspace is the provider_id name='admin_panel_' + provider_id, # name the container, name is provider_id ports=[(80, 'tcp'),]) # open port for binding, remote_server.py listens at 6000 docker_client.start(remote_server, port_bindings={80: ('0.0.0.0',admin_port)}, links= {'db': 'cassandra'})
  • OUR SOLUTION- EXPLAINED For now, a locally running container serving at PORT 9160 using the command similar to this: docker run -d -p 9160:9160 -name db flux7/cassandra
  • OUR SOLUTION- EXPLAINED ▪ Create a keyspace ‘provider1’ using pycassaShell. We fired up our two code bases on two separate containers like this: docker run -name remote_server_1 -link db:cassandra p 6000:6000 flux7/labs python software/remote_server. py provider1 docker run -name flask_app_1 -link db:cassandra -p 6000:6000 flux7/labs python software/flask_app.py provider1
  • DOCKER ISSUES DISCOVERED Docker does not support multiple instances of Cassandra running on the same machine. Hosting multiple database instances on a single machine can quickly cause resource shortages
  • OUR SOLUTION ❑ Followed the traditional solution to make an application multi-tenant Use of KEYSPACE as the namespace for each provider in the data store Code Changes Cassandra KEYSPACE / provider ID •• To data ingestion server and web server by adding the keyspace parameter to the DB accesses. •• Passed to each instance of the app on the command line. ❑ Each provider in the data store gets a separate namespace without making any changes to the column family schema.
  • LESSONS WE LEARNED 1. Docker is an extremely fast and elegant isolation framework: easy to port, cheap to run, easy to orchestrate 2. Multi-tenancy != changing the app to support multiple tenants 3. Docker orchestration frameworks are not at par with Docker today. What we have written is yet another one but for multi-tenancy. 4. Dockerfiles still need work -- we used shell scripts in some places 5. We can run multiple commands/container
  • DOCKER AUSTIN FOR MORE DISCUSSIONS ON DOCKER!