Azure Container Networking Solutions for Linux and Windows Containers
Перейти к файлу
Onur Filiz c8400962ba Updated plugins to use path constants 2016-05-01 17:55:21 -07:00
common Updated plugins to use path constants 2016-05-01 17:55:21 -07:00
core Moved common plugin functionality to base class 2016-04-27 17:53:05 -07:00
ipam Updated plugins to use path constants 2016-05-01 17:55:21 -07:00
log
netfilter
netlink Added netlink interface management APIs 2016-04-18 18:17:49 -07:00
network Updated plugins to use path constants 2016-05-01 17:55:21 -07:00
.gitignore
README.md
main.go

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