container networking with weaveIlya Dmitrichenko @errordeveloper @weavenetwork

Linux containers = Docker• Docker is most talked about

• Mostly seen as platform enablement tool

• Can be looked at from various angles:

• Virtualisation for microservices

• Open-source or commercial PaaS

• Homegrown CI/CD

• All of which won’t work without a network

Many options, hard to pick…๏ There are many Docker-based projects:

• Kubernetes

• CoreOS

• Flocker

• Shipyard

• Fig

๏ And more Docker-related:

• Consul

• Confd

• Fleet

• Etcd

• Synapse

Why pick weave first?✓ Application-oriented overlay

networking for containers

✓ Create multiple networks on commodity infrastructure

✓ Dynamic and secure cross-cloud virtual Ethernet

✓ Leverage network-level isolation

✓ Integrate DNS-based service discovery

✓ All without code or infrastructure changes

➡ Very easy to use bit.ly/hello-weave

App in the cloud, in-house DB

bit.ly/weave-nginx-php-mysql

weaveblog.com

Cross-cloud DB

cass1: 10.2.1.1

cass2: 10.2.1.2

cass3: 10.2.1.3

AWS Azure Local

bit.ly/weave-cross-cloud-cass

weaveblog.com

Scale containerised service easier

• Scalaris is an HA in-memory K/V store

• Easy to scale on bare-metal, not at in containers

• bit.ly/weave-scalaris

host1: 10.2.1.1:8000

host2: 10.2.1.2:8000

host3: 10.2.1.3:8000

host5: 10.2.1.4:8000

host4: 10.2.1.4:8000

weave network

weaveblog.com

Weave enables PaaS: Kubernetes

• Fresh and shiny Docker-based app platform from Google

• Imposes specific network requirements

• Each Docker host needs a subnet

• bit.ly/weave-for-kubernetes

Thank you for your attention :)

Ilya Dmitrichenko @errordeveloper @weavenetwork