designed for networkingcalico what why how and the

  • Slides: 16
Download presentation
designed for networking-calico – what, why, how, and the future Neil Jerram, Project Calico

designed for networking-calico – what, why, how, and the future Neil Jerram, Project Calico / Metaswitch Sponsored by

networking-calico

networking-calico

Calico’s premise: IP-only connectivity VM VM IP connectivity L 2 multicast VM VM L

Calico’s premise: IP-only connectivity VM VM IP connectivity L 2 multicast VM VM L 2 broadcast VM

Routed networks § https: //review. openstack. org/#/c/225384/ Network object … l 2_adjacency True |

Routed networks § https: //review. openstack. org/#/c/225384/ Network object … l 2_adjacency True | False …

The Calico data path Source compute host 172. 18. 203. 31 Destination compute host

The Calico data path Source compute host 172. 18. 203. 31 Destination compute host 172. 18. 203. 44 10. 65. 0. 3/32 via 172. 18. 203. 44 dev eth 0 10. 65. 0. 3/32 dev tap 12345 -ab tap 84637 -ef eth 0 Source VM 10. 65. 0. 2 10. 65. 0. 0/24 dev eth 0 tap 12345 -ab eth 0 Destination VM 10. 65. 0. 3

The Calico data path Source compute host 172. 18. 203. 31 Destination compute host

The Calico data path Source compute host 172. 18. 203. 31 Destination compute host 172. 18. 203. 44 10. 65. 0. 3/32 via 172. 18. 203. 44 dev eth 0 10. 65. 0. 3/32 dev tap 12345 -ab tap 84637 -ef DHCP eth 0 Source VM 10. 65. 0. 2 10. 65. 0. 0/24 dev eth 0 tap 12345 -ab eth 0 Destination VM 10. 65. 0. 3

The Calico data path Source compute host 172. 18. 203. 31 Destination compute host

The Calico data path Source compute host 172. 18. 203. 31 Destination compute host 172. 18. 203. 44 10. 65. 0. 3/32 via 172. 18. 203. 44 dev eth 0 10. 65. 0. 3/32 dev tap 12345 -ab tap 84637 -ef DHCP eth 0 Source VM 10. 65. 0. 2 10. 65. 0. 0/24 dev eth 0 Felix tap 12345 -ab eth 0 Destination VM 10. 65. 0. 3

The Calico data path Source compute host 172. 18. 203. 31 Destination compute host

The Calico data path Source compute host 172. 18. 203. 31 Destination compute host 172. 18. 203. 44 10. 65. 0. 3/32 via 172. 18. 203. 44 dev eth 0 10. 65. 0. 3/32 dev tap 12345 -ab BIRD tap 84637 -ef DHCP eth 0 Source VM 10. 65. 0. 2 10. 65. 0. 0/24 dev eth 0 Felix tap 12345 -ab eth 0 Destination VM 10. 65. 0. 3

Use case, provisioning and isolation § Intended for provider networks § All Calico networks

Use case, provisioning and isolation § Intended for provider networks § All Calico networks share same address space (or ‘scope’) § Currently no overlapping IPs § We have a design if needed § Isolation using security groups, not between networks

Public and private IP addressing

Public and private IP addressing

Making DHCP work tap 1… VM tap 2… DHCP interface ns-dhcp VM --bridge-interface=ns-dhcp, tap*

Making DHCP work tap 1… VM tap 2… DHCP interface ns-dhcp VM --bridge-interface=ns-dhcp, tap* --listen tap* --bind-dynamic tap 3… VM tap 4… 10. 65. 0. 1/24 VM tap 5… VM

Releases § Icehouse, Juno, Kilo § https: //github. com/projectcalico/calico-nova § https: //github. com/projectcalico/calico-neutron §

Releases § Icehouse, Juno, Kilo § https: //github. com/projectcalico/calico-nova § https: //github. com/projectcalico/calico-neutron § Liberty, Mitaka, … § Everything upstream, vanilla Open. Stack § Explicit IP-only semantics provided by routed network spec

Recent developments § Floating IPs – Nick Bartos Felix 1: 1 DNAT External network

Recent developments § Floating IPs – Nick Bartos Felix 1: 1 DNAT External network Tenant network Router Floating IP pool Fixed IPs § Calico DHCP agent Neutron RPC Neutron server Calico ML 2 driver Neutron DHCP agent etcd database Calico DHCP agent

Deployment and integrations § Dev. Stack plugin § Packaged for Ubuntu Trusty, Xenial; and

Deployment and integrations § Dev. Stack plugin § Packaged for Ubuntu Trusty, Xenial; and RHEL 7 § Juju charms § Calico plugin for Fuel 6 and 7; 8 and 9 coming soon § Kuryr § Ansible § Salt § ….

What next? § IRC meeting § IPAM work for route aggregation § ?

What next? § IRC meeting § IPAM work for route aggregation § ?

Summary and thank you! simple scalable secure just IP + Linux – no SDN

Summary and thank you! simple scalable secure just IP + Linux – no SDN controller hundreds of hosts thousands of VMs millions of containers fine-grained workload policy