Comment 4 for bug 1687305

Revision history for this message
Nobuto Murata (nobuto) wrote : Re: maas reports an incorrect amount of available storage space for a virsh pod

$ virsh pool-list
 Name State Autostart
-------------------------------------------
 default active yes
 uvtool active yes

$ virsh pool-info default
Name: default
UUID: 14fe8b2e-6a3f-475c-be84-4731cf08253a
State: running
Persistent: yes
Autostart: yes
Capacity: 117.99 GiB
Allocation: 35.02 GiB
Available: 82.97 GiB

$ virsh pool-info uvtool
Name: uvtool
UUID: 98f8636d-7c51-4363-9490-c5c64f003b75
State: running
Persistent: yes
Autostart: yes
Capacity: 117.99 GiB
Allocation: 35.02 GiB
Available: 82.97 GiB

$ maas ubuntu pods read
Success.
Machine-readable output follows:
[
    {
        "resource_uri": "/MAAS/api/2.0/pods/1/",
        "capabilities": [
            "composable",
            "dynamic_local_storage",
            "over_commit"
        ],
        "available": {
            "local_storage": 227381595626,
            "cores": -3,
            "memory": 10243
        },
        "architectures": [
            "amd64/generic"
        ],
        "used": {
            "local_storage": 26000000000,
            "cores": 7,
            "memory": 9728
        },
        "name": "pod-localhost",
        "total": {
            "local_storage": 253381595626,
            "cores": 4,
            "memory": 19971
        },
        "id": 1,
        "type": "virsh"
    }
]