Thanks for the MP Yao!
This looks good to me from the RAID standpoint
$ jq '.storage.blockdev[] | select(.DEVTYPE | test("partition")) | {DEVNAME,
ID_PART_TABLE_TYPE, ID_PART_ENTRY_SCHEME}'
examples/machines/lp1999173-raid1.json
{
"DEVNAME": "/dev/vdb1",
"ID_PART_TABLE_TYPE": "gpt",
"ID_PART_ENTRY_SCHEME": "gpt"
}
{
"DEVNAME": "/dev/vdb2",
"ID_PART_TABLE_TYPE": "gpt",
"ID_PART_ENTRY_SCHEME": "gpt"
}
{
"DEVNAME": "/dev/md127p1",
"ID_PART_TABLE_TYPE": null,
"ID_PART_ENTRY_SCHEME": "gpt"
}
But there are also scenarios where ID_PART_ENTRY_SCHEME is different from
ID_PART_TABLE_TYPE ; so I want to check what that means for them
$ jq '.storage.blockdev[] | select(.DEVTYPE | test("partition")) | {DEVNAME,
ID_PART_TABLE_TYPE, ID_PART_ENTRY_SCHEME}'
examples/machines/ms-win-dyn-disk.json
{
"DEVNAME": "/dev/sda1",
"ID_PART_TABLE_TYPE": "dos",
"ID_PART_ENTRY_SCHEME": null
}
{
"DEVNAME": "/dev/sda2",
"ID_PART_TABLE_TYPE": "dos",
"ID_PART_ENTRY_SCHEME": null
}
and probe-data from private reports:
{
"DEVNAME": "/dev/sdb5",
"ID_PART_TABLE_TYPE": "dos",
"ID_PART_ENTRY_SCHEME": "freebsd"
}
{
"DEVNAME": "/dev/sdb6",
"ID_PART_TABLE_TYPE": "dos",
"ID_PART_ENTRY_SCHEME": null
}
--
https://code.launchpad.net/~medicalwei/curtin/+git/curtin/+merge/481164
Your team curtin developers is requested to review the proposed merge of
~medicalwei/curtin:raid-partuuid into curtin:master.
--
Mailing list: https://launchpad.net/~curtin-dev
Post to : curtin-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~curtin-dev
More help : https://help.launchpad.net/ListHelp
