A while back there was a buzz on Twitter about the EMC Elect program. I didn’t know what it was, so I reached out to Matthew Brender to find out more.
If you are familiar with the VMware vExpert program, EMC Elect is a very similar program.
I’m going to keep this post short, as I’m sitting here in the Delta Sky Club in Terminal D, and quite frankly don’t know what to say.
I received an email with some pretty exciting news (to me at least). I have been selected as an EMC Elect Inaugural Member for 2013.
Apparently I made some type of impact with contributions on Twitter, the EMC Community Network, and through my Isilon blog posts.
I’d like to thank all of those that recommended me, and for Matt Brender’s email welcoming me to this group.
“Jase, for your incredible leadership around Isilon evangelism and just pure, humble dedication to the greater community, I’m thrilled to send you this email.” – Matthew Brender
I am truly honored to have been selected as an inaugural member of EMC Elect for 2013.
I guess I need to get back to Twitter/ECN/Blogging, so I can keep it up for next year…
Look for some more Isilon posts in the coming weeks…
So OneFS 7.0 has been announced. Some of the new features include some virtualization components, specifically around VMware integration.
One of those integrations, is around VASA.
I’m not going to go deep into VASA, I’ll let the above link do that.
With Isilon OneFS 7.0, it is very easy to implement VASA integration.
To get started, the VASA service needs to be enabled from within OneFS 7.0. The command for this is “isi services isi_vasa_d enable”
Looking back that the SmartConnect Part I post, remember that SmartConnect is handling DNS delegation of the SmartConnect Zone name (FQDN)… So… What happens if the SmartConnect Zone for an NFS data network is on an isolated network? Keep in mind, that DNS needs to contact the SmartConnect Service IP to request an IP resolution for the FQDN. How can this happen if the SmartConnect Service IP for that zone is on an isolated network?
The first network defined for the “front-end” is typically configured as subnet0. It is a common practice to leverage subnet0 for the management of an Isilon cluster. When using IP based storage in vSphere environments, it is a best practice to have the storage traffic isolated from the regular network. In my previous posts (SmartConnect Part I & SmartConnect Part II) the SmartConnect Zone was on the same subnet/pool. When this is the case, and isolated networks are being used, it is impossible to leverage SmartConnect on the isolated network, unless there is a DNS, and subsequent delegation, in that isolated network.
VMworld time is here again. And for the 4thd year, EMC is hosting a v0dgeball tournament to benefit the Wounded Warrior Project.
The folks at WWP have a primary mission of:
- Raising awareness and enlist ingthe public’s aid for the needs of injured service members.
- Helping injured service members aid and assist each other.
- Providing unique, direct programs and services to meet the needs of injured service members.
Without your support, they cannot provide this vital assistance to our injured veterans.
So I have had my lab hosts for about a year. I have to say that they have done pretty well. Because of the cost I configured these hosts with 16GB of RAM each. At the time I built them, 8GB sticks of RAM were about $250 a piece, which was a little bit out of my price range. I recently found some 8GB Kingston memory that wasn’t going to break the bank, and give me the ability to do more than I have been able to.
The initial configuration included the following components, and cost around $1,650 ($825/host) not counting shipping/etc.
A year later some prices have changed, some additional processors are support on my boards, larger memory is a little cheaper, and SSD prices have declined.