<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Virtualization on Rickelobe.com</title>
    <link>https://rickelobe.com/tags/virtualization/</link>
    <description>Recent content in Virtualization on Rickelobe.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Dec 2019 16:15:00 -0500</lastBuildDate>
    <atom:link href="https://rickelobe.com/tags/virtualization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Two Node Proxmox Cluster with High Availability</title>
      <link>https://rickelobe.com/posts/2019-12-04-two-node-proxmox-cluster-with-high-availability/</link>
      <pubDate>Wed, 04 Dec 2019 16:15:00 -0500</pubDate>
      <guid>https://rickelobe.com/posts/2019-12-04-two-node-proxmox-cluster-with-high-availability/</guid>
      <description>&lt;p&gt;I was recently tasked with creating a small deployment to host a single virtual machine at a customer site. The purpose of the virtual machine was to provide us with remote access to a specific customer resource that was otherwise unavailable to us. The deployment consisted of two physical machines running as Proxmox hypervisors (node-1 and node-2) hosting a single virtual machine. The virtual machine was configured to be replicated from node-1 over to node-2 every 5 or 10 minutes and was added as a HA resource. Side note: in order for replication to work, you need a ZFS filesystem. If you instead are using shared storage, replication is not needed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
