Jump to: navigation, search

Difference between revisions of "Kuryr"

(OpenStack Containers Networking ("Kuryr"))
(OpenStack Containers Networking ("Kuryr"))
Line 35: Line 35:
 
* [https://www.openstack.org/summit/tokyo-2015/videos/presentation/kuryr-docker-networking-in-an-openstack-world Kuryr - Tokyo Summit]   
 
* [https://www.openstack.org/summit/tokyo-2015/videos/presentation/kuryr-docker-networking-in-an-openstack-world Kuryr - Tokyo Summit]   
  
 +
== Kuryr Policies==
 +
TBD
  
 
== Related projects ==
 
== Related projects ==

Revision as of 11:21, 9 March 2017

OpenStack Containers Networking ("Kuryr")

Developer Doc
Source code
Bug tracker
Blueprints
Backlog

Kuryr Mission Statement

Bridge between containers frameworks networking models to OpenStack networking abstraction

What is Kuryr?

OpenStack and Neutron are no longer the new kid in the block, Neutron has matured and its popularity in OpenStack deployments over nova-network is increasing, it has a very rich ecosystem of plugins and drivers which provide networking solutions and services (like LBaaS, VPNaaS and FWaaS). All of which implement the Neutron abstraction and hopefully can be interchange by the cloud deployers.

What we noticed in regards to containers networking, and specifically in environments that are mixed for containers and OpenStack is that every networking solution tries to reinvent and enable networking for containers but this time with Docker API (or any other abstraction) OpenStack Magnum, for example, has to introduce an abstraction layer for different libnetwork drivers depending on the Container Orchestration Engine used. It would be ideal if Kuryr could be the default for Magnum COEs

The idea behind Kuryr, is to be able to leverage the abstraction and all the hard work that was put in Neutron and its plugins and services and use that to provide production grade networking for containers use cases. Instead of each independent Neutron plugin or solution trying to find and close the gaps, we can concentrate the efforts and focus in one spot - Kuryr.

Kuryr aims to be the “integration bridge” between the two communities, Docker and Neutron and propose and drive changes needed in Neutron (or in Docker) to be able to fulfill the use cases needed specifically to containers networking.

It is important to note that Kuryr is NOT a networking solution by itself nor does it attempt to become one. The Kuryr effort is focused to be the courier that delivers Neutron networking and services to Docker.

More Info:

Kuryr Policies

TBD

Related projects

  • Neutron

Neutron is an OpenStack project to provide "networking as a service" . Kuryr leverage Neutron abstraction in order to create virtual networks for containers and containers orchestration engines.

  • Magnum

Magnum is an OpenStack project to deploy contains, both at Virtual Machine or Physics Machine. Kuryr will work together with magnum and bind Neutron ports to containers that deployed by magnum.

  • Kolla
  • Astara
  • Docker / Docker Swarm
  • Kubernetes
  • Mesos