<rant>Within our VCDX design documentation, why do we all have the habit of making assumptions? Examples:
Design Assumptions
AS01: Network Bandwidth between Datacenters is adequate for storage replication
AS02: Load-Balancers will be used to load-balance Horizon Connection Servers
AS03: There are enough DHCP IP Addresses available
AS04: AD / DNS / NTP is configured through the environment
Why are we assuming things like these? If your design relies on these ‘Assumptions’ to meet SLA’s then would it not be a good idea to actually find out if these ‘Assumptions’ are actually correct? Documenting assumptions is not a waiver that implies ‘this is the customers problem’. As an Architect it is your responsibility to assist your customers to by identifying areas of their existing environment that may or may not be able to support your design.
If your assumptions are incorrect, your design might not be worth the paper it is written on.</rant>
Another VMworld is upon us!!! Sadly, it's only virtual again this year. However, that does…
As part of my recent move to Google, I'm working on quickly getting up to…
I am delighted to announce the next chapter in my career. Today is my first…
In episode thirteen of The VCDX Podcast, I am joined by two special guests who…
In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…
In my recent ‘Getting started with Oracle Cloud VMware Solution (OVCS)’ post; Getting Started With…