Startseite
Bild
Bild
  • ready to use and comfortable ZFS storage appliance for iSCSI/FC, NFS and SMB
  • Active Directory support with Snaps as Previous Version
  • user friendly Web-GUI that includes all functions for a sophisticated NAS or SAN appliance.
  • commercial use allowed
  • no capacity limit
  • free download for End-User


Bild
  • Individual support and consulting
  • increased GUI performance/ background agents
  • bugfix/ updates/ access to bugfixes
  • extensions like comfortable ACL handling, disk and realtime monitoring or remote replication
  • appliance diskmap, security and tuning (Pro complete)
  • Redistribution/Bundling/setup on customers demand optional
please request a quotation.
Details: Featuresheet.pdf

napp-it-zfs


napp-it cs "client/server" edition (currently beta preview, not all functions ready)


Main use cases for napp-it cs

  • Large ZFS systems with many filesystems, snaps, shares or users due list based views.
  • Serverfarms with centralized management for many (ZFS) servers (BSD, Illumos/Solaris, Linux, OSX, Windows)
  • Advanced and user extendable Web-GUI - mainly but not only for ZFS-
  • Web-GUI for low RAM/CPU systems (napp-it cs requires almost no resources on a server) like Raspberry labs
  • Web-GUI ZFS settings compatible with CLI settings. A server is fully operable with napp-it cs activated only on demand.

  • Napp-it cs is not  a replacement for napp-it on a local Illumos/Solaris ZFS server, it is an add-on
  • Napp-it cs is not a storage VM ex on Proxmox but an additional web-gui for storage and ZFS management
  • Napp-it cs is not restricted to ZFS management.  it can be used to even manage Raspberry IOT pools


Napp-it cs has three parts


1. The frontend management web-gui to manage a server or servergroup

The frontend part are Perl cgi scripts on Windows for an Apache webserver without admin permissions.
(Windows 10, Windows 11 or Windows server).

Software frontend requirement: Webserver with Perl, currently Windows Xampp portable.
Installation: Not required, just download the ready to run software and connect browser via http or https

Download frontend, uncompress folder xampp to c:\xampp
Download /doc/downloads/xampp.zip

Start the frontend software: /xampp/web-gui-it/data/start_as_admin.bat
(right mouse click, run as admin)

The backend server part of the software is in /xampp/napp-it/data/cs_server.
or available as seperate download. Copy this folder cs_server to any location of the ZFS servers you want to manage.
(preferred location is a systemfolder like /var/web-gui/data as a future online setup/update will use this folder)


2. The backend server application (cs_server)

These are two Perl background scripts (server.pl and monitor.pl)  that can run on nearly any OS or NAS appliance.
They are started as root to allow server management ex via zfs ,zpool or other tools.
Requirement: Perl, nothng else (this is why it runs on Arm or X86 up from 512 MB RAM. Communication between
frontend web-GUI and backend is done over a socket connection that you can restrict to frontend ip and an auth hash. 
Server tested on BSD (Free-BSD 14), Linux (Proxmox), OSX, Solaris/Illumos/SmartOS and devices like Raspberry.

Installation: not required, just download cs_server manually or via wget (console as root, to /var/web-gui,
wget download for BSD, Linux and Illumos/Solaris)
You can then edit server.auth, restrict ip, optionally enforce callback and start. After a second download cs_server is autostarted..
wget -O - https://www.napp-it.org/nappitcs  | perl

Download on Windows (cs_server part only): download xampp.zip, extract to c:\xampp and start via mouse right click on /as admin)
"C:\xampp\web-gui\data\start_server_only_as_admin.bat"

or copy cs_server to any location of your (ZFS) server or NAS, either the system folder /var/web-gui
or desktop (OSX, Windows) or a ZFS pool like tank/data, then start the software from a console as root/admin.
perl /path_to_cs_server/start_server_as_admin.pl

Communication between frontend web-gui and your servers is established via a socket channel on port 63000.
No api or other 3rd party software is required. Communication is restricted by ip and authentcation. 


3. HTTPS Webserver for encrypted callback communication between frontend an your servers (cs_connect, optional)

If you need a higher security level, you can encrypt communiction (command and results beside basic stats) between frontend and servers.
This is optional and requires curl for https up/downloads of commands and results on your backend servers.
You can enable callback communication in About > Settings (add ip or hostname of https server) or enforce in the server.pl app.

Encrypted callback communication:
With callback enabled, the frontend web-gui uploads a command like "zfs list" as a file to the https server (Xampp Apache or any other
external https server ex www2.university.org (with a valid certificate) and instructs a backend server to download the command file.
The server executes the command and uploads the result back to the https server from where it can be downloaded by the frontend gui.cs_connect
You can run the cs_connect modul on Apache or a public webserver wita h cgi capability. Just copy the small cs_connect folder/script to the cgi-folder and set cs_connect.pl to executable. On a Linux/Unix server modify first line of the script with correct Perl path (/usr/bin/perl). All communication is filebased in a tmp folder below cs_connect.


Basic configuration:
Frontend client: Use menu ZFS Servergroup to add (ZFS) servers with an auth value that you want to manage.
Backend Server: Care that server.auth has the same content as auth in the member file on Windows /xampp//web-gui/_log/group/
Optionally edit server.pl with settings to restrict ip access, timeout or other settings.

napp-it 15.05.2024