Update README.md

- Updated Roadmap and Updates.
- Removed Attention
- Added a note about systemctl restart pvescheduler.service before
2.2.0-0-beta8.
This commit is contained in:
Kevin Scott Adams 2023-02-12 17:14:15 -05:00
parent 9021ec22b7
commit b05124592f
1 changed files with 20 additions and 40 deletions

View File

@ -1,72 +1,46 @@
# TrueNAS ZFS over iSCSI interface [![Donate](https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=TCLNEMBUYQUXN&source=url) # TrueNAS ZFS over iSCSI interface [![Donate](https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=TCLNEMBUYQUXN&source=url)
### Updates 2022-06-04<br/> - New Repos available. See [!ATTENTION!](#NewRepo) below.<br/> - Support for TrueNAS 13 is available<br/> - Patched for issues with TrueNAS-Scale paths that had more then one level (e.g. Tank/Disk/vDisks) when converting slashes to dashes. ### Updates 2023-02-12<br/> - Added `systemctl restart pvescheduler.service` command to the package.
#### Roadmap #### Roadmap
* Fix automated builds. * Fix automated builds.
* Beta - 'testing' repo component.
* Production - 'main' repo component. * Production - 'main' repo component.
* Package the patches with the deb package.
* Remove the need for the git dependency.
* Change to LWP::UserAgent
* Remove depenancy of the REST::Client because LWP::UserAgent is already installed and used by Proxmox VE.
* Change from FreeNAS to TrueNAS. * Change from FreeNAS to TrueNAS.
* Cleanup the FreeNAS repo and name everything to TrueNAS to be inline with the product. * Cleanup the FreeNAS repo and name everything to TrueNAS to be inline with the product.
* Remove the need for SSH keys and use the API. * Add API key for direct TrueNAS services.
* This is tricky because the format needs to be that of the output of 'zfs list' which is not part of the LunCmd but that of the backend Proxmox VE system and the API's do a bunch of JSON stuff. * Will be a new enable field and API key and will only be used by the plugin.
* You will still need the SSH keys, username, and password because of Proxmox VE using `iscsiadm` to get the list of disks.
* This is tricky because the format needs to be that of the output of 'zfs list' which is not part of the LunCmd but that of the backend Proxmox VE system and the API's do a bunch of JSON stuff.
## Thank you for all that have recently donated to the project - Updated 2022-06-04 ## Thank you for all that have recently donated to the project - Updated 2022-06-04
Alexander Finkhäuser - Recurring Alexander Finkhäuser - Recurring
Bjarte Kvamme - Recurring Bjarte Kvamme - Recurring
Jonathan Schober - Recurring Jonathan Schober - Recurring
Frederic Silvi
Security Camera
Vincent Cui
Jakub Jochec
Mark Komarinski Mark Komarinski
Jesse Bryan Jesse Bryan
Maksym Vasylenko Maksym Vasylenko
Daniel Most Daniel Most
Velocity Host Velocity Host
Robert Hancock Robert Hancock
Clevvi Technology Clevvi Technology
Mark Elkins Mark Elkins
Marc Hodler Marc Hodler
Martin Gonzalez Martin Gonzalez
## <a name="NewRepo"></a>!ATTENTION!: New Repo and GPG file
Issue the following on each node to install the repo and get your Proxmox VE updating the TrueNAS patches automatically:
```bash
curl https://ksatechnologies.jfrog.io/artifactory/ksa-repo-gpg/ksatechnologies-release.gpg -o /etc/apt/trusted.gpg.d/ksatechnologies-release.gpg
curl https://ksatechnologies.jfrog.io/artifactory/ksa-repo-gpg/ksatechnologies-repo.list -o /etc/apt/sources.list.d/ksatechnologies-repo.list
```
The above 'should' overwrite the current list and gpg file to bring your system(s) back to using the ```apt``` or Proxmox VE Update subsystem.
You can used the Proxmox VE Repositories menu to enable and disable the 'main' (TBD) or 'testing' (default) component.
If you did use the temporary repo from "Cloudsmith" then issue the following to clean it up:
```
rm /etc/apt/sources.list.d/ksatechnologies-truenas-proxmox.list
rm /usr/share/keyrings/ksatechnologies-truenas-proxmox-archive-keyring.gpg
```
You can either perform an ```apt-get update``` from the command line or issue it from the Proxmox UI on each Node via ```Datacenter->[Node Name]->Updates```
### 'main' repo (Follows a release branch - Current 2.x) Currently unavailable. ### 'main' repo (Follows a release branch - Current 2.x) Currently unavailable.
Will be production ready code that has been tested (as best as possible) from the 'testing' repo. Will be production ready code that has been tested (as best as possible) from the 'testing' repo.
### 'testing' repo (Follows the master branch) ### 'testing' repo (Follows the master branch)
Will be 'beta' code for features, bugs, and updates. Will be 'beta' code for features, bugs, and updates.
### Converting from manual install to using the ```apt``` package manager.
If you wish, you may remove the directory 'freenas-proxmox' where your system is currently
housing the repo and then issue the following to have a clean system before installing the
package.
On Proxmox 5
```bash
apt install --reinstall pve-manager pve-docs libpve-storage-perl
```
On Proxmox 6 and 7
```bash
apt reinstall pve-manager pve-docs libpve-storage-perl
```
Then follow the new installs below
## New Installs. ## New Installs.
Issue the following from a command line: Issue the following from a command line:
```bash ```bash
@ -80,6 +54,12 @@ apt update
apt install freenas-proxmox apt install freenas-proxmox
``` ```
Before freenas-proxmox-2.2.0-0-beta8 please issue the following:
```
systemctl restart pvescheduler.service
```
due to this post https://github.com/TheGrandWazoo/freenas-proxmox/issues/109#issuecomment-1367527917
Then just do your regular upgrade via apt at the command line or the Proxmox Update subsystem; the package will automatically issue all commands to patch the files. Then just do your regular upgrade via apt at the command line or the Proxmox Update subsystem; the package will automatically issue all commands to patch the files.
```bash ```bash
apt update apt update