- Updated patch file for pvemanagerlib.js to pve-manager: 5.3-5
- Updated patch file for apidoc.js to pve-docs: 5.3-1
- Updated patch file for ZFSPlugin.pm to libpve-storage-perl: 5.0-33
- When changing the 'target' and 'pool' field to be editable in the Edit
ZFS over iSCSI panel it created an issue when you went to save any
change to that panel. The parameters were defined as { fixed => 1 }. Now
I don't know the backend of this but I changed it to { optional => 1} or
to { fixed => 0} they both worked. So I went with the { fixed => 0 } on
the 'target' and 'pool'. This fixes issue #27.
- Added a file with the version of the 'libpve-storage-perl' (e.g. -
ZFSPlugin-5.0-30.pm.patch to follow each version has it is changed.
- Made the fields Pool, Target, API Username, API Password editable.
- Added a Confirm Password field and logic to compare
- Hide the password in the 'Edit' panel.
- This is for issue/enhancement #26
- Kept each patch for the version of pvemanagerlib.js and if there are
bugs from the first patch release then added an '_<int>' to the version
of the patch. The pvemanagerlib.js will always follow the highest
version.
- Updated pvemanagerlib.js.patch to reflect pve-manager version 5.2-9
- Updated ZFSPlugin.pm.patch to reflect libpve-storage-perl version
5.0-30
- Fixed issue with multipathing when NOT multipathing on the run_command
function.
- Fixed whitespace in README.md
- Added patch from @tl8roy to add multipathing to the ZFSPluging.pm for
FreeNAS. I believe this was only patched and tested for FreeNAS. I
tested WITHOUT using multipathing and I have had no issues. Closes
enhancement request #15 and reference #11.
- This change allows the API traffic to be on a different interface then
the iSCSI Provider interface. This allows the selection of the FreeNAS
WebGUI address for HTTP/HTTPS to be on a specific interface instead of
"ALL" (0.0.0.0) interfaces. If the API Host is not defined then the API
traffic will default to the iSCSI Provider interface.
- Add a simple API test using the FreeNAS API call to get its version
number, which could prove useful in future versions. Closes#17
- Whitespace cleanup
- Whitespace cleanup
- Removed the 'hardcoded' username and password. Will not throw an error
if it is not defined or blank in /etc/pve/storage.cfg for each ZFS via
ISCSI definition.
- Used a Ternary (Elvis - ?:) Operator for the scheme variable.
Updates for pve-manager 5.2-6 and pve-docs 5.2-5. Fixes issue #13.
Added some functionality to the js code to be selective on the FreeNAS
fields only when FreeNAS-API is chosen. Fixes issue #14.
- The perl code was creating a new variable in the ‘if’ code block by
using 'my' at the beginning of the assignment at line 452. Once the code
exited this block that variable was released and now defaulted to the
main block variable at line 441 which is still set to 'undef'. Removing
the 'my' from the assignment line allowed the code to use the main block
$iscsi_lunid variable.
Fixes issue #7
- So we do not have to change the /usr/bin/pvedaemon a small fix to
check the $item->{'iscsi_target'} varaible from the API call is needed.
This closes issue #3.
- Updated patch files for Proxmox 5.2 changes
- Updated README for some newer instructions.
- Added change to the API viewer so the freenas_user and
freenas_password show on the 'edit' dialog.
- Added the ability to process two new fields in the storage.cfg under
an iSCSI configuration.
freenas_user <username>
freenas_password <password>
No more editing the FreeNAS.pm file
- In FreeNAS 11.1 it seems like a Lun of 0 becomes 'Auto'. When the API
returns the targent_to_extent data any Lun of "Auto" become 'undef' and
causes issues and errors in the syslog. This change corrects this
behavior. Have tested with adding, detaching, removing and "Moving Disk"
functions of Proxmox version 5.1-51.
Kevin Scott Adams
Kevin Scott Adams
Tristan Lostroh
Krzysztof Raczkowski
Eugene Chow
Andrew Beam
Ondrej Bima