WFA Learning Lab Update

In the previous post I mentioned I’d share my lab design, and this is detailed in the table (image) below.

Image: Components of my WFA Learning Lab (click to enlarge)

It’s not quite as ambitious as what was suggested in HA/DR Lab Design with OCUM and WFA. Still, it’s not far off the components that might exist in a real world setup - SnapMirroring VMs to a DR site is always the easiest method of DR. Yes, it is missing OnCommand Performance Manager - I might add the Linux version at a later date - for learning about WFA this isn’t a requirement.

Q: How much memory does it consume?

The sum of the RAM column = 43 GB RAM

With everything powered off 3.0 GB RAM is committed by the underlying Windows 10 O/S and utilities.

With everything powered on 34.7 GB RAM is committed.

Image: Memory utilization before power on

Image: Memory utilization with all VMs powered on

Q: How much disk space does it consume?

Powered off, the lab consumes 156 GB disk space. I do not use linked clones for anything!

Powered on, the lab consumes an extra 43 GB disk space (same as the full memory requirement), to make a total of 199 GB disk.

Image: Free space on VM1 SSD (V:) and VM2 SSD (W:)*

*19GB taken up by other stuff not in the lab

Image: Free space after lab power up

Q: What is the point of the lab?

The mission is to completely build the storage infrastructure configuration using OnCommand Workflow Automation, and do all the common repetitive tasks using WFA. Where the workflows exist, we’ll use them. Where we need something custom, we’ll create it.

Automating build processes is extremely useful for large Enterprises that might have 100s of systems, and need a common build to make support easy, and maintain compliance. And it’s useful for small Enterprises too, where they may not have experienced storage admins, and want to build a best practice and easily supportable infrastructure. And everything in between!

Of course, all this is time permitting. I’ve been fortunate to have a window - between my normally very busy project workloads - to find lab time. For me, I learn best from projects, so if I don’t have a real-world project to work on, I’ve got to give myself a mini-project to help my learning and understanding. And without documenting what I’m doing, it’s a total waste of time (due to forgetfulness), hence I document. And there’s no pleasure in doing stuff solely for oneself, much more pleasurable to share, hence the documentation finds its outlet via the blog. I’m hoping to document further progress in future posts (perhaps not much this month though, vacation is coming up) - if it goes quiet though, I got busy, and I apologize for the derth.

THE END