Software Selection¶

This is the reason we call it TAPPaaS. Pronounced Tapas like the Spanish dish: A collection of delicious appetizers that makes up a comprehensive serving.

The Software Stack of TAPPaaS delivers the capabilities we believe is needed for a well served Private IT Platform.

Selecting from the enormous pool of software we have used the principles of:

• must be Open Source
• must show a track record of being Secure
• must be "established", and sufficient feature complete
• must be open w.r.t. data formats (enabling migration away from TAPPaaS and/or away from the package)

Foundation¶

Mapping of TAPPaaS functionality to FOSS solutions

Base Cloud Infrastructure platform: Proxmox¶

This deliver most of the Compute and Storage foundation

Alternatives:

• XCP-ng: seems less polished and with less features.
• But it also seems more "free"
• FreeNAS, TrueNAS: good for storage, but not really a cloud platform, they do not have clustering and HA as Proxmox. Uses the same underpinning zfs file system

Persistent Storage layer¶

proxmox with ZFS gives: RAID, Snapshotting, Replication, NFS, iSCSI, Problem with proxmox is a limited GUI for management, and further the choice explosion zfs gives makes it hard to design a solution TAPPaaS will address this with recommended setup and automation

Note that proxmox and zfs do not give Hight Available storage. For this we plan on using CEPHT and Garage S3 We do not consider this a Foundation. but something that goes in to the business layer of TAPPaaS together with a HA implementation of a relational database

Firewall: OPNSense¶

Alternatives are:

• PFsense: PFSense is the original but is going more and more commercial
• OpenWRT: it seems less scalable and less feature rich
• proxmox firewall: would make it easier as it is already build in, but less secure

Backup:¶

• We generally keep all functions contained in VM's or LCM's.
• Running a Proxmox Backup service allow us to store backups on secondary tank, on separate nodes and on separate (off site) TAPPaaS systems
• In case of TAPPaaS deployment in High Availability then the HA mirror will add another backup copy
• We need to find a solution for backing up the PVE nodes them self, and any data that we store outside containers.
• We need to give special consideration to encryption keys

We will consider znapzend, used to snapshot and replicate zfs volumes across servers

AI Stack¶

Productivity Stack¶

Home Stack¶

Small Community (variation of HOME)¶

Productivity Stack¶

Software Development Stack¶