From 29bd0757579b51a741ec07410b31267e9fbc09e2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Wed, 24 Feb 2021 20:42:34 -0500
Subject: [PATCH] progress, but still blocked
---
howto/new-machine-cymru.md | 53 ++++++++++++++++++++++++++------------
1 file changed, 36 insertions(+), 17 deletions(-)
diff --git a/howto/new-machine-cymru.md b/howto/new-machine-cymru.md
index 15dc4c0b..82531544 100644
--- a/howto/new-machine-cymru.md
+++ b/howto/new-machine-cymru.md
@@ -786,30 +786,51 @@ Create a host group, a host inside it, and its matching iSCSI initiator:
create host userLabel="chi-node-01" hostType=1 hostGroup="stor01-raid10-1";
create iscsiInitiator iscsiName="iqn.2005-03.org.open-iscsi:c1ec2e02a4a" userLabel="chi-node-01-iscsi" host="chi-node-01";
-The `iscsiName` parameter comes from the output of the `iscsi-iname`
-command on the host.
+To find the right iSCSI initiator identifier, you need to run this
+command on the host:
-Map that group to a LUN:
+ iscsiadm -m session -P 1 | grep 'Iface Initiatorname' | sort -u
- set virtualDisk ["anarcat-test"] logicalUnitNumber=0 hostGroup="stor01-raid10-1";
+Map that group to a Logical Unit Number (LUN):
+
+ set virtualDisk ["anarcat-test"] logicalUnitNumber=3 hostGroup="stor01-raid10-1";
+
+Important: the LUN needs to be greater than 1, LUNs 0 and 1 are
+special.
+
+TODO: the above works in that we get a device to show up on
+chi-node-01, but we can't actually write to it. See [issue 40131](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40131).
Un-map a LUN:
remove virtualDisks ["anarcat-test"] lunMapping;
-TODO: those commands don't actually work. the devices are not visible
-from `chi-node-01`.
-
### iSCSI stuff
-```
- 659 iscsiadm -m discovery -t st -p 172.30.130.22
- 655 iscsiadm -m session -P 3
- 656 iscsiadm -m session -P 1
- 657 iscsiadm -m node -T iqn.1984-05.com.dell:powervault.md3200i.6782bcb00063c6a5000000004ed6d655 -p 172.30.130.22 --logout
- 658 iscsiadm -m node -T iqn.1984-05.com.dell:powervault.md3200i.6782bcb00063c6a5000000004ed6d655 -p 172.30.130.22 --login
- 706 iscsiadm -m node -T iqn.1984-05.com.dell:powervault.md3200i.6782bcb00063c6a5000000004ed6d655 -p 172.30.130.22 --rescan
-```
+Discover storage units interfaces:
+
+ iscsiadm -m discovery -t st -p 172.30.130.22
+
+Pick one of those targets, then login:
+
+ iscsiadm -m node -T iqn.1984-05.com.dell:powervault.md3200i.6782bcb00063c6a5000000004ed6d655 -p 172.30.130.22 --login
+
+This will show details about the connexion, including your iSCSI
+initiator name:
+
+ iscsiadm -m session -P 1
+
+This will also show recognized devices:
+
+ iscsiadm -m session -P 3
+
+This will disconnect from the iSCSI host:
+
+ iscsiadm -m node -T iqn.1984-05.com.dell:powervault.md3200i.6782bcb00063c6a5000000004ed6d655 -p 172.30.130.22 --logout
+
+And this will... rescan the host? Not actually sure *what* this does:
+
+ iscsiadm -m node -T iqn.1984-05.com.dell:powervault.md3200i.6782bcb00063c6a5000000004ed6d655 -p 172.30.130.22 --rescan
# Reference
@@ -864,8 +885,6 @@ quite flexible and provide the ability to create numerous independent
volume groups per unit. They also are capable of tagging spare disks
for auto disk replacement of failed hard drives.
-TODO: bring the iSCSI cluster in production, see [issue 40131](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40131)
-
### iSCSI cluster management tools setup
The access the iSCSI servers, you need to setup the (proprietary)
--
GitLab