@ChibangLW Do you know if there is a documentation for all networks json keys (in the LXD documentation are only a couple of values set).
Should we save the config json in the database or the values from the config object as separate attributes?

config

"config": {
            "ipv4.address": "10.121.38.1/24",
            "ipv4.nat": "true",
            "ipv6.address": "fd42:320d:b243:90dd::1/64",
            "ipv6.nat": "true"
       },

example json response from lxd

{
    "type": "sync",
    "status": "Success",
    "status_code": 200,
    "operation": "",
    "error_code": 0,
    "error": "",
    "metadata": {
        "config": {
            "ipv4.address": "10.121.38.1/24",
            "ipv4.nat": "true",
            "ipv6.address": "fd42:320d:b243:90dd::1/64",
            "ipv6.nat": "true"
        },
        "description": "",
        "name": "lxdbr0",
        "type": "bridge",
        "used_by": [
            "/1.0/containers/a2-Restore"
        ],
        "managed": true,
        "status": "Created",
        "locations": [
            "none"
        ]
    }
}

Network #144

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions