From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 927991FF0B7 for ; Fri, 13 Nov 2026 04:08:24 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 1C288218F6; Fri, 13 Nov 2026 04:04:09 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH v4 cluster,storage,docs,manager 00/36] SAN: cluster-wide multipath, SAN views and a guided setup for shared LVM Date: Fri, 13 Nov 2026 04:00:18 +0100 Message-ID: <20261113030146.1559030-1-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794538913330 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.094 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: ENGB5TB6R3KPPHHBPRIMEODXQ4U2V2SR X-Message-ID-Hash: ENGB5TB6R3KPPHHBPRIMEODXQ4U2V2SR X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: This is v4 of the combined and reduced series of the cluster-wide multipath work [0][1] and Dietmar's RFC for guided remote storage setup and SAN visibility [2]. v3 [3] had 76 patches in six repositories. I tried to trim v4 down by reducing both the scope, minimally, and the implementation. This narrows the series to shared LVM on iSCSI and Fibre Channel LUNs: 36 patches in four repositories, about 7700 added lines instead of 26300. It basically trades automatic cleanup and broad usage checks for a smaller implementation and documented procedures for the admin. "The rework" below gives some reasoning, "Changes since v3" the details. Overview of what an admin gets with this: - Datacenter > Storage > SAN, a new entry below Storage, shows the multipath state of every node and of the LUNs that multipath handles, and edits the multipath entries and array-specific overrides. I explicitly chose this over the client/plugin side of Storage, as we do not have e.g. Ceph or ZFS/LVM/... creation in there either. We might want to rethink and consolidate our storage interface vs. management story in the future, but IMO a partial switch now is not worth it, that would add even more potential for confusion than the new SAN view. - Its Add Storage menu guides through shared LVM on a LUN: for iSCSI it connects or reuses a target, with the initiator names of all nodes at hand, for Fibre Channel it takes a LUN the nodes already see. Both set up multipath for the LUN and end with its state on every node of the new storage. - Datacenter > Storage > Add keeps its dialogs. The iSCSI one gets a Multipath option and the LVM one enables Shared for a base storage, so the same works there in two steps. Both name the SAN view in a note whose link opens it, as admins coming from other platforms look for their SAN there first. - Node > SAN lists the LUNs of a node with their paths and usage, can wipe a LUN that no storage uses, and shows the iSCSI sessions. The rework: The series is for a cluster that reaches the LUNs of an array over iSCSI or Fibre Channel on two or more paths and puts shared LVM on them. v3 went further: it cleaned up after the admin, tried to find every user of a LUN before a write, and added iSCSI operations of its own. Each of these brought a ton of state and failure handling that has to be maintained and tested. v4 drops them for the time being to get this into a shippable state, and tries to follow a few rules instead: - Add, never remove. A node adds the WWIDs it needs to the multipath allow-list, but never removes one and never flushes a map. v3 did, which took a record of who added what and probes for maps still in use. Removing a LUN is rare and hurts when it goes wrong, so I made it a documented procedure. - Check a write where it happens. Creating a volume group or wiping a LUN checks that no storage references it and looks at the device on that node for mounts, holders and, for a volume group, existing data. v3 also scanned for other local users, let the web UI ask the other nodes and verified the device again between the writes of a wipe. Stopping the users on other nodes and hosts before a wipe is up to the admin now. - Lists do not probe. The LUN inventory uses what udev, multipathd and LVM's hint file already know, it no longer reads signatures or runs LVM commands. The price is that usage can lag behind, for example on the other nodes after a wipe, and that LVM keeps no hints while it sees duplicate PVs, for example a LUN with an old PV that has two paths and no map yet. Until that is resolved, the node shows no volume group names and no storage for a Fibre Channel LUN, which has no base volume to go by. A write asks LVM itself and is not affected. - Use what is there. The output of multipathd is parsed in Perl. v3 had a new crate in proxmox and its binding in proxmox-perl-rs for that (patches 01 and 02), both repositories are out of the series. Bounding the LVM status commands got reworked on top of the existing run_fork_with_timeout() and sent separately [4]. - No new iSCSI operations. Session logout, record removal, rescan and session parameters are gone from the API and from pvenode. The iSCSI view is read-only and iscsiadm remains for the rest, so removing an iSCSI storage leaves its sessions and node records behind, as on master. - The guided setup makes the API calls an admin would make by hand, for iSCSI and Fibre Channel only. It no longer tracks and resumes partial setups, always enables multipath, and no storage plugin gets a setup method for it. It looks at the LUN on the node serving the web UI only and does not ask the other nodes before it writes. Instead it ends with the state of the LUN on each node of the storage, from the cluster-wide status, so that a node without access shows up right there. - Multipath management is turned on by the admin. The API no longer checks that every node supports it before the option is set, or that nothing needs the option or an entry before it is removed. The docs say to upgrade all nodes first and how to remove a LUN. Again, we might reintroduce _some_ of this in a fitting form later, but scope creep weighed v3 (and the revisions before it) down way too much for it to ever get into a sane, shippable state where we do not get a ton of maintenance issues. This here is certainly not perfect, but it is at least still manageable and should get us the most relevant convenience features. Two things an admin will likely miss: there is no notification when a LUN loses path redundancy, the state only shows on the SAN pages and in the API. A node with fewer paths than its iSCSI portals or the expected paths of the LUN's entry at least shows as degraded there, and a LUN that only has one path reads "OK (1 path)" instead of optimal. And Fibre Channel starts at a LUN the nodes already see, the web UI neither lists the WWPNs of the nodes nor rescans their HBAs; the chapter gives the commands for both, and the setup points to the rescan. How it works: - /etc/pve/multipath.cfg holds explicit entries per WWID (nodes, alias, no-path-retry, expected paths), /etc/pve/multipath-overrides.conf array settings in multipath.conf syntax; patch 01 registers both. An iSCSI storage with the new 'multipath' option supplies its LUNs without entries, Fibre Channel LUNs get an explicit entry. - pvestatd calls one function of pve-storage per pass. It adds the WWIDs the node needs to /etc/multipath/wwids, writes the drop-ins /etc/multipath/conf.d/pve-*.conf (entries, overrides and one generated default, auto_resize grow_only) and reloads multipathd when something changed. The same call publishes the node's maps and their state through the node key-value store (key 'multipath'). - /cluster/multipath/status aggregates these reports, derives 'missing' from the configuration and names the storage that requests each map; /cluster/multipath/{wwid,overrides} edit the two files. - The volumes of an iSCSI storage with the option end in dm-uuid-mpath- instead of the name of one path, so an LVM storage uses them through the existing 'base' mechanism. - /nodes/{node}/scan/san-luns and 'pvesm scan san-luns' return one row per LUN with a WWID, /nodes/{node}/iscsi/{status,target} the read-only session view. - Volume group creation and wipe run under a cluster lock per LUN (cfs_lock_domain) and do not hold the storage configuration lock while they write. Adding an LVM storage with a new base volume still does, as before. - multipath-tools becomes a Recommends of libpve-storage-perl. Nodes without it report that; plain iSCSI and LVM are unaffected. Patches: - cluster 01: register the two configuration files - storage 02-22: helpers for the disk and iSCSI session inventory (mostly Dietmar's), the multipath library and configuration, the iSCSI option, the per-node apply and status with their API, the LUN inventory, the read-only iSCSI status, volume groups on LUNs and the wipe, in that order - docs 23: the multipath chapter, rewritten around tasks - manager 24-36: the pvestatd call, report and API mounts, then the views, the two dialog changes, the two guided setups and the note in the add dialogs Changes since v3 [3] (numbers are v3 patches): - applied meanwhile: the independent fixes 05 and 07 to 11, the documentation note 43 and the scan picker fixes 47 and 48 - sent separately [4]: the bound for LVM status commands (04, 06, 46), now one pve-storage patch without a pvestatd part or plugin API change. Unlike v3 it leaves thin pool activation unbounded. Whichever of the two is applied second has to pass the status cache to the two lvm_vgs() calls of the base volume activation - removed: everything "The rework" names, and with it the NFS, SMB/CIFS and ZFS over iSCSI types, the wipe step, the node selector and the multipath checkbox of the guided setup; the structured 'defaults' section of multipath.cfg and the per-LUN path settings except no-path-retry (the generated defaults no longer set find_multipaths, user_friendly_names and polling_interval); the duplicate PV flag, the rows for devices without a WWID and the 'incomplete' marking in the LUN lists; the include-remote option of the disk list; identity-based names for plain iSCSI volumes (40); the JavaScript unit tests - changed: - get_disks() lists iSCSI devices only on request, so Ceph OSD creation needs no change (45) and no Breaks - one SAN panel below Datacenter > Storage instead of a SAN and a Multipath view, with one state per node and per LUN. The state of a LUN names the nodes it applies to, a single path is shown as such instead of optimal, and the LUN list says how the multipath of each LUN is managed instead of a yes or no for an entry - the guided setup starts from the Add Storage menu of that panel instead of Datacenter > Storage > Add, offers snapshots as volume chain, the Fibre Channel one adds its storage itself, and both show the state of the LUN on each node at the end instead of asking the other nodes before - the node disk API adds the storage of a volume group on a LUN as shared and for all nodes, and only under a new storage ID - the chapter went from 527 to 260 lines - new: destroying the volume group of a shared storage through the node disk API is refused, and the LVM dialog enables Shared when a base storage is selected; explicit multipath entries can set the expected number of paths, which the Fibre Channel setup fills in When applying, versioned dependencies have to be set: pve-manager on libpve-storage-perl, and libpve-storage-perl (also as build dependency) on the libpve-cluster-perl with patch 01, as PVE::Storage registers the two files when it is loaded. The per-node target and portal series [5][6] are independent of this one. It takes the LUNs of an iSCSI storage from the sessions of its one target, so if a storage can have several targets per node, whichever is applied second has to cover that. I tested this on a six-node nested cluster attached to a NetApp AFF A20 with three iSCSI portals and to Linux LIO targets with two: the guided iSCSI setup with a new and with a reused connection storage, the same through the plain dialogs and from the CLI as documented, a LUN that one node is not allowed to see and gets access later, the Fibre Channel flow through the web UI, also as an administrator other than root@pam, a guest on the resulting storages (snapshot, rollback, online resize, live migration, one path cut under I/O), growing a LUN, wipe and its refusals, one path and all paths down with queued I/O, a stopped multipathd, a node reboot and the documented LUN removal. The lab has no FC hardware, so I emulated it with software FCoE in VN2VN mode and an LIO tcm_fc target on two fabrics: the nodes get real FC host and remote port objects, and the documented WWPN listing, rescan and LUN growth work there as written. The guided Fibre Channel setup ran on such a LUN, with one node on one fabric only and one node that saw the LUN only after the rescan. The setup records the paths it sees in the LUN's entry, so the node on one fabric shows as degraded, and a fabric cut stays degraded also after the kernel removed the lost paths (66 seconds dev_loss_tmo of the LIO profile). Real HBA drivers were not tested. Most of that ran with the NVMe over Fabrics series on top and with the LVM status patch [4] applied, the series alone ran on one node of that cluster for the guided setups, the CLI procedure and the views. Without [4] a stuck LVM command blocks pvestatd as on master. [0]: https://lore.proxmox.com/pve-devel/20260626121000.2095591-1-t.lamprecht@proxmox.com/ [1]: https://lore.proxmox.com/pve-devel/20260703124707.1172980-2-t.lamprecht@proxmox.com/ [2]: https://lore.proxmox.com/pve-devel/20260731102156.3947857-1-dietmar@proxmox.com/ [3]: https://lore.proxmox.com/pve-devel/20261105233336.2178064-1-t.lamprecht@proxmox.com/ [4]: https://lore.proxmox.com/pve-devel/20261111015217.941220-1-t.lamprecht@proxmox.com/ [5]: https://lore.proxmox.com/pve-devel/20260430173220.441001-1-m.limbeck@proxmox.com/ [6]: https://lore.proxmox.com/pve-devel/20260804090819.2136483-1-dietmar@proxmox.com/ pve-cluster: Thomas Lamprecht (1): cfs: observe the multipath configuration files src/PVE/Cluster.pm | 2 ++ src/pmxcfs/status.c | 2 ++ 2 files changed, 4 insertions(+) pve-storage: Dietmar Maurer (8): diskmanage: collect disk transport type from lsblk diskmanage: qualify NVMe over fabrics transport diskmanage: optionally include iSCSI session devices in disk enumeration diskmanage: collect native NVMe multipath path state iscsi: factor out session device map from device list diskmanage: add helper to list multipath devices pvesm: expose the SAN LUN inventory api: add node-level iSCSI status Thomas Lamprecht (13): multipath: add a library around multipathd multipath: add a cluster-wide configuration iscsi: add an option to manage storage LUNs with multipath lvm: activate a missing base volume before using the volume group multipath: apply the configuration on every node multipath: publish per-node status api: add endpoints for the cluster-wide multipath configuration api: multipath: add the cluster-wide health status api: scan: add a SAN LUN inventory disks: lvm: drop unused imports disks: lvm: allow volume groups on SAN LUNs and multipath maps disks: lvm: refuse to destroy the volume group of a shared storage disks: allow wiping a SAN LUN that no storage uses debian/control | 3 +- src/PVE/API2/Disks.pm | 36 +- src/PVE/API2/Disks/LVM.pm | 64 ++- src/PVE/API2/ISCSI.pm | 165 +++++++ src/PVE/API2/Makefile | 2 + src/PVE/API2/Multipath.pm | 446 ++++++++++++++++++ src/PVE/API2/Storage/Scan.pm | 197 ++++++++ src/PVE/CLI/pvesm.pm | 14 + src/PVE/Diskmanage.pm | 212 ++++++++- src/PVE/ISCSI/Topology.pm | 95 ++++ src/PVE/Makefile | 6 + src/PVE/Multipath.pm | 211 +++++++++ src/PVE/Multipath/Config.pm | 204 ++++++++ src/PVE/Multipath/Generator.pm | 112 +++++ src/PVE/Multipath/Identity.pm | 43 ++ src/PVE/Multipath/Status.pm | 184 ++++++++ src/PVE/Storage/ISCSIPlugin.pm | 211 +++++---- src/PVE/Storage/LVMPlugin.pm | 128 ++++- src/PVE/Storage/Makefile | 3 +- src/PVE/Storage/SAN.pm | 328 +++++++++++++ src/test/Makefile | 34 +- src/test/disk_api_test.pm | 256 ++++++++++ src/test/disk_tests/iscsi/disklist | 1 + .../disk_tests/iscsi/disklist_expected.json | 19 + src/test/disk_tests/iscsi/lsblk | 5 + src/test/disk_tests/iscsi/sda/device/model | 1 + src/test/disk_tests/iscsi/sda/device/vendor | 1 + .../disk_tests/iscsi/sda/queue/rotational | 1 + src/test/disk_tests/iscsi/sda/size | 1 + src/test/disk_tests/iscsi/sda_udevadm | 21 + src/test/disk_tests/multipath/disklist | 11 + .../multipath/disklist_expected.json | 107 +++++ src/test/disk_tests/multipath/dm-0/dm/name | 1 + src/test/disk_tests/multipath/dm-0/dm/uuid | 1 + src/test/disk_tests/multipath/dm-0/size | 1 + src/test/disk_tests/multipath/dm-0_slaves | 4 + src/test/disk_tests/multipath/dm-1/dm/name | 1 + src/test/disk_tests/multipath/dm-1/dm/uuid | 1 + src/test/disk_tests/multipath/dm-1/size | 1 + src/test/disk_tests/multipath/dm-1_slaves | 4 + src/test/disk_tests/multipath/dm-2/dm/name | 1 + src/test/disk_tests/multipath/dm-2/dm/uuid | 1 + src/test/disk_tests/multipath/dm-2/size | 1 + src/test/disk_tests/multipath/dm-2_slaves | 0 src/test/disk_tests/multipath/dm-3/dm/name | 1 + src/test/disk_tests/multipath/dm-3/dm/uuid | 1 + src/test/disk_tests/multipath/dm-3/size | 1 + src/test/disk_tests/multipath/dm-3_slaves | 0 src/test/disk_tests/multipath/dm-4/dm/name | 1 + src/test/disk_tests/multipath/dm-4/dm/uuid | 1 + src/test/disk_tests/multipath/dm-4/size | 1 + src/test/disk_tests/multipath/dm-4_slaves | 0 src/test/disk_tests/multipath/lsblk | 77 +++ src/test/disk_tests/multipath/lvs | 0 src/test/disk_tests/multipath/mounts | 1 + .../multipath/multipath_expected.json | 59 +++ src/test/disk_tests/multipath/multipathd | 124 +++++ .../multipath/multipathd_status_expected.json | 40 ++ .../nvme-subsystem/nvme-subsys0/nvme3/address | 1 + .../nvme-subsys0/nvme3/nvme2c3n1/ana_state | 1 + .../nvme-subsystem/nvme-subsys0/nvme3/state | 1 + .../nvme-subsystem/nvme-subsys0/nvme4/address | 1 + .../nvme-subsys0/nvme4/nvme2c4n1/ana_state | 1 + .../nvme-subsystem/nvme-subsys0/nvme4/state | 1 + .../nvme-subsystem/nvme-subsys1/nvme0/address | 1 + .../nvme-subsystem/nvme-subsys1/nvme0/state | 1 + .../disk_tests/multipath/nvme8n1/device/model | 1 + .../multipath/nvme8n1/device/transport | 1 + .../multipath/nvme8n1/queue/rotational | 1 + src/test/disk_tests/multipath/nvme8n1/size | 1 + src/test/disk_tests/multipath/nvme8n1_udevadm | 14 + .../disk_tests/multipath/nvme9n1/device/model | 1 + .../multipath/nvme9n1/device/transport | 1 + .../multipath/nvme9n1/device/vendor | 1 + .../multipath/nvme9n1/queue/rotational | 1 + src/test/disk_tests/multipath/nvme9n1/size | 1 + src/test/disk_tests/multipath/nvme9n1_udevadm | 12 + .../multipath/nvme_path_status_expected.json | 19 + src/test/disk_tests/multipath/partlist | 0 src/test/disk_tests/multipath/pvs | 1 + .../disk_tests/multipath/sda/device/model | 1 + .../disk_tests/multipath/sda/device/vendor | 1 + .../disk_tests/multipath/sda/holders/holder | 1 + .../disk_tests/multipath/sda/queue/rotational | 1 + src/test/disk_tests/multipath/sda/size | 1 + src/test/disk_tests/multipath/sda_udevadm | 18 + .../disk_tests/multipath/sdb/device/model | 1 + .../disk_tests/multipath/sdb/device/vendor | 1 + .../disk_tests/multipath/sdb/holders/holder | 1 + .../disk_tests/multipath/sdb/queue/rotational | 1 + src/test/disk_tests/multipath/sdb/size | 1 + src/test/disk_tests/multipath/sdb_udevadm | 18 + .../disk_tests/multipath/sdc/device/model | 1 + .../disk_tests/multipath/sdc/device/vendor | 1 + .../disk_tests/multipath/sdc/holders/holder | 1 + .../disk_tests/multipath/sdc/queue/rotational | 1 + src/test/disk_tests/multipath/sdc/size | 1 + src/test/disk_tests/multipath/sdc_udevadm | 18 + .../disk_tests/multipath/sdd/device/model | 1 + .../disk_tests/multipath/sdd/device/vendor | 1 + .../disk_tests/multipath/sdd/holders/holder | 1 + .../disk_tests/multipath/sdd/queue/rotational | 1 + src/test/disk_tests/multipath/sdd/size | 1 + src/test/disk_tests/multipath/sdd_udevadm | 18 + src/test/disk_tests/multipath/zpool | 1 + .../disk_tests/sas/disklist_expected.json | 1 + src/test/disk_tests/sas/lsblk | 5 + src/test/disklist_test.pm | 107 ++++- src/test/multipath-three-states.json | 52 ++ src/test/run_disk_api_tests.pl | 11 + src/test/run_iscsi_activation_tests.pl | 86 ++++ src/test/run_lun_identity_tests.pl | 48 ++ src/test/run_multipath_api_tests.pl | 352 ++++++++++++++ src/test/run_multipath_tests.pl | 169 +++++++ src/test/run_san_api_tests.pl | 94 ++++ src/test/run_san_library_tests.pl | 84 ++++ src/test/run_san_lun_scan_tests.pl | 180 +++++++ src/test/run_san_nvme_tests.pl | 107 +++++ src/test/run_san_taint_tests.pl | 60 +++ src/test/run_san_wipe_tests.pl | 137 ++++++ src/test/run_test_lvm_base_activation.pl | 117 +++++ src/test/run_test_lvm_base_conflicts.pl | 232 ++++++--- src/test/run_test_lvm_create.pl | 14 + 123 files changed, 5244 insertions(+), 214 deletions(-) pve-docs: Thomas Lamprecht (1): storage: document the cluster-wide multipath management pmxcfs.adoc | 2 + pve-storage-iscsi.adoc | 11 ++ pve-storage-iscsidirect.adoc | 2 +- pve-storage-lvm.adoc | 3 + pve-storage-multipath.adoc | 260 +++++++++++++++++++++++++++++++++++ pvesm.adoc | 18 ++- 6 files changed, 290 insertions(+), 6 deletions(-) pve-manager: Dietmar Maurer (2): api: nodes: expose the iSCSI status ui: node: san: show iSCSI targets and sessions Thomas Lamprecht (11): pvestatd: apply the multipath configuration and report the node status report: add the managed multipath configuration api: cluster: add the multipath endpoints ui: dc: add a SAN view ui: storage: iscsi: add the multipath option ui: lvm: enable shared when a base storage is selected ui: node: add SAN LUNs panel ui: node: san: wipe a LUN that no storage uses ui: dc: san: add a guided setup for shared LVM on iSCSI ui: dc: san: add a guided setup for shared LVM on Fibre Channel ui: storage: point the iSCSI and LVM add dialogs to the SAN view PVE/API2/Cluster.pm | 7 + PVE/API2/Nodes.pm | 7 + PVE/Report.pm | 3 + PVE/Service/pvestatd.pm | 7 + www/manager6/Makefile | 12 + www/manager6/SANUtils.js | 161 +++++++++ www/manager6/Utils.js | 14 + www/manager6/dc/Config.js | 23 +- www/manager6/dc/MultipathWwidEdit.js | 81 +++++ www/manager6/dc/SAN.js | 331 ++++++++++++++++++ www/manager6/node/Config.js | 24 ++ www/manager6/node/ISCSITargets.js | 122 +++++++ www/manager6/node/SANLuns.js | 184 ++++++++++ www/manager6/storage/Base.js | 5 + www/manager6/storage/IScsiEdit.js | 46 +++ www/manager6/storage/LVMEdit.js | 6 + www/manager6/storage/wizard/FibreChannel.js | 162 +++++++++ www/manager6/storage/wizard/IScsi.js | 272 ++++++++++++++ www/manager6/storage/wizard/LunSelect.js | 181 ++++++++++ www/manager6/storage/wizard/NodeIdentities.js | 83 +++++ www/manager6/storage/wizard/Wizard.js | 254 ++++++++++++++ www/manager6/window/SANLunState.js | 115 ++++++ www/manager6/window/SANLunWipe.js | 53 +++ 23 files changed, 2147 insertions(+), 6 deletions(-)