[pod, wishlist] Add support for multiple storage pools.

Bug #1708609 reported by Koaps
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Wishlist
Newell Jensen

Bug Description

I have configured a Pod using Virsh and it is only showing a Local storage (118.9 GiB) however I use a ZFS pool that is 14TB.

virsh pool-list
 Name State Autostart
-------------------------------------------
 default active no
 zfspool active yes

virsh pool-info default
Name: default
UUID: a33198cd-afb7-4184-9b2e-f18fb30bc72f
State: running
Persistent: yes
Autostart: no
Capacity: 102.61 GiB
Allocation: 22.17 GiB
Available: 80.45 GiB

virsh pool-info zfspool
Name: zfspool
UUID: f64a089b-1485-47d2-bf3d-bee5a18af823
State: running
Persistent: yes
Autostart: yes
Capacity: 16.25 TiB
Allocation: 9.48 GiB
Available: 16.24 TiB

maas maas pod read 1
Success.
Machine-readable output follows:
{
    "total": {
        "cores": 24,
        "local_storage": 127624953200,
        "memory": 128907
    },
    "resource_uri": "/MAAS/api/2.0/pods/1/",
    "name": "iaasdev",
    "capabilities": [
        "composable",
        "dynamic_local_storage",
        "over_commit"
    ],
    "type": "virsh",
    "available": {
        "cores": 24,
        "local_storage": 127624953200,
        "memory": 128907
    },
    "used": {
        "cores": 0,
        "local_storage": 0,
        "memory": 0
    },
    "architectures": [
        "amd64/generic"
    ],
    "id": 1
}

Tags: pod virsh

Related branches

Revision history for this message
Данило Шеган (danilo) wrote :

Actually, looking at this, this seems a lot like bug #1687305 — can you confirm you are using latest MAAS (or at least 2.2.1 which includes the fix)?

Local storage is reported as 127624953200 bytes, or 118.8599 GiB: MAAS misinterpreted storage size and assumed everything to be in GiB previously, so your 16.25TiB disk was added up as 16.25 GiB on top of 102.61 giving a total of 118.86Gib.

There seems to be another problem in that we are not ignoring inactive pools.

Can you please confirm what version of MAAS are you running?

Changed in maas:
status: New → Incomplete
Revision history for this message
Koaps (koaps) wrote :

I just upgraded to MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1)

If I try to compose a VM I get a new error:

maas maas pod compose 4 cores=2 memory=2048 storage=local:300 hostname=test

Unable to compose machine because: Failed talking to pod: Specification mandate value for attribute network, line 1, column 13

Changed in maas:
importance: Undecided → Wishlist
status: Incomplete → Triaged
milestone: none → next
summary: - Virsh Pods are not detecting all storage pools
+ [pod, wishlist] Add support for multiple storage pools.
Changed in maas:
milestone: next → 2.4.0beta2
assignee: nobody → Newell Jensen (newell-jensen)
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.