<?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>Tfd12 on The IT Hollow</title>
    <link>https://theithollow.com/tags/tfd12/</link>
    <description>Recent content in Tfd12 on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Jan 2017 15:00:51 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/tfd12/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Capabilities are Needed for a Startup Storage Company?</title>
      <link>https://theithollow.com/2017/01/10/capabilities-needed-startup-storage-company/</link>
      <pubDate>Tue, 10 Jan 2017 15:00:51 +0000</pubDate>
      <guid>https://theithollow.com/2017/01/10/capabilities-needed-startup-storage-company/</guid>
      <description>&lt;p&gt;At this point I assume everyone is tired of hearing about storage arrays. They seem to have saturated the market to the point where the new storage companies have all but evaporated, or got bought by a larger company. Couple that with a focus on moving to public clouds and the storage array seems to have been beaten to death.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://assets.theithollow.com/wp-content/uploads/2017/01/storage-os-logo.png&#34;&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://assets.theithollow.com/wp-content/uploads/2017/01/storage-os-logo-300x64.png&#34;&gt;&lt;/a&gt; While I was at &lt;a href=&#34;http://techfieldday.com/event/tfd12/&#34;&gt;Tech Field Day 12&lt;/a&gt; I had the opportunity to see the folks over at StorageOS present on their fancy new storage solution. I was fully prepared to be lulled to sleep with another storage device but StorageOS had an interesting new take on the storage array. Their solution is to use containers to provide a global namespace to a clustered file system. Having a lightweight 40MB container acting as a controller for your virtual storage array could be an interesting topic all by itself. Off of the top of my head the use cases would include:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Is Everything Pay-as-You-Go?</title>
      <link>https://theithollow.com/2016/12/12/everything-pay-go/</link>
      <pubDate>Mon, 12 Dec 2016 15:05:29 +0000</pubDate>
      <guid>https://theithollow.com/2016/12/12/everything-pay-go/</guid>
      <description>&lt;p&gt;A recent vendor product briefing during &lt;a href=&#34;http://techfieldday.com/event/tfd12/&#34;&gt;Tech Field Day 12&lt;/a&gt; got me thinking about the term &amp;ldquo;pay-as-you-go&amp;rdquo;. In my line of work, I talk about public cloud a decent amount and maybe I take pay-as-you-go for granted. When I think about this term it means that as soon as I&amp;rsquo;m done with a resource, I can destroy it and no longer have to pay for it anymore. It also means that I can scale when I need to and just start paying for the new resources as I start consuming them.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Decouple Disks and Compute with DriveScale</title>
      <link>https://theithollow.com/2016/12/05/decouple-disks-compute-drivescale/</link>
      <pubDate>Mon, 05 Dec 2016 15:05:15 +0000</pubDate>
      <guid>https://theithollow.com/2016/12/05/decouple-disks-compute-drivescale/</guid>
      <description>&lt;p&gt;I was pretty unsure of the value proposition from &lt;a href=&#34;https://www.drivescale.com/&#34;&gt;DriveScale&lt;/a&gt; in the weeks preceding &lt;a href=&#34;http://techfieldday.com/events/tfd12&#34;&gt;Tech Field Day 12&lt;/a&gt;. Maybe the reason is because I&amp;rsquo;m not a Hadoop expert by any means. They have a pretty interesting idea though, so I wanted to make sure others were clear about what their solution was capable of.&lt;/p&gt;
&lt;p&gt;In a virtualized world, we&amp;rsquo;re pretty familiar with decoupling disks from our storage. It&amp;rsquo;s done via storage arrays that present iSCSI, Fibre Channel, NFS or whatever. Once we&amp;rsquo;ve presented a pool of disks to our hypervisor, we can carve up small virtual disks to be used with our virtual machines. In a Hadoop world, we want to have direct access to our drives so that HDFS can manage the storage. For this, we usually have rack mounted pizza box type servers with a certain amount of storage in them and then we can add multiples of them to form a cluster. &lt;a href=&#34;https://www.drivescale.com/&#34;&gt;DriveScale&lt;/a&gt; wanted to give HDFS some extra flexibility by allowing a pool of disks to be added, or removed to our servers.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Throw Your Isilon in the Data Lake</title>
      <link>https://theithollow.com/2016/11/16/throw-isilon-data-lake/</link>
      <pubDate>Wed, 16 Nov 2016 18:10:59 +0000</pubDate>
      <guid>https://theithollow.com/2016/11/16/throw-isilon-data-lake/</guid>
      <description>&lt;p&gt;Customers have a ton of requirements around log aggregation, file shares, media streaming repositories, and just a simple place to store objects. It can be difficult to manage all of these different use cases but &lt;a href=&#34;http://www.emc.com/en-us/storage/isilon/index.htm&#34;&gt;Dell EMC Isilon&lt;/a&gt; might just be the solution that can help to manage these requirements. Many times customers have several small islands of storage used for different purposes. Maybe this is because of a brand new requirement like &amp;ldquo;all security camera data will be stored for seven years&amp;rdquo;, which might require some additional storage space. Whatever the reason, companies many times will have small islands of storage, possibly even from different storage companies. This can become tough to manage and require more storage administrators with differing skill sets.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
