The vExpert 2017 Applications are now open!

vexpert-624x111

Just to let you all know that you can now apply for the 2017 vExpert.

Hop over to http://blogs.vmware.com/vmtn/2016/11/vexpert-2017-applications-are-now-open.html to fill out your application.

I have already filled out mine, and fingers are crossed until February 8th when they announce the new vExperts for 2017.

I can only encourage you to apply, the vExpert community is truly outstanding and have made quite a few new acquaintances through this.

Good Luck

 

#VMworld T-shirts Review 2016 – Part 2

So here’s the second and last part of this T-Shirt review for this years VMworld. And as before I hope you can find this useful for Barcelona.

 

5. Platform 9 - front5. Platform 9 - Back

Name : Platform 9
Model: Next Level Apparel 60% Cotton 40% Polyester
Size: XL (why oh why no XXL ???)
QualityFeels really nice and soft and guessing the 40% polyester will help it stay better in shape than 100% Cotton.
Print: A city landscape with a Platform 9 blimp on it and a few different technologies that they support I guess, pretty low-key and thus usable elsewhere than home.
Score:  6(8)/10
Conclusion: I would have given this shirt an 8, but by not having XXL sizes I have to drop them down a few points. I mean why not bring XXL and since this was the US XXXL as well. I was almost tiny compared to some of the people there, and XL wont last more than 1 or 2 washes then they shrink 😦

 

6. Nimble Storage - Back 6. Nimble Storage - Front

Name : Nimble Storage
Model: C Port and Company 100% Cotton – Ring Spun
Size:  XL (Why do you only have XL in the US ????) and these are not US sizes
Quality:  Somewhat stiff version of this shirt, again have to wait and see whether or not this Ring Spun cotton does anything for shrinkage when washing these T-shirts.
Print: The Nimble Logo and then an kinda ugly red version of the vExpert logo both on the front and back. That would have been better with the normal White on Black.
Score:  5/10
Conclusion: Both the vExpert and only size XL drags this shirt down.

7. Cortado - Front

Name :  Cortado
Model:  C Port and Company – 100% Cotton
Size:  XXL
Quality:  A bit thicker than the other T-shirts from C Port, but otherwise seems quite ok. Guessing it will warp some when washed.
Print: A superman like version of the Cortado logo, but very stiff and you can feel that on the inside of the shirt.
Score:   6/10
Conclusion: What brings this shirt down is the Stiffness of the logo, which you can feel like plastic on the inside of the shirt.

 

8. Dell - Front 8. Dell Back

Name : Dell Software
Model: The Concert Tee – District 100% Pre-shrunk Cotton
Size: XXL
Quality:  First T-Shirt I’ve seen from this company, but being pre-shrunk it should hold up good when washed. Very soft and thin T-shirt
Print: A print that’s supposed to make it look like you have a clock on a gold chain around your neck. and a message that’s continue on the back.
Score:  6/10
Conclusion: The shirt is nice and soft and pre-shrunk should help a lot. But the print makes this another shirt I wouldn’t wear in public, but can be used around the house 🙂

 

That’s it for this year. As I wrote in the first post, I haven’t had much time in the Solutions Exchange and therefore didn’t get to grab that many T-Shirts this year.

I hope you still found this funny/useful/whatever 🙂

 

 #vExpert gifts at #vmworld

My humble opinion is that this years best vExpert gift comes from Datrium Storage


They gave out a Raspberry Pi 3 to all vExperts who had registered.

Cohesity had a really nice Timbuk2 backpack with a 6000mAh power bank, charger cables and a water bottle also a very nice and useful gift.

Over at the Nimble booth they gave out t-shirts, unfortunately the largest was XL and not American sizes.

Docker gave out a vExpert Cap and a T-shirt if you sat in on 15 min session about docker, by a very enthusiastic speaker.

At the Solidfire booth I picked up the new version of Cards against humanity and a pair of the famous Solidfire socks 😉

I saw that both Datacore and Catalogic Software had something too, but didn’t get around to picking those up.

Only sad thing this year is that no one did the really nice vExpert Polos, that I see a lot of fellow vExperts wear at VMworld.


But a BIG thank you to all the companies that decided to do something for the vExpert community.

PernixData FVP in the Home Lab Part 3. (SUCCESS)

I must admit that I think I have made quite a few mistakes in this Install.

I was told that 6.0 is not supported by PernixData yet, but it has been known to work. So I installed a 5.5 VCSA instead, and voila it joined my AD without any problems that the 6.0 had. (Guess I need to try the 6.0 VCSA again).  Then Uninstalled and Reinstalled the PernixData Management Software, and still no plugin showed up. My friend @FrankBrix told me to look at the log files of the FVP software, and yes it would obviously there. The logfiles clearly showed that the software couldn’t connect to the SQL server, and I Discovered I had entered the wrong password!. One thing there, I do think the Installed could have checked that instead of just writing it to a config file. After correcting that, the FVP plugin worked on 5.5.

I thought that I would give 6.0 a shot again before configuring anything in FVP, and I could also get the FVP plugin to the 6.0 vCenter. However it kept giving me authentication errors, each time I tried anything with FVP. So I went back to 5.5 (now my 4.th vCenter install) and followed the guide to create an FVP cluster. After that I tried to add resources to my cluster, but it kept saying that “No PernixData compatible hosts have been detected…” So I double checked that the VIB was actually installed and I tried rebooting the ESXi, but to no avail.

Again @FrankBrix to the rescue. We setup a WebEx and in like 30 seconds after he took over my screen he had solved my problem. After reinstalling and creating datacenters and clusters 4 times, the last time I had accidently forgotten to put my host INTO the cluster. No wonder FVP couldnt get any hosts.

With that fixed PernixData started its magic. And WOW I must say, I can already feel a big difference from the last days without caching, and I’m looking forward to seeing the write Cache in action once I get all my machines up to speed again.

And damn here 1½ hours after it was created look at these stats

FVP in action

57.000 IOPS saved from my small little 4 disk Synology, no wonder I can feel a big difference.

FVP Latency

And the Latency really has gotten down as well. you can see a Big spike at around 10:22PM from the datastore, but the VM never saw it. And this is from a single cheap Kingston SSD. Will have to try this out in a heavier environment than my homelab sometime soon. I will post more stats when this has been running for some time.

Once again a big thanks to @frankbrix http://www.vfrank.org/ for the help.

 

PernixData FVP in the Home Lab Part 1.

So I finally got around to upgrading my homelab to 32Gb ram, so I can run the vCenter all the time, which is needed for PernixData’s FVP solution. Also gotten a cheap Kingston v300 120Gb SSD for testing.

Been running for 2 weeks with vFlash Read Cache from VMware which seriously speeded up my homelab. However i did run in to one Caveat.

I had let the VCSA used some of the vflash as all the other servers, however i couldn’t start up my VCSA after a total shutdown of my homelab (to install the extra RAM).
Failing with a “Could not create vFlash cache: msg.vflashcache.error.VFC_FAILURE”. As its the vCenter Server that gives the vFlash out to the other server it seems that it can’t use it itself. I might be mistaken in this as I have not tested it again.

I found @h0bbel’s article on it, and removed vFlash from the vCenter Server and vupti it could boot, and after it had booted up, the rest of my servers could be booted normally.

With previously only 16Gb of ram, I had let the host use 30Gb of the 120Gb of the flash to Swap, and that was way faster than using my NAS. However it was still alot slower than after i had upgraded it to 32Gb of ram. It left with with roughly 90Gb of SSD to use for caching.

One thing I found annoying about vFRC from VMware is that it is per VMDK, meaning i had to edit each machine and set aside some part of the SSD for caching for that particular vmdk. I’d much rather have it use the SSD to boost the entire datastore, instead of trying to figure out how much each of the vmdk’s should have. As i have read Duncan’s tweets about it, that will be added in a coming version of vFRC.

As I have written earlier I was lucky enough to be selected as a PernixPro, and one of the nice benefits of that, is a NFR license to FVP. So that is what I’m going to install and write about in Part 2 of this blog post.