| After reading the previous digest, someone has drawn my attention to the fact that the infamous KB2151749 about ESXi PSOD bug with 10Gb Ethernet NICs has been updated to include vanilla vSphere 6.5 as well. The issue was originally thought to be specific vSphere 6.5 U1 hosts only – and this indeed is the configuration were the issue has been most commonly observed among our customers. But, it looks like the bug is actually present in all existing vSphere 6.5 builds - perhaps, due to being a race condition, just with the different likelihood of triggering. So, something to keep in mind to avoid doing things like creating vmkernel ports during the production hours.
Also as a feedback on the previous digest, one of my trustees noted that there is actually one other tool for a vCenter like experience with KVM that I did not mention > oVirt. This is basically the open source project of Redhat's Virtualization Manager, and apparently it's pretty good too – a very easy to use web based management console, not at all unlike vCenter, that really simplifies managing Hosts, Clusters, Storage and Networking on Linux/KVM. So, something else to check out for those who are evaluating KVM managers.
And, just as I expected, of course I've got tons of love/hate feedback regarding my OpenStack statement. I didn't really need to engage though, because the "strongest" point only proved my statement – this person has noted that he runs an OpenStack with "only" 4 developers. Depending on where you are, this can cost you anywhere up to 0.5M – 1M USD per year on employee salary and other expenses alone... and just to put this in perspective, 4 developers is a solid team for certain major Veeam features, which some other companies have been successfully selling as standalone products – so yes, to me it IS a small army... and for sure, not too many Veeam customers will be ready to make such investment purely from TCO perspective comparing to just going with VMware vSphere (although OpenStack is actually more equivalent to vCloud Director, except with real cloud stuff like object storage/containers).
We've released Veeam Availability Console (VAC) last week and this is the biggest no-cost product release from Veeam yet. While it is primarily targeted at the service providers, there's also a version of this product for the enterprises (VAC-E) with a slightly different UI. And I wanted to clarify some confusion caused by the fact that VAC can also manage Veeam Agent for Windows now – just as the upcoming Update 3 for Veeam Backup & Replication 9.5, which left many wondering what should they be using for agent management – and how to determine if you are "enterprise-enough" for VAC-E? Short answer – if you have just a handful of well-connected IT locations (datacenters or offices), then you are better off sticking with B&R for simplicity. However, if you are managing dozens of IT locations (think grocery store chain) and they are not VPN-connected – then introducing the additional complexity of VAC-E infrastructure will actually reduce the overall TCO. Especially if you also have the requirement to centralize your backups into HQ, as VAC-E plays hand-in-hand with VCC-E (Veeam Cloud Connect for Enterprise). TL;DR version: stick with B&R 9.5 U3 unless you are in charge of a very distributed environment and operate much like MSP for those countless remote offices.
I have pretty good ears for music, and has been into Hi-Fi since I learnt of its existence – so I always hated any and all "sound enhancers" out there. But my recent discovery of Adapt Sound feature in Galaxy S8 has changed this. This stuff is brutal, and it works because what it does is technically right thing to do. The feature is very well-hidden – in the main Settings menu, tap "Sounds and vibration", scroll down and select "Sound quality and effects". Leave all enhancers disabled and tap "Adapt Sound" towards the bottom. You'll be asked to grant additional permission, so press "Allow" and from there, leaving presets turned off, select "Personalize sound". Next, you'll need to pass a test of your unique ears + earbuds combination. Picking a quiet place is essential, because the test emits barely audible beeps of varying frequencies – and you're supposed to honestly answer if you can hear each tone. When in doubt, hit No – because what happens here is the creation of personalized equalizer tailored to each ear and earbud. Thing is, there are some frequencies – different for everyone – which our ears cannot hear well (especially as we get older), and there are some other frequencies which earbuds simply cannot emit well (the frequency response graph for even most expensive earbuds looks like a cardiogram) – so granularly boosting the output of those specific frequencies makes the perfect sense. And I have been completely blown away by the result. |
Komentáře
Okomentovat