Provide Support for Magnum

To meet requirements of the Magnum Project [1], Kuryr must provide the following:

1. Provide networking capabilities to containers running in Nova instances.

2. Magnum uses Heat to orchestrate multi-tenant application container environments. Therefore, Kuryr must have the ability to be deployed/orchestrated using Heat.

3. Current Magnum container networking implementations such as Flannel, provide networking connectivity to containers that reside across multiple Nova instances. Kuryr must provide multi-instance container networking capabilities.

4. Kuryr must provide a simple user experience that follows the Docker "batteries included but replaceable" philosophy. Magnum must have the ability to deploy Kuryr without any user intervention, but allow more advanced users to modify Kuryr's default settings in a simple manner.

5. If Kuryr must deploy software (ie agent) inside Magnum's Nova images, this must be accomplished in a secure manner.

6. Communication among Kuryr components must be secure.

7. Magnum services (Docker, Kubernetes, etc..) must work the same or better than they do with existing network providers such as Flannel.

8. Kuryr must scale just as well, if not better, than existing container networking providers.

This blueprint is based off the brainstorming etherpad [2] from both teams.

[1] https://launchpad.net/magnum
[2] https://etherpad.openstack.org/p/magnum-kuryr