<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Openvz on Daniel Pomfret</title>
    <link>https://pomfret.uk/tags/openvz/</link>
    <description>Recent content in Openvz on Daniel Pomfret</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© Daniel Pomfret</copyright>
    <lastBuildDate>Tue, 19 Dec 2017 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pomfret.uk/tags/openvz/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenVZ - Hostnames &amp; Systemd (ovzhostname.service)</title>
      <link>https://pomfret.uk/posts/openvz-hostnames-systemd-ovzhostname-service/</link>
      <pubDate>Tue, 19 Dec 2017 00:00:00 +0000</pubDate>
      <guid>https://pomfret.uk/posts/openvz-hostnames-systemd-ovzhostname-service/</guid>
      <description>&lt;h2 id=&#34;the-problem&#34;&gt;The problem?&lt;/h2&gt;&#xA;&lt;p&gt;For weeks, I&amp;rsquo;ve been battling with an issue with a new CentOS 7 template for cPanel and Plesk, I built for the OpenVZ hypervisor. Even when setting the &lt;code&gt;HOSTNAME=&amp;lt;hostname&amp;gt;&lt;/code&gt; in the &lt;code&gt;/etc/vz/&amp;lt;CTID&amp;gt;.conf&lt;/code&gt; the container still rebooted with the hostname which was used when the template was created. Meaning the new and correct hostname would never be remembered. Causing various issues with BIND, Apache etc.&lt;/p&gt;&#xA;&lt;p&gt;Even trying to set the hostname with the following failed!&lt;/p&gt;</description>
    </item>
    <item>
      <title>OpenVZ IO Limits</title>
      <link>https://pomfret.uk/posts/openvz-io-limits/</link>
      <pubDate>Wed, 12 Oct 2016 00:00:00 +0000</pubDate>
      <guid>https://pomfret.uk/posts/openvz-io-limits/</guid>
      <description>&lt;p&gt;OpenVZ has had IO limits for years, but I&amp;rsquo;ve never really had opportunity to implement them, especially with SSD disks becoming cheaper and the standard.&lt;/p&gt;&#xA;&lt;p&gt;However in some cases implementing IO Limits on your OpenVZ VMs can be a good practice. Especially on Database servers (High usage MySQL/MariaDB) or Mail servers (Exim on cPanel can be an IO hog at times).&lt;/p&gt;&#xA;&lt;p&gt;Depending on your disks, and how many OpenVZ containers live on your host, you may wish to adjust the following to better suited values.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
