Today is Wednesday November 9th, 2011. I have a few simple questions for you. Don’t over analyze. Go with your 1st instinct.
Question 1: When you see the written word ESX in a tool or documentation, what does it mean or imply to you?
A) ESX literally translates to ESX, an explicit VMware Type 1 hypervisor with a RHEL Service Console.
B) ESX is a marketing term which translates to ESX, ESXi, or both, two generations of Type 1 hypervisors from the VMware portfolio
Question 2: Is the written word ESX interchangeable with ESXi?
A) No
B) Yes
C) I really don’t care
Question 3: Should tools, documentation, and marketing make clear distinctions between ESX and ESXi?
A) No
B) Yes
C) I really don’t care
A – A – B
VMware needs to update all their dang documentation
I think we’ll see both ESX and ESXi for at least another year, then the “i” will get dropped and we’ll all move on as if it was never there
A, A, B: For now. As long as ESX (classic) is still supported and likely still well deployed around the industry. Only after it is very far from our minds (years from now) do I think you can get away with it.
It really frustrates me
A)
A)
B)
I wish it was clearly identified.
1 – A
2 – A
3 – B
Caveat; if a 5.0+ version is given, then “ESX” implies ESXi.
I prefer “vSphere Hypervisor”
Agreed with the rest, A, A, B.
A, A, B for sure. ESX is decidedly different than ESXi, even if they accomplish the same goal. If a product says it works with ESX but has no mention of ESXi I assume it won’t work with vSphere 5, or the vendor doesn’t care enough to get the details right. Neither of which are selling points.
What I’d like to know is what ESX means to VMware. They have a bad habit of renaming all sorts of things for (apparently) marketing reasons without warning. I’m really surprised ESXi hasn’t been renamed to VMware Sunrise, or some other equally pointless name.
A, A, B.
While I can understand the poster who states that “for v5.0+, ESX implies ESXi”, I have to disagree. ESX for v5.0 implies un unfamiliar speaker, to me.
Nope, I’m with Doug and against the rest of you so far – the ‘i’ is no longer needed, it’s only function was to differentiate it from another product that no longer exists.
For historical purposes, it could still be used in conjunction with version numbers to talk about specific releases during the period that both products existed, but going forward it makes sense to just called it ESX imho.
B-B-C
A-A-B
A, A, B
ESX and ESXi are two very different animals and there need to be a clear distinction.
AAB
A – A – B
A.
A.
B.
B – B – C
Especially with the release of 5 at this point, I see no reason to differentiate between them. My concern is that they provide the same capabilities at a hypervisor layer, not a “console” layer.
1) A – 2) A – 3) B
ESX looks like a typo, to me. 😉
A-A-B
It should be separated, damn it, and clearly stated. Drives me bonkers when I look in AD and see the ESX Admins group. UGH. I know I’m OCD, but still. I know many people that are still upset with the loss of ESX and its bloated COS… but I find they’re usually very fond of *nix. So am I, but a hypervisor shouldn’t have an operating system as part of the package. It certainly isn’t an operating system feature (DING).
It’s not the same thing, its different (in my mind) in ONLY good ways … its ESXi. There should be no confusion about it, and the only reason there is; is because VMware hasn’t made the distinction nearly clear enough.
A-A-B
B-C-C
I’ve used ESXi for a long time, long enough to assume there is no other version, although I know it is (or should I say was?) and even used it long time ago…
A-A-B
I started writing all my documentation and blog posts using the term ESX(i) just to avoid any confusion when referencing either as I was getting too many questions like “Does this also work with ESXi” when I had only mentioned ESX.
I thought it looked a bit bad when many presentations of VMworld 2011 around vSphere 5 most often than not used the word ESX representing a host.
When VMware has been spending a few years trying to teach their customers the distinction between ESX and ESXi they should be able to learn to.
AAB for me too.
A – A – B