ITQC/containernetworking-plugins
24
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 34 Wiki Activity

spec: fix fmt issues and example JSON

Browse Source
This commit is contained in:
Eugene Yakubovich 2015-07-06 17:00:57 -07:00
parent f56f1d90fd
commit edf08b56d2
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
SPEC.md
View File

@ -72,7 +72,7 @@ Network configuration in JSON format is streamed through stdin.
Success is indicated by a return code of zero and the following JSON printed to stdout in the case of the ADD command. This should be the same output as was returned by the IPAM plugin (see [IP Allocation](#ip-allocation) for details).
```json
```
{
"ip4": {
"ip": <ipv4-and-subnet-in-CIDR>,
@ -88,7 +88,7 @@ Success is indicated by a return code of zero and the following JSON printed to
```
Errors are indicated by a non-zero return code and the following JSON being printed to stdout:
```json
```
{
"code": <numeric-error-code>,
"msg": <short-error-message>,
@ -137,10 +137,10 @@ The network configuration is described in JSON form. The configuration can be st
"type": "ovs",
// type (plugin) specific
"bridge": "ovs0",
"vxlanID": 42
"vxlanID": 42,
"ipam": {
"type": "dhcp"
"routes": [ "10.3.0.0/16", "10.4.0.0/16" ]
"type": "dhcp",
"routes": [ { "dst": "10.3.0.0/16" }, { "dst": "10.4.0.0/16" } ]
}
}
```
@ -151,8 +151,8 @@ The network configuration is described in JSON form. The configuration can be st
"type": "macvlan",
// ipam specific
"ipam": {
"type": "dhcp"
"routes": [ "10.0.0.0/8" ]
"type": "dhcp",
"routes": [ { "dst": "10.0.0.0/8", "gw": "10.0.0.1" } ]
},
}
```
@ -170,7 +170,7 @@ Like CNI plugins, the IPAM plugins are invoked by running an executable. The exe
Success is indicated by a zero return code and the following JSON being printed to stdout (in the case of the ADD command):
```json
```
{
"ip4": {
"ip": <ipv4-and-subnet-in-CIDR>,