<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Storage on Virtualthoughts</title><link>http://virtualthoughts.co.uk/categories/storage/</link><description>Recent content in Storage on Virtualthoughts</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Mon, 05 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="http://virtualthoughts.co.uk/categories/storage/index.xml" rel="self" type="application/rss+xml"/><item><title>Replicating my vSphere network configuration in Openshift Virtualisation</title><link>http://virtualthoughts.co.uk/2024/02/05/replicating-my-vsphere-network-configuration-in-openshift-virtualisation/</link><pubDate>Mon, 05 Feb 2024 00:00:00 +0000</pubDate><guid>http://virtualthoughts.co.uk/2024/02/05/replicating-my-vsphere-network-configuration-in-openshift-virtualisation/</guid><description>&lt;p&gt;&lt;a href="https://www.redhat.com/en/technologies/cloud-computing/openshift/virtualization"&gt;Red Hat Openshift Virtualisation&lt;/a&gt; provides a platform for running and managing Virtual Machines alongside Containers using a consistent API. It also provides a mechanism for migrating VMs from platforms such as vSphere.&lt;/p&gt;
&lt;p&gt;As I have both environments, I wanted to deploy an Openshift Virtualisation setup that mimics my current vSphere setup so I could migrate Virtual Machines to it.&lt;/p&gt;
&lt;h2 id="existing-vsphere-design"&gt;Existing vSphere Design&lt;/h2&gt;
&lt;p&gt;Below is a diagram depicting my current vSphere setup. My ESXi hosts are dual-homed with a separation of management (vmkernel) and virtual machine traffic.&lt;/p&gt;</description></item><item><title>Homelab Networking Refresh</title><link>http://virtualthoughts.co.uk/2017/12/18/homelab-networking-refresh/</link><pubDate>Mon, 18 Dec 2017 00:00:00 +0000</pubDate><guid>http://virtualthoughts.co.uk/2017/12/18/homelab-networking-refresh/</guid><description>&lt;h1 id="adios-netgear-router"&gt;Adios, Netgear router&lt;/h1&gt;
&lt;p&gt;In hindsight, I shouldn&amp;rsquo;t have bought a Netgear D7000 router. The reviews were good but after about 6 months of ownership, it decided to exhibit some pretty awful symptoms. One of which was completely and indiscriminately drop all wireless clients regardless of device type, range, band or frequency it resided on. A reconnect to the wireless network would prompt the passphrase again, weirdly. Even after putting in the passphrase (again) it wouldn&amp;rsquo;t connect. The &lt;strong&gt;only&lt;/strong&gt; way to rectify this was to physically reboot the router.&lt;/p&gt;</description></item><item><title>VMware Cloud on AWS</title><link>http://virtualthoughts.co.uk/2017/11/24/vmware-cloud-on-aws/</link><pubDate>Fri, 24 Nov 2017 00:00:00 +0000</pubDate><guid>http://virtualthoughts.co.uk/2017/11/24/vmware-cloud-on-aws/</guid><description>&lt;p&gt;Perhaps one of VMware’s most significant announcements made in recent times is the partnership with Amazon Web Services (AWS), including the ability to leverage AWS’s infrastructure to provision vSphere managed resources. What exactly does this mean and what benefits could this bring to the enterprise?&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h1 id="collaboration-of-two-giants"&gt;&lt;strong&gt;Collaboration of Two Giants&lt;/strong&gt;&lt;/h1&gt;
&lt;p&gt;To understand and appreciate the significance of this partnership we must acknowledge the position and perspective of each.&lt;/p&gt;
&lt;p&gt;&lt;img src="images/vmware.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Market leader in private cloud offerings&lt;/li&gt;
&lt;li&gt;Deep roots and history in virtualisation&lt;/li&gt;
&lt;li&gt;Expanding portfolio&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src="images/amazon-300x131.png" alt=""&gt;&lt;/p&gt;</description></item><item><title>Intel Skylake/Kaby Lake processors: broken hyper-threading</title><link>http://virtualthoughts.co.uk/2017/06/26/intel-skylakekaby-lake-processors-broken-hyper-threading/</link><pubDate>Mon, 26 Jun 2017 00:00:00 +0000</pubDate><guid>http://virtualthoughts.co.uk/2017/06/26/intel-skylakekaby-lake-processors-broken-hyper-threading/</guid><description>&lt;h1 id="overview"&gt;Overview&lt;/h1&gt;
&lt;p&gt;Source : &lt;a href="https://lists.debian.org/debian-devel/2017/06/msg00308.html"&gt;https://lists.debian.org/debian-devel/2017/06/msg00308.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It appears some Intel Xeon CPU&amp;rsquo;s are susceptible to a recently discovered Hyper Threading bug. However, these are limited to E3 v5/v6 based Xeon systems which are found mostly in entry level servers with &lt;strong&gt;single socket&lt;/strong&gt; implementations. &amp;gt; Dual socket systems currently leverage E5 based Xeons which don&amp;rsquo;t appear to be affected.&lt;/p&gt;
&lt;p&gt;Currently, the easiest way to mitigate against this bug is to simply disable hyper-threading. The bug also appears to be OS agnostic.&lt;/p&gt;</description></item><item><title>Homelab v2 - Part 1</title><link>http://virtualthoughts.co.uk/2017/05/19/homelab-v2-part1/</link><pubDate>Fri, 19 May 2017 00:00:00 +0000</pubDate><guid>http://virtualthoughts.co.uk/2017/05/19/homelab-v2-part1/</guid><description>&lt;h1 id="out-with-the-old"&gt;Out with the old&lt;/h1&gt;
&lt;p&gt;My previous homelab, although functional was starting to hit the limits of 32GB of RAM, particularly when running vCenter, vSAN, NSX, etc concurrently.&lt;/p&gt;
&lt;p&gt;A family member had use for my old lab so I decided to sell it and get a replacement whitebox.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h1 id="requirements"&gt;Requirements&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Quiet&lt;/strong&gt; - As this would live in my office and powered on pretty much 24/7 it need a silent running machine&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Power efficient&lt;/strong&gt; - I&amp;rsquo;d rather not rack up the electric bill.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;64GB Ram Support&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt; &lt;/p&gt;</description></item><item><title>Achievement Unlocked : Dell Compellent Certified Deployment Professional</title><link>http://virtualthoughts.co.uk/2016/08/11/achievement-unlocked-dell-compellent-certified-deployment-professional/</link><pubDate>Thu, 11 Aug 2016 00:00:00 +0000</pubDate><guid>http://virtualthoughts.co.uk/2016/08/11/achievement-unlocked-dell-compellent-certified-deployment-professional/</guid><description>&lt;p&gt;I&amp;rsquo;ve only recently started focusing more on developing my storage skills which I personally believe to be a good complement to my existing VMware knowledge. I&amp;rsquo;ve been working with Compellent systems for a few months now and thought it was a good time to get officially certified.&lt;/p&gt;
&lt;p&gt;The exam itself put me a little out of my comfort zone, as in the past my storage level knowledge was limited to administrator level on EqualLogic setups. This exam was tough but rewarding.&lt;/p&gt;</description></item><item><title>An introduction to vSphere Metro Storage Cluster with Compellent Live Volume</title><link>http://virtualthoughts.co.uk/2016/06/16/an-introduction-to-vsphere-metro-storage-cluster-with-compellent-live-volume/</link><pubDate>Thu, 16 Jun 2016 00:00:00 +0000</pubDate><guid>http://virtualthoughts.co.uk/2016/06/16/an-introduction-to-vsphere-metro-storage-cluster-with-compellent-live-volume/</guid><description>&lt;h1 id="intro"&gt;Intro&lt;/h1&gt;
&lt;p&gt;VMware vSphere Metro Storage Cluster is a suite of infrastructure configurations that facilitate a stretched cluster setup. It&amp;rsquo;s not a feature like HA/DRS that we can switch on easily; it requires architectural design decisions that specifically contribute to this configuration. The foundation of which are &lt;em&gt;&lt;strong&gt;stretched clusters&lt;/strong&gt;&lt;/em&gt; and with regards to the Compellent suite of solutions &lt;em&gt;&lt;strong&gt;Live Volume&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h1 id="stretched-cluster"&gt;Stretched Cluster&lt;/h1&gt;
&lt;p&gt;Stretched clusters are pretty much self explanatory. In comparison to a lot of configurations where compute clusters reside within the same physical room, stretched clusters spread the compute capacity over more than one physical location. This can still be internally (different server rooms within the same building) or further apart over geographically disperse sites.&lt;/p&gt;</description></item></channel></rss>