Brilliant new adblocker – µBlock!

Hi all,

I’ve just discovered new adblocker which seems to be way easier on resources then Adblock Pro (which is a brilliant tool in every other way).

Check out µBlock.

So far it seems that my resource usage on my laptop is about ~15-20% lower then usual!

Bgrds,
FOG

Cool feature of Solaris IPS – Search for a CVE

Hi,

Just read a blog over at c0t0d0s0.org regarding searching installed packages by a CVE (Common Vulnerability and Exposures) number.

# pkg search -l CVE-2014-7187
INDEX ACTION VALUE PACKAGE
info.cve set CVE-2014-7187 pkg:/support/critical-patch-update/solaris-11-cpu@2014.10-1

Source here

Bgrds,
FOG

VCP – Going for the gold!

Howdy all.

Finally, after working with VMware virtualization products for more then 10 years I am finally going for the VCP.

The course has been booked in April if I remember correctly but I was hoping to finish the exam before that. To help me out I have two books, Mastering VMware vSphere 5.5 by Scott Lowe and VMware vSphere Design also by Scott Lowe, Forbes Guthrie and Kendrick Coleman.

Lets see if I can cram and take the exam before April!

Bgrds,
FOG

Configuring DNAT for Google DNS servers on Technicolor routers

Howdy all,

Stole the commands from: https://support.unlocator.com/customer/portal/articles/1501508-how-to-set-up-technicolor-router-for-chromecast

Add static routes for google dns servers Code:
nat mapadd intf=LocalNetwork type=napt outside_addr=8.8.4.4 inside_addr=192.168.1.254 outside_port=53 inside_port=53
nat mapadd intf=LocalNetwork type=napt outside_addr=8.8.8.8 inside_addr=192.168.1.254 outside_port=53 inside_port=53

save!
saveall

This will make sure all requests for Google’s DNS servers will be redirected to the router (which could have some other DNS servers, maybe some SmartDNS servers?).

Bgrds,
Finnzi

Yeah…the future of vCloud Director

Howdy,

I’ve been working with the vCloud Director for some time now. Now, late last year I started hearing some rumors that the future for the said product wasn’t all that bright.

Meh, I said. VMware won’t kill this product, It’s used by service providers and enterprises around the globe !

After reading loads of blogs and articles I came to the conclusion that the product would be staying with us for a long, long time.

Great I said – Let’s put our weight behind it and tell the world how awesome it is !

Boy was I wrong. Well…..at least I felt like VMware had thrown a snowball in the face of all the smaller service providers running vCloud.

The vCloud Director will be available for service providers for foreseeable future. However it will end up being “headless”, meaning that the web front is going away. Instead we will have the APIs to create our own interface on top of the vCloud Director.

I’m not sure when the product will be EoL’ed for enterprise customers. But vCAC would be the product they should be looking at instead.

The good thing is that most of the larger providers already have written their own interface. And there are even 3 or more commercial front ends available right now.

The bad thing is that the smaller ones will either have to write their own front end, buy a front end or start looking into other products.

Anyway – VMware: Not cool bro….not cool !

Maybe this would be the right time to start looking at an OpenStack powered front end for vSphere ?

Bgrds,
Finnzi

The death of vCloud Director have been greatly exaggerated !

Howdy,

Just saw this blog at blogs.vmware.com about the future of vCloud Director.

I had heard some rumors from the field (and the internetz) that vCAC would take over for the vCloud Director in the near future.

However it seems that vCloud Director will keep on going strong and the vCAC will be marketed towards the enterprises. Which is actually pretty cool I think.

At some point these products will probably collapse as one (or be built from pretty much the same code base).

Just found this blog interesting, especially after hearing about the death of the vCD 😉

Bgrds,
Finnzi

VMware: Datastore Clusters, StorageDRS and Thin Provisioning

Howdy all,

I recently migrated some VMs to use Thin Provisioned VMDKs since they had been provisioned with way too much diskspace. Our current setup only uses stand-alone VMFS volumes so it is a manual process to migrate the machines between datastores if and when the datastores are almost full. So I started thinking about datastore clusters (which I think are a pretty cool thing). How would this be managed in datastore clusters ?

After spending large amount of time googling and reading up on vSphere documentation I was still not 100% sure on how this worked exactly. So I sent a message to Larus Hjartarson (@lhjartarson).

Of course he had the answer 🙂

So – I decided to write this here so I would at least remember this:

StorageDRS will monitor the disk space. You choose the high-watermark for the datastore cluster. You also choose the watermark for how much would be gained from moving a VMDK from datastore X to Y.
StorageDRS will then monitor the datastore cluster every 8 hours (or any given time you configured). If it finds that datastore X or Y is nearing high-watermark and gain X percentage by migrating VMDKs to another datastore in the cluster it will either notify you or take action by migrating the VMDKs (by default it only notifies you).

Now, let’s go implement datastore clusters !

Bgrds,
Finnzi