Write your own selinux module with audit2allow.
I’m not at work so I can’t find the guides I use but this looks similar https://danwalsh.livejournal.com/24750.html
Myself over NFS can have serious latency issues. Some software can’t correctly file lock over NFS too which will cause write latency or just full blown errors.
iSCSI drops however can be really really bad and cause full filesystem corruption. Also backing up iSCSI volumes can be tricky. Software will likely work better and feel happy however and underlying issues may be masked until they’re unfixable. (I had an iSCSI volume attached to vmware silently corrupt for months before it failed and lost the data even though all scrubs/checksums were good until the very least moment).
You can make your situations with with either technology, both are just as correct. Would get a touch more throughput on iSCSI simply down to the write confirmation being drive based and not filesystem locks / os based.
YMMV
DL380 G9. Those bioses don’t support booting from PCIe at all.
They actually do but it can only be a HPE supported BootROM… anything non-HPE is ignored (weirdly, some Intel and Broadcom cards PXE boot without the HPE firmware but not all).
Most of these boards have internal USB and internal SD slots which you can boot from with any media, intact HPE sell a USB SD card raid adaptor for the usb slot. So I would recommend using SD card for this…
I’m not sure about anything you’re running but I would look into certbot.
Either using the basic web plugin or DNS plugin. Nginx would be simpler, you’d just have to open your web ports on certificate generation to pass the challenge.
I know some proxy tools have let’s encrypt support, such as traefik.
You also have Teams for Linux which is compatible with Microsoft Teams (Work)but no longer supported. It however isn’t compatible with Microsoft Teams (Personal) but if you try to use Microsoft Teams on Linux for personal use, it tells you to install the now non-existant Teams for Linux that only works with Microsoft Teams (Work).
There’s also two different versions of logging out in Teams for Linux, Logout and Log Out. Both of which log you out but only one lets you log in as a different user.
Don’t get me started with the Microsoft Teams PWA that is now the “way to use Teams on Linux” but isn’t the Teams PWA that installs if you try the normal way…
All hail Microsoft Teams! At least I can stream the games I’m playing to my work meetings so people know I’m skiving.
Technically it is, as someone else mentioned, text is copied on federation, this means is you as an admin need to actively moderate instances you federate with that may cause you issues in a legal standpoint whether correct or not. Facebook etc have rights that means you’re not liable for user content, you as an individual instance admin however would need to fight for those rights.
Sure it’s a rubbish thing they did but I also understand it completely.
SQLite doesn’t like NFS, the file locking isn’t stable/fast enough so any latency in the storage can cause data loss, corruption or just slow things down.
However SQLite to MySQL is relatively peanuts, Postgres less so…
Still it’s a nice move for those that don’t run containers on a single host with local filesystems.
Ceph works best if you have identical osd, quantity, type and capacity across the cluster, also works best on a 3+ node cluster.
I ran a mixed sata SSD/HDD 256gb/4tb cluster and it was always a bit pants. Now I have 7x1tb SSD per node (4nodes) and it works fantastic now.
Proxmox uses replica 3/2 failure at host level but you may find that EC works better for your mixed infra as you noticed you can’t meed the 3 host failure and so setting to osd failure level means data may be kept on a single host so would need to traverse the network to the other machine.
You may also need more than a single 10Gb nic too as you might start hitting bandwidth issues.
This compose looks like it should work, I’m not at a pc to test but it’s near identical to my own; I would maybe change onlyoffice for collabra otherwise try this.
Op states they are using a Nas and server, so if NFS is being used you may need :Z on the end of any kind volume (or a non-NFS mount point if using podman/extended ACLS don’t work).
IPv6 doesn’t support NAT… Or am I woefully out of date.
But your home router will just firewall like it does already but you don’t have NAT as a simple fall back for “security”. It does make running internal services much easier as you no long need to port forward. So you can run two webservers on port 80 and they be bother allowed inbound without doing horrible load balance or NAT translation.
Looks like Three doesn’t block it…