#cluster — Public Fediverse posts

ESP32S3 cluster running 1.58-bit (BitNet) Language model

https://github.com/Low-Zi-Hong/ESP32s3-LLM-Cluster

Comments: https://news.ycombinator.com/item?id=49884625

#HackerNews #ESP32S3 #BitNet #AI #LanguageModel #Cluster #Technology

ESP32S3 cluster running 1.58-bit (BitNet) Language model

https://github.com/Low-Zi-Hong/ESP32s3-LLM-Cluster

Comments: https://news.ycombinator.com/item?id=49884625

#HackerNews #ESP32S3 #BitNet #AI #LanguageModel #Cluster #Technology

ESP32S3 cluster running 1.58-bit (BitNet) Language model

https://github.com/Low-Zi-Hong/ESP32s3-LLM-Cluster

Comments: https://news.ycombinator.com/item?id=49884625

#HackerNews #ESP32S3 #BitNet #AI #LanguageModel #Cluster #Technology

ESP32S3 cluster running 1.58-bit (BitNet) Language model

https://github.com/Low-Zi-Hong/ESP32s3-LLM-Cluster

Comments: https://news.ycombinator.com/item?id=49884625

#HackerNews #ESP32S3 #BitNet #AI #LanguageModel #Cluster #Technology

ESP32S3 cluster running 1.58-bit (BitNet) Language model

https://github.com/Low-Zi-Hong/ESP32s3-LLM-Cluster

Comments: https://news.ycombinator.com/item?id=49884625

#HackerNews #ESP32S3 #BitNet #AI #LanguageModel #Cluster #Technology

[Blog Archive] How to create a #Proxmox Two-Node #cluster

If a Proxmox Two-Node cluster is configured without a third node, you may face issues in case one node fails or the cluster enters a split-brain scenario.

As a best practice, even a Two-Node cluster requires a third node to act as quorum. This can be easily achieved by using an additional computer with the corosync-qnetd http://rviv.ly/wDAmiF #twonode

[Blog Archive] How to configure the Veeam High Availability #Cluster - pt.1

Veeam #Backup & Replication v13 introduces the High Availability Cluster, which allows you to keep the backup infrastructure alive in case one Backup #Server fails.

Before proceeding with the configuration, it is important to be aware of the limitations of the HA cluster.

 
Blog series http://rviv.ly/e3Z6OI #highavailability

[Blog Archive] How to configure the Veeam High Availability #Cluster - pt.1

Veeam #Backup & Replication v13 introduces the High Availability Cluster, which allows you to keep the backup infrastructure alive in case one Backup #Server fails.

Before proceeding with the configuration, it is important to be aware of the limitations of the HA cluster.

 
Blog series http://rviv.ly/e3Z6OI #highavailability

[Blog Archive] How to create a #Proxmox Two-Node #cluster

If a Proxmox Two-Node cluster is configured without a third node, you may face issues in case one node fails or the cluster enters a split-brain scenario.

As a best practice, even a Two-Node cluster requires a third node to act as quorum. This can be easily achieved by using an additional computer with the corosync-qnetd http://rviv.ly/wDAmiF #twonode

[Blog Archive] Veeam High Availability Cluster: #switchover and #disassemble - pt.3

When a Veeam High Availability #Cluster is created, several tasks are available to maintain correct functionality, such as switchover and disassemble.

Depending on the maintenance typology you need to perform on your HA Cluster, every operation is safe and doesn't impact on the service functionality.

  http://rviv.ly/ZiDKH8