Systems & Services - Revision history

Wikisailor: /* List of Services */

2026-04-07T14:42:11Z

List of Services

← Older revision		Revision as of 14:42, 7 April 2026
Line 72:		Line 72:

	There are to be at lest two Minecraft servers setup one with a vanilla Minecraft and another with ATM10		There are to be at lest two Minecraft servers setup one with a vanilla Minecraft and another with ATM10


			===[[Silvan Reporter]]===

			A Prolog based application that can monitor and report on the state of the silvan Proxmox cluster

Wikisailor: /* Perfomance monitoring */

2026-02-25T00:39:57Z

Perfomance monitoring

← Older revision		Revision as of 00:39, 25 February 2026
Line 31:		Line 31:

	'''Second Update''' All three VMs are to be decommissioned as now we have the new '''[[Unified Monitoring Stack]]''' on Mango that replaces the separate hosts for each service.		'''Second Update''' All three VMs are to be decommissioned as now we have the new '''[[Unified Monitoring Stack]]''' on Mango that replaces the separate hosts for each service.

			===[[Management kiosk]]===

			Following on from the performance monitoring we have also started with a '''[[Management kiosk]]''' so that all of the Virtual Machines and Services can be viewed from a single location. The first dashboard under trial will be '''[[Homelab Dashboard \|Dashy]]''' installed on Blackberry More information can be seen '''[[Management kiosk \| here]]'''

	===[[UpLoad Server \| File Import]]===		===[[UpLoad Server \| File Import]]===

Wikisailor: /* Perfomance monitoring */

2026-02-22T07:42:09Z

Perfomance monitoring

← Older revision		Revision as of 07:42, 22 February 2026
Line 29:		Line 29:

	'''Update We should merge these three in to one host VM at some point at the same time we should use Vitoria Metrics as the scrapper but remember to preserve the Prometheus yaml file as then we can use the existing agents'''		'''Update We should merge these three in to one host VM at some point at the same time we should use Vitoria Metrics as the scrapper but remember to preserve the Prometheus yaml file as then we can use the existing agents'''

			'''Second Update''' All three VMs are to be decommissioned as now we have the new '''[[Unified Monitoring Stack]]''' on Mango that replaces the separate hosts for each service.

	===[[UpLoad Server \| File Import]]===		===[[UpLoad Server \| File Import]]===

Wikisailor: /* Perfomance monitoring */

2026-02-21T05:09:19Z

Perfomance monitoring

← Older revision		Revision as of 05:09, 21 February 2026
Line 26:		Line 26:
	===[[Prometheus & Grafana \|Perfomance monitoring]]===		===[[Prometheus & Grafana \|Perfomance monitoring]]===

	There was a need to monitor how the health of the various VM so '''[[Prometheus & Grafana \| 🕯️Prometheus & 📈Grafana]]''' were installed to to VMs '''🍍[[Pineapple]]''' for '''🍍[[Pineapple \| 🕯️Prometheus install]]''' and '''🍈[[Granadilla]]''' for '''[[Granadilla \| 📈Grafana ]]'''. Long term storage of the health data is handled by '''🕰️[[Victoria Metrics]]''' on '''[[Victoria Metrics \| Victoria ]]'''. These three could have been merged on to one VM but at the moment they are all on separate VMs. It should be noted that the data that they provide is sensitive in that it is the health data for the entire suite of VMs so it can only be accessed from within the Proxmox management environment.		There was a need to monitor how the health of the various VM so '''[[Prometheus & Grafana \| 🕯️Prometheus & 📈Grafana]]''' were installed to to VMs '''🍍[[Pineapple]]''' for '''🍍[[Pineapple \| 🕯️Prometheus install]]''' and '''🍈[[Granadilla]]''' for '''[[Granadilla \| 📈Grafana ]]'''. Long term storage of the health data is handled by '''🕰️[[Victoria Metrics]]''' on '''[[Victoria Metrics \| Victoria ]]'''. These three could have been merged on to one VM but at the moment they are all on separate VMs. It should be noted that the data that they provide is sensitive in that it is the health data for the entire suite of VMs so it can only be accessed from within the Proxmox management environment. The plan to merge these three will be happening now with the new host Mango.

	'''Update We should merge these three in to one host VM at some point at the same time we should use Vitoria Metrics as the scrapper but remember to preserve the Prometheus yaml file as then we can use the existing agents'''		'''Update We should merge these three in to one host VM at some point at the same time we should use Vitoria Metrics as the scrapper but remember to preserve the Prometheus yaml file as then we can use the existing agents'''

Wikisailor: /* Perfomance monitoring */

2026-02-13T02:44:53Z

Perfomance monitoring

← Older revision		Revision as of 02:44, 13 February 2026
Line 26:		Line 26:
	===[[Prometheus & Grafana \|Perfomance monitoring]]===		===[[Prometheus & Grafana \|Perfomance monitoring]]===

	There was a need to monitor how the health of the various VM so '''[[Prometheus & Grafana \| 🕯️Prometheus & 📈Grafana]]''' were installed to to VMs '''🍍[[Pineapple]]''' for '''🍍[[Pineapple \| 🕯️Prometheus install]]''' and '''🍈[[Granadilla]]''' for '''[[Granadilla \| 📈Grafana ]]'''. Long term storage of the health data is handled by '''🕰️[[Victoria Metrics]]''' on '''[[Victoria Metrics \| Victoria ]]'''. ~~these~~ three could have been merged on to one VM but at the moment they are all on separate VMs. It should be noted that the data that they provide is sensitive in that it is the health data for the entire suite of VMs so it can only be accessed from within the Proxmox management environment.		There was a need to monitor how the health of the various VM so '''[[Prometheus & Grafana \| 🕯️Prometheus & 📈Grafana]]''' were installed to to VMs '''🍍[[Pineapple]]''' for '''🍍[[Pineapple \| 🕯️Prometheus install]]''' and '''🍈[[Granadilla]]''' for '''[[Granadilla \| 📈Grafana ]]'''. Long term storage of the health data is handled by '''🕰️[[Victoria Metrics]]''' on '''[[Victoria Metrics \| Victoria ]]'''. These three could have been merged on to one VM but at the moment they are all on separate VMs. It should be noted that the data that they provide is sensitive in that it is the health data for the entire suite of VMs so it can only be accessed from within the Proxmox management environment.

	'''Update We should merge these three in to one host VM at some point at the same time we should use Vitoria Metrics as the scrapper but remember to preserve the Prometheus yaml file as then we can use the existing agents'''		'''Update We should merge these three in to one host VM at some point at the same time we should use Vitoria Metrics as the scrapper but remember to preserve the Prometheus yaml file as then we can use the existing agents'''

Wikisailor: /* Perfomance monitoring */

2026-02-13T02:43:39Z

Perfomance monitoring

← Older revision		Revision as of 02:43, 13 February 2026
Line 26:		Line 26:
	===[[Prometheus & Grafana \|Perfomance monitoring]]===		===[[Prometheus & Grafana \|Perfomance monitoring]]===

	There was a need to monitor how the health of the various VM so '''[[Prometheus & Grafana \| 🕯️Prometheus & 📈Grafana]]''' were installed to to VMs '''🍍[[Pineapple]]''' for '''🍍[[Pineapple \| 🕯️Prometheus install]]''' and '''🍈[[Granadilla]]''' for '''[[Granadilla \| 📈Grafana ]]'''. Long term storage of the health data is handled by '''🕰️[[Victoria Metrics]]''' on '''[[Victoria Metrics \| Victoria ]]'''. these three could have been merged on to one VM but at the moment they are all on separate VMs. It should be noted that the data that they provide is sensitive in that it is the health data for the entire suite of VMs so it can only be accessed from within the Proxmox management environment.		There was a need to monitor how the health of the various VM so '''[[Prometheus & Grafana \| 🕯️Prometheus & 📈Grafana]]''' were installed to to VMs '''🍍[[Pineapple]]''' for '''🍍[[Pineapple \| 🕯️Prometheus install]]''' and '''🍈[[Granadilla]]''' for '''[[Granadilla \| 📈Grafana ]]'''. Long term storage of the health data is handled by '''🕰️[[Victoria Metrics]]''' on '''[[Victoria Metrics \| Victoria ]]'''. these three could have been merged on to one VM but at the moment they are all on separate VMs. It should be noted that the data that they provide is sensitive in that it is the health data for the entire suite of VMs so it can only be accessed from within the Proxmox management environment.

			'''Update We should merge these three in to one host VM at some point at the same time we should use Vitoria Metrics as the scrapper but remember to preserve the Prometheus yaml file as then we can use the existing agents'''

	===[[UpLoad Server \| File Import]]===		===[[UpLoad Server \| File Import]]===

Wikisailor: /* Data Archive */

2026-02-09T11:08:05Z

Data Archive

← Older revision		Revision as of 11:08, 9 February 2026
Line 42:		Line 42:
	===[[Data Archive]]===		===[[Data Archive]]===

	The Main [[Data Archive]] is another VM hostname '''[[Data Archive\| Blackberry]]''' has a '''[[The Kiwix Archive]]''' docker application that will serve as an encyclopaedia with a load of ZIMs. There is also a 🕸️[[The Web Archive (ArchiveBox)]] on the same VM. To enable some automation to be linked the is a N8N application as well. We did have [[OpenAlex]] in this space but it has been moved to VM Tayberry on Kiwi as it proved to be too much of a resource drain and would not have been able to index or serve anything like the full set of papers, it is not certain that it will be able to run satisfactorily on kiwi if not it will be disabled and left until there is more ram available.		The Main [[Data Archive]] is another VM hostname '''[[Data Archive\| Blackberry]]''' has a '''[[The Kiwix Archive]]''' docker application that will serve as an encyclopaedia with a load of ZIMs. There is also a 🕸️[[The Web Archive (ArchiveBox)]] on the same VM. To enable some automation to be linked the is a N8N application as well. We did have '''[[OpenAlex]]''' in this space but it has been moved to VM Tayberry on Kiwi as it proved to be too much of a resource drain and would not have been able to index or serve anything like the full set of papers, it is not certain that it will be able to run satisfactorily on kiwi if not it will be disabled and left until there is more ram available.
	{\| class="wikitable"		{\| class="wikitable"
	\|+ Dashboards		\|+ Dashboards

Wikisailor: /* AI and Jellyfin Docker */

2026-02-09T10:32:43Z

AI and Jellyfin Docker

← Older revision		Revision as of 10:32, 9 February 2026
Line 36:		Line 36:
	The original nameserver was a VM called ns1. It was decided to scrap that VM and use a LXC for DNS within the homelab so the new '''[[Nameserver]]''' is '''[[Nameserver \| ctns1]]'''. As all that was required of the namserver was to keep the internal hosts organised with the local IP addresses and have a DNS cache we use DNSmasq. To make the '''[[Add a Hostname & IP Address to DNSmsaq \| admin of the domain names]]''' simple and consistent there are a few simple scripts to add, delete and list the DNS entries written by Gemini, they work well enough and more importantly they are all consistent with no typos. Since then we have added another nameserver outside of Proxmox with Adguard installed. The new '''[[Nameserver \| Adguard]]''' is still DNSmasq under the hood but it has a nice web interface in place of the basic shell of '''[[Nameserver \| ctns1]]'''. To make '''[[Nameserver \| ctns1]]''' filter the same set of adverts it has the Adguard IP address as the upstream DNS.		The original nameserver was a VM called ns1. It was decided to scrap that VM and use a LXC for DNS within the homelab so the new '''[[Nameserver]]''' is '''[[Nameserver \| ctns1]]'''. As all that was required of the namserver was to keep the internal hosts organised with the local IP addresses and have a DNS cache we use DNSmasq. To make the '''[[Add a Hostname & IP Address to DNSmsaq \| admin of the domain names]]''' simple and consistent there are a few simple scripts to add, delete and list the DNS entries written by Gemini, they work well enough and more importantly they are all consistent with no typos. Since then we have added another nameserver outside of Proxmox with Adguard installed. The new '''[[Nameserver \| Adguard]]''' is still DNSmasq under the hood but it has a nice web interface in place of the basic shell of '''[[Nameserver \| ctns1]]'''. To make '''[[Nameserver \| ctns1]]''' filter the same set of adverts it has the Adguard IP address as the upstream DNS.

	===[[Docker ~~Hosts~~ \|AI and Jellyfin Docker]]===		===[[Linux Docker And GPU Passthrough \|AI and Jellyfin Docker]]===

	We have a few VMs that have docker. '''[[Docker Hosts \| Quince]]''' has the 5060ti passed through to it so it is running the docker apps that benefit from the GPU eg AI and Jellyfin.		We have a few VMs that have docker. '''[[Docker Hosts \| Quince]]''' has the 5060ti passed through to it so it is running the docker apps that benefit from the GPU eg AI and Jellyfin.

Wikisailor: /* AI and Jellyfin Docker */

2026-02-09T10:21:43Z

AI and Jellyfin Docker

← Older revision		Revision as of 10:21, 9 February 2026
Line 36:		Line 36:
	The original nameserver was a VM called ns1. It was decided to scrap that VM and use a LXC for DNS within the homelab so the new '''[[Nameserver]]''' is '''[[Nameserver \| ctns1]]'''. As all that was required of the namserver was to keep the internal hosts organised with the local IP addresses and have a DNS cache we use DNSmasq. To make the '''[[Add a Hostname & IP Address to DNSmsaq \| admin of the domain names]]''' simple and consistent there are a few simple scripts to add, delete and list the DNS entries written by Gemini, they work well enough and more importantly they are all consistent with no typos. Since then we have added another nameserver outside of Proxmox with Adguard installed. The new '''[[Nameserver \| Adguard]]''' is still DNSmasq under the hood but it has a nice web interface in place of the basic shell of '''[[Nameserver \| ctns1]]'''. To make '''[[Nameserver \| ctns1]]''' filter the same set of adverts it has the Adguard IP address as the upstream DNS.		The original nameserver was a VM called ns1. It was decided to scrap that VM and use a LXC for DNS within the homelab so the new '''[[Nameserver]]''' is '''[[Nameserver \| ctns1]]'''. As all that was required of the namserver was to keep the internal hosts organised with the local IP addresses and have a DNS cache we use DNSmasq. To make the '''[[Add a Hostname & IP Address to DNSmsaq \| admin of the domain names]]''' simple and consistent there are a few simple scripts to add, delete and list the DNS entries written by Gemini, they work well enough and more importantly they are all consistent with no typos. Since then we have added another nameserver outside of Proxmox with Adguard installed. The new '''[[Nameserver \| Adguard]]''' is still DNSmasq under the hood but it has a nice web interface in place of the basic shell of '''[[Nameserver \| ctns1]]'''. To make '''[[Nameserver \| ctns1]]''' filter the same set of adverts it has the Adguard IP address as the upstream DNS.

	===AI and Jellyfin Docker===		===[[Docker Hosts \|AI and Jellyfin Docker]]===

	We have a few VMs that have docker. '''[[Docker Hosts \| Quince]]''' has the 5060ti passed through to it so it is running the docker apps that benefit from the GPU eg AI and Jellyfin.		We have a few VMs that have docker. '''[[Docker Hosts \| Quince]]''' has the 5060ti passed through to it so it is running the docker apps that benefit from the GPU eg AI and Jellyfin.

Wikisailor: /* Data Archive */

2026-02-09T09:20:42Z

Data Archive

← Older revision		Revision as of 09:20, 9 February 2026
Line 58:		Line 58:
	\|http://blackberry:8080 \|\| ArchiveBox \|\| Personal Web Archive		\|http://blackberry:8080 \|\| ArchiveBox \|\| Personal Web Archive
	\|-		\|-
	\|http://tarberry:5601 \|\| Opensearch \|\|		\|http://tarberry:5601 \|\| Opensearch \|\| Massive, open-source index of the world's scholarly research
	\|}		\|}

← Older revision		Revision as of 02:43, 13 February 2026
Line 26:		Line 26:
	===[[Prometheus & Grafana \|Perfomance monitoring]]===		===[[Prometheus & Grafana \|Perfomance monitoring]]===

	There was a need to monitor how the health of the various VM so '''[[Prometheus & Grafana \| 🕯️Prometheus & 📈Grafana]]''' were installed to to VMs '''🍍[[Pineapple]]''' for '''🍍[[Pineapple \| 🕯️Prometheus install]]''' and '''🍈[[Granadilla]]''' for '''[[Granadilla \| 📈Grafana ]]'''. Long term storage of the health data is handled by '''🕰️[[Victoria Metrics]]''' on '''[[Victoria Metrics \| Victoria ]]'''. these three could have been merged on to one VM but at the moment they are all on separate VMs. It should be noted that the data that they provide is sensitive in that it is the health data for the entire suite of VMs so it can only be accessed from within the Proxmox management environment.		There was a need to monitor how the health of the various VM so '''[[Prometheus & Grafana \| 🕯️Prometheus & 📈Grafana]]''' were installed to to VMs '''🍍[[Pineapple]]''' for '''🍍[[Pineapple \| 🕯️Prometheus install]]''' and '''🍈[[Granadilla]]''' for '''[[Granadilla \| 📈Grafana ]]'''. Long term storage of the health data is handled by '''🕰️[[Victoria Metrics]]''' on '''[[Victoria Metrics \| Victoria ]]'''. these three could have been merged on to one VM but at the moment they are all on separate VMs. It should be noted that the data that they provide is sensitive in that it is the health data for the entire suite of VMs so it can only be accessed from within the Proxmox management environment.

			'''Update We should merge these three in to one host VM at some point at the same time we should use Vitoria Metrics as the scrapper but remember to preserve the Prometheus yaml file as then we can use the existing agents'''

	===[[UpLoad Server \| File Import]]===		===[[UpLoad Server \| File Import]]===

← Older revision		Revision as of 10:32, 9 February 2026
Line 36:		Line 36:
	The original nameserver was a VM called ns1. It was decided to scrap that VM and use a LXC for DNS within the homelab so the new '''[[Nameserver]]''' is '''[[Nameserver \| ctns1]]'''. As all that was required of the namserver was to keep the internal hosts organised with the local IP addresses and have a DNS cache we use DNSmasq. To make the '''[[Add a Hostname & IP Address to DNSmsaq \| admin of the domain names]]''' simple and consistent there are a few simple scripts to add, delete and list the DNS entries written by Gemini, they work well enough and more importantly they are all consistent with no typos. Since then we have added another nameserver outside of Proxmox with Adguard installed. The new '''[[Nameserver \| Adguard]]''' is still DNSmasq under the hood but it has a nice web interface in place of the basic shell of '''[[Nameserver \| ctns1]]'''. To make '''[[Nameserver \| ctns1]]''' filter the same set of adverts it has the Adguard IP address as the upstream DNS.		The original nameserver was a VM called ns1. It was decided to scrap that VM and use a LXC for DNS within the homelab so the new '''[[Nameserver]]''' is '''[[Nameserver \| ctns1]]'''. As all that was required of the namserver was to keep the internal hosts organised with the local IP addresses and have a DNS cache we use DNSmasq. To make the '''[[Add a Hostname & IP Address to DNSmsaq \| admin of the domain names]]''' simple and consistent there are a few simple scripts to add, delete and list the DNS entries written by Gemini, they work well enough and more importantly they are all consistent with no typos. Since then we have added another nameserver outside of Proxmox with Adguard installed. The new '''[[Nameserver \| Adguard]]''' is still DNSmasq under the hood but it has a nice web interface in place of the basic shell of '''[[Nameserver \| ctns1]]'''. To make '''[[Nameserver \| ctns1]]''' filter the same set of adverts it has the Adguard IP address as the upstream DNS.

	===[[Docker ~~Hosts~~ \|AI and Jellyfin Docker]]===		===[[Linux Docker And GPU Passthrough \|AI and Jellyfin Docker]]===

	We have a few VMs that have docker. '''[[Docker Hosts \| Quince]]''' has the 5060ti passed through to it so it is running the docker apps that benefit from the GPU eg AI and Jellyfin.		We have a few VMs that have docker. '''[[Docker Hosts \| Quince]]''' has the 5060ti passed through to it so it is running the docker apps that benefit from the GPU eg AI and Jellyfin.