<?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 Shane Cunningham</title><link>https://cunninghamshane.com/tags/storage/</link><description>Recent content in Storage on Shane Cunningham</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 13 Mar 2015 09:43:35 +0000</lastBuildDate><atom:link href="https://cunninghamshane.com/tags/storage/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenStack Swift and Cyberduck</title><link>https://cunninghamshane.com/posts/openstack-swift-and-cyberduck/</link><pubDate>Fri, 13 Mar 2015 09:43:35 +0000</pubDate><guid>https://cunninghamshane.com/posts/openstack-swift-and-cyberduck/</guid><description>&lt;p&gt;Just a couple notes. I recently added a &lt;a href="https://wiki.openstack.org/wiki/Swift"&gt;Swift&lt;/a&gt; node to my OpenStack deployment in my closet. For some reason I kept wanting to point Cyberduck to the infra1_swift_proxy_container at port 8080. Instead, you want to point it to port 5000 for Keystone auth, duh. By default SSL is not enabled in Swift so you can download the HTTP OpenStack profile &lt;a href="https://svn.cyberduck.ch/trunk/profiles/Openstack%20Swift%20(HTTP).cyberduckprofile"&gt;OpenstackSwift(HTTP).cyberduckprofile&lt;/a&gt;. &amp;ldquo;Username:&amp;rdquo; in Cyberduck wants tenant:user, so out of the box you could use admin:admin, and the &amp;ldquo;Secret Key&amp;rdquo; would be the admin users password.&lt;/p&gt;</description></item><item><title>Migrating Cinder volumes to Icehouse</title><link>https://cunninghamshane.com/posts/migrating-cinder-volumes-to-icehouse/</link><pubDate>Fri, 09 May 2014 07:20:18 +0000</pubDate><guid>https://cunninghamshane.com/posts/migrating-cinder-volumes-to-icehouse/</guid><description>&lt;p&gt;I upgraded my all in one OpenStack Havana box to the new &lt;a href="http://www.openstack.org/software/icehouse/"&gt;Icehouse&lt;/a&gt; release. All the same steps apply as in &lt;a href="https://cunninghamshane.com/posts/my-all-in-one-openstack-deployment-at-home/"&gt;my all in one OpenStack deployment&lt;/a&gt; post except use &lt;a href="http://rdo.fedorapeople.org/rdo-release.rpm"&gt;http://rdo.fedorapeople.org/rdo-release.rpm&lt;/a&gt; which now redirects to the Icehouse RPM. I wanted to blow everything away and not perform an upgrade. The only issue I ran into was I boot my VMs with Cinder volumes for persistant storage (just use LVM to create a volume group named &amp;ldquo;cinder-volumes&amp;rdquo;) and I wanted to move those to Icehouse with the data untouched.&lt;/p&gt;</description></item><item><title>Cloud Block Storage and NFS</title><link>https://cunninghamshane.com/posts/cloud-block-storage-and-nfs/</link><pubDate>Sat, 25 May 2013 20:34:33 +0000</pubDate><guid>https://cunninghamshane.com/posts/cloud-block-storage-and-nfs/</guid><description>&lt;p&gt;With &lt;a href="http://www.rackspace.com/cloud/"&gt;Rackspace Cloud&lt;/a&gt; you can use &lt;a href="http://www.rackspace.com/cloud/block-storage/"&gt;Cloud Block Storage&lt;/a&gt; and NFS to create shared directories amongst your &lt;a href="http://www.rackspace.com/cloud/servers/"&gt;Cloud Servers&lt;/a&gt;. This setup was done on CentOS 6.3 and used the internal Cloud Server interfaces. First, attach your Cloud Block Storage to your Cloud Server. When I attached mine, it was designated /dev/xvdb. We will need to create a partition and format.&lt;/p&gt;&#10;&lt;figure class="code-block"&gt;&#10; &lt;figcaption class="code-bar"&gt;&#10; &lt;span class="code-title"&gt;console&lt;/span&gt;&#10; &lt;span class="code-meta"&gt;&#10; &lt;button type="button" class="copy-btn" data-copy&gt;Copy&lt;/button&gt;&#10; &lt;/span&gt;&#10; &lt;/figcaption&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-console" data-lang="console"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="gp"&gt;[root@nfsserver ~]#&lt;/span&gt; fdisk /dev/xvdb&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="go"&gt;n #create partition&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="go"&gt;defaults #can use defaults to use entire disk&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="go"&gt;w #write changes&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="gp"&gt;[root@nfsserver ~]#&lt;/span&gt; mkfs.ext4 /dev/xvdb1 &lt;span class="c1"&gt;#create ext4 filesystem on the partition&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/figure&gt;&#10;&lt;p&gt;Here we create a directory to mount our Cloud Block Storage and mount it.&lt;/p&gt;</description></item><item><title>Adding local SATA drive to VM using RDM</title><link>https://cunninghamshane.com/posts/adding-local-sata-drive-to-esxi-using-rdm/</link><pubDate>Sun, 19 Feb 2012 14:01:35 +0000</pubDate><guid>https://cunninghamshane.com/posts/adding-local-sata-drive-to-esxi-using-rdm/</guid><description>&lt;p&gt;My whitebox ESXi build did not go as well as I had hoped. Even though my ASUS M4A88T-M/USB3 motherboard has the IOMMU setting available under Secure Virtual Machine, it does not appear to work. Secure Virtual Machine should allow the motherboard and a compatible AMD-V CPU to passthrough devices directly to the VM using VMWare DirectPath I/O. I needed this since I have 2 x 2 TB hard drives with all of my data that I wanted to use for my fileserver VM. These drives already have data on them and I needed to pass them to the VM without putting any VMFS on the disks.&lt;/p&gt;</description></item><item><title>TRIM on your non-Apple SSD</title><link>https://cunninghamshane.com/posts/trim-on-your-non-apple-ssd/</link><pubDate>Mon, 23 Jan 2012 20:52:33 +0000</pubDate><guid>https://cunninghamshane.com/posts/trim-on-your-non-apple-ssd/</guid><description>&lt;p&gt;&lt;a href="http://en.wikipedia.org/wiki/TRIM"&gt;TRIM&lt;/a&gt; is only officially supported by Apple for the SSDs that they install on their Mac line. If you install your own SSD you can still enable TRIM with Terminal and some commands or use a program called &lt;a href="http://www.groths.org/"&gt;TRIM Enabler&lt;/a&gt;. I used beta 4 version of the program on my Intel X25-M G2 160GB SSD and it worked perfectly. The author just released version 2.0. Below is a short write up from Anandtech.&lt;/p&gt;</description></item><item><title>Getting OS X Lion working with network share</title><link>https://cunninghamshane.com/posts/getting-os-x-lion-working-with-network-share/</link><pubDate>Sat, 08 Oct 2011 08:44:00 +0000</pubDate><guid>https://cunninghamshane.com/posts/getting-os-x-lion-working-with-network-share/</guid><description>&lt;p&gt;Mac OS X Lion broke the ability for Time Machine to backup to a network share over Samba. I usually backup everything to a Windows Server 2008 R2 computer running headless in my closet, but OS X Lion will not connect any longer due to AFP 3.3 being used. I still haven’t found a way for my iMac to connect directly to the server but I have a workaround that might work for you.&lt;/p&gt;</description></item></channel></rss>