Azure Container Networking Solutions for Linux and Windows Containers
Перейти к файлу
Onur Filiz 8bfba82f6f Merge pull request #10 from Azure/development
Implemented IPAM plugin for multiCA integration
2016-05-10 17:58:42 -07:00
common Updated SendErrorResponse to receive error arg 2016-05-09 04:20:27 -07:00
core Moved common plugin functionality to base class 2016-04-27 17:53:05 -07:00
ipam Added null IPAM support 2016-05-10 17:47:51 -07:00
log Simplified and improved performance of log APIs 2016-05-02 19:26:13 -07:00
netfilter Support in Penguin for Multi CA enabled NICs. Logging to be fixed. 2016-03-07 21:17:08 -08:00
netlink Added netlink interface management APIs 2016-04-18 18:17:49 -07:00
network Simplified and improved performance of log APIs 2016-05-02 19:26:13 -07:00
.gitignore Fix the case for dependencies path 2016-03-21 15:40:21 -07:00
README.md Update README 2016-03-22 23:02:36 -07:00
main.go Added capability to pass cmd line options to plugins 2016-05-06 14:08:24 -07:00

README.md

Overview

Aqua sets up networking for containers running in Azure VMs. The current implementation does the following

  1. Implements the interface published by docker's libnetwork.

Usage

aqua [net] [ipam]

Examples

To start the remote network plugin for docker: aqua net
To start the remote ipam plugin for docker: aqua ipam

To create a docker network called "azure", use the following
docker network create --driver=aqua --ipam-driver=nullipam azure

Once the above network is created, you can have container join the above network as follows
docker run --net=azure -it ubuntu:latest /bin/bash

#Requirements Aqua currently relies on the fact that the interfaces in the VM are provisioned with multiple ip-addresses (called CAs in azure). In the current version of Aqua, multiple ip-addresses need to be manually configured on the interface. These ip-addresses need to be provisioned via Azure ARM APIs before they can be used inside VMs.

For help, send an email to